The Demand Transaction Review Assembly can be used to view demand transaction data, as well as aggregate statistics by customer code. This assembly is often used in conjunction with the customer demand analysis functionality, however, it can be used to review individual transactions without utilizing the customer code analysis functionality as well. The screen is split into 5 main components which are described in detail below.
Demand Transaction Review Assembly
Customer Code Summary Grid
This grid at the top center of the screen aggregates by Customer Code. By default, the 4 columns shown are: Customer Code, Customer Description, Customer Sales Change Coefficient, and Abs. T Value Intervened. The "Customer Sales Change Coefficient" is the average value by which the Customer Codes' past 30 days of buying history differs from the past year. The "Abs. T-Value Intervened" refers to the statistical significance of the shift in buying history (More information on both of these calculations can be found in the Customer Demand Analysis page). Additional fields can be added to this grid by right-clicking and going through the customize pop-up
Customer Code Summary Grid
Graphs
Currently, the tabbed graph section to the right of the Customer Code Summary Grid has three different charts:
- 90 Day Time Series: 90 Day Time Series Graph of COGS by Customer Code. Each month is shown in a different color as detailed in the key
- History & Forecast: Currently unavailable. Will show history/forecast information at customer level once available
- Summary Tree Map: Tree map where each box represents a different customer code. The size of each cell corresponds to COGS over the past year and color corresponds to T-Value
90 Day Time Series and Summary Tree Map Graphs
Customer Code SKUL Summary Grid
The middle grid on the screen shows aggregate transactional data by SKUL for the customer code selected in the main summary grid. Descriptions of each of the columns are below (by default period refers to 30 days):
| Field | Description |
| Item | |
| Ship Loc | |
| Customer Units Per Period (Past Yr) | A calculation of average units of this SKUL purchased by the selected customer code across the past year per defined period (by default will be 30 day periods) |
| Customer Units Last Period | Actual Units Sold in Past 30 Days |
| Customer $ Per Period (Past Yr) | A calculation of average dollarized value of this SKUL purchased by the selected customer code across the past year per defined period (by default will be 30 day periods) |
| Customer $ Last Period | Actual COGS in Past 30 Days |
| Customer Units Difference |
Customer Units Last Period – Customer Units Per Period (Past Yr) |
| Customer $ Difference |
Customer $ Last Period – Customer $ Per Period (Past Yr) |
| Average SKUL Forecast Units Per Period (Next Yr) | Average Forecasted Unit Per 30 Day Period Based on Upcoming 12 Month Forecast |
| Average SKUL History Units Per Period (Past Yr) | Average Units Sold Per 30 Day Period Based on Past Year’s History |
Customer Code SKUL Summary Grid
Transaction Grid
Detailed demand transaction data can be reviewed in the bottom grid in this assembly. This grid is very similar to the "Demand Transaction Review" pop-up in the Forecast Details/Forecast Summary assemblies. On the left side are fields for including or excluding individual demand transactions from consideration in future forecasting.
The Detailed Demand Transaction Grid
The fields in this grid can be customized by users to show the desired information. Details on some of the fields that are commonly included in this grid are listed below
Description of fields in the Demand Transaction Review window
| Field | Description |
| Forced Exclude | This checkbox can be ticked manually or may be applied via a mass update in the Demand Transaction Management screen. Click Save after making changes. Excluded records will not be considered in creating forecasts |
| Forced Include | The checkbox can be ticked to include a transaction that has been flagged by GAINS as an outlier. If neither the include or exclude box are checked, the calculation will by default be included n the history calculation (i.e. no need to check this box to include a transaction unless some process has been excluding this transaction) |
| Calc Outlier | This yes/no field indicates if the (optional) outlier logical processing has identified the record as an outlier (i.e., excluded from consideration in future forecasts). Refer to the GAINS Reference Manual for more information on how outliers are identified |
| Outlier Override | This drop-down menu has three fields – blank, Forced Included and Forced Excluded. The blank allows the results of the Calc Outlier field to stand, while the others force inclusion or exclusion of the record from consideration in forecasts |
| Customer Code | Code for the customer conducting the transaction |
| Customer Code Description | Description of the code for the customer conducting the transaction |
| Request Date | Requested receive date of the transaction |
| Request Qty | Quantity requested for the transaction |
| Ship Quantity | Quantity that has already been shipped for the transaction |
| Status | Status of the transaction (00 - Open, 03 - Closed, 04 - Cancelled) |
| Sale Price | Price per unit |
| Total Price | Total price of the transaction. Equal to Requested Quantity multiplied by Price. |
Inspectors
On the left of the assembly there are two sets of inspectors. The top set includes SKUL level information for which SKUL has been selected in the the SKUL Summary. These contain similar information to the inspectors in the Forecast Details screen. The bottom set of review metrics correspond to customer code specific data. Below are descriptions on each of the fields in this inspector:
| Field | Description |
| Customer Code | |
| Number of SKUs Purchased | Total count of different SKUs purchased by Customer Code (Over entire history, not just past year) |
| Requested Sum of Sales Dollars | Sum of Sales Dollars Requested |
| Shipped Sum of Sales Dollars | Sum of Sales Dollar Shipped |
| Number of Orders | Count of Unique Orders from Customer Code |
| Average Advance Notice | Average Days Between Order Create Date and Request Date |
| Lines in Time | Count of Lines Where Ship_Date <= Request Date |
| Lines in Full | Count of Lines Where Ship Qty >= Request Quantity |
Customer Code Review Metrics Inspector