Verifying the Implementation

The best way to verify the implementation is to start each application individually then manually running the integration points:

• GL Integration Point

• AP Request Integration Point

• AP Data Integration Point

GL Integration Point

1. Identify Financial Transactions in CI_FT table that must be sent to Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL for creating Journal Entries. If needed, generate a bill, adjustment, or payment event to create financial transactions.

2. Run the GLASSIGN process to assign the Account Number to the FT in CI_FT.

3. Run the GLS process to mark the FTs in the CI_FT table for download. The staging process to create a GL download (GLS) creates a staging record for every financial transaction that is ready for download. This process populates the FT / Batch Process table with the unique ID of all financial transactions to be interfaced to the GL. This process marks each staging record with the batch process ID (defined on the installation record) for the GL interface. It also stamps the current run number for the respective batch control record.

Note: The integration BPEL process uses the information on this staging table to create the consolidated journal entries that are interfaced to your GL. The integration process reads the CI_BATCH table to check for new BATCH_JOB_ID and BATCH_JOB_STAT_FLG.

4. Run the GLS process.

5. Invoke the GL Integration Point process from enterprise manager or wait for its next run to occur. The package does the following:

• Select the FT in the CI_FT table based on the batch code and the run number provided to it by Oracle BPEL Process Manager.

• Extract and group (summarize) the Financial Transactions (FT) and push them into Oracle BPEL Process Manager.

• Update the Distribution status to 'D' after extracting the FT and increment the NEXT _BATCH_NBR in the CI_BATCH_CTL table.

• Data is transformed by the BPEL process and written to the GL journal staging table in Oracle E-Business Suite financials for General Ledger and Accounts Payable.

6. Use the Oracle E-Business Suite GL Journal import Process to load the GL data into the Oracle E-Business Suite financials for General Ledger and Accounts Payable GL base tables.

AP Request Integration Point

1. Create an AP Request for a refund customer in Oracle Utilities Customer Care and Billing. You must generate an adjustment of the appropriate type to do this.

2. Run the GLASSIGN process to assign the Account Number to the FT in CI_FT.

3. Invoke the AP Request Integration Point to extract the AP Request Information, and the corresponding customer information from Oracle Utilities Customer Care and Billing, transform it, and load it into Oracle E-Business Suite Financials for General Ledger and Accounts Payable AP Invoice Interface tables.

4. Run the Payables Open Interface Import (APXIIMPT) in Oracle E-Business Suite Financials for General Ledger and Accounts Payable to create Invoices from the AP Check Request and Customer data that is staged in the Invoice Interface tables.

AP Data Integration Point

1. Generate a payment in Oracle E-Business Suite Financials for General Ledger and Accounts Payable Payables for an Invoice created by the Oracle Utilities Customer Care and Billing AP Request process above.

2. Invoke the AP Data Integration Point to update the AP Check Request table (CI_ADJ_APREQ) with the Payment Information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable.

3. If you wish to further test a cancellation of payment functionality, cancel the Payment you made above in Oracle E-Business Suite Financials for General Ledger and Accounts Payable Payables.

4. Invoke the integration process to update the AP Check Request table (CI_ADJ_APREQ) with the Payment Information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable. This cancels the AP Request and adjustment.