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

WIE_OPERATION_TRANSACTIONS

SharedUsed in 2 subject areas19 reporting columns

Work in Process (WIE).

Likely primary key: WO_OPERATION_TRANSACTION_ID (inferred from Oracle naming conventions, verify against Tables & Views)

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
FROM_DISPATCH_STATEFrom dispatch state.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEDate and time the row was last updated (the incremental-extract key).
OP_COMPL_FLAGIndicator (Y/N) for the op compl.
REASON_CODECode identifying the reason.
SOURCE_HEADER_REFSource header reference.
SOURCE_LINE_REFSource line reference.
SOURCE_SYSTEM_CODECode identifying the source system.
SOURCE_SYSTEM_IDIdentifier for the source system.
SOURCE_SYSTEM_TYPEType of source system.
TO_DISPATCH_STATETo dispatch state.
TRANSACTION_DATETransaction date.
TRANSACTION_NOTETransaction note.
TRANSACTION_QUANTITYTransaction quantity.
TRANSACTION_UOM_CODECode identifying the transaction unit of measure.
VARIANCE_QUANTITYVariance quantity.
WO_OPERATION_TRANSACTION_IDPK?Identifier for the wo operation transaction.

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 WIE_OPERATION_TRANSACTIONS?
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