Search Results assign_atp_input_rec

Overview

MRP_ATP_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API. It forms part of the Available-to-Promise (ATP) infrastructure used by Oracle's Advanced Supply Chain Planning and materials planning modules. Its principal role is to act as a thin wrapper layer that delegates ATP record manipulation to the underlying SATP utility package, MSC_SATP_FUNC, while exposing a stable, package-qualified interface to callers within MRP and adjacent modules.

The package operates against the ATP_Rec_Typ record type defined in MRP_ATP_PUB, the public specification that mirrors this body. Because the header revision dates to 2002 (MRPGATPB.pls 115.253), the logic has remained stable across the 12.1.1 and 12.2.2 releases, with behavior effectively unchanged other than environment-level refactoring. The package contains no standalone business logic of its own; each procedure is a pass-through call to MSC_SATP_FUNC, which holds the actual ATP scheduling and record-transformation logic. The private classification indicates it is not intended as a directly supported integration point and may change without notice, unlike the corresponding public API.

Key Procedures and Functions

Three documented procedures make up the package body:

• EXTEND_ATP — Extends an ATP record table, delegating to MSC_SATP_FUNC.Extend_Atp. It supports growth of the ATP_Rec_Typ collection when additional ATP rows must be accommodated during planning or scheduling operations.
• ASSIGN_ATP_INPUT_REC — Copies a single indexed input ATP record into a target ATP table. It is used to normalize inbound ATP request data before it is passed into the ATP engine.
• ASSIGN_ATP_OUTPUT_REC — Transfers ATP results from the working ATP table into an output record structure, again delegating to MSC_SATP_FUNC. This is the procedure most closely associated with the search term "assign_atp_output_rec," which is the lowercase form of this procedure name.

All three procedures follow the same convention: they accept an input ATP_Rec_Typ (or a source table plus index), an IN OUT NOCOPY destination ATP_Rec_Typ, and an OUT NOCOPY return status. None of the procedures perform independent validation or exception handling; error semantics are inherited from the wrapped MSC_SATP_FUNC routines.

Tables Accessed

The documented metadata lists no directly referenced base tables through APPS synonyms. This is consistent with the package's design: it manipulates PL/SQL collection types (ATP_Rec_Typ) rather than issuing SQL against persistent tables. All database access is confined to the underlying MSC_SATP_FUNC implementation, which resolves the appropriate ATP and planning tables at runtime. Consequently, no table-level privileges or dependencies should be expected on MRP_ATP_PVT itself.

Usage Notes

MRP_ATP_PVT is referenced by 17 other packages in the documented dependency graph, confirming its role as an internal utility rather than an entry point. Typical invocation occurs indirectly, when planning, scheduling, or order-promising code populates ATP input collections and needs them extended, normalized, or copied to output structures. Forms and concurrent programs in the MRP and MSC product families reach this logic through the public MRP_ATP_PUB layer or through direct calls from sibling private packages.

Because the package is classified as PVT, custom code should not bind to MRP_ATP_PVT directly. Integrations that require ATP record manipulation should use the supported public API surface (MRP_ATP_PUB) or the underlying MSC_SATP_FUNC where documented. The pass-through nature of these procedures also means that any behavioral change originates in MSC_SATP_FUNC; referencing this package body alone is insufficient to reason about ATP outcomes. Migration from 12.1.1 to 12.2.2 does not alter the callable interface described here.