Search Results dep_plan_required

Overview

ONT_DEP_PLANNING_DEF_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Management (ONT) module and supports the dependent planning requirement functionality associated with the Order Entry Toolkit. The package name reflects its role as a utility (UTIL classification) for the Dependent Planning definition area, and its primary responsibility is to expose attribute values from the OE_AK_DEP_PLAN_REQD_V view through a standardized access interface. The package was created on 30-MAR-09 and carries the internal header identifier OEXDFWKB.pls version 115.0. Its global constant G_PKG_NAME identifies the package, and the global variable g_database_object_name is initialized to the value OE_AK_DEP_PLAN_REQD_V, which is the underlying database object supplying the dependent planning records consumed by the utility functions.

Key Procedures and Functions

Three program units are documented for this package:

• GET_ATTR_VAL_VARCHAR2 — Accepts an attribute code and a record typed against OE_AK_DEP_PLAN_REQD_V%ROWTYPE, returning a VARCHAR2 value. It resolves the dependent planning required flag for the requested attribute. The documented logic recognizes both DEP_PLAN_REQUIRED and DEP_PLAN_REQUIRED_FLAG as valid attribute codes, returning record.DEP_PLAN_REQUIRED_FLAG when the value is not FND_API.G_MISS_CHAR and NULL otherwise. Unrecognized attribute codes also return NULL.
• GET_ATTR_VAL_DATE — Mirrors the varchar2 variant but returns a DATE. For the same two recognized attribute codes it converts DEP_PLAN_REQUIRED_FLAG using the format mask 'RRRR/MM/DD HH24:MI:SS', returning NULL when the source value is FND_API.G_MISS_CHAR or the attribute code is unrecognized.
• SYNC_DEP_PLANNING_CACHE — Synchronizes the dependent planning cache, ensuring cached dependent planning requirement data remains consistent with the underlying view. This unit supports the caching strategy employed around dependent planning definitions.

Tables Accessed

The documented database object referenced by this package is OE_AK_DEP_PLAN_REQD_V, a view accessed through an APPS synonym. Both attribute accessor functions operate against a row of this view, and the global g_database_object_name explicitly names it. The view supplies the DEP_PLAN_REQUIRED_FLAG column, which records whether dependent planning is required. No other tables are documented in the metadata. The SYNC_DEP_PLANNING_CACHE unit works in conjunction with this view to keep in-memory or cached dependent planning definitions synchronized with the persistent data.

Usage Notes

The package is referenced by one other package and is typically invoked indirectly through the Order Entry dependent planning framework rather than directly by end users. Its accessor functions provide a uniform, attribute-code-driven retrieval pattern that allows generic attribute-handling code to obtain dependent planning values as either character or date types, while correctly honoring FND_API.G_MISS_CHAR as an unset marker. This pattern is characteristic of Oracle's AK (Attribute Knowledge) style attribute resolution used by order capture and dependent planning configuration in Release 12. Customizations that extend dependent planning attributes should call these functions rather than reading OE_AK_DEP_PLAN_REQD_V directly, so that missing-value handling and attribute-code translation remain consistent. Because the package is a utility body with no documented concurrent program registration, it is not exposed as a standalone executable; it is invoked from forms, other packages, or custom PL/SQL that processes dependent planning requirement records.