Name convention
BPXSLUSH_<CompanyNumber>_<DateTime>_<SEQNO>[<BatchId>].DAT
| Names Component | Description |
|---|---|
| CompanyNumber | The company number in PayEx ledger system |
| DateTime | Date created in format YYYYMMDDHHMMSS |
| SEQNO | Unbroken serial number sequence. |
| BatchId | Billing process Id |
For example: BPXSLUSH_99999_2020040523121243_00123[123456].DA
Change log
| Version | Date | Description | Created by |
|---|---|---|---|
| 1.2 | 2021-02-23 | Created document | Daniel Olsson |
General information and explanation of records
The report BPXSLUSH is a part of the billing error correction system. When logical error occurs in rating system, such as “Missing destination code in DP file” or “Identifier is missing in customer set”, the CDR record is put in suspense (Slush file).
The BPXSLUSH report contains information about unsuccessful rated CDRs and the associated reason why they failed.
Records in the BPXSLUSH report contain individual CDR information and information about from which CDR file the CDR was originated
The report is produced during normal rating and when the Slush set get reprocessed.
Logic
Logic rating
When a CDR file is processed (normal rating) and a CDR cannot be processed due to a logical error, only T1 records will be presented in the BPXSLUSH report. T1 records indicate that new CDRs have logical error and will be added to the Slush file.
Logic re-rating
When the Slush file is processed (re-rating), the first record in BPXSLUSH report is a T6-record. T6 record indicates that all the T1 records in the report will represent the entire Slush file. The receiving system can replace all previous records for this slush file ID.
File description
All fields in the mentioned reports are separated with semicolons ”;”. The format field is written in the way that numerical values are written as N and alphanumerical characters are written as X. where ”n” is the maximum number of characters/digits or in certain cases number of characters that must exist.
Dot “.” is decimal separator on fields with amount. Some records are not obligatory but if they exist can some fields in the record be obligatory. Obligatory records are described with the abbreviation ” Req.” in the type column.
H - Header record
| Field name | Field no. | Format | Type | Description |
| Recordtype | 1 | H | Req. | Header record. |
| CompanyNumber | 2 | N(5) | Req. | You receive the company number from PayEx. |
| CompanyName | 3 | X(40) | Req. | Your company name |
| Creationdate | 4 | N(6) | Req. | YYMMDD– Same date as in the file name |
| Creationtime | 5 | N(4) | Req. | HHMM – Time when the file was created. |
T - Usage records
Below you will find a description of the different usage records
T1 - Adding new slush record after rating process
| Field name | Field no. | Format | Type | Description | ||||
| Recordtype | 1 | T1 | Req. | Recordtype | ||||
| CDRId | 2 | N(19) | Req. | Unique ID on CDR. Default created by Payex | ||||
| YearMonth | 3 | YYYYMM | Req. | YYYYMM | ||||
| ErrorCode | 4 | N(9) | Req. | Errorcode See Errorcodes | ||||
| FileName | 5 | X(100) | Req. | Original file name | ||||
| RowNumber | 6 | N(9) | Req. | Row number in the original cdr CDR file | ||||
| ProcessId | 7 | N(9) | Req. | Payex processID for rating | ||||
| CompanyNumber | 8 | N(8) | Req. | Company number | ||||
| FileFormatgroup | 9 | N(8) | Req. | Groupnumber where rating has been processed | ||||
| FileFormatName | 10 | X(20) | Req. | Fileformat for CDR-file | ||||
| SlushFileId | 11 | N(9) | Req. | Identification number for file name (Slush) | ||||
| FileExtension | 12 | X(100) | Additional file extension | |||||
| CustomerNumber | 13 | X(15) | Identification number from customer information | |||||
| SubscriberID | 14 | X(19) | Req. | Identification for CDR. (Customer,ANR/IMSI/CLI) | ||||
| StartDateSubscription | 15 | YYYY-MM-DD | Subscription start date | |||||
| EndDateSubscription | 16 | YYYY-MM-DD | Subscription end date | |||||
| UsageType | 17 | X(10) | Type of usage. See Usage codes | |||||
| Details | 18 | X(25) | Dialed number (BNR or Specifikationstext) | |||||
| DestinationCode | 19 | X(15) | Destinationcode for ”perfect match” | |||||
| DestinationMatchingMethod | 20 | N(2) | Method to match search string (BNR) to destination code. See Destination match methods | |||||
| StartDestinationscode | 21 | X(15) | Destination code for startfee | |||||
| StartDateTime | 22 | YYYY-MM-DD HH:MM:SS | Req. | Date and time of call start, "timestamp" | ||||
| Charge | 23 | N(9).(3) | Initial cost of the call. From the CDR's charge field | |||||
| Volume | 24 | N(19) | Req. | Volume: number, seconds, mb etc. depending on volume code | ||||
| Volumecode | 25 | X(10) | Volume column unit. See Volume codes | |||||
| VAT | 26 | N(2).(2) | The VAT rate of the call | |||||
| IpAddress | 27 | X(15) | Ip Address | |||||
| External reference | 28 | X(20) | External CDR Id or other reference from CDR file | |||||
| PLMNcode | 29 | X(10) | Code used for roaming that informs about which foreign operator was used. | |||||
| PriceListMinuteFee | 30 | X(10) | Price list note used for the minute fee. Only suitable for error code 26 | |||||
| PriceListStartFee | 31 | X(10) | Price list designation used for the startup fee. Only sutable for error code 26 | |||||
| ServiceProvider | 32 | X(25) | Code that identifies a service provider | |||||
| CountryCode | 33 | X(3) | Code used for roaming that informs about from which country the call has been made | |||||
| PortabilityDirectionPrefix | 34 | X(8) | Route Portability Direction Prefix (BNET) | |||||
| Tariff | 35 | N(1) | Code for tariff used for the start of the call. Only suitable for error code 26. See Tariff codes | |||||
| DPFileVersion | 36 | YYYY-MM-DD | Version of the DP file used for the call. Only suitable for error code 26 | |||||
| Error code description | 37 | X(300) | Description of error category | |||||
| Reserved | 38 | |||||||
| Reserved | 39 | |||||||
| Reserved | 40 | |||||||
T3 – Remove record during rating process
This record will be used if there are CDRs deleted from Slush set. The T3 record can also be used when CDRs are removed directly from the CDR process.
| Field name | Field no. | Format | Type | Description |
| Recordtype | 1 | T3 | Req. | Recordtype |
| CDRId | 2 | N(19) | Req. | Unique ID on CDR. Default created by Payex |
| YearMonth | 3 | YYYYMM | Req. | YYYYMM |
| Code | 4 | N(9) | Req. | See Error codes |
| FileName | 5 | X(100) | Req. | Original file name |
| RowNumber | 6 | N(9) | Req. | Row number in the original CDR file |
| ProcessId | 7 | N(9) | Req. | PayEx process ID for rating |
| CompanyNumber | 8 | N(8) | Req. | Company number |
| FileFormatgroup | 9 | N(8) | Req. | Group number where rating has been processed |
| FileFormatName | 10 | X(20) | Req. | Fileformat for CDR-file |
| SlushFileId | 11 | N(9) | Req. | Identification number for file name (Slush) |
| FileExtension | 12 | X(100) | Additional file name extension | |
| CustomerNumber | 13 | X(15) | Identification number from customer information | |
| SubscriberID | 14 | X(19) | Req. | Identification for CDR. (Customer,ANR/IMSI/CLI) |
| External reference | 15 | X(20) | External CDRId or other reference from CDR file | |
| StartDateTime | 16 | YYYY-MM-DD HH:MM:SS | Req. | Date and time of call start, "timestamp" |
| Error code description | 17 | X(300) | Description of error category | |
| Source for delete | 18 | X(1) | Req. | 0 = Removed directly from CDR file, 1 = Removed from existing Slush set |
| Reserved | 19 | |||
| Reserved | 20 | |||
| Reserved | 21 |
T6 - Delete slush record directive.
The T6 record is used for total synchronization of Slush set in the receiving system. The T6 record indicates that complete Slush set will follow in the file. Following T1 entries will replace previously loaded entries.
T6 record is only produced when processing the Slush file in PayEx billing system
| Field name | Field no. | Format | Type | Description | |
| Recordtype | 1 | T6 | Req. | Delete record | |
| SlushFileId | 2 | N | Req. | Identification number for the Slush set (part of Slush file name) |
S - Trailer record
| Field name | Field no. | Format | Type | Description |
| Recordtype | 1 | S | Req. | Trailer record |
| Number of records | 2 | N(9) | Req. | Total number of records including header and trailer |
Example
H;123456;Company name;201202;1539
T3;15924707952557681;202008;420;CDRF5_123456_200922093247_00001.DAT;231735;696295;123456;123456;CDRF5;1608;;CustNo1;Subscr1;1036;2020-08-21 15:27:07;Deleted calls;1;;;
T6;1608
T1;4880930000000017;202009;71;CDRF5_123456_200930195553_00001.DAT;16;709008;123456;123456;CDRF5;1608;;CustNo1;Subscr1;;;VO;4608;DESTKOD1;1;;2020-09-30 19:44:15;0.140;12;S;25.00;;1037;;;;;;;;;Warning: No suitable destination code in DP-file (Perfect match).;;;
T1;4880930000000018;202009;71;CDRF5_123456_200930195553_00001.DAT;17;709008;123456;123456;CDRF5;1608;;CustNo1;Subscr1;;;VO;4608;DESTKOD2;1;;2020-09-30 19:47:12;0.080;7;S;25.00;;1038;;;;;;;;;Warning: No suitable destination code in DP-file (Perfect match).;;;
T1;4880930000000035;202010;45;CDRF5_123456_200930195553_00001.DAT;31;709008;123456;123456;CDRF5;1608;;CustNo1;Subscr1;;;VO;4608;1111;1;;2020-10-01 07:00:14;3.100;270;S;25.00;;1039;OOOOO;;;;;;;;Warning: Unknown GSM operator.;;;
T1;5431024000000085;202010;73;CDRF5_123456_200930195553_00001.DAT;33;709008;123456;123456;CDRF5;1608;;CustNo1;Subscr1;;;VO;460900;2222;1;;2020-10-24 11:24:05;47.420;143;S;0.00;;1040;;;;CP_xyz;;;;;Warning: Unknown content provider.;;;
S;8
Translation tables
Error codes
| Error Code | Description | Related to receipt code |
| 21 | Warning: Subscriber uses an unknown pricelist. | 262 |
| 24 | Warning: Unknown subscriber. | 260 |
| 25 | Warning: Unknown subscriber at the time of the record. | 261 |
| 26 | Warning: Missing destination or pricelist at the time of the record. | 263 |
| 36 | Warning: Missing destination or pricelist at the time of the record. | 263 |
| 40 | Warning: Unknown subscriber (IMSI) at the time of the record. | 261 |
| 41 | Warning: Unknown subscriber (IMSI). | 260 |
| 45 | Warning: Unknown GSM operator. | 264 |
| 55 | Warning: Unknown GSM operator. | 264 |
| 60 | Warning: No suitable destination code in DP-file. | 259 |
| 61 | Warning: No suitable destination code in DP-file (Perfect match). | 259 |
| 64 | Warning: Country not member in companydefined roamingzones. | 311 |
| 65 | Warning: Charge on hidden traffic. Not allowed. | 313 |
| 70 | Warning: No suitable destination code in DP-file. | 259 |
| 71 | Warning: No suitable destination code in DP-file (Perfect match). | 259 |
| 73 | Warning: Unknown content provider. | 427 |
| 74 | Warning: Country not member in companydefined roamingzones. | 311 |
| 75 | Warning: Charge on hidden traffic. Not allowed. | 313 |
| 76 | Warning: CDR is untreatable at the moment. | 314 |
| 81 | Warning: Missing matching content provider | 309 |
Information codes
| Information Code | Description | Related to receipt code |
| 420 | Removed by age criteria | 274 |
Usage code
| Usage code | Usage code description |
| VO | Voice call Originated |
| VT | Voice call Terminated |
| SMSMO | SMS Originated |
| SMSMT | SMS Terminated |
| MMSMO | MMS Originated |
| MMSMT | MMS Terminated |
| GPRS | GPRS |
| SMSKV | SMS confirmation |
| SVC | Service |
Destination match methods
| MethodCode | Method |
| 1 | Perfect Match |
| 2 | Dynamic match priority 1 |
| 3 | Dynamic match priority 2 |
| 4 | Dynamic match priority 3 |
| 5 | Dynamic match, requires agreement with PayEx for setup |
Volume codes
| Volume Unit Code | Used text |
| N/A | Unknown volume unit |
| S | Seconds |
| E | Event |
| B | Byte |
| KB | Kilobyte |
| MB | Megabyte |
| GB | Gigabyte |
Tariff codes
| Tariff code | Used text |
| 0 | Unknown/Not used |
| 1 | Low |
| 2 | Mediumhigh |
| 3 | High |