Search Results is_gdf_postbatch_valid

Overview

AR_GDF_VALIDATION is an Oracle E-Business Suite package body owned by the APPS schema that provides validation services for Global Descriptive Flexfields (GDF) during the AutoInvoice process. AutoInvoice is the principal interface through which external feeder systems load invoice, credit memo, and debit memo data into Oracle Receivables. Because AutoInvoice supports global descriptive flexfields — the flexfield structures that are only relevant when Oracle Financials for certain localizations (notably JG, the India localization) are installed — the validation logic associated with those flexfields must be isolated from the base Receivables code. AR_GDF_VALIDATION serves that isolation role.

As documented in the package header, the actual global descriptive flexfield validation package, JG_ZZ_AUTO_INVOICE, is installed only when JG is installed. AR_GDF_VALIDATION therefore operates as a stub or wrapper module: it checks whether the localization-specific validation package exists and delegates to it, or returns a success indicator when no localization-specific validation applies. This design allows AutoInvoice to call a single, stable entry point regardless of which localizations are present in the instance. The API is classified as OTHER, reflecting that it is primarily an internal dependency invoked by AutoInvoice and related processing rather than a public integration API.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• IS_GDF_VALID — The primary validation entry point for global descriptive flexfields during an AutoInvoice run. It accepts a request identifier and returns 1 when validation succeeds and 0 when an error occurs. The header documentation states it is a stub that delegates to the JG_ZZ_AUTO_INVOICE package when available.
• IS_GDF_POSTBATCH_VALID — Performs global descriptive flexfield validation in the post-batch phase, after the main AutoInvoice batch has been processed, ensuring GDF data is consistent before final completion.
• IS_GDF_TAXID_VALID — Validates global descriptive flexfield values relating to tax identifiers, complementing the standard Receivables tax validation steps.
• IS_CUST_IMP_VALID — Supports validation in the customer import context, applying the same GDF rules to imported customer data.
• COPY_GDF_ATTRIBUTES — Copies global descriptive flexfield attribute values, typically used to propagate GDF data between interface and base tables during processing.
• INSERT_GLOBAL_TABLE — Inserts rows into the relevant global flexfield structure, supporting persistence of validated GDF values.
• IS_JG_INSTALLED — Determines whether the JG localization is installed, effectively the gate that decides whether localization-specific validation can be invoked.

Tables Accessed

The documented referenced objects, accessed through APPS synonyms, include:

• AR_SYSTEM_PARAMETERS — Read to derive Receivables system-level settings. The package body initializes a global variable from ARP_GLOBAL.SYSPARAM.ORG_ID, which is populated from this table, so that the correct operating unit context is available to the validation logic.
• ALL_SOURCE — Queried to detect the presence of localization packages such as JG_ZZ_AUTO_INVOICE, which underpins the IS_JG_INSTALLED check and the stub-to-implementation delegation pattern.
• DBMS_SQL — The dynamic SQL built-in package, used for constructing and executing validation statements dynamically, consistent with the SQLSTMT variable and cursor handle declared in the package body.

Usage Notes

AR_GDF_VALIDATION is invoked automatically by the AutoInvoice concurrent program and its dependent processing when global descriptive flexfields are present. It is not intended as a standalone user-facing API. The package logs debug information through ARP_STANDARD.ENABLE_DEBUG and ARP_STANDARD.DEBUG when the AFLOG_ENABLED profile option is set to Y or C, which is useful when diagnosing AutoInvoice GDF failures. Because three other packages reference it, customization should be avoided; instead, extensions should target the localization implementation package. Calling AR_GDF_VALIDATION.IS_GDF_VALID with a valid AutoInvoice request identifier returns 1 on success and 0 on failure, and remains the documented pattern for programmatic checks.