XLA_EVENTS
This table contains all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE.
Details
-
Schema: FUSION
-
Object owner: XLA
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
XLA_EVENTS_PK |
EVENT_ID, APPLICATION_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
EVENT_ID | NUMBER | 18 | Yes | Identifier of the categorization of accounting events that is unique within an application and event class. | |
FILE_IDENTIFIER | VARCHAR2 | 1000 | File Name or OCI object storage identifier of the data file using which the transaction is created. | ||
APPLICATION_ID | NUMBER | 18 | Yes | Functional area within a software suite of products. For example, Financials or Payroll. | |
TRANSACTION_LEDGER_ID | NUMBER | 18 | Identifier of the ledger for which the accounting event is created. | ||
EVENT_TYPE_CODE | VARCHAR2 | 30 | Yes | Unique abbreviated name assigned to an event type and used for reporting or in reference to an option. | |
EVENT_DATE | DATE | Yes | Date when an accounting event is created. | ||
ENTITY_ID | NUMBER | 18 | Yes | Internal identified of the entity. | |
EVENT_STATUS_CODE | VARCHAR2 | 1 | Yes | Short name of the status associated with the accounting entries generated for this event. | |
PROCESS_STATUS_CODE | VARCHAR2 | 1 | Yes | Abbreviated code that tracks the status of generated accounting entries. | |
DATA_SET_NAME | VARCHAR2 | 30 | Used to identify a set of events to be processed by a specific Create Accounting process. Events with a data set can still be processed by a generic Create Accounting process, but they can also be processed by a Create Accounting process submitted for just the specific data set that contains them. | ||
REFERENCE_NUM_1 | NUMBER | Additional reference (Number). | |||
REFERENCE_NUM_2 | NUMBER | Additional reference (Number). | |||
REFERENCE_NUM_3 | NUMBER | Additional reference (Number). | |||
REFERENCE_NUM_4 | NUMBER | Additional reference (Number). | |||
REFERENCE_CHAR_1 | VARCHAR2 | 240 | Additional reference (Character). | ||
REFERENCE_CHAR_2 | VARCHAR2 | 240 | Additional reference (Character). | ||
REFERENCE_CHAR_3 | VARCHAR2 | 240 | Additional reference (Character). | ||
REFERENCE_CHAR_4 | VARCHAR2 | 240 | Additional reference (Character). | ||
REFERENCE_DATE_1 | DATE | Additional reference (Date). | |||
REFERENCE_DATE_2 | DATE | Additional reference (Date). | |||
REFERENCE_DATE_3 | DATE | Additional reference (Date). | |||
REFERENCE_DATE_4 | DATE | Additional reference (Date). | |||
EVENT_NUMBER | NUMBER | 38 | Yes | Identifying number of an accounting event. | |
ON_HOLD_FLAG | VARCHAR2 | 1 | Yes | Flag indicates whether the event is on hold or not. Possible values are: Y for Yes, and N for No. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
JOB_DEFINITION_NAME | VARCHAR2 | 100 | Enterprise Service Scheduler: indicates the name of the job that created or last updated the row. | ||
JOB_DEFINITION_PACKAGE | VARCHAR2 | 900 | Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row. | ||
UPG_BATCH_ID | NUMBER | 18 | Identifier of the upgrade batch. | ||
UPG_SOURCE_APPLICATION_ID | NUMBER | 18 | Internal identifier of the Upgrading application. | ||
UPG_VALID_FLAG | VARCHAR2 | 1 | Flag to indicate if Validation was successfully run for the batch. | ||
TRANSACTION_DATE | DATE | Yes | Date when a business transaction occurred, often involving the exchange of items or value. | ||
BUDGETARY_CONTROL_FLAG | VARCHAR2 | 1 | Indicates if it is a budgetary control event. | ||
MERGE_EVENT_SET_ID | NUMBER | 18 | Unique identifier of merge event set. | ||
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. | |
HAS_WARNINGS_FLAG | VARCHAR2 | 1 | Indicates whether an event has a warning message resulted from the accounting processing. | ||
PARTITION_GROUP_CODE | VARCHAR2 | 15 | Partition grouping information, when combined with the period, determines the database partition in which this journal will be stored. | ||
PERIOD_NAME | VARCHAR2 | 15 | Period name of the transaction date. It is used only for archive and purge process. It may not be the same as the accounting entry period name for this event. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
jv_accounting_headers | xla_events | EVENT_ID |
ar_adjustments_all | xla_events | EVENT_ID, PROGRAM_APPLICATION_ID |
ra_cust_trx_line_gl_dist_all | xla_events | EVENT_ID, PROGRAM_APPLICATION_ID |
vrm_perf_obligation_lin_dists | xla_events | EVENT_ID, APPLICATION_ID |
ar_misc_cash_distributions_all | xla_events | EVENT_ID, PROGRAM_APPLICATION_ID |
ar_cash_receipt_history_all | xla_events | EVENT_ID, PROGRAM_APPLICATION_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
XLA_EVENTS_N1 | Non Unique | Default | TRANSACTION_DATE |
XLA_EVENTS_N2 | Non Unique | Default | REQUEST_ID, EVENT_TYPE_CODE |
XLA_EVENTS_N3 | Non Unique | Default | PROCESS_STATUS_CODE, EVENT_TYPE_CODE, ENTITY_ID |
XLA_EVENTS_U1 | Unique | Default | EVENT_ID, APPLICATION_ID |
XLA_EVENTS_U2 | Unique | Default | ENTITY_ID, EVENT_NUMBER, APPLICATION_ID |