9.1.1 Configure ERP Settings

Configure ERP Settings to establish the connection between AFCS and other applications and other changes post-deployment.

Note:

For Service Instances Upgrade: ERP Settings should be re-saved via the UI for automatic creation of BI Cloud Connector extract jobs to be available.

Note:

The user credentials to access the ERP interface should have the following entitlements at a minimum:

• Access and execute upload of files into UCM associated with said ERP Financials service instance.
• Access and execute APIs in said ERP Financials service instance.

Note:

Users must raise a SR for allow listing the following URLs:

• ERP URLs :

  The example URLs are as follows:

  • https://xxxx.login.xx.oraclecloud.com
  • https://xxxx.fa.xx.oraclecloud.com
• AFCS URL :

  The example URLs are as follows:

  • https://xx-xxxxx.ofsaa.xx-xxxxx-1.ocs.oraclecloud.com/<<tenant-id>>/afc

To configure ERP Settings, follow these steps:

1. On the Home page, click the My Profile icon located on the top-right corner and select Administration.
2. Select ERP Settings from the LHS menu.
3. Enter the following details:
   • URL for Accounting Hub Cloud Service: Enter the URL assigned to you as part of your Oracle ERP Cloud AHCS subscription here. This information is specific to your tenancy on Oracle Cloud and subscription to ERP Cloud AHCS instance.

     For example:

     https://abc.de.fg.oraclecloud.com

   • Version: Enter the version of the AHCS instance.
   • User ID: Enter the user identification assigned to you for the AHCS instance here.
   • Password: Enter the password for your AHCS instance here.

     OR

     You can specify the JWT token-based authentication to integrate with ERP.
   • Token: Enter the JWT token. For more details on how to generate the JWT token, see Configure JWT Authentication Provider.
   • Event Type Column Name: This is pre-populated with the Transaction Type value: the auto-generated value for the Transaction Type Column Name in the Register Transaction Source System step.

     If you modify the auto-generated value for Transaction Type Column Name in the Register Transaction Source System step, edit the pre-populated text and capture the assigned column name here.

   • Line Number Column Name: This is pre-populated with the LINE NUMBER value, the auto-generated value for Line Number Column Name in the Register Transaction Source System step.

     If you modify the auto-generated value for the Line Number Column Name in the Register Transaction Source System step, edit the pre-populated text and capture the assigned column name here.

   • Date Format: Enter the date format which your instance of AHCS accepts for the date columns. If you do not enter a value here, the date field uses the default format.
   • Supporting Reference Mapping:

     Line numbers generated for each SLA in AFCS must be configured as supporting reference attribute in ERP. The supporting reference attribute must be added to all accounting methods. Once completed, respective supporting reference attribute number must be specified in AFCS by updating the Supporting reference mapping field. By default, it is set to Supporting Reference 31.

     For more details on how to add a line number as a Supporting Reference in an ERP instance, refer to the ERP documentation.

4. Click Save or Test Connection.
   For more information, see the Verification of ERP Setting section.

   After you save, the entered settings are used while producing the Transaction Template. This is a one-time setup activity. Do not change these settings unless required by changes to your instance of AHCS.

   After you save, the following jobs are created in the BI Cloud Console for General Ledger and Journal Extraction:

   • GL_SR_EXTRACT_JOB
   • JOURNAL_INGESTION_EXTRACT_JOB

     Note:

     The above jobs will extract records with PRIMARY ledger type.