Search Results get_nonrev_perm

Overview

APPS.HR_HEAD_COUNT is a PL/SQL package that supports the Oracle E-Business Suite Human Resources head count reporting infrastructure. Its primary business function is to compute and expose head count metrics for a given organization structure element, distinguishing throughout between revenue (rev) and non-revenue (nonrev) categories of employees and positions. This rev/nonrev bifurcation is characteristic of public-sector and government deployments, where funded head count must be tracked separately for revenue-generating and non-revenue-generating organizational units.

The package defines a PL/SQL record type, HQOrgTableType, that aggregates the full set of head count measures for a single organization, and a collection type, HQOrgTable, indexed by binary integer. All individual accessor functions return NUMBER and are decorated with PRAGMA RESTRICT_REFERENCES(…,WNDS,WNPS), asserting that they neither write database state nor package state — a strong indication that the functions are designed for safe, read-only invocation from SQL and from reporting queries. The package header carries the revision tag perhdcnt.pkh 120.0.12010000.1, dated 2008/07/28, placing its last shipped revision within the 12.1.x code line, which is carried forward unchanged into 12.2.2.

Key Procedures and Functions

The package exposes 35 documented functions, each taking a single p_org_structure_element_id argument identifying the organization structure element to be evaluated. They fall into paired rev/nonrev families:

• Starting and ending values: GET_REV_START_VAL, GET_NONREV_START_VAL, GET_REV_END_VAL and GET_NONREV_END_VAL return the opening and closing funded head count for the element.
• Employment category counts: GET_REV_PERM / GET_NONREV_PERM (permanent), GET_REV_CONT / GET_NONREV_CONT (contract), GET_REV_TEMP / GET_NONREV_TEMP (temporary), and GET_REV_NH / GET_NONREV_NH plus GET_REV_CUR_NH / GET_NONREV_CUR_NH (non-head count and current non-head count).
• Movement metrics: GET_REV_TRANSFER_IN / GET_NONREV_TRANSFER_IN and GET_REV_TRANSFER_OUT / GET_NONREV_TRANSFER_OUT quantify transfers between organization elements.
• Recruitment pipeline: GET_REV_OPEN_OFFERS / GET_NONREV_OPEN_OFFERS return the count of offers extended but not yet accepted — the function most directly associated with the term get_nonrev_open_offers. GET_REV_ACCEPTED_OFFERS / GET_NONREV_ACCEPTED_OFFERS return offers that have been accepted.
• Additional measures: vacant FTE, voluntary termination, involuntary termination, and current termination counts are exposed through their corresponding rev/nonrev function pairs.

Tables Accessed

The package reads from the following APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — the primary source of active assignment rows used to derive current head count and employment category, including assignment category and status.
• PER_ASSIGNMENT_STATUS_TYPES — supplies the status classification used to distinguish current, terminated and non-head-count assignments.
• PER_PERIODS_OF_SERVICE and PER_PERIODS_OF_PLACEMENT — provide service and placement dates underpinning start, end, transfer and termination measures.
• PER_ORG_STRUCTURE_ELEMENTS and PER_ORG_STRUCTURE_VERSIONS — resolve the organization structure element and its effective version.
• PER_REQUISITIONS — the source for requisition-derived offer activity, supporting the open and accepted offer functions.
• FF_FORMULAS_F — supplies Fast Formula definitions used to evaluate derived head count rules.
• DUAL — used for single-row scalar evaluation.

Usage Notes

HR_HEAD_COUNT is a read-only reporting utility rather than a transactional API, as confirmed by its RESTRICT_REFERENCES declarations. It is typically invoked from the Oracle HRMS head count and establishment reporting forms and concurrent programs, and from custom SQL or PL/SQL that needs rev/nonrev head count figures by organization structure element. Because the accessor functions are pure with respect to database and package state, they can be called safely from SELECT statements. The package is referenced by one other package within the ETRM metadata set, indicating it is consumed as a supporting layer rather than being an entry point itself; callers should therefore be aware that upstream organization structure versions must be correctly defined for results to be meaningful.