| Oracle® Application Integration Architecture Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite Implementation Guide Release 3.1.1 Part Number E22284-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite Implementation Guide Release 3.1.1 Part Number E22284-04 |
|
|
PDF · Mobi · ePub |
This chapter includes the following sections:
This section discusses prerequisites and includes the following topics:
The prerequisites include:
The customer management process integration does not have a dependency on other processes being run; however, the Organization cross-reference must be set up first.
For more information about setting up cross-references, see Appendix C, "Settings for Multi-Org Implementation"
You do not have to perform this step if you are using Oracle E-Business Suite Release 11.5.10.2.
If account synchronization is to occur in near real time, you must schedule the TCA Raise Business Event concurrent program to run at specified intervals.
The process integration for product management has no prerequisites.
The prerequisites include:
In CRM On Demand, you must enable the Opportunity-to-Quote or the Opportunity-to-Order business process as described in "Implementing the Opportunity to Quote or Order Business Process."
Products are synchronized from Oracle E-Business Suite to CRM On Demand.
Customer information is synchronized between Oracle E-Business Suite and CRM On Demand.
Data requirements indicate the mandatory data that must be provided to make the integration flows successful.
This section includes the following topics:
The data requirements include:
Oracle E-Business Suite profile options must be specified.
For Oracle E-Business Suite Release 12.1.1 or later, you must specify the MO: Operating Unit profile option.
For Oracle E-Business Suite Release 11.5.10CU2 and Release 12.1.1 or later, the values of the Auto Generate Customer Number and Auto Generate Site Number EBS profile parameters are set to Y at the operating unit level so that customer number and site number are automatically generated in EBS.
Address data to be synchronized must have address line 1, city, state, and zip code.
Locations cannot be shared by different organization parties in Oracle E-Business Suite, and addresses cannot be shared between accounts in CRM On Demand.
In Oracle E-Business Suite, the contact should be associated at the account level only.
For the Order Management Application Programming Interface (API) to process the contact, it should not be associated at multiple levels of an account, for example, not at the account site (address) level.
If the contact used in CRM On Demand during Order submit is associated with several accounts and contact points (phone numbers or email address) are present, then order submission is not supported because the Oracle E-Business Suite API for contact update or create does not support shared contact points.
Only items associated with an Oracle E-Business Suite OE Item Validation Organization are synchronized from Oracle E-Business Suite to CRM. You must add the IDs of the validation organizations to the INVENTORY_LOCATION_ID cross-reference table.
For more information about adding organization IDs to the INVENTORY_LOCATION_ID cross-reference table, see Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1.
The data requirements include:
To convert an opportunity to a quote or order, you must supply the account details with the opportunity.
Primary contact and product revenue line details are optional.
If you have implemented Oracle CRM HTML quoting, you must set the value of the ASO: Automatic Sales Team Assignment profile option to NONE.
This section describes the tasks that you must perform in Oracle E-Business Suite (Oracle E-Business Suite) to implement the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP and discusses how to:
Change the email address.
Grant access to the 360 Degree view in Oracle E-Business Suite.
Change the default status of new orders in Oracle E-Business Suite.
Assign sales rep.
Note:
Ensure that you have applied all of the Oracle E-Business Suite patches listed in Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Software and Hardware Requirements."
When CRM On Demand is configured to implement the CRM HTML quoting integration, the sales user email ID in CRM On Demand must match the sales person's email ID in his or her JFT Resource profile in Oracle E-Business Suite (specifically, it must match the source_email value in the jtf_rs_resource_extns table in Oracle E-Business Suite). This topic describes how to identify the email resource ID of a sales person in Oracle E-Business Suite so that you can ensure that it matches the sales user's email address within CRM On Demand.
CRM HTML quoting requires that the sales person resource ID be used to create a quote in Oracle E-Business Suite. The quote that is created is associated with the ID of the sales person, and to view the quote in Oracle E-Business Suite, the sales person's login ID must be used.
CRM On Demand sends the sales person's email address in the request to create the quote. The email address is used by the CreateSalesQuoteEbizProvABCSImpl Business Process Execution Language (BPEL) process to obtain the sales person's email resource ID from Oracle E-Business Suite using the Service QueryJTFResourceSalesPersonAdapter.
To change the email address:
Log in to Oracle E-Business Suite.
Select the Human Resources responsibilities for your organization.
Click Enter and Maintain under People.
Search for the employee.
Update the email under Office Details.
Select the CRM Administrator, <organization> responsibility.
Click Run under Resource Manager : Others : Requests to run Synchronize Employee Concurrent Requests.
Use the default parameters to run the request.
Verify the email address in the JFT Resource profile by issuing the query in Example 6-1:
Example 6-1 Query for JFT Resource profile
Select resource_id, source_email, decode (category, 'EMPLOYEE', 1, 'PARTNER', 2, 'PARTY', 3,'SUPPLIER_CONTACT', 4, 'OTHER', 5, 'TBH', 6) preference from jtf_rs_resource_extns RS where source_email like '&email_id_form_CRMOD' and user_id is not null and exists (select salesrep_id from jtf_rs_salesreps where resource_id = RS. resource_id) and rownum = 1 order by preference.
Where email_id_form_CRM OD is the email in the request EBM
Note:
You must replace email_id_from_CRMOD text with either email from the request EBM or the value passed for step 5.
For more information about JFT resource and sales person information, see Oracle Common Application Components User's Guide in 11i. In R12, use the Oracle Trading Community Architecture User Guide: B25893-01
To enable users to launch the Oracle E-Business Suite Transaction View from CRM On Demand, you must grant users the Oracle Customers Online User or Super user responsibilities.
When a new order is created, the default status of the new order in Oracle E-Business Suite is ENTERED. This default value is determined by the value of the OrderStatus property in the AIA Configuration file for the ProcessSalesOrderCRMODReqABCSImpl service.
To change the default status value of new orders in Oracle E-Business Suite, you must change the value of the OrderStatus property in the AIA configuration file.
To change the default status of new orders in Oracle E-Business Suite:
Locate the following file:
AIA_HOME/aia_instance/instancename/AIAMetaData/config/AIAConfigurationProperties.xml
Search for the ProcessSalesOrderCRMODReqABCSImpl service.
Update the OrderStatus property with the new default status value.
The possible values for the OrderStatus property are configured in the ORDER_STATUS domain value map (DVM) in the COMMON value.
Log in to the AIA Console http://<server name>:<port number>/AIA/ with the server administrator user name.
In the AIA Console, navigate to Setup, Configuration.
Click Reload to save the changes that you have made.
CRM Quote requires that the sales rep assigned to the "<Operating Unit>" be the sales rep.
For more information, see Appendix C, "Settings for Multi-Org Implementation".
You must set the following profile options in Oracle EBS:
Log in to Oracle E-Business Suite using the System Administrator responsibility.
Open the System Profile Values form.
Query these profile options E-Business Suite 11.5.10.2 and set the indicated values at the site level:
HZ: Execute API Callouts to 'All Events Enabled' or 'Only Business Object Events Enabled'
HZ: Format Business Object Business Events as Bulk to 'N'
HZ: Generate Party Number to 'Yes'
HZ: Generate Party Site Number to 'Yes'
Query these profile options E-Business Suite 12.1.x. and set the indicated values at the site level:
HZ: Raise API Events to 'All Events Enabled' or 'Only Business Object Events Enabled'
HZ: Format Business Object Business Events as Bulk to 'N'
HZ: Generate Party Number to 'Yes'
HZ: Generate Party Site Number to 'Yes'
This section describes the tasks that you must perform in CRM On Demand to implement the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP and includes the following topics:
Section 6.4.1, "Implementing the Opportunity to Quote or Order Business Process"
Section 6.4.2, "Setting Up the CRM On Demand Integration User"
Section 6.4.3, "Creating the Custom Fields Required to Support the Integration"
Section 6.4.4, "Creating the Web Link for the 360 Degree View"
Section 6.4.7, "Configuring Integration and Workflow Events in CRM On Demand"
To implement the Opportunity-to-Quote or Opportunity-to-Order functionality provided by the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP, you must perform several tasks:
(Optional) Enable the Order Management Quoting module.
Enable the order and quote object in CRM On Demand.
Create the web link to enable CRM On Demand users to view orders and quotes in Oracle E-Business Suite.
Display quote or order details on a page, for example, the Opportunity Details page.
Grant users access to the Quote or Order applet on a page.
Ensure that the sales user's email address in CRM On Demand equals the corresponding sales user's email address in Oracle E-Business Suite.
For more information about verifying a sales user's email address in Oracle E-Business Suite, see Section 6.3.1, "Changing the Email Address".
If you choose to implement the Opportunity-to-Quote process integration, you can use the functionality provided by either of the following modules:
CRM On Demand Opportunity to Oracle CRM HTML Quoting
CRM On Demand Opportunity to Order Management Quoting
The Oracle CRM HTML Quoting module is enabled by default. If you prefer to use the Order Management quoting module, you must update the CRMQuoteProvider service configuration property in the AIAConfigurationProperties.xml file as described in the following procedure.
To enable the Order Management Quoting module:
Locate the following file:
AIA_HOME/aia_instance/instancename/AIAMetaData/config/AIAConfigurationProperties.xml.
Search for the CreateSalesQuoteEbizProvABCSImpl service.
Change the value of the CRMQuoteProvider property to False.
The CRMQuoteProvider property is set to true by default, which means that Oracle CRM HTML Quoting is enabled. To enable the Order Management Quoting module, change the value to false.
Log in to the AIA Console http://<server name>:<port number>/AIA/ with the server administrator user name.
In the AIA Console, navigate to Setup, Configuration.
Click Reload to save the changes that you have made.
Restart the SOA server.
To implement the Opportunity-to-Quote or Opportunity-to-Order business processes, you must enable the Order and Quote objects in CRM On Demand.
To enable the Order or Quote objects in CRM On Demand:
Log in to CRM On Demand.
On the welcome page, click the Admin link.
On the Admin Homepage, navigate to Role Management & Access Profiles, and then Role Management.
In the Role Management wizard, perform the following steps:
Select the role name for which you want to enable the Quote or Order objects.
In Step 2, Record Type Access, select the Can Access, Can Read, and Can Create check boxes for the Order or Quote objects.
In Step 5, Tab Access & Order, move the Order or Quote items from the Not Available to the Selected Tab section.
Click Finish.
Click Admin, User Management and Access Controls, Access Profiles.
In the Access Profiles wizard, perform the following steps:
Click Edit Link beside the role name for which you want to enable the Quote or Order objects.
For step 2, Specify Access Levels, change the value of the Default Access field for the Order or Quote objects from No Access to Read/Edit for Sales Users. Set to Read/Edit/Delete for the appropriate administrative users.
Click Finish.
A web link is used to enable CRM On Demand users to view the orders and quotes in Oracle E-Business Suite that are associated with a CRM On Demand opportunity.
This topic describes how to create the web link for the Order object, and how to add the web link to the Order Details page. Use the same procedure to create a web link for the Quote object and to add it to the Quote Details page.
To create the web link to enable CRM On Demand users to view orders in Oracle E-Business Suite:
Log in to CRM On Demand
On the welcome page, click the Admin link.
On the Admin Homepage, navigate to Application Customization, Order, and click Order Field setup.
Click the New Field button and enter the following values:
In the Name field, enter the name for the web link you are creating.
In the Field Type field, select Web link.
Save the record.
On the Order Fields page, click Edit Web Link beside the Web link field that you created in the previous step.
The Edit Web Link page appears.
In the Edit Web Link page, set the focus on the Display Text field, and then select Order Number from the Order field.
The value of the Display Text field is similar to Order: %%%Order_Number%%%. The value "%%%Order_Number%%%" is displayed in the Link Properties URL column.
In the Web Link Target field, select Open in New Window.
Configure one URL as appropriate:
For Order Management orders, specify the following URL:
http://Oracle E-Business Suite Host:port/OA_HTML/OA.jsp?OAFunc=ONT_PORTAL_ORDERDETAILS &HeaderId=%%%Order_Id%%%&&addBreadCrumb=Y
For Order Management quotes, specify the following URL:
http://Oracle E-Business Suite Host:port/OA_HTML/OA.jsp?OAFunc=ONT_PORTAL_ORDERDETAILS &HeaderId=%%%Quote_Id%%%&&addBreadCrumb=Y
For Oracle CRM HTML quotes on release 11.5.10.2:
i. Specify this URL to get the JFN token, where ebusinesssuiteserver:port is your E-Business Suite server name and port name.: http://<<ebusinesssuiteserver:port>>/OA_HTML/qotSSbcJfnToken.jsp?qotRespKey=HTML_QUOTING_SALES_AGENT
ii. Replace HTML_QUOTING_SALES_AGENT with the responsibility that you are using. If you are using several responsibilities, you must get this token for each one. Example: Responsibility Key: HTML_QUOTING_SALES_AGENT JFN Token: jfn=ZG2CEA6CEBABDF177950927FE65D4DBFD2DF1FACE827272872EE91FA689615D43B44DFB00D207A89882A640D55DEB2E24836
iii. Append the JFN token to this URL: http://<<ebusinesssuiteserver:port>>/OA_HTML/qotSZzpAppsLink.jsp?qotHdrId=%%%Quote_Id%%%&qotReqSetCookie=Y&qotDetCode=QUOTE&qotFrmMainFile=qotSZzdContainer.jsp&<<JFN token calculated in the step i>>
For Oracle CRM HTML quotes on release 12, specify the following URL, where Oracle E-Business Suite Host:port is your Oracle E-Business Suite host name and port name: http://Oracle E-Business Suite Host:port/OA_HTML/OA.jsp?OAFunc=QOT_OAUI_QUOTE_DETAILS& QotIntgEvtSrc=CRMOD&QotIntgEvt=Event.QuoteDet&QotIntgEvtVal=%%%Quote_Id%%%&addBreadCrumb=Y
To add the web link to the Order Details page, perform the following steps.
Navigate to Admin, Application Customization.
Click Order, Order Page Layout.
Select the Copy Link against Order Page Standard Layout option.
The page layout wizard is displayed.
In Step 1, Layout Name, specify Oracle E-Business Suite Order Layout as the layout name.
In Step 3, Field Layout, move the web Link field that you created from the Available Order Fields section to the Key Order Information section.
Click Finish.
Navigate to Admin, User Management & Access control, and Role Management.
Click the Edit link beside the role to which you want to assign the page layout.
In Step 6, Page Layout Assignment, select Oracle E-Business Suite Order Layout as the Order page layout.
The default value is Order Page Standard layout.
To enable users to view the quote or order information on a page, you must configure the Quote or Order object to appear as an applet on the relevant page, then grant specific users or user roles access to the relevant applet on the page.
Note:
Ensure that you have completed the steps in Enabling the Order or Quote Object in CRM On Demand before performing the procedure in this topic.
This topic describes how to grant users access to the Quote applet on the Opportunity Details page. Use the same procedure to grant users access to the Quote applet on the Account Details page, or to grant users access to the Order applet on the Opportunity or Account Details page. Simply substitute the relevant object and page names when following the steps in the procedure.
To grant access to the Quote applet on the Opportunity Details page:
Log in to CRM On Demand.
On the welcome page, click the Admin.
On the Admin Homepage, navigate to User Management & Access Profiles, and Access Profiles.
Select the role for which you want to grant access to the Quote applet.
Click step 2, Specify Access Levels, and then Opportunity related information.
For the quote object, change the value of the Access level from No access to View.
Click Related Information beside the Account item.
For the quote or order object, change the setting from No Access to View.
You can choose to display quote or order details on the Opportunity or Account Details page according to your preferences.
This topic describes how to configure the Quote object so that users can view quote details on the Opportunity Details page. Use the same procedure to configure the quote object to appear on the Account Details page, or to configure the Order object to appear on the Opportunity or Account Details page. Simply substitute the relevant object and page names when following the steps in the procedure.
To configure quote details to appear on the Opportunity Details page:
Log in to CRM On Demand.
On the welcome page, click the Admin.
On the Admin Homepage, navigate to Application Customization, Opportunity, Opportunity Related Information Layout, Quotes.
Arrange the columns using the default layout, or edit the layout as required.
On the Admin Homepage, navigate to Application Customization, Opportunity, Opportunity Page Layout.
Click the Edit link beside the Page layout name.
Click Step 4, Related Information.
Drag the Quote object into the Display Information section.
Click Step 5, Related Information Layout.
Select the quote layout that you created in step 4.
Before you can use the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP, you must set up an integration user within CRM On Demand. This section discusses how to:
Define integration users in CRM On Demand.
Update integration user information in CRM On Demand.
Note:
This topic provides information about the values that you must define in CRM On Demand to support the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP.
For more information about creating custom fields, see CRM On Demand Online Help, "Administering Siebel CRM On Demand," User Management and Access Controls.
To define an integration user in CRM On Demand:
Log in to CRM On Demand.
On the Welcome page, click the Admin.
On the Admin Homepage, click the User Management & Access Controls link.
On the User Management & Access Controls page, click the Role Management link in the Role Management section.
On the Role List page, click Edit next to an existing name to update an existing user, or click New User to create a user.
Ensure that the user has these privileges set up:
Manage Data Rules - Manage Workflow Rules
Manage Integration Event Queue
Note:
If these privileges are not available to you in the Administration user interface, or if the size of the default integration event queue is less than 500,000, contact your CRM On Demand system administrator to ensure that these privileges and settings are enabled for the integration user.
After you set up an integration user, changes to that user may be required. For example, you might want to change the user ID or password. To change the user ID or password, you must update the AIAConfigurationsProperties.xml.
For more information, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager."
This topic describes how to configure the custom fields required by the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP in CRM On Demand.
A custom pick list field that is defined within CRM On Demand controls whether records are to be synchronized to Enterprise Business Suite. This field is also used to display information if synchronization of a record fails. A synchronization status field, Integration Status, and corresponding long text field, Integration Message, provide details of a failed synchronization. These fields must be defined on the Account, Contact, Product, and Lead objects. Oracle recommends that these fields be made available only to administrators, and not to CRM On Demand sales users. Business rules can be defined to set the default Integration Status value to either Sync On or Sync Off using the CRM On Demand Expression Builder.
For more information, see CRM On Demand Online Help, "Administering Siebel CRM On Demand," Application Customization.
The process of configuring custom fields to support the integration involves the following steps:
Create these custom fields:
An Integration Status field for the Account, Contact, Product, and Lead objects in CRM On Demand.
An Integration Message field for the Account, Contact, and Product objects in CRM On Demand (you do not have to create this field for lead objects).
Add the custom fields to page layouts.
After you create the Integration Status and Integration Message fields, you must add them to page layouts so that the fields are available to system administrators and end users.
The Account, Contact, Product, and Lead page layouts must contain the Integration Status and Integration Message field for the PIP to function.
After you add the new fields to these page layouts, you must also point the Administrator user role to the updated page layouts.
Set up field mapping for lead conversion.
After you have created the Integration Status and Integration Message fields and added them to the appropriate page layouts, you must set up field mapping information to support the CRM On Demand lead conversion process.
The lead conversion process requires that the Integration Status field from the Lead page layout is mapped to the Integration Status field from the Account page layout and Contact page layout.
You define integration status and message fields on the CRM On Demand Account, Contact, Product, and Lead objects.
Note:
These instructions provide details for creating the Integration Status field for the Account object only. You must also create this field for the Product, Contact, and Lead objects.
To set up the Integration Status field:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Application Customization, Record Type Setup: object link, Field Management: object Field Setup.
In this navigation, object is the object type for which you are setting the synchronization status, that is, Account, Contact, Product, or Lead.
Note:
The Integration Message field is not required for the Lead object.
On the Object Fields page, click New Fields.
On the Object Field Edit page, complete the following fields, and click Save:
Return to the Object Fields page and locate the Integration Status field.
Click the Edit Picklist link that is associated with the Integration Status field.
Enter these picklist values for the Integration Status field:
Table 6-2 Picklist Values for the Integration Status Field
| Order | ID | Picklist Values |
|---|---|---|
|
1 |
Sync ON |
Sync ON |
|
2 |
Sync OFF |
Sync OFF |
|
3 |
Sync FAILED |
Sync FAILED |
Note:
You must disable the No Value row.
Navigate back to the Object Fields page, and click New Fields.
On the Object Field Edit page, complete these fields as follows, and then click Save.
From the Object Fields page, click Rename Fields, Advanced, and enter these field values:
After you create the Integration Status and Integration Message fields, you must add them to several page layouts so that they are available to system administrators.
To add the integration fields to the Admin layout, complete these steps for the account, contact, product, and lead objects:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Application Customization, Record Type Setup: object link, Page Layout Management: object Layout, Edit Sections (Administrator).
In this navigation, object is the object type for which you are amending the page layout, that is, account, contact, product, or lead.
On the Section Names Setup page, name one available section Oracle E-Business Suite Integration and click Save.
Return to the Page Layout page, and click the Edit link associated with the Administrators version of the object page.
Click Next twice, stopping when you reach step 3, Field Layout.
Add the Integration Status and Integration Message fields to the Oracle E-Business Suite Integration section and click Finish.
Assign the modified page layouts to the Admin user role.
Note:
This procedure documents the recommended method of adding Integration Status and Integration Message fields to page layouts. You can, however, place these fields anywhere on the Account, Contact, Product, and Lead Detail pages, and assign the modified page layouts to any role you choose.
To configure the Account-Contact field:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Application Customization, Record Type Setup: Account, Account Contact Field Setup.
On the Account Contact Fields page, mark the following fields as Required:
Account ID
Contact ID
After you create the custom Integration Status field for the Lead, Account, and Contact objects, you must map the fields used in the integration from the Lead object to the Account, Contact, and Opportunity objects.
To map the Integration Status field:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Business Process Management: Data Rules & Assignment, and Lead Conversion Mapping.
Perform the mapping as listed in the Table 6-5:
Table 6-5 Mapping for Integration Status Field
| Lead | Contact | Account | Opportunity |
|---|---|---|---|
|
Address1 |
Contact Address1 |
Billing Address1 |
NA |
|
Address2 |
Contact Address2 |
Billing Address2 |
NA |
|
Address3 |
Contact Address3 |
Billing Address3 |
NA |
|
Annual Revenues |
NA |
Annual Revenues |
NA |
|
Cellular Phone # |
Cellular Phone # |
NA |
NA |
|
City |
Contact City |
Billing City |
NA |
|
Company |
NA |
Account Name |
NA |
|
Country |
Contact Country |
Billing Country |
NA |
|
Description |
NA |
NA |
Description |
|
|
|
NA |
NA |
|
Estimated Close Date |
NA |
NA |
Close Date |
|
Furigana First Name |
Furigana First Name |
NA |
NA |
|
Furigana Last Name |
Furigana Last Name |
NA |
NA |
|
Industry Id |
Industry Id |
NA |
NA |
|
Integration Status |
Integration Status |
Integration Status |
NA |
|
Job Title |
Job Title |
NA |
NA |
|
Mr./Ms. |
Mr./Mrs. |
NA |
NA |
|
Never Email |
Never Email |
NA |
NA |
|
Next Step |
NA |
NA |
Next Step |
|
Number Of Employees |
NA |
Number Of Employees |
NA |
|
PO Box/Sorting Code |
Contact PO Box/Sorting Code |
Billing PO Box/Sorting Code |
NA |
|
Potential Revenue |
NA |
NA |
Revenue |
|
Primary Phone # |
Work Phone # |
NA |
NA |
|
Province |
Contact Province |
Billing Province |
NA |
|
Sales Rep Id |
Primary Owner Id |
Primary Owner Id |
Primary Owner Id |
|
Source |
Lead Source |
NA |
Lead Source |
|
US State |
Contact US State |
Billing US State |
NA |
|
Work Fax # |
Work Fax # |
NA |
NA |
|
Zip/Post Code |
Contact ZIP/Post Code |
Billing ZIP/Post Code |
NA |
|
Campaign Id |
Campaign Id |
Campaign Id |
Campaign Id |
|
Lead Currency |
NA |
Account Currency |
Opportunity Currency |
Click Save.
The Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP enables users to review back-office Oracle E-Business Suite transaction details for the account they are viewing from within CRM On Demand. An administrator can configure a web link that enables end users to launch the Oracle E-Business Suite Transaction View from the Account Details page for the account they are reviewing. This topic describes how to configure the web link for 360 Degree view.
For more information about the tasks that you must perform to enable user access to the 360 Degree View feature, see Section 6.3.2, "Granting Access to the 360 Degree View in Oracle E-Business Suite".
Accessing the Oracle Customers Online application from CRM On Demand includes the following steps:
The administrator configures a web link on the Account Details page within CRM On Demand and enables access to end users as is appropriate for their business.
From CRM On Demand, the user clicks the web link that has been set up to access the Oracle Customer's Online 360 Degree Transaction View page.
The system opens a new browser window to display the 360 Degree Transaction View page.
Upon the first invocation of the 360 Degree Transaction View page, the user is required to log in using his or her Oracle E-Business Suite credentials. Upon subsequent invocations, the user login information is cached, and no additional login is required, provided the login session is valid and has not timed out.
Note:
Users must have the Customer Online Super User responsibility to access the 360 Degree Transaction View page in Oracle E-Business Suite.
The 360 Degree Transaction View page is launched, enabling users to review account details directly from CRM On Demand by launching an in-context Oracle E-Business Suite page.
The controls for the application are loaded, based on the form data that is passed through the URL (account ID and customer name).
Note:
From this page, the user has full access to the responsibilities granted in Oracle E-Business Suite.
The user finishes viewing the account details and closes the new browser window.
Web links are configured within CRM On Demand with context-sensitive parameters that enable you to define:
The application, form, and version to launch.
The data to pass to Oracle E-Business Suite to retrieve the appropriate record.
For more information about creating Web links in CRM On Demand, see CRM On Demand Online Help, "Administering Siebel CRM On Demand," Application Customization.
The following procedure describes how to configure the web link to launch the Oracle E-Business Suite Transaction View from an Account Detail page.
To set up the web link for account integration, complete these steps:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Application Customization.
From the Application Customization page, navigate to Record Type Setup: Account, and Account Management: Account Field Setup.
From the Account Fields page, click New Field, and create these fields:
From the Account Fields page, click the Edit Web Link for the new Web link field.
From the Edit Web Link page, specify how you want the system to display the application when opened.
Oracle recommends that you select the Open in New Window option.
Specify the URL of Oracle E-Business Suite as follows:
http://Oracle E-Business Suite_Host:Port/OA_HTML/OA.jsp?OAFunc=IMC_NG_360_VIEW_FUNC& ImcEBIAccountId=%%%External_System_Id%%%&ImcPartyName=%%%Name%%%
In this URL, Oracle E-Business Suite_Host:Port is the name and port of your Oracle E-Business Suite host server.
Complete the steps, as defined by CRM On Demand, to finish the web link setup.
After you create the web link, you must add the web link to the Account Page Layout, and then assign the updated page layout to the appropriate user roles.
Note:
Detailed instructions regarding the Page Layout Wizard are included in CRM On Demand Online Help.
For a cluster install, refer to Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Deploying AIACompositeScheduler on Weblogic Cluster" and note ID 1348907.1 on My Oracle Support.
For more information about how to modify AIACompositeScheduler, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, “AIACompositeScheduler,” Modifying AIACompositeScheduler Properties.
Within CRM On Demand, integration events are stored as XML files and are placed in integration event queues for processing. Two queues must exist to process the integration events:
The default queue, which is available by default
The priority queue, which you must create.
Each company has an integration event file limit that specifies the maximum number of integration event files that can exist in CRM On Demand for that company. The recommended limit is 500,000 for the relevant production, UAT or stage instance. A company can create multiple queues and specify different queue sizes for each, but the total combined size of all the queues cannot exceed the maximum limit specified for the company. The recommended queue size for the default queue is 450,000. The recommended size of the Priority Queue is 50,000 (which is 10% of the limit).
In addition to creating the Priority Queue, you must configure the time zone and picklist format for the integration event default queue. Use the following procedures to perform each of these tasks.
To create the Priority Queue:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Integration Event Administration.
Click Integration Event Queue Management.
Click New Queue.
For the Queue Name field, enter PriorityQueue.
Enter a value for the Queue Size field, for example, 50,000, and save the record.
Configure the integration event default queue as described in the following procedure.
To configure the time zone and picklist format for the default queue:
Log in to CRM On Demand.
From the welcome page, navigate to Admin, Integration Event Administration.
Edit the Default Queue.
In the Time Zone field, select UTC.
In the Picklist Format field, select Language Independent Value.
This section provides an overview of integration and workflow event configuration and discusses how to:
Define workflow rule conditions.
Create and configure integration events.
Note:
The documentation in this section provides information and examples that are specific to the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP.
For more information, see CRM On Demand Online Help, "Administering Siebel CRM On Demand," Data Management Tools and CRM On Demand Online Help, "Administering Siebel CRM On Demand," Business Process Management.
To enable the synchronization of account and account address data between CRM On Demand and Oracle E-Business Suite, you must first define workflow rule conditions for several workflow events in CRM On Demand. Table 6-7 lists the workflow events that you must configure, and specifies the workflow rule condition that you must use:
Table 6-7 Workflow Events and Rule Conditions Configuration Fields
| Workflow Name | Record Type | Trigger Event | Workflow Rule Condition |
|---|---|---|---|
|
Account Delete |
Account |
When record is deleted |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync ON")) OR ([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync FAILED")) |
|
Account Insert |
Account |
When new record is saved |
[<plSync_Status_ITAG>] = LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync ON" ) |
|
Account Update |
Account |
When modified record is saved |
([<plSync_Status_ITAG>] = LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync ON")) |
|
Contact Insert |
Contact |
When new record is saved |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync ON")) |
|
Contact Update |
Contact |
When modified record is saved |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync ON")) |
|
Contact Delete |
Contact |
When record is deleted |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync ON")) OR ([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync FAILED")) |
|
Contact-Account-Assoc |
Contact |
After association with parent |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync ON")) |
|
Contact-Account-Disassoc |
Contact |
After disassociation with parent |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync ON")) |
|
Account-Contact-Assoc |
Account |
After association with parent |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync ON")) |
|
Account-Contact-Disassoc |
Account |
After disassociation with parent |
([<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync ON")) |
After you define workflow rule conditions, you must create and configure an integration event for several account, address, contact, order, and quote workflows. Table 6-8 lists the workflows for which you must create integration events and includes the configuration data that you must use:
Table 6-8 Workflows and Integration Events Configuration Fields
| Workflow Name | Action Name/ Queue Name for Integration Event Creation | Trigger Event | Configuration Data |
|---|---|---|---|
|
Account Delete |
Account - Delete Default Queue |
When record is deleted |
No configuration required. |
|
Account Insert |
Account - Insert Default Queue |
When new record is saved |
Select these fields for tracking: Account Currency Account Name Account Type Annual Revenues Main Fax # Main Phone # Number of Employees Public Company Status Integration Status Web Site |
|
Account Update |
Account - Update Default Queue |
When modified record is saved |
Select these fields for tracking: Account Currency Account Name Account Type Annual Revenues Main Fax # Main Phone # Number of Employees Public Company Status Integration Status Web Site |
|
Address Delete |
Address - Delete Default Queue |
When record is deleted |
No configuration required. |
|
Address Insert |
Address - Insert Default Queue |
When new record is saved |
Select these fields for tracking: Address 3 City Country County Description Postal Code Province State Street Address Street Address 2 |
|
Address Update |
Address - Update Default Queue |
When modified record is saved |
Select these fields for tracking: Address 3 City Country County Description PostalCode Province State Street Address Street Address 2 |
|
Contact Insert |
Contact - Insert Default Queue |
When new record is saved |
Select these fields for tracking: Account Id Cellular Phone # First Name Home Phone # Job Title Last Name Middle Name Mr./Ms. Integration Status Work Fax # Work Phone # |
|
Contact Update |
Contact - Update Default Queue |
When modified record is saved |
Select these fields for tracking: Account Id Cellular Phone # First Name Home Phone # Job Title Last Name Middle Name Mr./Ms. Integration Status Work Fax # Work Phone # |
|
Contact Delete |
Contact - Delete Default Queue |
When record is deleted |
No configuration required. |
|
Contact-Account-Assoc |
Contact-Account-Assoc Default Queue |
After association with parent |
No configuration required. |
|
Contact-Account-Disassoc |
Contact-Account-Disassoc Default Queue |
After disassociation with parent |
No configuration required. |
|
Account-Contact-Assoc |
Account-Contact-Assoc Default Queue |
After association with parent |
No configuration required. |
|
Account-Contact-Disassoc |
Account-Contact-Disassoc Default Queue |
After disassociation with parent |
No configuration required. |
|
Account Contact Insert |
Account Contact - Insert Default Queue |
When new record is saved |
Select these fields for tracking: Account ID Contact ID |
|
Account Contact Update |
Account Contact - Update Default Queue |
When modified record is saved |
Select these fields for tracking: Account ID Contact ID |
|
Account Contact Delete |
Account Contact - Delete Default Queue |
When record is deleted |
No configuration required. |
|
Order Insert |
Order - Insert Priority Queue |
When new record is saved |
Select these fields for tracking: Created: Date Currency Description External Flag External System Id Id Modified: Date Order Created Order Creation Status Order Id Order Integration Message Order Num Order Number Order Type |
|
Quote Insert |
Order - Insert Priority Queue |
When new record is saved |
Select these fields for tracking: Created: Date Currency Description External Flag External System Id Id Modified: Date Name Quote Created Quote Creation Status Quote Id Quote Integration Message Quote Num Quote Number Exchange Date |
To define workflow rule conditions:
Log in to CRM On Demand.
On the welcome page, click the Admin.
On the Admin Home page, click the Workflow Configuration link in the Business Process Management section.
On the Workflow Rules List page, to update the workflow rule, click the Edit link next to the it.
On the Workflow Rule Edit page, use the Expression Builder to update the workflow rule condition.
Complete the steps 1 to 5 for the Account - Delete, Account - Insert, and Account - Update workflows.
To create integration events:
Log in to CRM On Demand.
On the welcome page, click the Admin.
On the Admin Homepage, click the Workflow Configuration link in the Business Process Management section.
On the Workflow Rules List page, to update the workflow rule, click it.
On the Workflow Rule Detail page, select Create Integration Event from the Action menu.
On the Workflow Action Edit page, specify the appropriate values for the Action Name field and the Queue Name field, select the Active option and click Save.
Configure the integration event as described in the following procedure:
Access the Workflow Rule Details page for the selected workflow item.
Click the Configure link for the integration event you must configure.
Select the specified fields for tracking, and then click Save.
Administrators require a simple way to review records that have failed to synchronize and take the appropriate corrective action. The List feature for accounts and contacts provides a means for an administrator to generate a list of records for which synchronization has failed.
To set up synchronization failure lists
Log in as an administrator.
For the account and contact objects, complete steps a through f.
Navigate to Object Homepage, Object Lists, and then New.
Replace Object with the name of an object, for example, Contact Homepage.
Set the following criteria:
Field. Integration Status
Condition. Equal to
Filter Value(s). Sync FAILED
Select the following fields for display in the list:
Integration Status
Integration Message
Other fields relevant to the object
Click Save.
Set the following fields:
List Name. Object Sync Failures
List Accessibility. Private
Click Save and Run.
Alerts can be configured within Oracle CRM On Demand such that when a record has failed to synchronize, a designated user receives a failure alert by email that can indicate the record that has failed to synchronize and the reason for failure.
To set up synchronization failure alerts:
Navigate to Admin, Workflow Configuration.
Click New and add the following workflow rule:
In the Action Pane, choose Menu and then Create Email Notification, and then add the following action:
Action Name. Opportunity Sync Failure Alert
Active. Selected
Email Message (To*, Subject*, Message Body*). Specify message details to be sent to your administrator if there is a synchronization failure.
Click New and add the following workflow rule:
Workflow Name. Account Sync Failure Alert
Active. Selected
Record Type. Account
Trigger Event. When Modified Record Saved
Workflow Rule Condition.
[<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_ACCOUNT_0", "Sync FAILED")
In the Action Pane, choose Menu and then Create Email Notification, and add the following action:
Action Name. Account Sync Failure Alert
Active. Selected
Email Message (To*, Subject*, Message Body*). Specify message details to be sent to your administrator if there is a synchronization failure.
Click New and add the following workflow rule:
Workflow Name. Contact Sync Failure Alert
Active. Selected
Record Type. Contact
Trigger Event. When Modified Record Saved
Workflow Rule Condition.
[<plSync_Status_ITAG>]=LookupValue("OCC_CUST_LOV_CONTACT_0", "Sync FAILED")
In the Action Pane, choose Menu and then Create Email Notification, and add the following action:
Action Name. Contact Sync Failure Alert
Active. Selected
Email Message (To*, Subject*, Message Body*). Specify message details to be sent to your administrator if there is a synchronization failure.
All operations including create, read, update, and delete in CRM On Demand are performed by CRM On Demand public web services. For all web service calls to CRM On Demand, a valid session ID is required. As part of the data synchronization architecture, a pool of CRM On Demand sessions is created on demand. Different BPEL processes that make web service calls to CRM On Demand reuse these sessions.
This pool of CRM On Demand sessions in the SOA server are managed by the AIA Common Utility called Session Pool Manager (SPM). SPM manages sessions for multiple instances of CRM On Demand and other Oracle application web servers. Each application web server instance is identified by a host ID. The default host ID for this PIP is CRMOD_01.
For more information about SPM, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager."
Domain value maps (DVMs) are a standard feature of the Oracle SOA Suite that enable you to equate lookup codes and other static values across applications. Examples are "FOOT" and "FT" or "US" and "USA."
DVMs are static in nature, though administrators can add additional maps as needed. Transactional business processes never update DVMs-they only read from them. They are stored in XML files and cached in memory at run time.
These are the DVMs for the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP:
Note:
If you have defined custom values for any picklist fields in CRM On Demand that are to be synchronized to Oracle E-Business Suite, the corresponding DVM must be configured with the required mapping.
Table 6-9 DVMs for Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite
| DVM Type | DVM Column Name | Description |
|---|---|---|
|
ADDRESS_COUNTRYID |
EBIZ_01, COMMON, CRM OD_01 |
Country codes |
|
STATE |
EBIZ_01, COMMON, CRM OD_01 |
State codes |
|
PROVINCE |
EBIZ_01, COMMON, CRM OD_01 |
Province codes |
|
ORDER_SOURCE_ID |
COMMON, EBIZ_01 |
Mapping for multiple sources of Order or Quote |
|
CONTACT_SALUTATION |
EBIZ_01, COMMON, CRM OD_01 |
Salutation (such as Mr., Mrs., and so on) |
|
CUSTOMERPARTY_STATUSCODE |
EBIZ_01, COMMON, CRM OD_01 |
Account status codes |
|
PHONENUMBER_TYPE |
EBIZ_01, COMMON, CRM OD_01 |
Phone number type codes (such as home, work, mobile, fax, and so on) |
|
SITEUSAGE_CODE |
EBIZ_01, COMMON, CRM OD_01 |
Address site usage code (such as bill to, ship to, and so on) |
|
ITEM_TYPE |
EBIZ_01, COMMON, CRM OD_01 |
Mapping of Oracle E-Business Suite Item Types to CRM On Demand Product Types |
|
CURRENCY_CODE |
EBIZ_01, COMMON, CRM OD_01 |
Currency codes |
|
ORDER_STATUS |
EBIZ_01, COMMON, CRM OD_01 |
Order and quote status codes |
|
ORDER_TYPE |
EBIZ_01, COMMON, CRM OD_01 |
Type of order (such as sales order, RMA, quote, and so on) |
|
PRODUCT_STATUS |
EBIZ_01, COMMON, CRM OD_01 |
Product status codes |
|
CUSTOMERPARTY_NUMBERLABEL |
COMMON, EBIZ_01 |
Type of revenue (for example, Annual Revenue) |
For information about additional DVM setup for multi-org implementation, see Appendix C, "Settings for Multi-Org Implementation".
For more information about DVMs, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Understanding Message Transformation, Enrichment, and Configuration," Domain Value Maps.
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.
These are the cross-references for the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP:
Table 6-10 Cross-References for Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite
| Table | Column | Description | Usage |
|---|---|---|---|
|
CUSTOMERPARTY_PARTYID |
EBIZ_01 |
Customer party ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Account ID |
Lookup: populate during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ACCOUNTID |
EBIZ_01 |
Customer account ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Account ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ADDRESSID |
EBIZ_01 |
Address (location) ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Address ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_CONTACTID |
EBIZ_01 |
Contact/Person IDs |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Contact ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ LOCATIONREFID |
EBIZ_01 |
Address (location) ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Address ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ PARTYLOCATIONID |
EBIZ_01 |
Party address ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Address ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ACCOUNT_PHONECOMMID |
EBIZ_01 |
Account phone contact point |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Account ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_ACCOUNT_FAXCOMMID |
EBIZ_01 |
Account fax contact point |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Account ID |
||
|
CUSTOMERPARTY_ACCOUNT_WEBCOMMID |
EBIZ_01 column |
Account email/Web contact points |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Account ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_CONTACT_PHONECOMMID |
EBIZ_01 column |
Contact phone contact point |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Contact ID: HOME Contact ID: WORK Contact ID: MOBILE |
Lookup: populated during customer, sales order, or sales quote flow If this is a contact home phone, then the cross-reference value is Contact Id: Home. If this is a work phone, then the cross-reference value is Contact Id: WORK, and so on. |
|
|
CUSTOMERPARTY_CONTACT_FAXCOMMID |
EBIZ_01 |
Contact's fax contact point |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Contact ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY_CONTACT_EMAILCOMMID |
EBIZ_01 |
Contact email/Web contact point |
Lookup: populated during customer, sales order, or sales quote flow |
|
COMMON |
System-generated GUID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CRM OD_01 |
Contact ID |
Lookup: populated during customer, sales order, or sales quote flow |
|
|
CUSTOMERPARTY _PARTYCONTACTID |
EBIZ_01 |
Party contact IDs |
Lookup during sales order flow, lookup: populated during customer flow |
|
COMMON |
System-generated GUID |
Lookup during sales order flow, lookup: populated during customer flow |
|
|
CRM OD_01 |
Contact ID |
Lookup during sales order flow, lookup: populated during customer flow |
|
|
SALESORDER_ID |
EBIZ_01 |
Sales order ID |
Populated by sales order flow |
|
COMMON |
System-generated GUID |
Populated by sales order flow |
|
|
CRM OD_01 |
Order ID |
Populated by sales order flow |
|
|
SALESORDER_LINEID |
EBIZ_01 |
Sales order line ID |
Populated by sales order flow |
|
COMMON |
System-generated GUID |
Populated by sales order flow |
|
|
CRM OD_01 |
Product revenue ID |
Populated by sales order flow |
|
|
QUOTE_ID |
EBIZ_01 |
Quote ID |
Populated by sales quote flow |
|
COMMON |
System-generated GUID |
Populated by sales quote flow |
|
|
CRM OD_01 |
Quote ID |
Populated by sales quote flow |
|
|
QUOTE_LINEID |
EBIZ_01 |
Quote line ID |
Populated by sales quote flow |
|
COMMON |
System-generated GUID |
Populated by sales quote flow |
|
|
CRM OD_01 |
Quote ID |
Populated by sales quote flow |
|
|
ORGANIZATION_ID |
EBIZ_01 |
Organization/business unit IDs |
Lookup during sales order, sales quote, and customer flow |
|
COMMON |
System-generated GUID |
Lookup during sales order, sales quote, and customer flow |
|
|
CRM OD_01 |
|||
|
ITEM_ITEMID |
EBIZ_01 |
Item/product ID |
Lookup during sales order/sale quote flow Lookup: populated during item flow |
|
COMMON |
System-generated GUID |
Lookup during sales order/sale quote flow Lookup: populate during item flow |
|
|
CRM OD_01 |
Product ID |
Lookup during sales order/sale quote flow Lookup: populate during item flow |
|
|
INVENTORY_LOCATION_ID USER_NAME |
EBIZ_01 |
Org Id |
You must complete this table manually after you have installed the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP. For more information, see Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 |
|
COMMON |
GUID |
You must complete this table manually after you have installed the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP. For more information, see Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 |
|
|
EBIZ_01 |
Ebiz user ID |
Lookup during sales order, sales quote, and customer flow |
|
|
COMMON |
System-generated unique ID |
Lookup during sales order, sales quote, and customer flow |
|
|
CRM OD_01 |
CRM On Demand integration user ID |
Lookup during sales order, sales quote, and customer flow |
For information about the additional cross-reference table setup for multi-org implementation, see Appendix C, "Settings for Multi-Org Implementation".
For more information about cross-references, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite Oracle Fusion Middleware Infrastructure Components and Utilities User11g Release 1, "Understanding Message Transformation, Enrichment, and Configuration," Cross-References.
Based on the roles defined for the services, email notifications are sent if a service ends in error. Table 6-11 lists the errors that are caused by the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP services.
Table 6-11 Errors Caused by Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite
| Error Code | Message Text |
|---|---|
|
AIA_ERR_AIAO2C2_1001 |
Timeout while waiting for a response from the InterfaceCustomerToFulfillmentEBF service. |
|
AIA_ERR_AIAO2C2_1002 |
Timeout while waiting for a response from the InterfaceSalesOrderToCustomerEBFV2 service. |
|
AIA_ERR_AIAEBSI_0001 |
Failed to fetch the Sales Representative Resource ID. Please make sure the Sales Representative email addresses are identical in both systems. |
For more information about the errors caused by CRM On Demand or Oracle E-Business Suite, see that product's documentation.
For more information about AIA error handling, see the Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Setting Up and Using Error Handling and Logging."
The CRM On Demand to Oracle E-Business Suite flows consist of a central error handling process, the CRMOnDemandErrorHandler service. Faults generated from the CRM On Demand requester ABCSs and Oracle E-Business provider ABCS/EBFs (Enterprise Business Flow) are published to the AIA Java Message Service (JMS) error queue. The CRM On Demand error handler service subscribes to the error queue for CRM On Demand requester faults only; the CRM On Demand error handler service then processes each fault according to the type of fault (see retryable and nonretryable faults). The AIA default error handler service subscribes to the error queue for other service faults; the service then processes each fault (regardless of the type of fault) by sending an email to the OracleAIACSR user (see Setup Error Notification Roles and Users) with the content of the fault.
The following steps outline the processing that results if errors occur when information is synchronized from CRM On Demand to Oracle E-Business Suite.
Events are pulled from the CRM On Demand server and sent to middle-tier queues called resequencers.
Resequencers store events in different groups. Account and account address events are grouped by account ID so that the account and address events (for example, create account, update account, create address, update address, and so on) of the same account are stored in one group with account ID as the group ID. Similarly, contact events are grouped by contact ID, and order and quote events are grouped by order ID and quote ID respectively.
For more information about resequencer queues, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1.
The resequencers retrieve each event from the queue, initiate a global transaction to process the event, and route the event to the appropriate CRM On Demand requester to start synchronizing the event to Oracle E-Business Suite.
If a service fails because of a business or system error, then it publishes the fault message to the AIA JMS error queue with one type code:
AIA_EH_ONDEMAND: for CRM On Demand requester services or EBIZ provider services
AIA_EH_DEFAULT: for other services
The error is passed from the service that generated the error to previous calling services until it is received by the CRM On Demand requester. Each service that receives the fault publishes the fault to the AIA JMS error queue with a type code.
When an error occurs, the global transaction initiated by the resequencer is eventually rolled back and the group to which the event belongs becomes blocked. When a group is blocked, any subsequent events from the same group are not processed, although the resequencer can process events for other groups that are not blocked.
The CRM On Demand error handler service subscribes to the JMS error queue if the type code is AIA_EH_ONDEMAND.
After the error is received by the CRM On Demand error handler service, the service determines whether the error is a retryable or non-retryable error:
If an error is retryable, the service sends a notification email with the word SYSTEM in the email subject line, with the fault information, for example, service name, group ID, service ID, and so on.
If an error is not retryable, the service skips the event in the resequencer so that the next event (if any) in the same group can continue to be processed.
It also updates the corresponding CRM On Demand record associated with the event; the Integration Status field is set to Sync FAILED and the Integration Message field is updated with the instance ID of the requester service. A notification email is also sent, but it does not contain the word SYSTEM in the email subject line.
For more information about configuring email addresses to receive these notifications, see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Setting Up and Using Error Handling and Logging"
The installation process takes care of the setting up CRM On Demand Error Handler. Table 6-12 lists the services and their attributes for which the setup is required:
Table 6-12 Services and Attributes for CRM On Demand
| Service Name | System Code | Error Type | Error Ext Handler |
|---|---|---|---|
|
InterfaceCustomerToFulfillmentEBF |
NA |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
InterfaceSalesQuoteToFulfillmentEBF |
NA |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
InterfaceSalesOrderToCustomerEBFV2 |
NA |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
CreateSalesOrderEbizProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
SyncItemListCRMODProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
UpdateCustomerPartyEbizProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
SyncCustomerPartyListEbizProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
CreateSalesQuoteEbizProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
CreateCustomerPartyEbizProvABCSImpl |
EBIZ_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
CreateCustomerAddressCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
CreateCustomerCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
DeleteCustomerAddressCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
UpdateCustomerAddressCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
UpdateCustomerCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
ProcessSalesOrderCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
ProcessContactCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
DeleteCustomerCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
|
ProcessSalesQuoteCRMODReqABCSImpl |
CRMOD_01 |
AIA_EH_ONDEMAND |
ERRORHANDLER_EXT |
Within the Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite PIP, errors are categorized as retryable errors or non-retryable errors.
Retryable errors are system errors. If a retryable error occurs, the original message can be resubmitted by Enterprise Manager 11g Fusion Middleware Control (Oracle Enterprise Manager).
The notification email, sent when a retryable error occurs, contains the string SYSTEM in the email subject line. The email includes a Corrective Action link to it.
When a system error occurs, correct the error, and then resubmit the message in Oracle Enterprise Manager.
The CRM On Demand Error Handling Service identifies an error as a system error by searching the error message text for a specific string or pattern that matches the text for a system error code. The error message text is read from the SysErrorCodes property of the CRMOnDemandErrorHandlerService Service Configuration in the AIAConfigurationProperties.xml file.
The SysErrorCodes property is set as the following string:
<Property name="SysErrorCodes">ORABPEL-11622</Property>
Note:
ORABPEL-11622 indicates that the Oracle E-Business Suite system is down.
The SysErrorCodes property accepts regular expressions (regex). You can edit the regex string by changing the regex pattern to locate system errors that are specific to your environment. For example, if you edit the regex string as follows, any error message that contains the text ORABPEL-02181, ORA320, or any string beginning with SIEBEL-11* is identified as a system error.
<Property name="SysErrorCodes">ORABPEL-11622|ORA320|SIEBEL-11*</Property>
Non-retryable errors (business errors) are generally the result of user errors, for example, incorrect or missing data in a record. These types of error messages are skipped in the resequencer queue, and processing moves to the next message. You should not resubmit non-retryable messages using Oracle Enterprise Manager. You must correct the CRM On Demand record causing the error, and then set the Integration Status field to Sync On. The record is then synchronized again to Oracle E-Business Suite.
About Enterprise Manager for Resubmitting Failed Messages
If a message fails due to a system error (retryable error), it remains in the resequencer and blocks any subsequent messages that belong to the same group. Oracle Enterprise Manager provides means to unlock the locked group and resubmit (or terminate) a failed message.
After fixing the system error, to resubmit a failed message follow these steps:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Locate the resequencer containing the faulted message and click it.
Select Faults and Rejected Messages.
Click Recovery for the faulted message.
A window appears with the message ID and Recovery state.
Click Recoverable.
Click Retry.
The message is resubmitted.
For more information about AIA error handling, see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Setting Up and Using Error Handling and Logging."
Events that are initiated in Oracle E-Business Suite are placed in the Oracle Advanced Queue (AQ) in the Oracle E-Business Suite database under the queue name WF_BPEL_Q. The WF_BPEL_Q queue is located in the WF_BPEL_QTAB queue table. The WF_BPEL_QTAB queue table also maintains a queue, AQ$_WF_BPEL_QTAB_E, for holding messages that have failed due to errors.
Messages that are processed successfully are removed from the WF_BPEL_Q queue. If an error occurs during the message processing, the transaction is rolled back and the AQ messaging system moves the message from the WF_BPEL_Q queue to the AQ$_WF_BPEL_QTAB_E queue.
The PIP installation process creates several consumer adapter services, for example, CreateItemEbizEventConsumer. The consumer services create a subscription to the main business events that are processed in the Oracle E-Business Suite database and these subscriptions add messages to the WF_BPEL_Q queue. The consumer services then read the messages from the WF_BPEL_Q queue.
Administrators can use the message submit utility provided by the AIA Foundation Pack to resubmit failed messages after taking corrective action to resolve the error that caused the message to fail. Resubmitting a message moves the message from the AQ$_WF_BPEL_QTAB_E queue to the WF_BPEL_Q queue so that the message can be reprocessed.
The following procedure describes how to resubmit a message that has failed.
To resubmit a message:
Obtain the message ID for the event that failed from the BPEL Instance:
Open the Error Notification email, which has a subject line similar to this:
Error in AIA UpdateProductEbizReqABCSImpl Process
Open the attachment, which contains the Faulting Service Instance ID.
In the BPEL console, open the BPEL instance for the Faulting Service Instance ID.
In the receiveInput step, note the value of the EVENT_DATA field in the message, for example:
<EVENT_DATA>7342C2350EDEA30DE040B98B97154924<EVENT_DATA>
Log in to the SOA server.
If you are using a Microsoft Windows environment, run the $AIA_HOME\bin\aiaenv.bat file.
If you are using a Linux environment, perform the following steps:
Source $AIA_HOME/bin/aiaenv.sh.
Navigate to the $AIA_HOME/util/AIAMessageResubmissionUtil directory.
Edit the ResubmitBuild.properties file and set the properties listed in Table 6-13 to the respective values:
Table 6-13 Properties for ResubmitBuild.properties field
| Property | Value |
|---|---|
|
jdbc_url |
For the jdbc_url, specify the Oracle E-Business Suite database name using a format similar to this: jdbc:oracle:thin:@<dbhostname>:<dbport>:dbSID |
|
Username |
The Oracle E-Business Suite database schema user name. |
|
Password |
Password. The Oracle E-Business Suite database schema password. |
|
IntermediateSenderResourceTypeCode |
1 |
|
Set IntermediateSenderResourceID |
WF_BPEL_Q |
|
IntermediateSenderMessageID |
The value of the EVENT_DATA field obtained in step 1d. |
|
TableName |
WF_BPEL_QTAB |
Run the following command:
ant -buildfile MessageResubmit.xml
For more information, see the Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack "Using the Message Resubmission Utility".
If a large number of events are generated at a time in Oracle E-Business Suite, Oracle Advanced Queue can contain many messages, which can lead to a decrease in performance. To avoid this situation, you can configure the number of messages that are processed at a time by Oracle Advanced Queue by setting the JAVA VM system property called adapter.aq.dequeue.threads for the server to more than 1 (default).
Oracle recommends that you set the value of the adapter.aq.dequeue.threads property to 5 during the initial batch loading of account and product data.
For more information, see Oracle Fusion Middleware User's Guide for Technology Adapters, 11g, Release 1, "Oracle JCA Adapter for AQ".
To set the Java VM system property:
Log in to the console.
Navigate to Environment, Servers.
In the Servers table, click the name of the Managed Server (for example, soa_server1) to configure.
Select Configuration, Server Start.
Set Dadapter.aq.dequeue.threads=3 for the argument.
Save and restart the Managed Server.
For more information about using XSL Mapping Analyzer (XMAN), see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, Using the XSL Mapping Analyzer.
For more information about how services are mapped, see the My Oracle Support document: EBO Implementation Maps (EIMs) 881022.1.
Configure these properties in the AIAConfigurationProperties.xml file. The file is located in AIA_HOME>/aia_instances/$INSTANCE_NAME/AIAMetaData/config/. Entries in the AIAConfigurationProperties.xml file are case-sensitive.
For more information about requirements for working with AIAConfigurationProperties.xml, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Building AIA Integration Flows," How to Set Up AIA Workstation.
Table 6-14 lists the settings for the system properties:
| Property Name | Value/Default Value | Description |
|---|---|---|
|
EBIZ_01.SERVER_TIMEZONE |
GMT-08:00 |
This is the Oracle E-Business Suite server time zone. Change this value as appropriate. |
Table 6-15 lists the properties for the TransformAppContextEbizService service:
Table 6-15 Properties for the TransformAppContexEbizService Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
TransformAppContextEbizService.Soap.EndpointURL |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/TransformAppContextEbizService/TransformAppContextEbizService |
End point URI of the Ebiz adapter. |
|
TransformAppContextEbizService.EBIZ_01.ResponsibilityDVM |
ORACLE_RESPONSIBILITY |
|
|
TransformAppContextEbizService.DefaultUser |
OPERATIONS |
Default integration user in Oracle E-Business Suite. This user should be able to create the customer, order, and quote in Oracle E-Business Suite. |
|
TransformAppContextEbizService.DefaultOperatingUnit |
204 |
Default operating unit in Oracle E-Business Suite in which the quote or order is created. This should be set to the correct operating unit. |
|
TransformAppContextEbizService.DefaultResponsibility |
Order Management Super User |
Default responsibility for creating the order or quote in Oracle E-Business Suite. This is set in the DefaultUser. This responsibility should be in Oracle E-Business Suite. |
|
Routing.QueryResponsibilityEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the Composite Application Validation System (CAVS) end point. The default value is false, which does not route to CAVS. If set to true, it is routed to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryRespEbizAdapter.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Default.SystemID |
EBIZ_01 |
Ebiz system code such as EBIZ_01, defined in Business Service Repository (BSR) to which data is synced. The system code value present in the Enterprise Business Message (EBM) header of the incoming message takes precedence over this property value. |
|
Routing.QueryRespEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryResponsibilityEbizAdapter/QueryResponsibilityEbizAdapter_ep |
Table 6-16 lists the properties for the BatchLoadCustomerPartyListEbizReqABCSImpl service:
Table 6-16 Properties for the BatchLoadCustomerPartyListEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synchronized. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.BatchLoadCustomerPartyListEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/BatchLoadCustomerPartyListEbizAdapter/BatchLoadCustomerPartyListEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.BatchLoadCustomerPartyListEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/ AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.BatchLoadCustomerPartyListEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.CAVS.End point URI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
ABCSExtension.PreXformCreateABMtoEBMABM |
true/false Default = false |
Governs whether Application Business Connector Service (ABCS) extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeCustEBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-17 lists the properties for the BatchLoadProductEbizReqABCSImpl service:
Table 6-17 Properties for the BatchLoadProductEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
EBIZ_01 |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synchronized. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.QuerySimpleItemBatchLoadAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QuerySimpleItemBatchLoadAdapter/QuerySimpleItemBatchLoadAdapter_ep |
End point URI of Ebiz Adapter. |
|
Routing.QuerySimpleItemBatchLoadAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QuerySimpleItemBatchLoadAdapter.CAVS.EndpointURI |
http://${http.hostname}:${http.port}/AIAValidationSystemServlet/asyncresponse recipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.ItemEBSV2.SyncItemList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.ItemEBSV2.SyncItemList.MessageProcessingInstruction.EnvironmentCode |
Default = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.ItemEBSV2.SyncItemList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponse recipient |
CAVS End point URI, when CAVS is enabled. |
|
ABCSExtension.PreXformABM ToEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeItem EBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
SourceMileStone |
WF_BPEL_Q |
The source AQ Queue from which the batchload messages are coming. |
Table 6-18 lists the properties for the CreateProductEbizReqABCSImpl service:
Table 6-18 Properties for the CreateProductEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
EBIZ_01 |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synchronized. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.QuerySimpleItemAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QuerySimpleItemAdapter/QuerySimpleItemAdapter_ep?WSDL |
End point URI of Ebiz Adapter. |
|
Routing.QuerySimpleItemAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.ItemEBSV2.SyncItemList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the End point specified in the CAVS.EndpointURI property. |
|
Routing.ItemEBSV2.SyncItemList.MessageProcessingInstruction.Environment Code |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.ItemEBSV2.SyncItemList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QuerySimpleItemAdapter.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
BYPASS_ITEMVALIDATIONORG _FLAG |
Y/N Default value=N |
This property controls bypassing the validation of the organization associated with an item against OE:Item Validation Org. By default, the organization associated with an Item is validated against OE:Item Validation Org. |
|
ABCSExtension.PreXformABMToEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeItem EBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
PUBLISH_ALL_PRODUCT |
Y/N Default = N |
Governs whether to synchronize both nonorderable and orderable products (when value is Y) or sync only nonorderable products while performing Item sync (when value is N). |
Table 6-19 lists the properties for the UpdateProductEbizReqABCSImpl service:
Table 6-19 Properties for the UpdateProductEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
EBIZ_01 |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synchronized. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.QuerySimpleItemUpdateAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QuerySimpleItemUpdateAdapter/QuerySimpleItemUpdateAdapter_ep?WSDL |
End point URI of Ebiz Adapter. |
|
Routing.QuerySimpleItemUpdateAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
BYPASS_ITEMVALIDATION ORG_FLAG |
Y/N Default =N |
This property controls bypassing the validation of the organization associated with an item against OE:Item Validation Org. By default, the organization associated with an item is validated against OE:Item Validation Org. |
|
ABCSExtension.PreXformABMToEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeItem EBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
Routing.ItemEBSV2.SyncItemList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.ItemEBSV2.SyncItemList.MessageProcessingInstruction.Environment Code |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.ItemEBSV2.SyncItemList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QuerySimpleItemUpdateAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
Table 6-20 lists the properties for the CreateSalesOrderEbizProvABCSImpl service:
Table 6-20 Properties for the CreateSalesOrderEbizProvABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
EBIZ_01 |
Ebiz system code (such as EBIZ_01, defined in BSR) from which requests originate for this process. |
|
Routing.ProcessSalesOrderEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/ProcessSalesOrderEbizAdapter/ProcessSalesOrderEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.ProcessSalesOrderEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.ProcessSalesOrderEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SalesOrderResponseEBSV2.CreateSalesOrderResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderResponseEBSV2.CreateSalesOrderResponse.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
RMAOrderTypes |
RMA |
This property defines the value for RMA order types. The list of code values that represent RMA order types. This affects the attribute mappings. This is a comma-separated (no spaces) list of string values. |
|
ABCSExtension.PreXformEBMToABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeProcessSOEbizAdapter |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostInvokeProcessSOEbizAdapter |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformABMToEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-in to point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
OrderSourceReference |
COMMON/SourceSystemIdentifier Default=COMMON Change this property to OrderSourceReference so that the Oracle E-Business Suite OSR field contains the value of the opportunity ID from the EBM field as follows: corecom:SourceDocumentReference/corecom:DocumentIdentification/corecom:ContextID[@schemeID="OrderSource Reference"] |
Property to decide whether OSR holds the common ID or source system identifier. |
|
DefaultOrderSourceId |
28 |
Property to supply the ORDER_SOURCE_ID by default if a data value map lookup failure occurs for quotes. |
Table 6-21 lists the properties for the InterfaceSalesOrderToFulfillmentEBF service:
Table 6-21 Properties for the InterfaceSalesOrderToFulfillmentEBF Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
InterfaceSalesOrderToCustomer |
True |
Controls whether the InterfaceSalesOrderToCustomerEBF is invoked during order processing. |
|
InterfaceSalesOrderToCustomerResponseRequired |
True |
Controls whether the InterfaceSalesOrderToCustomerEBF Response is Required during order processing. This must be set to false for the Lead-to-Order: CRM On Demand - Oracle E-Business Suite PIP. The value is set to false during the installation of the PIP. |
|
UpdateSalesOrder |
True |
Governs whether the Update Order operation has to perform to update the sales order in the source system during order processing. This must be set to false for the Lead-to-Order: CRM On Demand - Oracle E-Business Suite PIP. The value is set to false during the installation of the PIP. |
|
UpdateSalesOrder.ResponseRequired |
False |
Governs whether a response is required from UpdateSalesOrder. |
|
RMAOrderTypes |
RMA |
This property defines the value for RMA order types and comprises a list of code values that represent RMA order types. During processing of orders with this type, customer synchronization does not occur. This is a comma-separated (no spaces) list of string values. |
|
InterfaceSalesOrderToCustomer.Async TimeoutDuration |
PT5M30S |
Duration to wait for the asynchronous callback from the InterfaceSalesOrderToCustomer service. If a response is not received within the wait duration, a fault occurs. |
|
CreateSalesOrder.AsyncTimeout Duration |
PT3M |
Duration to wait for the asynchronous CreateSalesOrderResponse callback from the SalesOrderResponseEBS service. If a response is not received within the wait duration, a fault occurs. |
|
CreateSalesOrder.ResponseRequired |
True |
Governs whether response is required from CreateSalesOrder. |
|
UpdateSalesOrder.AsyncTimeout Duration |
PT1M |
Duration to wait for the asynchronous UpdateSalesOrderResponse callback from the SalesOrderResponseEBS service. If a response is not received within the wait duration, a fault occurs. |
|
Routing.SalesOrderEBSV2.CreateSalesOrder.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderEBSV2.CreateSalesOrder.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SalesOrderEBSV2.UpdateSalesOrder.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderEBSV2.UpdateSalesOrder.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SalesOrderOrchestrationEBSV2.InterfaceSalesOrderToCustomer.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderOrchestrationEBSV2.InterfaceSalesOrderToCustomer.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SalesOrderOrchestrationResponseEBSV2.InterfaceSalesOrderToFulfillmentResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderOrchestrationResponseEBSV2.InterfaceSalesOrderToFulfillmentResponse.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
isLegacyEbizProviderSupported |
True/false Default-false |
This must be set to true for the Lead-to-Order: CRM On Demand - Oracle E-Business Suite PIP. The value is set to true during the installation of the PIP. |
|
SyncSalesOrder.ResponseRequired |
True |
Governs whether response is required from SyncSalesOrder. |
|
SyncSalesOrder.AsyncTimeoutDuration |
PT3M |
Governs the duration to wait for the response. |
|
Routing.SalesOrderEBSV2.SyncSalesOrderList.RouteToCAVS |
True/false Default=false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderEBSV2.SyncSalesOrderList.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
Table 6-22 lists the properties for the InterfaceSalesOrderToCustomerEBFV2 service:
Table 6-22 Properties for the InterfaceSalesOrderToCustomerEBFV2 Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Routing.SalesOrderOrchestrationResponseEBSV2.InterfaceSalesOrderToCustomerResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesOrderOrchestrationResponseEBSV2.InterfaceSalesOrderToCustomerResponse.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
InterfaceCustomerToFulfillment.AsyncTimeoutDuration |
PT5M |
Duration to wait for the asynchronous InterfaceCustomerToFulfillmentResponse callback from the SalesOrderOrchestrationResponseEBS service. If a response is not received within the wait duration, a fault occurs. |
|
InterfaceCustomerToFulfillmentResponseRequired |
True |
Governs whether the InterfaceCustomerToFulfillment Response is Required. This must be set to false for the Lead-to-Order: CRM On Demand - Oracle E-Business Suite PIP. The value is set to false during the installation of the PIP. |
|
Routing.CustomerPartyOrchestrationEBSV2.InterfaceCustomerToFulfillment.RouteToCAVS |
true/false Default=false |
Governs whether the service routes the message to the CAVS. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyOrchestrationEBSV2.InterfaceCustomerToFulfillment.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
Table 6-23 lists the properties for the InterfaceCustomerToFulfillmentEBF service:
Table 6-23 Properties for the InterfaceCustomerToFulfillmentEBF Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
InterfaceCustomerToFulfillment |
true/false Default = true |
Standard properties to control EBF functionality. |
|
ProcessCustomerPartyList |
true/false Default = true |
Standard properties to control EBF functionality. |
|
SyncCustomerPartyList.AsyncTimeoutDuration |
Default value = PT5M |
Specifies the time for which the service waits to receive a response. If a response is not received within this time, the process times out and terminates. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyEBSV2.QueryCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBSV2.QueryCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CustomerPartyEBSV2.QueryCustomerPartyList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
SyncCustomerPartyListResponseRequired |
True/false Default = true |
Governs whether a response is required from SyncCustomerPartyList. This must be set to false for the Lead-to-Order: CRM On Demand - Oracle E-Business Suite PIP. The value is set to false during the installation of the PIP |
|
Routing.CustomerPartyOrchestrationResponseEBSV2.InterfaceCustomerToFulfillmentResponse.MessageProcessingInstruction.EnvironmentCode |
Default = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyOrchestrationResponseEBSV2.InterfaceCustomerToFulfillmentResponse.RouteToCAVS |
True/false Default=false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyOrchestrationResponseEBSV2.InterfaceCustomerToFulfillmentResponse.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
Table 6-24 lists the properties for the SyncCustomerPartyListEbizReqABCSImpl service:
Table 6-24 Properties for the SyncCustomerPartyListEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) from which requests originate for this process. |
|
Routing.QueryCustomerPartyListEbizCreate.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryCustomerPartyListEbizCreate.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryCustomerPartyListEbizCreateAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryCustomerPartyListEbizCreateAdapter/QueryCustomerPartyListEbizCreateAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryCustomerPartyListEbizUpdate.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryCustomerPartyListEbizUpdate.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryCustomerPartyListEbizUpdateAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryCustomerPartyListEbizUpdateAdapter/QueryCustomerPartyListEbizUpdateAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyEBSV2.SyncCustomerPartyList.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
ABCSExtension.PreXformCreateABMtoEBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreXformUpdateABMtoEBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeCustEBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
SyncAllContactRelationshipTypes |
true/false Default = false. Recommended value = true |
Allows the integration to synchronize "account contacts" created for relationships when the RELATIONSHIP_TYPE is different to Organization-Contact. For example, "Employment". Set this property to true if you have or use account contacts with a relationship that is not of Organization-Contact type. |
Table 6-25 lists the properties for the MergeAccountEbizReqABCSImpl service:
Table 6-25 Properties for the MergeAccountEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) from which requests originate for this process. |
|
Routing.QueryMergeAccountEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryMergeAccountEbizAdapter/QueryMergeAccountEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryMergeAccountEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryMergeAccountEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryCustomerPartyEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryCustomerPartyEbizAdapter/QueryCustomerPartyEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryCustomerPartyEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryCustomerPartyEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
ABCSExtension.PreXformSyncAcctABMToEBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreXformMergeAcctABMToEBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeCustPartyEBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-26 lists the properties for the MergePartyEbizReqABCSImpl service:
Table 6-26 Properties for the MergePartyEbizReqABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) from which requests originate for this process. |
|
Routing.QueryPartyMergeEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryPartyMergeEbizAdapter/QueryPartyMergeEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryPartyMergeEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryPartyMergeEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryMergeOrgCustEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryMergeOrgCustEbizAdapter/QueryMergeOrgCustEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryMergeOrgCustEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryMergeOrgCustEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.QueryRelatedOrgCustEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryRelatedOrgCustEbizAdapter/QueryRelatedOrgCustEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.QueryRelatedOrgCustEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryRelatedOrgCustEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyEBS.SyncCustomerPartyList.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
ABCSExtension.PreXformABMTo EBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreXformRelatedABM ToEBMABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeSync CustomerPartyEBSEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-27 lists the properties for the SyncCustomerPartyListEbizProvABCSImpl service:
Table 6-27 Properties for the SyncCustomerPartyListEbizProvABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Routing.SyncCustomerPartyListPersonEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/SyncCustomerPartyListPersonEbizAdapter/SyncCustomerPartyListPersonEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.SyncCustomerPartyListPersonEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synced. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.SyncCustomerPartyListEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/SyncCustomerPartyListEbizAdapter/SyncCustomerPartyListEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.SyncCustomerPartyListEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SyncCustomerPartyListEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SyncCustomerPartyListPersonEbizAdapter.RouteToCAVS |
False |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.SyncCustomerPartyListResponse.MessageProcessingInstruction.Environment Code |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyResponseEBSV2.SyncCustomerPartyListResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.SyncCustomerPartyListResponse.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
ABCSExtension.PreXformEBMto ABMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeEbizAdapter ABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostInvokeEbizAdapterABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformABMto EBMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-28 lists the properties for the InterfaceSalesQuoteToFulfillmentEBF service:
Table 6-28 Properties for the InterfaceSalesQuoteToFulfillmentEBF Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
InterfaceSalesQuoteToCustomer |
true/false |
The default value is true. Controls whether the InterfaceQuoteToCustomerEBF is invoked during Quote processing. |
|
InterfaceSalesQuoteToCustomer ResponseReq |
true/false |
The default value is false. Controls whether to wait for a response from the InterfaceQuoteToCustomerEBF. If set to true, then the global transaction commits at the point. |
|
InterfaceSalesQuoteToCustomer.Async TimeoutDuration |
Duration (for example, 'PT5M30S' represents 5 min, 30 seconds) |
Duration to wait for the asynchronous callback from the InterfaceSalesQuoteToCustomer service. If a response is not received within the wait duration, a fault occurs. |
|
CreateSalesQuote.AsyncTimeoutDuration |
Duration (for example, 'PT5M30S' represents 5 min, 30 seconds) |
Duration to wait for the asynchronous CreateSalesQuoteResponse callback from the SalesQuoteResponseEBS service. If a response is not received within the wait duration, a fault occurs. |
|
Routing.SalesQuoteEBS.CreateSalesQuote.RouteToCAVS |
true/false |
Enable/disable CAVS. |
|
Routing.SalesQuoteEBS.CreateSalesQuote.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS End point URL with optional simulator ID included in the query string. |
|
Routing.SalesQuoteOrchestrationEBS.InterfaceSalesQuoteToCustomer.RouteToCAVS |
true/false |
Enable/disable CAVS. |
|
Routing.SalesQuoteOrchestrationEBS.InterfaceSalesQuoteToCustomer.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS End point URL with optional simulator ID included in the query string. |
|
Routing.SalesQuoteOrchestrationResponseEBS.InterfaceSalesQuoteToFulfillmentResponse.RouteToCAVS |
true/false |
Enable/disable CAVS. |
|
Routing.SalesQuoteOrchestrationResponseEBS.InterfaceSalesQuoteToFulfillmentResponse.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS End point URL with optional simulator ID included in the query string. |
Table 6-29 lists the properties for the CreateCustomerPartyEbizProvABCSImpl service:
Table 6-29 Properties for the CreateCustomerPartyEbizProvABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synced. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.CreateCustomerPartyEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/SyncCustomerPartyListEbizAdapter/SyncCustomerPartyListEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.CreateCustomerPartyEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CreateCustomerPartyEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.CreateCustomerPartyResponse.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyResponseEBSV2.CreateCustomerPartyResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.CreateCustomerPartyResponse.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
ABCSExtension.PreXformEBMtoABMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeEbizAdapterABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostInvokeEbizAdapterABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformABMtoEBMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreXformEBMtoPersonABMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformPersonABMtoEBMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-30 lists the properties for the UpdateCustomerPartyEbizProvABCSImpl service:
Table 6-30 Properties for the UpdateCustomerPartyEbizProvABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
No default value |
Ebiz system code (such as EBIZ_01, defined in BSR) to which data is synced. The system code value present in the EBM header of the incoming message takes precedence over this property value. |
|
Routing.SyncCustomerPartyListEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/SyncCustomerPartyListEbizAdapter/SyncCustomerPartyListEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.SyncCustomerPartyListEbizAdapter.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.SyncCustomerPartyListEbizAdapter.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.UpdateCustomerPartyResponse.MessageProcessingInstruction.EnvironmentCode |
Default value = PRODUCTION |
Governs whether the message is routed to CAVS or to the specified target service. The default value is PRODUCTION, which routes to the target service. |
|
Routing.CustomerPartyResponseEBSV2.UpdateCustomerPartyResponse.RouteToCAVS |
true/false Default = false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.CustomerPartyResponseEBSV2.UpdateCustomerPartyResponse.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncrequestrecipient |
CAVS end point URI, when CAVS is enabled. |
|
ABCSExtension.PreXformEBMtoABMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreInvokeEbizAdapterABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostInvokeEbizAdapterABM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformABMtoEBMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PreXformEBMtoPersonABMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
|
ABCSExtension.PostXformPersonABMtoEBMEBM |
true/false Default = false |
Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked. |
Table 6-31 lists the properties for the InterfaceSalesQuoteToCustomerEBF service:
Table 6-31 Properties for the InterfaceSalesQuoteToCustomerEBF Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Routing.SalesOrderOrchestrationEBSV2.InterfaceCustomerToFulfillment.RouteToCAVS |
true/false |
Enable/disable CAVS. |
|
Routing.SalesOrderOrchestrationEBSV2.InterfaceCustomerToFulfillment.CAVS.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponsesimulator |
CAVS End point URL with optional simulator ID included in the query string. |
|
Routing.SalesQuoteOrchestrationResponseEBS.InterfaceSalesQuoteToCustomerResponse.RouteToCAVS |
true/false |
Enable/disable CAVS. |
|
Routing.SalesQuoteOrchestrationResponseEBS.InterfaceSalesQuoteToCustomerResponse.CAVS.End point URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/asyncresponserecipient |
CAVS End point URL with optional simulator ID included in the query string. |
|
InterfaceCustomerToFulfillment.AsyncTimeoutDuration |
Duration (for example, 'PT5M30S' represents 5 min, 30 seconds) |
Duration to wait for the asynchronous InterfaceCustomerToFulfillmentResponse callback from the SalesQuoteOrchestrationResponseEBS service. If a response is not received within the wait duration, a fault occurs. |
Table 6-32 lists the properties for the CreateSalesQuoteEbizProvABCSImpl service:
Table 6-32 Properties for the CreateSalesQuoteEbizProvABCSImpl Service
| Property Name | Value/Default Value | Description |
|---|---|---|
|
Default.SystemID |
EBIZ_01 |
Ebiz system code (such as EBIZ_01, defined in BSR) from which requests originate for this process. |
|
Routing.ProcessSalesOrderEbizAdapter.RouteToCAVS |
true/false |
Governs whether the service routes the message to the CAVS. The default is false. |
|
Routing.ProcessSalesOrderEbizAdapter.CAVS.EndpointURI |
http:// ://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.ProcessSalesOrderEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/ProcessSalesOrderEbizAdapter/ProcessSalesOrderEbizAdapter_ep |
End point URI of the Ebiz adapter. |
|
Routing.CreateSalesQuoteEbizAdapter.RouteToCAVS |
true/false |
Governs whether the service routes the message to the CAVS. The default is false. |
|
Routing.CreateSalesQuoteEbizAdapter.CAVS.EndpointURI |
http:// ://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/ syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.CreateSalesQuoteEbizAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/CreateSalesQuoteEbizAdapter/CreateSalesQuoteEbizAdapter_ep</Property |
End point URI of the Ebiz adapter. The end point URI depends on the EBIZ system (EBIZ_01) version. If the EBIZ system is 11.5.10, use http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/CreateSalesQuoteEbizAdapter/CreateSalesQuoteEbizAdapter_ep, which is the default. If the EBIZ system is R12.1.1 and above use http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/CreateSalesQuoteEbizAdapter/CreateSalesQuoteEbizR12VersionAdapter_ep. |
|
Routing.QueryJTFResourceSalesPersonAdapter.RouteToCAVS |
true/false |
Governs whether the service routes the message to the CAVS. The default is false. |
|
Routing.QueryJTFResourceSalesPersonAdapter.CAVS.EndpointURI |
http:// ://<SOA_HOST>:<SOA_PORT>/AIAValidationSystemServlet/syncresponsesimulator |
CAVS end point URI, when CAVS is enabled. |
|
Routing.QueryJTFResourceSalesPersonAdapter.EBIZ_01.EndpointURI |
http://<SOA_HOST>:<SOA_PORT>/soa-infra/services/default/QueryJTFResourceSalesPersonAdapter/QueryJTFResourceSalesPersonAdapter_ep |
End point URI of the Ebiz adapter for the Query JTF resource sales person. |
|
Routing.SalesQuoteResponseEBS.CreateSalesQuoteResponse.RouteToCAVS |
true/false |
Governs whether the service routes the message to the CAVS end point. The default value is false, which does not route to CAVS. If set to true, it routes to CAVS using the end point specified in the CAVS.EndpointURI property. |
|
Routing.SalesQuoteResponseEBS.CreateSalesQuoteResponse.CAVS.Endpoint URI |
http://<SOA_HOST>:<SOA_PORT>/AIAValidationSystem Servlet/asyncresponserecipient |
CAVS end point URI, when CAVS is enabled. |
|
ABCSExtension.PreProcessEBM |
true/false |
The default is false. Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked before transforming the Request EBM to ABM. |
|
ABCSExtension.PreProcessABM |
true/false |
The default is false. Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked before invoking the ABS. |
|
ABCSExtension.PostProcessABM |
true/false |
The default is false. Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked before transforming the ABM to EBM. |
|
ABCSExtension.PostProcessEBM |
true/false |
The default is false. Governs whether ABCS extension is enabled at the predefined plug-into point. If set to true, then the Extension process (defined along AIA ABCS extension guidelines) is invoked before invoking the response. |
|
TRACE.LOG.ENABLED |
true/false |
The default is false. Controls the Trace log creation. |
|
DefaultQuoteSourceId |
integer |
The default is 29. Property to supply the ORDER_SOURCE_ID by default if a data value map lookup failure exists for quotes. |
|
CRMQuoteProvider |
true/false |
The default is true. Controls whether to create CRM Quote or OM Quote in Oracle E-Business Suite. |
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
