Search Results default_country_code

Overview

ARH_ARXCUDCI_PKG is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name follows the ARH module prefix convention associated with Oracle Receivables customer and address entry functionality. The package provides the initialization logic required by the Customer Update or Customer Interface form when it is first opened. Specifically, it centralizes the assembly of session defaults, system parameters, and profile option values that the form requires before the user can work with customer records. By encapsulating this logic in a single procedure rather than embedding it in form-level triggers, Oracle preserves a consistent initialization contract between the form and the database, and permits the same defaults to be reused by any calling layer that requires the same set of values. The ETRM classification records this package as an OTHER API object, meaning it is not a public, supported programmatic interface in the sense of an open API, but rather an internal utility package invoked by the E-Business Suite forms runtime. As such, it is documented for reference and impact analysis rather than for direct customer invocation.

Key Procedures and Functions

The package body exposes one documented procedure, INITIALIZE. Its purpose is to populate all of the default values and system options that the calling form needs in a single round trip. The procedure contains a substantial OUT parameter list (customer_type, tax_printing_option, grouping_rule, create_reciprocal, auto_cust_numbering, auto_site_numbering, profile_class, change_cust_name, use_customer_keys_flag, so_organization_id, address_validation, location_structure_id, from_postal_code, to_postal_code, home_country_code, default_country_code, default_country_disp, address_style, and functional_currency), and it writes into each of these variables as its execution progresses.

Internally, the procedure couples simple lookups with system parameter reads and a currency query. Examples visible in the source include retrieving the CUSTOMER_TYPE lookup value, reading the tax invoice printing option from the AR system parameters record, resolving the default grouping rule name from RA_GROUPING_RULES using the configured grouping rule identifier and current date, and selecting the functional currency code from the set of books. The default_country_code output, which is the term most commonly searched for in connection with this package, is one of the address-related defaults the procedure returns so that the form can pre-populate country information on new address records.

Tables Accessed

ETRM documents three tables referenced through APPS synonyms. AR_SYSTEM_PARAMETERS supplies the Receivables system option values, including tax invoice printing and the default grouping rule identifier used to resolve a grouping rule name. RA_GROUPING_RULES is queried to translate that grouping rule identifier into the human-readable rule name, with date-range filtering to select the currently effective rule. HZ_CUST_PROFILE_CLASSES supplies customer profile class information used for the profile class default. Additional lookups originate from the ARP_STANDARD package hierarchy, which in turn reads AR_LOOKUPS and GL_SETS_OF_BOOKS; the functional currency is selected directly from GL_SETS_OF_BOOKS.

Usage Notes

INITIALIZE is intended to be called once during form initialization, typically from a WHEN-NEW-FORM-INSTANCE trigger or an equivalent pre-query point in the Oracle Forms-based customer maintenance and customer interface screens. It is not referenced by any other documented package, which confirms its role as a leaf utility used only by the user interface layer. The procedure relies on the ARP_STANDARD package for several of its values, so callers must ensure that the Receivables system parameters record exists and that ARP_STANDARD initialization has completed. Because the parameter list is implemented as IN OUT NOCOPY, callers should supply pre-declared variables of the correct types. Release 12.1.1 and 12.2.2 share this implementation; the $Header value indicates the last functional change predates both releases, so behavior is stable across the two versions. Customizations should avoid calling this procedure directly and instead read the underlying system parameters, as Oracle may revise internal initialization logic without notice.