MRP_AD% Tables or Snapshots Have Grown Due To New Triggers Introduced In Baseline Patching
Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 184.108.40.206 and later
Information in this document applies to any platform.
In an R220.127.116.11 Production Instance (Centralized Planning Environment):
MRP_AD% tables have grown due to new triggers introduced in baseline patching. The patches we applied as dictated by the following note:
Note 883202.1 Minimum Baseline Patch Requirements for Extended Support on EBS
The patches were for ASCP as follows: 3930903, 4392231,6444221,7531850,7661713,8278480,8671960,8686151,9254001, 9296691,9495205. This intoduced 2 triggers MRP_SN_BOM_T1 and MRP_SN_BOM_T2 which track inserts and deletes to the base tables that are used for Data collections (as follows):
MRP_AD_BOMS, MRP_AD_INV_COMPS, MRP_AD_SUB_COMPS, MRP_AD_PROCESS_EFFECTIVITY and MRP_AD_OPERATION_COMPONENTS.
The question/concern comes from desire to disable trigger and truncate tables. What would be the best approach as space problems are a huge concern and it's impact to MRP?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms