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

FND_BPM_TASK_HISTORY_VL

Common / FoundationUsed in 1 subject areas25 reporting columnsBICC incremental-ready

Foundation / Setup (FND), view layer, joins the base table with translations for the current language.

Primary key: not yet catalogued for FND_BPM_TASK_HISTORY_VL, reference Oracle Tables & Views guide. · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
ACQUIRED_BYAcquired by.
COMPLETED_DATECompleted date.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
DOMAINDomain.
FROM_USERFrom user.
IDENTIFICATION_KEYIdentification key.
INITIATED_DATEInitiated date.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEINCRDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
OUTCOMEOutcome.
OUTCOME_CODECode identifying the outcome.
PARENT_TASK_IDIdentifier for the parent task.
PARTICIPANTParticipant.
PARTICIPANT_CODECode identifying the participant.
ROOT_TASK_IDIdentifier for the root task.
STAGEStage.
STAGE_CODECode identifying the stage.
STATUS_CODECode identifying the status.
TASK_IDIdentifier for the task.
TASK_NUMBERTask number.
VERSIONVersion.
VERSION_REASONVersion reason.
WORKFLOWPATTERN_CODECode identifying the workflowpattern.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for FND_BPM_TASK_HISTORY_VL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern