eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: APPLSYS.FND_REGISTRATIONS

Object Details

Object Name:	FND_REGISTRATIONS
Object Type:	TABLE
Owner:	APPLSYS
FND Design Data:	FND.FND_REGISTRATIONS
Subobject Name:
Status:	VALID

Table contains commonly used columns and is the driving table for the User Management Framework (UMF). Data for which there is no column in this table should be stored in the FND_REGISTRATION_DETAILS table. DBA Note: For cases in which many sparse invitations are expected, performance may be enhanced by increasing the %Free, which may be inadequate for this use case.

Storage Details

Tablespace:	APPS_TS_ARCHIVE
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
FND_REGISTRATIONS_U1	NORMAL	UNIQUE	APPS_TS_ARCHIVE	REGISTRATION_ID
FND_REGISTRATIONS_U2	NORMAL	UNIQUE	APPS_TS_ARCHIVE	REGISTRATION_KEY
FND_REGISTRATIONS_U3	FUNCTION-BASED NORMAL	UNIQUE	APPS_TS_ARCHIVE	DECODE("REGISTRATION_STATUS",'REGISTERED','A',TO_CHAR("REGISTRATION_ID"))
FND_REGISTRATIONS_N1	NORMAL	NONUNIQUE	APPS_TS_ARCHIVE	APPLICATION_ID REGISTRATION_TYPE
FND_REGISTRATIONS_N2	NORMAL	NONUNIQUE	APPS_TS_ARCHIVE	PARTY_ID
FND_REGISTRATIONS_N3	NORMAL	NONUNIQUE	APPS_TS_ARCHIVE	ASSIGNED_USER_NAME

Columns

Name	Datatype	Length	Mandatory	Comments
REGISTRATION_ID	NUMBER	(15)	Yes	PK for the table. This is unique, indexed, and synthetic
REGISTRATION_KEY	VARCHAR2	(100)	Yes	This is the encrypted form of the registration_id.
APPLICATION_ID	NUMBER	(15)	Yes	FK to FND_APPLICATIONS, striping the data by the application for which the prospective user is registering. Also part of FK to FND_REGISTRATION_TYPES
PARTY_ID	NUMBER	(15)		FK to HZ_PARTIES
REGISTRATION_TYPE	VARCHAR2	(255)	Yes	With APPLICATION_ID, FK to FND_REGISTRATION_TYPES, allowing multiple types of registration within a particular application
REQUESTED_USER_NAME	VARCHAR2	(100)		Prospective USER_NAME for the user. Will be uppercased in the insert methods.
ASSIGNED_USER_NAME	VARCHAR2	(100)		FK to FND_USER: Username which is used once the user is approved. These are uppercased before being stored in this table.
REGISTRATION_STATUS	VARCHAR2	(30)	Yes	This is used to drive flow progression. Possible values are INVITED, REGISTERED, APPROVED, REJECTED
EXISTS_IN_FND_USER_FLAG	VARCHAR2	(30)	Yes	Y if user does not need to be created in FND_USER again
USER_TITLE	VARCHAR2	(100)		The user's title, eg Mr., Mrs., Dr... This would ordinarily be a lookup code.
FIRST_NAME	VARCHAR2	(100)		User's first name
MIDDLE_NAME	VARCHAR2	(100)		User's middle name. Often only an initial is captured here.
LAST_NAME	VARCHAR2	(100)		User's last name
USER_SUFFIX	VARCHAR2	(30)		A name suffix, eg Jr
EMAIL_CONTACT_POINT_ID	NUMBER	(15)		FK to HZ_CONTACT_POINTS. This is provisional, as we would like to use the TCA packages for validation.
EMAIL	VARCHAR2	(100)		The user's email address
PHONE_CONTACT_POINT_ID	NUMBER	(15)		FK to HZ_CONTACT_POINTS. This is provisional, as we would like to use the TCA packages for validation.
PHONE_COUNTRY_CODE	VARCHAR2	(100)		The country code for the phone number
PHONE_AREA_CODE	VARCHAR2	(10)		The area code for a US phone number
PHONE	VARCHAR2	(100)		The user's phone number. The data is usually pushed after stripping out non-numeric characters
PHONE_EXTENSION	VARCHAR2	(100)		The user's extension
FAX_CONTACT_POINT_ID	NUMBER	(15)		FK to HZ_CONTACT_POINTS. This is provisional, as we would like to use the TCA packages for validation.
FAX_COUNTRY_CODE	VARCHAR2	(100)		The country code for the fax
FAX_AREA_CODE	VARCHAR2	(10)		The area code for a US fax number
FAX	VARCHAR2	(100)		The user's fax. The data is usually pushed after stripping out non-numeric characters.
FAX_EXTENSION	VARCHAR2	(100)		The user's fax extension
LANGUAGE_CODE	VARCHAR2	(4)		FK to FND_LANGUAGES LANGUAGE_CODE
TIME_ZONE	VARCHAR2	(100)		User's timezone. Note that this is inconsistent across platforms: TCA stores a number, others applications store a code referencing a lookup.
TERRITORY_CODE	VARCHAR2	(2)		FK to FND_TERRITORIES TERRITORY_CODE
LOCATION_ID	NUMBER	(15)		reference to HZ_LOCATIONS.LOCATION_ID
ADDRESS1	VARCHAR2	(240)		First line of address information
ADDRESS2	VARCHAR2	(240)		Second line of address information
CITY	VARCHAR2	(100)		Name of user's city
STATE	VARCHAR2	(60)		Name of user's state, if in US
PROVINCE	VARCHAR2	(100)		Name of user's province or region, if outside US
ZIP	VARCHAR2	(10)		User's US zip code, if in US
POSTAL_CODE	VARCHAR2	(40)		User's postal code, if outside US
COUNTRY	VARCHAR2	(100)		User's country for address. Usually implemented as an FND_TERRITORY TERRITORY_CODE
DATE_REQUESTED	DATE			Date the registration was completed
LAST_UPDATE_DATE	DATE		Yes	Who field
LAST_UPDATED_BY	NUMBER	(15)	Yes	Who field
CREATED_BY	NUMBER	(15)	Yes	Who field
CREATION_DATE	DATE		Yes	Who field
LAST_UPDATE_LOGIN	NUMBER	(15)		Who field

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT REGISTRATION_ID
,      REGISTRATION_KEY
,      APPLICATION_ID
,      PARTY_ID
,      REGISTRATION_TYPE
,      REQUESTED_USER_NAME
,      ASSIGNED_USER_NAME
,      REGISTRATION_STATUS
,      EXISTS_IN_FND_USER_FLAG
,      USER_TITLE
,      FIRST_NAME
,      MIDDLE_NAME
,      LAST_NAME
,      USER_SUFFIX
,      EMAIL_CONTACT_POINT_ID
,      EMAIL
,      PHONE_CONTACT_POINT_ID
,      PHONE_COUNTRY_CODE
,      PHONE_AREA_CODE
,      PHONE
,      PHONE_EXTENSION
,      FAX_CONTACT_POINT_ID
,      FAX_COUNTRY_CODE
,      FAX_AREA_CODE
,      FAX
,      FAX_EXTENSION
,      LANGUAGE_CODE
,      TIME_ZONE
,      TERRITORY_CODE
,      LOCATION_ID
,      ADDRESS1
,      ADDRESS2
,      CITY
,      STATE
,      PROVINCE
,      ZIP
,      POSTAL_CODE
,      COUNTRY
,      DATE_REQUESTED
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATE_LOGIN
FROM APPLSYS.FND_REGISTRATIONS;

Dependencies

[top of page]

APPLSYS.FND_REGISTRATIONS does not reference any database object

APPLSYS.FND_REGISTRATIONS is referenced by following:

APPLSYS: FND_REGISTRATIONS#