Results for “get_site_use_location”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ARI_UTILITIES is a shared Oracle Receivables utility package owned by APPS and defined with AUTHID CURRENT_USER, meaning that its unqualified references resolve against the calling schema's privileges rather than the package owner. It is classified as an "OTHER" API in the ETRM metadata, reflecting that it is not a formal business-object API but rather a library of helper routines consumed internally by Oracle Receivables and its dependent modules in Oracle E-Business Suite 12.1.1 and 12.2.2. The package centralises functionality that would otherwise be duplicated across Receivables forms, concurrent programs, and dependent packages: currency rounding, lookup translation, customer and contact retrieval, site-use resolution, access-check logic, and notification dispatch.
The header comment in the source identifies build ARIUTILS.pls 120.18.12020000.3, dated 25 December 2012, which places the shipped 12.2.x version firmly in the late-2012 code line. The most recent documented functional addition to the package body — the curr_round_amt function — dates from December 2004, indicating that the core utility surface has been stable for many release cycles. Metadata records 41 documented procedures and functions and six dependent packages that reference it.
Key Procedures and Functions
- CHECK_EXTERNAL_USER_ACCESS — Determines whether an external (typically iReceivables or self-service) user is permitted to access a given combination of person party, customer, and customer site use.
- SEND_NOTIFICATION — Dispatches a workflow notification for a concurrent request, taking the user, customer, request identifiers, and the subject/body message names and applications as inputs. Defaults point to the AR application.
- CURR_ROUND_AMT — Rounds a numeric amount according to the precision defined for the supplied currency code. This is the canonical rounding helper for monetary values in Receivables logic.
- GET_LOOKUP_MEANING — Returns the meaning of a lookup code for a given lookup type, using a cached PL/SQL table (
pg_ar_lookups_rec) to avoid repeated queries. - GET_BILL_TO_SITE_USE_ID / GET_SITE_USES / SITE_USE_MEANING — Resolve a bill-to site use identifier from an address identifier, return the site uses associated with an address, and translate a site use code into its display meaning.
- CUST_SRCH_SEC_PREDICATE — Builds the security predicate used to constrain customer search results.
- CHECK_SITE_ACCESS and CHECK_ADMIN_ACCESS — Access-control helpers applied to site-level and administrative operations.
- GET_CONTACT_ID, GET_CONTACT, GET_PHONE — Retrieve contact identifiers, contact details, and telephone information for a party.
- GET_SERVICE_CHARGE_ACTIVITY_ID and IS_SERVICE_CHARGE_ENABLED — Determine the activity identifier for service charges and whether service charge functionality is active.
- GET_MAX_FUTURE_PAYMENT_DATE — Returns the furthest date to which a future-dated payment may be recorded.
- SAVE_PAYMENT_INSTRUMENT_INFO and IS_SAVE_PAYMENT_INSTR_ENABLED — Persist payment instrument information and indicate whether instrument saving is enabled.
- GET_DEFAULT_CURRENCY and IS_AGING_ENABLED — Report the default currency and whether aging functionality is active.
Tables Accessed
The package reads and writes Receivables, Trading Community, and Oracle Workflow data through APPS synonyms. Customer and party data comes from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUSTOMER_PROFILES, and HZ_CONTACT_POINTS (contacts and phone numbers). Site-use resolution draws on AR_IREC_USER_ACCT_SITES_ALL. Banking and payment instrument handling uses AP_BANK_ACCOUNTS and AR_BANK_DIRECTORY. Transaction and balance context comes from AR_PAYMENT_SCHEDULES, AR_PAYMENT_SCHEDULES_ALL, AR_TRX_BAL_SUMMARY, and AR_NOTES. AR_SYSTEM_PARAMETERS and FND_PROFILE_OPTION_VALUES supply system-level configuration such as aging and service-charge settings, while FND_FORM_FUNCTIONS supports access checks and WF_EVENT_T supports workflow notification activity.
Usage Notes
ARI_UTILITIES is not intended to be called directly by end users or by customer extensions seeking a supported public API; it is a plumbing layer invoked from Receivables forms, concurrent programs, iReceivables self-service flows, and the six dependent packages recorded in the metadata. Because the package is defined AUTHID CURRENT_USER, callers must possess the necessary privileges on the underlying HZ, AR, AP, FND, and WF objects — a common cause of runtime errors when the package is executed from a custom schema that lacks grants on the Receivables base tables. In 12.1.1 and 12.2.2 the online patching and editioning model means the package body is compiled into the APPS edition; custom code should always call it through the APPS synonym rather than referencing a specific edition schema. Where equivalent supported APIs exist — for example, the public AR and HZ APIs for customer or receipt operations — those should be preferred, and ARI_UTILITIES treated as internal implementation subject to change without notice between patches.
-
PACKAGE: APPS.ARI_UTILITIES 12.1.1
-
PACKAGE: APPS.CS_STD 12.2.2
-
PACKAGE BODY: APPS.CS_STD 12.1.1
-
PACKAGE: APPS.CS_STD 12.1.1
-
PACKAGE: APPS.ARI_UTILITIES 12.2.2
-
PACKAGE BODY: APPS.CS_STD 12.2.2
-
PACKAGE: APPS.CS_STD 12.1.1
-
PACKAGE: APPS.CS_STD 12.2.2
-
PACKAGE: APPS.ARI_UTILITIES 12.1.1
-
PACKAGE BODY: APPS.CS_STD 12.1.1
-
PACKAGE: APPS.ARI_UTILITIES 12.2.2
-
PACKAGE BODY: APPS.CS_STD 12.2.2