IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 308 / 330

Collaboration Switch Additions
294
Integration Guide
Before you modify the MXCOLLAB table to reflect these conditions, the INV
collaboration switches to have the following values:
Modifying the MXCOLLAB Table
To modify the MAXCOLLAB table:
1
Change the value of the INV/ EXT/ THISMX collaboration switches to 1 to
bypass normal update processing.
To update the collaboration switch, use the following SQL statement:
update mxcollab
set pcvalue = 1
where pcid = ’INV’
and owner1sysid = ’EXT’
and owner2sysid = ’THISMX’;
2
Select a system ID to represent Oracle Financials.
This procedure uses ORC as the system ID.
3
Add a new collaboration switch INV/ORC/THISMX to the MXCOLLAB table.
The single SQL statement following step 5 performs the processing for steps 3,
4, and 5.
4
Set the new collaboration switch process control value to 0.
This value directs the system to perform the normal balance and cost updates
when it receives issues from Oracle Financials.
5
Set the OWNERSYSID attribute on the inbound transaction to the system ID
you chose in step 2–in this case, ORC.
If OWNERSYSID is blank, the value in the DEFEXTSYS integration control is
used.
To perform the processing described in steps 3, 4 and 5, use the following SQL
statement:
insert into mxcollab
(pcid, owner1sysid, owner2sysid, pcvalue)
values (’INV’, ’ORC’, ’THISMX’, 0);
Process Control ID System ID 1 System ID 2 Process Control
Value
INV THISMX EXT 1
INV EXT THISMX 0
INV EXT EXT 1