Search Results validate_orgid_pub_api

Overview

HZ_MO_GLOBAL_CACHE is a TCA (Trading Community Architecture) package body owned by APPS and classified as an "OTHER" API in ETRM. Its principal business function is to cache operating unit (ORG_ID) level attributes that govern customer and address processing so that repeated lookups against system parameter and organization tables are eliminated at runtime. As the name implies, it is a global, session-scoped cache rather than a transactional API. The package retrieves operating unit attributes from the database through its private populate procedure and stores them in a package-level associative array (G_Cache) indexed by ORG_ID, keyed to the record structure GlobalsRecord. A second global, G_Cust_Gen_Cache, holds customer number generation metadata. The body carries a 2006 header revision (ARHMOGCB.pls 120.8) and was originally created in May 2005 by Rajib Ranjan Borah as part of the TCA SSA Uptake (Bug 3456489). It exposes fourteen documented procedures and functions and is referenced by eight other packages, confirming its role as shared infrastructure used broadly across TCA customer, site, and address validation flows.

Key Procedures and Functions

The documented interface centers on a single private populator and a family of public getter routines. In Oracle EBS terms, these functions return cached operating-unit settings without forcing a re-query of the underlying parameter tables.

• RETRIEVE_GLOBALS — Private helper invoked by populate; reads the complete set of operating unit attributes from the database into a batch (table) structure for bulk loading into the cache.
• GET_ORG_ATTRIBUTES — Returns the consolidated attribute set for a given operating unit.
• GET_AUTO_SITE_NUMBERING — Returns whether automatic site numbering is enabled for the operating unit.
• GET_DEFAULT_COUNTRY — Returns the default country configured for the operating unit.
• GET_LOCATION_STRUCTURE_ID — Returns the location structure identifier used for address/location validation.
• GET_TAX_METHOD — Returns the tax method configured for the operating unit.
• GET_CHART_OF_ACCOUNTS_ID — Returns the chart of accounts identifier associated with the operating unit.
• GET_SET_OF_BOOKS_ID — Returns the set of books identifier for the operating unit.
• GET_GENERATE_CUSTOMER_NUMBER — Returns the customer number generation setting, backed by G_Cust_Gen_Cache.
• GET_ADDRESS_VALIDATION — Returns the address validation level/flag for the operating unit.
• VALIDATE_ORGID_PUB_API — Public validation entry point; verifies that a supplied ORG_ID is valid and resolvable, using the module constant MOD_validate_orgid_pub_api for logging.
• GET_CREATE_RECIPROCAL_FLAG — Returns the reciprocal customer creation flag.
• GET_AUTOCASH_HIERARCHY_ID — Returns the aut cash hierarchy identifier.
• GET_DEFAULT_GROUPING_RULE_ID — Returns the default grouping rule identifier used in customer/account grouping.

Tables Accessed

The cache is populated from a small, focused set of tables accessed through APPS synonyms:

• AR_SYSTEM_PARAMETERS_ALL and AR_SYSTEM_PARAMETERS — Source of operating unit level Receivables/TCA settings such as auto site numbering, default country, tax method, address validation, chart of accounts, and set of books.
• HR_ORGANIZATION_INFORMATION — Provides organization classification/attribute data used to confirm and enrich operating unit attributes.
• PLITBLM — The PL/SQL table-to-array utility used to marshal the bulk retrieved rows into PL/SQL collections during population.

These tables are read-only from the perspective of this package; it writes only to its in-memory cache structures.

Usage Notes

HZ_MO_GLOBAL_CACHE is invoked indirectly rather than through a dedicated form or concurrent program. It is referenced by eight other packages, which call its getters (and VALIDATE_ORGID_PUB_API) to obtain operating-unit context before performing customer, site, or address processing. Typical callers include TCA customer and site APIs and address validation routines. Because the cache is populated lazily via populate and reset with G_Cache.DELETE, callers should not assume the cache is pre-loaded at session start. In custom code, invoking the getters is preferred over direct queries against AR_SYSTEM_PARAMETERS_ALL, since the cache reflects parameters loaded during the session and reduces redundant database round trips. The VALIDATE_ORGID_PUB_API routine is the appropriate public entry point when a custom program must confirm that a user-supplied or interface-supplied ORG_ID is valid before proceeding; its logging constant supports trace diagnostics.