Suggestion compliance
VidiStock suggests; the transaction is made in the ERP. The Planlama → Öneri Uyumu (Planning → Suggestion compliance) page shows whether each forecast run’s order and transfer suggestions were carried out in the ERP. Orders and transfers are not entered manually in VidiStock; completed ones come from the ERP connection or Import files.
Period
Section titled “Period”A suggestion looks for a match in the ERP from the day its run completed until the day of the next forecast run (both days included). The latest run’s period stays open until today. Once the next run is made the period closes, and a suggestion with no match counts as not applied.
Matching
Section titled “Matching”- Order suggestion: purchase orders opened during the period (by order date) are matched by product and warehouse. If the ERP order has no warehouse, it is spread over the product’s suggestions, filling the suggestion with the largest remaining gap first. In the company-wide (consolidated) scope the warehouse is ignored and all of the product’s orders count.
- Transfer suggestion: transfers in the period are matched by product, source and destination warehouse. A transfer to the same destination from another warehouse also counts, because it covers the destination’s need.
- Several orders or transfers can match one suggestion; each document number and quantity is listed.
Statuses
Section titled “Statuses”| Status | Condition |
|---|---|
| Pending | The period is open and there is no match yet. |
| Applied | The completed quantity is at least 90% of the suggestion. |
| Partial | The completed quantity is above zero but below 90% of the suggestion. |
| Not applied | The period has closed with no match. |
Indicators
Section titled “Indicators”- Compliance rate = the share of each suggestion that was covered (at most 100%), averaged with the suggestion’s value as weight. Transfers use quantity instead of value. Ordering more than suggested does not raise the rate.
- Outside suggestions: orders opened (value in the base currency at the order day’s rate) or transfers made during the period for products and warehouses with no suggestion. They may point to needs the plan missed or to unnecessary purchases.
- Compliance trend: order and transfer compliance rates of the last 12 runs.
Example
Section titled “Example”A run completed on 3 October and the next run on 10 October. An order of 200 units was suggested for the branch warehouse.
| In the ERP | Result |
|---|---|
| 5 October: order of 120 units to the branch | Partial (60%) |
| 8 October: order of 70 units with no warehouse | Counts towards the product’s suggestion: 190 units, Applied (95%) |
| No order until 10 October | Not applied |
Good to know
Section titled “Good to know”- Results are not stored; they are recalculated each time the page opens. An order that arrives late from the ERP also updates the status of a past run.
- If there is no completed data at all (no ERP connection and no uploaded file), compliance cannot be measured; the page says so.
- The Sipariş Önerileri (Order suggestions) page shows each row’s ERP status and order numbers, and the Stok Transferleri (Stock transfers) page shows the status of transfer suggestions.
- Transfer suggestions are stored from the runs made after this feature was added; older runs have no transfer compliance.