Customer.Order

Purpose

The Customer Order view provides a high-level “document header” for customer orders, designed to summarise and contextualise individual order lines within customer orderline views. It includes essential details such as order number, customer information, order dates, and status codes, serving as a consolidated source for tracking and reporting on customer orders. By connecting order-level data with detailed order lines, it ensures data clarity and supports comprehensive analysis.

Use Case

Owner: Soon Tan
Typical Use Case: This view is ideal for applications and reports requiring an overarching summary of customer orders, enabling users to integrate and align with individual order line details.
Style: Dimension, Single row per unique Order No with summarised customer and order attributes.

DataMart Integration

This view can be utilised across the following DataMarts:

• Customer
• Project
• Company

Source

QFACT_CUSTOMER_ORDER_CFV_OL$

This table consolidates customer order information, providing essential summarised data points for integration with order line views.

Sample Exec

For sample data execution, use the code:

EXEC get.myView @dataMart = 'Customer', @viewName = 'Order', @token = '<myToken>', @version = '<202404>'

Response

Identifiers

• COMPANY: Identifier for the company placing the order.
• ORDER_NO: Unique order number.
• CUSTOMER_ID (CUSTOMER_NO): Identifier for the customer.
• PROJECT_ID: Project associated with the order.
• OPPORTUNITY_NO (BUSINESS_OPPORTUNITY_NO): Related business opportunity number.

Dates

• DATE_ENTERED: Date the order was entered.
• WANTED_DELIVERY_DATE: Customer’s desired delivery date.
• WON_DATE: Date when the order was marked as won.

Currency (JSON Format)

• CURRENCY: Currency code for the transaction.

Codes (JSON Format)

• AUTHORIZE_CODE: Authorisation code, if any.
• CONTRACT: Contract details.
• CUSTOMER PO and REF: Includes purchase order number and customer reference details.

Status (JSON Format)

• OBJSTATE: Object state of the order.
• STATE: Current state or status of the order.
• CANCEL_REASON: Reason for cancellation, if applicable.

Market Information (JSON Format)

• SALES_MARKET: Code for the sales market.
• STRATEGIC_PILLAR: Code and description for the strategic pillar associated with the order.
• SALES_REGION: Code for the sales region.
• SALES_DISTRICT: Code for the sales district.

SQL

BMT-DWH-DEV/Customer_Order.sql