13 Reviewing Prerequisites and Data Requirements

This chapter provides prerequisites and data requirements for initial data loads and each of the process integration flows.

This chapter includes the following sections:

• Section 13.1, "Initial Data Loads: Prerequisites"

• Section 13.2, "Customer Management: Prerequisites and Data Requirements"

• Section 13.3, "Product Management: Prerequisites and Data Requirements"

• Section 13.4, "Price Lists: Prerequisites"

• Section 13.5, "Quotes: Prerequisites and Data Requirements"

• Section 13.6, "Available to Promise Check: Prerequisites and Data Requirements"

• Section 13.7, "Shipping Charges: Prerequisites and Data Requirements"

• Section 13.8, "Credit Check: Prerequisites and Data Requirements"

• Section 13.9, "Payment Authorization: Prerequisites and Data Requirements"

• Section 13.10, "Order Management: Prerequisites and Data Requirements"

• Section 13.11, "Asset Management: Prerequisites and Data Requirements"

13.1 Initial Data Loads: Prerequisites

Before proceeding with the data loads, ensure that:

• The Siebel CRM Integration Pack for Oracle Order Management pre-built integration is installed.

• Oracle Data Integrator (ODI) is installed on the same computer as AIA_HOME.

• ODI master and work repositories are created.

• Siebel is installed on Oracle, and users can access the Siebel base tables and Enterprise Integration Manager (EIM) tables for account, product, asset, and price list.

• If there are any schema changes on the Siebel side for mandatory columns, then they must be included in the sample ifb files provided so that the EIM jobs on the Siebel side run successfully.

• A database sequence with the name AIA_BULK_LOAD_SEQ is created in the target Siebel database schema. Use this SQL command to create the sequence CREATE or REPLACE sequence AIA_BULK_LOAD_SEQ.

• A database sequence with the name AIA_BULK_LOAD_SEQ is created in the intermittent target Xref database schema. Use this SQL command to create the sequence CREATE sequence AIA_BULK_LOAD_SEQ

• For pricelist initial load, QP_CRMINTEG_PRICELIST_V retrieves records for the pricing organization setup in the profile option QP: Item Validation Organization at the site level. This profile option must be setup with the organization for which pricing data has to be retrieved.

13.2 Customer Management: Prerequisites and Data Requirements

This section discusses the prerequisites and data requirements for the Customer Management process integration flow.

13.2.1 Prerequisites

The process integration for customer management does not depend on other processes being run; however, the Organization cross-reference must be set up first.

For more information about setting up cross-references, see Chapter 15, "Configuring the Order to Cash Pre-Built Integration."

13.2.2 Data Requirements

The process integration for customer management data requirements are:

• The Siebel Customer Relationship Management (Siebel CRM) business units and Oracle E-Business Suite (Oracle EBS) operating units must be mapped as described in Chapter 15, "Configuring the Order to Cash Pre-Built Integration."

• Oracle EBS profile options must be specified.

• The contact associated with the order must have the same account associated with it.

• Specify the contact name on the Payments tab of the Sales Order screen.

• The address must include address line 1, city, state, and zip code.

• Different organization parties cannot share locations in Oracle EBS, though they can share addresses between accounts in Siebel CRM. Therefore, the address should be re-created in Siebel CRM.

• In Oracle EBS, 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, the contact should not be associated at the account site (address) level.

• If the contact used in Siebel CRM during Order submit is associated with multiple accounts and contact points (phone numbers or email address) are present, then Order submit is not supported because the Oracle EBS API for contact update or create does not support shared contact points.

For more information about setting up Siebel organizations and about Oracle EBS operating units and profile options, see Chapter 15, "Configuring the Order to Cash Pre-Built Integration."

13.3 Product Management: Prerequisites and Data Requirements

This section discusses the prerequisites and data requirements for the Product Management process integration flow.

13.3.1 Prerequisites

The process integration for product management does not have a dependency on other processes; however, the following steps should be performed:

• Set up organization cross-references.

• Set up inventory location cross-references.

For more information about setting up the organizations and cross-references, see Chapter 15, "Configuring the Order to Cash Pre-Built Integration."

13.3.2 Data Requirements

The process integration for product management has the following data requirements:

1. The Item Name field in Oracle EBS consists of concatenated key flexfield segments. It cannot exceed 50 characters in length.

2. Do not use special characters, such as &, in the Oracle EBS item name field definition.

3. For an Item to be synchronizable from Oracle EBS:

   • It must have a Customer Orderable Flag

   • The Item Type value must be either Model, Option Class, or Standard

   • The Item must belong to an Oracle EBS Item Validation Org.

4. The unique key to product in Siebel CRM is product name, organization (business unit), and vendor account (not mapped in this integration). The organization name in Siebel CRM must be unique. Siebel CRM supports duplicate product names across organizations but not within an organization.

13.4 Price Lists: Prerequisites

This section discusses prerequisites for the Price List process integration flow.

13.4.1 Prerequisites

The prerequisite for the process integration for price lists is to run the product synchronization flow.

For more information about product synchronization, see Chapter 4, "Process Integration for Product Management."

13.5 Quotes: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Quotes process integration flow.

13.5.1 Prerequisites

The prerequisites for the process integration for quotes integration are:

• Product synchronization.

• Pricing synchronization.

For more information, see Chapter 4, "Process Integration for Product Management." and Chapter 5, "Process Integration for Price Lists."

13.5.2 Data Requirements

This list indicates the mandatory information that must be provided to make this flow successful:

• The Quotes integration flow must have a minimum of one quote line item, and the quote line item must have a product synchronized from the back office.

• The quote must have valid customer information details, including account, billing and shipping address, and contact information.

13.6 Available to Promise Check: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Available to Promise (ATP) Check process integration flow.

13.6.1 Prerequisites

The prerequisite for the ATP Check integration flow is product synchronization.

For more information about the product synchronization flow, see Chapter 4, "Process Integration for Product Management."

13.6.2 Data Requirements

This list indicates the mandatory information that must be provided to make this flow successful:

• Order has at least one line item.

• The quantity on the order line is greater than zero.

• A product that has been synchronized from Oracle EBS is specified.

• A valid requested delivery date is specified.

13.7 Shipping Charges: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Shipping Charges process integration flow.

13.7.1 Prerequisites

The prerequisites for the shipping charges integration flow are:

1. The glog.integration.remoteQuery.wrapReplyInTransmission property must be set for OTM 5.5 CU5.

   For more information about setting this property, see Section 15.12, "Setting a Property in OTM."

2. Product synchronization.

   For more information about the product synchronization flow, see Chapter 4, "Process Integration for Product Management."

13.7.2 Data Requirements

The data requirements for the shipping charges integration flow are:

• Order has at least one line item.

• The order line item has a valid product.

• The product weight is specified.

• The source and target addresses are specified.

• The source inventory location is specified.

13.8 Credit Check: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Credit Check process integration flow.

13.8.1 Prerequisites

The prerequisite for the Credit Check integration flow is product synchronization.

For more information about product synchronization, see Chapter 4, "Process Integration for Product Management."

13.8.2 Data Requirements

This list indicates the mandatory information that must be provided to make this flow successful:

• Payment method is Purchase Order.

• Order has account information.

• Transaction amount is greater than zero.

• Order has at least one line item.

• Order quantity is greater than zero.

13.9 Payment Authorization: Prerequisites and Data Requirements

This section discusses perquisites and data requirements for the Payment Authorization process integration flow.

13.9.1 Prerequisites

For the Payment Authorization flow to work, the iPayment application must be configured properly.

For more information about iPayment, see the product documentation.

13.9.2 Data Requirements

This list indicates the mandatory information that must be provided to make the flow successful:

• Valid credit card data.

• Order has one line item, and quantity is greater than zero.

• Transaction amount is greater than zero.

13.10 Order Management: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Order Management process integration flow.

13.10.1 Prerequisites

The prerequisites for the process integration for order management are:

• Product synchronization.

• Account synchronization.

• Price List synchronization (optional).

• Organization cross-reference setup.

For more information about these process integrations, see Chapter 13, "Reviewing Prerequisites and Data Requirements," Chapter 4, "Process Integration for Product Management," and Chapter 5, "Process Integration for Price Lists."

13.10.2 Data Requirements

The process integration for order management has the following data requirements:

1. The order must be of the type Sales Order.

2. The sales order must contain account, billing and shipping address, and shipping contact.

3. Orders are submitted with the Booked status.

4. If Price List integration is implemented, the price list name must be specified on the order header.

5. Only one payment type can be used for the entire order.

6. If an order line is revised or canceled, a change reason value must be provided at the line-level. The default value is No Reason.

7. If the entire order is being canceled, the cancel reason must be provided at the order header-level.

13.11 Asset Management: Prerequisites and Data Requirements

This section discusses prerequisites and data requirements for the Asset Management process integration flow.

13.11.1 Prerequisites

The cross-business process functional prerequisites for asset integration are:

• Product synchronization.

• Customer Account synchronization.

For more information about these process integrations, see Chapter 3, "Process Integration for Customer Management" and Chapter 4, "Process Integration for Product Management."

13.11.2 Data Requirements

Product and customer data must be synchronized for the asset integration flow to work properly.