Results for “fnd_registrations”

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

Overview

FND_REGISTRATIONS is a table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It stores the common data underpinning the User Management Framework (UMF), the infrastructure that governs self-service user registration, account provisioning, and approval workflows. In EBS 12.1.1 and 12.2.2, UMF supports the controlled creation of application users from external or self-service channels, and FND_REGISTRATIONS is the staging and persistence layer where those requests are captured, reviewed, and ultimately reconciled against fnd_user and the trading community model.

From a Data Vault modeling perspective, the metadata's heuristic classification places this table as satellite-leaning. This is a sensible suggestion: FND_REGISTRATIONS carries descriptive attributes (names, contact details, addresses, and status) around a single transactional identifier rather than acting as a pure hub or associative link. Its foreign key to HZ_PARTIES nonetheless introduces a genuine link-like characteristic, tying registration records to the unified party model maintained by Oracle Trading Community Architecture.

Key Information Stored

Each row represents a single registration request, identified internally by the surrogate key REGISTRATION_ID. Two business-key candidates are documented as unique indexes: REGISTRATION_KEY, an external reference suitable for tracing requests across systems, and a functional unique index on REGISTRATION_STATUS, which enforces a constrained value set (the index expression decodes a status of 'REGISTERED' to 'A').

The most operationally significant columns include:

• REGISTRATION_ID — surrogate primary key, system-assigned.
• REGISTRATION_KEY — externally meaningful unique identifier.
• APPLICATION_ID — the EBS application for which access is requested.
• PARTY_ID — foreign key to HZ_PARTIES, linking the registrant to the trading community party record.
• REGISTRATION_TYPE and REGISTRATION_STATUS — control the request classification and its position in the approval lifecycle.
• REQUESTED_USER_NAME and ASSIGNED_USER_NAME — the login desired by the requester and the final name granted.
• EXISTS_IN_FND_USER_FLAG — indicates whether an application user already exists for the request.
• FIRST_NAME, MIDDLE_NAME, LAST_NAME, USER_SUFFIX, USER_TITLE — personal identity attributes.
• EMAIL and EMAIL_CONTACT_POINT_ID — contact e-mail and its TCA contact point reference.
• PHONE-related columns and FAX-related columns — alternate contact channels, each with matching contact point IDs.
• DATE_REQUESTED — the submission timestamp.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit and concurrency controls.

Common Use Cases and Queries

Administrators, auditors, and workflow developers typically query FND_REGISTRATIONS to monitor the state of pending user requests, audit rejected registrations, or reconcile registration data against fnd_user. Common queries include status rollups by application, duplicate detection, and match-back routines against HZ_PARTIES.

A representative pattern:

SELECT r.registration_id, r.registration_key, r.registration_status,
       r.requested_user_name, r.assigned_user_name, r.email, u.user_id
FROM   applsys.fnd_registrations r
LEFT   OUTER JOIN applsys.fnd_user u
       ON u.user_name = r.assigned_user_name
WHERE  r.registration_status = 'REGISTERED';

Reporting scenarios commonly aggregate volume by DATE_REQUESTED or exercise the EXISTS_IN_FND_USER_FLAG to surface requests that were never provisioned, a frequent concern during SOX or access-certification reviews.

Related Objects

The following objects are most significant to working with this table:

• HZ_PARTIES — referenced via FND_REGISTRATIONS.PARTY_ID, providing the master party record.
• FND_USER — matched on ASSIGNED_USER_NAME to confirm provisioning.
• HZ_CONTACT_POINTS — related through EMAIL_CONTACT_POINT_ID, PHONE_CONTACT_POINT_ID, and FAX_CONTACT_POINT_ID.
• FND_APPLICATION — joined via APPLICATION_ID to resolve application names.
• HZ_LOCATIONS — related through LOCATION_ID for address resolution.
• UMF workflow components and the User Management responsibility — process registrations through the approval chain.
• FND_REGISTRATIONS_U1, _U2, and _U3 — the unique indexes enforcing identifier and status integrity.