Search Results call_synchronize

Overview

The concurrent program MSC_ATP_24X7_SYNC belongs to the MSC - Advanced Supply Chain Planning product family within Oracle E-Business Suite. Its user-facing name is ATP 24x7 Synchronization Process, and it is described in the ETRM metadata as the ATP 24x7 Plan Synchronization Program. The program is recorded as enabled in release 12.2.2 and is also documented for 12.1.1.

The program exists to synchronize data associated with the ATP (Available-to-Promise) 24x7 planning configuration. In Advanced Supply Chain Planning, ATP 24x7 is the mode that allows near-real-time availability checks without requiring a full planning run. Because ATP 24x7 depends on a repeated, incremental plan that is continuously refreshed, the underlying data structures must be kept aligned with the source transactional data. MSC_ATP_24X7_SYNC performs that synchronization so that availability results reflect current supply, demand, and on-hand information. It is an internal, housekeeping-style program that operates on behalf of the ATP 24x7 planning process rather than being a user analysis report.

The hint that the user searched for, "call_synchronize", corresponds directly to the execution entry point of the concurrent program. In ETRM the execution file for this executable is named MSC_ATP_24X7.CALL_SYNCHRONIZE, which is the packaged routine named in the executable definition. This confirms that CALL_SYNCHRONIZE is the API-level driver invoked when the concurrent request runs.

Execution Details

The documented execution attributes are as follows:

• Product: MSC - Advanced Supply Chain Planning
• User-facing name: ATP 24x7 Synchronization Process
• Short name / executable: MSC_ATP_24X7_SYNC
• Execution method: PL/SQL Stored Procedure
• Argument method: Standard
• Execution file: MSC_ATP_24X7.CALL_SYNCHRONIZE
• Enabled: Yes
• Subroutine name: not populated in the documented metadata

Because the execution method is PL/SQL Stored Procedure and the execution file is expressed as a package-qualified routine (MSC_ATP_24X7.CALL_SYNCHRONIZE), the program is submitted by the concurrent manager through the standard PL/SQL concurrent program path. The argument method is Standard, meaning the concurrent program definition uses the conventional token-based parameter prompt rather than a custom argument form. In release 12.1.1 the same metadata values apply, since the executable name and call interface were not changed between 12.1.1 and 12.2.2.

How to Run

Like most EBS concurrent programs, MSC_ATP_24X7_SYNC is submitted through the Submit Request (SRS) window, typically navigated from the Advanced Supply Chain Planning responsibility menu under a Requests or Run function. It is generally not intended for manual ad hoc execution; it is normally scheduled as part of the ATP 24x7 planning cycle, often via a request set or a recurring schedule configured by the planning administrator.

Where parameters are exposed, they are presented in the standard SRS parameter region driven by the Standard argument method. Practical guidance for planning administrators:

• Confirm that ATP 24x7 planning is actually enabled for the relevant plan before submitting, since the program synchronizes existing ATP 24x7 plan data.
• Schedule the request to run in step with the ATP 24x7 plan refresh cycle to avoid contention with the planning engine.
• Check the concurrent request log and output rather than a printed report; this program has no user-facing report layout.
• Re-run only after the prior synchronization completes, since overlapping synchronization requests can produce redundant processing against the same plan data.

Related Objects

MSC_ATP_24X7_SYNC operates within the Advanced Supply Chain Planning schema (MSC). It is closely related to the MSC_ATP_24X7 package that contains its CALL_SYNCHRONIZE entry point, and to the ATP 24x7 incremental plan definition it services. Other objects commonly associated with this synchronization area include the planning interface and staging tables used to load supply, demand, and on-hand records into the ATP 24x7 plan, and the standard concurrent manager request and log tables that record each execution. Because no strict interface table or public API names are enumerated in the ETRM metadata beyond the executable and execution file, administrators should treat the MSC_ATP_24X7 package and the associated ATP 24x7 plan setup as the primary related objects when troubleshooting. Output and diagnostics are obtained from the concurrent request log rather than from a dedicated report or interface listing.