This table requires activation of Draft Order Management functional area. Draft Sales Order Header Fact
Module: Order Management
ORDER_HEADER_ID
Name | Datatype | Length | Precision | Not Null | Comments | Referred Table | Referred Column |
---|---|---|---|---|---|---|---|
ORDER_HEADER_ID | NUMBER | 38 | 0 | True | Unique identifier of the orchestration order | ||
SOURCE_RECORD_ID | VARCHAR2 | 128 | This column is for Oracle Internal use only. Unique identifier | ||||
ORDER_NUMBER | VARCHAR2 | 64 | Representation of a sales order used in communication with fulfillment systems | ||||
BUSINESS_UNIT_ID | NUMBER | 38 | 0 | Business Unit identifier | DW_BUSINESS_UNIT_D | BUSINESS_UNIT_ID | |
LEGAL_ENTITY_ID | NUMBER | 38 | 0 | Legal entity identifier | DW_LEGAL_ENTITY_D | LEGAL_ENTITY_ID | |
ORDER_TYPE_CODE | VARCHAR2 | 32 | Name of the type of order that was placed. Stores codes for values of order types. | DW_ORDER_TYPE_LKP_TL | ORDER_TYPE_CODE | ||
ORDER_STATUS_CODE | VARCHAR2 | 32 | Status of the order. | DW_OM_STATUS_D | STATUS_CODE | ||
SOURCE_ORDER_SYSTEM | VARCHAR2 | 64 | Reference to the Source Order System | ||||
SOURCE_DOCUMENT_TYPE_CODE | VARCHAR2 | 64 | Indicates the Original Document document type on the order | ||||
SOLD_TO_PARTY_ID | NUMBER | 38 | 0 | Reference to the unique identifier for the sold-to Party. | DW_PARTY_D | PARTY_ID | |
SOLD_TO_CONTACT_PARTY_ID | NUMBER | 38 | 0 | Reference to the unique identifier for the sold-to contact Party. | DW_PARTY_D | PARTY_ID | |
LEDGER_ID | NUMBER | 38 | 0 | Primary ledger id. Derived from the Business Unit. | DW_LEDGER_D | LEDGER_ID | |
FISCAL_PERIOD_TYPE | VARCHAR2 | 16 | Period type. Derived from the ledger associated with the Business Unit. #1 | DW_FISCAL_DAY_D | FISCAL_PERIOD_TYPE | ||
FISCAL_PERIOD_SET_NAME | VARCHAR2 | 16 | Period Set Name.Derived from the ledger associated with the Business Unit. #1 | DW_FISCAL_DAY_D | FISCAL_PERIOD_SET_NAME | ||
ORDERED_DATE | DATE | Date when the items where ordered #1 | DW_DAY_D | CALENDAR_DATE | |||
ORDERED_TIMESTAMP | TIMESTAMP | Date with timestamp when the items where ordered | |||||
CREATION_DATE | DATE | order creation date | DW_DAY_D | CALENDAR_DATE | |||
CREATION_TIMESTAMP | TIMESTAMP | order creation date with timestamp | |||||
ORDER_CUSTOMER_PO_NUMBER | VARCHAR2 | 64 | Header level customer PO number |
#1 In these cases to join with DW_FISCAL_DAY_D apart from FISCAL_PERIOD_TYPE and FISCAL_PERIOD_SET_NAME the relationship should be based on ORDERED_DATE column
Copyright © 2019, 2024, Oracle and/or its affiliates.