Results for “p_locn_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HXC_RPT_TC_AUDIT_TRAIL is an Oracle Applications (APPS) PL/SQL package that supports the Time and Labor audit trail reporting capability within Oracle E-Business Suite. Its purpose is to assemble and present the historical record of changes made to timecard data, allowing administrators, payroll personnel, and supervisors to review who changed a timecard, when the change occurred, and what regenerated or saved data resulted. The package is primarily a reporting engine that drives a concurrent-program-style audit trail output. It accepts a set of filter parameters — date range, data regeneration flag, record save flag, and optional organization, location, payroll, supervisor, and person identifiers — and produces the audit information for the selected population. The package is documented in ETRM for both 12.1.1 and 12.2.2 with an API classification of OTHER, indicating it is an internal supporting package rather than a public integration API. The source header (hxcrptaudittrail.pkh, 120.4.12010000.2) shows the package has been stable since the 12.1 code level.

Key Procedures and Functions

• AFTERPFORM — A report trigger function returning BOOLEAN, invoked after the parameter form is submitted. It performs post-parameter-form processing.
• BEFOREREPORT — A report trigger function returning BOOLEAN, executed before the report body is generated; typically used to initialize state and resolve parameters.
• AFTERREPORT — A report trigger function returning BOOLEAN, executed after report generation completes, used for cleanup and finalization.
• TRANSLATE_PARAMETERS — Translates the internal package-level parameter variables into the form required by the report, and resolves descriptive values (organization, location, payroll, supervisor, and person names) from the numeric identifiers supplied by the user.
• EXECUTE_AUDIT_TRAIL_REPORTING — The principal driver procedure. It accepts the date range, data regeneration and record save flags, and the optional org, location, payroll, supervisor, and person identifiers, then produces the audit trail report output.

The package also declares several collection types (NUMTABLE, VARCHARTABLE, DATETABLE, FLOATTABLE, TIMEDETAILSTABLE, AUDITTABLE) and a set of package-level parameters and local variables that hold the filter values and their translated display equivalents.

Tables Accessed

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

• HXC_RPT_TC_AUDIT and HXC_RPT_TC_DETAILS_ALL — the primary audit and timecard detail tables from which the audit trail is constructed.
• HXC_RPT_TC_HIST_LOG — the historical log that records change activity over time.
• HXC_TIMECARD_SUMMARY — summarized timecard data used to reconcile the audit view.
• HXC_TIME_BUILDING_BLOCKS — the underlying time building blocks that compose timecard entries.
• FND_USER — resolves the user who performed each change.
• HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, PAY_ALL_PAYROLLS_F, and PER_ALL_PEOPLE_F — supply descriptive names for organizations, locations, payrolls, and people used as report filters and display values.
• DBMS_UTILITY and PLITBLM — utility packages used for error formatting and PL/SQL table manipulation.

Usage Notes

HXC_RPT_TC_AUDIT_TRAIL is invoked through the Oracle Reports and concurrent program framework rather than from external application code. It is referenced by zero other packages in the ETRM metadata, confirming it functions as a terminal reporting component. The AFTERPFORM, BEFOREREPORT, and AFTERREPORT triggers indicate it is bound to an Oracle Reports definition, while EXECUTE_AUDIT_TRAIL_REPORTING exposes the runnable entry point, commonly called from a concurrent program or the report's parameter form. Callers supply the date range and optional org, location, payroll, supervisor, and person filters to scope the audit trail. Because the package relies on HR and payroll descriptive tables, the calling user's security profile governs which organizations, locations, and people are visible. When customizing or troubleshooting audit trail output, note that the report generation depends on the HXC_RPT_TC_AUDIT, HXC_RPT_TC_DETAILS_ALL, and HXC_RPT_TC_HIST_LOG tables being populated; without corresponding change history, the audit trail will return no rows for the selected criteria.