Search Results main_address

Overview

APPS.HR_PERSON_INFO_UTIL_SS is a server-side PL/SQL utility package in Oracle E-Business Suite Human Resources (Oracle HRMS) that supports the Person Information self-service flow. It functions as a shared helper library for the "Personal Information" and Contacts modules, coordinating the Oracle Workflow–based approval processing that governs updates to employee and contact records. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, consistent with Oracle EBS coding standards for shared utility APIs.

The package defines a set of global constants that identify workflow section names and action types, including gv_main_address_sect ('MAIN_ADDRESS'), gv_secondary_address_sect ('SECONDARY_ADDRESS'), gv_basic_details_sect ('BASIC_DETAILS'), and gv_contacts_sect ('CONTACTS'). Corresponding action values such as gv_update_main_address_value ('HR_UPDATE_MAIN_ADDRESS'), gv_update_basic_details_value, and gv_add_main_address_value are also declared. These constants indicate that the library is the central reference for how personal information changes—including the user-searched "main address" section—are routed and identified within the HR Person Information workflow. The default result code gv_default_result_code is set to 'HR_SUBMIT_FOR_APPROVAL'.

Key Procedures and Functions

ETRM documents nine callable units within this package. Each serves a validation, control, or workflow-coordination purpose:

• CHECK_PENDING_APPROVAL_ITEMS — Determines whether there are outstanding approval items for a person's information changes, supporting the 'VIEW_PENDING_APPROVAL_CHANGES' view constant.
• PROCESS_ACTION — Central routine for processing a requested action (add, update, delete) against the person information workflow.
• IS_DUPLICATE_PERSON — Checks whether a person record already exists, preventing duplicate creation.
• CREATE_IGNORE_DF_VALIDATION — Establishes an "ignore" marker for descriptive flexfield validation during a transaction, allowing partial or staged data entry to bypass DF validation.
• REMOVE_IGNORE_DF_VALIDATION — Removes the flexfield validation bypass marker established by the companion routine.
• GET_TRNS_EMPLOYEE_NUMBER — Retrieves the employee number associated with the current transaction context.
• CHECK_NI_UNIQUE — Validates uniqueness of a national identifier.
• VALIDATE_NATIONAL_IDENTIFIER — Performs format and business-rule validation on a national identifier value.
• TRANSACTION_API_STEP_EXIST — Determines whether an API transaction step exists for the current process, used to prevent duplicate step creation.

Tables Accessed

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

• WF_ITEM_ATTRIBUTES, WF_ITEM_ATTRIBUTE_VALUES, and WF_ITEM_ACTIVITY_STATUSES — Oracle Workflow tables holding the process section, action type, and approval result code for each person information transaction.
• HR_API_TRANSACTION_STEPS — tracks API transaction step state, used by TRANSACTION_API_STEP_EXIST.
• PER_ALL_PEOPLE_F — the core person/assignment datable, used for duplicate detection and employee number retrieval.
• FND_SESSIONS — provides session context for the current EBS user.
• PLITBLM — the PL/SQL character table type, used internally for list-based processing.

Usage Notes

HR_PERSON_INFO_UTIL_SS is typically invoked from the Oracle HRMS self-service Personal Information and Contacts functionality, and from Oracle Workflow process definitions associated with those flows. ETRM records that the package is referenced by four other packages, confirming its role as a shared dependency rather than an entry-point API. Because its procedures are largely internal helpers, custom code should generally call the formal HRMS person/contact APIs instead. Where direct use is required, developers must observe the workflow attribute conventions exposed by the package constants—particularly the MAIN_ADDRESS section and HR_UPDATE_MAIN_ADDRESS action values—to ensure approval routing remains consistent across releases 12.1.1 and 12.2.2.