Search Results pay_element_templates_s

Overview

PAY_ETM_INS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, documented as VALID under both release 12.1.1 and 12.2.2. It forms part of the Oracle Payroll Element Template Maintenance (ETM) framework, the component responsible for the storage, validation, and lifecycle management of element templates. Element templates are the metadata definitions from which payroll elements are generated; they determine element classification, input values, processing rules, and the resulting payroll calculations.

The package is classified in the ETRM repository as API classification OTHER, indicating that it is an internal implementation unit rather than a formally published public API. Within the ETM subsystem it functions as the insertion layer: the component that writes new element template records into the underlying schema on behalf of the business logic and shared services that surround it. The dependency graph confirms this role. PAY_ETM_INS depends on PAY_ETM_BUS (the business rules layer for element templates), PAY_ETM_SHD (shared/common logic), and PAY_ELEMENT_TEMPLATES and PAY_ELEMENT_TEMPLATES_S, together with supporting infrastructure such as HR_API, HR_UTILITY, DUAL, and STANDARD.

Key Procedures and Functions

The documented package metadata lists two procedures or functions, one of which is identified by name: INS.

• INS — The primary insertion routine. Its documented purpose is to create element template records within the ETM data model. Consistent with the naming convention used throughout Oracle HRMS and Payroll packages, the INS procedure encapsulates the insert-time processing required before and after a row is written to the element template tables.
• Second documented entry — The metadata records a total of two procedures or functions for this package body but does not expose the name of the second entry point in the excerpt provided. In practice, an insertion package of this type typically also exposes a helper or wrapper that orchestrates validation, defaulting, or post-insert processing called by INS. The exact identity of this second entry point cannot be confirmed from the available dependency and ETRM data.

No parameter lists are documented for either entry point, and none are reproduced here. Callers should obtain signature details from the source definition in the APPS schema rather than relying on inferred interfaces.

Tables Accessed

The package operates directly against two documented tables, both referenced through APPS synonyms:

• PAY_ELEMENT_TEMPLATES — The primary transactional table for element template definitions. The insertion logic in PAY_ETM_INS writes new template rows here, establishing the element template header and its associated definition data.
• PAY_ELEMENT_TEMPLATES_S — The corresponding secondary table (the _S suffix follows the Oracle HRMS convention for a related or shadow table in the template data model). The package writes to and reads from this table as part of the same insertion transaction, ensuring the template record is persisted consistently across both tables.

In addition, the dependency list shows references to HR_API and HR_UTILITY, which are invoked for validation, date-tracked or business-group-aware processing, and standard error handling rather than for direct table access by this package. PAY_ETM_BUS and PAY_ETM_SHD supply the business logic and shared routines that INS coordinates.

Usage Notes

PAY_ETM_INS is not a standalone user-facing program. It is invoked from other PL/SQL units in the ETM stack, principally PAY_ETM_BUS, and is reached when element templates are created through the standard Oracle Payroll element template maintenance flows. The ETRM metadata records that PAY_ETM_INS is not referenced by any database object within the documented scope, while the package itself references several; this indicates it sits at the top of the internal call chain for template insertion rather than being called outward from forms or concurrent programs directly.

Custom code should treat PAY_ETM_INS as an internal implementation package. Direct invocation is not supported by Oracle, and the supported integration surface for element template creation is the published business API layer (PAY_ETM_BUS and related public APIs). Because the package is marked VALID and is not referenced externally, it should be expected to change between patch levels without notice. During upgrades or patching, the package is recompiled as part of the APPS schema, and any invalidated dependent objects — particularly PAY_ETM_BUS — should be revalidated alongside it.