D-2
Oracle Telecommunications Billing Integrator Implementation Guide
as the TCA account or the OM Sales Order. The structure and content of this area
varies based on the DTD for each message.
Outbound and Inbound BOD
TBI provides the XML DTDs for all the messages exchanged between E-Business Suite
and the external billing applications. These DTDs must be used to define BODs in the
messaging middleware. TBI generates outbound BODs corresponding to:
1.
TCA Account (Add and Update)
2.
OM Sales Order
3.
Inventory Item
4.
Grouped Sales Order
There is only one inbound BOD for TBI. This is the ConfirmBOD (CBOD). The CBOD is
used by the billing application to return the status of processing the outbound BODs.
Note:
The DTDs for BODs must be used along with the OAG based
DTDs to define the business objects in the messaging middleware. The
OAG based DTDs are modified to include extensions for TBI.
XML Message Format
Oracle XML Gateway generates the TBI outbound messages and they are delivered as
Advanced Queue payloads. The inbound messages (CBOD messages) from a billing
application must contain information that the E-Business Suite can use to track success
or failure of a published outbound message.
Outbound Messages
The outbound messages publish information on the Oracle E-Business Suite objects,
such as customers, products, sales orders, and so on to the external billing applications.
Messages are delivered to the Outbound AQ: XNB_JMS_OUTBOUND queue and are
picked up by the middleware adapters from the queue.
JMS Message Structure
The table below lists the structure of the JMS standard message.
