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

VRM_MEA_DOC_CARVEOUT_HDRS

SharedUsed in 1 subject areas15 reporting columns

Revenue Management (VRM).

Primary key: not yet catalogued for VRM_MEA_DOC_CARVEOUT_HDRS, reference Oracle Tables & Views guide.

Columns

ColumnKeyIn reportsDescription (inferred)
ADJUSTMENT_DATE●Adjustment date.
ADJUSTMENT_STATUS●Status of the adjustment.
APPROVAL_DATE●Approval date.
APPROVED_BY●Approved by.
CARVEOUT_ADJUSTMENT_NUMBER●Carveout adjustment number.
CARVEOUT_METHOD●Carveout method.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DISPLAY_FLAG●Indicator (Y/N) for the display.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATE●Date and time the row was last updated (the incremental-extract key).
LATEST_REC_FLAG●Indicator (Y/N) for the latest rec.
REVERSED_FLAG●Indicator (Y/N) for the reversed.
REV_REC_PROCESSED_FLAG●Indicator (Y/N) for the rev rec processed.
SUGGESTED_CARVEOUT_METHOD●Suggested carveout method.

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