H Expectations from an Order Management System for Billing Integration

This appendix provides a summary of the general billing integration expectations from an order management system for billing integration (the Synchronize Fulfillment Order Accounts and Bill Fulfillment Order business flows).

For feature-specific expectations, see the respective flow feature sections (for example, see "Understanding the Bill Fulfillment Order Business Flow" for two-phase billing, and time-based offers).

Oracle Communications Order and Service Management (OSM) and OSM AIA Cartridges meet these documented feature specific expectations and the general expectations listed here. If you are using an order management system other than OSM, it must comply with all of these expectations.

The expectations from an order management system are as follows:

• For Account Synchronization actions:

  • The order management system can either call CommsProcessFulfillmentOrderBillingAccountListEBF directly to process the account synchronization message, or it can send 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.

  • To handle Oracle Communications Billing and Revenue Management (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 order management 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 order management system can optionally filter lines based on this.

• For Initiate Billing or Fulfill Billing actions:

  • The order management system can either call ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl directly to interface the order to BRM, or it can send the Order Interface message to AIA_CRTBO_OUT_JMSQ SAF Queue. The Consumer (ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer) picks up the message and sends it to ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl to interface the order to BRM.

  • The order management 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 customizable product lines); therefore, the order management system can optionally filter them out. The target system ID must be stamped on the payload sent to the service.

  • The order management 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 order management system must interface MOVE-ADD lines with the corresponding MOVE-DELETE lines (linked using related line ID).

  • The order management system must interface the one-time charge lines tied to service bundle lines with the service bundles (linked using related line ID).

  • The order management system must interface promotion penalty charges with the promotion line (linked using related line ID).

• For Update Sales Order actions:

  • The order management system can either call UpdateSalesOrderSiebelCommsProvABCSImpl directly to update the sales order status in Siebel CRM, or it can send the update sales order message to AIA_UPDSO_OUT_JMSQ SAF Queue. The Consumer (UpdateSalesOrderOSMCFSCommsJMSConsumer) picks up the message and sends it to UpdateSalesOrderSiebelCommsProvABCSImpl to update the sales order status in Siebel CRM.

  • The order management 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.

  • See "Understanding the Update Sales Order Business Flow" for more information on how the order management system can use the extended status attributes and other guidelines.

By default, Account Synchronization, Initiate Billing, and Fulfill Billing actions do not send a response back to the caller for system or business errors (OSM and the OSM AIA Cartridges do not expect such a response).

If your order management system requires a response for business errors (or for business and system errors), see "CommsProcessFulfillmentOrderBillingAccountListEBF" and "ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl" for information on how to achieve this.