Search Results ar_cust_interface

Overview

JG_GLOBE_FLEX_VAL is an Oracle E-Business Suite PL/SQL package owned by APPS and classified as an "OTHER" API within the ETRM repository. Its name reflects its core purpose: it is the server-side validation engine for Global Descriptive Flexfields (GDF), the mechanism by which Oracle EBS captures country-specific, localization-driven attributes on business documents such as payables invoices, receivables transactions, and customer records. The package validates that values assigned to global attribute segments comply with the flexfield definitions, value sets, and context integrity rules configured in the FND descriptive flexfield framework. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the APPS schema, and its header revision (120.7.12020000.1, dated June 2012) places it within the 12.1.1 and 12.2.2 code lines documented by ETRM.

The package is organized around the dual Globalization (JG) flows that Oracle supports: the Payables (AP) side and the Receivables (AR) side. It provides both single-attribute validation and broader record-level integrity checks for context combinations, and it is referenced by five other packages, indicating it functions as a shared validation utility rather than an entry-point API.

Key Procedures and Functions

The thirteen documented entry points group into several functional clusters.

• GDF_CONTEXT_EXISTS — The routine associated with the user's search term. It determines whether a given global descriptive flexfield context code is valid or already present for the entity under evaluation, serving as the gate that other validation logic depends on.
• CHECK_ATTR_VALUE — The generic attribute-level validator that tests a supplied global attribute value against its configured value set.
• CHECK_ATTR_VALUE_AP and CHECK_ATTR_VALUE_AR — Payables- and Receivables-specific variants of attribute validation, applying the business rules appropriate to each application.
• CHECK_AP_CONTEXT_INTEGRITY and CHECK_AR_CONTEXT_INTEGRITY — Validate that a context code and its dependent global attributes are mutually consistent, rejecting incomplete or contradictory context structures.
• CHECK_AP_BUSINESS_RULES and CHECK_AR_BUSINESS_RULES — Apply application-level business constraints beyond simple value set membership, enforcing cross-attribute and contextual rules on the AP and AR sides respectively.
• REJECT_VALUE_FOUND — Reports or handles the condition in which a value fails validation and must be rejected, supporting error reporting back to the caller.
• REASSIGN_CONTEXT_CODE — Repositions or reassigns the context code on a record, typically during correction or migration processing.
• AR_CUST_INTERFACE — Supports validation of global flexfield data on the customer interface path.
• INSERT_JG_ZZ_INVOICE_INFO and INSERT_GLOBAL_TABLES — Persistence routines that write validated globalization and invoice-related information into the JG shadow tables used by the localization flows.

Tables Accessed

Through APPS synonyms the package reads and writes a tightly scoped set of tables. FND_DESCR_FLEX_CONTEXTS supplies the descriptive flexfield context definitions against which existence and integrity checks are performed. AP_INVOICE_DISTRIBUTIONS_ALL and the receivables interface tables RA_CUSTOMERS_INTERFACE and RA_CUSTOMER_PROFILES_INTERFACE provide the transactional and interface rows whose global attributes are being validated. AR_SYSTEM_PARAMETERS supplies receivables configuration influencing the AR-side rules. FND_CONCURRENT_REQUESTS is used where validation runs under concurrent program control. PLITBLM is the standard PL/SQL index-by table used by Oracle's table-handling utilities for set-based operations.

Usage Notes

JG_GLOBE_FLEX_VAL is not typically invoked directly by end users. It is called from globalization-enabled forms during record entry and save, from the Payables and Receivables interface/concurrent programs when importing data that carries global attributes, and from customizations that must enforce the same GDF validation contract as the standard product. The presence of the AR_CUST_INTERFACE and INSERT_GLOBAL_TABLES routines confirms that the customer interface concurrent programs are a principal caller. Because it is referenced by five other packages, implementers extending GDF behavior should call these documented routines rather than reimplementing context and attribute validation, ensuring that localization rules remain consistent across the AP, AR, and customer data flows in both 12.1.1 and 12.2.2.