Billing Extract File Name Pattern

The billing extract task creates the following file set in the Gateway outbound source directory:

.dat: The file that contains all the extracted records
.rte: An XML file that contains customer routing information
.eof: A file that indicates the file set is complete

The billing extract task uses a specific file naming pattern to create the file name for each file. All files in the file set contain the same name except for the file extension. The file name must be configured using the add transmission definition screen. The file name is configured in the file name definition table. For more information about configuring the file name, see Transaction Server User's Guide.

The file naming pattern for the notification file uses a substitution pattern to ensure that the file names sent to the Gateway outgoing directory are unique. The following is an example of a file naming pattern used by the billing extract task.

MYBANK.%DTyyyyMMdd%.%DThhmm%.<ext>

The following is an example of a file created on May 29, 2009 at 1:41:23:497 PM:

MYBANK.20090529.134123497.dat
MYBANK.20090529.134123497.rte
MYBANK.20090529.134123497.eof

A formatter is a Java™ class that generates a custom routing file string. To create a custom routing file, the user must implement a unique formatter class and define the class and routing file schema name. Define the class and routing file schema name on the edit transmission definition screen. For more information about defining the class and routing file schema name, see Transaction Server User's Guide.