B Organization Data Setup for Product Synchronization

For the product synchronization from Oracle E-Business Suite (Oracle EBS) to Siebel Customer Relationship Management (Siebel CRM) to execute as designed, certain entities must be established appropriately in the participating applications. This appendix discusses organization definitions and relationships in participating applications, Oracle Application Integration Architecture (Oracle AIA) mapping, and Order to Cash product synchronization behavior.

As part of the business flow of the Order to Cash: Siebel CRM - EBS pre-built integration, the primary objective of synchronizing items from Oracle EBS to products in Siebel CRM is to enable a customer service representative (CSR) to place an order in Siebel CRM for these products and for the Order flow to submit this order in Oracle EBS.

This appendix contains the following sections:

Section B.1, "Organization Definitions and Relationships in the Participating Applications"
Section B.2, "Oracle AIA Mapping"
Section B.3, "Order to Cash Product Synchronization Behavior"

B.1 Organization Definitions and Relationships in the Participating Applications

This section discusses the definitions and relationships of organizations in the following participating applications:

Oracle EBS
Siebel CRM

B.1.1 Oracle EBS

This section discusses these definitions and relationships of the organizations in Oracle EBS:

Operating Units
Inventory Organizations
Item Master Organization
Item Validation Organization

Operating Units: An operating unit is a logical organization within a company that the company management decides to operate. Order transactions are owned by the operating unit organizations.

The transactions for an operating unit are restricted to using the reference data for that same operating unit. That is, all the sales orders (transactional entities) are not only owned by the operating unit on the transaction side, but the reference data is also owned (namely, customer accounts) or associated (namely, items).

Inventory Organizations: Inventory organizations represent manufacturing and storage facilities. Each inventory organization belongs to one parent operating unit. Oracle implements storage facilities, warehouses, and distribution centers in inventory organizations.

Item Master Organization: There can be many inventory organizations in Oracle EBS and one of them is identified with the role of Item Master Organization.

Note:

It is a best practice in an Oracle EBS implementation to have only one master organization, even though technically it may be possible to have multiple master organizations.

Items are the first to be set up and defined in this item master organization. An item master organization holds a single definition of items that can be shared across many inventory organizations.

The unique key to identify an item in Oracle EBS is Inventory Item Id and Inventory Organization.

Item Validation Organization: In the Order Management module, there is a system parameter called Item Validation Organization defined at the operating-level. This is the inventory organization used by Order Management to validate items when orders are placed against that operating unit. Therefore, when the items are defined, they must be associated to this inventory organization. The OE: Item Validation Organization is also called Item Validation Org.

Because the master organization is an inventory organization, the master organization might also be identified as the item validation org for an operating unit.
The same inventory organization can be the item validation org. for multiple operating units.
The Operating Unit to Item Validation Org. relationship is different from Parent Operating Unit to Inventory Organization relationship. Although in certain implementations, the customers may choose to designate an inventory organization as the item validation org. for an operating unit (OU), where this operating unit also happens to be the parent operating unit for this inventory organization.
Only the items that are associated with the inventory organization that are also established as item validation org. are visible in the respective operating unit when an order is placed in the same.

B.1.2 Siebel CRM

This section discusses these definitions and relationships of the organizations in Siebel CRM:

Business Units
Inventory Locations

Business Units: The business unit organization in Siebel CRM allows the implementation company to partition itself into logical groups. This allows the information associated with the business unit to be visible only to the end-users associated to that business unit (BU).

The transaction data in Siebel CRM (that is, Sales Order), is always associated to the primary business unit. In Siebel CRM, although an order is associated to a specific business unit, products from different business units can be associated on the order lines. In other words, unlike Oracle EBS, the reference data for a transaction can belong to a different organization in Siebel CRM.

A product in Siebel CRM is always associated with a business unit, which becomes its primary business unit. Multiple business units can also be associated with a product.

The unique key to a product in Siebel CRM is Product Name, Business Unit, and Vendor Account (optional - not mapped).

Inventory Locations: Inventory locations in Siebel CRM are used to identify where products are stored, and the source from which the product is fulfilled. An inventory location may be a warehouse, a field office, or it may be virtual location. An inventory location is also associated to a business unit.

Note:

In Siebel CRM there is no equivalent of the Oracle EBS item master organization or item validation organization.

B.2 Oracle AIA Mapping

This section discusses:

Organization mapping
Inventory location mapping

B.2.1 Organization Mapping

The concepts of business units in Siebel CRM, and operating units in Oracle EBS map directly. Therefore, the existence of one-to-one mapping for them across the applications in the Order to Cash: Siebel CRM - EBS pre-built integration is assumed. See Table B-1 for an example.

For more information about how to set up an organization cross-reference mapping, see Section B.3, "Order to Cash Product Synchronization Behavior."

Table B-1 Organization Mapping Example

Siebel CRM Business Unit	Oracle EBS Operating Unit	Oracle AIA
S_BU1	O_OU_1	AIA_1
S_BU2	O_OU_2	AIA_2
S_BU3	O_OU_3	AIA_3

Many operating units can be defined in Oracle EBS, or multiple business units defined in Siebel CRM. However, from an order processing perspective, only specific business units and operating units must be mapped in the cross-reference where order capture is performed in Siebel CRM and the corresponding fulfillment in Oracle EBS.

B.2.2 Inventory Mapping

There can be multiple inventory organizations in Oracle EBS for an item. However, from an order capture perspective, only those inventory organizations that are associated as item validation organizations for the item in Oracle EBS should be defined as inventory locations in Siebel CRM.

The business unit of the inventory location being created in Siebel CRM should be mapped to the operating unit of the item validation org. in Oracle EBS.

Note:

The INVENTORY_LOCATION_ID XREF has an additional attribute SEBL_01_INVLOC_BU, to capture the primary business unit in Siebel CRM for a given inventory location. It is optional, and must be set up only if the item validation organization is shared by multiple operating units. In such cases, the primary business unit for the inventory location must be defined.

For more information about this use case, see Order to Cash Product Synchronization Behavior, Section B.3.2, "Scenario #2: The Item Validation Org. is Shared Across Multiple Operating Units" and Section B.3.3, "Scenario #3: The Item Master Organization is the Item Validation Org. and Shared Across Multiple Operating Units."

Figure B-1 illustrates the logical data mapping for Oracle EBS to Siebel CRM:

Figure B-1 Product Integration: Oracle EBS to Siebel CRM Logical Data Map

B.3 Order to Cash Product Synchronization Behavior

This section discusses cases when an item in Oracle EBS is synchronized as a product in Siebel CRM. Also included are the following best practice scenarios about how to set up the organization cross-reference mappings:

Section B.3.1, "Scenario #1: Each Operating Unit has a Distinct (Non-Shared) Item Validation Org."
Section B.3.2, "Scenario #2: The Item Validation Org. is Shared Across Multiple Operating Units"
Section B.3.3, "Scenario #3: The Item Master Organization is the Item Validation Org. and Shared Across Multiple Operating Units"

An item from Oracle EBS is synchronized as a product in Siebel CRM:

For every item Id and inventory organization combination in Oracle EBS only where the inventory organization also happens to be an item validation organization. Therefore, not all combinations of item Id and inventory organization Id from Oracle EBS creates a unique product in Siebel CRM.
The Siebel CRM product's business unit corresponds to the Oracle EBS operating unit that has the inventory organization as the item validation organization.

If in Oracle EBS, the item is associated to multiple operating units by distinct (non-shared) item validation orgs, then the item records associated with the item validation orgs in all these multiple operating units are synchronized, and cross-references created. Therefore, in Siebel CRM the same product is created for different business units individually.
Because the item validation org. can be shared across multiple operating units in Oracle EBS, all of the corresponding business units may have to be associated to the product in Siebel CRM. This depends on how product visibility is set up in Siebel CRM. If catalog-based (enterprise-level) visibility is set up in Siebel CRM, then associating additional business units may not be required. However, if organization-based visibility is set up in Siebel CRM for products, then the additional non-primary (multi-org) business unit must be manually associated to the product.
If the master organization is also the item validation org, then those item records with the master organization Ids are synchronized, and the cross-reference created. If the master organization is not the item validation org, then the item records with the master organization are ignored for creating the cross-reference.

Based in the previous information, there can be various combinations of organization setup and Item and product definition across the two applications. This appendix provides a few best practice scenarios about how to set up the organization cross-reference mappings, and based on this setup how product synchronization to Siebel CRM takes place. How the product cross-reference is established is also described.

Note:

There may be other setup options that you make that may not be supported and therefore, may require customization.

B.3.1 Scenario #1: Each Operating Unit has a Distinct (Non-Shared) Item Validation Org.

The scenario description is:

Only one master organization exists in Oracle EBS. All items are defined in the master organization.
Each operating unit is associated with a distinct item validation org. In other words, item validation org. is not shared across operating units.
The item master organization is not associated as the item validation org. to any of the operating units in which an order can be placed.
The parent operating unit of the inventory organization may or may not be an operating unit in which orders can be placed.

Table B-2 lists the operating units (OU) in Oracle EBS:

Table B-2 Operating Units (OU) in Oracle EBS

#	Name	ID	Order Capture OU	OE Item Validation Org
1	United States OU	504	No	na
2	Purple OU	505	Yes	Beta IO
3	Red OU	506	Yes	Gamma IO
4	Yellow OU	507	Yes	Delta IO
5	White OU	509	No	na
6	Orange OU	510	No	na
7	Green OU	511	No	na
6	Blue OU	512	No	na

Table B-3 lists the organizations (IO) in Oracle EBS:

Table B-3 Organizations (IO) in Oracle EBS

#	Name	ID	Parent Operating Unit	Item Master Org	Does IO serve as Item Validation Org
1	Alpha IO (Item Master Org)	750	United States OU	Yes	No
2	Beta IO	751	White OU	No	Yes
3	Gamma IO	752	Orange OU	No	Yes
4	Delta IO	753	Green OU	No	Yes
5	Phi IO	754	Blue OU	No	No
6	Kappa IO	755	Purple OU	No	No

Table B-4 lists business units (BU) in Siebel

Table B-4 Business Units (BU) in Siebel

#	Name	ID	Used for Order Capture
1	Purple BU	1-AC	Yes
2	Red BU	1-AD	Yes
3	Yellow BU	1-AE	Yes
4	Brown BU	1-AG	No

Table B-5 lists inventory locations (IL) in Siebel. (These are item validation orgs. from Oracle EBS).

Table B-5 Inventory Locations (IL) in Siebel

#	Name	ID	Primary Business Unit
1	Beta IL	1-XB	Purple BU
2	Gamma IL	1-XC	Red BU
3	Delta IL	1-XC	Yellow BU

Table B-6 lists AIA_ORGANIZATION_ID X-Ref

Table B-6 AIA_ORGANIZATION_ID X-Ref

#	Oracle EBS ID	Common	Siebel ID
1	505 (Purple OU)	C1	1-AC (Purple BU)
2	506 (Red OU)	C2	1-AD (Red BU)
3	507 (Yellow OU)	C3	1-AE (Yellow BU)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Table B-7 lists AIA_INVENTORY_ID X-Ref

Table B-7 AIA_INVENTORY_ID X-Ref

Oracle EBS ID	Common	Siebel ID
751 (Beta IO)	C51	1-XB (Beta IL)
752 (Gamma IO)	C52	1-XC (Gamma IL)
753 (Delta IO)	C53	1-XD (Delta IL)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Based on the organization setup, the following tables illustrate how the Oracle EBS item is synchronized to a Siebel product.

Table B-8 lists the item definition in Oracle EBS:

Table B-8 Item Definition in Oracle EBS

#	Item Name	ID	Inventory Org. ID	Parent OU
1	Item A	10	750 (Alpha IO)	504 (US OU)
2	Item A	10	751 (Beta IO)	509 (White OU)
3	Item A	10	752 (Gamma IO)	510 (Orange OU)
4	Item A	10	753 (Phi IO)	512 (Blue OU)
5	Item B	20	751 (Beta IO)	509 (White OU)
6	Item B	20	755 (Kappa IO)	505 (Purple OU)

Table B-9 lists the product definition in Siebel.

Table B-9 Product Definition in Siebel

#	Product Name	Row	Primary Bus. Unit ID	Secondary Bus. Unit ID
1	Item A	1-PD1	1-AC (Purple BU)	na
2	Item A	1-PD2	1-AD (Red BU)	na
3	Item B	1-PD3	1-AC (Purple BU)	na

The Oracle AIA X-Ref contains the information listed in Table B-10 for this product synchronization scenario.

Table B-10 Oracle AIA X-Ref

#	Type	Siebel ID	Oracle EBS ID	Common
1	ITEM_ITEMID	1-PD1	10::751::509	C101
2	ITEM_ITEMID	1-PD2	10::752::510	C102
3	ITEM_ITEMID	1-PD3	20::751::509	C103

B.3.2 Scenario #2: The Item Validation Org. is Shared Across Multiple Operating Units

The scenario description is:

Only one master organization in Oracle EBS. All items are defined in this master organization.
The same inventory organization is specified as the item validation organization in the profile option across multiple order capturing operating units.
- This implies that there is a single corresponding inventory location created in Siebel CRM. However, the business unit to be specified for this single inventory location in Siebel CRM may be corresponding to any of the operating units (for that item validation org.).
- Whichever business unit is chosen to be specified for the inventory location becomes the primary business unit on the product created during synchronization.
- All other business units for the given product must be manually associated within the Siebel product definition. This may only be necessary if organization-based visibility is set up in Siebel CRM for the users. (If default catalog-based visibility is used, manually associating the other business units may not be required.)
The master organization may be this item validation org. across multiple operating units in which an order can be placed.
The parent operating unit associated with the inventory organization may or may not be the operating unit against which orders are going to be placed.

Table B-11 lists the operating units (OU) in Oracle EBS:

Table B-11 Operating Units (OU) in Oracle EBS

#	Name	ID	Order Capture Operating Unit	OE Item Validation Org
1	United Stated OU	504	No	na
2	Purple OU	505	Yes	Beta IO
3	Red OU	506	Yes	Beta IO
4	Yellow OU	507	Yes	Beta IO
5	White OU	509	No	na
6	Orange OU	510	No	na
7	Green OU	511	No	na
8	Blue OU	512	No	na

Table B-12 lists the inventory organizations (IO) in Oracle EBS:

Table B-12 Inventory Organizations (IO) in Oracle EBS

#	Name	ID	Parent Operating Unit	Item Master Organization	Does IO serve as Item Validation Org.
1	Alpha IO (Item Master Organization	750	United States OU	Yes	No
2	Beta IO	751	White OU	No	Yes
3	Gamma IO	752	Orange OU	No	No
4	Delta IO	753	Green OU	No	No
5	Phi IO	754	Blue OU	No	No
6	Kappa IO	755	Purple OU	No	No

Table B-13 lists business units (BU) in Siebel

Table B-13 Business Units (BU) in Siebel

#	Name	Row	Used for Order Capture
1	Purple BU	1-AC	Yes
2	Red BU	1-AD	Yes
3	Yellow BU	1-AE	Yes
4	Brown BU	1-AG	No

Table B-14 lists inventory locations (IL) in Siebel. (This is the item validation org. from Oracle EBS.)

Table B-14 Inventory Locations (IL) in Siebel

#	Name	ID	Primary Business Unit
1	Beta IL	1-XB	Purple BU

Table B-15 lists the AIA_ORGANIZATION_ID X-Ref

Table B-15 AIA_ORGANIZATION_ID X-Ref

#	Oracle EBS ID	Common	Siebel ID
1	505 (Purple OU)	C1	1-AC (Purple BU)
2	506 (Red OU)	C2	1-AD (Red BU)
3	507 (Yellow OU)	C3	1-AE (Yellow BU)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Table B-16 lists the AIA_INVENTORY_LOCATION_ID X-Ref

Table B-16 AIA_INVENTORY_LOCATION_ID X-Ref

#	Oracle EBS ID	Common	SEBL_01	SEBL01_INVLOC_BU
1	751 (Beta IO)	C51	1-XB (Beta IL)	1-AC (Purple BU)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Based on the organization setup, the following tables illustrate how the Oracle EBS item is synchronized as a Siebel product.

Table B-17 lists the item definitions in Oracle EBS:

Table B-17 Item Definitions in Oracle EBS

#	Item Name	ID	Inventory Org. ID	Parent Operating Unit
1	Item A	10	750 (Alpha IO)	504 (US OU)
2	Item A	10	751 (Beta IO)	509 (White OU)
3	Item A	10	752 (Gamma IO)	510 (Orange OU)
4	Item A	10	753 (Phi IO)	512 (Blue OU)
5	Item B	20	750 (Alpha IO)	504 (US OU)
6	Item B	20	751 (Beta IO)	509 (White OU)
7	Item B	20	755 (Kappa IO)	505 (Purple OU)

Table B-18 lists the product definitions in Siebel

Table B-18 Product Definitions in Siebel

#	Product Name	Row ID	Primary Bus. Unit ID	Non-Primary Bus. Unit ID (Optional)
1	Item A	1-PD1	1-AC Purple BU)	1-AD (Red BU 1-AE (Yellow BU)
2	Item B	1-PD3	1-AC (Purple BU)	1-AD (Red BU 1-AE (Yellow BU)

Product Name

Row ID

Primary Bus. Unit ID

Non-Primary Bus. Unit ID (Optional)

Item A

1-PD1

1-AC Purple BU)

1-AD (Red BU

1-AE (Yellow BU)

Item B

1-PD3

1-AC (Purple BU)

1-AD (Red BU

1-AE (Yellow BU)

Note:

If required, the non-primary business unit (multi-org) must be manually set up for the product.

The Oracle AIA X-Ref contains the information listed in Table B-19 for this product synchronization scenario.

Table B-19 Oracle AIA X-Ref

#	Type	Siebel ID	Oracle EBS ID	Common
1	ITEM_ITEMID	1-PD1	10::751::509	C101
2	ITEM_ITEMID	1-PD3	20::751::509	C103

B.3.3 Scenario #3: The Item Master Organization is the Item Validation Org. and Shared Across Multiple Operating Units

The scenario description is:

There is only one item master organization in Oracle EBS. All items are defined in this master organization.
The item master organization also serves as the item validation organization in the profile option across multiple order capturing operating units.
- This implies that there is a single corresponding inventory location created in Siebel CRM. However, the business unit to be specified for this single inventory location in Siebel CRM may be corresponding to any of the operating units (for that item validation org.).
- Whichever business unit is chosen to be specified for the inventory location becomes the primary business unit on the product created during synchronization.
- All other related business units for the given product must be manually associated within the Siebel product definition. This may only be necessary if organization-based visibility is set up in Siebel CRM for the users. (If default catalog-based visibility is used, manually associating the other business units may not be required.)
The parent operating unit associated with the inventory organization may or may not be the operating unit against which orders are going to be placed.

Table B-20 lists the operating units (OU) in Oracle EBS:

Table B-20 Operating Units (OU) in Oracle EBS

#	Name	ID	Order Capture Operating Unit	OE Item Validation Org.
1	United States OU	504	No	na
2	Purple OU	505	Yes	Alpha IO
3	Red OU	506	Yes	Alpha IO
4	Yellow OU	507	Yes	Alpha IO
5	White OU	509	No	na
6	Orange OU	510	No	na
7	Green OU	511	No	na
8	Blue OU	12	No	na

Table B-21 lists the inventory organizations (IO) in Oracle EBS:

Table B-21 Inventory Organizations (IO) in Oracle EBS

#	Name	ID	Parent Operating Unit	Item Master Org.	Does IO serve as item Validation Org
1	Alpha IO (Item Master organization)	750	United States OU	Yes	Yes
2	Beta IO	751	White OU	No	No
3	Gamma IO	752	Orange OU	No	No
4	Delta IO	753	Green OU	No	No
5	Phi IO	754	Blue OU	No	No
6	Kappa IO	755	Purple OU	No	No

Table B-22 lists business units (BU) in Siebel

Table B-22 Business Units (BU) in Siebel

#	Name	Row ID	Used for Order Capture
1	Yes	Purple BU	1-AC
2	Yes	Red BU	1-AD
3	Yes	Yellow BU	1-AE
4	No	Brown BU	1-AG

Table B-23 lists inventory locations (IL) in Siebel. (This is the item validation org. from Oracle EBS.)

Table B-23 Inventory Locations (IL) in Siebel

#	Name	ID	Primary Business Unit
1	Alpha IL	1-XM	Purple BU

Table B-24 lists AIA_ORGANIZATION_ID X-Ref

Table B-24 AIA_ORGANIZATION_ID X-Ref

#	Oracle EBS ID	Common	Siebel ID
1	505 (Purple OU)	C1	1-AC (Purple BU)
2	506 (Red OU)	C2	1-AD (Red BU)
3	507 (Yellow OU)	C3	1-AE (Yellow BU)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Table B-25 lists the AIA_INVENTORY_LOCATION_ID X-Ref

Table B-25 AIA_INVENTORY_LOCATION_ID X-Ref

#	Oracle EBS ID	Common	SEBL_01	SEBL01_INVLOC_BU
1	750 (Alpha IO)	C51	1-XM (Alpha IL)	1-AC (Purple BU)

Note:

The values in parenthesis are just for explanation, they do not go into the X-Ref.

Based on the organization setup, the following tables illustrate how the Oracle EBS item is synchronized to a Siebel product.

Table B-26 lists the item definitions in Oracle EBS:

Table B-26 Item Definitions in Oracle EBS

#	Item Name	ID	Inventory Org. ID	Parent Operating Unit
1	Item A	10	750 (Alpha IO)	504 (US OU)
2	Item A	10	751 (Beta IO)	509 (White OU)
3	Item A	10	752 (Gamma IO)	510 (Orange OU)
4	Item A	10	753 (Phi IO)	512 (Blue OU)
5	Item B	20	750 (Alpha IO)	504 (US OU)
6	Item B	20	751 (Beta IO)	509 (White OU)
7	Item B	20	755 (Kappa IO)	505 (Purple OU)

Table B-27 lists the product definitions in Siebel

Table B-27 Product Definitions in Siebel

#	Product Name	Row ID	Primary Bus. Unit ID	Non-Primary Bus. Unit ID (Optional)
1	Item A	1-PD1	1-AC Purple BU)	1-AD (Red BU 1-AE (Yellow BU)
2	Item B	1-PD3	1-AC (Purple BU)	1-AD (Red BU 1-AE (Yellow BU)

Product Name

Row ID

Primary Bus. Unit ID

Non-Primary Bus. Unit ID (Optional)

Item A

1-PD1

1-AC Purple BU)

1-AD (Red BU

1-AE (Yellow BU)

Item B

1-PD3

1-AC (Purple BU)

1-AD (Red BU

1-AE (Yellow BU)

Note:

If required, the non-primary business unit (multi-org) must be manually set up for the product.

The Oracle AIA X-Ref contains the information listed in Table B-28 for this product synchronization scenario.

Table B-28 Oracle AIA X-Ref

#	Type	Siebel ID	Oracle EBS ID	Common
1	ITEM_ITEMID	1-PD1	10::750::504	C101
2	ITEM_ITEMID	1-PD3	20::750::504	C103