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

VRM_MEA_DOC_HEADERS

SharedUsed in 2 subject areas24 reporting columns

Revenue Management (VRM), header table, one row per transaction or event (with detail in the paired _LINES table).

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

Columns

ColumnKeyIn reportsDescription (inferred)
ADJUSTMENT_STATUSStatus of the adjustment.
AMOUNT_REQUIRING_ATTENTIONAmount requiring attention.
ARRANGEMENT_AMOUNTArrangement amount.
BILLED_AMOUNTBilled amount.
COMPLIANCE_STATUSStatus of the compliance.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
CURRENCY_CODECode identifying the currency.
DEFERRED_FLAGIndicator (Y/N) for the deferred.
DEFERRED_REV_AMOUNTDeferred rev amount.
ELEMENT_COUNTElement count.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEDate and time the row was last updated (the incremental-extract key).
LINES_PENDING_PRICE_CALC_COUNTLines pending price calc count.
LINES_REQUIRING_ATTENTIONLines requiring attention.
LINE_COUNTLine count.
MEA_DATEMea date.
MEA_DOC_HEADER_IDPK?Identifier for the mea doc header.
MEA_END_DATEMea end date.
MEA_NUMBERMea number.
PARTY_NAMEName of the party.
RECOGNIZED_REV_AMOUNTRecognized rev amount.
REFERENCEReference.
TOTAL_FMV_AMOUNTTotal fmv amount.
TOTAL_LINE_AMOUNTTotal line amount.

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