This document is an innovation requisite specification material, of extremely technical content. |
General Information
Specification | |||
Product | Microsiga Protheus | Module | Travel and Tourism Management |
Executor Segment | Services | ||
Project1 | M_SER_SER015 | IRM1 | PCREQ-4320 |
Requisite1 | PCREQ-4322 | Subtask1 | |
Planned Delivery Release | 12.1.8 | Copy |
|
Country | ( x ) Brazil ( x ) Argentina ( x ) Mexico ( x ) Chile ( x ) Paraguay ( x ) Ecuador ( x ) USA ( x ) Colombia ( ) Other _____________. | ||
Others | <If needed, enter other references pertaining this specification. Example: links of other related documents or subtasks>. |
Caption: 1 – Innovation 2 – Maintenance (you must fill out the other fields for both processes).
Routine | Operation Type | Menu Option | Business Rules |
[TURA038] | [Creation] | [Updates -> Provider Reconciliation -> Agent Billing Analysis] |
|
[TURA038IMP] | [Creation] | [Updates -> Provider Reconciliation -> Agent Billing Analysis -> Other Features -> Import A.B.A.] |
|
Objective
To develop a routine to register the ABAs sent by the various providers of the travel agency. Besides the regular operations of addition, edition and deletion, the routine must import TXT files, with invoicing data, sent by the airlines or by invoicing consolidators (example: BSP).
Definition of Business Rule
The Add / Import routine is the register that receives one or more files, regarding the ABAs sent by the airlines or consolidator companies. You can send these ABAs two ways: electronically and physically; either way, you must add/import them through this register.
You can combine the electronic ABAs to contain items from various companies. Generally, you will send them to the agency through a financial or invoicing consolidation company (such as BSP), or send them through the airline itself. In both cases, the system only generates one addition/importation record, in which the key is the ABA number.
Each airline or consolidation company has its own layout. Nevertheless, the ABA items are imported to a single system table with the data duly consolidated. In other words, according to the layout entered, a process is initiated in order to identify the attributes of the ABA with the respective attributes of this table.
As some companies send various electronic files from the same period, separated by service station (IATA), the system offers a feature for you to import all files from a directory. It is noteworthy that a record is created in the ABAs Table for each file imported, referent to the ABAs sent, correlating each item imported to its source file.
You can import the file(s) of an ABA more than once. To do so, you must delete the record of the ABA previously added/imported, also consequently deleting its respective items. Nevertheless, you can only delete an ABA if no item related to it has been approved. To meet this need, this register offers the option of undoing the item approval processes.
When you add or import an ABA, the system provides a parameter setting interface in which you can enter the import type, the provider (which can be of report), month, year, periodicity, period, issue date, due date, the number, the total value and the layout of the ABA. All such data is stored in a system table.
Electronic ABAs do not require entering the ABA data, as the aforementioned integration process is responsible for identifying the information. Regarding ABAs lacking a number entry, the system generates a provisional number, which you may change if you wish. After reconciling the ABA, you can no longer change this number.
Moreover, in the case of an electronic ABA, the system automatically imports the items into a Tourism module table. Regarding physical ABAs, you must use the same interface to normally add them and, regardless of it being physical, you can record the ABA file name in the register. However, distinctly from an electronic ABA, you must add the items of a physical ABA manually and, after adding them, run the Association process through the button displayed on the import screen.
The layouts offered for adding or importing ABAs consider the information of ABAs from air providers and other types of products sold by the travel agency. When you add or import an ABA, a field is available at the header for registering the layout of origin, from the following options: Airline Locator (GOL), Airline Ticket (BSP) and Airline Manual.
In ABAs from airlines or consolidator companies, information on issues and reissues pertaining air product sales made by the travel agency. Once the import process is finished, the routine associates the ABA items with the possible and respective Reservation Documents. To accomplish this, Ticket Number and/or Locator data are used in accordance with the layout selected.
The import routine will be elaborated through the MILE tool. For purposes of deploying the SIGATUR module, the layout import prior settings are available in the XML format, to incorporate the layouts to the environment of the customer. Importing in MILE uses a MVC standard adapter, which shares its Model with an ABA addition routine used for manual entries (by typing) for occasions when the airline or the consolidator company does not send interface files, such as the case of Azul Airlines. The same process is used for an ABA.
Operations
Name | Description | Considerations |
Add | Add or Import an A.B.A. | You can only add or import an A.B.A. once |
Edit | Editing an A.B.A. | When you edit an ABA, you perform the processes of Association and Adjustment for those ABA items with divergences and lacking adjustment. |
View | Viewing an A.B.A. | Non-applicable |
Delete | Deleting an A.B.A. | You can only delete ABAs with items that have not been Approved. |
Technical Definition
G6H_PERCID | Consistency | G6H_PERIOD |
Weekly | The value of the attribute must be above or equal to 1 and below or equal to 4. | 1 to 4 |
Ten Day Period | The value of the attribute must be above or equal to 1 and below or equal to 3. | 1 to 3 |
Fortnightly | The value of the attribute must be above or equal to 1 and below or equal to 2. | 1 and 2 |
Monthly | The value of the attribute must be 1 | 1 |
Twenty Day Period | The value of the attribute must be above or equal to 1 and below or equal to 2. | 1 and 2 |
G6H_TIPO | Field | Required | |
Yes | No | ||
"Directory" or "File" | G6H_ARQUIV | X |
|
G6H_LAYOUT | X |
| |
G6H_FATFOR |
| X | |
G6I_EMISSA |
| X | |
G6H_VENCTO |
| X | |
G6I_TARIFA |
| X | |
"Physical" | G6H_ARQUIV |
| X |
G6H_LAYOUT |
| X | |
G6H_FATFOR | X |
| |
G6I_EMISSA | X |
| |
G6H_VENCTO | X |
| |
G6I_TARIFA | X |
|
The layout of the GOL ABA contains airline sales, identified by the ABA number, the PNR code and the number of the ticket issued.
The GOL ABA file structure is of CSV type, with a variable number of rows reflecting the sales quantity in the period referred to by the file, including transactions of domestic sales as well as of international sales and refunds. The segments containing the transactions do not have a specific separator type, just an identifier indicating that, at some point, there is a segment with international sales, with domestic sales or with refunds.
Thus, we have the following GOL file structure in the table below:
ID (for reference in the from/to) | Row | Description | Example |
GOL001 | 1 | Name of provider that issued ABA. | VRG AIRLINES S/A |
GOL002 | 2 | Provider address | Av. Vinte de Janeiro, S/nº Terminal 02 |
GOL003 | 3 | Postal Code, city and state of provider | CEP:21.941-570;Rio de Janeiro;RJ |
GOL004 | 4 | Provider CNPJ | CNPJ:;07.575.651/0001-59 |
GOL005 | 5 | ABA number | ABA:;57518016 1410311 |
GOL006 | 6 | ABA period | Period:;10/31/2014 |
GOL007 | 7 | ABA due date | Date due:;13/11/2014 |
GOL008 | 8 | Header row with agency information | Agent;Name;Address;POSTAL CODE;CNPJ |
GOL009 | 9 | It contains the agency code, name, address, Postal Code and CNPJ. | 57518016;WALHALATUR - MANTECORP;AV. SAO LUIS, 50 - CJ 41 A - SAO PAULO - SP;01046-00;66822537000145 |
GOL010 | 10 | Header row with sales information and other agency values. | PNR;Ticket;Date;Tariff Paid Cash;Tariff Credit;Fees;DU;CC DU/SU;Commissions;Incentive;Net;Notes. |
The first ten rows of the ABAs file of the GOL layout are displayed the same way; that is, regardless of the file received, the initial structure is composed of the ten rows described in the table above. The ABA presents the sales from the tenth row onwards, which can be domestic, international or refund.
To identify the sales to be presented, the ABA presents the rows for domestic and international sales as follows:
Each of these blocks is broken by a row that contains the sub-total of sales types. For example:
In each block, of domestic as well as international sales, the refund segment is added to each sales block, containing the refund transactions of this period.
The sales transactions in the file are presented as shown below (each column in from/to corresponds to ID GOL010A to ID GOL010L):
Domestic sales:
ABK85P;2134473232;22/10/2014;0,00;856,90;107,26;-85,69;2,36;0,00;0,00;-83,33;CA 5314************
AB9U6C;2135286244;31/10/2014;0,00;1818,80;220,40;-181,88;5,00;0,00;0,00;-176,88;CA 5314************
ADCSKM;2135187290;30/10/2014;0,00;1395,80;175,19;-139,58;3,84;0,00;0,00;-135,74;CA 5314************
AEUBNW;2134582030;23/10/2014;0,00;446,90;66,26;-44,69;1,23;0,00;0,00;-43,46;CA 5314************
AEUZNW;2134384482;21/10/2014;0,00;235,90;64,03;-40,00;1,10;0,00;0,00;-38,90;CA 5314************
AM4ENB;2134712095;24/10/2014;0,00;1589,90;180,56;-158,99;4,37;0,00;0,00;-154,62;CA 5314************
BCG6QP;2134405329;21/10/2014;0,00;114,90;63,37;-40,00;1,10;0,00;0,00;-38,90;CA 5314************
BCG7QP;2134405330;21/10/2014;0,00;511,90;72,76;-51,19;1,41;0,00;0,00;-49,78;CA 5314************
BDHV2J;2134504079;22/10/2014;0,00;362,90;64,03;-40,00;1,10;0,00;0,00;-38,90;CA 5314************
BHZ4SQ;2134415609;21/10/2014;0,00;904,90;112,06;-90,49;2,49;0,00;0,00;-88,00;CA 5314************
BL6GPE;2134460302;22/10/2014;0,00;1415,80;187,18;-141,58;3,89;0,00;0,00;-137,69;CA 5314************
BMGZWB;2134631036;23/10/2014;0,00;836,80;126,82;-83,68;2,30;0,00;0,00;-81,38;CA 5314************
BYIKNV;2134632703;23/10/2014;0,00;409,80;84,12;-40,98;1,13;0,00;0,00;-39,85;CA 5314************
B9DDFY;2134401509;21/10/2014;0,00;172,90;63,37;-40,00;1,10;0,00;0,00;-38,90;CA 5314************
B9DDFY;2135189377;30/10/2014;0,00;0,00;0,00;0,00;0,00;0,00;0,00;0,00;VI 4108************
In the example above, you can see that the same locator can occur more than once, which indicates a rebooking, change, etc., for that locator, creating different tickets.
After some rows, certain fees and fines are shown with the following row identifiers, as follows:
If the block is of international sales, the block starts as follows:
OS;;;;;20,00;;;;;;;;;
AA;;;;;240,00;;;;;;;;;
DT;;;;;-1,80;;;;;;;;;
XC;;;;;100,00;;;;;;;;;
DP;;;;;-24,02;;;;;;;;;
OCDiffs;;;;;-45,00;;;;;;;;;
OCPenalty;;;;;467,90;;;;;;;;;
OCNoShow;;;;;150,00;;;;;;;;;
OCReemb;;;;;64,12;;;;;;;;;
Notice that, in the rows above, all values displayed are arranged in column "Fees", which is the sixth column from left to right.
The table below describes all fee types occurring in the GOL integration file and their descriptions:
Code | Description |
AA | Change fee |
AI | Animal transport fee |
AV | Fee by kilogram - animal |
BD | Declared luggage |
C1 | Scheduled cancellation fee |
C2 | Scheduled change fee |
C3 | Promotional cancellation fee |
C4 | Operator cancellation fee |
C5 | Promotional change fee |
CA | Cancellation change |
CD | Cancel/Charge fee for tariff |
CE | Group cancellation fee |
CH | Family change fee |
CL | Group cancellation fee |
CN | Group cancellation |
CX | Family cancellation fee |
CY | 24hrs cancellation fee |
DW | Downgrade FEE |
FR | Charge back |
GR | Regular groups cancellation fee |
MN | Assistance to unescorted minor |
NC | No show |
NS | No show |
OC | Call center fee |
OS | Special seats |
OX | Oxygen |
PT | Animal in cabin |
RC | Refund fee |
RE | Family refund fee |
RF | Refund fee |
SP | Sports equipment fee |
SU | Sulamerica insurance |
UP | Cabin upgrade |
XB | Excess luggage |
XC | Cancellation fee |
Fees are imported with Item Type (G6I_TIPOIT) type "4" (Reissue). Based on table G6K,
a FROM/TO of GOL Fees is executed for the internal code fees registered in table G3A. This fee code
is stored in field G6I_CODTAX.
The refund blocks start inside a block with domestic sales and/or international sales, as shown in the example below:
Refunds
A8I9WY;2408052045;22/10/2014;0,00;0,00;0,00;0,00;0,00;0,00;0,00;0,00;AX 376************
DP;;;;;-24,02;;;;;;;;;
DFKQMG;2135195565;31/10/2014;0,00;-1175,80;-38,52;0,00;0,00;0,00;0,00;0,00;CA 5314************
OCPenalty;;;;;467,90;;;;;;;;;
XC;;;;;240,00;;;;;;;;;
EEQ8QJ;2134625747;24/10/2014;0,00;-1280,90;-21,57;0,00;0,00;0,00;0,00;0,00;CA 5314************
OCPenalty;;;;;116,09;;;;;;;;;
XC;;;;;120,00;;;;;;;;;
GYQ6KV;2134673065;25/10/2014;0,00;-1201,90;-21,57;0,00;0,00;0,00;0,00;0,00;CA 5314************
OCPenalty;;;;;540,95;;;;;;;;;
XC;;;;;120,00;;;;;;;;;
Within this structure, the columns presented contain the following ABA data:
Thus, in the first 10 rows we have the ABA "header" data and, from the 11th row onwards, the items data of this ABA, its fees, refunds and fines. Such data feed the ABA tables, allowing the reconciliation routine to process the data received versus the transactions made in the system.
The file records feed entities "ABA" and "ABA Items".
When generating the ABA from the GOL layout files, you must generate the ABA number with the IATA code catenation sent in ID GOL005B plus the sequential number generated and controlled by the backoffice routine. Example:
- IATA Code: 57518016
- Number generated: 000001
- ABA Number: 8016000001 (8016 + 000001)
The BSP IATA layout is structured in blocks, the rows of which contain the generated ABA data restricted to a fixed size, with no use of separator. What differentiates the regular layout from the simplified layout is the presence of all or of only some record types in the file. Every BSP IATA file may contain the following structure, as exemplified below:
Header Record
The file header is defined in the following structure:
ID | Field | Start | Size | Type | Description |
HDR001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
HDR002 | Record type | 7 | 1 | Numeric | Always 0 |
HDR003 | Month of sale | 8 | 2 | Numeric | Month and year of sales |
HDR004 | Year of sale | 10 | 2 | Numeric | |
HDR005 | Period from | 12 | 7 | Numeric | Range of period noted as YYYYMMP |
HDR006 | Period to | 19 | 7 | Numeric | |
HDR007 | Reserved space | 26 | 135 | Alphanumeric | Always blank |
HDR008 | Reserved space | 161 | 46 | Alphanumeric | Always blank |
Transaction Record
The file transaction record is defined in the following structure:
ID | Field | Start | Size | Type | Description |
TRR001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
TRR002 | Record type | 7 | 1 | Numeric | Always 1 |
TRR003 | Code of agent | 8 | 8 | Numeric | IATA agent code with verification digit |
TRR004 | Code of airline | 16 | 4 | Alphanumeric | IATA airline code with verification digit |
TRR005 | Code of transaction | 20 | 1 | Numeric | Transaction type, one of: 0 Canceled document 1 Mixed sale (MCO, MPD, ARV, etc.) 2 Ticket sale 3 Refund 4 ADM 5 ACM 6 TASF 7 VMPD 9 BSP Brazil only, regulation CCGR ADM of type “47” |
TRR006 | Document number | 21 | 11 | Numeric | Document number with verification digit, without airline code |
TRR007 | Blank vouchers | 32 | 4 | Alphanumeric | List of segment identifiers of blank vouchers and of surface. For example: “34 “ indicates vouchers numbered 3 and 4 are not flown |
TRR008 | Date of issue | 36 | 6 | Numeric | Date of transaction issue in format DDMMYY |
TRR009 | Currency | 42 | 4 | Alphanumeric | Transaction currency in format CUTP |
TRR010 | Collection of funds | 46 | 9 | Numeric | Gross tariff paid cash and credit (excepting fees) |
TRR011 | Creditor balance | 55 | 9 | Numeric | |
TRR012 | Fees total | 64 | 9 | Numeric | Sum total of fees (excepting fines) |
TRR013 | Cancellation fine | 73 | 9 | Numeric | Total cancellation fines (only refund) |
TRR014 | Commission fee | 82 | 2.2 | Numeric | By default, the actual commission fee and the totals; however, in BSP Brazil and in countries with generation of net ACM shipments, the default commission fee and quantity are added |
TRR015 | Taxable commission | 86 | 9 | Numeric | |
TRR016 | Non-taxable commission | 95 | 9 | Numeric | BSP Brazil only, cash and credit discount total. Filled out with zeros for other BSPs |
TRR017 | Commission in cancellation fine | 104 | 9 | Numeric | Commission in cancellation fine |
TRR018 | Commission taxes | 113 | 9 | Numeric | Taxes in commission total |
TRR019 | Balance payable | 122 | 9 | Numeric | Net payable to airline |
TRR020 | Supplemental commission | 131 | 9 | Numeric | Supplemental commission |
TRR021 | Account number | 140 | 15 | Alphanumeric | Number of agent bank account |
TRR022 | Traffic type | 155 | 1 | Alphanumeric | Always blank, unless environment variable LIS2040_CON_ID has been exported, in which case the traffic type field may display: “I” – International “D” – Domestic |
TRR023 | Reserved space | 156 | 4 | Alphanumeric | Always blank |
TRR024 | Down payment of balance payable | 160 | 1 | Alphanumeric | Down payment of balance payable, which can be: “+” – Sum owed to airline “-“ – Owed to agent |
TRR025 | Code of tour | 161 | 15 | Alphanumeric | Code of tour, only BSP Brazil. Sent blank to other BSPs |
TRR026 | Fee of service agent | 175 | 9 | Numeric | Fee of service agent and fee of merchant / sum of discount (BSP Brazil only) |
TRR027 | Merchant fee | 185 | 9 | Numeric | |
TRR028 | PNRR | 194 | 13 | Alphanumeric | PNRR (Passenger Name Record Reference) / BSP Brazil only |
Credit Form of Payment Record
The credit record of payment method is defined in the following structure:
ID | Field | Start | Size | Type | Description |
CPR001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
CPR002 | Record type | 7 | 1 | Numeric | Always 2 |
CPR003 | FPAC 1 | 8 | 20 | Alphanumeric | Number of credit card account (FPAC) of the first seven credit card payment methods |
CPR004 | FPAC 2 | 28 | 20 | Alphanumeric | |
CPR005 | FPAC 3 | 48 | 20 | Alphanumeric | |
CPR006 | FPAC 4 | 68 | 20 | Alphanumeric | |
CPR007 | FPAC 5 | 88 | 20 | Alphanumeric | |
CPR008 | FPAC 6 | 108 | 20 | Alphanumeric | |
CPR009 | FPAC 7 | 128 | 20 | Alphanumeric | |
CPR010 | Reserved space | 148 | 13 | Alphanumeric | Always blank |
CPR011 | Reserved space | 161 | 46 | Alphanumeric | Always blank |
Related Document Record
The credit record of payment method is defined in the following structure:
ID | Field | Start | Size | Type | Description |
RDR001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
RDR002 | Record type | 7 | 1 | Numeric | Always 3 |
RDR003 | Code of airline | 8 | 3 | Alphanumeric | Code of airline without the verification digit of correlated ticket |
RDR004 | Document number | 11 | 10 | Numeric | Number of correlated document without verification digit |
RDR005 | Vouchers | 21 | 4 | Alphanumeric | Correlated vouchers |
RDR006 | Code of airline | 25 | 3 | Alphanumeric | Second correlated document |
RDR007 | Document number | 28 | 10 | Numeric | |
RDR008 | Vouchers | 38 | 4 | Alphanumeric | |
RDR009 | Code of airline | 42 | 3 | Alphanumeric | Third correlated document |
RDR010 | Document number | 45 | 10 | Numeric | |
RDR011 | Vouchers | 55 | 4 | Alphanumeric | |
RDR012 | Code of airline | 59 | 3 | Alphanumeric | Fourth correlated document |
RDR013 | Document number | 62 | 10 | Numeric | |
RDR014 | Vouchers | 72 | 4 | Alphanumeric | |
RDR014 | Code of airline | 76 | 3 | Alphanumeric | Fifth correlated document |
RDR016 | Document number | 79 | 10 | Numeric | |
RDR017 | Vouchers | 89 | 4 | Alphanumeric | |
RDR018 | Code of airline | 93 | 3 | Alphanumeric | Sixth correlated document |
RDR019 | Document number | 96 | 10 | Numeric | |
RDR020 | Vouchers | 106 | 4 | Alphanumeric | |
RDR021 | Code of airline | 110 | 3 | Alphanumeric | Seventh correlated document |
RDR022 | Document number | 113 | 10 | Numeric | |
RDR023 | Vouchers | 123 | 4 | Alphanumeric | |
RDR024 | Code of airline | 127 | 3 | Alphanumeric | Eighth correlated document |
RDR025 | Document number | 130 | 10 | Numeric | |
RDR026 | Vouchers | 140 | 4 | Alphanumeric | |
RDR027 | Reserved space | 144 | 17 | Alphanumeric | Always blank |
RDR028 | Reserved space | 161 | 46 | Alphanumeric | Always blank |
Conjunction Document Record
The conjunction document record is defined in the following structure:
ID | Field | Start | Size | Type | Description |
CRD001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
CDR002 | Record type | 7 | 1 | Numeric | Always 4 |
CDR003 | Conjunctive ticket | 8 | 11 | Numeric | First conjunctive ticket with verification digit |
CDR004 | Blank vouchers | 19 | 4 | Alphanumeric | Unused vouchers |
CDR005 | Conjunctive ticket | 23 | 11 | Numeric | Second conjunctive ticket |
CDR006 | Blank vouchers | 34 | 4 | Alphanumeric | |
CDR007 | Conjunctive ticket | 38 | 11 | Numeric | Third conjunctive ticket |
CDR008 | Blank vouchers | 49 | 4 | Alphanumeric | |
CDR009 | Conjunctive ticket | 53 | 11 | Numeric | Fourth conjunctive ticket |
CDR010 | Blank vouchers | 64 | 4 | Alphanumeric | |
CDR011 | Conjunctive ticket | 68 | 11 | Numeric | Fifth conjunctive ticket |
CDR012 | Blank vouchers | 79 | 4 | Alphanumeric | |
CDR013 | Conjunctive ticket | 83 | 11 | Numeric | Sixth conjunctive ticket |
CDR014 | Blank vouchers | 94 | 4 | Alphanumeric | |
CDR015 | Conjunctive ticket | 98 | 11 | Numeric | Seventh conjunctive ticket |
CDR016 | Blank vouchers | 109 | 4 | Alphanumeric | |
CDR017 | Conjunctive ticket | 113 | 11 | Numeric | Eighth conjunctive ticket |
CDR018 | Blank vouchers | 124 | 4 | Alphanumeric | |
CDR019 | Reserved space | 128 | 33 | Alphanumeric | Always blank |
CDR020 | Reserved space | 161 | 46 | Alphanumeric | Always blank |
Trailer Record
The file trailer is defined in the following structure:
ID | Field | Start | Size | Type | Description |
TRL001 | Sequential number | 1 | 6 | Numeric | Self increasing sequential number starting at 1 and increased for each record of file |
TRL002 | Record type | 7 | 1 | Numeric | Always 9 |
TRL003 | Reserved space | 8 | 153 | Alphanumeric | Always blank |
TRL004 | Reserved space | 161 | 46 | Alphanumeric | Always blank |
The register is developed in header format (ABA) and tabs, each tab with its respective functionality. Namely:
Attributes
(*) – Fields required
(**) – Key fields of table
ABA Items (validate the items along the integration process)
Name | Description | Example |
Branch (**) | Code of system branch | 01 – Head Office |
ABA Code (**) | Sequential code of ABA table | 000002 |
Item (**) | Sequential code of imported item | 000001 |
File | Imported file name | 231014GOL3563575.TXT |
Item Type | Type of Item. Options: 1 – TKTA (regular sale) 2 – ADM (fine) 3 – RFND (refund) * a FROM/TO in Alatur identifies these types * you must evaluate it through the integration process (Pedro) | TKTA |
Row No. | Number of row in file | 15 |
Airline No. | Number of airline | JJ |
Ticket Sr. | Serial number of ticket/document | 55258 |
Ticket No. | Number of ticket/document | 8327001350 |
Ticket dig. | Verification digit of ticket | 24 |
Locator | Number of locator for electronic ticket |
|
Issue Dt. | Date of ticket/document issue | 28/11/2014 |
Currency Cd. | Code of currency in which the sale was made | BRL |
Tariff Vl. | Value of tariff sold | 280.22 |
Fees Vl. | Total value of fees | 56.39 |
DU Fee | Value of DU Fee | 0.00 |
Commission % | Commission percentage | 10 |
Commission Vl. | Value of commission | 28.02 |
Incentive Vl. | Value of fixed incentive | 0.00 |
Refund F.Vl. | Value of fine in case of refund | 0.00 |
Net Vl. | Net value to be paid to or received from provider | 308.59 |
Operation Tp. | Type of ABA option. Options: 1 – Debit 2 – Credit | Debit |
Tour Code | Number of Tour Code used in sale |
|
Divergent | Defines whether the item has any divergence. Options: 1 – Divergent 2 – Not Divergent | No |
Diverg. Note | Note on divergence found when associating the item (evaluate whether you need a list, a register or free completion at development) |
|
Adjustment Generated? | Enter whether an adjustment has been generated after the item divergence was identified. Options: 1 – Yes 2 – No If no adjustment has been generated, the item cannot be approved. |
|
Status | The status of the item during reconciliation. Options: 1 – Not Associated 2 – Associated 3 – Approved | Not Associated |
Reconciliation Cd. | Code of reconciliation process with which the item is correlated | 000001 |
DR Cd. | Code of Reservation Document to which it is associated |
|
Considerations:
Data Dictionary
TABLE G6H – ABAs' Headers
Index | Key |
01 | G6H_FILIAL + G6H_FATURA + G6H_EMISSA +G6H_FORNEC + G6H_LOJA |
02 | G6H_FILIAL + G6H_ FATFOR |
03 | G6H_FILIAL+DTOS(G6H_EMISSA)+G6H_FORNEC+G6H_LOJA |
04 | G6H_FILIAL + DTOS(G6H_VENCTO) )+G6H_FORNEC+G6H_LOJA |
Table | Description |
Acronym | G6H |
Name | ABAs' Header |
Branch Ac. Mod. | Shared |
Unit Ac. Mod. | Shared |
Company Ac. Mod. | Exclusive |
Single Key | G6H_FILIAL + G6H_FATURA + G6H_EMISSA +G6H_FORNEC + G6H_LOJA |
Display | G6H_FILIAL + G6H_FATURA + G6H_EMISSA +G6H_FORNEC + G6H_LOJA |
Field | G6H_FILIAL |
Type | C |
Size | 8 |
Picture | @! |
Context | Real |
Property | View |
Description | Branch of System |
Bill | Branch |
Field Help | Branch of System |
System Vl. | 0 |
Default Init. | 0 |
Required | Yes |
Used | Yes |
Browser | No |
Modules | All |
|
|
Field | G6H_FATURA |
Type | C |
Size | 8 |
Picture | @! |
Context | Real |
Property | View |
Description | ABA Code |
Bill | ABA |
Field Help | ABA Code |
Validation | NotBlank() |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
Default Initializer | GetSXENum("G6H","G6H_FATURA") |
|
|
Field | G6H_TIPO |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Import Type |
Bill | Type |
Field Help | Import Type 1=Directory. 2=File. 3=Physical |
SXB Cons. | 1=Directory. 2=File. 3=Physical |
System Vl. | Belongs("123") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_LAYOUT |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Layout |
Bill | Layout |
Field Help | ABA Layout 1=BSP Simplified. 2=Airline Manual. 3=Airline Locator. 4=Others |
SXB Cons. | 1=BSP Simplified. 2=Airline Manual. 3=Airline Locator. 4=Others |
System Vl. | Belongs("1234") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_MES |
Type | C |
Size | 2 |
Picture | 99 |
Context | Real |
Property | Edit |
Description | Reference Month |
Bill | Month |
Field Help | Reference Month Enter a month between 01 and 12 |
System Vl. | Val(M->GH6_MES) >= 1 .and. Val(M->GH6_MES) <= 12 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_ANO |
Type | C |
Size | 4 |
Picture | 9999 |
Context | Real |
Property | Edit |
Description | Reference Year |
Bill | Year |
Field Help | Reference Year. |
Options | 0 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_PERCID |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Periodicity |
Bill | Periodicity |
Field Help | ABA Periodicity. 1=Weekly.2=Ten Day Period.3=Fortnightly.4=Monthly;5=Twenty Day Period |
Options | 1=Weekly.2=Ten Day Period.3=Fortnightly.4=Monthly;5=Twenty Day Period |
Validation | Belongs("12345") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_PERIOD |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | ABA Period |
Bill | Period |
Field Help | Enter the period within the periodicity, considering Weekly from 1 to 4, Ten Day Period from 1 to 3, Fortnightly from 1 to 2, Monthly just 1, Twenty Day Period from 1 to 2. |
Options | 1=1;2=2;3=3;4=4 |
Validation | TURA038Per() |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_FATFOR |
Type | C |
Size | 20 |
Picture | @! |
Context | Real |
Property | Edit |
Description | ABA at Provider |
Bill | ABA Prov |
Field Help | Code of ABA in Provider |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_EMISSA |
Type | D |
Size | 8 |
Context | Real |
Property | Edit |
Description | ABA Issue |
Bill | Issue |
Field Help | ABA issue date |
Validation | 0 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_VENCTO |
Type | D |
Size | 8 |
Context | Real |
Property | Edit |
Description | ABA Due Date |
Bill | Due Date |
Field Help | ABA Due Date |
Validation | 0 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_VALOR |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | ABA Value |
Bill | Value |
Field Help | ABA Value |
Options | 0 |
Validation | Positive() |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_FORNEC |
Type | C |
Size | 0 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Provider Code |
Bill | Provider |
Field Help | Code of ABA Provider |
Validation | ExistCpo("SA2") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_LOJA |
Type | C |
Size | 0 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Store |
Bill | Store |
Field Help | Store of ABA Provider |
Validation | TURA038Loj() |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_NREDUZ |
Type | C |
Size | 0 |
Picture | @! |
Context | Virtual |
Property | Edit |
Description | Provider Corporate Name |
Bill | Corporate Name |
Field Help | Provider Corporate Name |
Validation | 0 |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_REPORT |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Report Provider |
Bill | Report |
Field Help | Report Provider 1=Yes. 2=No. |
Options | 1=Yes.2=No |
Validation | Belongs("12") |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_EFETIV |
Type | C |
Size | 0 |
Picture | @! |
Context | Real |
Property | Edit |
Description | ABA in Effect |
Bill | In Effect |
Field Help | ABA in Effect |
Options | 1=Reconciled.2=Not Reconciled |
Validation | Belongs("12") |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6H_DTIMP |
Type | D |
Size | 8 |
Context | Real |
Property | View |
Description | Import Date |
Bill | Import Date |
Field Help | Date of ABA Import |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
TABLE G6I – ABA Items
Index | Key |
01 | G6I_FILIAL + G6I_FATURA + G6I_ITEM |
02 | G6I_FILIAL + DTOS(G6I_EMISSA) |
03 | G6I_FILIAL + G6I_NUMCIA + DTOS(G6I_EMISSA) |
04 | G6I_FILIAL + G6I_BILHET + G6I_SRBILH + G6I_DGBILH |
05 | G6I_FILIAL + G6I_LOCALI |
06 | G6I_FILIAL + G6I_TOURCD |
07 | G6I_FILIAL + G6I_CONCIL |
08 | G6I_FILIAL + G6I_DOCRES |
Table | Description |
Acronym | G6I |
Name | ABAs' Items |
Branch Ac. Mod. | Shared |
Unit Ac. Mod. | Shared |
Company Ac. Mod. | Exclusive |
Single Key | G6I_FILIAL + G6I_FATURA + G6I_ITEM |
Display | G6I_FILIAL + G6I_FATURA + G6I_ITEM |
Field | G6I_FILIAL |
Type | C |
Size | 8 |
Picture | @! |
Context | Real |
Property | View |
Description | Branch of System |
Bill | Branch |
Field Help | Branch of System |
System Vl. | 0 |
Default Init. | 0 |
Required | Yes |
Used | Yes |
Browser | No |
Modules | All |
|
|
Field | G6I_FATURA |
Type | C |
Size | 8 |
Picture | @! |
Context | Real |
Property | View |
Description | ABA Code |
Bill | ABA |
Field Help | ABA Code |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_ITEM |
Type | C |
Size | 4 |
Picture | @! |
Context | Real |
Property | View |
Description | ABA Item |
Bill | Item |
Field Help | ABA Item |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TIPOIT |
Type | C |
Size | 1 |
Picture | 99 |
Context | Real |
Property | Edit |
Description | Type of Item |
Bill | Type of Item |
Field Help | Type of Item. Options: 1=TKTA (regular sale);2=ADM (fine);3=RFND (refund) |
SXB Cons. | 1=TKTA (regular sale);2=ADM (fine);3=RFND (refund) |
System Vl. | Belongs("123") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_NUMLIN |
Type | C |
Size | 6 |
Picture | 9999 |
Context | Real |
Property | Edit |
Description | File Row No. |
Bill | Row Number |
Field Help | Number of Row |
Options | 0 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_NUMCIA |
Type | C |
Size | 2 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Number of Airline |
Bill | Airline No. |
Field Help | Abbreviated Airline Number |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_SRBILH |
Type | C |
Size | 6 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Ticket Serial |
Bill | Ticket Ser. |
Field Help | Ticket Serial |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_BILHET |
Type | C |
Size | 20 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Ticket Number |
Bill | Ticket No. |
Field Help | Ticket Number |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_DGBILH |
Type | C |
Size | 2 |
Context | Real |
Property | Edit |
Description | Ticket Digit |
Bill | Ticket Dig. |
Field Help | Ticket Digit |
Validation | 0 |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_LOCALI |
Type | C |
Size | 6 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Locator |
Bill | Locator |
Field Help | Locator |
Validation | 0 |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_EMISSA |
Type | D |
Size | 8 |
Context | Real |
Property | Edit |
Description | ABA issue date |
Bill | Issue |
Field Help | ABA issue date |
Options | 0 |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_MOEDA |
Type | C |
Size | 3 |
Picture | @! |
Context | Real |
Property | Edit |
Description | ABA Currency |
Bill | Currency |
Field Help | ABA Currency |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TARIFA |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Tariff |
Bill | Tariff |
Field Help | Tariff |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TAXAS |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Fees |
Bill | Fees |
Field Help | Fees |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TAXADU |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | DU Fee |
Bill | DU Fee |
Field Help | DU Fee |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_PERCOM |
Type | N |
Size | 3.9 |
Picture | @E999.999999999 |
Context | Real |
Property | Edit |
Description | Commission Percentage |
Bill | Commission % |
Field Help | Commission Percentage |
Validation | Empty() .or. Positive() |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_VLRCOM |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Value of Commission |
Bill | Commission |
Field Help | Value of Commission |
Validation | Empty() .or. Positive() |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_VLRINC |
Type | N |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Value of Incentive |
Bill | Incentive |
Field Help | Value of Incentive |
Options | 0 |
Validation | Empty() .or. Positive() |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_VLRREE |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Value of Refund |
Bill | Refund |
Field Help | Value of Refund |
Options | 0 |
Validation | Empty() .or. Positive() |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_VLRLIQ |
Type | N |
Size | 12.2 |
Picture | @E999,999,999.99 |
Context | Real |
Property | Edit |
Description | Net Value |
Bill | Net Value |
Field Help | Net Value |
Options | 0 |
Validation | Empty() .or. Positive() |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TPOPER |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Type of ABA Operation |
Bill | Operation Tp |
Field Help | Type of ABA Operation 1=Debit.2=Credit. |
Options | 1=Debit.2=Credit. |
Validation | Belongs("12") |
Required | Yes |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_TOURCD |
Type | C |
Size | 20 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Tour Code |
Bill | Tour Code |
Field Help | Tour Code |
Options | 0 |
Validation | 0 |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_DIVERG |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Enter whether you have found Divergences |
Bill | Divergence |
Field Help | Enter whether you have found Divergences 1=Yes.2=No. |
Options | 1=Yes.2=No |
Validation | Belongs("12") |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_CODDIV |
Type | C |
Size | 250 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Stores the codes of Divergences found |
Bill | Diverg Cd. |
Field Help | Stores the codes of Divergences found |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_ACERTO |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Enter whether an Adjustment was generated |
Bill | Adjustment |
Field Help | Enter whether an Adjustment was generated 1=Yes.2=No. |
Options | 1=Yes.2=No |
Validation | Belongs("12") |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_SITUAC |
Type | C |
Size | 1 |
Picture | @! |
Context | Real |
Property | Edit |
Description | The status of the item during reconciliation. |
Bill | Status |
Field Help | The status of the item during reconciliation. Options: 1=Non-associated;2=Associated;3=Approved |
Options | 1=Non-associated;2=Associated;3=Approved |
Validation | Belongs("123") |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_CONCIL |
Type | C |
Size | 6 |
Picture | @! |
Context | Real |
Property | Edit |
Description | Code of reconciliation process |
Bill | Reconciliation |
Field Help | Code of reconciliation process with which the item is correlated |
Options | 0 |
Validation | 0 |
Required | No |
Used | Yes |
Browser | Yes |
Modules | All |
|
|
Field | G6I_CODTAX |
Type | C |
Size | 6 |
Picture | @! |
Context | Real |
Property | View |
Description | Code of Fee |
Bill | Fee Code |
Field Help | Code of Fee applied to ticket. |
Validation | ExistCpo("G3A") |
Required | No |
Used | Yes |
Browser | No |
Modules | All |
Field | G6I_NUMID |
Type | C |
Size | 10 |
Picture | @! |
Context | Real |
Property | View |
Description | Sales Rec. Code |
Bill | SR Cd. |
Field Help | Single identification number of Sales Record |
Required | No |
Used | Yes |
Browser | No |
Modules | All |
Field | G6I_IDITEM |
Type | C |
Size | 4 |
Picture | @! |
Context | Real |
Property | View |
Description | Sales Item Cd. |
Bill | SI Cd. |
Field Help | Sequential number of Sales Item of Sales Record. |
Required | No |
Used | Yes |
Browser | No |
Modules | All |
Field | G6I_NUMSEQ |
Type | C |
Size | 2 |
Picture | @! |
Context | Real |
Property | View |
Description | Sales Item Seq. |
Bill | SL Seq. |
Field Help | Identification sequence of Sales Item, used to gather related Sales Items. |
Required | No |
Used | Yes |
Browser | No |
Modules | All |
Screen Prototypes
Provider ABA - Browser
Attributes of parameter setting interface for Import
Provider ABA - Header
Provider ABA - Tab: Tickets / Documents - Layout: Simplified BSP
Provider ABA - Tickets / Documents - Layout: Airline Locator
Integrity Rules
Premises
Release Notes
Module | Tourism |
Function | TURA038() |
Description of Function | Now you can register and import the ABAs of airline providers to allow the definition of the rule negotiated with the entities. |
Process Flow
Entity and Relationship
Test Cases
A test case contains general information that determine how to conduct tests previously specified by the Tests Plan. Generally, they are grouped by requisite. However, you can group test cases by set of requisites, if the tests are integrally checking the requisites that belong to this set.
You must execute the test cases mentioned below to ensure the quality of the product, meeting the purpose of the project and the expected results.
Test Cases | There are none |
Storage |
|
Procedures/Test Scenarios |
|
Estimates |
|
Tests Purpose |
|
Recommendations |
|
Product integrations |
|
Test Cases | Register an Airline Provider ABA |
Tests Purpose | Registration of an Airline Provider ABA to be used by SIGATUR module routines |
Estimates | 5 min |
Programmer Test | ( X ) Yes ( ) No |
Recommendations |
|
Preconditions |
|
Post-conditions |
|
How to check the results | Updates -> Provider Reconciliation -> Agent Billing Analysis |
Procedures | Expected Results |
Register an Additional Entity |
|
Test Cases | Import an Airline Provider ABA |
Tests Purpose | Import of an Airline Provider ABA to be used by SIGATUR module routines |
Estimates | 5 min |
Programmer Test | ( X ) Yes ( ) No |
Recommendations |
|
Preconditions |
|
Post-conditions |
|
How to check the results | Updates -> Provider Reconciliation -> Agent Billing Analysis |
Procedures | Expected Results |
Register an Additional Entity |
|
This document is an innovation requisite specification material, of extremely technical content. |