GL_JE_ACTION_LOG
GL_JE_ACTION_LOG stores the history of a journal batch. Each row represents an action that has occurred on the batch, and provides the user that executed the action, the role that they were acting as, and the date and time of the action. In the case of the reversal action, the journal that was reversed is also stored. This table has a many to one relationship with the GL_JE_BATCHES table, which stores the journal batches.
Details
-
Schema: FUSION
-
Object owner: GL
-
Object type: TABLE
-
Tablespace: Default
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
JE_BATCH_ID | NUMBER | 18 | Yes | Journal batch identifier. Foreign key to GL_JE_BATCHES. | |
ACTION_CODE | VARCHAR2 | 30 | Yes | Indicates the action performed on journal batch. | |
ACTION_DATE | DATE | Yes | Date and time on which the action occurred. | ||
JE_HEADER_ID | NUMBER | 18 | Journal header identifier. Foreign key to GL_JE_HEADERS. | ||
USER_ID | VARCHAR2 | 64 | Yes | User definition column. Foreign key to PER_USERS. | |
TARGET_JE_HEADER_ID | NUMBER | 18 | Target journal header identifier after journal reversal or replication actions of the source journal. | ||
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. | |
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_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
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. | |
PARTITION_GROUP_CODE | VARCHAR2 | 15 | Partition grouping information which when combined with the period, determines the database partition in which this journal will be stored. | ||
PERIOD_NAME | VARCHAR2 | 15 | Accounting period for the journal. Maintained in sync with the actual period for the journal. Not used to retain an audit trail of any periods the journal might previously have been associated with. | ||
HISTORY_HASHCODE | VARCHAR2 | 250 | Stores the hash code keys for comments, attachments, or history records. Hash code keys are 20 characters long. The application can store a maximum of 11 hash codes separated by comma. As a result, the length limit for the column is 229 characters, including commas. | ||
HISTORY_ID | NUMBER | 18 | Unique history identifier assigned to a user comment. | ||
RULE_NAME | VARCHAR2 | 4000 | The workflow rule used for assigning the workflow task to the user. | ||
PARTICIPANT_NAME | VARCHAR2 | 200 | Participant in a step in the approval workflow process. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
GL_JE_ACTION_LOG | gl_je_batches | JE_BATCH_ID |
GL_JE_ACTION_LOG | gl_je_headers | JE_HEADER_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
GL_JE_ACTION_LOG_N1 | Non Unique | Default | HISTORY_ID |
GL_JE_ACTION_LOG_U1 | Unique | Default | JE_BATCH_ID, ACTION_CODE, ACTION_DATE, JE_HEADER_ID |