Oracle Fusion · Data dictionary
PAY_ELEMENT_TYPES_TL
PayrollUsed in 0 subject areas12 reporting columnsBICC incremental-ready
Payroll (PAY), translation table, multi-language labels (join on the base key + LANGUAGE).
Likely primary key: ELEMENT_TYPE_CODE, LANGUAGE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| DESCRIPTION | ● | Description. | |
| ELEMENT_NAME | ● | Name of the element. | |
| ELEMENT_TYPE_CODE | PK? | ○ | Code identifying the element type. |
| ELEMENT_TYPE_ID | ● | Identifier for the element type. | |
| LANGUAGE | PK? | ● | Language. |
| 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. | |
| REPORTING_NAME | ● | Name of the reporting. | |
| SOURCE_LANG | ● | Source lang. |
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 PAY_ELEMENT_TYPES_TL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table