Oracle Fusion · Data dictionary
WLF_ASSIGNMENT_RECORDS_F
SharedUsed in 0 subject areas45 reporting columnsBICC incremental-ready
Learning (WLF).
Likely primary key: ASSIGNMENT_RECORD_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ASSIGNED_ON_DATE | ● | Assigned on date. | |
| ASSIGNMENT_RECORD_ID | PK? | ● | Identifier for the assignment record. |
| ASSIGNMENT_RECORD_NUMBER | ● | Assignment record number. | |
| ASSIGNMENT_RULE_ID | ● | Identifier for the assignment rule. | |
| ATTACHMENT_ID | ● | Identifier for the attachment. | |
| ATTRIBUTION_ID | ● | Identifier for the attribution. | |
| ATTRIBUTION_LOOKUP_CODE | ● | Lookup code for the attribution. | |
| ATTRIBUTION_TYPE | ● | Type of attribution. | |
| CALCULATED_DUE_DATE | ● | Calculated due date. | |
| COMPLETION_DATE | ● | Completion date. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| DATE_STATUS_CHANGED | ● | Date status changed. | |
| EFFECTIVE_END_DATE | ● | End date of the effective-dated record. | |
| EFFECTIVE_START_DATE | PK? | ● | Start date of the effective-dated record. |
| ENTERPRISE_ID | ● | Identifier for the enterprise. | |
| EVENT_ASSIGNMENT_ID | ● | Identifier for the event assignment. | |
| EVENT_CREATED_BY_ID | ● | Identifier for the event created by. | |
| EVENT_SUB_TYPE | ● | Type of event sub. | |
| EVENT_TYPE | ● | Type of event. | |
| EXPIRATION_DATE | ● | Expiration date. | |
| IS_HISTORY_FLAG | ● | Indicator (Y/N) for the is history. | |
| 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. | |
| LEARNER_ID | ● | Identifier for the learner. | |
| LEARNING_ITEM_ID | ● | Identifier for the learning item. | |
| LI_EFFECTIVE_DATE | ● | Li effective date. | |
| NOTIFICATION_STATUS | ● | Status of the notification. | |
| OBJECT_VERSION_NUMBER | ● | Optimistic-locking version number, incremented on each update. | |
| PRE_ASSIGNMENT_RECORD_ID | ● | Identifier for the pre assignment record. | |
| PRICING_RULE_ID | ● | Identifier for the pricing rule. | |
| REASON_CODE | ● | Code identifying the reason. | |
| REQUEST_DETAIL_ID | ● | Identifier for the request detail. | |
| SOURCE_ID | ● | Identifier for the source. | |
| SOURCE_INFO | ● | Source info. | |
| SOURCE_TYPE | ● | Type of source. | |
| STATUS | ● | Status. | |
| STATUS_CHANGE_COMMENT | ● | Status change comment. | |
| STATUS_CHANGE_TYPE | ● | Type of status change. | |
| SUB_STATUS | ● | Status of the sub. | |
| SUCC_ASSIGNMENT_RECORD_ID | ● | Identifier for the succ assignment record. | |
| TOTAL_LEARNING_TIME | ● | Total learning time. | |
| TRANSACTION_DETAILS_RULE_ID | ● | Identifier for the transaction details rule. | |
| VALIDITY_DATE | ● | Validity date. |
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 WLF_ASSIGNMENT_RECORDS_F?
We ship parameterized SQL, BICC config, and dbt models you own.