Oracle Fusion · Data dictionary
PER_PERSON_TYPES
HCMUsed in 0 subject areas12 reporting columnsBICC incremental-ready
Person / Worker (PER) — type / category reference.
Likely primary key: PERSON_TYPE_CODE (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ACTIVE_FLAG | ● | Indicator (Y/N) for the active. | |
| BUSINESS_GROUP_ID | ● | Identifier for the business group. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| DEFAULT_FLAG | ● | Indicator (Y/N) for the default. | |
| 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. | |
| PERSON_TYPE_CODE | PK? | ○ | Code identifying the person type. |
| PERSON_TYPE_ID | ● | Identifier for the person type. | |
| SEEDED_PERSON_TYPE_KEY | ● | Seeded person type key. | |
| SYSTEM_PERSON_TYPE | ● | Type of system person. |
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 PER_PERSON_TYPES?
We ship parameterized SQL, BICC config, and dbt models you own.