For more information, see Setting Up Collaboration History, page
•Middleware independent: TBI requires a middleware as an integration point to billing applications for messaging, transforming, and routing the XML messages. TBI can integrate with any middleware that has a native AQ or JMS adapter. TBI has been tested and certified using Oracle Applications InterConnect (OAI 9.0.4). For information on configuring Oracle Applications InterConnect (OAI 9.0.4), see Configuring Oracle Applications InterConnect, page
•Display bill summary and bill image: TBI provides access to the bill summary data through Oracle Contact Center. The Bill Summary UI displays the bill summary for a single account number. The customer service agents can view the bill summary from the 'Bill Summary' option in Oracle Contact Center. The bill number provided in the bill summary UI is linked to the image data supplied by the billing application. To enable the 'Bill Summary' option in Oracle Contact Center, see Setting up Bill Summary UI, page
•Business Event Enabled: Business Event System is a
Publishing Information to the Billing Applications
TBI publishes information on the following EBS entities to the external billing applications:
•New Account
•Account Update
•Item/Product
•Sales Order
•Grouped Sales Order
Publishing New Account Details
Account information is maintained in Oracle Trading Community Architecture (TCA) and is published to the external billing application only when an order is booked for the first time for an account.
For more information, see Integrating Workflow Process for Publishing Account Information, page
Publishing Account Update Details
Introduction to Telecommunications Billing Integrator