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.

Primary key: not declared here, see Oracle's Tables and Views page for VRM_MEA_DOC_LINES

Columns

ColumnKeyIn reportsDescription (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●Line number.
LINE_UPDATE_STATUS●Status of the line update.
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.

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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed 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