Search Results p_deliver_to_org_id

Overview

The APPS.JG_GLOBE_UTIL_PKG package body is a globalization utility within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 codebase. It functions as a country-specific dispatch layer that evaluates the operating product for a given organization and, when that product resolves to the localized "JL" (Latin America / global localization) application, delegates processing to the corresponding JL_GLOBE_UTIL_PKG hook. The package version corresponds to header jggutilb.pls 120.4, last modified in November 2010, and is classified under the APPS schema as an OTHER API type. Its primary purpose is to bridge generic EBS ordering flows (iProcurement/ICX and Purchasing/PO) with localization logic that derives a transaction reason code required for statutory reporting and global compliance.

Key Procedures and Functions

The ETRM metadata documents three public program units, each referenced by the supplied source excerpt.

• PROCESS_ICX_LINE_GLOBE_EVENT — A function that processes Globe events originating from the ICX (iProcurement) flow. It accepts organization, item, and delivery destination context (the latter identified by the p_deliver_to_org_id parameter the user searched for) and returns a transaction reason code as a VARCHAR2. It first determines the product for the organization; if the product is "JL", it calls the JL hook (jl_globe_util_pkg.populate_icx_trx_reason_code) to populate the reason code. Otherwise it returns null. An exception handler returns null and logs the SQL error code and message via DEBUG.
• PROCESS_PO_GLOBE_EVENT — A procedure that processes Globe events originating from the Purchasing flow. It accepts a document type, level type, and level ID, resolves the owning organization from the referenced PO line, and, where the product is "JL" and the document type is STANDARD or BLANKET at the LINE level, derives the transaction reason code.
• DEBUG — A diagnostic helper used throughout the package to emit trace information, including parameter values and error details, supporting troubleshooting of the globalization dispatch logic.

Tables Accessed

Two tables are documented as accessed through APPS synonyms:

• PO_LINES_ALL — Read to resolve the org_id associated with a purchasing document line, which in turn determines the operating product and whether JL localization processing is required.
• DUAL — Used as the select source for invoking the JL hook function, allowing the returned transaction reason code to be captured into a local variable.

Usage Notes

JG_GLOBE_UTIL_PKG is invoked indirectly by standard EBS business flows rather than being called by users directly. The ICX path is normally triggered from iProcurement checkout and requisition processing, where the delivery organization context (p_deliver_to_org_id) is significant for determining the applicable localization rules. The PO path is triggered during purchasing document entry and processing for STANDARD and BLANKET agreements at the line level. The package is not referenced by any other documented packages, indicating it sits at the boundary between the base applications and the JL localization layer. Customers extending or diagnosing these flows should note that failures inside the JL hook are swallowed by the WHEN OTHERS handler and surfaced only through the DEBUG output, so diagnostic tracing must be enabled when investigating unexpected null reason codes. Debug statements such as those confirming the passed p_deliver_to_org_id value are the primary means of verifying the correct destination organization is being routed into the localization logic.