6 Configuring the Order to Cash Business Process

This chapter describes how to configure the Order to Cash business process.

Configuring Order Lifecycle Management

This section describes how to configure order lifecycle management in Order to Cash business process.

About Configuring Order Lifecycle Management

This chapter assumes that you have already installed Oracle Communications Billing and Revenue Management (BRM), Siebel CRM, and Oracle AIA and performed any Oracle AIA post-installation tasks described in Oracle Application Integration Architecture Cloud Native Deployment Guide.

See the Oracle AIA software compatibility matrix available from My Oracle Support for information about required versions and patches.

In addition to basic setup, configuring order lifecycle management includes:

• Working with domain value maps (DVMs) and cross-references.

• Handling error notifications.

• Setting Oracle AIA configuration properties.

Working with Domain Value Maps (DVMs) for Order Lifecycle Management

DVMs are a standard feature of the Oracle SOA Suite and 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 order management flows, and administrators can extend the list of mapped values by adding more maps.

Note:

The DVM names in the following table have an underscore. If you open the file in FTP mode, the underscore is replaced with 95.

Table 6-1 lists the DVMs for the process integration for order lifecycle management.

Table 6-1 Order Lifecycle Management DVMs

DVM	Description
SALESORDER_DYNAMICPRICEIND	Dynamic Pricing Indicator
SALESORDER_FULFILLCOMPOSITIONTYPE	Fulfillment Composition Type Code
SALESORDER_FULFILLMENTMODECODE	Fulfillment Mode Code
SALESORDER_LINEFULFILLMENTMODECODE	Line Fulfillment Mode Code
SALESORDER_NETWORKINDICATOR	Network Indicator
SALESORDER_PARTIALFULFILLALLOWEDIND	Partial Fulfillment Mode Indicator
SALESORDER_PRIORITY	Order Priority
SALESORDER_PROCESSINGTYPECODE	Processing Type Code
ITEM_TYPE	Product/Item Type Code
SALESORDER_REVISIONPERMISIBLECODE	Revision Permissible Code
SALESORDER_SERVICEINDICATOR.	Service Indicator
SALESORDER_STRTBILLSERVICEUSAGE	Start Billing Service Usage
SALESORDER_STATUS	Status
SALESORDER_TYPECODE	Type Code
STATE	State
PROVINCE	Province
ADDRESS_COUNTRYID	Country Code
CUSTOMERPARTY_TYPECODE	Account Type Code
ITEM_BILLINGTYPECODE	Billing Type Code. Examples values include Subscription, Discount, Item, and Sponsorship.
SALESORDER_CHANGEDIND	Order Changed Indicator. Values are True or False. Used to validate the OrderChangedIndicator attribute. For example, The order management system can set this attribute to True if, as part of fulfillment, the order changes significantly such that Siebel CRM must make a copy of the customer order to preserve the customer intent before updating the working version of the order.
SALESORDER_ACTIONCODE	Sales Order Line Action Code
SALESORDER_REVISIONPERMISIBLECODE	Revision Permissible Code
SALESORDER_LINESTATUS	Order Line Status
DISCOUNT_METHODCODE	Discount Method Code
CURRENCY_CODE	Currency Code
PRICE_TYPE	Price Type
PRICELIST	Maps price list Row IDs from Siebel CRM to logical common price list names for BRM and Oracle Product Hub. Used to communicate price lists from order lines for products synchronized from BRM using a rate plan selector. See Working with the PRICELIST DVM for details.

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about working with DVMs.

Working with the PRICELIST DVM

You must update the PRICELIST DVM before submitting any orders so that the integration can map Siebel CRM price lists to BRM rate plans. You can migrate the PRICELIST DVM information between environments.

Updating the PRICELIST DVM

To update the PRICELIST DVM:

1. Log in to Oracle SOA Composer and open PRICELIST.dvm.

   For information about using Oracle SOA Composer with DVMs, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

2. Replace the placeholder domain values for the first row in PRICELIST.dvm as follows:

   • For SEBL_01, enter the Siebel CRM price list row ID for one of the price lists you created in Siebel CRM before synchronizing the products to BRM. You can find price list row IDs using a query in Siebel CRM.

   • For COMMON and BRM_01, enter the logical name of the price list that corresponds to the Siebel CRM price list.

3. Add and fill in new rows for all additional price lists that you created in Siebel CRM with the exception of the default price list that you entered into the AIAConfigurationProperties.xml file. For more information about configuring Siebel CRM for integrated product lifecycle management, see Oracle AIA Oracle Communications Order to Cash Integration Pack Implementation Guide

4. Save and commit the changes.

Migrating PRICELIST DVM Between Environments

To migrate the PRICELIST DVM between environments:

1. In the source environment, in Siebel CRM, open the S_PR_LST table.

2. Search in the ROW_ID column for the price list row IDs listed in the SEBL_01 column in PRICELIST.dvm.

3. Copy the values in the NAME, SUBTYPE_CD, and BU_ID columns for each row ID to a text editor and close the table.

4. In the target environment, in Siebel CRM, open the S_PR_LST table.

5. Search the ROW_ID column for the price list row IDs listed in the source environment's S_PR_LST table and PRICELIST.dvm.

6. Enter the values copied to the text editor in the NAME, SUBTYPE_CD, and BU_ID columns.

7. Using Oracle SOA Composer, open PRICELIST.dvm.

8. In the SEBL_01 column, add the row IDs copied to the text editor. Fill out the COMMON and BRM_01 columns as described in Updating the PRICELIST DVM.

9. Save and commit the changes in both files.

Working with Cross-References for Order Lifecycle Management

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 6-2 lists the order lifecycle management cross-references.

Table 6-2 Order Lifecycle Management Cross-References

Cross-Reference Table Name	COMMON	SEBL_01	BRM_01	Description
SALESORDER_ID	SalesOrderIdentification	Id	N/A	The Siebel CRM Sales Order ID is cross-referenced.
SALESORDER_LINEID	SalesOrderLine/Identification	OrderItem/OrderId	N/A	The Siebel CRM OrderItem/OrderId is mapped to the SalesOrderLine Identification in the EBM.
INSTALLED PRODUCT_ID	InstalledProductIdentification	AssetIntegrationId	Product, service, or discount OBJ, or sharing group POID	The Siebel CRM Asset Integration ID is mapped to the product/service/discount OBJ or sharing group POID of the BRM object.
ITEM_ITEMID	ItemIdentification	ProductId	Product or discount POID	The Siebel CRM Product ID is mapped to the product/discount POID of the BRM object.
CUSTOMERPARTY_ACCOUNTID	CustomerPartyAccountIdentification	AccountId	Account POID	The Siebel CRM Customer ID is mapped to the BRM Account POID.
CUSTOMERPARTY_CONTACTID	CustomerPartyAccountContactIdentification	ContactId	Contact POID	The Siebel CRM Contact ID is mapped to the BRM Contact POID.
CUSTOMERPARTY_DEFAULTBALANCEGROUPID (Populated only when service-level balance groups are enabled)	InstalledProductIdentification (Populated from INSTALLEDPRODUCT_ID)	AssetIntegrationID	Balance group POID	The balance group POID for each service bundle or simple service bundle is mapped to the InstalledProductIdentification for the product and to the Siebel CRM AssetIntegrationID sent on the order line. For nested service bundles, the integration populates only the values for the parent service bundle. To track the parent of a nested service bundle, the integration populates the BalanceBundleIdentification field in the order EBM with the common InstalledProductIdentification value of the parent service bundle.
CUSTOMERPARTY_DEFAULTBALANCEGROUPID (Entry for default account-level balance group)	CustomerPartyAccountIdentification	ServiceAccountId/BillingAccountId	Balance group POID	The default balance group POID is mapped to the common ID of the account.
CUSTOMERPARTY_PAYPROFILEID	PaymentProfileIdentification	BillingProfileId	/payinfo POID	The billing profile ID is mapped to the pay info POID from BRM.
CUSTOMERPARTY_BILLPROFILEID	BillingProfileIdentification	BillingProfileId	/billinfo POID	The billing profile ID is mapped to the bill info POID from BRM.
CUSTOMERPARTY_ADDRESSID	CustomerPartyAccountAddressIdentification	AddressId	Address POID	The address ID is mapped to the BRM Contact POID.
PROMOTIONGROUP_MEMBER_ID	The common ID of a promotion group (Populated from INSTALLEDPRODUCT_ID) combined with the common ID of a BRM bundled promotion POID.	Promotion group RowId	BRM bundled promotion POID	The Siebel CRM RowId for a promotion group is mapped to the POID of a bundled promotion (but not the components of the bundled promotion). The integration uses this XREF to determine if a bundled promotion is associated with a promotion group membership. A bundled promotion can be associated with multiple promotion group memberships. In this case, the BRM value is included only for the first promotion group membership. A promotion group membership can be associated with multiple bundled promotions. In this case, the BRM value is included for each bundled promotion.
COMMUNITYOFFER_ID	Bundled promotion common ID	Bundled promotion RowId	POID of the discount sharing group	The Siebel CRM RowId for a bundled promotion that includes a discount with the Community Offer attribute enabled is mapped to the POID of the corresponding discount sharing group.
COLLECTION_GROUP_OWNER_ID	Common ID of the owner billing profile	N/A	POID of the owner /billinfo	The common ID of the billing profile for the owner account on the sales order is mapped to the corresponding /billinfo POID. When creating new collections sharing groups, the integration checks if the owner account's /billinfo POID already exists in this table. If so, the member is added to the existing group.
COLLECTION_GROUP_MEMBER_ID	Common ID of the member billing profile	N/A	POID of the member /billinfo	The common ID of the billing profile for the member account on the sales order is mapped to the corresponding /billinfo POID.

Handling Error Notifications for Order Lifecycle Management

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

Order Fallout Management can generate trouble tickets for failed orders.

See About Order Fallout Management for more information about order fallout.

Table 6-3 lists the error messages that are issued when order billing integration is called in billing initiation mode.

Table 6-3 Error Messages for Order Lifecycle Management

Error Code	Error Text	Description
AIA_ERR_AIACOMOMPI_0001	Date Validation Failed: Either a Purchase Date/Cycle Start Date/ Usage Start Date should be set to the future.	In Billing Initiation mode, the ProcessFulfillmentOrderBillingBRMComms AddSubProcess ends in an error when at least one billing date (purchase, cycle start, usage start date) is not set to the future for lines with products of type Subscription or Discount.
AIA_ERR_AIACOMOMPI_0002	Date Validation Failed: Purchase Date should be set to the future.	In Billing Initiation mode, the ProcessFulfillmentOrderBillingBRMComms AddSubProcess ends in an error when the purchase date is not set to the future for lines with products of type Item.
AIA_ERR_AIACOMOMPI_0003	Purchased promotion instance does not exist for a promotion that was previously purchased. A data upgrade script was not run.	ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl ends in an error if a change order is processed for data that was created using AIA for Communications 2.0/2.0.1 and the custom upgrade script was not run to create the necessary cross-reference and purchased promotion instances in BRM.
AIA_ERR_AIACOMOMPI_0004	Promotion referenced on Sales Order &OrderNum, Line &LineNum for &Product has not been interfaced to billing. The promotion must be interfaced to billing, before interfacing the order line that references it.	ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl ends in an error if service bundle/account-level product with promotion reference is sent to billing before the corresponding promotion line.

For more information about the errors caused by Siebel CRM or BRM, see the Siebel CRM and BRM documentation.

See Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack for more information about AIA error handling.

About Error Notification Roles and Users

The integration uses the following default roles and users to issue error notifications:

• Role: AIAIntegrationAdmin

• User: AIAIntegrationAdminUser

See the discussion of configuring Oracle AIA processes for error handling and trace logging in Oracle Fusion Middleware Developer's Guide for Oracle SOA Core Extension for more information about configuring error notifications.

Configuring Order Lifecycle Management

This section provides instructions for setting the Oracle AIA configuration properties and setting the BRM version number for backward compatibility.

Setting Oracle AIA Configuration Properties

Configure the properties described in this section in the COMMS_AIA_HOME/source/soainfra/apps/AIAMetaData/config/AIAConfigurationProperties.xml file.

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about working with AIAConfigurationProperties.xml.

Note:

Entries in the AIAConfigurationProperties.xml file are case sensitive.

System-Level Configuration Properties

Table 6-4 shows the system-level configuration properties for order lifecycle management.

Table 6-4 System Configuration Properties for Order Lifecycle Management

Property Name	Value/Default Values	Description
O2C.AccountLevelBalanceGroup	TRUE/FALSE Default value: FALSE	A value of FALSE enables service-level balance groups. A value of TRUE disables service-level balance groups and tracks all services in one account-level balance group in BRM.

Configuration Properties for Siebel CRM Services

Table 6-5 shows the properties for the UpdateSalesOrderSiebelCommsProvABCSImpl service.

Table 6-5 UpdateSalesOrderSiebelCommsProvABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	SEBL_01	URL for Siebel CRM Instance web service for "Order spcLine spcItem spcUpdate spc- _spcComplex" web service.
Routing.SWI_spcOrder_spcUpsert.RouteToCAVS	true/false. Default = false.	Controls whether UpdateSalesOrderSiebelCommsProvABCSImpl routes messages to the CAVS or to the Siebel CRM system.
Routing.SWI_spcOrder_spcUpsert.SEBL_01.EndpointURI	Target Endpoint URL for the Siebel CRM upsert web service. example: http://${siebel.http.host}:${siebel.http.port}/eai_enu/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1Status OpenFixedClosed	Target Endpoint URL for the Siebel CRM upsert web service.
ABCSExtension.PreXformEBMtoABM	true/false. Default = false.	Whether there is any extension in the ABCS before transformation of EBM to ABM.
ABCSExtension.PreInvokeABS	true/false. Default = false.	Indicates whether there is any extension in the ABCS before invoking application business service.

Table 6-6 shows the properties for the ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl service.

Table 6-6 ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	Possible value: A Siebel CRM system instance code. Default value: SEBL_01	Default Siebel CRM system instance code (defined in BSR). This is used only if the Siebel CRM Order message does not contain the EnterpriseServerName.
ABCSExtension.PreXformABMtoEBM	Possible values: true or false Default value: false	Indicates whether there is any extension in the ABCS before transformation of EBM to ABM.
ABCSExtension.PostXformABMtoEBM	true/false. Default = false	Indicates whether there is any extension in the ABCS after transformation of EBM to ABM.
ABCSExtension.PreInvokeEBS	Possible values: true or false Default value: false	Indicates whether there is any extension in the ABCS before invoking application business service.
ABCSExtension.PostInvokeEBS	Possible values: true or false Default value: false	Indicates whether there is any extension in the ABCS after invoking application business service.
EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.Address	Possible value: address of web service that must be invoked. Default value: http://<soa_server>:<soa port>/soa-infra/services/default/ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer/client	This property is used to dynamically invoke any web service from this service. This holds the address of the web service that must be invoked dynamically. To invoke CAVS/EBS or any other web service this property must be updated accordingly.
EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.PortType	Possible value: PortType of the web service that must be invoked. Default value: ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer	This value should be in consistent with EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.Address.
EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.ServiceName	Possible value: ServiceName of the web service that must be invoked. Default value: http://xmlns.oracle.com/ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer}ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer	This value should be in consistent with EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.Address.

Configuration Properties for BRM Services

Table 6-7 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsAddSubProcess service.

Table 6-7 ProcessFulfillmentOrderBillingBRMCommsAddSubProcess Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used only if the request message does not contain the target information.
BRM_01.FutureTimeThresholdForBillingDates	8640	This property is used for future date validation in Billing Initiation. It is set to a default value of 8640 hours (360 days). This property is billing-instance-specific and must be set for any instance that the order must be sent for billing integration. See Using Single-Phase Billing or Two-Phase Billing for more information on how this property is used.
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PostprocessAddPCM_OP_SUBSSCRIPTION_PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL.
ABCSExtension.PostProcessA ddPCM_OP_ SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL.
ABCSExtension.PreProcessAd dPCM_OP_CUST_MODIFY_ CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_CUST_MODIFY_CUSTOMER.
ABCSExtension.PostProcessA ddPCM_OP_CUST_ MODIFY_CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_CUST_MODIFY_CUSTOMER.

Table 6-8 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess service.

Table 6-8 ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used only if the request message does not contain the target information.
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PreProcessPCM_ OP_SUBSCRIPTION_CANCEL_ DISCOUNTABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_SUBSCRIPTION_CANCEL_ DISCOUNT.
ABCSExtention.PostprocessPCM _OP_SUBSCRIPTION_CANCEL_ DISCOUNTABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_SUBSCRIPTION_CANCEL_ DISCOUNT.
ABCSExtension.PreProcessPCM_ OP_SUBSCRIPTION_CANCEL_ PRODUCTABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_SUBSCRIPTION_CANCEL_ PRODUCT.
ABCSExtention.PostProcessPCM _OP_SUBSCRIPTION_CANCEL_ PRODUCTABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_SUBSCRIPTION_CANCEL_ PRODUCT.
ABCSExtension.PreProcessPCM_ OP_CUST_SET_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_CUST_SET_STATUS.
ABCSExtension.PostProcessPCM _OP_CUST_SET_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_CUST_SET_STATUS.
ABCSExtension.PreProcessPCM_ OP_SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_SUBSCRIPTION_ PURCHASE_DEAL.
ABCSExtension.PostProcessPCM _OP_SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_SUBSCRIPTION_ PURCHASE_DEAL.

Table 6-9 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess service.

Table 6-9 ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used only if the request message does not contain the target information.
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PreProcessMoveAddPCM_OP_ SUBSCRIPTION_PURCHASE_ DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL.
ABCSExtension.PostProcessMoveAddPCM_OP_ SUBSCRIPTION_PURCHASE_ DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL.

Table 6-10 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl service.

Table 6-10 ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used only if the request message does not contain the target information.
Routing.BRMSUBSCRIPTIONService.RouteToCAVS	true/false. Default = false	CAVS simulator to be enabled or disabled for this partner link.
Routing.BRMSUBSCRIPTIONService.BRM_01.EndpointURI	End point for BRM Adapter. Example: eis/BRM	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMSUBSCRIPTIONService.BRM_02.EndpointURI	End point for BRM Adapter. Example: eis/BRM2	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMSUBSCRIPTIONService.BRM_03.EndpointURI	End point for BRM Adapter. Example: eis/BRM3	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMCUSTService.RouteToCAVS	true/false. Default = false	CAVS simulator to be enabled or disabled for this partner link.
Routing.BRMCUSTService.BRM_01.EndpointURI	End point for BRM Adapter. Example: eis/BRM	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMCUSTService.BRM_02.EndpointURI	End point for BRM Adapter. Example: eis/BRM2	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMCUSTService.BRM_03.EndpointURI	End point for BRM Adapter. Example: eis/BRM3	End point for BRM Adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMBALService.RouteToCAVS	true/false. Default = false	CAVS simulator to be enabled or disabled for this partner link.
Routing.BRMBALService_ptt.BRM_01.EndpointURI	End point for BRM Adapter. Example: eis/BRM	End point for BRM adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMBALService_ptt.BRM_02.EndpointURI	End point for BRM Adapter. Example: eis/BRM2	End point for BRM adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMBALService_ptt.BRM_03.EndpointURI	End point for BRM Adapter. Example: eis/BRM3	End point for BRM adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMARService.RouteToCAVS	true/false. Default = false	CAVS simulator to be enabled or disabled for this partner link.
Routing.BRMARService.BRM_01.EndpointURI	End point for BRM Adapter. Example: eis/BRM	End point for BRM adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
Routing.BRMBASEService.RouteToCAVS	true/false. Default = false	CAVS simulator to be enabled or disabled for this partner link.
Routing.BRMBASEService.BRM_01.EndpointURI	End point for BRM Adapter. Example: eis/BRM	End point for BRM adapter. Example: Update with CAVS endpoint URL to route to CAVS along with changing the above property to "true"
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PreProcessPCM_OP_CUST_CREATE_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_CUST_CREATE_PROFILE.
ABCSExtension.PostProcessPCM_OP_CUST_CREATE_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_CUST_CREATE_PROFILE.
ABCSExtension.PreProcessPCM_OP_CUST_MODIFY_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_CUST_MODIFY_PROFILE.
ABCSExtension.PostProcessPCM_OP_CUST_MODIFY_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_CUST_MODIFY_PROFILE.
ABCSExtension.PreProcessPCM_OP_CUST_DELETE_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_OP_CUST_DELETE_PROFILE.
ABCSExtension.PostProcessPCM_OP_CUST_DELETE_PROFILEABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_OP_CUST_DELETE_PROFILE.
ABCSExtension.PreProcessPCM_OP_SUBSCRIPTION_SET_BUNDLEABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_BUNDLEABM.
ABCSExtension.PostProcessPCM_OP_SUBSCRIPTION_SET_BUNDLEABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_BUNDLEABM.
EBSOverride.CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingResponse.Address	Address of the web service that must be invoked. Example (Default): {http://host:port/soa-infra/services/default/ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer/client	This property is used to dynamically invoke any web service from this service. This holds the Address of the web service that must be invoked dynamically. To invoke CAVS/EBS or any other web service this property must be updated accordingly.
EBSOverride.CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingResponse.PortType	PortType of the web service that must be invoked. Example (Default): ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer	This property is used to dynamically invoke any web service from this service. This holds the PortType of the web service that must be invoked dynamically. To invoke CAVS/EBS or any other web service this property must be updated accordingly.
EBSOverride.CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingResponse.ServiceName	ServiceName of the web service that must be invoked. Example (Default): {http://xmlns.oracle.com/ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer}ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer	This property is used to dynamically invoke any web service from this service. This holds the ServiceName of the web service that must be invoked dynamically. To invoke CAVS/EBS or any other web service this property must be updated accordingly.

Table 6-11 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess service.

Table 6-11 ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used if the request message does not contain the target information.
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PreProcessResumePCM_OP_CUST_SET_ STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_CUST_SET_STATUS for resume scenario.
ABCSExtension.PostProcessResumePCM_OP_CUST_SET_ STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_CUST_SET_STATUS for resume scenario.
ABCSExtension.PreProcessSuspendPCM_OP_CUST_SET_ STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_CUST_SET_STATUS for suspend scenario.
ABCSExtension.PostProcessSuspendPCM_OP_CUST_SET_ STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_CUST_SET_STATUS for suspend scenario.
ABCSExtension.PreProcessResumePCM_OP_SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL for resume scenario.
ABCSExtension.PostProcessResumePCM_OP_SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL for resume scenario.
ABCSExtension.PreProcessSuspendPCM_OP_SUBSCRIPTION_ PURCHASE_DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL for suspend scenario.
ABCSExtension.PostProcessSuspendPCM_OP_ SUBSCRIPTION_PURCHASE_ DEALABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_PURCHASE_DEAL for suspend scenario.
ABCSExtension.PreProcessPCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_DISCOUNT_ STATUS.
ABCSExtension.PostProcessPC M_OP_SUBSCRIPTION_SET_ DISCOUNT_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_DISCOUNT_ STATUS.
ABCSExtension.PreProcessPCM _OP_SUBSCRIPTION_SET_ PRODUCT_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension before calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_PRODUCT_ STATUS.
ABCSExtension.PostProcessPC M_OP_SUBSCRIPTION_SET_ PRODUCT_STATUSABM	true/false. Default = false	To indicate whether the ABCS has any extension after calling BRM opcode PCM_ OP_SUBSCRIPTION_SET_PRODUCT_ STATUS.

Table 6-12 shows the properties for the ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess service.

Table 6-12 ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess Properties

Property Name	Value/Default Values	Description
Default.SystemID	BRM_01	Default target billing system instance code (defined in BSR). This is used if the request message does not contain the target information.
ABCSExtension.PreInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension before transformation of EBM to ABM.
ABCSExtension.PostInvokeEBM	true/false. Default = false	To indicate whether the ABCS has any extension after transformation of EBM to ABM.
ABCSExtension.PreProcessUpdate1PCM_OP_SEARCHABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the first BRM opcode call PCM_OP_SEARCH.
ABCSExtension.PostProcessUpdate1PCM_OP_SEARCHABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the first BRM opcode call PCM_OP_SEARCH.
ABCSExtension.PreProcessUpdate2PCM_OP_SEARCHABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the second BRM opcode call PCM_OP_SEARCH.
ABCSExtension.PostProcessUpdate2PCM_OP_SEARCHABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the second BRM opcode call PCM_OP_SEARCH.
ABCSExtension.PreProcessUpdate1PCM_OP_CUST_MODIFY_ CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the first BRM opcode call PCM_OP_CUST_MODIFY_ CUSTOMER.
ABCSExtension.PostProcessUpdate1PCM_OP_CUST_ MODIFY_CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the first BRM opcode call PCM_OP_CUST_MODIFY_ CUSTOMER.
ABCSExtension.PreProcessUpdate2PCM_OP_CUST_MODIFY_ CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the second BRM opcode call PCM_OP_CUST_MODIFY_ CUSTOMER.
ABCSExtension.PostProcessUpdate2PCM_OP_CUST_ MODIFY_CUSTOMERABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the second BRM opcode call PCM_OP_CUST_MODIFY_ CUSTOMER.
ABCSExtension.PreProcessPCM _OP_SUBSCRIPTION_ TRANSFER_ SUBSCRIPTIONABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the BRM opcode call PCM_OP_SUBSCRIPTION_ TRANSFER_SUBSCRIPTION.
ABCSExtension.PostProcessPCM_OP_SUBSCRIPTION_ TRANSFER_ SUBSCRIPTIONABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the BRM opcode call PCM_OP_SUBSCRIPTION_ TRANSFER_SUBSCRIPTION.
ABCSExtension.PreProcessPCM _OP_CUST_UPDATE_ SERVICESABM	true/false. Default = false	To indicate whether the ABCS has any extension before making the BRM opcode call PCM_OP_CUST_UPDATE_SERVICE.
ABCSExtension.PostProcessPCM_OP_CUST_UPDATE_ SERVICESABM	true/false. Default = false	To indicate whether the ABCS has any extension after making the BRM opcode call PCM_OP_CUST_UPDATE_SERVICE.

Setting the BRM Version Number for Backward Price List Compatibility

When sending order data to BRM, Oracle AIA checks the BRM version number in the Oracle AIA system configuration property. Oracle AIA sends order line price list information to BRM versions 7.5 and later. For earlier versions of BRM, Oracle AIA does not send the order line price list information.

To support the behavior for earlier versions of BRM, you must change the version number in the AIA system configuration property.

To change the BRM version number:

1. Browse to your AIA Home Page. For example:

   http://host:port/AIA
   

2. In the Setup area, click Go.

3. Select the Systems tab.

4. In the Version column of the BRM row, enter your BRM version number.

5. Save your changes.

Configuring Customer Management

This section describes how to configure customer management in the Order to Cash business process.

About Configuring Customer Management

Configuring customer management includes:

• Working with domain value maps (DVMs) and cross-references.

• Handling error notifications.

• Setting Oracle AIA configuration properties.

This section assumes that you have already installed Oracle Communications Billing and Revenue Management (BRM) and Siebel CRM. See Oracle Application Integration Architecture Compatibility Matrix for information about required versions and patches.

Working with Domain Value Maps for Customer Management

DVMs are a standard feature of the Oracle 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 customer management flows, and administrators can extend the list of mapped values by adding more maps.

Table 6-13 lists the DVMs for the process integration for customer management.

Table 6-13 Customer Management DVMs

DVM	Columns	Description
CUSTOMERPARTY_ACCOUNTTYPECODE.dvm	SEBL_01, COMMON, BRM_01	Used to get the type of the account, such as Business or Residential.
PROVINCE.dvm	SEBL_01, COMMON, BRM_01	Province name.
STATE.dvm	SEBL_01, COMMON, BRM_01	State name.
ADDRESS_COUNTRYID.dvm	SEBL_01, COMMON, BRM_01	Country codes.
ADDRESS_COUNTRYSUBDIVID.dvm	SEBL_01, COMMON, BRM_01	State codes.
CONTACT_SALUTATION.dvm	SEBL_01, COMMON, BRM_01	Salutation (such Mr., Mrs.). In BRM, Salutation is not a language-independent code. If BRM requires salutations in a language other than English, then you must update the DVM with the appropriate BRM values.
CURRENCY_CODE.dvm	SEBL_01, COMMON, BRM_01	Currency codes.
CUSTOMERPARTY_BILLPROFILE_BILLTYPECODE.dvm	SEBL_01, COMMON, BRM_01	Bill type (summary and detailed).
CUSTOMERPARTY_BILLPROFILE_FREQUENCYCODE.dvm	SEBL_01, COMMON, BRM_01	Billing frequency (monthly, yearly, quarterly, and so on).
CUSTOMERPARTY_PAYPROFILE_BANKACCOUNTTYPE.dvm	SEBL_01, COMMON, BRM_01	Bank account type (checking, savings, and so on).
CUSTOMERPARTY_PAY PROFILE CREDIT_CARDTYPE.dvm	SEBL_01, COMMON	Credit Card type (Visa, Mastercard, and so on).
CUSTOMERPARTY_PAYPROFILE_DELIVERYPREF.dvm	COMMON, BRM_01	Bill media/delivery preference (Email or Mail).
CUSTOMERPARTY_PAYPROFILE_PAYMETHODCODE.dvm	SEBL_01, COMMON, BRM_01	Payment profile payment method types (credit card, direct debit, and invoice/bill me).
CUSTOMERPARTY_PAYPROFILE_PAYTERMCODE.dvm	COMMON, BRM_01	Payment term codes.
CUSTOMERPARTY_STATUSCODE.dvm	SEBL_01, COMMON, BRM_01	Account status codes.
PHONENUMBER_TYPE.dvm	SEBL_01, COMMON, BRM_01	Phone number type codes (home, work, mobile, fax, and so on).

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about working with DVMs.

Working with Cross-References for Customer Management

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 6-14 lists the customer management cross-references.

Table 6-14 Customer Management Cross-References

Cross-Reference Table Name	COMMON	SEBL_01	BRM_01
CUSTOMERPARTY_ACCOUNTID	Common GUID (generated by Oracle AIA)	Account ID	Account POID
CUSTOMERPARTY_BILLPROFILEID	Bill Profile ID	Bill Profile ID	Bill-info POID
CUSTOMERPARTY_PAYPROFILEID	Payment Profile ID	Bill Profile ID	Pay-info POID
CUSTOMERPARTY_ADDRESSID	Address ID	Address ID	Account POID (if this is the billing address) Pay-info POID (if this is the pay-info address)
CUSTOMERPARTY_CONTACTID	Contact ID	Contact ID	Account POID (if this is the main contact) Pay-info POID (if this is the pay-info contact)
CUSTOMERPARTY_DEFAULTBALANCEGROUPID	Account ID	Not applicable	Balance Group POID
CUSTOMERPARTY_PARTYID	Customer Party ID	Customer Party ID	Not applicable
CUSTOMERPARTY_PARTYLOCATIONID.xref	Customer Party Location ID	Customer Party Location ID	Not applicable
CUSTOMERPARTY_LOCATIONREFID	Customer Party Location Reference ID	Customer Party Location Reference ID	Not applicable
CUSTOMERPARTY_ACCOUNT_PHONECOMMID	Customer Account's phone number	Customer Account's phone number	Not applicable
CUSTOMERPARTY_ACCOUNT_FAXCOMMID	Customer Account's fax number	Customer Account's fax number	Not applicable
CUSTOMERPARTY_ACCOUNT_WEBCOMMID	Customer Account's email address	Customer Account's email address	Not applicable
CUSTOMERPARTY_CONTACT_PHONECOMMID	Customer Contact's phone number	Customer Contact's phone number	Not applicable
CUSTOMERPARTY_CONTACT_FAXCOMMID	Customer Contact's fax number	Customer Contact's fax number	Not applicable
CUSTOMERPARTY_CONTACT_EMAILCOMMID	Customer Contact's email address	Customer Contact's email address	Not applicable

Handling Error Notifications

Based on the roles defined for the services, email notifications are sent if a service ends due to an error. Table 6-15 lists the errors that are caused by the process integration for customer management services.

Table 6-15 Errors Caused by Customer Management Services

Service Name	Error Code	Possible Cause
SyncCustomerPartyListBRMCommsProvABCSImpl	AIA_ERR_AIACOMCMPI_0004	Subordinate account cannot have multiple parent accounts.
SyncCustomerPartyListBRMCommsProvABCSImpl	AIA_ERR_AIACOMCMPI_0005	Ambiguous subordinate bill profile update: Multiple distinct Pay-From-Party billing profile references are associated with a single Prior Pay-From-Party billing profile reference.
SyncCustomerPartyListBRMCommsProvABCSImpl	AIA_ERR_AIACOMCMPI_0006	None of the existing subordinate bill profiles are included in the move account request.
CommsProcessBillingAccountListEBF	AIA_ERR_AIACOMCMPI_0001	EBMHeader/Sender/ID is required.
CommsProcessBillingAccountListEBF	AIA_ERR_AIACOMCMPI_0002	EBMHeader/Target/ID is required.
CommsProcessBillingAccountListEBF	AIA_ERR_AIACOMCMPI_0003	Account sequence error: Pay-From accounts and billing profiles must appear before dependent and subordinate accounts and billing profiles.

About Error Notification Roles and Users

The integration uses the following default roles and users to issue error notifications:

• Role: AIAIntegrationAdmin

• User: AIAIntegrationAdminUser

See Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack for more information about setting up error notifications.

Order Fallout Management

When an order is submitted from Siebel CRM, the order may fail while customer-related information is being interfaced to BRM. In that case, a trouble ticket is generated by the Order Fallout flow. The trouble ticket generated is displayed in Siebel CRM. This helps the Customer Service Representative (CSR) in getting notified about any error while processing the order without checking the instances in the Business Process Execution Language (BPEL) Console.

Whenever an error occurs during customer synchronization, it is propagated to the CommsProcessFulfillmentOrderBillingAccountListEBF. This enterprise business flow (EBF) generates an error notification in the error topic (similar to any other Oracle AIA process). From the error topic, the order fallout flow is triggered only for the CommsProcessFulfillmentOrderBillingAccountListEBF (among all the processes in customer management process integration), thereby generating one trouble ticket for any error.

See About Order Fallout Management for more information about order fallout.

Configuring the Process Integration for Customer Management

Configure the properties described in this section in the Comms_home/source/soainfra/apps/AIAMetaData/config/AIAConfigurationProperties.xml file.

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about working with AIAConfigurationProperties.xml.

Note:

Entries in the AIAConfigurationProperties.xml file are case sensitive.

System-Level Configuration Properties

Table 6-16 shows the system-level properties for the process integration for customer management.

Table 6-16 Customer Management System-level Properties

Property Name	Value/Default Value	Description
O2C.LegalGroup	TRUE/FALSE. Default: FALSE	Determines whether the integration creates collections sharing groups in BRM. If set to TRUE, the integration creates collections sharing groups when the owner account and billing account on an order line are different. If set to FALSE, the integration ignores the owner account and does not create collections sharing groups.

Configuration Properties for BRM Services

Table 6-17 shows the properties for the ProcessCollectionSharingBRMCommsProvABCSImpl service.

Table 6-17 ProcessCollectionSharingBRMCommsProvABCSImpl Properties

Property Name	Value/Default Value	Description
Default.SystemID	BRM_01	Specifies the BRM instance code. It is used if the request message does not contain the target system ID.
Routing.BRMCOLLECTIONSService.RouteToCAVS	true/false Default: false	Specifies whether the end point routes to CAVS.
Routing.BRMCOLLECTIONSService.BRM_01.EndpointURI	Default: eis/BRM	Specifies the end point URL for the CAVS.
ABCSExtension.ABCSExtension.PreXformABMtoEBM	true/false Default: false	Indicates whether the ABCS has been extended before the EBM to ABM transformation.
ABCSExtension.PostXformEBMtoABM	true/false Default: false	Indicates whether the ABCS has been extended after the EBM to ABM transformation.

Table 6-18 shows the properties for the SyncCustomerPartyListBRMCommsProvABCSImpl service.

Table 6-18 SyncCustomerPartyListBRMCommsProvABCSImpl Properties

Property Name	Value/Default Value	Description
Default.SystemID	BRM_01	Specifies the BRM instance code that is used if the request message does not contain the target system ID.
EBSOverride.CommunicationsCustomerPartyEBSV2.SyncCustomerPartyListResponse.PortType	CommsProcessBillingAccountListEBF	The port type of the web service to invoke dynamically. This value should be consistent with the Address property.
EBSOverride.CommunicationsCustomerPartyEBSV2.SyncCustomerPartyListResponse.ServiceName	{http://xmlns.oracle.com/EnterpriseFlows/Industry/Comms/CommsProcessBillingAccountListEBF/V1}CommsProcessBillingAccountListEBF	The service name of the web service to invoke dynamically. This value should be consistent with the Address property.
EBSOverride.CommunicationsCustomerPartyEBSV2.SyncCustomerPartyListResponse.Address	http://SOA_host:port/soa-infra/services/default/CommsProcessBillingAccountListEBF/client	The address endpoint URI of a web service, such as CAVS or another ABCS, to dynamically invoke from this service.
EnableAccountStatusSync	true/false. Default: false	Indicates whether the integration synchronizes account status. When set to true, the integration synchronizes account status from Siebel CRM to BRM.
Routing.BRMCUSTService.BRM_01.EndpointURI	Default: eis/BRM	Specifies the connection factory to connect to the BRM JCA adapter for the first of multiple instances of BRM for the CUST opcodes.
Routing.BRMCUSTService.RouteToCAVS	true/false. Default: false	Specifies whether the end point routes to CAVS for the CUST opcodes.
AccountLevelBalanceGroupName	Account Level Balance Group	Names the default balance group created in BRM when an account is created.
ABCSExtension.PreXFormEBMtoABM	true/false. Default: false	Indicates whether the ABCS has been extended before the EBM to ABM transformation.
ABCSExtension.PreInvokePCM_OP_BILL_GROUP_GET_PARENTABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokePCM_OP_BILL_GROUP_GET_PARENTABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PreInvokePCM_OP_SEARCHABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokePCM_OP_SEARCHABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PreInvokeABSPCM_OP_CUST_COMMIT_CUSTOMERABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokeABSPCM_OP_CUST_COMMIT_CUSTOMERABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PreInvokePCM_OP_CUSTCARE_MOVE_ACCTABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokePCM_OP_CUSTCARE_MOVE_ACCTABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PreInvokePCM_OP_CUST_UPDATE_CUSTOMERABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokePCM_OP_CUST_UPDATE_CUSTOMERABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PreInvokePCM_OP_CUST_DELETE_PAYINFOABM	true/false. Default: false	Indicates whether the ABCS has been extended before the invocation of the opcode in the property name.
ABCSExtension.PostInvokePCM_OP_CUST_DELETE_PAYINFOABM	true/false. Default: false	Indicates whether the ABCS has been extended after the invocation of the opcode in the property name.
ABCSExtension.PostXFormABMtoEBM	true/false. Default: false	Indicates whether the ABCS has been extended after the ABM to EBM transformation.
Routing.BRMCUSTService_ptt.RouteToCAVS	true/false. Default: false	Specifies whether to route to CAVS for the CUST opcodes.
Routing.BRMCUSTCAREService.RouteToCAVS	true/false. Default: false	Specifies whether to route to CAVS for the CUSTCARE opcodes.
Routing.BRMBILLService.RouteToCAVS	true/false. Default: false	Specifies whether to route to CAVS for BILL opcodes.
Routing.BRMBASEService.RouteToCAVS	true/false. Default: false	Specifies whether to route to CAVS for BASE opcodes.
Routing.BRMTXNService.RouteToCAVS	true/false. Default: false	Specifies whether to route to CAVS for TXN opcodes.

Configuration Properties for Siebel CRM Services

Table 6-19 shows the properties for the SyncAccountSiebelReqABCSImpl service.

Table 6-19 SyncAccountSiebelReqABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	SEBL_01	Specifies the Siebel CRM instance code that is used if the request message does not contain the target system ID.
ABCSExtension.PreXformABMtoEBMABM	true/false. Default: false	Indicates whether the ABCS has been extended before the ABM to EBM transformation.
ABCSExtension.PreInvokeEBSEBM	true/false. Default: false.	Indicates whether the ABCS has been extended before the EBS invocation.
Routing.SWICustomerParty.SEBL_01.EndpointURI	http://Siebel_host:port/eai_Siebel_language/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1	Endpoint URI of the SEBL_01 Siebel instance.
Routing.SWICustomerParty.RouteToCAVS	true/false. Default: false.	Specifies whether the end point routes to CAVS.
Routing.SWICustomerParty.CAVS.EndpointURI	http://SOA_host:port/AIAValidationSystemServlet/syncresponsesimulator	Specifies the end point URL for the CAVS service.
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	NA
RoutingCustomerPartyEBSV2.SyncCustomerPartyList.CAVS.EndpointURI	http://${fp.server.soaserverhostname}:{fp.server.soaserverport}/AIAValidationSystemServlet/asyncrequestrecipient	Specifies whether the end point routes to CAVS.
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.RouteToCAVS	true/false. Default: false.	Specifies whether the end point routes to CAVS.
Routing.TransformAppContextSiebelService.RouteToCAVS	true/false. Default: false.	Specifies whether the end point routes to CAVS.
Routing.TransformAppContextSiebelService.CAVS.EndpointURI	http://${fp.server.soaserverhostname}:{fp.server.soaserverport}/AIAValidationSystemServlet/asyncrequestrecipient	Specifies whether the end point routes to CAVS.
Account.ProcessUpdateEventsOnly	true/false. Default: true.	To optimize the integration flow, leave this property set to true. This prevents the Siebel CRM ABCS from propagating create events. By default the integration supports creation of customers only as part of the order flow. Setting this property to false results in a less optimized flow, and the default integration behavior remains the same. See Oracle Application Integration Architecture Pre-Built Integrations Functional Interoperability Configuration Guide for more information.
Contact.QueryAllEntities	true/false. Default: false.	NA
Address.QueryAllEntities	true/false. Default: false.	NA

Table 6-20 shows the properties for the ProcessAccountHierarchyListSiebelCommsProvABCSImpl service.

Table 6-20 ProcessAccountHierarchyListSiebelCommsProvABCSImpl Properties

Property Name	Value/Default Value	Description
Default.SystemID	SEBL_01	Specifies the Siebel CRM instance code that is used if the request message does not contain the target system ID.
ABCSExtension.PreXformEBMtoABM	true/false Default: false	Indicates whether the ABCS has been extended before the EBM to ABM transformation.
ABCSExtension.PostXformEBMtoABM	true/false Default: false	Indicates whether the ABCS has been extended after the EBM to ABM transformation.
Routing.SWI_spcAccount_spcHierarchy.RouteToCAVS	true/false Default: false	Specifies whether the end point routes to CAVS.
Routing.SWI_spcAccount_spcHierarchy.CAVS.EndpointURI	http://SOA_server:port/AIAValidationSystemServlet/syncresponsesimulator.	Specifies the CAVS endpoint URI for the Siebel CRM adapter.
Routing.SWI_spcAccount_spcHierarchy.SEBL_01.EndpointURI	http://Siebel_server:port/eai_Siebel_language/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1	Specifies the Siebel CRM instance endpoint URI.
Routing.SWI_spcAccount_spcHierarchy.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Specifies the type of environment for which to route to CAVS.
ABCSExtension.PreInvokeABS	true/false Default: false	Indicates whether the ABCS invokes the extension service before invoking the application.
ABCSExtension.PostInvokeABS	true/false Default: false	Indicates whether the ABCS invokes the extension service after invoking the application.

Table 6-21 shows the properties for the QueryCustomerPartyListSiebelProvABCSImpleV2 service.

Table 6-21 QueryCustomerPartyListSiebelProvABCSImpleV2 Properties

Property Name	Value/Default Value	Description
Default.SystemID	SEBL_01	Specifies the Siebel CRM instance code that is used if the request message does not contain the target system ID.
ABCSExtension.PreXformEBMtoABMEBM	true/false Default: false	Indicates whether the ABCS has been extended before the EBM to ABM transformation.
ABCSExtension.PostXformABMtoEBMEBM	true/false Default: false	Indicates whether the ABCS has been extended after the EBM to ABM transformation.
Routing.SWI_spcCustomer_spcParty_spcService.RouteToCAVS	true/false Default: false	Specifies whether the end point routes to CAVS.
Routing.SWI_spcCustomer_spcParty_spcService.CAVS.EndpointURI	http://SOA_server:port/AIAValidationSystemServlet/syncresponsesimulator.	Specifies the CAVS endpoint URI for the Siebel CRM adapter.
Routing.SWI_spcCustomer_spcParty_spcService.SEBL_01.EndpointURI	http://Siebel_server:port/eai_Siebel_language/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1	Specifies the Siebel CRM instance endpoint URI.
Routing.SWI_spcAccount_spcHierarchy.MessageProcessingInstruction.EnvironmentCode	PRODUCTION	Specifies the type of environment for which to route to CAVS.
ABCSExtension.PreInvokeSWICustServiceABM	true/false Default: false	Indicates whether the ABCS invokes the extension service before invoking the Siebel CRM web service.
ABCSExtension.PostInvokeSWICustServiceABM	true/false Default: false	Indicates whether the ABCS invokes the extension service after invoking the Siebel CRM web service.

Configuring Order Fallout Management

This section describes how to configure order fallout management in the Order to Cash business process.

About Configuring Order Fallout Management

Configuring order fallout management includes:

• Configuring Oracle AIA

• Configuring Siebel CRM to integrate with Oracle AIA

• Working with domain value maps (DVMs) and cross-references

• Handling error notifications

• Setting Oracle AIA configuration properties

This section assumes that you have already installed Siebel CRM. See the Oracle AIA software compatibility matrix available from My Oracle Support for information about required versions and patches.

Configuring Oracle AIA for Order Fallout Management

To configure Oracle AIA for order fallout management:

1. If necessary, update the data seeded by the installation process in the AIA_ERROR_NOTIFICATIONS table. See Using Error Type to Control Response to Order Fallout for more information.

2. Ensure that the SystemType for the applications configured in the AIA_SYSTEMS table matches the COMMON value of the TROUBLETICKET_AREA DVM.

Configuring Siebel CRM for Integrated Order Fallout Management

To configure Siebel CRM for order fallout management, add the following dependencies to Siebel Trouble Ticket Area's List of Values (LOVs) for the trouble ticket functionality:

Area:
Oracle OSM - OLM
Oracle OSM - Provisioning
BRM_01
  
Sub-Area:
OSM OLM ABC
OSM Provisioning ABC
BRM ABC
  

Add any additional values needed for your environment.

See Siebel documentation for more information on adding values to a LOV.

Working with Domain Value Maps for Order Fallout Management

DVMs are a standard feature of the Oracle SOA Suite. They 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 additional maps as required. Transactional business processes never update DVMs; they only read from them. DVMs are stored in XML files and cached in memory at run time.

DVM types are seeded for the order fallout flows, and administrators can extend the list of mapped values by adding more maps. The DVM data should be synchronized with what the participating applications use.

Table 6-22 lists the DVMs for the process integration for order fallout.

Table 6-22 Order Fallout Management DMVs

DVM	Description
TROUBLETICKET_AREA	DVM to map the Area of the trouble ticket. SEBL_01 column maps to the Area element in Siebel CRM. COMMON column points to the SystemCode column of the corresponding system in the AIA Systems page.
TROUBLETICKET_SUBAREA	DVM to map the SubArea of the trouble ticket. SEBL_01 column maps to the Sub-Area element in Siebel CRM. COMMON column points to the appropriate FailureSubSystemCode or the faulting service.
TROUBLETICKET_STATUS	DVM to map the status of the trouble ticket. SEBL_01 column maps to the Status element in Siebel CRM. COMMON column maps to the appropriate status in Oracle AIA.
TROUBLETICKET_SEVERITY	DVM to map the severity of the trouble ticket. SEBL_01 column maps to the Severity element in Siebel CRM. COMMON column maps to the appropriate severity (1-5) in Oracle AIA.
TROUBLETICKET_PRIORITY	DVM to map the recovery priority of the trouble ticket. SEBL_01 column maps to the Priority element in Siebel CRM. COMMON column maps to the appropriate priority (1-4) in Oracle AIA.

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

Working with Cross-References for Order Fallout Management

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 6-23 lists the order fallout cross-reference.

Table 6-23 Order Fallout Management Cross-Reference

Cross-Reference Table Name	Column NameCOMMON	Column ValueSEBL_01	Description
TROUBLETICKET_TROUBLETICKETID	CreateTroubleTicketResponseEBM/DataArea/CreateTroubleTicketResponse/Identification/BusinessComponentID stores this value. A randomly generated ID is used as the COMMON value for the trouble ticket and referenced with the Siebel value.	The row ID for the trouble ticket created in Siebel, which is returned in the ListOfSWITroubleTicketIO/TroubleTicket/Id element of the response of the web service, is cross-referenced.	The trouble ticket ID returned by the Siebel web service is cross-referenced to the BusinessComponentID of the TroubleTicket Response enterprise business message (EBM). The idea is to use this cross-referenced value for making any updates to this trouble ticket. So this cross-referencing is done only when the response is sought from the process CreateTroubleTicketSiebelCommsProvABCSImpl.

Handling Error Notifications for Order Fallout Management

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

Table 6-24 lists the localized custom errors that are caused by the order fallout management services for data insufficiency for creating a trouble ticket.

Table 6-24 Localized Custom Errors

Error Code	Message Text
AIA_ERR_AIACOMOFMPI_0001	Data Insufficient for Trouble Ticket Creation. Order Originating System Code not available.
AIA_ERR_AIACOMOFMPI_0002	Data Insufficient for Trouble Ticket Creation. Order ID not available.

For more information about the errors caused by Siebel CRM or BRM, see the documentation for that product.

See Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack for more information about AIA error handling.

About Error Notification Roles and Users

The integration uses the following default roles and users to issue error notifications:

• Role: AIAIntegrationAdmin

• User: AIAIntegrationAdminUser

See Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack for more information about setting up error notifications.

Using Error Type to Control Response to Order Fallout

The ERROR_TYPE column in the AIA Error Notifications table (AIA_ERROR_NOTIFICATION) determines what happens when there is a failure during order processing.

The supported values for ERROR_TYPE are:

• AIA_EH_DEFAULT - Generates the standard Oracle AIA error notification.

• AIA_ORDERFALLOUT_CFS - Results in Oracle AIA notifying an order management system or central fulfillment system (such as OSM) regarding the order fallout so that it can create and manage the trouble ticket. This value enables the default Order Fallout handling for the Create and Manage Trouble Ticket for Order Fallout flow.

• AIA_ORDERFALLOUT_TTS - Results in Oracle AIA creating a trouble ticket for the order fallout. This value enables the default Order Fallout handling for the Create Trouble Ticket for Order Fallout flow.

The value AIA_EH_DEFAULT can be combined with the value AIA_ORDERFALLOUT_CFS or AIA_ORDERFALLOUT_TTS, using a comma as the separator. For example, AIA_EH_DEFAULT,AIA_ORDERFALLOUT_CFS results in the actions associated with both the values being triggered.

Note:

You cannot have both AIA_ORDERFALLOUT_CFS and AIA_ORDERFALLOUT_TTS values specified for a given record.

If both the Oracle Communications Order to Cash Siebel CRM business process option and the Oracle Communications Order to Cash OSM business process options are installed, the seeded value for ERROR_TYPE is AIA_ORDERFALLOUT_CFS. If the Oracle Communications Order to Cash: Siebel CRM business process option is installed alone (without the Oracle Communications Order to Cash OSM business process option) the seeded value for ERROR TYPE is AIA_ORDERFALLOUT_TTS.

Different ERROR_TYPE values can be given for different combinations of BPEL and ESB service, business process, system code, and error code. As delivered, Oracle AIA seeds these values for all order services. In cases where a service is used in multiple business processes, it is separately seeded for each business process.

In any given order service, there can be two categories of errors:

• Business Errors

  A business error is usually due to invalid or incomplete data on the order or missing setup in the end fulfillment system, which results in the request to process an order failing. In this case, for the order to be successfully processed, either the order must be corrected or revised and resubmitted, or the setup in the end fulfillment system must be corrected and the order resubmitted. For this type of error, Order Fallout should be triggered.

  This type of error usually happens when an order reaches either the participating or the edge application (such as BRM). The expectation is that the fault coming from the application is a BPEL error code: "{http://schemas.oracle.com/bpel/extension}bindingFault". BRM returns a bindingFault when it sees a business error in the order.

• All Other Errors

  This includes system errors. System errors can arise when a certain system (such as BRM or BRM JCA Adapter) is down. The assumption is that there is actually nothing wrong with the order data itself and when system errors are addressed, the order can be resubmitted without any changes. For these types of errors, Order Fallout should not occur.

Order services are delivered seeded with two entries in the AIA_ERROR_NOTIFICATIONS table:

• Error Code - "{http://schemas.oracle.com/bpel/extension}bindingFault

  The seeded value for Error Type is either AIA_EH_DEFAULT,AIA_ORDERFALLOUT_TTS or AIA_EH_DEFAULT,AIA_ORDERFALLOUT_CFS. The expected behavior for this case is both standard AIA error notification and order fallout processing occurs.

• Error Code - null or no value

  The seeded value for Error Type is AIA_EH_DEFAULT. The expected behavior for this case is only standard Oracle AIA error notification occurs.

Table 6-25 is an example entry for the ProcessFulfillmentOrderBillingBRMCommsAddSubProcess order service.

Table 6-25 Example Entry for ProcessFulfillmentOrderBillingBRMCommsAddSubProcess Order Service

Error Code	Service Name	Error Type	Error Extn Handler
--	ProcessFullmentOrderBillingBRMCommsAddSubProcess	AIA_EH_DEFAULT	AIACOM_OFM_EXT
{http://schemas.oracle.com/bpel/extension}bindingFault	ProcessFullmentOrderBillingBRMCommsAddSubProcess	AIA_EH_DEFAULT,AIA_ORDERFALLOUT_CFS	AIACOM_OFM_EXT

If additional error codes are also classified as business errors, you can add new entries into the AIA_ERROR_NOTIFICATIONS table with the appropriate Error Code value.

Note:

The Error Extn Handler value for all order service entries must be AIACOM_OFM_EXT. This is required so that the correct information is in the fallout and the standard error notification.

You can perform a bulk update or the error types for all of the processes by using a SQL script to update the table ERROR_TYPE column in the AIA_ERROR_NOTIFICATIONS table with the appropriate values. See the $AIA_HOME/pips/Communications/O2C/DatabaseObjects/AIA_OFM_CreateOrderFalloutAIAErrorNotificationsData.sql for reference. After the table is updated, you must restart FMW.

Configuring Order Fallout Services

Configure the properties described in this section in the COMMS_AIA_HOME/source/soainfra/apps/AIAMetaData/config/AIAConfigurationProperties.xml file.

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about working with AIAConfigurationProperties.xml.

Note:

Entries in the AIAConfigurationProperties.xml file are case sensitive.

Table 6-26 shows the properties for the CreateTroubleTicketAIACommsReqImpl service.

Table 6-26 CreateTroubleTicketAIACommsReqImpl Properties

Property Name	Value/Default Values	Description
Sender.Default.SystemID	COMMON	Use this only if the request message does not contain the system instance ID. This value is always COMMON because this service is triggered from Oracle AIA.
EBSOverride.TroubleTicketEBS.CreateTroubleTicket.PortType	{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/CreateTroubleTicketSiebelCommsProvABCSImpl/V1}CreateTroubleTicketSiebelCommsProvABCSImplService	Port Type of the provider ABCS/EBS service of the CreateTroubleTicket operation.
EBSOverride.TroubleTicketEBS.CreateTroubleTicket.Address	http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/CreateTroubleTicketSiebelCommsProvABCSImpl/CreateTroubleTicketSiebelCommsProvABCSImpl	Address of the provider ABCS/EBS service CreateTroubleTicket operation.
EBSOverride.TroubleTicketEBS.CreateTroubleTicket.ServiceName	{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/CreateTroubleTicketSiebelCommsProvABCSImpl/V1}CreateTroubleTicketSiebelCommsProvABCSImplService	Service Name of the provider ABCS/EBS service of the CreateTroubleTicket operation.
TroubleTicket.DefaultSeverity	Any number from 1 to 5. Default = 2.	If the fault message does not have any severity associated with it, the default severity is assigned to the fault message and reflects the same in the trouble ticket.
TroubleTicket.DefaultPriority	Any number from 1 to 4. Default = 2.	This service assigns the recovery priority for the trouble ticket by default to the value specified in this configuration property.

Table 6-27 shows the properties for the CreateTroubleTicketSiebelCommsProvABCSImpl service name.

Table 6-27 CreateTroubleTicketSiebelCommsProvABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	SEBL_01	Siebel system instance code (defined in BSR). Used when the target system cannot be identified from the request message or if the configuration property. TroubleTicket.UseDefaultInstance is set to true.
ABCSExtension.PreXformEBMtoABMTroubleTicketEBM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (before the EBM to ABM transformation).
ABCSExtension.PostXformABMtoEBMTroubleTicketEBM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (after the ABM to EBM transformation).
ABCSExtension.PreInvokeABSSWITroubleTicketIOABM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (PreInvoke Application).
ABCSExtension.PostInvokeABSSWITroubleTicketIOABM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (PostInvoke Application).
EBSOverride.TroubleTicketEBSResponse.CreateTroubleTicketResponse.PortType	{http://xmlns.oracle.com/Industry/Comms/CreateTroubleTicketRespOSMCFSCommsJMSProducer/V1}CreateTroubleTicketRespOSMCFSCommsJMSProducer	Port Type of the provider ABCS/EBS service of the CreateTroubleTicketResponse operation.
EBSOverride.TroubleTicketEBSResponse.CreateTroubleTicketResponse.Address	http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/CreateTroubleTicketRespOSMCFSCommsJMSProducer	Address of the provider ABCS/EBS service of the CreateTroubleTicketResponse operation.
EBSOverride.TroubleTicketEBSResponse.CreateTroubleTicketResponse.ServiceName	{http://xmlns.oracle.com/Industry/Comms/CreateTroubleTicketRespOSMCFSCommsJMSProducer/V1}CreateTroubleTicketRespOSMCFSCommsJMSProducer	Service Name of the provider ABCS/EBS service of the CreateTroubleTicketResponse operation.
Routing.SWI_spcTrouble_spcTicket_spcService.RouteToCAVS	true/false Default: false	Indicates whether the Partner link SWI_spcTrouble_spcTicket_spcService should be routed to CAVS or the actual application.
Routing.SWI_spcTrouble_spcTicket_spcService.SEBL_01.EndpointURI	Endpoint URI of the SEBL_01 Siebel instance	Endpoint URI of the SEBL_01 Siebel instance or CAVS simulator (if RouteToCAVS is true).
TroubleTicket.GenerateTroubleTicketResponse	true/false Default: false	CreateTroubleTicketSiebelCommsProvABCSImpl creates a trouble ticket response message (creates a cross-reference for the trouble ticket ID with the Siebel ID) and invokes the CommunicationsTroubleTicketResponseEBSV1 if this property is set to true or if the response code attribute is not null. Otherwise, this service acts only as a fire-and-forget flow and ignores the response.
TroubleTicket.UseDefaultInstance	true/false Default: false	If set to true, overwrites the target Siebel instance to the default instance indicated by the property Default.SystemID. Gives the user an option to create a trouble ticket in a Siebel instance different from the one where the order was placed.
TroubleTicket.SR_TYPE	Order Failure	SR_TYPE identifies that the trouble ticket is for Order Failure. Siebel web service expects this value to be Order Failure for Order Failure Trouble Tickets.

Table 6-28 shows the properties for the UpdateTroubleTicketSiebelCommsProvABCSImpl service name.

Table 6-28 UpdateTroubleTicketSiebelCommsProvABCSImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	SEBL_01	Siebel system instance code (defined in BSR). Used when the target system cannot be identified from the request message or if the configuration property TroubleTicket.UseDefaultInstance is set to true.
ABCSExtension.PreXformEBMtoABMTroubleTicketEBM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (before the EBM to ABM transformation).
ABCSExtension.PreInvokeABSSWITroubleTicketIOABM	true/false Default: false	Value determines whether the ABCS should invoke the Extension service (PreInvoke Application).
Routing.SWI_spcTrouble_spcTicket_spcService.RouteToCAVS	true/false Default: false	Indicates whether the Partner link SWI_spcTrouble_spcTicket_spcService should be routed to CAVS or the actual application.
Routing.SWI_spcTrouble_spcTicket_spcService.SEBL_01.EndpointURI	Endpoint URI of the SEBL_01 Siebel instance	Endpoint URI of the SEBL_01 Siebel instance or CAVS simulator (if RouteToCAVS is true).

Table 6-29 shows the properties for the CreateOrderFalloutNotificationOSMCFSCommsProvImpl service.

Table 6-29 CreateOrderFalloutNotificationOSMCFSCommsProvImpl Properties

Property Name	Value/Default Values	Description
Default.SystemID	OSMCFS_01	Siebel system instance code (defined in BSR). Used when the target system cannot be identified from the request message or if the configuration property TroubleTicket.UseDefaultInstance is set to true.
Routing.CreateOrderFalloutNotification.OSMCFS_01.EndpointURI	http://${http.host name}:${http.port}/orabpel/default/CreateOrderFalloutNotificationOSMCFSCommsJMSProducer/1.0	Endpoint URI of the service that sends the fallout notification to OSMCFS_01. The default value is the EndpointURI of the out-of-the-box JMS enqueuing or producing service that enqueues or produces the message in the OSM JMS Queue.
Fault.DefaultSeverity	Any number from 1 to 5 Default - 2	If the fault message has no severity associated with it, assigns the default severity to the fault message and reflects the same in the trouble ticket.

The following fields extract the localized values using the aia:getAIALocalizedString xpath function:

EBM Field Name: DataArea / CreateTroubleTicket / Description
Siebel Field Name: Description
ResourceBundle - oracle.apps.aia.core.i18n.AIAListResourceBundle
ResourceBundle Key - TROUBLETICKET_DESCRIPTION
Resource Bundle Value: SalesOrder- {OrderNumber} # {OrderRevision}for Account {AccountName} failed at {Timestamp}
--
EBM Field Name: EBMHeader/BusinessScope/ID
Siebel Field Name: Abstract
ResourceBundle - oracle.apps.aia.core.i18n.AIAListResourceBundle
ResourceBundle Key - TROUBLETICKET_ABSTRACT
Resource Bundle Value: [{Timestamp}] Trouble Ticket for (Sales)Order - {OrderNumber} # {OrderRevision}