Apps Functional

Oracle setup steps for Customer outbound interface through PIP to Siebel

By Jag - April 04, 2014

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.
  1. oracle.apps.ar.hz.OrgCustBO.create
  2. oracle.apps.ar.hz.OrgCustBO.update
  3. oracle.apps.ar.hz.CustAccount.merge
  4. 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
  1. TCA Business Object Events: Raise Events Program
  2. 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,
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
+---------------------------------------------------------------------------+
 
**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,
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
+---------------------------------------------------------------------------+
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.
  • Share:

You Might Also Like

0 comments