Skip Headers
Oracle® Application Integration Architecture Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide
Release 11.2

Part Number E26496-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

9 Configuring the Process Integration for Billing Management

This chapter discusses how to set up Oracle Billing and Revenue Management (Oracle BRM) and Siebel Customer Relationship Management (Siebel CRM). In addition, it discusses how to work with domain value maps (DVMs) and cross-references, how to handle errors, and how to configure the process integration for billing management.

This chapter includes the following sections:

9.1 Setting Up Oracle BRM

This section describes how to set up Oracle BRM.

To set up Oracle BRM:

9.2 Setting Up Siebel CRM

For some Siebel CRM interfaces, in Siebel, you must set the process property UTCCanonical to Y.

For more information about which Siebel CRM interfaces require you to enable the UTCCanonical process property, see instructions for ACR 474 and ACR 508 in the Siebel Maintenance Release Guide.

Perform the following AQ configuration:

For more information about Siebel side configuration, see Transports and Interfaces: Siebel Enterprise Application Integration v8.1, Process of Configuring JMS Messaging Between Siebel Business Applications and Oracle SOA Suite.

For more information about the corresponding Oracle AIA side configuration, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

9.3 Working with DVMs

Domain value maps (DVMs) are a standard feature of the Oracle service-oriented architecture (SOA) Suite that enable you to equate lookup codes and other static values across applications, for example, FOOT and FT or US and USA.

DVMs are static in nature, though administrators can add maps as required. Transactional business processes never update DVMs-they only read from them. They are stored in XML files and cached in memory at run time.

DVM types are seeded for the Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care flows. Administrators can extend the list of mapped values by adding more maps.

Table 9-1 lists the DVMs for the process integration for billing management.

Table 9-1 Billing Management Integration - DVMs

DVM Description

CURRENCY_CODE

Currency codes.

RESOURCE

Nonmonetary resources (Free Minutes, Text Messages, and so on).

ACCOUNTBALANCEADJUSTMENT_REASON

Reason for adjustment.

ACCOUNTBALANCEADJUSTMENT_STATUS

Status of adjustment request (Posted, Not-Posted).

ACCOUNTBALANCEADJUSTMENT_TYPE

Type of adjustment (Credit, debit, and so on).

ACCOUNTBALANCEADJUSTMENT_TAXTREATMENT

Tax treatment on adjustment amount (Include, Exclude).

ACCOUNTBALANCEADJUSTMENT_ USAGEALLOCATION_TAXTREATMENT

Tax treatment on CDR adjustment amount (Include, Exclude).

INSTALLEDPRODUCT_STATUS

Status of installed product (Active, Canceled, and so on).

RECIEVEDPAYMENT_TYPE

Type of payment (Credit, Direct Debit).

ACCOUNTBALANCEADJUSTMENT_SUBSTATUS

Sub-status of adjustment request.


For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Message Transformations," Working with DVMs and Cross-References.

9.4 Working with Cross-References

Cross-references map and connect the records within the application network, and they enable these applications to communicate in the same language. The integration server stores the relationship in a persistent way so that others can refer to it.

Table 9-2 contains the billing management integration cross-references.

Table 9-2 Billing Management Integration - Cross-References

Name Columns Mapping Details Description

CUSTOMERPARTY_ACCOUNTID

SEBL_01,COMMON,BRM_01

Set up as part of customer sync

Query

CUSTOMERPARTY_BILLPROFILEID

SEBL_01,COMMON,BRM_01

Set up as part of customer sync

Query


9.5 Handling Errors

Based on the roles defined for the services, e-mail notifications are sent if a service ends due to an error.

Table 9-3 lists the error messages provided by the process integration for billing management.

Table 9-3 Billing Management Integration - Error Messages

Integration/Service Name Error Code Message Text

Account Balance / QueryBalanceSummarySiebel ReqABCSImpl

Query Invoice List / QueryInvoiceListSiebelCommsReqABCSImpl

AIA_ERR_AIACOMBMPI_0003

Billing Profile BPName for the account does not exist in the billing system.

1) To correct the error, submit a sales order with this billing profile.

2) Ensure that the sales order created with this billing profile is successfully submitted to the billing system.

Create Payment / CreateReceivedPaymentBRMCommsProvABCSImpl

AIA_ERR_AIACOMBMPI_0005

BRM Error Message (For example, Service Unavailable)


9.5.1 Describing Delivered Error Notification Roles and Users

The following roles and users are delivered as default values for issuing error notifications for the process integration for billing management.

Actor roles and users:

  • Role: AIAIntegrationAdmin

  • User: AIAIntegrationAdminUser

    The default password set for all users is welcome1.

For more information about setting up error notifications using these values, see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack, "Using Error Notifications" and "Using Trace and Error Logs."

9.6 Configuring the Process Integration for Billing Management

Configure these properties in the AIAConfigurationProperties.xml file. The file is located in <AIA_INSTANCES>/config/. Entries in the AIAConfigurationProperties.xml file are case-sensitive.

For more information about reloading updates to AIAConfigurationProperties.xml, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Building AIA Integration Flows."

These Business Process Execution Language (BPEL) processes have entries listed in Table 9-4.

Table 9-4 BPEL Process Property Values - 1

Property Name Value/Default Value Description

ABCSExtension.PreXform<ABM/EBM Name>TO<EBM/ABM Name>

true/false

Default value is false. Controls whether the extension point before transformation of application business message (ABM) to enterprise business message (EBM) is invoked during processing.

ABCSExtension.PreInvoke<PartnerLinkName>

true/false

Default value is false. Controls whether the extension point before invocation to enterprise business service (EBS) is invoked during processing.

ABCSExtension.PostXform<EBM/ABM Name>to<ABM/EBM Name>

true/false

Default value is false. Controls whether the extension point before transformation of EBM to ABM is invoked during processing.

ABCSExtension.PostInvoke<PartnerLinkName>

true/false

Default value is false. Controls whether the extension point before invocation of callback service or response return is invoked during processing.

Routing.<Partnerlinkname>.RouteToCAVS

true/false

Default value is false. Controls whether the Composite Application Validation System (CAVS) is used to handle the request.

Default.SystemID

Valid string

Specifies the name of the default systemID of the requester application.

Routing.partnerlinkname.BRM_01.EnpointURI

eis/BRM

Specifies the JNDI entry for the partner link.

EBSOverride.<EBS Name>.<operationname>.PortType

Valid string

PortType of the webservice that needs to be invoked dynamically. This value should be in consistent w.r.t to the Address property mentioned below.

EBSOverride.<EBS Name>.<operationname>.ServiceName

Valid string

ServiceName of the webservice that needs to be invoked dynamically. This value should be in consistent w.r.t to the Address property mentioned below.

EBSOverride.<EBS Name>.<operationname>.Address

Valid string

This property is used to dynamically invoke any webservice from this service. This holds the address.endpoint URI of the webservice that needs to be invoked dynamically. To invoke CAVS or any other provider ABCS, this property needs to be updated accordingly.

BRM.Payment.Command

0

This property is specific to CreateReceivedPaymentBRMCommsProvABCSImpl.

Routing.CreateAccountBalanceAdjustmentListResponseBRMCommsJMSProducer.EndpointURI

Valid string

Endpoint URL of the CreateAccountBalanceAdjustmentListResponseBRMCommsJMSProducer. (This property is specific to CreateAccountBalanceAdjustmentBRMCommsProvABCSImpl.


These BPEL processes have entries listed in Table 9-5.

Table 9-5 BPEL Processes Property Values - 2

Property Name Value/Default Value Description

ABCSExtension.PreXform<ABM/EBM Name>TO<EBM/ABM Name>

true/false

Default value is false. Controls whether the extension point before transformation of ABM to EBM is invoked during processing.

ABCSExtension.PreInvoke<PartnerLinkName>

true/false

Default value is false. Controls whether the extension point before invocation to enterprise business service (EBS) is invoked during processing.

Routing.<Partnerlinkname>.RouteToCAVS

true/false

Default value is false. Controls whether the CAVS is used to handle the request

Default.SystemID

Valid string

Specifies the name of the default systemID of the requester application

EBSOverride.<EBS Name>.<operationname>.PortType

Valid string

PortType of the webservice that needs to be invoked dynamically. This value should be in consistent w.r.t to the Address property mentioned below.

EBSOverride.<EBS Name>.<operationname>.ServiceName

Valid string

ServiceName of the webservice that needs to be invoked dynamically. This value should be in consistent w.r.t to the Address property mentioned below.

EBSOverride.<EBS Name>.<operationname>.Address

Valid string

This property is used to dynamically invoke any webservice from this service. This holds the address.endpoint URI of the webservice that needs to be invoked dynamically. To invoke CAVS or any other provider ABCS, this property needs to be updated accordingly.

Routing.SWIAdjustmentStatusUpdate.SEBL_01.EndpointURI

Valid string

Siebel endpoint URIL. (This property is specific to UpdateAccountBalanceAdjustmentRespSiebelCommsProvABCSImpl.)