Results for “fnd_registrations_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPLSYS.FND_REGISTRATIONS is a core Oracle E-Business Suite table that underpins the User Management Framework (UMF) across both release 12.1.1 and 12.2.2. It stores the common attributes of user registration records — self-service sign-ups, workflow-driven invitations, and prospective-user onboarding — and acts as the driving table for UMF processing. The object resides in the APPLSYS schema with FND design data sourced from FND.FND_REGISTRATIONS, carries a status of VALID, and is physically stored in the APPS_TS_ARCHIVE tablespace with a PCTFREE of 10.

The table is deliberately designed to hold only commonly used columns. Registration data for which no column exists in FND_REGISTRATIONS is stored in the companion table FND_REGISTRATION_DETAILS. From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification: the table hangs off HZ_PARTIES and FND_APPLICATIONS rather than acting as a pure hub or link, so it is best treated as an attribute-bearing satellite in any analytical or integration model.

A practical DBA note accompanies the object: where many sparse invitations are expected, performance may be improved by increasing the percentage of free space, since the default allocation may be inadequate for that use case.

Key Information Stored

FND_REGISTRATIONS exposes 44 documented columns. The most operationally significant are:

• REGISTRATION_ID (NUMBER(15)) — synthetic surrogate primary key, unique and indexed.
• REGISTRATION_KEY (VARCHAR2(100)) — the encrypted representation of the registration ID, used in externally visible links and notifications.
• APPLICATION_ID (NUMBER(15)) — FK to FND_APPLICATIONS, striping the data by the registering application; also part of the FK to FND_REGISTRATION_TYPES.
• REGISTRATION_TYPE (VARCHAR2(255)) — combined with APPLICATION_ID, forms the FK to FND_REGISTRATION_TYPES, permitting multiple registration types per application.
• PARTY_ID (NUMBER(15)) — FK to HZ_PARTIES, tying the registration to a trading community party record.
• REQUESTED_USER_NAME and ASSIGNED_USER_NAME (VARCHAR2(100)) — the prospective username (uppercased on insert) and the username actually used once approved; the latter relates to FND_USER.
• REGISTRATION_STATUS — controls lifecycle state and is the basis of the function-based unique index.
• EXISTS_IN_FND_USER_FLAG — indicates whether an FND_USER account already exists.
• EMAIL and EMAIL_CONTACT_POINT_ID — registration contact channels.
• FIRST_NAME, MIDDLE_NAME, LAST_NAME, USER_TITLE, USER_SUFFIX — prospective user identity attributes.
• DATE_REQUESTED, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit and tracking columns.

Three unique indexes are documented. FND_REGISTRATIONS_U1 (REGISTRATION_ID) is the primary surrogate key, while FND_REGISTRATIONS_U2 (REGISTRATION_KEY) is a genuine business-key candidate. FND_REGISTRATIONS_U3 is a function-based unique index over DECODE("REGISTRATION_STATUS",'REGISTERED','A',TO_CHAR("REGISTRATION_ID")), enforcing conditional uniqueness tied to status. Non-unique indexes FND_REGISTRATIONS_N1 (APPLICATION_ID, REGISTRATION_TYPE), N2 (PARTY_ID), and N3 (ASSIGNED_USER_NAME) support the principal access paths.

Common Use Cases and Queries

FND_REGISTRATIONS is queried when auditing pending registrations, reconciling invitations to created FND_USER accounts, or reporting on registration volume by application. Typical patterns include:

• Retrieving a registration from an external callback using the encrypted key: SELECT registration_id, requested_user_name, registration_status FROM fnd_registrations WHERE registration_key = :p_key;
• Listing outstanding, not-yet-approved registrations for an application: SELECT registration_id, registration_type, requested_user_name FROM fnd_registrations WHERE application_id = :app AND registration_status <> 'REGISTERED';
• Reconciling registrations to created accounts via the party identifier, joining to HZ_PARTIES and FND_USER, or by matching ASSIGNED_USER_NAME.
• Volume and status reporting grouped by APPLICATION_ID and REGISTRATION_TYPE, exploiting the N1 index.
• Identifying registrations whose party already has an account, using EXISTS_IN_FND_USER_FLAG.

Related Objects

• FND_REGISTRATION_DETAILS — companion table holding attributes that have no corresponding column in FND_REGISTRATIONS.
• FND_REGISTRATION_TYPES — referenced through the composite key (APPLICATION_ID, REGISTRATION_TYPE).
• FND_APPLICATIONS — referenced by APPLICATION_ID; drives the fingerprint used for application striping.
• HZ_PARTIES — referenced by PARTY_ID, linking the registration to trading community party data.
• FND_USER — related through ASSIGNED_USER_NAME and the EXISTS_IN_FND_USER_FLAG, allowing reconciliation of prospective registrations to provisioned accounts.
• UMF (User Management Framework) APIs — the functional layer that inserts, approves, and converts registration rows into FND_USER accounts.