Escolar Documentos
Profissional Documentos
Cultura Documentos
Outgoing Processing
The term outgoing refers to interchange sent from the members processing center to the VIC. See Figure 11. Pre-Edit Processing The first part of the outgoing process is performed by software belonging to the processing center. This is usually referred to as pre-edit processing, since it is done prior to processing by the Edit Package. Pre-edit processing involves the capture, editing, and formatting of interchange data. Transactions submitted into interchange are processed through the processing centers pre-edit software, which places this information into a Center Transaction File (CTF). Once pre-editing is completed, the data is ready to be run through the Edit Package.
Figure 11: Outgoing Interchange
Edit Package Processing E3OUT, the overall outgoing control program, calls initialization processes at the beginning of each outgoing Edit Package run and then processes each transaction found in the CTF. At the end of processing, the control program produces the necessary reports. Then the Edit Package produces an Interchange Transaction File (ITF) which is transferred to a VAP, where it is held until a predetermined collection time. The transmission of the file is jointly managed by the VAP and the VIC, with little or no intervention required by center personnel. If a VAP or other electronic transmission means is unavailable, the file must be mailed to the VIC. BASE II System Processing At a predetermined time, the BASE II System at the VIC dials the VAP and collects the interchange. As the interchange transactions are received by BASE II at the VIC, clearing occurs. The transactions are validated, converted to the appropriate currencies, and totaled and sorted by destination. Fees are then calculated. At the end of each BASE II cycle, settlement positions are computed for all members with either incoming or outgoing transactions. Interchange data are protected from system failure after being accepted by the VIC. In the event of a failure, the BASE II System can restart processing where the failure occurred. If requested, interchange files can also be rebuilt and electronically transmitted to the processing center.
Incoming Processing
The term incoming refers to interchange coming into the members processing center from the VIC. See Figure 12. The overall incoming control program E3IN calls an initialization process at the beginning of each incoming Edit Package run and then processes each transaction found in the ITF. At the end of processing, the control program produces the necessary reports and makes the CTF available for use by the processing center if there are no severe errors in the interchange file.
Incoming Edit Package files contain: Financial and nonfinancial interchange transactions Settlement totals BASE II System settlement reports Edit Package table update transactions NOTE: To ensure proper application of table update transactions, all incoming files must be processed. Files must be processed in sequence by the Central Processing Date (CPD) on which they were created to properly update the table files.
Post-Edit Processing Post-edit software, written by center personnel or by an outside vendor, reformats and processes incoming interchange received from the VIC. This software prepares interchange so that it can be processed by cardholder and merchant posting programs and used for other processing center purposes, such as fraud analysis.
interchange. This reduces the need to install new Edit Package software whenever changes are introduced.
Input Requirements
The following items are required before an outgoing Edit Package run can be executed: An outgoing CTF generated by the processing centers pre-edit program The following files, which must reside on a direct access storage device: Permanent and Temporary Run Control Options Files Incoming Run Hold File Account Range Definition (ARDEF) File BIN File Language File Rules File History File (indexed and backup) Log File (indexed and backup) Merged Table File Table Control File BIN and ARDEF Top Gun History Files (may be initially empty)
Table Key (TBLKEY) Table Data (TBLDATA) NOTE: TABLEDATE, RUNDATE, RUNMODE, TBLKEY, and TBLDATA run control options are not required. If not present in either run control options file, default values are used. Load Internal Tables Next, E3OUT uses the information from the above run control options to load the following files into internal tables: ARDEF File BIN File NOTE: Information from the BIN and ARDEF Top Gun History files determine the Processing Centers most frequently referenced BINs and ARDEFs. and ensure they are loaded into computer memory. Language File Rules File E3OUT loads the tables with values needed for the transaction validation process. If specified, E3OUT calls optional extended service modules to calculate cutoff dates required to perform timeliness edits for incentive scheme processing.
Validate Run Control Options Once the files and tables are loaded, E3OUT validates all run control options, and: 1. Sets default values for run control options, where necessary 2. Performs cross-validation of run control options to ensure that there are no conflicting options in the run 3. Stores the run control options in effect for the run in internal tables 4. Writes the run control options in effect for the run to the Log File Assign Run and Starting Batch Numbers After validating the run control options, E3OUT references the History File to assign run and starting batch numbers. Batch numbers start at 1 for each processing day and are incremented by 1 for each batch processed. RerunsIf the current outgoing Edit Package run is a rerun, E3OUT verifies that it has already performed the run for the run date in effect and reuses the starting batch number in effect for the original run.
Component Record (TCR) at a time from the outgoing CTF, validates the sequence number, and groups the TCRs together to build each logical transaction. Validate Transactions E3OUT passes the TCRs for each logical transaction to the table manipulation submodule that validates the transaction code. Based on the transaction code, the table manipulation submodule uses the appropriate transaction layout from the tables and performs edits against the rules and values defined in the tables. (See BASE II Clearing Interchange Formats manuals for definitions of the transaction edits.) The table manipulation submodule also passes back to E3OUT any errors and formatted information needed to generate reports.
Perform Optional Processing After validating transactions, E3OUT performs optional processing, including: Item or run tolerance checking Calculates the hash value for each record, if duplicate batch checking via hashing is selected Extract Reports Once optional processing is completed, E3OUT calls the report extract module which extracts summary and transaction-based report information and passes it to a work file. Create ITF After extracting summary and transaction-based report information, E3OUT calls the transaction write module. If a transaction was not rejected, it is written to the outgoing ITF. Rejected TransactionsIf a transaction was rejected and the processing center has selected the SAVEREJECT run control option, the transaction is written to the Rejected Item File. Hash TotalsIf the processing center uses an IBM mainframe (MVS and VSE), a 2-byte hash total field is inserted in each transaction at this time. CTF Trailers E3OUT verifies that all batch and file trailers balance, that is, totals read from the records in the CTF equal the sums of accepted and rejected totals accumulated by E3OUT during processing. If duplicate batch detection has been selected using the DUPBATCH option, E3OUT will also compare the batch hash value or Center Batch ID against the history file values. ITF Trailers The Edit Package writes a batch trailer to the ITF every time a batch trailer is encountered in the CTF. File trailers are written to the ITF at the end of CTF processing. If more than one CTF is processed, the Edit Package will combine the CTFs on the ITF. If ITF files are being written to tape or diskette, the Edit Package will also write a file trailer whenever the tape or diskette is full. A file header record for the next tape or diskette is then written to the ITF.
Generate TC 50 Text Transactions Before loading tables for reporting, the Edit Package generates a batch in the
ITF that contains TC 50 text transactions. These transactions contain: Edit Package incoming and outgoing environmental information, such as date of run and version and date of tables used during the run. Information showing the version number of the Edit Package software being used and the level of TIUs applied. There is one TC 50 for each record in the Permanent and Temporary Run Control Options Files. There also is an environmental record and a record for each run control option used during the previous incoming Edit Package run.
end of the outgoing run, whatever data was accumulated in the Log File during the run is written to the EP199 Log Report.
Exception Conditions
The several types of exception conditions are as follows: Severe Errors If a severe error is detected during the outgoing Edit Package run: The appropriate severe error message appears in the Validation Exception Detail Report (EP100A) and the Log File Report (EP199) An ITF is not created Processing of the Edit Package continues to the end of the run, if possible. If the Reject Message Limit (REJMSGLIM) run control option is specified, processing stops when the percentage of the transactions processed so far exceed the percentage specified for the REJMSGLIM option. If the Reject ITF Limit (REJITFLIM) run control option is specified, error reporting continues until all transaction in the input file are processed, but the ITF is not created if the percentage of transactions containing errors for the entire input file, exceeds the percentage specified on the REJITFLIM option. CTF Errors If any errors are detected during the processing of the CTF, the transactions with errors are written to the Validation Exception Detail Report (EP100A) and are not passed to the ITF. If the SAVEREJECT run control option is selected, the transactions in error are written to a separate CTF. Messages After each outgoing Edit Package run, the banner page on the EP100A Validation Exception Detail Report displays a message indicating the status of the run.
The indexed ARDEF File is a permanent file containing a valid ARDEF Table. The ARDEF Table contains all valid ARDEF entries, including the account prefix range, its associated BIN, card-number length indicator, check-digit indicator, and card type. The ARDEF File is used to validate account numbers used in transactions processed for interchange. BIN File The indexed BIN File is a permanent file containing a valid BIN Table. A BIN is a six-digit system number used by Visa to identify processing centers and members. The BIN Table contains all valid BINs and their BASE II processing status codes. The BIN File is used to validate BINs used in transactions processed for interchange. Language File The indexed Language File includes the text of: Validation error messages Log messages Report headings Report literals Reason code descriptions Returned item code descriptions Rules File The indexed Rules File contains transaction layouts and business validation logic. The transaction layouts and business validation logic are used to edit and report interchange transactions. Table Control File This file indicates which version of the merged sequential files is current. During outgoing runs, this file controls the table recovery process, if the indexed table files become unusable. Merged Table Files These files contain all the data from ARDEF, BIN, Language, and Rules Files in a sequential format. During the outgoing run, the merged table files are used to recover the contents of the indexed files when the indexed files are not usable. There are four merged files, one for each image and copy of the tables.
This file collects BIN and ARDEF reference statistics for the current outgoing run, and is used to update the Top Gun History files at the end of the run.
History File
The indexed History File contains a history of batches, files, and runs for outgoing and incoming Edit Package processing.
Log File
The indexed Log File contains messages recorded during Edit Package processing. The messages include run control and environmental information, as well as any unusual conditions warranting review.
Backup Files
The types of backup files are as follows: Log Backup File The Log Backup File is a sequential copy of the indexed Log File used to restore the indexed Log File if it becomes unusable. The Log Backup File is also used to reorganize the indexed Log File on a monthly basis. History Backup File The History Backup File is a sequential copy of the indexed History File used to restore the indexed History File if it becomes unusable. The indexed
History File is copied into this file after every successful run of the Edit Package. The History Backup File is also used to reorganize the indexed History File on a monthly basis.
Report Files
Each outgoing Edit Package report is written to a separate file. If data for a particular report was not received, the file will contain a report header and a message indicating that there is not any data to report.
that creates outgoing CTFs destined for outgoing interchange. Duplicate file detection is based on two data elements in the TC 90 header record: Center Processing DateThis is the processing date of the members pre-edit system. File IDThis is a three-digit number that must be unique for each CTF processed by the Edit Package for any given Center Processing Date. File IDs do not need to be in an ascending sequence. The outgoing Edit Package compares the combination of Center Processing Date and File ID against the Edit Package History File. If a match is found, the Edit Package run is immediately terminated. Processing centers can produce a TC 90 header record and avoid duplicate detection by applying a value of zero in the File ID field. NOTE: If multiple pre-edit systems create outgoing CTFs destined for outgoing interchange, Visa recommends that a pre-defined range be allocated to each pre-edit system to ensure uniqueness of File IDs and to avoid potential conflict.
Numbering Convention Edit Package reports are identified by the prefix EP, an en dash (), and a three-digit number that conforms to the following numbering scheme: Report Type Report Outgoing Reports Incoming Reports On-Request Reports Optional Transaction-Based Reports Index of Reports Number Series 100199 200299 300399 700799 999
For example, the report ID for the incoming Interchange Transaction File Distribution report is: EP230. The following provides report extensions used by the Edit Package: Report Levels Transaction Detail Batch or BIN File or Center Central Processing Date (CPD) Run Final Summary Report Extensions A B C D E F
For example, the incoming interchange summary reports that are produced with different levels of detail are labeled EP210B at the batch level, EP210C at the file level, EP210D at the CPD level, EP210E at the run level, and EP210F at the final summary level. A separate set of alphabetic identifiers applies to Fee Collection/Funds Disbursement reports or the EP748 BASE I Advice reports. The levels for the reports are as follows: Transaction Format or Origin Combined Visa and Non-Visa-Generated Enriched Format Non-Visa-Generated Standard Format Visa-Generated Report Extensions C E N S V
(EXCPRPTFMT=DUMP), which does not include field names. The second sample, which includes field names, is selected by using EXCPRPTFMT=FORMAT.
Report EP110B totals draft financial transaction types within a batch as drafts, vouchers, or cash disbursements. Totals for other transactions, including Fee Collections (TC 10) and Funds Disbursements (TC 20), are listed under TOTAL columns only. The report includes both accepted and rejected transactions. There is a breakdown for each currency type. If currency types are mixed, the report includes a warning that there is more than one currency or settlement type.
Description The report is produced at two different summary levels: file (EP111C) and run (EP111E). Both levels of reporting are in the same basic format. There is a separate page for each currency and settlement flag. Accepted, rejected, and total transactions are summarized.
Separate pages are produced for each specific currency and settlement combination present in outgoing interchange. EP111C is always produced. If there are no multiple currencies or settlement types, the information in report EP111 will be the same as the financial transaction information in report EP110. Separate EP111C report summary totals are produced for the following settlement types: 0 International Settlement Service. BASE II selects the appropriate settlement service based on routing and country default. 3 Clearing Only Service. This settlement type may be used only if the members country has registered with Visa for this type of service for domestic interchange. 6 National Bilateral Interchange. Settlement is in the currency of the country in which the transactions took place. 8 National Net Interchange. Settlement is in the currency of the country in which the transactions took place. 9 Settlement to be determined by Visa. Settlement is in the currency established by Visa at the request of a processing center.
Purpose Reports all system activity during outgoing runs. Description This report lists all messages generated by the system, including selected options (permanent and temporary overrides) and system status. Messages have five levels of severity: A Abnormal termination (highest severity). A system error caused processing to stop abruptly. E Severe error. A serious error caused an abnormal termination of the control program. I Informational only. R Reply requested. The message is a cue to the operator to manually intervene. W Warning or precautionary. The message requires attention after the Edit Package run. The information on this report applies to one outgoing run of the Edit Package and is retained in the Edit Package log file.
Input Requirements
The following items are required before an incoming Edit Package run can be executed: An incoming ITF generated by the VisaNet Interchange Center (VIC). The following files which must reside on a direct access storage device: Permanent and Temporary Run Control Options Files Account Range Definition (ARDEF) File BIN File Language File Rules File History File (indexed and backup)
Log File (indexed and backup) Merged Table File Table Control File BIN and ARDEF Top Gun History (may be initially empty) NOTE: For processing centers that subscribe to the Currency Rate Delivery Service, the Currency Conversion Rates File is required. In addition, the processing center must have the Edit Package software itself available for execution.
counts in the trailers must equal the sum of the returned and accepted counts. The monetary transaction count and the monetary amount hash totals must equal the corresponding values for accepted transactions.
Updating/Creating Files
During processing the Edit Package will update/create the following files: Write TC 33 (Optional) Certain optional Visa services may cause the delivery of TC 33 records in the interchange file to write to a separate file. Data delivered by this mechanism include: Plus BIN tables, combined Visa/Plus routing table, Visa Transaction Routing Service tables, Interlink BIN tables, Visa Electron Routing Table, Visa check card II BIN file, MasterCard Routing, Cirrus Routing, Armed Forces Financial Network, and VisaVue Solution Series Data. The Edit Package recognizes designated TC 33 records and writes the full-length TC 33 into a separate file. A program written by the processing center may be required to separate the different types of data and extract that data in the format required for the processing center to use. For more information regarding data content and extraction, refer to documentation provided by Visa that applies to the services to which the processing center subscribes. Update Currency Conversion Rates File (Optional) If the processing center subscribes to the Currency Rate Delivery Service, this process uses TC 56 conversion rate update transactions to replace currency rate entries contained in the Currency Conversion Rates File. Update Control Tables This process uses TC 54 table update transactions to update individual entries in the BIN, ARDEF, Rules, and Language Tables. E3IN writes the TC 54s to a work file during CTF processing. After reporting is completed, the TC 54s are applied to the appropriate tables. Save Environmental Run Information E3IN writes a record with environmental information and copies permanent
and temporary run control options to the incoming Run Hold File. This data is passed to the VIC during the next outgoing Edit Package run. The Run Hold File is overlaid with data each time an incoming ITF is processed. Update History File If the run was successful, E3IN updates the History File with file and run information from the incoming Edit Package run. Update Engine Table Usage Metric File At the completion of each Edit Package run, statistics regarding the dynamic usage of the Edit Package tables are output to the Engine Table Usage Metric Files. This information may be requested by Visa to assist in support issues.
Rules File The indexed Rules File contains transaction layouts and validation logic. The transaction layouts and business validation logic are used to ensure file integrity and report interchange transactions. Table Control File This file indicates which version of the merged sequential files is current. The table control file controls the TC 54 table update merge process. This control file also controls the recovery process, if the indexed table files become unusable. Merged Table Files These files contain BIN, ARDEF, Language, and Rules file data in a sequential format. The merged table files are used when updated TC 54 table transactions are processed. TC 54 Work File TC 54 table update transactions are written to the TC 54 Work File during ITF processing. When ITF processing is complete, transactions from this file are used to update the Edit Package table files.
History File
The indexed History File contains a history of batches, files, and runs for outgoing and incoming Edit Package processing.
Log File
The indexed Log File contains messages recorded during Edit Package processing. The messages include run control and environmental information, as well as any unusual conditions warranting review.
TC 33 Extract File
The TC 33 Extract File contains data received from optional Visa services. This file consists of BASE II TC 33 transactions and includes: Plus BIN tables, combined Visa/Plus routing table, Visa Transaction Routing tables, Interlink BIN tables, Visa Electron Routing Table, Visa check card II BIN file, MasterCard Routing, Cirrus Routing, Armed Forces Financial Network, and VisaVue Solution Series data.
Backup Files
Log Backup File The Log Backup File is a sequential copy of the indexed Log File used to restore the indexed Log File, if it becomes unusable. This file is also used to reorganize the indexed Log File on a monthly basis. History Backup File The History Backup File is a sequential copy of the indexed History File used to restore the indexed History File, if it becomes unusable. The indexed History File is copied into this file after every successful run of the Edit Package. The History Backup File is also used to reorganize the indexed History File on a monthly basis.
EP200 Work File This file contains information used to produce the EP200B and EP200C summary reports. EP210 Work File This file contains information for the EP210 summary reports series. EP221 Work File This file contains information for the EP221 batch acknowledgment summary reports series. Transaction Report Sort File This file contains sorted information for use in the transaction-based reports and the EP200A Validation Exception Report. Summary Report Sort File This file contains sorted information for use in the summary reports.
Report Files
Each Edit Package report is written to a separate file. If data for a particular report was not received, then the file will contain a report header and a message indicating that there is no data to report. Microfiche Reports File (Optional) This file contains transaction-based reports, VIC settlement reports, and General Delivery Reports in a format suitable for microfiche. The Microfiche Reports File is optional. Reports can be directed to this file using the REPTFICHE run control option,
Generate reports Create either the Center Transaction File (CTF) or the Interchange Transaction File (ITF) containing valid interchange transactions
Each erroneous transaction is printed and all the fields in error are identified. An error code and a brief description are also provided. If the run contains no errors, only the banner page containing the message NO ERRORS DETECTED will be printed. An incoming CTF is not created when errors are detected on financial transactions, file headers, batch trailers, or file trailers.
This report will always print even if no returned items are received in the ITF.
EP204A: Detail
Report EP204A contains unformatted images of returned transactions, along with the return reason codes. The primary reporting sequence is by BIN. This report is formatted like the transaction-based reports and the EP206A report. This report will always print even if no returned items are received in the ITF.
(CRS).
Balancing and Reconciliation Check if total number of returned transactions match per currency on the EP206A and EP206B reports for the same BIN. EP206B items are also reported on the VSS900 (Reconciliation) series reports. Return Item Charges are listed in the VSS-140 (Visa Charges Report). All returned items on EP204C and EP206C should add up to the returned item amounts on EP210E, EP211E, and EP230. They are also reported in the VSS110 (Settlement Summary Report). Description A transaction detail report contains a formatted image of returned transactions along with the return reason codes. The VIC returns to the originator any transactions failing to conform to the Chargeback Reduction Service edit requirements. Those returned items are listed on the following set of reports: CRSReturned Item Detail (EP206A) CRSReturned Item Summary by BIN (EP206B) CRSReturned Item Summary by Center (EP206C)
This report will always print even if no returned items are received in the ITF.
EP206A: Detail
Report EP206A contains a formatted image of returned transactions along with the return reason codes. The reporting sequence is by BIN. The report has the same layout as EP204A when there are Chargeback Reduction Service returns.
This report is produced at three summary levels: File (EP211C) CPD (EP211D) Run (EP211E) All levels of reporting are in the same basic format. Each currency and settlement flag are printed on a separate page. The report shows transaction counts and transaction amounts. Each transaction type is printed on a separate line.
Confirms the collection of outgoing batches from the previous cycle, indicates any batches rejected by the VIC, and flags any discrepancies between VIC information and Edit Package history information. Balancing and Reconciliation Check if amounts reconcile on EP220, EP221B (Collected Batch Acknowledgements), and EP110B (Outgoing Interchange Batch Summary). Description This report is based on batch acknowledgement transactions sent by the VIC to confirm batches received from this processing center. It lists all batches received by the VIC since the last time this report was produced (usually the last cycle). It shows the results of comparison between the Edit Package History File and the incoming batch acknowledgement transactions. Three columns are printed for each batch, reflecting what was sent by a member and what was accepted or returned by the VIC. When the batch acknowledgement data does not reconcile with the information in the Edit Package History File, you will receive an out-of-balance condition message.
The layout of Report EP221D is the same as EP221E. This report summarizes collected interchange by transaction code for all batches acknowledged on one Central Processing Date. If files containing acknowledgements from more than one processing date are processed, a separate EP221D report will be created for each day.
Reports EP240N, EP240V, and EP240C have the same format. Only EP240N is explained in detail.
On-Request Reports
On-request reports can be produced at any time by processing centers. They can be used to print the contents of internal Edit Package files.
Provides a permanent record of the contents of the BIN Validation Table, which shows the status of BINs used for the current processing cycle. Description This report prints a formatted dump of the Edit Package internal BIN Validation Table. EP301 lists each BIN in numerical sequence, reading from left to right across each line. To obtain this report, enter the following parameters when executing the E3U510 utility program: E3U510^REPORT^BIN
Description This report produces a formatted dump of Edit Package internal Rule and Value Tables, which consist of: Country Code Table Currency Code Table Holiday Table Merchant Category Value Table Chargeback Reason Code Table Transaction Code Value Table Fee Collection Reason Code Table Return Item Reason Code Table Sendback Reason Code Table List all value table Ids Language Table for all language file tables Rules Table for all rules file tables
To obtain this report, enter the following parameters when executing the E3U510 utility program: E3U510^REPORT^MERCAT
The EP303 LIST report lists the headers and values. It is used to determine the table ID of tables that can be reported. To obtain this report, enter the following parameters when executing the E3U510 utility program: E3U510^LIST
Report ID EP701, EP702, EP703, EP709, EP719, EP730, EP731, EP732, EP733, EP738*, EP739, EP 742, EP743, EP744, EP746, EP754, EP757, EP759, EP790, EP791, and EP792 Purpose Displays record data in transaction codes 01, 02, 03, 09, 19, 30, 31, 32, 33, 38, 39, 42, 43, 44, 46, 54, 57, 59, 90, 91, and 92. Description Each of these reports provides an unformatted listing of individual transactions.
Depending on the value of the FEERPTFMT run control option, one of the following set of reports will be generated during incoming runs: Visa Originated Fee Collections (EP710V) Non-Visa Originated Fee Collections (EP710N) Combined Visa and Non-Visa Originated Fee Collections (EP710C)
This report provides a listing of the data for each ISO-enriched BASE I advice record on the BASE I advice file for the processing centers cardholders. The report is useful in the manual reconciliation and review of this activity.
Frequency Each incoming interchange run or generated on request using the TCOUTPRT run control option (outgoing). Description This report provides a listing of each request received by the processing center for a copy of the original of a sales draft, credit voucher, or cash advance. The report is used as a source when searching for originals or microfilm, and when issuing confirmations of mailings to the requesting processing center.
Displays record data in National Settlement Advice transactions (transaction code 58). Frequency Each incoming interchange run or generated on request using the TCOUTPRT run control option (outgoing). Description This report provides a listing of each National Settlement Advice transaction passed by the VIC from other centers within the same country exchanging national settlement (National Net or National Bilateral) or intercountry transactions.
Output Summary
At the end of a run, the Edit Package creates a list of all reports produced during the entire run. Reports are listed by report ID, title, and number of pages.