Extract processes extract information that is interfaced out of the system. Processes of this type typically extract records marked with a given run number. If the requester of the process does not supply a specific run number, the system assumes that the latest run number should be extracted. If you need to re-extract an historical batch, you can - simply supply the respective run number when you request the batch process.
Batch Control ID |
Program Name |
Description |
Multiple Threads |
Extra Parameters |
Records Between Commits / Minutes Between Cursor Re-Initiation |
---|---|---|---|---|---|
CIPPXAPB |
The automatic payment ACH (automated clearing house) download extraction process creates the flat file that is interfaced to the ACH. This process downloads all auto pay download staging records associated with its batch control ID that are marked with a supplied run number. If a run number is not supplied, the process extracts all automatic payment download records marked with the current run number. Note: the ACTVTAPY process updates auto pay download records on their extract date so that they will be downloaded by this process. Refer to Downloading Automatic Payments for more information. |
Yes |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
|
CIPADAPB |
The A/P download process creates the flat file that is interfaced to your accounts payable software (to cut checks). The process that is delivered has skeletal logic and must be customized by your organization to satisfy the needs of your accounts payable software. In order to adapt the base product program to your specific needs, please following the standard steps:
This process uses all adjustment extract records associated with its batch control that are marked with a supplied run number. If a run number is not supplied, the process uses all A/P request extract records marked with the current run number. Refer to the A/P Interface for more information. |
Yes |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
|
Java |
This SEPA (Single Euro Payments Area) Direct Debit extract process creates the flat file that contains direct debit collection transactions. This process downloads all auto pay download staging records associated with its batch control code and that are marked with a supplied run number. If a run number is not supplied, this process will extract all auto pay staging records marked with the current run number. Note: the ACTVTAPY process updates auto pay download records on their extract date so that they will be downloaded by this process. Refer to the Download SEPA Direct Debit Collections for more information. |
Yes |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
|
DWLDCOLL |
CIPLXCRB |
The collection agency referral download extraction process creates the flat file that contains referrals to be interfaced to your collection agencies. This process extracts all collection agency referral history records associated with its batch control that are marked with a supplied run number. If a run number is not supplied, the process extracts all referral history records marked with the current run number. The program that is delivered contains skeletal logic that should be used as the basis for your specific processing. The skeletal logic does NOT extract information to a flat file; you must introduce the logic to support your specific flat file format. In order to adapt the base product program to your specific needs, please following the standard steps:
Note: records are written to the referral history table when a collection agency oriented write-off events are activated. Referral history records may also be added manually by an operator. Refer to The Big Picture of Collection Agency Referrals for more information. |
No |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
CIPFXGLB |
The general ledger download process creates the flat file that is interfaced to your general ledger software. This process uses all FT / Batch Process records associated with its batch control that are marked with a supplied run number. If a run number is not supplied, the process uses all FT / Process records marked with the current run number. In order to adapt the base product program to your specific needs, please following the standard steps:
Refer to The GL Interface for more information. |
No |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
|
CIPCLTPB |
The customer contact letter download process creates the flat file(s) that are interfaced to your letter print software to print letters associated with letter-oriented customer contacts. This process extracts all customer contact records associated with its batch control ID that are marked with a supplied run number. If a run number is not supplied, the process uses all customer contact records associated with its batch control ID that are marked with the current run number. Each downloaded letter's output is written to a filename that is a concatenation of the letter's Letter Template Code and the process's Thread Number. This means that this process can write to multiple files as multiple Letter Template Codes may be downloaded by this process. The information that is extracted and placed on the flat file for each letter is controlled by each customer contact's letter template's extract algorithm. Refer to Letter Templates Control The Information Merged Onto Letters for information about how a letter's flat file records are constructed. The FILE-PATH parameter controls where the output files are placed. The format of the information on the flat file can be either tilde delimited or in a fixed position (based on the FIELD-DELIM-SW parameter). Tilde delimited output is used if you merge the information into a Word template. Fixed position output is used if you merge the information into a template that expects this type of format. You can use the CNTL-REC-SW parameter to cause the extract to produce a control record that contains batch code, run number, number of letters to print, etc. Refer to Printing Letters for more information. |
Yes |
FILE-PATH= directory path into which output should be placed FIELD-DELIM-SW=Y or N CNTL-REC-SW=Y or N |
NA |
|
CIPBXBLB |
The bill print process creates the flat file that is interfaced to your bill print software. This process uses all bill routing extract records associated with its batch control that are marked with a supplied run number. If a run number is not supplied, the process extracts all bill routing extract records marked with the current run number. The information that is extracted and placed on the flat file for each bill is controlled by each bill route type's extract algorithm. Refer to Bill Route Controls The Information Merged Onto Bills for information about how a bill's flat file records are constructed. The FILE-PATH parameter controls where the output files are placed. Refer to Printing Bills for more information. |
Yes |
FILE-PATH= directory path into which output should be placed FILE-NAME= name of file into which output should be placed |
NA |
Please refer to Column Descriptions for more information on the columns used in the table above.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.