Search Results verify_customer_site_access




Overview
Explore in AI Chat

Overview

ARI_SELF_REG_CONFIG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM object taxonomy as an "OTHER" API rather than a standard public interface. Its name and its procedural surface indicate that it acts as a configuration and validation helper for the Oracle iStore / Oracle Trade Management self-registration flow, where anonymous or unauthenticated users create their own customer accounts and site usages without intervention from an order-entry clerk. Within that flow the package supplies the decision logic that determines whether a prospective registrant is permitted to reach a given customer, account, or site, and it supplies identifiers and password-generation policy that the registration screens require in order to complete a self-service signup.

The package is tightly coupled to APPS.ARI_SELF_REGISTRATION_PKG. The ETRM dependency report shows a bidirectional relationship: ARI_SELF_REG_CONFIG references ARI_SELF_REGISTRATION_PKG, and ARI_SELF_REGISTRATION_PKG in turn references ARI_SELF_REG_CONFIG, alongside a self-reference from ARI_SELF_REG_CONFIG to itself. Both packages stand on the SYS.STANDARD package. The object is reported with a status of VALID, meaning it is compiled and present in the dictionary, and it is referenced by one other package in addition to the registration package.

Key Procedures and Functions

ETRM documents six callable units in ARI_SELF_REG_CONFIG. Their names describe an access-control and identifier-resolution role:

  • VERIFY_CUSTOMER_SITE_ACCESS — confirms whether a registrant is entitled to operate against a particular customer site, forming the primary gate for site-level self-registration.
  • VALIDATE_CUST_DETAIL_ACCESS — validates access at the more granular customer-detail level, typically invoked before exposing account specifics to the self-service user.
  • GET_CUSTOMER_ID — returns the customer identifier associated with the registration context, supplying the key used by downstream registration and profile logic.
  • AUTO_GENERATE_PASSWD_OPTION — determines or exposes the policy setting for automatic password generation during registration, allowing the site to decide whether users choose or are assigned credentials.
  • VALIDATE_ACCESS — a general access-validation entry point used where a specific site or detail check is not required.
  • GET_CUSTOMER_ID_NUMBER — returns the customer number (the human-readable account identifier) rather than the internal primary key.

Parameter lists are not published in the ETRM excerpt and should be confirmed against the package specification in the target instance.

Tables Accessed

The package reaches eight base tables through APPS synonyms, spanning Receivables and the Trading Community Architecture:

Usage Notes

ARI_SELF_REG_CONFIG is not intended for direct invocation by end users. It is called programmatically by ARI_SELF_REGISTRATION_PKG, which drives the registration screens and concurrent processing that accept new self-service customers. Customizations should avoid modifying the package body; instead, wrap or extend behavior through the documented registration package. Because the object is an "OTHER" classification rather than a supported public API, Oracle does not guarantee signature stability across releases, so any custom code depending on these procedures must be re-validated during upgrades from 12.1.1 to 12.2.2. Note that self-registration functionality is enabled per site and controlled by profile options; if those options are disabled, the validation routines may never be exercised, which is a useful first check when troubleshooting. The self-referencing dependency suggests internal recursion or shared private helpers, so debugging should start from the registration package's entry points rather than from this package in isolation.