Search Results permit_extended_pay_poi

Overview

APPS.PE_POI_BUS is the business (BUS) layer package body for the Position Extra Information entity within Oracle HRMS / Oracle E-Business Suite. Position Extra Information, stored in PER_POSITION_EXTRA_INFO, allows implementations to capture supplementary, customer-defined attributes that are associated with a position (PER_ALL_POSITIONS / HR_ALL_POSITIONS_F) but are not part of the seeded position model. Typical examples include extended pay, budget, or permitting-related attributes; users searching for permit_extended_pay_poi are generally working with configurations where position-level "extra pay" or permit information is stored as a Position Extra Information row type.

The package acts as the business-rule and validation layer that sits beneath the corresponding Table Handler (PE_POI_SHD / the _TAPI wrapper). It does not itself perform the DML against the base table; rather it encapsulates the pieces of logic that the Table Handler calls during its insert, update, and delete processing. Its responsibilities are to derive the security group for Row Level Security (RLS), resolve the legislation code for the row, enforce mandatory-argument and lookup validation, and prevent impermissible mutation of non-updateable columns. In the Oracle EBS 12.1.1 and 12.2.2 releases this object is a standard APPS-owned PL/SQL package body shipped as part of the HRMS product family, with the header comment showing revision 120.0.

Key Procedures and Functions

• SET_SECURITY_GROUP_ID — Derives the security_group_id for the current business group context by joining PER_POSITION_EXTRA_INFO to PER_BUSINESS_GROUPS via HR_ALL_POSITIONS_F. This value is used by the Table Handler to populate the RLS column on the row.
• RETURN_LEGITIMATION_CODE — Returns the legislation code associated with the row, using the package globals g_legislation_code and g_position_extra_info_id to cache the lookup between calls.
• CHK_POSITION_INFO_TYPE — Validates the Position Information Type attribute against PER_POSITION_INFO_TYPES, ensuring the extra information being recorded is a defined type.
• CHK_POSITION_ID — Validates the Position Id foreign key against HR_ALL_POSITIONS_F.
• CHK_MULTIPLE_OCCURENCES_FLAG — Validates the multiple-occurrence indicator, controlling whether more than one row of the same information type may exist for a position.
• CHK_NON_UPDATEABLE_ARGS — Enforces that columns defined as non-updateable are not altered on an update call, raising the standard HR_API error when they are.
• INSERT_VALIDATE — Aggregates the applicable row-level validations invoked before an insert is committed.
• UPDATE_VALIDATE — Aggregates the applicable row-level validations invoked before an update is committed, including the non-updateable-argument check.
• DELETE_VALIDATE — Aggregates the validations invoked before a delete is committed.

Tables Accessed

• PER_POSITION_EXTRA_INFO — The primary entity; read for validation and security-group derivation and written by the Table Handler layer.
• PER_POSITION_INFO_TYPES — Lookup table validating the Position Information Type against seeded or user-defined types.
• HR_ALL_POSITIONS_F — Used both to validate the Position Id and, via its business_group_id, to resolve the security group through PER_BUSINESS_GROUPS.
• FND_SESSIONS — Read to obtain the current session's business group / security context when deriving RLS information.

Usage Notes

PE_POI_BUS is not normally called directly by end users. It is invoked indirectly from the HRMS Position Extra Information maintenance form, from the Position Extra Information Table Handler (and therefore from the associated TAPI), and from any custom code or concurrent program that maintains position extra information through the supported API rather than through direct DML on PER_POSITION_EXTRA_INFO. Because it is referenced by three other packages, changes to its validation logic ripple through the HRMS position maintenance stack. Customizations that need to add or relax validation for position extra information—such as extended pay or permit-related attributes—should be evaluated against these documented procedures, and direct updates to the base table should be avoided in favor of the packaged API to preserve the security group, legislation code, and validation behaviour described above.