Search Results get_parent_org_id

Overview

APPS.PER_CN_SHARED_INFO is a shared PL/SQL utility package within the Oracle E-Business Suite Human Resources (PER) product family. The "CN" prefix designates it as a country-specific localization component, and the package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than as the APPS owner. Its header comment (pecnshin.pkh 120.1) dates the version to May 2010, confirming its presence in the 12.1.1 code line and its continued deployment in 12.2.2.

The package centralizes reusable lookup and organizational-hierarchy logic that is otherwise duplicated across country-specific HR extensions. It exposes helper functions that resolve descriptive text for coded values, retrieve person-level documentation and cadre/technical-post details as of a given effective date, and — the function that prompted the current search — resolve the parent organization for a supplied organization identifier. Because it is classified as OTHER rather than as a public or private API, Oracle does not formally guarantee its signature across releases, although it remains stable in practice and is referenced by one other documented package.

Key Procedures and Functions

• GET_LOOKUP_MEANING — Accepts a lookup code and lookup type and returns the corresponding meaning (displayed description) as a VARCHAR2. It provides a thin wrapper over FND_LOOKUP_VALUES, sparing callers from writing the standard join themselves.
• CN_GET_DOC_DETAILS — Takes a person identifier, an effective date, and a type indicator, returning documentation detail as a VARCHAR2. It supports country-specific personnel documentation requirements.
• GET_PARENT_ORG_ID — Accepts a single organization identifier and returns the parent organization identifier as a NUMBER. This is the function most frequently targeted by developers searching for parent-organization resolution logic. Internally it traverses the HR organization hierarchy, relying on the organization structure and structure element tables rather than a simple parent-organization column, and it honors the currently effective structure version.
• GET_CADRE_JOB_DETAILS — Takes a person identifier and date and returns cadre and job information as a VARCHAR2, describing the individual's cadre classification and associated job at that point in time.
• GET_TECH_POST_DETAILS — Takes a person identifier and date and returns technical post details as a VARCHAR2, supporting assignments specific to technical positions.

All five functions are declared in the package specification and are directly callable from SQL and PL/SQL. No parameter lists beyond those shown in the specification should be assumed.

Tables Accessed

The documented table references are consistent with the package's stated purpose:

• FND_LOOKUP_VALUES — source of lookup meanings for GET_LOOKUP_MEANING.
• HR_ORGANIZATION_INFORMATION — descriptive and classified organization attributes used during hierarchy resolution.
• PER_ALL_PEOPLE_F — dated person records, providing the effective-dating context for the person-based functions.
• PER_ANALYSIS_CRITERIA and PER_PERSON_ANALYSES — the person-analysis (extra information type) framework, used to store and retrieve cadre, technical post, and documentation attributes.
• PER_PEOPLE_EXTRA_INFO — additional person-level descriptive detail keyed to the person and information type.
• PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS — the organization hierarchy model traversed by GET_PARENT_ORG_ID to identify the parent organization within the applicable structure version.

All access is through APPS synonyms, and reads dominate; the package is a query utility rather than a transactional API.

Usage Notes

Because PER_CN_SHARED_INFO is a shared helper, it is typically invoked indirectly — from Oracle Forms personalizations and custom library routines, from country-specific concurrent programs and reports, and from custom PL/SQL that needs an effective-dated person detail or a parent organization without reimplementing the underlying joins. GET_PARENT_ORG_ID in particular is useful when a developer needs the hierarchy parent of an organization without querying PER_ORG_STRUCTURE_ELEMENTS directly, since the function applies the correct effective structure version automatically.

Callers should note three constraints. First, the functions are not bulk-enabled; each call resolves a single person or organization, so high-volume loops should be avoided in favor of set-based SQL. Second, the person-based functions require an effective date, and passing a date outside the person's active record range yields no detail. Third, since the package is classified OTHER and was last revised at version 120.1, custom code should treat the signatures as stable but unsupported, and should be regression-tested on any upgrade between release 12.1.1 and 12.2.2, as Oracle reserves the right to modify non-public interfaces.