1-6
Oracle Telecommunications Billing Integrator Implementation Guide
Grouped Sales Order Message
This feature provides a single XML message that includes all the lines of an order. This
enables the billing system to initiate the billing process for the entire order at the same
time. The complete sales order message is grouped by order number and published to
the billing application. A single message per order ensures that the dependencies and
relationships across order lines are maintained when the message is delivered to the
billing system and the billing system can initiate the billing process for the entire order
at the same time.
A group sales order message is useful when an order contains different parts or order
lines that are provisioned at the same time and the billing also happens at the same
time. For example: An order for provisioning Wireless Service, Voice Mail and SMS for
an account. These services are activated immediately and do not have a long waiting
time. These services also can be billed immediately.
In the earlier version of TBI, three separate messages would have been created for each
of the services provided. With group sales order message, billing information for all
these three items can be sent in a single message. The group sales order message is
generated after all the billable lines in the order have been successfully fulfilled and the
products and services on the order are reflected in the customer's installed base.
Note:
Group sales order and sales order line messages are mutually
exclusive.
Publish Bill To Accounts for a Sales Order
The Bill To account (payee account) for each order line is published to the billing
application. In the previous release, the bill-to accounts were part of the sales order line
message. In this release, the Bill To accounts are published separately as independent
account messages.
Additional TCA Events for Account Update Message
The TCA events added to the existing Account Update message are:
•
oracle.apps.ar.hz.Person.update: This event is triggered when there are changes to
personal information about a person.
•
oracle.apps.ar.hz.Organization.update: This event is triggered when there are
changes to information related to an organization.
•
oracle.apps.ar.hz.CustomerProfile.update: This event is triggered when there are
changes to information about the credit characteristics of a single customer account,
customer account site or a party.