Search Results per_kw_xdo_report




Overview
Explore in AI Chat

Overview

APPS.PER_KW_XDO_REPORT is a server-side PL/SQL package belonging to the Oracle HRMS (People/PER) module family. Its name reflects its role as a report-generation utility for HRMS key/worksheet-style reporting that uses Oracle XML Publisher (XDO) technologies. The package encapsulates the logic required to assemble XML data structures, transform them into XFDF/PDF-friendly binary large objects (BLOBs), and persist those artifacts for downstream retrieval and delivery. It is a "noship" development artifact (the header indicates an internal APPLDEV source), which means it is shipped for internal dependency rather than as a public documented API.

The package is classified as OTHER in the ETRM metadata, indicating it is not a formally supported public API but is still referenced by Oracle EBS runtime components. It exposes six documented program units and maintains package-level state including a generic XML record type, an associative array of those records (gxmltable), and a counter (gCtr) used during XML assembly. Its central object model revolves around HRMS reporting extracts covering disability data and contract data, both of which are rendered through XML Publisher and stored as BLOBs.

Key Procedures and Functions

  • get_disability_data — Builds the XML/XFDF payload for the disability report, accepting request, report name, date, business group, organization structure and version, legal employer, disability type, and disability status criteria, and returning the report BLOB.
  • get_contract_data — The procedure referenced by the user's search. It generates the contract report payload, accepting the same common reporting parameters plus a duration and units qualifier, and returns the resulting XFDF BLOB.
  • clob_to_blob — A conversion helper that copies the content of a CLOB into a BLOB, used when the generated XML or template output begins as character data and must be stored or transmitted as binary.
  • Writetoclob — Writes the assembled output to an XFDF BLOB and accepts a total page count parameter, supporting multi-page report assembly and pagination metadata.
  • fetch_pdf_blob — Retrieves a previously generated PDF BLOB for a given report and date, enabling consumers to re-retrieve rendered output rather than regenerate it.
  • get_lookup_meaning — Returns the meaning (display description) for a given lookup type and lookup code, providing the standard HRMS mechanism for resolving coded values into human-readable text in report output.

Tables Accessed

The package reads from core HRMS and FND tables via APPS synonyms. People, assignment, and position data come from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_ALL_POSITIONS. Employment lifecycle context is drawn from PER_PERIODS_OF_SERVICE and PER_WORK_INCIDENTS, while PER_DISABILITIES_F supplies disability attributes used by get_disability_data. Organization hierarchy and job context are sourced from HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, HR_SOFT_CODING_KEYFLEX, PER_JOBS, PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS, supporting the org-structure reporting parameters. FND_LOBS and FND_SESSIONS are used to persist and retrieve generated report artifacts and to manage the requesting session context.

Usage Notes

PER_KW_XDO_REPORT is typically invoked from HRMS concurrent programs and Oracle XML Publisher report definitions that render disability and contract reports. The procedures are also callable from custom PL/SQL that needs to programmatically produce the same XFDF/PDF output, for example when integrating HRMS reporting with a document management or distribution process. Because the package is marked "noship" and classified OTHER, customizations should treat it as an internal dependency rather than a stable public interface; signatures may change between releases. When invoking it, callers should supply a valid request ID and report name, provide the business group and org-structure identifiers where the report is hierarchy-based, and retrieve results through the OUT NOCOPY BLOB parameters. Generated PDFs can subsequently be fetched with fetch_pdf_blob using the report name and date.