Monitoring from Integration
Use any of the following to monitor the integration:
Monitoring Using WebLogic SOA Enterprise Manager
Perform the following steps to monitor through WebLogic SOA Enterprise Manager:
1. Login to the WebLogic SOA Server Enterprise Manager, and then navigate to SOA > SOA-Infra > CCB-EBS.
All composite processes deployed for integration are available under the partition CCB-EBS.
2. Select the appropriate process to list all the instances for the processes sorted by time of execution.
3. Click the appropriate process instance and it displays the flow for the process. The composite flow lists all activities in the process instance.
Monitoring Using WebLogic Logs
Login to the machine where SOA server is installed. The SOA logs are stored in:
<WebLogic installation folder>/user_projects/domains/<SOA Domain name>/servers/<SOA Server name>/logs
Example: /Oracle/Middleware/Oracle_Home/user_projects/domains/soa_domain/servers/soa_server1/logs
Monitoring Using Integration Error Store Table
Errors occurring during the integration such as when financial transactions are extracted or summarized, when data formats are translated, or when data is inserted into one of the edge applications are logged and reported by the integration product in the INTEGRATION_ERROR_STORE table.
Use standard database (SQL based) tools to view the error information in the table if necessary, however the e-mail notification you receive must include all of the information necessary to investigate and correct the error.
If errors occur during the extraction or load process for any of the integration points, the system logs an error in INTEGRATION_ERROR_STORE. Business data is stored in the ERROR_MESSAGE field of the table, and the information is also included in the notification email.
The following sections indicate where to locate error messages and logged error data in each of the integration point:
GL Integration Point
If errors occur during the extraction of Financial Transactions from Oracle Utilities Customer Care and Billing tables or during loading these transactions into Oracle E- Business Suite Financials for General Ledger and Accounts Payable GL_INTERFACE table, integration process inserts the error into INTEGRATION_ERROR_STORE.
The following business data is stored in the ERROR_MESSAGE field of INTEGRATION_ERROR_STORE. This information is included in the notification email.
The GL integration point utilizes set based processing. If there is an error, with any part of the batch, the entire batch is rejected.
Table
Column
Data Type
CI_FT_PROC
BATCH_NBR
NUMBER (10)
CI_FT_GL
DST_ID
CHAR (10)
CI_FT_GL
GL_ACCT
VARCHAR2 (48)
CI_FT
CIS_DIVISION
CHAR (5)
CI_FT
GL_DIVISION
CHAR (5)
AP Request Integration Point
If errors occur during the extraction of Financial Transactions from Oracle Utilities Customer Care and Billing tables or during loading these transactions into Oracle E- Business Suite Financials for General Ledger and Accounts Payable Invoice Interface tables, BPEL inserts the error into INTEGRATION_ERROR_STORE.
The following business data is stored in the ERROR_MESSAGE field of INTEGRATION_ERROR_STORE. This information is included in the notification email:
Table
Column
Data Type
CI_ADJ_APREQ
AP_REQ_ID
CHAR (12)
BATCH_NBR
NUMBER (10)
ENTITY_NAME
VARCHAR2 (64)
SCHEDULED_PAY_DT
DATE
CI_ADJ
ADJ_ID
CHAR (12)
CRE_DT
CHAR (12)
ADJ_TYPE_CD
CHAR (8)
ADJ_AMT
NUMBER (15,2)
CI_SA
CIS_DIVISION
CHAR (5)
AP Data Integration Point
The following business data is stored in the ERROR_MESSAGE field of INTEGRATION_ERROR_STORE. This information is included in the notification email:
Table
Column
Data Type
AP_CHECKS_ALL
CHECK_NUMBER
NUMBER (15)
CHECK_ID
NUMBER (15)
CHECK_DATE
DATE
AMOUNT
NUMBER
BANK_ACCOUNT_NUM
VARCHAR2 (50)
AP_INVOICES_ALL
INVOICE_NUM
VARCHAR2 (50)
PAYMENT_REASON_COM MENTS
VARCHAR2 (240)
INVOICE_ID
NUMBER (15)
VENDOR_ID
NUMBER (15)
 
VENDOR_SITE_ID
NUMBER (15)