4 Invoice Integration Flow

This chapter provides an overview of the invoice integration flows and describes Siebel Customer Relationship Management (Siebel CRM) and Oracle Billing and Revenue Management (BRM) interfaces, industry Oracle Application Integration Architecture (Oracle AIA) components, and integration services.

Invoice Integration Overview

The invoice integration between Siebel CRM and BRM supports the following integration scenarios:

• QueryInvoiceList lets you view a list of invoices for an account billing profile in Siebel CRM.

• QueryPDFInvoice lets you view a PDF version of an invoice in Siebel CRM.

• QueryInvoice lets you view invoice details in Siebel CRM.

• QueryInvoiceUsageAllocation lets you view invoice event details (call detail (CDR) records) in Siebel CRM.

• SearchInvoiceUsageAllocation lets you search invoice event detail records (CDR records) in Siebel CRM.

• QueryInvoiceUsageAllocationResource lets you view nonmonetary resource balance details in Siebel CRM.

BRM generates invoices on a periodic basis by after a bill cycle. Once generated, an invoice does not change. An invoice usually consists of sections for a header, a summary, and details. You can view invoice data at any of these levels, and resolve most bill inquiries by viewing the header and summary. The integration between Siebel CRM and BRM presents the most current invoices in Siebel CRM and retrieves the header, summary, and details on demand from BRM to show in Siebel CRM.

When you select the Bills tab of the Billing Profile screen, the integration shows a list of the latest invoices. You set the number of invoices to display in Siebel CRM, and the integration retrieves that many invoices from BRM. From this list, you can take the following actions:

• View a PDF of the invoice:

  1. Highlight an invoice in the list.

  2. Click View Invoice.

     A PDF corresponding to the invoice appears in a new window.

• View invoice details:

  1. Click the Bill Number link.

     The Bill Detail view appears and the integration retrieves the invoice or bill header and item data, and displays it on the header and items applet of the Bill Detail view. A single request from Siebel CRM invokes two APIs in BRM that call the invoice header and items data and return a single hierarchical message to Siebel CRM.

  2. Click the Payment tab or the A/R items tab.

     The integration retrieves payment or A/R items data for the selected invoice or bill.

• View item or event details:

  1. Click the Bill Number link.

  2. Select an invoice item.

  3. Click the Net Amount link associated with the item charge.

     The integration retrieves the item or event details record from BRM. Because this item detail data is generally large, you can filter the data using search criteria.

• View individual service charges:

  1. Click the Bill Number link.

  2. Select the Service Charges applet.

Note:

The date and time information of the event details and CDR displayed in Siebel CRM is specific to the time zone from where the event originated.

Figure 4-1 illustrates the invoice integration flow.

Figure 4-1 The Invoice Integration Flow

Description of "Figure 4-1 The Invoice Integration Flow"

To view invoice information for an account in the billing profile in Siebel CRM:

1. Navigate to the Accounts screen and query an account. Scroll down to the Billing Profile applet for this account and click the Billing Profile Name link.

2. Click the Bills tab to view a list of invoices.

3. Click the Bill Number link to view the details for that invoice.

4. Go to the Item Charges applet and click the Net Amount link to view the invoice usage allocation (CDRs) for that item.

5. Click the Search tab to search invoice event detail records.

6. In the Event Details, click View Details to query the resource impact details (non-monetary charges, for example free minutes, and so on) for an event from the billing system.

See "Mapping Siebel Billing Management UI Elements to BRM Customer Center" for more information on mapping Siebel CRM elements to BRM elements.

QueryInvoiceList Integration Flow

This integration flow uses the following interfaces:

• InvoiceSiebelCommsReqABCS with operation QueryInvoiceList

• QueryInvoiceListSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

Figure 4-2 illustrates the QueryInvoiceList integration scenario.

Figure 4-2 QueryInvoiceList Integration Flow Sequence Diagram

When you initiate the QueryInvoiceList process, the following events occur:

1. In Siebel CRM, a user navigates to the Accounts screen, queries an account, and clicks a billing profile for the account.

   This displays the Billing Profile BRM screen, Bills tab, a web service call is made to query the list of n invoices for that billing profile. Many invoices may be in BRM, but the number n of invoices to be fetched is sent from Siebel CRM as part of the request message and <=n number of invoices are returned from BRM. The default values of invoices (n) queried depends on the configuration in Siebel Integration Object CMU Request Billing Profile IO integration component Com Invoice Profile field Maximum Number Of Records.

2. Navigating to the Invoice applet in the Billing Profile BRM screen invokes outbound web service InvoiceSiebelCommsReqABCS, which in turn calls the InvoiceSiebelCommsReqABCS with operation QueryInvoiceList.

   InvoiceSiebelCommsReqABCS is a generic Invoice interface service with several operations defined on the Invoice application business message (ABM).

3. Invoking InvoiceSiebelCommsReqABCS with operation QueryInvoiceList routes the QueryInvoiceListReqMsg to the QueryInvoiceListSiebelCommsReqABCSImpl.

4. The QueryInvoiceListSiebelCommsReqABCSImpl first transforms the QueryInvoiceListReqMsg into QueryInvoiceListRequest enterprise business message (EBM) and routes the QueryInvoiceListReqMsg to the appropriate billing systems.

   As delivered, QueryInvoiceListReqMsg is routed to the QueryInvoiceListBRMCommsProvABCSImpl.

5. QueryInvoiceListBRMCommsProvABCSImpl first checks the Query Criteria code.

   If it is Query Invoice List, QueryInvoiceListReqMsg is transformed into PCM_OP_BAL_GET_ACCT_BILLINFO_inputflist. This opcode call returns the list of BILLINFO and AR_BILLINFO of that account.

6. From the response of PCM_OP_BAL_GET_ACCT_BILLINFO opcode, the appropriate BILLINFO and AR_BILLINFO are picked.

   QueryInvoiceListReqMsg is transformed into the input of PCM_OP_AR_GET_ACCT_BILLS and calls the BRM opcode PCM_OP_AR_GET_ACCT_BILLS. Many invoices may be in the billing system for an account billing profile. Based on the value of n passed from Siebel CRM, the application programming interface (API) returns <=n number of invoices.

7. QueryInvoiceListBRMCommsProvABCSImpl then transforms the API output PCM_OP_AR_GET_ACCT_BILLS_RespMsg into EBM QueryInvoiceListRespMsg and returns it to QueryInvoiceListSiebelCommsReqABCSImpl.

8. QueryInvoiceListSiebelCommsReqABCSImpl then transforms the QueryInvoiceListRespMsg into QueryInvoiceListRespMsg, which is returned to the InvoiceSiebelCommsReqABCS.

9. InvoiceSiebelCommsReqABCS returns the QueryInvoiceListRespMsg to the calling Siebel web service InvoiceSiebelCommsReqABCSService.

10. The system then writes the list of bills to the Siebel Invoice virtual business component (VBC) for the user.

QueryPDFInvoice Integration Flow

This integration flow is supported by a process for generating and storing PDF invoices that does not use Oracle AIA services and interfaces. Instead, the process uses custom integration between supporting applications to deliver PDF invoices to Siebel CRM.

The following applications participate in the process of generating, storing, and displaying invoices:

• BRM: Generates invoice data in XML format according to a schedule and sends the data to Oracle Business Intelligence Publisher (BI Publisher) in batches.

• BI Publisher: Converts the BRM XML invoice data to PDFs according to a template and uploads the batch of invoices to Oracle WebCenter Content.

• WebCenter Content: Stores the PDF invoices in a central repository.

• Siebel CRM: Requests the PDF invoices from WebCenter Content and then displays them.

The QueryPDFInvoice integration flow handles the process of requesting the PDF invoices from WebCenter Content and displaying them in Siebel CRM.

Figure 4-3 illustrates the process for generating, storing, and displaying invoices alongside the QueryPDFInvoice integration flow.

Figure 4-3 Process for Generating, Storing, and Displaying Invoices

Description of "Figure 4-3 Process for Generating, Storing, and Displaying Invoices"

As part of the QueryPDFInvoice integration flow, you configure the applications to integrate directly as described in "Setting Up PDF Invoice Display."

QueryInvoice Integration Flow

This integration flow uses the following interfaces:

• InvoiceSiebelCommsReqABCS with operation QueryInvoice

• QueryInvoiceSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

Figure 4-4 illustrates the QueryInvoice integration scenario.

Figure 4-4 QueryInvoice Integration Flow Sequence Diagram

When you initiate the QueryInvoice process, the following events occur:

1. In Siebel CRM, navigate to the Accounts screen, query an account, and click a Billing Profile for the account.

   This displays the Billing Profile screen. Click the Bills tab and drill-down on the Bill Number to call the query invoice information (header, service charges, and items) from the billing system.

2. The InvoiceSiebelCommsReqABCS with the operation QueryInvoice is called.

   The InvoiceSiebelCommsReqABCS is a generic Siebel invoice interface service with several operations defined on the Invoice EBO.

3. The InvoiceSiebelCommsReqABCS with the operation QueryInvoice routes the QueryInvoiceReqMsg to the QueryInvoiceSiebelCommsReqABCSImpl.

4. The QueryInvoiceSiebelCommsReqABCSImpl transforms the QueryInvoiceReqMsg into the Invoice EBM and routes the QueryInvoiceListReqMsg to the appropriate billing system.

   As delivered, QueryInvoiceListReqMsg is routed to the QueryInvoiceListBRMCommsProvABCSImpl.

5. The QueryInvoiceListBRMCommsProvABCSImpl first checks the Query Criteria code. If it is Query Invoice, it then transforms QueryInvoiceListReqMsg into the input of PCM_OP_BAL_GET_ACCT_BILLINFO_inputFlist and invokes PCM_OP_BAL_GET_ACCT_BILLINFO to get the Bill Info object.

   This information is used to populate PCM_OP_AR_GET_BILL_ITEMS_inputFlist and calls the BRM opcode PCM_OP_AR_GET_BILL_ITEMS. The opcode returns the invoice header, service charges, and items in a flat message to the calling QueryInvoiceListBRMCommsProvABCSImpl.

6. The QueryInvoiceListBRMCommsProvABCSImpl transforms the API output PCM_OP_AR_GET_BILL_ITEMS_outputFlist into the EBM QueryInvoiceListRespMsg and returns it to QueryInvoiceSiebelCommsReqABCSImpl.

7. The QueryInvoiceSiebelCommsReqABCSImpl transforms the QueryInvoiceListRespMsg into the QueryInvoiceRespMsg and returns it to the Siebel Invoice ABC interface service.

   The QueryInvoiceListRespMsg is a flat message from which service charges are calculated and the invoice header, service charges, and items are returned as the QueryInvoiceRespMsg to the calling InvoiceSiebelCommsReqABCS.

8. The InvoiceSiebelCommsReqABCS returns the QueryInvoiceRespMsg to the calling Siebel web service.

QueryInvoiceUsageAllocation Integration Flow

This integration flow uses the following interfaces:

• InvoiceSiebelCommsReqABCS with operation QueryEventDetails

• QueryInvoiceEventDetailsSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

Figure 4-5 illustrates the QueryInvoiceUsageAllocation integration scenario.

Figure 4-5 QueryInvoiceUsageAllocation Integration Flow Sequence Diagram

When you initiate the QueryInvoiceUsageAllocation process, the following events occur:

1. In Siebel CRM, navigate to the Accounts screen, query an account, and select the billing profile for the account.

   In the Billing Profile screen, click the Bills tab and select an invoice. Select an item charge and click the Net Amount link of the item to view Event Details. This action calls Siebel outbound web service InvoiceSiebelCommsReqABCS to query the event details from the billing system.

2. Navigating to the Invoice Event Details (call detail (CDR) records) applet in the Billing BRM screen invokes the InvoiceSiebelCommsReqABCSService web service with operation QueryEventDetails, which in turn calls the InvoiceSiebelCommsReqABCS with operation QueryEventDetails.

   InvoiceSiebelCommsReqABCS is a generic Siebel Invoice interface service with several operations defined in the Invoice EBO.

3. Invoking InvoiceSiebelCommsReqABCS with operation QueryEventDetails routes the QueryEventDetailsReqMsg to the QueryInvoiceEventDetailsSiebelCommsReqABCSImpl.

4. The QueryInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the QueryEventDetailsReqMsg into Invoice EBM and routes the QueryInvoiceListReqMsg to the appropriate billing system.

   As delivered, QueryInvoiceListReqMsg is routed to the QueryInvoiceListBRMCommsProvABCSImpl.

5. QueryInvoiceListBRMCommsProvABCSImpl checks query criteria code.

   If it is Query Usage Allocation, then it transforms QueryInvoiceListReqMsg into the input of PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT and calls the opcode PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT.

6. QueryInvoiceListBRMCommsProvABCSImpl then transforms the API output PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT_RespMsg into EBM QueryInvoiceListRespMsg and returns it to QueryInvoiceEventDetailsSiebelCommsReqABCSImpl.

7. QueryInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the QueryInvoiceListRespMsg into QueryEventDetailsRespMsg, which is returned to InvoiceSiebelCommsReqABCS.

8. InvoiceSiebelCommsReqABCS returns the QueryEventDetailsRespMsg to the calling Siebel web service.

9. The system then writes the response message to the Siebel Invoice VBC for the user.

SearchInvoiceUsageAllocation Integration Flow

This integration flow uses the following interfaces:

• InvoiceSiebelCommsReqABCS with operation SearchEventDetails

• SearchInvoiceEventDetailsSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

The SearchInvoiceUsageAllocation supports searching invoice event details (CDR records) on the following columns in addition to the account ID and the item charge ID that are passed to Query Invoice Details:

• Minimum Amount

• Maximum Amount

• Start Date

• End Date

The BRM opcode PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT supports only simple queries, so the search supports passing only the data through and not passing complex query criteria, (for example, >, <, between, and so on).

Figure 4-6 illustrates the SearchInvoiceUsageAllocation integration scenario.

Figure 4-6 ServiceinvoiceUsageAllocation Integration Flow Sequence Diagram

When you initiate the SearchInvoiceUsageAllocation process, the following events occur:

1. In Siebel CRM, navigate to the Accounts screen, query an account, and select the billing profile for the account.

   In the Billing Profile screen, click the Bills tab and select an invoice. Select an item charge, and click the Net Amount link of the item to view event details of all CDR records for that item charge.

2. Clicking the Search button on the Invoice Event Details (CDR details) applet opens the search applet for query.

3. Entering the search criteria and clicking Go invokes an outbound web service InvoiceSiebelReqABCS that in turn calls the InvoiceSiebelCommsReqABCS with operation SearchEventDetails.

   InvoiceSiebelCommsReqABCS is a generic Siebel Invoice interface service with several operations defined on the Invoice EBO.

4. Invoking InvoiceSiebelCommsReqABCS with operation SearchEventDetails routes the SearchEventDetailsReqMsg to the SearchInvoiceEventDetailsSiebelCommsReqABCSImpl.

5. The SearchInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the SearchEventDetailsReqMsg into an Invoice EBM and routes the QueryInvoiceListReqMsg to the appropriate billing systems.

   As delivered, QueryInvoiceListReqMsg is routed to the QueryInvoiceListBRMCommsProvABCSImpl.

6. QueryInvoiceListBRMCommsProvABCSImpl checks the query criteria code. If the query criteria code is Usage Allocation, it then transforms QueryInvoiceListReqMsg into the input of PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT and calls the BRM opcode PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT.

7. QueryInvoiceListBRMCommsProvABCSImpl transforms the API output PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT_RespMsg into EBM QueryInvoiceListRespMsg and returns it to SearchInvoiceEventDetailsSiebelCommsReqABCSImpl.

8. SearchInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the QueryInvoiceListRespMsg into a SearchEventDetailsRespMsg, which is returned to InvoiceSiebelCommsReqABCS.

9. InvoiceSiebelCommsReqABCS returns the SearchEventDetailsRespMsg to the calling Siebel web service.

10. The system writes the search response to the Siebel Invoice VBC for the user.

QueryInvoiceUsageAllocationResource Integration Flow

This integration flow uses the following interfaces:

• InvoiceSiebelCommsReqABCS with operation QueryBalanceDetails

• QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

Figure 4-7 illustrates the QueryInvoiceUsageAllocationResource integration scenario.

Figure 4-7 QueryInvoiceUsageAllocationResource Integration Flow Sequence Diagram

When you initiate the QueryInvoiceUsageAllocationResource process, the following events occur:

1. In Siebel CRM, navigate to the Accounts screen, query an account, and select the billing profile for the account.

   In the Billing Profile screen, click the Bills tab and select an invoice. In Event Details, click View Detail to query the resource impact details for an event from the billing system. A web service call is made to query resource impact details for a particular event from the billing system, which in turn calls the InvoiceSiebelCommsReqABCS with operation QueryResourceBalance.

   InvoiceSiebelCommsReqABCS is a generic Siebel Invoice interface service with several operations defined on the Invoice EBO.

2. Invoking InvoiceSiebelCommsReqABCS with operation QueryBalanceDetails routes the QueryBalanceDetailsReqMsg to the QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl.

3. The QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl transforms the QueryBalanceDetailsReqMsg into Invoice EBM and routes the QueryInvoiceListReqMsg to the appropriate billing system.

   As delivered, QueryInvoiceListReqMsg is routed to the QueryInvoiceListBRMCommsProvABCSImpl.

4. QueryInvoiceListBRMCommsProvABCSImpl checks the query criteria code.

   If the query criteria code is Query Balance Details, it transforms QueryInvoiceListReqMsg into the input of PCM_OP_ AR_RESOURCE_AGGREGATION and calls the opcode PCM_OP_ AR_RESOURCE_AGGREGATION.

5. QueryInvoiceListBRMCommsProvABCSImpl transforms the API output PCM_OP_ AR_RESOURCE_AGGREGATION_RespMsg into EBM QueryInvoiceListRespMsg and returns it to QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl.

6. QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl transforms the QueryInvoiceListRespMsg into QueryBalanceDetailsRespMsg, which is returned to the InvoiceSiebelCommsReqABCS.

7. InvoiceSiebelCommsReqABCS returns the QueryBalanceDetailsRespMsg back to the calling Siebel web service.

8. The system writes the message to the Siebel UsageAllocationResource VBC for the user.

BRM Interfaces

The integration uses opcodes with the integration flows as shown in Table 4-1.

Table 4-1 Invoice Integration Flow Opcodes

Opcode	Integration Flow
PCM_OP_AR_GET_ACCT_BIILS	QueryInvoiceList
PCM_ OP_AR_GET_BILL_ITEMS	QueryInvoice
PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT	QueryInvoiceUsageAllocation
PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT	SearchInvoiceUsageAllocation
PCM_OP_AR_RESOURCE_AGGREGATION_RespMsg	QueryInvoiceUsageAllocationResource

See BRM Opcode Flist Reference and BRM Developer's Guide for more information about individual opcodes.

Siebel CRM Interfaces

The Invoice integration flow uses the following Siebel CRM interface:

• InvoiceSiebelCommsReqABCS

See the Siebel Order Management Guide Addendum for Communications for more information about individual web services.

Industry Oracle AIA Components

The Invoice integration flow uses the following delivered enterprise business object (EBO) and enterprise business messages (EBMs):

• InvoiceEBO

• QueryInvoiceEBM

• QueryInvoiceResponseEBM

• QueryInvoiceListEBM

• QueryInvoiceListResponseEBM

The industry enterprise business object (EBO) and enterprise business message XML schema (EBM XSD) files are located under the Metadata Services (MDS) repository at: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Communications/EBO/

The industry enterprise business service (EBS) WSDL files are located under the MDS repository at: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Industry/Communications/EBO/

For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository (OER).

See "Configuring and Using Oracle Enterprise Repository as the Oracle SOA Repository" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information on how to use and configure OER to provide the AIA Reference Doc link.

EBOs can be extended such as adding new data elements. These extensions are protected and will remain intact even after a patch or an upgrade, so long as the extensibility guidelines are followed.

See "Working with AIA Design Patterns", AIA Assets Extensibility Patterns, Extending Existing Schemas in AIA in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information.

Integration Services

These services are delivered with the Invoice Integration flow:

• InvoiceSiebelCommsReqABCS with operations QueryInvoiceList, QueryInvoice, QueryEventDetails, SearchEventDetails, and QueryBalanceDetails

• QueryInvoiceListSiebelCommsReqABCSImpl

• QueryInvoiceListBRMCommsProvABCSImpl

• QueryInvoiceSiebelCommsReqABCSImpl

• QueryInvoiceEventDetailsSiebelCommsReqABCSImpl

• SearchInvoiceEventDetailsSiebelCommsReqABCSImpl

• QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl

InvoiceSiebelCommsReqABCS

InvoiceSiebelCommsReqABCS exposes the following operations related to the Invoice integration on the Siebel ABM:

• QueryInvoiceList:

  • Routes QueryInvoiceListReqMsg to the requester implementation service

  • Routes QueryInvoiceListRespMsg to the requester

• QueryInvoice:

  • Routes QueryInvoiceReqMsg to the requester implementation service

  • Routes QueryInvoiceRespMsg to the requester

• QueryEventDetails:

  • Routes QueryEventDetailsReqMsg to the requester implementation service

  • Routes QueryEventDetailsRespMsg to the requester.

• SearchEventDetails:

  • Routes SearchEventDetailsReqMsg to the requester implementation service

  • Routes SearchEventDetailsRespMsg to the requester

• QueryBalanceDetails:

  • Routes QueryBalanceDetailsReqMsg to the requester implementation service

  • Routes QueryBalanceDetailsRespMsg to the requester

• QueryInvoiceListSiebelCommsReqABCSImpl

• QueryInvoiceListSiebelCommsReqABCSImpl transforms the Siebel message into a QueryInvoiceList EBM and calls the provider to query the invoice list response from the billing system. It then transforms the EBM response back to a Siebel message and returns it to the calling Siebel web service.

QueryInvoiceListBRMCommsProvABCSImpl

QueryInvoiceListBRMCommsProvABCSImpl transforms:

• QueryInvoiceListRequestEBM into BRM API input format and calls the API to query the invoice list output from the billing system.

  It then transforms the output from the API back to an Invoice EBM message and returns it to the calling requestor.

• QueryInvoice EBM into BRM API input formats and calls the APIs to Query the Invoice output from the billing system.

  It then transforms the output from the APIs back to an Invoice EBM message and returns it to the calling requestor.

• QueryInvoiceList EBM into BRM API input formats and calls the APIs to Query the Invoice Event Details output from the billing system.

  It then transforms the output from the APIs back to an Invoice EBM message and returns it to the calling requestor.

• Invoice EBM into BRM API input formats and calls the APIs to Query the Resource Impact output from the billing system.

  It then transforms the output from the APIs back to an Invoice EBM message and returns it to the calling requestor.

QueryInvoiceSiebelCommsReqABCSImpl

QueryInvoiceSiebelCommsReqABCSImpl transforms the Siebel message into QueryInvoiceEBM and calls the provider to query the invoice from the billing system. It then transforms the EBM response back to a Siebel message and returns it to the calling Siebel web service.

QueryInvoiceEventDetailsSiebelCommsReqABCSImpl

QueryInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the Siebel message into QueryInvoiceList EBM and calls the provider to query the invoice event details response from the billing system. It then transforms the EBM response back to a Siebel message and returns it to the calling Siebel web service.

SearchInvoiceEventDetailsSiebelCommsReqABCSImpl

SearchInvoiceEventDetailsSiebelCommsReqABCSImpl transforms the Siebel message into QueryInvoiceList EBM and calls the provider to query the Invoice Event Details response from the billing system. It then transforms the EBM response back to a Siebel message and returns it to the calling Siebel web service.

SearchInvoiceCharge supports searching invoice event details (CDR records) on the following columns in addition to the account ID and the item charge ID that are passed to Query Invoice Details:

• Minimum Amount

• Maximum Amount

• Start Date

• End Date

The BRM opcode PCM_OP_ BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT supports only simple queries, so the search supports passing only the data through and not passing complex query criteria (for example: >, <, between, and so on).

QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl

QueryInvoiceBalanceDetailsSiebelCommsReqABCSImpl transforms the Siebel message into an Invoice EBM and calls the provider to query the Resource Impact response from the billing system. It then transforms the EBM response back to a Siebel message and returns it to the calling Siebel web service.