Adding a collaboration switch to the database
Authorized users can add collaboration switches to the MXCOLLAB table. New switches must use an existing process control ID, but they can use new system IDs.
About this task
Only the default collaboration switches can use the values THISMX and EXT in the system ID fields.
Procedure
Example
For example, you can configure the integration framework to integrate with an Oracle Financials system and other applications. When Oracle Financials issues system-owned inventory, the integration framework accepts the transaction and updates inventory balances and costs in the Maximo database. When other applications issue system-owned inventory, the integration framework accepts the transaction, but does not update inventory balances or costs in the Maximo database.
Before you modify the MXCOLLAB table to reflect these conditions, the INV collaboration switches have the following values:
Process Control ID | System ID 1 | System ID 2 | Process Control Value |
---|---|---|---|
INV | THISMX | EXT | 1 |
INV | EXT | THISMX | 0 |
INV | EXT | EXT | 1 |
To modify the MXCOLLAB table, to support this scenario:
- To update the collaboration switch, use the following SQL statement:
This statement changes the value of the INV/ EXT/ THISMX collaboration switches to 1 to bypass normal update processing.update mxcollab set pcvalue = 1 where pcid = 'INV' and owner1sysid = 'EXT' and owner2sysid = 'THISMX';
- Use the following SQL statement to add a new collaboration switch
for transactions from the Oracle Financials system:
The new collaboration switch sets ORC as the system ID, and sets the process control value to 0 so that normal processing is applied to issue transactions received from Oracle Financials. If the OWNERSYSID is blank, the value in the DEFEXTSYS integration control is used.insert into mxcollab (pcid, owner1sysid, owner2sysid, pcvalue) values ('INV', 'ORC', 'THISMX', 0);
After you perform this procedure, the INV collaboration switches have the following values.
Process Control ID | System ID 1 | System ID 2 | Process Control Value |
---|---|---|---|
INV | THISMX | EXT | 1 |
INV | EXT | THISMX | 1 |
INV | EXT | EXT | 1 |
INV | ORC | THISMX | 0 |
For example, when you set the value of the ISUIN integration control to 1, issue transactions are accepted from an external system. The INV collaboration switch controls the update of inventory balance and cost related to issues. You can adjust the setting of this switch, if necessary, to bypass that update process.
The INV/EXT/THISMX collaboration switch controls the processing of inventory (where the Process Control ID = INV) that is issued in the external system (System ID 1 = EXT) and owned by the system (System ID 2 = THISMX).
If the value of the INV/EXT/THISMX collaboration switch is 0, default processing applies and inventory balance and cost values are updated.
If the value of the INV/EXT/THISMX collaboration switch is 1, default processing is bypassed and inventory balance and cost values are not updated.
In the example, ISUIN accepts any issues into the system. The INV/EXT/THISMX collaboration switch determines how the inventory business component processes a specific type of issue.