Search Results jg_zz_invoice_create




Overview
Explore in AI Chat

Overview

JG_ZZ_INVOICE_CREATE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, operating with AUTHID CURRENT_USER privileges. It is classified under the "OTHER" API category, indicating that it is not a standard public-interface API but rather an internal or country-specific utility package. The package name prefix "JG" associates it with Oracle's globalization and regional localization modules, which in EBS are responsible for country-specific legal, fiscal, and regulatory requirements. The source header, dated 2004, indicates that the package originated in the 11i generation of the product and has been carried forward into Release 12.1.1 and 12.2.2 as part of the localization infrastructure.

The package supports the creation and validation of invoice-related transactions within a country-specific (globalization) flow. Its principal responsibilities are to register error messages against specific transaction headers and lines, and to validate a descriptive flexfield (DFF) associated with a concurrent request. As an "OTHER"-classified package, it is not intended for direct customer invocation but is instead called by other localization components.

Key Procedures and Functions

  • PUT_ERROR_MESSAGE (overload 1) — Accepts a header identifier, a line identifier, a message text, and an invalid value, and returns a BOOLEAN. This overload records a free-form error message against a specific invoice header and line, capturing the offending value for diagnostic or user-display purposes.
  • PUT_ERROR_MESSAGE (overload 2) — Accepts an application short name, a message name, a header identifier, a line identifier, and an invalid value, and returns a BOOLEAN. This overload resolves a predefined Oracle Application Object Library message by application and message name, then logs it against the specified header and line. It is the standard mechanism for surfacing seeded, translatable messages rather than hard-coded text.
  • VALIDATE_GDFF — Accepts a concurrent request identifier and returns a NUMBER. It validates the global descriptive flexfield data associated with the given request, returning a status code that the calling program interprets to determine whether processing should proceed.

All three routines are declared in the package specification, making them callable by other database objects. No parameter lists beyond those declared are assumed or inferred here.

Tables Accessed

The only documented table referenced by this package, via an APPS synonym, is AR_TRX_ERRORS_GT. This is a global temporary table used by Receivables transaction-processing flows to stage error records. The PUT_ERROR_MESSAGE overloads write error entries into this structure, associating each message with a transaction header and line. The presence of this table confirms that the package participates in the Receivables invoice/transaction pipeline, using the temporary table as a transient repository for validation failures that are consumed later in the same session or concurrent request.

Usage Notes

JG_ZZ_INVOICE_CREATE is referenced by two other packages within the EBS codebase, confirming its role as a shared localization utility rather than a standalone entry point. It is typically invoked from within country-specific invoice creation or validation programs, including concurrent programs that process transaction batches and need to accumulate errors before reporting. The header identifier and line identifier parameters passed to PUT_ERROR_MESSAGE allow granular error attribution, which is useful when a single batch contains many invoices or lines.

Because the package is AUTHID CURRENT_USER, privilege resolution occurs against the calling schema rather than APPS, meaning callers must themselves have the necessary grants on AR_TRX_ERRORS_GT and any referenced message dictionaries. Customizations should not modify the package directly; instead, developers should invoke the documented overloads and interpret the BOOLEAN/NUMBER return values. When investigating a user search for "put_error_message," the relevant entry point is the PUT_ERROR_MESSAGE function pair, which is the package's public error-logging interface.