OKC_BUS_DOC_EVENTS
Business Document Events are certain key events in the business document life cycle. Deliverable due dates are based on the occurrence of these events. These events are seeded by external applications. For example following are the business document events identified in Purchasing document. Purchase Order Signed Purchase Order Cancelled Purchase Order Closed
Details
-
Schema: FUSION
-
Object owner: OKC
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
Name | Columns |
---|---|
OKC_BUS_DOC_EVENTS_PK |
BUS_DOC_TYPE, EVENT_ID, START_END_QUALIFIER |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
EVENT_ID | NUMBER | 18 | Yes | Unique Identifier for a Business Document Event. Also the Primary key for the table. | |
BUS_DOC_TYPE | VARCHAR2 | 30 | Yes | Business Document Type for the given Business Document Event. | |
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
START_END_QUALIFIER | VARCHAR2 | 30 | Yes | Code Value to identify whether, for a given Deliverable, the specified Business Document Event can be used as the starting event or ending event or both. Points to fnd lookup type OKC_REPEAT_UNTIL_EVENT | |
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
OKC_BUS_DOC_EVENTS | okc_bus_doc_types_b | BUS_DOC_TYPE |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
OKC_BUS_DOC_EVENTS_U1 | Unique | Default | BUS_DOC_TYPE, EVENT_ID, START_END_QUALIFIER, ORA_SEED_SET1 |
OKC_BUS_DOC_EVENTS_U11 | Unique | Default | BUS_DOC_TYPE, EVENT_ID, START_END_QUALIFIER, ORA_SEED_SET2 |