A Frequently Asked Questions

1. Q: Is it possible to synchronize items from OPH/PIM to Siebel that are associated with multiple inventory organizations that in turn are associated with the same operating unit?

   A: No. Uniqueness of a product in Siebel is based on a combination of product, business unit, and vendor; therefore, if such synchronization is done, the key does not remain unique.

2. Q: Why only set up the cross-references for inventory locations associated with item validation organization for Siebel?

   A: Item synchronization to Siebel is based on the requirement that Siebel is able to use that item as part of the order capture process in the Order to Cash: Siebel CRM - EBS integration. In Oracle E-Business Suite, an order can refer to products that are part of item validation organization only. For this reason, you must populate the cross-references for inventory location only with item validation organization.

3. Q: How to extend the Siebel provider service to consume the UDAs published by Oracle E-Business Suite?

   A: For SyncProductSiebelProvABCSImpl and SyncBillOfMaterialsListSiebelProvABCSImpl, set the flag enableCustomExtensions in XformSyncItemListEBMToSiebelProdABM_Custom_UDA.xsl or XformSyncBillOfMaterialsListEBMToSiebelProdABM_Custom_UDA.xsl to true/. Then add custom contents in these files.

4. Q: How to configure the STRUCTURE_TYPE and STRUCTURE_NAME_ALTERNATE_BOM DVMs?

   A:STRUCUTRE_TYPE is composed of Structure Name and Structure Type. Structure Name value is the common value associated with a Structure Name in the DVM STRUCTURE_NAME_ALTERNATE_BOM. Structure Type can be Sales for Sales BOM and any other value for all other BOMs. The Sales BOM needs to be identified by Sales as type, if this is changed the routing rules need to be changed to reflect the new value, since this value determines if the product will be routed to Siebel or not.

5. Q: Does the service support sharing of inventory organization across multiple operating units?

   A: No. This release of the integration does not support sharing of Inventory Organization across multiple operating units.

6. Q: Would there be an issue if the same item validation organization were shared across multiple operating units?

   A: For answer, see question and answer 5.

7. Q: What are the default values for MDM-product related entries in the AIA Configuration properties XML?

   A: See Section 7.8, "Setting Configuration Properties".

8. Q: When invoking OPH/PIM service, the OPH/PIM errors out with a message "No Access to Method [Method Name]".

   A: To resolve this, here is a workaround:

   1. Remove the existing grants to service methods on Irep.

   2. Go to Launch Functional Administrator, Core Services, Caching Framework, Select Total Cache Components, Select All.

   3. Click Clear all cache.

   4. Recreate grants.

   5. Click Redeploy on Irep service page to redeploy the service.

9. Q: When invoking OPH/PIM services multiple times, the subsequent invocation may take long time and the service request ends with a SocketTimeOut error

   A: To resolve this, here is a workaround:

   1. Launch Integrated SOA Gateway, Launch SOA Monitor.

   2. Click Purge.

   3. Click Turn off Web Service Monitor.

10. Q: The following error occurred during Item sync to EBS instance: Unexpected error occured in package EGO_ITEM_PVT procedure Process_Items: ORA-06502: PL/SQL: numeric or value error: character string buffer too small. Please contact your system administrator or support representative.

    A:To resolve this issue, compile System Items KFF {Key Flexfield } by following these steps:

    1. Log on to Ebiz Application. Navigate to System Administrator -> Application -> Flexfield -> Key -> Segments

    2. In Key Flexfield Segment form, search for application with keyword as Inventory and then search for Flexfield Title with keyword as System Items.

    3. Click Compile. Run a background Concurrent Program to compile KPF. If it is completed successfully, the KFF is compiled.

    4. Compile the package bodies INV_EBI_CHANGE_ORDER_PUB and INV_EBI_ITEM_HELPER

       Note:

       While compiling, if you receive an error :Unable to extend index SYS.I_PLSCOPE_SIG_ACTION$ by 128 in tablespace SYSAUX, then increase the application's table space and recompile.