Search Results mtl_demand_interface_s

Overview

CZ_ATP_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its classification as a UTIL API indicates that it provides reusable helper logic rather than a business-facing transaction entry point. The package supports Available-to-Promise (ATP) checking within the Oracle Advanced Supply Chain Planning and order management flow, supplying the infrastructure needed to submit ATP requests, execute the availability check, and retrieve the resulting supply commitments.

ATP functionality determines whether demand, such as a sales order line or a planned shipment, can be satisfied on a requested date based on current on-hand supply, scheduled receipts, and ATP rules. CZ_ATP_UTIL encapsulates the database-side steps of that process so that calling programs do not need to interact directly with the ATP demand interface, rule tables, and group ATP views. The "CZ" prefix associates the package with the Oracle EBS configuration and order capture product family.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions on this package:

• INSERT_ATP_REQUEST — Populates the ATP request staging structures, writing the demand or request record that the ATP engine will subsequently evaluate. This procedure is the entry point for creating an ATP inquiry.
• RUN_ATP_CHECK — Executes the actual availability check against the staged request, applying the ATP rule and item/organization parameters to determine if the requested quantity can be promised on the requested date.
• GET_ATP_RESULT — Retrieves the outcome produced by the check, returning the ATP result for the caller to consume, for example the confirmed quantity or the earliest feasible date.

The three procedures form a natural sequence: stage the request, run the check, then read the result. Parameter lists are not documented in the available metadata and should be confirmed against the deployed package specification in the target instance.

Tables Accessed

Through APPS synonyms, the package references the following tables:

• MTL_DEMAND_INTERFACE_S — The ATP demand interface table used to stage demand records processed by the ATP engine.
• MTL_ATP_RULES — Defines the ATP rule assigned to an item/organization, governing how supply is allocated and how the promise date is derived.
• MTL_SYSTEM_ITEMS — Supplies item-level attributes required to validate and process the ATP request.
• MTL_PARAMETERS — Provides organization-level planning and inventory parameters relevant to the availability calculation.
• DUAL — Used for single-row evaluations and scalar computation.

Additional dependencies recorded in the ETRM dependency listing include FND_GLOBAL, FND_TRANSACTION, HR_ORGANIZATION_UNITS, MFG_LOOKUPS, MTL_GROUP_ATPS_VIEW, and the STANDARD package, which supply concurrent request context, organization validation, lookup decoding, and group ATP view access.

Usage Notes

CZ_ATP_UTIL is not referenced by any other database object, confirming its role as a terminal utility rather than a shared framework component. It is therefore invoked directly by external callers — typically Oracle Forms, concurrent programs, or custom PL/SQL extensions — that require server-side ATP evaluation. Invocation is commonly required during order entry scheduling, available-to-promise simulation, or batch availability processing.

Because the package writes to the demand interface and executes a check, callers should initialize the FND_GLOBAL application context and supply a valid organization and item context before calling INSERT_ATP_REQUEST. In 12.1.1 and 12.2.2 the underlying MTL tables are shared, so behavior is consistent across both releases; however, any customization should account for the possibility of overlapping ATP processing by other sessions.