GL Account mapping inconsistency

GL Integration point

CCB

When the Journal Voucher is created in Oracle E- Business Suite Financials for General Ledger and Accounts Payable, the Accounting information is incorrect.

Since the source of truth is Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL, the user needs to correct the Accounting Structure in the Oracle Utilities Customer Care and Billing distribution code using information from the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.

Wrong GL Operating Unit

GL Integration point

CCB

The financial information being sent to Oracle E- Business Suite Financials for General Ledger and Accounts Payable has the wrong Operating Unit associated with it.

Correct the GL Division set up in Oracle Utilities Customer Care and Billing to match the GL Operating Unit in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.

Data in AP Request row and BPEL process does not fail.

AP request integration point

CCB

If a particular AP Request has an error in Oracle Utilities Customer Care and Billing, it is not picked by the integration process but the remaining requests of that BPEL run are picked up and inserted into the interface tables and the BPEL process status is successful. If one or more rows have failed at any point in the integration, the information is logged in the integration log table and an error email is generated.

Correct the specific AP Request in error using the tools provided by Oracle Utilities Customer Care and Billing. Then rerun the BPEL integration process.

Data successfully inserted in Oracle E- Business Suite Financials for General Ledger and Accounts Payable interface table, but data has errors.

GL integration point

EBS

If the integration process completes successfully and data is inserted into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface tables, but the data has errors in it, the Journal Generator process may not be able to process the data and create journal vouchers from it.

Correct the information directly in Oracle E- Business Suite Financials for General Ledger and Accounts Payable and load the journal voucher using the online tools provided in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.

Journal Generator process cannot complete successfully.

GL integration point

EBS

When the Journal Generator process encounters errors, the error status/reason associated with the Journal Generator process is also identified in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Process monitor. All the rows in the interface table remain unprocessed and the Distribution Status remains unchanged as ‘N’.

Correct the information directly in Oracle E- Business Suite Financials for General Ledger and Accounts Payable and load the journal voucher using the online tools provided in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.

Journal Generator process completes successfully with bad data.

GL integration point

EBS

In this instance, journals are created for the row of bad data, which can be detected and rectified by viewing, editing, and loading the journal online.

Correct the information directly in Oracle E- Business Suite Financials for General Ledger and Accounts Payable and load the journal voucher using the online tools provided in Oracle E- Business Suite Financials for General Ledger and Accounts Payable. After the process is successfully completed, the Distribution Status of all the rows in the Interface table is updated to ‘D’.

Row of bad data in Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface table does not get picked up.

GL integration point

EBS

The Journal Generator process does not error out and the row of bad data in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface table does not get picked up. This situation can occur if the Accounting Date lies outside the Open Period.

Correct the Accounting Date manually in Oracle E- Business Suite Financials for General Ledger and Accounts Payable.

After the process has completed successfully, the Distribution Status of the row still remains in ‘N’.(does not change to ‘D’).

Error Data in Oracle E-Business Suite Financials for General Ledger and Accounts Payable staging table and the process fails.

AP Request integration point

EBS

All the data is successfully inserted into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Interface tables, but there is an error while running the Invoice build process.

Load the Invoices directly into Oracle E- Business Suite Financials for General Ledger and Accounts Payable and resolve any incorrect data.

Error Data in Oracle E- Business Suite Financials for General Ledger and Accounts Payable staging table and the process does not fail.

AP Request integration point

EBS

Oracle E-Business Suite Financials for General Ledger and Accounts Payable Invoice Build process ends successfully but the Invoices are in recycle status.

Load the Invoices directly in Oracle E- Business Suite Financials for General Ledger and Accounts Payable and resolve any incorrect data.

System or Network Down

Any integration Point

Integration BPEL Process

If server goes down in the middle of an integration process.

If server goes down in the middle of a long running process, it can be restarted and will resume where it went down. A retry policy can be set up in the Oracle BPEL Process Manager which administratively enables BPEL process instances to retry adapter connectivity.

Data failed to insert in the Oracle E- Business Suite Financials for General Ledger and Accounts Payable interface table.

GL integration point

Integration BPEL Process

If one row fails to insert into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Interface table during a batch, the entire batch rolls back. In this instance, the BPEL process shows a status of error and an error notification is sent via email.

Re-establish the connections between BPEL and the edge applications if necessary. Correct the configuration and/or transactional data in the Oracle Utilities Customer Care and Billing database if necessary. Make sure that the GLASSIGN and GLS processes are run again. The Integration process must also be re-run once you have taken the above actions.

GL Account Mapping inconsistency

GL integration point

Integration BPEL Process

When the Journal Voucher is created in Oracle E-Business Suite Financials for General Ledger and Accounts Payable, the

Accounting information is incorrect.

Since the source of truth is Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL, the user needs to correct the Accounting Structure in the Oracle Utilities Customer Care and Billing distribution code using information from the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.

The integration is unable to update the AP Request table with payment information.

AP Data integration point

Integration BPEL Process

It is likely that the error is technical in nature (data mapping etc).

Review BPEL error table and product error logs. Update BPEL and/or product configurations as needed to correct the errors reported. Re-run the integration once corrections have been made.

The integration is unable to invoke the Adjustment Maintenance Service.

AP Data integration point

Integration BPEL Process

It is likely that the error is technical in nature (service retired etc).

Review BPEL error table and product error logs. Update BPEL and/or product configurations as needed to correct the errors reported. Re-run the integration once corrections have been made.