TXN TYPE | TXN SUB | MAP | CONN/HU | USERNAM | SRCT P | DOC |
| TYPE |
| B | E | LOC | CONF |
|
|
|
|
| CODE |
|
|
|
|
|
|
|
|
XNB | CBODI | XNB_CLN | - | - | <Hub | 0 |
|
| _CBOD_O |
|
| Entity |
|
|
| AG72_IN |
|
| Code of |
|
|
|
|
|
| Billing |
|
|
|
|
|
| Applicatio |
|
|
|
|
|
| ns> |
|
|
|
|
|
|
|
|
Defining Trading Partners
A trading partner is an entity which exchanges messages with the XML Gateway. The trading partner has many transactions enabled for each hub user. The transactions enabled for each hub user determines the type of messages generated and the direction of the message. The Protocol Type is populated for outbound messages from the hub protocol type. Protocol Type is not applicable for inbound messages.
For more information about setting up trading partners, see the Oracle XML Gateway User's Guide.
Party and Location for the Hub must be created in TCA. For details, see Oracle Trading Community Architecture User Guide.
Navigation: XML Gateway Setup > Define Trading Partners.
Notes
Company Admin Email: Enter the System Administrator's
Connection/Hub: Enter 'XNB_HUB'. This is required only for outbound messages.
Destination Trading Partner Location Code: Leave this field blank.
Document Confirmation: Specifies if the trading partner would like to send or receive a confirmation. Select 2 (Always send a confirmation) for outbound messages and select 0 (Never send a confirmation) for inbound messages.
Setting Up Oracle Collaboration History
Oracle Collaboration History maintains a history or record of the communication between EBS and the billing applications. Using Collaboration History, you can track all the events and messages exchanged during a collaboration including exceptions and the XML Payloads where available. Setting up Oracle Collaboration History involves the following:
