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)

Columns

Column	Key	In reports	Description (inferred)
ADJUSTMENT_ACTION		●	Adjustment action.
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.
DEFERRED_REV_AMOUNT		●	Deferred rev amount.
ELEMENT_TYPE		●	Type of element.
FMV_LINE_ID		●	Identifier for the fmv line.
ITEM_TYPE		●	Type of item.
LAST_UPDATED_BY		●	User who last updated the row.
LAST_UPDATE_DATE		●	Date and time the row was last updated (the incremental-extract key).
LINE_NUMBER	PK?	●	Line number.
LINE_UPDATE_STATUS		●	Status of the line update.
MEA_DOC_HEADER_ID	PK?	○	Identifier for the mea doc header.
POST_ADJ_COMPLIANCE_STATUS		●	Status of the post adj compliance.
RECOGNIZED_REV_AMOUNT		●	Recognized rev amount.
REV_COMPLIANCE_PROCESS_FLAG		●	Indicator (Y/N) for the rev compliance process.
TOTAL_FMV_AMOUNT		●	Total fmv amount.
TOTAL_LINE_AMOUNT		●	Total line amount.
UNIT_REVENUE_PRICE		●	Unit revenue price.

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

We ship parameterized SQL, BICC config, and dbt models you own.