Search Results cz_atp_callback_util




Overview
Explore in AI Chat

Overview

APPS.CZ_ATP_CALLBACK_UTIL is a configuration-utility PL/SQL package within the Oracle E-Business Suite Configure-to-Order (CTO) and Advanced Supply Chain Planning (ASCP) landscape. Its principal business function is to mediate Availability-to-Promise (ATP) callback processing for configured items — that is, items whose availability cannot be validated as a simple stock query but must be exploded into their bill-of-material components before ATP inquiry. The package translates between the external "item key" identifiers presented by configuration forms and the internal inventory item identifiers and component codes stored in the CTO schema, then assembles and persists the ATP request records consumed by downstream planning logic.

The package is classified as a UTIL (utility) object in ETRM metadata, indicating that it exposes reusable helper routines rather than a self-contained business flow. It resides in the APPS schema and is referenced by five other packages, placing it in a shared dependency layer rather than at the top of any call stack.

Key Procedures and Functions

  • RUN_ATP_CALLBACK — The primary entry point; orchestrates the ATP callback for a configured item, invoking the supporting routines and producing one or more ATP records.
  • INSERT_ATP_REC — Inserts a single ATP request record into the CTO ATP request table.
  • DELETE_ATP_RECS — Removes stale or superseded ATP request records, typically before re-processing a configuration.
  • INV_ITEM_ID_FROM_ITEM_KEY — Resolves an external item key to the internal inventory item identifier.
  • COMPONENT_CODE_FROM_ITEM_KEY — Derives the component code associated with a given item key.
  • COMPONENT_CODE_TOKENS — Parses or maps component code tokens used to construct item keys.
  • ITEM_KEY_TOKENS — Decomposes an item key into its constituent tokens for interpretation.
  • VALIDATION_ORG_FOR_CFG_MODEL — Validates that a configuration model is valid within the given organization context.
  • ROOT_BOM_CONFIG_ITEM_ID — Identifies the root configured item identifier in the BOM structure, anchoring the explosion logic.

Collectively these routines provide identifier translation, structural validation, and record maintenance. Parameter signatures are not documented and should be confirmed against the package source or ALL_ARGUMENTS in the target instance.

Tables Accessed

  • BOM_EXPLOSIONS — Read to determine the component structure of the configured item, supporting ROOT_BOM_CONFIG_ITEM_ID and component resolution.
  • CZ_ATP_REQUESTS — The transactional ATP request table that INSERT_ATP_REC populates and DELETE_ATP_RECS purges.
  • CZ_ATP_REQUESTS_S — The sequence (or supporting) object for the ATP request table, used to generate request identifiers.
  • DUAL — Used for scalar evaluations and single-row expression selection.
  • PLITBLM — The standard Oracle Applications PL/SQL integer table type, used for array-based token processing in the item-key routines.

Usage Notes

CZ_ATP_CALLBACK_UTIL is not typically invoked directly by end users. It is called programmatically by the higher-level CTO callback machinery — notably CZ_OM_ATP_CALLBACK, CZ_PRC_CALLBACK_UTIL, CTO_ATP_INTERFACE_PK, ASO_CFG_INT, and OKC_CFG_PUB — which drives ATP checks during order entry, configuration validation, and quote capture. In Oracle EBS 12.1.1 and 12.2.2, these calls occur within the runtime execution of the configuration forms and the CTO ATP interface, not from a standalone concurrent program.

Customizations that extend CTO ATP behaviour should call RUN_ATP_CALLBACK rather than the individual helper routines, since the helpers assume the identifier and BOM context established by the orchestrating procedure. Because the package is a shared dependency for five compiled packages, any modification invalidates and requires recompilation of those dependents. The object status is VALID in the documented instance, indicating that the specification and body compile cleanly against the referenced dependencies. No standalone form or concurrent program is documented for this package; it should be treated as an internal utility layer.