Pre-requisite for the Sales Orders purging
Introduction In the oracle EBS the concept of Purging and before purging the order management related tables, pre-requisite to be done for the smooth purging process. The below script will…
Read MoreIntroduction In the oracle EBS the concept of Purging and before purging the order management related tables, pre-requisite to be done for the smooth purging process. The below script will…
Read MoreIntroduction/ Issue: This SQL query is designed to extract Batch Header and Material Details from Oracle Process Manufacturing (OPM). It consolidates information such as company code, plant, batch number, recipe,…
Read MorePrerequisite: 100GB size is required for OEM, Agent. Below parameters to be updated on DB. Alter system set “_allow_insert_with_update_check”=true scope=both; Alter system set session_cached_cursors=200 scope=spfile; Alter system set shared_pool_size=600M scope=spfile;…
Read MoreStep 1: Deploy Oracle SR Package → Description: Apply the Oracle-provided script Compile the package /*===========================================================================+ | Copyright (c) 1999, 2025 Oracle Corporation | | …
Read MoreStep 1: Take Table Counts Before Purging Before performing any purge, get the record counts of the affected tables to ensure you can verify the archival later. Affected Tables: WSH_TRIPS WSH_TRIP_STOPS WSH_DELIVERY_LEGS WSH_NEW_DELIVERIES WSH_DELIVERY_DETAILS WSH_DELIVERY_ASSIGNMENTS SQL statement: SELECT COUNT(*) FROM WSH_TRIPS; SELECT COUNT(*) FROM WSH_TRIP_STOPS; SELECT COUNT(*) FROM WSH_DELIVERY_LEGS; SELECT COUNT(*) FROM WSH_NEW_DELIVERIES; SELECT COUNT(*) FROM WSH_DELIVERY_DETAILS; SELECT COUNT(*) FROM WSH_DELIVERY_ASSIGNMENTS; Step 2: Configure Archival Setup Insert configuration metadata into a custom configuration table XXXX ARCHIVE_CONFIG_TBL. SQL statement: INSERT INTO XXXX_ARCHIVE_CONFIG_TBL (SNO, MODULE_SHORT_NAME, MODULE_LONG_NAME, ARCHIVE_REQUIRED, ORIG_TABLE_NAME, ARCHIVE_TABLE_NAME, LAST_ARCHIVED_ON) VALUES (XXXX_ARCHIVE_SEQ.NEXTVAL, ‘WSH’, ‘SHIPPING’, ‘Y’, ‘WSH_TRIP_STOPS’, ‘XXXX_WSH_TRIP_STOPS_ARCHIVE’, SYSDATE) (SNO, MODULE_SHORT_NAME, MODULE_LONG_NAME, ARCHIVE_REQUIRED, ORIG_TABLE_NAME, ARCHIVE_TABLE_NAME, LAST_ARCHIVED_ON) VALUES (XXXX_ARCHIVE_SEQ.NEXTVAL, ‘WSH’, ‘SHIPPING’, ‘Y’, ‘WSH_TRIPS’, ‘XXXX_WSH_TRIPS_ARCHIVE’, SYSDATE) (SNO, MODULE_SHORT_NAME, MODULE_LONG_NAME, ARCHIVE_REQUIRED, ORIG_TABLE_NAME, ARCHIVE_TABLE_NAME, LAST_ARCHIVED_ON) VALUES (XXXX_ARCHIVE_SEQ.NEXTVAL, ‘WSH’, ‘SHIPPING’, ‘Y’, ‘WSH_DELIVERY_LEGS’, ‘XXXX_WSH_’WSH_DELIVERY_LEGS _ARCHIVE’, SYSDATE) (SNO, MODULE_SHORT_NAME, MODULE_LONG_NAME, ARCHIVE_REQUIRED, ORIG_TABLE_NAME, ARCHIVE_TABLE_NAME, LAST_ARCHIVED_ON) VALUES (XXXX_ARCHIVE_SEQ.NEXTVAL, ‘WSH’, ‘SHIPPING’, ‘Y’, ‘WSH_DELIVERY_DETAILS’, ‘XXXX_WSH_’WSH_DELIVERY_DETAILS’_ARCHIVE’, SYSDATE)…
Read MoreIntroduction/ Issue: In Oracle Fusion Supply Chain Planning, planners often need to extract plan measure data from demand or supply plan layouts for reporting and analysis outside the application. Instead…
Read MoreIssue: The Work Orders for a specific item loaded from EBS into Fusion Supply Chain Planning are appearing in the Buyer Material Plan within the supply plan. However, they are…
Read MoreProcedure: Item Regulatory Interface Objective The purpose of this document is to outline the process for loading and updating Item Regulatory Information into Oracle using an API, based on data…
Read MoreUPDATE PO SHIPMENT LINE USING API Objective: The intent of this document is to understand how we can update or split the PO Shipment line using API Scenario: Currently…
Read More