We would like to integrate customer from Oracle Apps/EBS with Siebel. The integration will be done using PIP (Process Integration Pack) that has been supplied by Oracle.
Step 1: Enable the business events
As per the setup document given by Oracle the business events the following business events have to be enabled in Oracle apps.
- oracle.apps.ar.hz.OrgCustBO.create
- oracle.apps.ar.hz.OrgCustBO.update
- oracle.apps.ar.hz.CustAccount.merge
- oracle.apps.ar.hz.Party.merge
Login to Oracle Apps. Go to System Administrator responsibility
Navigation: Workflow > Workflow Administrator > Business Events
Search for an event, say oracle.apps.ar.hz.OrgCustBO.create.
Ensure that the Status is Enabled. For details on business events you can refer to the following article. Now you need to ensure that all the business events are enabled for the outbound integration to work.
Step 2: Add the TCA programs to the responsibility
Add the following programs to the responsibility from where you will execute
- TCA Business Object Events: Raise Events Program
- TCA Business Object Events: Generate Infrastructure Packages Program
We have added the programs to a request group for Order Management
Step 3: Execute Generate Infrastructure Packages Program
Execute the program, TCA Business Object Events: Generate Infrastructure Packages Program, to generate the packages that will be used by TCA Business Object Events: Raise Events Program.
Go to the responsibility to which you have added the programs in step 1. Execute the program.
Note:
If the Raise Events Program is executed before Generate Infrastructure Packages Program, the program will error out with message as shown below,
+---------------------------------------------------------------------------+ **Starts**25-NOV-2012 11:38:34 **Ends**25-NOV-2012 11:38:35 +---------------------------------------------------------------------------+ Start of log messages from FND_FILE +---------------------------------------------------------------------------+ bes_main(+) get BO versions from BOD delete duplicate rows from BOT populate missing links populate_missing_links()+ populate_missing_links()- insert into GT the root nodes with short circuting completness check for Person BO ORA-06508: PL/SQL: could not find program unit being called Error: Aborting concurrent program +---------------------------------------------------------------------------+ End of log messages from FND_FILE +---------------------------------------------------------------------------+
You can check Metalink note ID 1317394.1 for the same.
Step 4: Update a customer
Open a customer in the customer form
Update some details for this customer and save it record.
Step 5: Execute the Raise Events Program
Go to the responsibility where you had added the program as per step 2. Execute the program, TCA Business Object Events: Raise Events Program.
Click on Submit button to execute the program.
Once the program completes click on View Log button. The log file shows the following,
+---------------------------------------------------------------------------+ Start of log messages from FND_FILE +---------------------------------------------------------------------------+ bes_main(+) get BO versions from BOD delete duplicate rows from BOT populate missing links populate_missing_links()+ populate_missing_links()- insert into GT the root nodes with short circuting completness check for Person BO event type check for Person BO completness check for Org BO event type check for Org BO insert (in GT) all those related PERSON/ORG CUST BO records that are not in GT completness check for Person Cust BO event type check for Person Cust BO completness check for Org Cust BO event type check for Org Cust BO raise the one event per object instance Total count in GT is:2 CDH_EVENT_ID is: 10376 CDH_OBJECT_ID is: 170040 Updating BOT object hierarchy with event_id Raise oracle.apps.ar.hz.OrgBO.update CDH_EVENT_ID is: 10377 CDH_OBJECT_ID is: 170040 Updating BOT object hierarchy with event_id Raise oracle.apps.ar.hz.OrgCustBO.update Updating hz_parties for future short circuiting Person Business Object bo_version_number is: 1 Organization Business Object bo_version_number is: 1 Person Customer Business Object bo_version_number is: 1 Organization Customer Business Object bo_version_number is: 1 Concurrent Program completed successfully. +---------------------------------------------------------------------------+ End of log messages from FND_FILE +---------------------------------------------------------------------------+
The log file gives the event ID for update event.
Step 6: Check BPEL console
Log in to BPEL console
Enter your credentials. Go to Instances tab
You can see that the customer message has been passed into PIP.
Cheers!
Related articles
- Forms login error in Oracle Apps (oraclemaniac.com)
- Document Sequence Numbering (oraclemaniac.com)
- Change Viewer Options to view concurrent request output in web browser (oraclemaniac.com)
- Points to keep in mind while developing Oracle Apps forms (oraclemaniac.com)
- PL/SQL to execute Workflow Background Process (oraclemaniac.com)
- Configure Oracle to receive inbound Sales Orders from Siebel through PIP (oraclemaniac.com)
- Personalize OAF Pages: Add an OAF Page as a new section into an existing OAF Page (oraclemaniac.com)
- Set up Oracle to send Items through PIP to Siebel (oraclemaniac.com)
- Receivables Invoice Interface/Conversion (oraclemaniac.com)
