Oracle Fusion · Data dictionary
VRM_SOURCE_DOCUMENTS
SharedUsed in 4 subject areas11 reporting columns
Revenue Management (VRM).
Primary key: not yet catalogued for VRM_SOURCE_DOCUMENTS, reference Oracle Tables & Views guide.
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CANCELLED_FLAG | ● | Indicator (Y/N) for the cancelled. | |
| CUSTOMER_CONTRACT_NUMBER | ● | Customer contract number. | |
| CUST_PO_NUMBER | ● | Customer purchase order number. | |
| DOCUMENT_DATE | ● | Document date. | |
| DOCUMENT_NUMBER | ● | Document number. | |
| MEA_FLAG | ● | Indicator (Y/N) for the mea. | |
| QUOTE_NUMBER | ● | Quote number. | |
| RETURN_REASON_CODE | ● | Code identifying the return reason. | |
| SALES_AGREEMENT_NUMBER | ● | Sales agreement number. | |
| SOURCE_SYSTEM | ● | Source system. | |
| SOURCE_TYPE_CODE | ● | Code identifying the source type. |
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. You can't join across them in OTBI, the owned conformed model joins them on shared keys.
- Revenue Management - Revenue Compliance Fair Market Value Real Time
- Revenue Management - Revenue Compliance MEA Carve-out Real Time
- Revenue Management - Revenue Recognition Real Time
- Revenue Management - Source Documents Real Time
Need the extract + dbt staging for VRM_SOURCE_DOCUMENTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table