Purge Data Repository ESS Process Does Not Purge UOM (Unit Of Measure) Cross Reference Data
(Doc ID 1540841.1)
Last updated on JANUARY 25, 2017
Applies to:Oracle Fusion Global Order Promising - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 1.0]
Information in this document applies to any platform.
***KM Review - Dec 2016 - Checked for Relevance - Release 9 Specific***
We have run the Purge Data Repository ESS process which does NOT Purge UOM (Unit of Measure) cross reference data for the Source System.
Our expectation is that this should delete ALL xref (cross reference) data for the source system as per Dev's description of this process:
This program takes 2 inputs – Instance code and Global Flag
It deletes the collected data for all non-global entities for the given instance. In addition, if Global Flag is Yes, it also deletes the collected data for global entities for the given instance.
To obtain a list of global entities, execute the following SQL.
TABLE_NAME IN (SELECT
GLOBAL_FLAG = 1);
The ESS program also deletes the instance data in cross references table i.e. MSC_XREF_MAPPING.
We have run this process, which has completed successfully, however it has not deleted entries in the MSC_XREF_MAPPING table for the Source system, where the ENTITY_NAME is UOM_CODES. i.e. the UOM cross references have not been purged. This has been verified by executing the following SQL:
MAI.INSTANCE_ID = MXM.SR_INSTANCE_ID AND
INSTANCE_CODE = '%SOURCE_SYSTEM'
Results of which are:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document