Ordering File 

Use

The ordering file is needed in general to transfer card data to the processor. Depending on the degree of processing, this processor fulfills various tasks that are not covered by the banking system.

The function consists of several subfunctions:

Generating an Ordering File

This function enables you to exchange the data for cards being ordered with the processor.

Depending on the processor, a file is then generated in an agreed format and stored in the chosen file system.

After such an ordering run, you have the option of viewing the log for the file that has been generated so that you can identify and, if necessary, adjust incorrect data records. Card records (card ordering data) that are not included are processed in the next ordering run.

Managing an Ordering File

You can process a created ordering file further. You can find out more about the card records contained in this file so you know, for example, how to respond to queries from the processor.

You have the option of downloading and saving the file locally.

You can also display the history of downloads made and duplicates generated.

You can create a duplicate of an ordering file directly from this transaction.

Generating a Duplicate

It is possible to generate a duplicate of an ordering file.This is necessary if the file no longer exists in the previously agreed file system (TemSe is standard) and has not yet been forwarded to the processor, or has been lost during transport there.

This means the duplicate is generated from data that is in the database.

The local saving of files and generation of duplicates are updated in a history table.

Displaying an Ordering File Application Log

A log is created in each individual subarea of the ordering file. You can view this directly in all functions.

This function gives you the option of displaying the logs for the ordering file and other communication processes for cards independently.

Confirmation of Order

This function is used to import confirmation data from a processor into the system. It can be executed during end-of-day processing. An application log is completed in parallel to the processing.

Prerequisites

Before you can generate an ordering file, there must be cards in the system that need to be ordered.

You must also ensure that the corresponding BAdI for generating the format according to the card category has been stored.

If you use a processor other than ATOS, you need to implement its format as a BAdI.

Scope of Functions

The ordering file is always forwarded to the processor in batch mode, regardless of the output mode set for the card product.

You can find detailed technical information on status development in Card Management under Setting the Status of a Card.