Scheduling the Batch Process
Run the following Oracle Utilities Customer Cloud Service batch processes to create the extracts:
GL Extract For Oracle E-Business Suite for General Ledger and Accounts Payable Batch Process
• Schedule the GLASSIGN and GLS batch processes to run at an appropriate time of day. These processes get sub ledger information in Oracle Utilities Customer Cloud Service and all information that has not been posted to the General Ledger, making them ready for extract.
• After both GLASSIGN and GLS processes have run successfully, schedule the C1-GLFCX batch process to create the GL extract file. Some of the batch parameters are already defaulted. Make sure these parameters are defined.
• fileName: Name of the GL extract file.
Note: The extract file name defined here should be defined in the gl.extract.filename.prefix property name of the CCSEBSFIN_ConfigProps lookup in Oracle Integration Cloud.
Example file name: GLEXTRACTFILE_{BC}_{BN}.csv. Only the GLEXTRACTFILE part is defined in gl.extract.filename.prefix property name in Oracle Integration Cloud. The system variables {BC} - Batch Code and {BN}- Batch Number are not needed.
• filePath: Give the path name to the object storage where the file will be stored.
Example path: file-storage://OS-APP/Int-Export
Refer to the Object Storage Setup Guide 19B at https://docs.oracle.com/cd/F20155_01/index.htm.
Note: When these processes are scheduled to run automatically at a preset time, make sure to have coordinated this timing with the timing of other actions done by Oracle E-Business Suite for General Ledger and Accounts Payable and the integration product. Alternatively, use the standard user interface within Oracle Utilities Customer Cloud Service to run these batch processes manually.
Accounts Payable Extract for Oracle E-Business Suite for General Ledger and Accounts Payable Batch Process
• Schedule the C1-APFCX batch processes to create the AP extract file. Some of the batch parameters are already defaulted. Make sure these parameters are defined:
• source: Indicates the source of the accounts payable request. This value must be a valid value in Payables Lookup, Type= Source in Oracle E-Business Suite for General Ledger and Accounts Payable. Each external system should be defined as a source in Oracle E-Business Suite for General Ledger and Accounts Payable.
Example: CCS
• paymentMethod: The value should be an Oracle E-Business Suite for General Ledger and Accounts Payable valid payment method.
• fileName: Name of the AP extract file.
Note: The extract file name defined here should be defined in the property name apreq.extract.filename.prefix of the CCSEBSFIN_ConfigProps in Oracle Integration Cloud.
Example filename: APEXTRACTFILE_{BC}_{BN}.csv. Only the APEXTRACTFILE part is defined in apreq.extract.filename.prefix property name in Oracle Integration Cloud. The system variables {BC} - Batch Code and {BN}- Batch Number are not needed.
• filePath: Give the path name to the object storage where the file will be stored.
Example path: file-storage://OS-APP/Int-Export
Refer to the Object Storage Setup Guide 19B at https://docs.oracle.com/cd/F20155_01/index.htm.
Note: When these processes are scheduled to run automatically at a preset time, make sure to have coordinated this timing with the timing of other actions done by Oracle E-Business Suite for General Ledger and Accounts Payable and the integration product. Alternatively, use the standard user interface within Oracle Utilities Customer Cloud Service to run these batch processes manually.
Run the following Oracle Utilities Customer Care and Billing batch processes to create the extracts:
GL Extract For Oracle E-Business Suite for General Ledger and Accounts Payable Batch Process
• Schedule the GLASSIGN and GLS batch processes to run at an appropriate time of day. These processes get sub ledger information in Oracle Utilities Customer Care and Billing and all information that has not been posted to the General Ledger, making them ready for extract.
• After both GLASSIGN and GLS processes have run successfully, schedule the C1-GLFCX batch process to create the GL extract file. Some of the batch parameters are already defaulted. Make sure these parameters are defined.
• fileName: Name of the GL extract file
Note: The extract file name defined here should be defined in the property name gl.extract.filename.prefix of the CCSEBSFIN_ConfigProps in Oracle Integration Cloud.
Example file name: GLEXTRACTFILE_{RDT}.csv. Only the GLEXTRACTFILE part is defined in gl.extract.filename.prefix property name in OIC. The system variables {RDT} - appends the date time to file name is not needed.
• filePath: Give the path name to the file storage where the file will be stored.
Example Path: file-storage://file-APP/GLSFileDirectory
When these processes are scheduled to run automatically at a preset time, make sure to have coordinated this timing with the timing of other actions done by Oracle E-Business Suite for General Ledger and Accounts Payable and the integration product. Alternatively, use the standard user interface within Oracle Utilities Customer Cloud Service to run these batch processes manually.
Accounts Payable Extract for Oracle E-Business Suite for General Ledger and Accounts Payable Batch Process
• Schedule the C1-APFCX batch processes to create the AP extract file. Some of the batch parameters are already defaulted. Make sure these parameters are defined:
• source: Indicates the source of the accounts payable request. This value must be a valid value in Payables Lookup, Type= Source in Oracle E-Business Suite for General Ledger and Accounts Payable. Each external system should be defined as a source in Oracle E-Business Suite for General Ledger and Accounts Payable.
Example: CCS
• paymentMethod: The value should be an Oracle E-Business Suite for General Ledger and Accounts Payable valid payment method.
• fileName: Name of the AP extract file
Note: The extract file name defined here should be defined in the property name apreq.extract.filename.prefix of the CCSEBSFIN_ConfigProps in Oracle Integration Cloud.
Example filename: APEXTRACTFILE_{RDT}.csv. Only the APEXTRACTFILE part is defined in apreq.extract.filename.prefix property name in Oracle Integration Cloud. The system variables {RDT} is not needed.
• filePath: Give the path name to the file storage where the file will be stored.
Example path: file-storage://file-APP/APFileDirectory
When these processes are scheduled to run automatically at a preset time, make sure to have coordinated this timing with the timing of other actions done by Oracle E-Business Suite for General Ledger and Accounts Payable and the integration product. Alternatively, use the standard user interface within Oracle Utilities Customer Cloud Service to run these batch processes manually.