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

VRM_MEA_DOC_LINES

SharedUsed in 2 subject areas19 reporting columns

Revenue Management (VRM), line table, one row per line item under the header.

Likely primary key: MEA_DOC_HEADER_ID, LINE_NUMBER (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): MEA_DOC_HEADER_IDVRM_MEA_DOC_HEADERS

Columns

ColumnKeyIn reportsDescription (inferred)
ADJUSTMENT_ACTIONAdjustment action.
BILLED_AMOUNTBilled amount.
COMPLIANCE_STATUSStatus of the compliance.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
DEFERRED_REV_AMOUNTDeferred rev amount.
ELEMENT_TYPEType of element.
FMV_LINE_IDIdentifier for the fmv line.
ITEM_TYPEType of item.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEDate and time the row was last updated (the incremental-extract key).
LINE_NUMBERPK?Line number.
LINE_UPDATE_STATUSStatus of the line update.
MEA_DOC_HEADER_IDPK?Identifier for the mea doc header.
POST_ADJ_COMPLIANCE_STATUSStatus of the post adj compliance.
RECOGNIZED_REV_AMOUNTRecognized rev amount.
REV_COMPLIANCE_PROCESS_FLAGIndicator (Y/N) for the rev compliance process.
TOTAL_FMV_AMOUNTTotal fmv amount.
TOTAL_LINE_AMOUNTTotal line amount.
UNIT_REVENUE_PRICEUnit revenue price.

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