Analytics Catalog/Data dictionary/PER_DRIVERS_LICENSES
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

PER_DRIVERS_LICENSES

HCMUsed in 0 subject areas21 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: DRIVERS_LICENSE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_ID●Identifier for the business group.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DATE_FROM●Date from.
DATE_TO●Date to.
DRIVERS_LICENSE_IDPK?●Identifier for the drivers license.
ISSUING_AUTHORITY●Issuing authority.
ISSUING_COUNTRY●Issuing country.
ISSUING_LOCATION●Issuing location.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATEINCR●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.
LEGISLATION_CODE●Code identifying the legislation.
LICENSE_NUMBER●License number.
LICENSE_SUSPENDED●License suspended.
NUMBER_OF_POINTS●Number of points.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
PERSON_ID●Identifier for the person.
SUSPENDED_FROM_DATE●Suspended from date.
SUSPENDED_TO_DATE●Suspended to date.
VIOLATIONS●Violations.

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_DRIVERS_LICENSES?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
The report that lies quietly · Approval history vanishes · What the extract does not carry