D Scenarios

This appendix discusses three scenarios for synchronizing items from Oracle Product Hub (OPH) to Oracle E-Business Suite when item versions in OPH and Oracle E-Business Suite are different.

The scenarios covered include the following:

• ASCII Code of the item version is set same in OPH and Oracle E-Business Suite.

• ASCII Code of the item version is set higher in OPH and is set lower in Oracle E-Business Suite.

• ASCII Code of the default item version is set higher in Oracle E-Business Suite and is set lower in OPH.

D.1 ASCII Code of the item version is set same in OPH and Oracle E-Business Suite

This is the Oracle recommended approach and has been tested and supported out-of-the-box (OOTB) in the Oracle Product Master Data Management (MDM) integration base pack. You must make sure to set the default item version number and the ASCII code of the item version number to the same value in OPH and Oracle E-Business Suite. For example, the value 0 is not same as 00.

D.2 ASCII Code of the item version is set higher in OPH and is set lower in Oracle E-Business Suite

In this scenario, the API used by the Product MDM pre-built integrations has a wrapper on the base API used to create items in the Oracle E-Business Suite.

To compare the effective date of an incoming item message, the wrapper API uses additional logic such as:

• If the effective date on the incoming item message is less than the current system datetime, then it updates the effective date for the item message to system datetime plus 2 seconds.

• If the item is synchronized from OPH to Oracle E-Business Suite for the first time, and the item version number is set higher than the default version for items in Oracle E-Business Suite, then the Oracle E-Business Suite API first creates a default version of the items and then creates a version synchronized from OPH.

The Product MDM pre-built integrations API uses the current system datetime as the effective date for the default version and then creates the next version of item with the effective date on the item which was the original system datetime plus 2 seconds set by the wrapper API. The effective datetime for the default version of the item must be lesser than the effective datetime of subsequent versions of the item created in Oracle E-Business Suite.

D.2.1 Assumption

1. The processing time for the default version of the item is less than 2 seconds. The following table lists the examples.

   Table D-1 When assumption 1 applies

   OPH	Oracle E-Business Suite	Comments
   Itemversion = 1Effective datetime = 04/15/11 10:00:00	Default version set = 0System datetime = 04/15/11 10:00:10	Assuming the item synchronization from OPH to Oracle E-Business Suite takes 10 seconds.
   	Item version = 1 Effective datetime = 04/15/11 10:00:12	The Wrapper API sets the effective date time = system datetime + 2 seconds since the effective datetime is less than the system datetime.
   	Item version = 1. Effective start date = 04/15/11 10:00:12. Effective end date = 04/15/11 10:00:12	The base API creates the default version first. Assumption 1 applies.
   	Item version = 1 Effective start date = 04/15/11 10:00:12Effective end date =	The base API creates the next version of the item. Note: The effective start date of item version 1 is higher than the effective start date of default item version 0.

   
   

2. The processing time for the default version of the item is more than 2 seconds

   Table D-2 When assumption 2 applies

   OPH	Oracle E-Business Suite	Comments
   Item version = 1Effective datetime = 04/15/11 10:00:00	Default version set = 0System datetime = 04/15/11 10:00:10	Assuming the item synchronization from OPH to Oracle E-Business Suite takes 10 seconds.
   	Item version = 1 Effective datetime = 04/15/11 10:00:12	The Wrapper API sets the effective date time = system datetime + 2 seconds since the effective datetime is less than the system datetime.
   	Item version = 1 Effective start date = 04/15/11 10:01:10Effective end date =	The base API creates the default version first. Assumption 2 applies since the processing of default version takes more than 2 seconds. In this case, it takes 13 seconds.
   	Itemversion = 1 Effective start date = 04/15/11 10:01:10 Effective end date =	When the base API tries to create the next version of the item, the effective start date of version 1 is less than the effective start date of the existing default version and the item creation fails.

   
   

D.2.2 Workaround

Customers whose Oracle E-Business Suite takes more than 2 seconds to process and create the default version of the item in Oracle E-Business Suite must update the value based on their individual requirements. For example, customers can increase the time interval to 60 seconds.

To update the time interval, follow these steps:

1. Backup the Inveipitb.pls file from customer's Oracle E-Business Suit instance.

2. Open the Inveipitb.pls file, and then modify the process_item API by following the steps listed below

   1. Replace the following code snippet with the code snippet listed in step 2.

      IF (l_item.main_obj_type.effectivity_date IS NULL OR

      l_item.main_obj_type.effectivity_date = fnd_api.g_miss_date OR

      l_item.main_obj_type.effectivity_date <= sysdate) THEN

      l_item.main_obj_type.effectivity_date := sysdate+(2/(60*60*24));

      END IF;

   2. IF (l_item.main_obj_type.effectivity_date IS NULL OR

      l_item.main_obj_type.effectivity_date = fnd_api.g_miss_date OR

      l_item.main_obj_type.effectivity_date <= sysdate) THEN

      l_item.main_obj_type.effectivity_date := sysdate+(60/(60*60*24));

      END IF;

   3. Save the changes, and then recompile the Inveipitb.pls file.

D.3 ASCII Code of the default item version is set higher in Oracle E-Business Suite and is set lower in OPH

This scenario is not supported by Oracle.