Search Results per_ppc_flex

Overview

APPS.PER_PPC_FLEX is a PL/SQL package body in the Oracle E-Business Suite Applications schema (APPS) whose name associates it with the Oracle Human Resources "PER" module. The prefix "PPC" corresponds to the Payroll/Primary Payroll Costing area, while "FLEX" indicates that the package exists to support Flexfield-related processing — specifically the Descriptive Flexfield (DFF) handling used by the Primary Payroll Costing (PPC) feature. In Oracle EBS 12.1.1 and 12.2.2, the PPC facility allows an organization to designate a payroll as the primary payroll for costing purposes, and it invokes descriptive flexfields to capture and validate additional costing- and grouping-related attributes entered by users.

The package body is documented in ETRM with a status of VALID and an API classification of "OTHER," meaning it is not a published, supported public API but rather an internal implementation package. In practical terms, PER_PPC_FLEX encapsulates the server-side logic that reads and writes the descriptive flexfield segments for the PPC entity, executes the associated value-set validation, and returns the flexfield structure and values to the calling UI. It therefore forms the technical backbone that lets Oracle HRMS Forms and concurrent processes present and store the PPC descriptive flexfield without placing that logic directly in the form or in a client-side library.

Key Procedures and Functions

ETRM documents a single procedure or function in this package body: DF.

• DF — The routine is named after the descriptive flexfield it serves. Its purpose is to support the PPC descriptive flexfield by performing the operations required at runtime, typically the retrieval of flexfield definition metadata (segments, structure, prompts and validation information) and the processing of segment values entered by the user. As the only documented entry point, DF is the routine invoked whenever the PPC flexfield must be initialized or populated. ETRM does not publish the formal parameter list for this routine, so no signature is asserted here; the behavior described is limited to the documented fact that DF is the package's sole documented program unit.

Tables Accessed

ETRM does not enumerate base tables accessed through APPS synonyms for PER_PPC_FLEX. The documented dependency list identifies the following referenced database objects instead:

• HR_UTILITY (APPS) — the shared Oracle HRMS utility package that supplies common date, value-set and error-handling helpers used throughout the HR product family; PER_PPC_FLEX depends on it for standard processing routines.
• PER_PPC_FLEX (self-reference) — indicating internal recursion or invocation of package-level constructs within the body itself.
• PER_PPC_SHD (APPS) — the shadow/support package for the PPC feature, from which PER_PPC_FLEX draws additional PPC-specific routines or data access code.
• STANDARD (SYS) — the Oracle kernel's standard PL/SQL package providing the default implementation of core language behavior.

No underlying HR/FND flexfield tables are conclusively identified in the provided metadata; descriptive-flexfield packages of this type characteristically read FND_DESCRIPTIVE_FLEXS, FND_FLEX_VALUES and related value-set definitions, but these are not documented here and should be treated as likely rather than confirmed.

Usage Notes

PER_PPC_FLEX is an internal implementation package. ETRM records that it is not referenced by any database object, which confirms it is not exposed as a dependency for other packages; it is instead invoked at the top of the call chain — most commonly from Oracle HRMS Forms and from PPC-related concurrent programs when the PPC descriptive flexfield is displayed, validated or saved.

• When invoked from an Oracle Forms-based PPC window, the package is called to populate and validate the descriptive flexfield segments for the current PPC record.
• Because its classification is "OTHER" and it is not part of the published HRMS API surface, it is not intended for direct invocation from custom code. Customers and integrators should use supported public APIs or the PPC setup UI, allowing this package to run beneath them.
• The dependency on HR_UTILITY and PER_PPC_SHD means the package must always execute within the APPS schema context so that the required synonyms and privileges are available.

Customizations that modify or bypass this package are unsupported and may be overwritten by patching or cloning operations in either 12.1.1 or 12.2.2.