GL_PURGE_DATA_TO_PURGE

This table stores the details of what is going to be purged after the purge action for specific criteria is selected, but before the purge process is submitted. These details are stored only when the retention location for the archived data is Oracle Cloud ERP.

Details

  • Schema: FUSION

  • Object owner: GL

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

GL_PURGE_DATA_TO_PURGE_PK

PURGE_RUN_ID, BUSINESS_OBJECT_CODE, CALENDAR_ID, LEDGER_ID, LEGAL_ENTITY_ID, BALANCING_SEGMENT_VALUE

Columns

Name Datatype Length Precision Not-null Comments
PURGE_RUN_ID NUMBER 18 Yes Purge run identifier for this row.
BUSINESS_OBJECT_CODE VARCHAR2 30 Yes Business object for which the archived data is going to be purged. Some valid values are ORA_GL_JOURNALS for General Ledger journals and ORA_GL_BALANCES for General Ledger balances.
CALENDAR_ID NUMBER 18 Yes Accounting calendar identifier associated with the archived data that is going to be purged.
PERIOD_SET_NAME VARCHAR2 15 Yes Accounting calendar name associated with the archived data that is going to be purged.
PERIOD_TYPE VARCHAR2 15 Yes Period type for the accounting calendar associated with the archived data that is going to be purged.
LEDGER_ID NUMBER 18 Yes Ledger identifier for which the archived data is going to be purged. Can be a primary ledger, secondary ledger, or reporting currency. A value of -99 indicates this row applies to all ledgers.
LEGAL_ENTITY_ID NUMBER 18 Yes Legal entity for which archive and purge is being done. -99 in cases where this row is across legal entities.
FROM_PERIOD_NAME VARCHAR2 15 Yes First period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
FROM_PERIOD_YEAR NUMBER 18 Yes Period year of the first period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
FROM_PERIOD_NUM NUMBER 18 Yes Period number of the first period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
TO_PERIOD_NAME VARCHAR2 15 Yes Last period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
TO_PERIOD_YEAR NUMBER 18 Yes Period year of the last period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
TO_PERIOD_NUM NUMBER 18 Yes Period number of the last period that is going to be purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
PURGE_DATE DATE Yes Date through which periods are being purged for this combination of business object, calendar, ledger (if applicable), and legal entity (if applicable).
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.
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.
BALANCING_SEGMENT_VALUE VARCHAR2 25 Yes Balancing segment value associated with the specified retention period. A value of -99 indicates all balancing segment values.

Indexes

Index Uniqueness Tablespace Columns
GL_PURGE_DATA_TO_PURGE_U1 Unique Default PURGE_RUN_ID, BUSINESS_OBJECT_CODE, CALENDAR_ID, LEDGER_ID, LEGAL_ENTITY_ID, BALANCING_SEGMENT_VALUE