Search Results check_gre_without_naic

Overview

APPS.PER_CA_EE_EXTRACT_PKG is a Canadian payroll legislative extract package within Oracle E-Business Suite Human Resources. Its documented API classification is OTHER, indicating it is a supporting utility package rather than a formally published public API. The package supports the extraction of employee-level data required for Canadian statutory reporting, most notably Records of Employment (ROE) and related year-end or periodic legislative extracts. The header comment for the package source includes a build stamp referencing version 120.0.12020000.1, confirming its presence in both the 12.1.1 and 12.2.2 code lines. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling session rather than as definer, which is relevant when it is invoked from concurrent programs or OLTP form sessions.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, several of which are private helpers that support the reporting logic.

• EMPLOYEE_PROMOTIONS — Determines promotions or comparable status changes for an employee assignment within a date range. It is the routine directly associated with the "employee_promotions" search term and is used to evaluate whether a promotion event affects the extract being produced.
• JOB_EXISTS — Validates whether a given job identifier exists in the job definitions referenced by the extract.
• PERSON_TYPE_EXISTS — Validates whether a person type identifier is defined, ensuring only valid person types are processed in the report.
• CHECK_GRE_WITHOUT_NAIC — Scans for Government Remittance Entities (GREs) that lack an assigned NAIC code. A return value of -1 signals an error condition, and the routine returns the offending GRE names in an output collection so the report can list them.
• FORM1, FORM2, FORM2N, FORM3, FORM4, FORM5, FORM6 — A series of formatting and computation routines corresponding to the individual sections of the printed Canadian extract form. Each routine assembles the specific data elements required by its respective section.
• UPDATE_REC — Writes or updates the extracted report lines, persisting the generated output for subsequent printing or archival.

The package declares numerous PL/SQL collection types (for example person, soft-coding, organization, job, person type, NAIC, and segment tables), which are used to batch-fetch and process data efficiently during report generation.

Tables Accessed

The package reads and writes through APPS synonyms covering the following documented tables:

• HR_ORGANIZATION_INFORMATION — Supplies organization-level GRE attributes, including the ORG_INFORMATION8 and organization identifier values used to map remittance entities.
• HR_SOFT_CODING_KEYFLEX — Provides soft-coding keyflex segment values (segments 1 and 6) for cost and legislative distribution on the extract.
• PER_JOBS — Source of job definitions validated by JOB_EXISTS.
• PER_PERSON_TYPES — Source of person type definitions validated by PERSON_TYPE_EXISTS.
• PAY_CA_LEGISLATION_INFO — Canadian legislation information driving statutory extract rules.
• PER_CA_EE_REPORT_LINES — The primary output table, populated and maintained by UPDATE_REC.
• PER_PAY_BASES — Pay basis definitions used to interpret earnings and hours.
• PER_PERIODS_OF_SERVICE — Periods of service and termination data for the employee.
• PLITBLM — PL/SQL index-by table utility structures used internally for array handling.

Usage Notes

PER_CA_EE_EXTRACT_PKG is typically invoked by the Canadian employee extract concurrent program, which produces the printed statutory forms. Because the package is AUTHID CURRENT_USER and depends on the APPS schema and its synonyms, it should be run from a session with appropriate APPS privileges. It is referenced by one other package, indicating it is a component of a larger extract framework rather than a standalone entry point. Customizations should call the documented functions only as designed and avoid direct invocation of the FORM and UPDATE_REC routines outside the report flow, since those routines assume prior validation by CHECK_GRE_WITHOUT_NAIC, JOB_EXISTS, and PERSON_TYPE_EXISTS.