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

VRM_REVENUE_DOCUMENTS_ALL

SharedUsed in 2 subject areas18 reporting columns

Revenue Management (VRM), transaction table (rows scoped across all operating units).

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

Columns

ColumnKeyIn reportsDescription (inferred)
COMPLETE_FLAG●Indicator (Y/N) for the complete.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DOCUMENT_DATE●Document date.
DOCUMENT_NUMBER●Document number.
EXCHANGE_RATE●Exchange rate.
EXCHANGE_RATE_DATE●Exchange rate date.
EXCHANGE_RATE_TYPE●Type of exchange rate.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATE●Date and time the row was last updated (the incremental-extract key).
PAYMENT_AMOUNT●Payment amount.
REVENUE_TOTAL_AMOUNT●Revenue total amount.
REVENUE_TOTAL_CARVEOUT_AMOUNT●Revenue total carveout amount.
SOURCE●Source.
SOURCE_DOCUMENT_DATE●Source document date.
SOURCE_DOCUMENT_NUMBER●Source document number.
SOURCE_SYSTEM●Source system.
TOTAL_SELLING_AMOUNT●Total selling 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. 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_REVENUE_DOCUMENTS_ALL?
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