Search Results mfg_lookups




Overview
Explore in AI Chat

Overview

MSCATPDP is a concurrent program registered under the MSC – Advanced Supply Chain Planning product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The user-facing name is ATP Data Pull, and the program's underlying description identifies it as an ATP Specific Data Pull. Functionally, MSCATPDP belongs to the broader Planning Data Pull infrastructure and is responsible for extracting and staging Available-to-Promise (ATP) related planning data so that it can be consumed by the Advanced Supply Chain Planning engine and its associated planning runs.

The program is enabled (Enabled: Yes) and is delivered as part of the standard MSC concurrent program set. It complements the parent Planning Data Pull executable by isolating the ATP-specific portion of the data collection cycle, allowing planners to refresh ATP-relevant supply, demand, and scheduling information independently of a full planning data pull.

Execution Details

The documented execution configuration for MSCATPDP is as follows:

  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: MSCPDP
  • Execution File: msc_cl_pull.launch_monitor
  • Executable User Name: MSCPDP
  • Executable Description: Planning Data Pull

The program can be submitted with a request set argument structure that exposes a series of descriptive flexfield attributes (ATTRIBUTE1 through ATTRIBUTE21 and beyond). These attributes are tied to the $SRS$.MSCATPDP shared name and are largely display-only (Display = Y, Insert = N, Update = N) or hidden, controlling which components of the ATP data pull are executed.

How to Run

Users typically submit MSCATPDP through the Standard Request Submission (SRS) window: Responsibility → View → Requests → Submit a New Request → Single Request, then selecting ATP Data Pull. Because the Argument Method is Standard, the parameter dialog is generated directly from the concurrent program definition.

Several of the program's descriptive flexfield attributes derive their default values from lookups. Specifically, the metadata shows selections against lookup_type = 'SYS_YES_NO' using lookup_code values of 1 and 2 for attributes such as ATTRIBUTE10 through ATTRIBUTE22. The default expressions resolve these codes to their meanings via:

  • select meaning from mfg_lookups where lookup_type = 'SYS_YES_NO' and lookup_code = 1
  • select meaning from mfg_lookups where lookup_type = 'SYS_YES_NO' and lookup_code = 2

Administrators reviewing or troubleshooting parameter behavior should verify the SYS_YES_NO lookup set remains intact, since altered or missing lookup codes will cause the parameter defaults to fail to resolve. This is the point where a search for "lookup_code" most often leads users working with MSCATPDP configuration.

Related Objects

MSCATPDP is closely associated with the following elements of the Advanced Supply Chain Planning data model and concurrent manager infrastructure:

  • Executable MSCPDP – the parent Planning Data Pull executable and its launch monitor routine msc_cl_pull.launch_monitor.
  • mfg_lookups – the lookup table referenced by the program's default flexfield values, using lookup type SYS_YES_NO.
  • MSC staging and interface tables – populated during the ATP data pull cycle and consumed by the planning engine.
  • Planning Data Pull request set – the collection of concurrent programs (including MSCATPDP) run together to refresh planning data.

Because the executable is shared with the general Planning Data Pull program, monitoring MSCATPDP in the Concurrent Manager request log alongside MSCPDP provides the clearest view of its completion status and any errors surfaced during the ATP-specific pull phase.