Search Results lp_trip

Overview

WSH_WSHRDVLS_XMLP_PKG is the generated PL/SQL package associated with the Oracle E-Business Suite XML Publisher (BI Publisher) concurrent program report used during the shipping and delivery confirmation cycle. The package name reflects its origin as an XML Publisher data model / report definition built against the WSH (Shipping Execution) schema. In releases 12.1.1 and 12.2.2 the package is owned by APPS and is classified as OTHER within the ETRM repository, meaning it is not published as a formal public API but is a report-support package whose globals and helper functions are consumed by the report template and by the concurrent program's data source.

The core business function is to extract delivery-leg and consolidated-delivery information for printing and confirmation purposes. The package holds report-level bind and global variables — including P_TRIP_ID, P_SOB_ID, P_CONC_REQUEST_ID, P_DEBUG, RP_SUB_TITLE and the notable LP_TRIP character variable — that are populated at runtime by the report layout and passed into the report's queries. In this context, "lp_trip" (lexical parameter TRIP) holds the trip identifier value used to filter and format delivery-leg output on the printed report. The report's subtitle and company-name logic is driven from the same package, allowing the template to display set-of-books-specific headings.

Key Procedures and Functions

The documented program units number six:

• BEFOREREPORT — The Oracle Reports / XML Publisher "before report" trigger function. It initialises package globals and performs setup work prior to the main data query execution, returning a BOOLEAN success indicator.
• AFTERREPORT — The complementary "after report" trigger, executed once the main result set has been produced. It supports any required cleanup or finalisation of report state, again returning BOOLEAN.
• AFTERPFORM — The "after parameter form" trigger. It runs after the concurrent program parameters have been accepted and validated, and is typically used to derive or default values such as the trip or SOB identifiers before the query block is invoked.
• C_COMPANY_NAME — A report column/group function returning VARCHAR2 that supplies the company (organisation) name for the report header, resolved from the SOB or operating unit context established at runtime.
• CF_CONSOL_DELIVERY_NAMEFORMULA — A formula-column function (the "CF_" prefix denotes a report formula column) taking a parent delivery leg identifier and returning the corresponding consolidated delivery name. It is used to render a human-readable consolidated shipment label alongside each detail line.
• RP_SUB_TITLE_P — A report parameter/global accessor returning VARCHAR2, exposing the RP_SUB_TITLE global so the template can print the dynamic sub-title (for example, trip or delivery context).

No parameter lists are documented for these units; only their declared names and purposes are authoritative.

Tables Accessed

The package's report queries read from two Shipping Execution tables via APPS synonyms:

• WSH_DELIVERY_LEGS — the core delivery-leg detail table. Delivery legs represent each stop or movement within a trip/delivery, carrying the leg identifier, delivery association, sequence and status information that the report prints. The PARENT_DELIVERY_LEG_ID argument of the consolidated-delivery-name formula is sourced from this table's hierarchy.
• WSH_NEW_DELIVERIES — the delivery header table (the 11i/12.x "new deliveries" model). It supplies delivery name, organisation and status attributes joined to the legs, enabling the report to resolve the consolidated delivery name and company context.

The package references no other documented tables, and ETRM records zero packages referencing it, confirming it is a leaf-level report dependency rather than a shared utility.

Usage Notes

WSH_WSHRDVLS_XMLP_PKG is typically invoked indirectly: it is called by the XML Publisher concurrent program at run time, using the concurrent request identifier (P_CONC_REQUEST_ID) to bind the report's data source. The LP_TRIP variable that users search for is not a standalone API entry point; it is a package-level global populated from the report's TRIP parameter, consumed by the data model's WHERE clause and formatting logic. Administrators and developers should therefore treat LP_TRIP, P_TRIP_ID, P_SOB_ID and RP_SUB_TITLE as runtime state rather than callable interfaces.

Because the package is generated and marked noship in its header, it should not be modified directly; customisations belong in the underlying XML Publisher data template or in a separate custom package. Any change to shipping report behaviour in 12.1.1 or 12.2.2 should be validated against the standard WSH delivery-confirmation concurrent program and its associated template, since regeneration of the report definition can overwrite edits to this package.