Results for “hr_lei_flex_ddf”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_LEI_FLEX_DDF is an internal Oracle E-Business Suite package owned by the APPS schema and classified under the ETRM taxonomy as an OTHER API object. Its stated purpose is to control the validation processing required for developer descriptive flexfields on a Legal Entity Infrastructure (LEI) entity record. In the file header, this role is abbreviated as ddf (developer descriptive flexfield). The package belongs to the family of HR Legal Entity Infrastructure (HR_LEI_*) packages that mediate the HRMS descriptive flexfield architecture, but it is explicitly scoped to the developer-defined segments rather than the key or global segments.

The package acts as a validation dispatcher. When invoked, it evaluates the reference field value present on the incoming entity record and routes control to the appropriate dependent validation procedure. As documented in the header comments, validation outcome is driven by the value of the relevant entity reference field. This design allows a single entry point to support multiple descriptive flexfield contexts without embedding context-selection logic in every calling API.

Two documented failure conditions exist. First, a failure occurs when the supplied reference field value is not supported by the package. Second, a failure occurs when the reference field value is null but one or more attribute arguments are non-null, because attribute arguments cannot be populated without a corresponding reference field value. On success, processing simply returns to the calling API and continues. The package is annotated with an Access Status of "Internal Development Use Only," indicating it is not intended as a public integration interface.

Key Procedures and Functions

The ETRM metadata documents a single procedure within the package:

  • DDF — The sole documented procedure. It performs the developer descriptive flexfield validation processing for the relevant entity. It accepts the entity record structure as its input argument (referred to as p_rec in the package specification), inspects the record's reference field value, and calls the applicable validation routines based on that value. It returns no value; success is signalled by normal return to the caller, and failure by raising an error under the two conditions described above. No additional parameters, overloads, or helper functions are documented in the provided metadata.

Tables Accessed

The ETRM record for HR_LEI_FLEX_DDF lists no tables accessed through APPS synonyms. This is consistent with the package's declared role as a validation dispatcher: the flexfield definition data it exercises is generally sourced by the dependent validation routines and the HR_LEI shadow record structure (hr_lei_shd.g_rec_type) supplied by the caller, rather than by direct SQL inside this package. No direct reads or writes to base tables are documented, and no package is recorded as referencing HR_LEI_FLEX_DDF. Consequently, the validation logic it invokes should be regarded as operating on data already materialised in the calling API's record structure.

Usage Notes

Because the package is marked "Internal Development Use Only" and is documented with no dependent packages, it is intended to be called from within Oracle's own HR Legal Entity Infrastructure code paths rather than from customer extensions. It is not a standalone concurrent program and is not registered as a form-level API in its own right. Custom code should not invoke HR_LEI_FLEX_DDF.DDF directly, since the record type it consumes is an internal shadow structure and the procedure provides no documented extension hooks.

Developers encountering this package while tracing developer descriptive flexfield behaviour in EBS 12.1.1 or 12.2.2 should treat it as a validation pass-through within the broader LEI flexfield stack. The correct integration point for custom descriptive flexfield logic remains the flexfield definition and the supported public APIs of the owning entity, not this internal package.