Search Results sync_dep_planning_cache




Overview
Explore in AI Chat

Overview

ONT_DEP_PLANNING_DEF_UTIL is a utility package in the Oracle E-Business Suite Order Management (ONT) module. It belongs to the APPS schema and is classified as a UTIL (utility) API. Its purpose is to support the dependent planning requirement determination functionality associated with order capture. Specifically, the package provides attribute value retrieval and cache synchronization services for a dependent planning requirement definition structure, built around a cached record of type OE_AK_DEP_PLAN_REQD_V%ROWTYPE. This cached record reflects the attributes exposed by the view OE_AK_DEP_PLAN_REQD_V, which represents dependent planning required flag information used during order entry and scheduling flows. The package header was created in March 2009 and is shipped as part of the Order Management feature workbook area (source file OEXDFWKB.pls). The package operates with AUTHID CURRENT_USER, meaning that execution privileges are resolved according to the calling schema rather than the defining schema, and it is referenced by one other package in the application.

Key Procedures and Functions

The package exposes three documented routines:

  • GET_ATTR_VAL_VARCHAR2 — Returns the value of a specified attribute as a VARCHAR2, given an attribute code and a dependent planning requirement record. It provides generic, code-driven access to character-type attributes of the underlying dependent planning record without requiring callers to reference each column directly.
  • GET_ATTR_VAL_DATE — Returns the value of a specified attribute as a DATE, using the same attribute code and record input pattern. It is the date-typed counterpart used when the target attribute stores temporal data, such as planning or requirement dates.
  • SYNC_DEP_PLANNING_CACHE — Synchronizes the package-level cached record (g_cached_record) based on the dependent planning required flag supplied by the caller. It returns a NUMBER, typically acting as a status or success indicator. This routine is the object most directly associated with the sync_dep_planning_cache search term, and it governs refresh of the package global cached record so subsequent attribute lookups reflect current planning requirement values.

Tables Accessed

The documented metadata does not enumerate base tables accessed through APPS synonyms. The package's data contract is defined against the view OE_AK_DEP_PLAN_REQD_V, whose row structure is used both for the package global cached record and for passing records into the attribute retrieval functions. Because the metadata lists no base tables, the package's persistent data interactions are understood indirectly through this view and its dependent planning requirement flag values rather than through direct DML statements. The design indicates a read-oriented utility whose primary state is held in the package-level cache populated by SYNC_DEP_PLANNING_CACHE.

Usage Notes

ONT_DEP_PLANNING_DEF_UTIL is invoked when dependent planning requirement logic must resolve attribute values from the OE_AK_DEP_PLAN_REQD_V structure or refresh cached flag data during an Order Management transaction. Typical invocation occurs from the Order Management order capture flow, where the dependent planning required flag is evaluated to determine whether dependent planning applies to an order line or schedule. Callers first invoke SYNC_DEP_PLANNING_CACHE with the relevant flag so that g_cached_record is current, then call GET_ATTR_VAL_VARCHAR2 or GET_ATTR_VAL_DATE using an attribute code to retrieve the required value. Because the package is defined with AUTHID CURRENT_USER and resides in APPS, execution privileges follow the calling user's schema. Custom extensions or the one identified referencing package may call these routines directly; however, the package is intended as an internal utility rather than a public API, so it should be treated as supporting infrastructure behind Order Management's dependent planning determination features rather than a standalone, documented integration point.