Oracle Fusion · Data dictionary
GL_PERIOD_STATUSES
General LedgerUsed in 1 subject areas11 reporting columns
General Ledger (GL), period open/close status per ledger and application.
Primary key: LEDGER_ID, APPLICATION_ID, PERIOD_NAME
Joins (inferred from key columns): LEDGER_ID → GL_LEDGERS
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| APPLICATION_ID | PK | ● | Identifier for the application. |
| CLOSING_STATUS | ● | Status of the closing. | |
| EFFECTIVE_PERIOD_NUM | ● | Effective period number. | |
| END_DATE | ● | End date. | |
| LEDGER_ID | PK | ○ | Ledger identifier for the row. |
| PERIOD_NAME | PK | ● | Name of the period. |
| PERIOD_TYPE | ● | Type of period. | |
| PERIOD_YEAR | ● | Period year. | |
| QUARTER_NUM | ● | Quarter number. | |
| QUARTER_START_DATE | ● | Quarter start date. | |
| START_DATE | ● | Start date. | |
| YEAR_START_DATE | ● | Year start date. |
3 reports read from this table
Change a column here and these are the reports that move with it, the blast radius for any change to GL_PERIOD_STATUSES.
- GL Period Status Report
- General Ledger Report for China Secondary Ledgers
- Subledger Period Close Exceptions Report
Where this surfaces in OTBI
The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.
Need the extract + dbt staging for GL_PERIOD_STATUSES?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table