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

Column	Key	In reports	Description (inferred)
ADJUSTMENT_STATUS		●	Status of the adjustment.
AMOUNT_REQUIRING_ATTENTION		●	Amount requiring attention.
ARRANGEMENT_AMOUNT		●	Arrangement amount.
BILLED_AMOUNT		●	Billed amount.
COMPLIANCE_STATUS		●	Status of the compliance.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
CURRENCY_CODE		●	Code identifying the currency.
DEFERRED_FLAG		●	Indicator (Y/N) for the deferred.
DEFERRED_REV_AMOUNT		●	Deferred rev amount.
ELEMENT_COUNT		●	Element count.
LAST_UPDATED_BY		●	User who last updated the row.
LAST_UPDATE_DATE		●	Date and time the row was last updated (the incremental-extract key).
LINES_PENDING_PRICE_CALC_COUNT		●	Lines pending price calc count.
LINES_REQUIRING_ATTENTION		●	Lines requiring attention.
LINE_COUNT		●	Line count.
MEA_DATE		●	Mea date.
MEA_DOC_HEADER_ID	PK?	○	Identifier for the mea doc header.
MEA_END_DATE		●	Mea end date.
MEA_NUMBER		●	Mea number.
PARTY_NAME		●	Name of the party.
RECOGNIZED_REV_AMOUNT		●	Recognized rev amount.
REFERENCE		●	Reference.
TOTAL_FMV_AMOUNT		●	Total fmv amount.
TOTAL_LINE_AMOUNT		●	Total line amount.

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

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.