Customer.OrderlineStatus

Purpose

The Customer Order Line Status view provides detailed tracking of the operational state of each customer order line. It monitors statuses, user actions, and error messages for each line item within customer orders, offering insights into the progress and any potential issues in order line processing. This view is essential for maintaining transparency and continuity in order tracking at a granular level.

Use Case

Owner: Soon Tan
Typical Use Case: Ideal for applications requiring monitoring of order line processing, error tracking, and status changes, enabling teams to quickly identify and resolve issues at the line-item level.
Style: Fact, Each row represents a unique Order Line with associated status, user actions, and order sequence.

This Customer Order Line Status view supports operational dashboards focused on the performance and troubleshooting of individual order lines, capturing both user interactions and error logs to aid in managing the workflow of each line item. Its structured JSON format for sequence tracking enhances flexibility in reporting platforms and streamlines multi-level order tracking.

Source

QFACT_CUSTOMER_ORDER_LINE__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 = 'OrderlineStatus', @token = '<myToken>', @version = '<202404>'

Response

Identifiers

• ORDER_NO: Unique identifier for the customer order.
• ORDER_LINE_SEQ (JSON Format): Provides keys for precise tracking of each order line, including:
  • ORDER_NO_KEY: Key order number.
  • LINE_NO_KEY, REL_NO_KEY, LINE_ITEM_NO_KEY: Sequential keys for detailed line-item tracking.

Status

• HIST_STATE: The current state of the order line, capturing the latest operational status.
• DATE_ENTERED: The date when the status or action was recorded.

User and Actions

• USERID: Identifier for the user who performed the action or status change.
• MESSAGE_TEXT: Additional message or error description associated with the status update, useful for diagnostics.

Additional Context

• CONTRACT: Contract reference associated with the order line.
• HISTORY_NO: History sequence number, maintaining a chronological record of status changes.

SQLCode

To access the full SQL structure, refer to…

BMT-DWH-DEV/Customer_OrderlineStatus.sql