Search Results f_sort_order




Overview

WSH_WSHRDOPN_XMLP_PKG is a report-support package body owned by APPS that underpins the Oracle Shipping open orders extract. Its purpose is to assemble the data bind variables and derived values required by the XML Publisher (BI Publisher) report definition that prints the open (unshipped) order or delivery information for a given warehouse. The package performs the classic Oracle Reports-to-XML-Publisher wrapper role: the report definition invokes it at defined trigger points, and the package resolves organization codes, organization names, customer details, item display meanings and picking batch references, then hands those values back as bind parameters used by the report's data model and format triggers.

In EBS 12.1.1 and 12.2.2 this pattern is typical of converted report templates where the original PL/SQL library logic was consolidated into a package body. The package operates on the operational warehouse dataset — MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, HZ_CUST_ACCOUNTS, MTL_SYSTEM_ITEMS_KFV and WSH_PICKING_BATCHES — making it read-only with respect to transactional data.

Key Procedures and Functions

Tables Accessed

  • MTL_PARAMETERS — resolves ORGANIZATION_CODE for the entered organization id.
  • HR_ALL_ORGANIZATION_UNITS — resolves the organization NAME for header display.
  • HZ_CUST_ACCOUNTS — resolves ACCOUNT_NUMBER for the customer identifier.
  • MTL_SYSTEM_ITEMS_KFV — resolves CONCATENATED_SEGMENTS for the item within the organization.
  • WSH_PICKING_BATCHES — resolves the picking batch NAME for the batch id.

Lookups are additionally read from FND_LOOKUP_VALUES_VL and WSH_LOOKUPS for item display and sort-by meanings; the metadata lists these as lookup sources rather than base tables.

Usage Notes

The package is invoked exclusively as a supporting unit of the WSH open orders XML Publisher report. It is registered as the report's PL/SQL package on the concurrent program definition, and the report template calls BEFOREREPORT before execution and AFTERREPORT afterwards. It is not designed as a public API — no other packages reference it — so customisations should call the report or read the same tables directly rather than invoking these procedures. Because it is read-only and driven by concurrent request parameters, it is safe under standard multi-org access, provided the responsible organisation is set for the session.