Search Results get_create_reciprocal_flag

Overview

HZ_MO_GLOBAL_CACHE is an Oracle EBS Release 12 (12.1.1 and 12.2.2) PL/SQL package owned by the APPS schema and defined with AUTHID CURRENT_USER. It belongs to the Oracle Receivables and Trading Community (HZ) modules, providing a centralized, in-memory caching layer for organization-level and system-level setup attributes. The package exposes a collection of strongly typed PL/SQL tables and record types—including OrgIDTable, AutoSiteNumberingTable, DefaultCountryTable, SetOfBooksIDTable, ChartOfAccountsIDTable, LocationStructureIDTable, TaxMethodTable, AddressValTable, and ReciprocalFlagTable—plus composite record types such as GlobalsRecord and GlobalsTable, whose fields mirror the columns of AR_SYSTEM_PARAMETERS_ALL and GL_SETS_OF_BOOKS.

Its core purpose is to reduce repetitive, high-cost queries against AR_SYSTEM_PARAMETERS_ALL, HR_ORGANIZATION_INFORMATION, and GL_SETS_OF_BOOKS by materializing frequently accessed configuration values into memory for the duration of a session. Business functions served include customer and site number generation, tax configuration, address validation, location structure determination, chart of accounts and set of books resolution, and reciprocal customer handling.

The API classification is OTHER, and the package is referenced by eight other packages in the E-Business Suite, confirming its role as shared infrastructure for forms, concurrent programs, and other PL/SQL APIs within the Order-to-Cash and Trading Community processes.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. RETRIEVE_GLOBALS is the master loader that populates the internal global cache collections from AR_SYSTEM_PARAMETERS_ALL and GL_SETS_OF_BOOKS in a single read.

• GET_ORG_ATTRIBUTES — returns organization-level attributes for the requested organization.
• GET_AUTO_SITE_NUMBERING — retrieves the auto site numbering setting from system parameters.
• GET_DEFAULT_COUNTRY — returns the default country defined in Receivables system parameters.
• GET_LOCATION_STRUCTURE_ID — supplies the location structure identifier used for address derivation.
• GET_TAX_METHOD — returns the configured tax method.
• GET_CHART_OF_ACCOUNTS_ID — resolves the chart of accounts identifier for a set of books.
• GET_SET_OF_BOOKS_ID — returns the associated set of books identifier.
• GET_GENERATE_CUSTOMER_NUMBER — returns the system parameter controlling whether customer numbers are generated automatically; the user's search term "get_generate_customer_number" maps directly to this function.
• GET_ADDRESS_VALIDATION — returns the address validation setting.
• VALIDATE_ORGID_PUB_API — public API wrapper that validates an organization identifier.
• GET_CREATE_RECIPROCAL_FLAG — returns the reciprocal customer creation flag (added via Bug 5002547).
• GET_AUTOCASH_HIERARCHY_ID — returns the AutoCash hierarchy identifier.
• GET_DEFAULT_GROUPING_RULE_ID — returns the default grouping rule identifier.

Tables Accessed

The package reads AR_SYSTEM_PARAMETERS_ALL and AR_SYSTEM_PARAMETERS for Receivables system parameters including auto site numbering, default country, location structure, tax method, address validation, and reciprocal flag. HR_ORGANIZATION_INFORMATION supplies organization identifiers used to build the OrgIDTable collection. GL_SETS_OF_BOOKS provides set of books and chart of accounts identifiers. PLITBLM is referenced for PL/SQL table processing utilities. All access is performed through APPS synonyms. The package is primarily read-only, serving as a caching reader rather than a data-maintenance interface.

Usage Notes

HZ_MO_GLOBAL_CACHE is typically invoked implicitly by Receivables and Trading Community forms, concurrent programs, and dependent PL/SQL APIs that require repeated access to organization and system parameters. Callers generally invoke RETRIEVE_GLOBALS once at the start of a session to prime the global cache, then call the individual GET_* functions to retrieve specific values without repeated table access. In custom development, the package should be treated as a performance-oriented buffer; direct calls are appropriate when the same setup attributes are needed many times within a single logical transaction or processing loop.