Results for “process_deliveries”

28 results




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

Overview

JAI_OM_WSH_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM metadata as an "OTHER" API type. It belongs to the Oracle Financials for India (JAI) product family and, more specifically, to the excise and tax reporting subsystem operating within the Order Management (OM) and Shipping (WSH) execution flows. The package name combines the JAI prefix (India Localization), OM (Order Management), and WSH (Warehouse Management/Shipping) identifiers, reflecting its role at the intersection of delivery processing and Indian excise duty computation.

The core business function of the package is to process shipping deliveries and determine the appropriate excise register treatment for goods being moved out of the organization. In the Indian localization context, every outbound delivery must be evaluated against statutory excise registers — RG23A, RG23C, RG23D, and PLA — to ascertain whether duty has been paid, whether balances are sufficient, and whether the transaction qualifies as exempt, export-oriented, or otherwise privileged. The package encapsulates this evaluation logic and drives the resulting financial and statutory postings.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, which is a relevant consideration for security and synonym resolution in a multi-organization environment.

Key Procedures and Functions

The package exposes three documented program units.

  • PROCESS_DELIVERY — Processes a single delivery. It accepts a delivery identifier and returns the standard concurrent program OUT parameters (errbuf and retcode), making it suitable for both direct invocation and concurrent program registration. This procedure performs the excise determination and posting logic for one delivery at a time.
  • PROCESS_DELIVERIES — Processes deliveries in a batch context. It mirrors the signature of PROCESS_DELIVERY, accepting errbuf, retcode, and a delivery identifier parameter. Given its plural name and the presence of the concurrent program OUT parameters, this procedure is designed for set-based or concurrent processing of deliveries.
  • GET_EXCISE_REGISTER_WITH_BAL — A function returning VARCHAR2 that resolves the applicable excise register and its available balance for a given delivery context. Its extensive parameter list covers preferred register selections (RG23A, RG23C, PLA), SSI unit flag, exempt amount, the various register and PLA balances (basic, additional, and other), excise duty amounts by category, export-oriented unit indicator, register code, delivery, organization, and location identifiers, and cess amounts including special/higher cess. It returns a process flag and process message through OUT parameters, allowing the caller to determine whether the delivery is eligible for processing against the identified register.

Tables Accessed

The package reads and writes an extensive set of India-localization and standard EBS tables, accessed through APPS synonyms.

Usage Notes

JAI_OM_WSH_PKG is typically invoked from the Oracle Shipping Execution delivery confirmation flow and from India-localization concurrent programs that process pending deliveries. The presence of errbuf and retcode OUT parameters in PROCESS_DELIVERY and PROCESS_DELIVERIES indicates these procedures are registered as concurrent program executables, either directly or through a wrapper. The package is also referenced by two other packages in the ETRM repository, suggesting it serves as a callable utility for excise-aware delivery processing elsewhere in the localization stack.

Implementation considerations include the AUTHID CURRENT_USER declaration, which requires that calling sessions possess the necessary object privileges, and the dependency on a valid financial year and organization registration in JAI_CMN_INVENTORY_ORGS before processing can succeed. Custom code should invoke the procedures within the standard concurrent manager framework to ensure GL_INTERFACE rows are picked up by the appropriate journal import program. The header comment indicates the package was last modified in 2007, so behavior should be validated against the current 12.1.1 or 12.2.2 patch level of the India Localization module.