Search Results set_document_data




Overview
Explore in AI Chat

Overview

PQH_SS_PRINT is an Oracle EBS Applications (APPS) PL/SQL package used within the Public Sector/HR (PQH) product family to support document generation and printing for HR self-service and transactional workflows. Its name follows the PQH_SS_ prefix convention, indicating a self-service supplier role, and the _PRINT suffix indicating that its primary responsibility is assembling the data required by print-oriented concurrent or document-generation processes rather than performing the underlying business transaction itself.

In Oracle EBS 12.1.1 and 12.2.2, this package functions as a data-preparation and conversion utility layer. It gathers transactional context, resolves internal code values into human-readable meanings, and populates temporary staging data that a printing or document template engine can consume. The package exposes both the entry points expected by the calling framework (populate_temp_data, set_eff_dte_for_refresh_atts) and an extensive set of conversion functions used to translate stored lookup codes into displayed text on printed output.

Key Procedures and Functions

The package is divided into procedures that orchestrate data preparation and functions that resolve individual values.

  • SET_EFF_DTE_FOR_REFRESH_ATTS — establishes the effective date used when refreshing attribute values, ensuring the print extract reflects the correct point-in-time state of HR data.
  • POPULATE_TEMP_DATA — the principal extraction procedure; given a transaction identifier, effective date, and document short name, it writes the required print data into a temporary structure and returns a session identifier for downstream retrieval.
  • GET_FUNCTION_PARAMETER_VALUE — retrieves the value of a named function parameter for a transaction, honoring the supplied parameter type and effective date.
  • SET_DOCUMENT_DATA — stores a tag/value pair representing a single document data element for later merge into the printed document.
  • GET_SESSION_DETAILS — returns the transaction, session, and effective date context associated with the current print session.

The remainder of the package consists of single-purpose conversion functions that translate coded values into descriptive text for display on printed output. These include GET_TABLE_ROUTE_ID, GET_TENURE_STATUS, GET_QUALIFICATION, GET_AWARD_STATUS, GET_TUITION_METHOD, GET_CURRENCY_MEANING, GET_PERSON_TITLE, GET_GENDER, GET_MARITAL_STATUS, GET_TERMINATION_REASON, GET_WORK_SCHEDULE_FREQUENCY, GET_EMPLOYEE_CATEGORY, GET_EMPLOYMENT_CATEGORY, GET_YES_NO, and GET_ESTABLISHMENT. Collectively these functions shield the document layer from raw lookup codes and internal identifiers.

Tables Accessed

Through APPS synonyms, PQH_SS_PRINT reads from several core EBS tables. HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, and HR_API_TRANSACTION_VALUES provide the transactional context and attribute values that drive the extract. PER_ALL_PEOPLE_F supplies person and assignment data, while PER_ASSIGNMENT_STATUS_TYPES and PER_PAY_BASES support conversion of status and pay basis codes. FND_CURRENCIES, FND_FORM_FUNCTIONS, and FND_SESSIONS provide currency meanings, function parameter definitions, and print session context. PQH_TABLE_ROUTE and FF_FORMULAS_F support routing and formula resolution, and the PAY tables (PAY_ALL_PAYROLLS_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F) contribute payroll-related descriptive values. PER_PAY_PROPOSALS is also referenced for proposal data.

Usage Notes

This package is not a business API in the transactional sense and exposes no documented interface for creating or updating HR records. It is invoked indirectly by self-service print flows and by concurrent programs responsible for producing HR documents such as employee records, assignment letters, and similar printed artifacts. Custom code that needs to reproduce formatted HR print output can call POPULATE_TEMP_DATA followed by the relevant GET_* conversion functions, though the package is best treated as an internal implementation detail of the PQH self-service print framework. Because referenced-by count is zero, no other documented package depends on it, and direct calls should be made with awareness that standard patch application may modify its behavior.