Search Results cp_p_to_creation_date_p

Overview

WSH_WSHRDOPN_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Shipping Execution "Open Shipments" report, internally identified as WSHRDOPN. Reports in EBS 12.1.1 and 12.2.2 are frequently implemented as Oracle Reports (XML Publisher) executables whose PL/SQL logic resides in a companion XMLP_PKG package. This package holds the report's user-entered parameters, derived ("CP_") formula columns, and report-level trigger functions that control data selection and formatting when the concurrent program is run. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking session rather than the definer, and the embedded header ($Header: WSHRDOPNS.pls 120.3 2010/08/17) confirms it is a standard shipped file, version 120.3, last revised in 2010. The package is documentation-classified as OTHER, indicating it is not a published public API but an internal report support package.

Key Procedures and Functions

The package exposes two broad categories of callable units. The first group comprises Oracle Reports trigger functions: BEFOREREPORT, BEFOREPFORM, AFTERPFORM, and AFTERREPORT. These fire at the standard report lifecycle points, allowing the package to initialize state, build dynamic WHERE and ORDER BY fragments prior to the query, and perform cleanup after output is produced. Two formatting formula functions are also documented: CF_SHIPMENT_PRIORITYFORMULA, which derives the shipment priority display value from the SHIPPRI input, and CF_LPNFORMULA, which derives the licence plate number (LPN) display flag from CONTAINER_FLAG. Together these govern conditional presentation of shipping attributes on the report layout.

The second group consists of the CP_ (computed parameter) accessor functions: CP_WAREHOUSE_NAME_P, CP_WHSE_LONGNAME_P, CP_P_SHIPTO_LOCATION_P, CP_P_CUSTOMER_P, CP_TEMP_P, CP_P_SHIP_METHOD_P, CP_P_ITEM_NO_P, CP_P_BATCH_NO_P, CP_P_FROM_CREATION_DATE_P, CP_P_TO_CREATION_DATE_P, CP_P_ITEM_DISPLAY_P, and CP_P_SORT_ORDER_P. These return the corresponding package-level variables (for example, CP_TEMP_P returns CP_TEMP). The user search term "cp_temp_p" corresponds directly to the CP_TEMP_P function, which surfaces the CP_TEMP VARCHAR2(4000) variable used as a general-purpose scratch/output buffer in the report logic. All accessors are parameterless, returning VARCHAR2 or DATE values to the report template.

Tables Accessed

The documented APPS synonyms read by this package are: HR_ALL_ORGANIZATION_UNITS, used to validate and resolve the operating unit and warehouse organization identifiers; HZ_CUST_ACCOUNTS, used to resolve the ship-to customer account; MTL_PARAMETERS, which supplies inventory organization defaults such as the warehouse short and long names; MTL_SYSTEM_ITEMS_KFV, the key flexfield view providing the concatenated item number and description for the item display parameter; and WSH_PICKING_BATCHES, the shipping execution picking batch table that supplies the batch number filter. These tables align with the report's selection criteria: organization, customer, ship method, item, batch, and creation-date range.

Usage Notes

WSH_WSHRDOPN_XMLP_PKG is invoked exclusively in the context of the Open Shipments concurrent program and its associated Oracle Reports/XML Publisher definition; it is not a callable business API and is referenced by zero other packages. Because the package maintains session-level state in its package variables (P_ORGANIZATION_ID, P_CUSTOMER_ID, P_SORT_BY, and related CP_ values), correct invocation requires that the report's parameter form populate these variables before the main query executes, a sequence enforced by the BEFOREPFORM/AFTERPFORM triggers. The F_WHERE, F_SORT_SELECT, and F_SORT_ORDER variables demonstrate that the package constructs dynamic SQL fragments at runtime rather than relying solely on static query text. Customizations should avoid modifying this shipped package directly; Oracle patches (as evidenced by the version history) may overwrite it. Customer extensions are better placed in the report definition or in separate custom packages. Support diagnostics typically inspect the CP_ accessors, particularly CP_TEMP_P, to confirm that runtime parameters were correctly derived.