Working with the BACS Format
When you write payments using the BACS format, the system:
Populates the A/P Payment Tape table (F04572OW).
You can view the data written by the Write process here, but Oracle recommends that you do not transfer this data to the media that you use to send the information to your bank because the data will not be formatted correctly.
Populates the Text Processor Header (F007101) and Text Processor Detail (F007111) tables.
You can use the Text File Processor program (P007101) to copy the data from the text processor tables to the media that you send to your bank. The data that you copy from the text file processor tables will be in the correct format for submission to banks.
Generates a summary PDF.
The PDF includes a batch number, which you can use to locate the data in the text file processor tables.
When you write payments using the BACS format from the Work with Payment Groups program, the system populates the A/P Payment Tape table (F04572OW) as shown in this table:
Field |
Description |
|---|---|
KNMID |
The member ID. The system populates this field using the next number for system 04, line 6. |
KNLNID |
The line number. |
KNFNAM |
The file name. For BACS processing, this is F04572B. |
The KNAPTA field includes this payment information:
Line 1: VOL 1 (volume header label).
Line 2: HRD 1 (first file header label).
Line 3: HRD 2 (second file header label).
Line 4: UHL 1 (user header label).
Line 5: Account information, one line per account.
Line 6: Account information, one line per account.
Line 7: EOF 1 (first end-of-file).
Line 8: EOF 2 (second end-of-file).
Line 9: UTL 1 (user trailer label).
Note: This description of the KNAPTA is based on a nine-line payment file. An actual payment file will be a different length, based on how many account information lines it has.