Search Results submit_copy_request

Overview

MSC_CL_COPY_STG_TBL is an Oracle Advanced Supply Chain Planning (ASCP) staging package that resides in the APPS schema and is declared with AUTHID CURRENT_USER. Its principal business function is to support the collection and staging of planning data from one Oracle E-Business Suite source instance into the MSC (Material and Supply Chain) staging tables of a destination planning instance. In multi-instance or distributed planning architectures, this package moves source-side supply chain entities — calendars, resources, routings, sourcing rules, trading partners, demands, bills of resources, and business intelligence data — into a consolidated staging area so that the planning engine can run against a coherent snapshot.

The package manages a state machine that governs the lifecycle of a copy operation. Constants defined in the specification track stage status: G_ST_EMPTY (no instance data exists), G_ST_PULLING, G_ST_READY, G_ST_COLLECTING, and G_ST_PURGING. These states allow the copy process to be monitored and orchestrated across multiple worker processes.

Key Procedures and Functions

The reported inventory lists 106 documented procedures and functions. The following highlights the procedures captured in the ETRM excerpt:

• LAUNCH_MONITOR — The controlling procedure that launches and monitors a copy request for a specified instance, source instance, timeout, and worker count. It accepts an instance identifier to associate the copy operation with a specific source and drives the overall state transitions.
• COPY_* procedures — A large family of entity-specific copy routines, each responsible for staging one planning entity type. Documented examples include COPY_CALENDAR_DATES, COPY_CALENDAR_EXCEPTIONS, COPY_CALENDAR_SHIFTS, COPY_CALENDAR_ASSIGNMENTS, COPY_RESOURCE_REQUIREMENTS, COPY_ROUTING_OPERATIONS, COPY_SOURCING_HISTORY, COPY_SOURCING_RULES, COPY_TRADING_PARTNERS, COPY_TRADING_PARTNER_SITES, COPY_APPS_INSTANCES, COPY_ASSIGNMENT_SETS, COPY_ATP_RULES, COPY_BILL_OF_RESOURCES, COPY_DEMANDS, COPY_ITEM_CATEGORIES, COPY_CATEGORY_SETS, COPY_COMPANY_USERS, COPY_COMPONENT_SUBSTITUTES, COPY_DESIGNATORS, COPY_GROUP_COMPANIES, COPY_CARRIER_SERVICES, COPY_CO_PRODUCTS, COPY_DEMAND_CLASSES, COPY_DEPT_RES_INSTANCES, COPY_NET_RES_INST_AVAIL, COPY_BOR_REQUIREMENTS, COPY_BIS_BUSINESS_PLANS, COPY_BIS_PERIODS, COPY_BIS_PFMC_MEASURES, COPY_BIS_TARGET_LEVELS, COPY_BIS_TARGETS, COPY_CAL_WEEK_START_DATES, and COPY_CAL_YEAR_START_DATES.

Each COPY_ procedure isolates the logic for extracting its respective entity from the source and writing it into the corresponding MSC staging table, allowing parallel execution and granular progress reporting.

Tables Accessed

The package references the following tables through APPS synonyms:

• MSC_APPS_INSTANCES — Stores metadata about registered E-Business Suite source instances. COPY_APPS_INSTANCES maintains this registry, and LAUNCH_MONITOR uses instance identifiers to determine which source to pull from and which destination to populate.
• MSC_COLL_PARAMETERS — Holds collection and copy parameters that govern what data is staged and how. The copy procedures consult these parameters to determine scope and behavior during a copy request.
• FND_USER — Used to resolve the identity and effective user context (relevant given AUTHID CURRENT_USER) when the copy request is submitted or monitored.

Usage Notes

MSC_CL_COPY_STG_TBL is typically invoked through the ASCP collection and staging infrastructure rather than directly by end users. When a planner submits a copy or collection request for a source instance, the concurrent program and its associated monitor call LAUNCH_MONITOR, which in turn coordinates the individual COPY_ procedures across worker processes. The user search term "submit_copy_request" corresponds to this submission path: a copy request is created and submitted, LAUNCH_MONITOR is launched with the instance and source instance identifiers, and the package proceeds through the pulling, ready, and collecting states until staging completes.

Because the package runs with AUTHID CURRENT_USER and references data through APPS synonyms, customizations should avoid modifying it in place; any extension should be implemented in a separate package that calls the public procedures. The absence of dependent packages in the metadata means it is a top-level orchestrator and can generally be invoked safely from concurrent programs, provided the correct instance identifiers and collection parameters are supplied.