H Expectations from a COM System for Billing Integration

This appendix provides a summary of the general billing integration expectations from a Central Order Management (COM) system for billing integration (Synchronize Fulfillment Order Accounts and Bill Fulfillment Order).

For feature-specific expectations, see the respective flow feature sections (for example, see Chapter 12, "OLM - Understanding the Bill Fulfillment Order Business Flow" for two-phase billing, time-based offers, and so on). Oracle Order and Service Management (Oracle OSM) and OSM AIA Cartridges meet these documented feature specific expectations and the general expectations listed here. If you are using a COM system other than Oracle OSM, it must comply by all these expectations.

Table H-1 lists the expectations from a COM system.

Table H-1 Expectations from a COM System

Number	Action	Comments
1	Account Synchronization *	The COM system sends the account synchronization message to AIA_CRTCUST_OUT_JMSQ Store and Forward (SAF) Queue. The Consumer (ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer) picks up the message and sends it to CommsProcessFulfillmentOrderBillingAccountListEBF for processing the account synchronization. Or, the COM system can call CommsProcessFulfillmentOrderBillingAccountListEBF directly to process the account synchronization message. To handle Oracle Billing and Revenue Management (Oracle BRM) limitations on customer hierarchy updates, all the lines on the order targeted for a given billing system must be sent at the same time. The target system ID must be stamped on the payload sent. The promotion line must go to every billing system in which promotion components are targeted. This service processes only lines with actions of ADD, UPDATE, and MOVE-ADD and ignores others. The COM system can choose to not send messages that do not have lines with these actions. This service processes only lines with billing type of Service Bundle, Item, Subscription, or Discount, and lines with product type of Offer (Promotion). It ignores the rest. The COM system can optionally filter lines based on this.
2	Initiate Billing or Fulfill Billing *	The COM system sends the Order Interface message to AIA_CRTBO_OUT_JMSQ SAF Queue and the Consumer (ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer) picks up the message and sends it to ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl to interface the order to Oracle Billing and Revenue Management. Or, the COM system can call ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl directly to interface the order to Oracle BRM The COM system must send lines for promotions (product type is Promotion), account-level products (billing type is Item, Subscription, or Discount), service bundles (billing type is Service Bundle), or any combination of these destined for a single billing system. Service Bundle refers to the Service Bundle line and all its children. This service ignores other kinds of lines (for example, Non Service Bundle CP lines); therefore, the COM system can optionally filter them out. The target system ID must be stamped on the payload sent to the service. The COM system must interface the promotion lines to billing either before the first service bundle or the account-level product (including penalties) for the promotion along with it. This applies to both Initiate Billing and Fulfill Billing. The COM system must interface MOVE-ADD lines with the corresponding MOVE-DELETE lines (linked using related line ID). The COM system must interface the one-time charge lines tied to service bundle lines with the service bundles (linked using related line ID). The COM system must interface promotion penalty charges with the promotion line (linked using related line ID).
3	Update Sales Order	The COM system sends the update sales order message to AIA_UPDSO_OUT_JMSQ SAF Queue and the Consumer (UpdateSalesOrderOSMCFSCommsJMSConsumer) picks up the message and sends it to UpdateSalesOrderSiebelCommsProvABCSImpl to update the sales order status in Siebel CRM. Or, the COMS system can call UpdateSalesOrderSiebelCommsProvABCSImpl directly to update the sales order status in Siebel CRM. The COM system is responsible for consolidating status updates and sending only updates that are significant to Siebel CRM or the end customer. It must set a status of Completed for lines that complete fulfillment as this triggers auto-asset functionality in Siebel CRM. Assets are required for supporting Change Order functionality. For more information about how the COM system can use the extended status attributes and other guidelines, see Chapter 16, "OLM - Understanding the Update Sales Order Business Flow."

* - Out-of-the-box (OOTB) these do not send a response back to the caller for system or business errors (Oracle OSM and the OSM AIA Cartridges do not expect such a response).

If your COM system requires a response for business errors (or for business and system errors), see Section 11.5.2, "CommsProcessFulfillmentOrderBillingAccountListEBF" and Section 13.5.2, "ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl" for information about how you can achieve this.