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: OKC.OKC_STATUSES_B

Object Details

Object Name:	OKC_STATUSES_B
Object Type:	TABLE
Owner:	OKC
FND Design Data:	OKC.OKC_STATUSES_B
Subobject Name:
Status:	VALID

[STATUS is a user defined value that defines a contract's status.
Each user-defined status must be in one of six STATUS TYPES, which are seeded values in FND_LOOKUPS. The six status types are:
Entered
Cancelled
Active
Hold
Expired
Terminated
Within each status type, users may define as many statuses as they need. Along with OPERATIONS, SUBCLASS, and ASSENT, status helps drive what the system can or cannot do and what the system allows users to do. For example, it may be allowed to delete a contract in a Cancelled status but not in an Active status.
Users may manually change a contract's status provided both status codes belong to the same status type. They may manually transition from any status code of the Entered type to any status code of the Cancelled type. They may manually transition from any status code of the Active type to any status code of the Hold type and vice-versa. All other transitions must be performed by the application.
In those cases where the application transitions a contract from one status type to another, it may use the DEFAULT_YN flag to determine which status code to use for the new state. For example, the application will detect when an active contract reaches its end date. The application must put the contract into an Expired status. It will determine which of all the possible Expired statuses to use by selecting the one with the DEFAULT_YN flag set to 'Y'.

Storage Details

Tablespace:	APPS_TS_SEED
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
OKC_STATUSES_U1	NORMAL	UNIQUE	APPS_TS_SEED	CODE
OKC_STATUSES_N1	NORMAL	NONUNIQUE	APPS_TS_SEED	STE_CODE

Columns

Name	Datatype	Length	Mandatory	Comments
CODE	VARCHAR2	(30)	Yes	Status code as defined in FND_LOOKUP_VALUES.
STE_CODE	VARCHAR2	(30)	Yes	Status Type to which this Status Code belongs to. For example, Status Type "ENTERED'' can have ''ENTERED'', ''SUBMITTED FOR APPROVAL'' as status codes.
DEFAULT_YN	VARCHAR2	(3)	Yes	Indicates if a status code is the default status code for the given status type.
START_DATE	DATE		Yes	The beginning of the active period, one second after midnight on the date indicated.
END_DATE	DATE			The end of the active period, one second before midnight on the date indicated.
OBJECT_VERSION_NUMBER	NUMBER	(9)	Yes	Sequential number set at 1 on insert and incremented on update. Used by APIs to ensure current record is passed.
CREATED_BY	NUMBER	(15)	Yes	Standard Who column.
CREATION_DATE	DATE		Yes	Standard Who column.
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard Who column.
LAST_UPDATE_DATE	DATE		Yes	Standard Who column.
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who column.
SECURITY_GROUP_ID	NUMBER			Used in hosted environments

Query Text

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


SELECT CODE
,      STE_CODE
,      DEFAULT_YN
,      START_DATE
,      END_DATE
,      OBJECT_VERSION_NUMBER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      SECURITY_GROUP_ID
FROM OKC.OKC_STATUSES_B;

Dependencies

[top of page]

OKC.OKC_STATUSES_B does not reference any database object

OKC.OKC_STATUSES_B is referenced by following:

APPS: OKC_STATUSES_B