Search Results chk_ler_typ_cd

Overview

APPS.BEN_LPL_BUS is a business-layer PL/SQL package within the Oracle E-Business Suite Benefits (BEN) module. It belongs to the family of "BUS" packages that Oracle generates from its table-handler (RHI) and business-rule infrastructure. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoker rather than the definer, and its header carries the internal development marker "Internal Development Use Only."

The package governs operations against the BEN_LER_F ("Learned/Regulatory" information types) entity and its associated child tables, including BEN_LER_PER_INFO_CS_LER_F and BEN_PER_INFO_CHG_CS_LER_F. Its central purpose is the enforcement of business rules that control when child records may or may not be created for specific LER (legislation/regulatory requirement) types. It also provides utility logic for deriving the legislation code associated with a given primary key. The package is referenced by four other packages in the application, confirming its role as a shared validation and DML-support component rather than an end-user-facing API.

Key Procedures and Functions

• RETURN_LEGISLATION_CODE — A function that accepts a LER person-information primary key value and returns the business group's legislation code. It raises an error if the supplied primary key does not exist.
• CHK_LER_ID — A validation procedure invoked by the user search term. It ensures that child records are not created for specific LER types, enforcing the parent-child integrity rule before any insert proceeds.
• CHK_LER_TYP_CD — A companion validation procedure that prevents OSB (Oracle Standard Benefits) customers from creating child records for all LER types except the "ABS" type, restricting child creation to an approved subset.
• INSERT_VALIDATE — The pre-insert validation routine that applies the package's business rules before a new LER record is committed.
• UPDATE_VALIDATE — The pre-update validation routine, applying equivalent checks when an existing LER record is modified.
• DELETE_VALIDATE — The pre-delete validation routine, evaluating whether a LER record may be removed without violating referential or business constraints.

The three validation routines (INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE) form the standard Oracle table-handler triad, ensuring that all DML against the entity passes through consistent rule checking.

Tables Accessed

• BEN_LER_F — The base table holding LER definition records; the primary subject of the validation and DML routines.
• BEN_LER_PER_INFO_CS_LER_F — Child table linking LER records to person information; accessed to confirm child-record existence and prevent prohibited creations.
• BEN_PER_INFO_CHG_CS_LER_F — Related child table for person information changes; read during validation to determine dependent rows.
• FF_FORMULAS_F — The FastFormula repository, referenced when the LER logic depends on defined formulas.
• FND_PRODUCT_INSTALLATIONS — Used to determine the installed product/legislation context, supporting the RETURN_LEGISLATION_CODE derivation.
• ALL_TABLES — An Oracle data dictionary view, typically consulted for existence or metadata checks during validation.

Access to these tables is performed through APPS synonyms, consistent with standard EBS coding conventions.

Usage Notes

BEN_LPL_BUS is not intended for direct invocation by end users or external integrations. It is classified as "Internal Development Use Only" and is normally called from within Oracle Forms (the Benefits LER maintenance windows), from other business-layer packages, and from the generated table-handler/API stack that mediates inserts, updates, and deletes on BEN_LER_F. The four dependent packages reference it to reuse its validation logic. Custom code should avoid calling it directly; any extension of LER validation behavior should instead use the supported public APIs of the benefits module, since the package header is subject to regeneration by Oracle and its internal routines (particularly CHK_LER_ID and its parameter list) are not guaranteed to remain stable across patch levels or releases such as 12.1.1 versus 12.2.2.