Lookup Type | Lookup Code | Description | Enable |
|
|
| d? |
|
|
|
|
CLN_COLLABORATION | XNB_ACCOUNT | TBI Account | Y |
_TYPE |
|
|
|
CLN_COLLABORATION | XNB_SALESORDER | TBI Sales Order | Y |
_TYPE |
|
|
|
CLN_COLLABORATION | XNB_SYNC_ITEM | TBI Sync Item | Y |
_DOC_TYPE |
|
|
|
CLN_COLLABORATION | XNB_SYNC_ACCOUNT | TBI Sync Account | Y |
_DOC_TYPE |
|
|
|
CLN_COLLABORATION | XNB_ADD_SALESORDE | TBI Add Sales Order | Y |
_DOC_TYPE | R |
|
|
|
|
|
|
Note: After updating the lookup values, bounce the Apache server on the environment only if the values are not reflected in the Collaboration Setup UI.
Setting Up Collaboration Events
A Collaboration Event represents a system component acting on information in a message or XML Payload.
Navigation: Workflow Administrator : Collaboration Monitor : SetUp > Collaboration Event Definition
Notes
Application: Select the Oracle Application that owns the collaboration.
Document Type: Select the Document Message Payload identified for the event.
Setting up the Final Collaboration Event
The final collaboration event must be set up in Collaboration History to record the final status of the overall collaboration. The final event is generally the occurrence of an inbound or outbound message in the XML Gateway. After the collaboration is created or updated from the business flow, the collaboration can be tracked using the Collaboration History function.
Navigation: Workflow Administrator : Collaboration Monitor : SetUp > Collaboration
