Oracle Fusion · Data dictionary
ZMM_SR_SCHEDULES_B
SharedUsed in 0 subject areas14 reporting columnsBICC incremental-ready
base table — language-neutral data (paired with _TL labels and the _VL view).
Primary key: not yet catalogued for ZMM_SR_SCHEDULES_B — reference Oracle Tables & Views guide. · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ASSIGNMENT_NUM | ● | Assignment number. | |
| CATEGORY_CODE | ● | Code identifying the category. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| DELETED_FLAG | ● | Indicator (Y/N) for the deleted. | |
| EFFECTIVE_FROM_DATE | ● | Effective from date. | |
| EFFECTIVE_TO_DATE | ● | Effective to date. | |
| LAST_UPDATED_BY | ● | User who last updated the row. | |
| LAST_UPDATE_DATE | INCR | ● | Date and time the row was last updated (the incremental-extract key). |
| LAST_UPDATE_LOGIN | ● | Session login of the user who last updated the row. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| QTRLY_TYPE_CODE | ● | Code identifying the qtrly type. | |
| SCHEDULE_ID | ● | Identifier for the schedule. | |
| SCHEDULE_TYPE_CODE | ● | Code identifying the schedule type. |
Used by reports
No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.
- —
Subject areas
- —
Need the extract + dbt staging for ZMM_SR_SCHEDULES_B?
We ship parameterized SQL, BICC config, and dbt models you own.