Search Results after_report

Overview

CSD_REPAIR_TRAVELER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Service (CSD) product family and supports the Repair Traveler functionality used in depot repair and field service operations. The Repair Traveler is the printed or on-screen routing document that accompanies a unit through the repair process, capturing operation sequences, routing steps, resource requirements, and related repair details associated with a repair order line.

The package is classified as a PVT (private) API, meaning it is not part of the published, supported integration surface. It is intended strictly for internal consumption by Oracle's own reporting and concurrent processing infrastructure. The package header is declared with AUTHID CURRENT_USER, so all SQL executed within its body runs under the privileges of the invoking user rather than the package owner — a common convention for report-support packages that must respect the caller's data security context.

The source header identifies the file as csdvtvls.pls and carries a revision stamp dated 2008, indicating the package has remained stable across releases and is carried forward into EBS 12.1.1 and 12.2.2 without structural change.

Key Procedures and Functions

The ETRM metadata documents two functions in the package specification. Both were auto-generated by the XDO (XML Publisher / BI Publisher) converter, a tool that scaffolds PL/SQL packages to integrate with Oracle's XML-based reporting engine.

• BEFORE_REPORT — A function returning BOOLEAN. It is the standard pre-processing hook invoked by the XDO execution engine before the report data model is processed. Its purpose is to perform any initialization required ahead of the report run, such as resolving setup parameters or preparing session state. The source comment explicitly notes it was auto-generated and "may have data source logic later," indicating it currently contains minimal or placeholder logic.
• AFTER_REPORT — A function returning BOOLEAN. It is the corresponding post-processing hook, invoked after report generation completes. It handles cleanup or finalization tasks. Like BEFORE_REPORT, it is scaffolded by the XDO converter and may remain a stub in current releases.

The package also declares two package-level variables, P_REPAIR_LINE_ID and P_CONC_REQUEST_ID, which are required by the XDO execution context to pass the repair line identifier and the concurrent request identifier into the report session.

Tables Accessed

The ETRM metadata for this package lists no directly referenced tables via APPS synonyms. This is consistent with its role as a report-integration scaffold: the actual data retrieval for the Repair Traveler report is typically defined in the report's data model (XML Publisher data template or underlying query), not in the PL/SQL hook functions. Any table access that does occur is performed at runtime through the caller's schema context, governed by AUTHID CURRENT_USER.

Usage Notes

CSD_REPAIR_TRAVELER_PVT is not intended for direct invocation by customers or third-party developers. It is invoked exclusively by the XDO/BI Publisher runtime when the Repair Traveler report is executed — either from the concurrent manager or from a report launch form. Because it is classified as a private API, Oracle does not guarantee backward compatibility of its signature or behavior across patches.

Custom developers who need to extend Repair Traveler output should do so through supported XML Publisher data template or RTF template modifications rather than by altering this package. Any custom code referencing CSD_REPAIR_TRAVELER_PVT directly risks breakage on upgrade and falls outside Oracle support boundaries. When troubleshooting report failures, the P_CONC_REQUEST_ID and P_REPAIR_LINE_ID values passed into this package are useful for tracing the specific repair line and concurrent request that triggered the error.