Results for “abs_pay_info_src_comp”

14 results




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

Overview

PQP_OMP_TEMPLATE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PQP – Public Sector Payroll product. Its stated purpose is to expose all absence information elements that are created by the OMP (absence management) element template. In practice, the view decodes the flexfield-style EI_INFORMATION* attributes stored against payroll element types into named, human-readable columns such as LOS_CALC, LOS_DURATION, LOS_UOM, and ABS_DAYS, so that absence element configuration can be queried without manually interpreting segment numbers. The view is read-only and carries a VALID status, indicating it is compiled and usable in both 12.1.1 and 12.2.2 environments. It is typically consumed for configuration auditing, payroll integration mappings, and reporting on absence plans and their associated lengths of service (LOS) and average earnings rules.

Underlying Base Objects

The view joins several synonym-based base objects. Core element definition data comes from PAY_ELEMENT_TYPES_F (PETF), which supplies identification, naming, legislation, processing type, priority, and audit columns. The extended attributes are held in PAY_ELEMENT_TYPE_EXTRA_INFO (PETEI), whose EEI_INFORMATION1 through EEI_INFORMATION30 columns are mapped to semantic names. Classification lookup data is joined from PAY_ELEMENT_CLASSIFICATIONS (PEC) and through it the HR_LOOKUPS view (HRL) for meaning values. Template linkage is established via PAY_ELEMENT_TEMPLATES (PET) and PAY_TEMPLATE_CORE_OBJECTS (PTCO). Benefit plan information is resolved from BEN_PL_F (BPL) and BEN_PL_TYP_F (BPTY). User-defined absence entity tables are resolved from PAY_USER_TABLES aliased PUT1 and PUT2. The metadata also lists FND_SESSIONS (SES) as the session context, plus the FND_NUMBER and HR_API packages available for use in the defining query.

Key Columns

Common Use Cases and Queries

Typical uses include verifying how absence elements were created by the OMP template, extracting LOS unit-of-measure settings for interface mapping, and producing configuration extracts for audits or data migration. A query targeting the searched term might be:

  • SELECT element_name, plan_name, los_calc, los_duration, los_uom FROM pqp_omp_template_v WHERE legislation_code = 'US';
  • SELECT element_name, avgearn_duration, avgearn_uom, avgearn_balname FROM pqp_omp_template_v;
  • SELECT element_name, abs_days, primary_abs_info_ele_flag FROM pqp_omp_template_v WHERE primary_abs_info_ele_flag = 'Y';

Because the view derives effective-dated rows from PAY_ELEMENT_TYPES_F, queries comparing current configuration should filter or order by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. Access is granted to the view in the APPS schema, so reporting should be executed with an account holding the appropriate APPS responsibilities or synonym grants.