Customer.InvoiceStatus

Purpose

The Customer Invoice Status view provides insight into the operational state of customer invoices by tracking statuses and reporting errors. This view is intended for monitoring the life-cycle and status changes of invoices, including entry dates, user actions, and error messages. It supports operational reporting by offering visibility into any issues or errors that may affect invoice processing.

This query generates a row for each status update of an invoice, ordered by the date and time of entry. It provides a historical sequence to aid in understanding the life-cycle of an invoice and diagnosing any processing issues.

Use Case

Owner: Soon Tan
Typical Use Case: Ideal for applications and reports needing a comprehensive view of invoice processing statuses, allowing users to monitor and troubleshoot any errors or delays in the invoice life-cycle.
Style: Fact, Each row represents a unique Invoice ID and History Number, providing a historical snapshot of the invoice status at each recorded stage.

Source

QFACT_CUST_ORDER_INVOICE_H_OL$

Sample Exec

For sample data execution, use the code:

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

Response

Identifiers

INVOICE_SEQ (JSON Format): Structured sequence for Invoice tracking, including:

• COMPANY: Company identifier.
• ORDER_NO: Order number.

SEQ

HISTORY_NO: Chronological sequence number, tracking each recorded status change.

Dates

• DATE_ENTERED: Date when the status or action was recorded.

User and Actions

• ENTERED_BY: JSON-formatted user and action details, including:
  • TIME_ENTERED: Time the status or action was recorded.
  • USER_ID: Identifier of the user who performed the action.
• MESSAGE_TEXT: Text message or error description associated with the status, which can help diagnose issues or track specific actions.

SQL Code

To access the full SQL structure, refer to…

BMT-DWH-DEV/Customer_InvoiceStatus.sql