Kevin Schopenhouer

Below issue is dicsussed as high prio with Microsoft and it was forwarded after several discussions to the idea portal.

During production report as finished it is possibile to scan a quantiy with more then 15 digits and with some specific item cost resulting in a extensive inventory transaction. This amount of this transaction is to big for the system to calculate. This resulting in a imbalance of the general ledger. The system creates an debit transaction different then the credit transaction. which causes the imbalance.

This imbalance of the general ledger resulting in a corrupt general ledger which can not be fixed by Microsoft. Resulting in the only solution to execute a restore back in time on a go live environment. This to make sure that the system integrity is

Our proposal is that all transactions causing an inventory imbalance should be avoided at all possibile ways. Meaning a blocking error should be triggered in cases an imbalance is occuring.

When using the old masterplanning safetystock is shown as demand in the pegging of planned orders. When using planning optimization it is not visible anymore in the pegging/ net requirements why a planned proposal is created when it is based on a safetystock requirement.

A support ticket was raised but it was parked as 'as designed'

Currently within F&O there is no insight in what is the status of the forecast consumption on a demand forecast.

This would be a big improvement for the current functionality.

Currently Microsoft introduced new functionality related to multisourcing products.

When sourcing items by multiple vendors, it happens often that clients would be able to define different default order settings. Within the current solution this is not possibile.

Vendor A delivers in Tank of 591 KG

Vendor B delivers in Tank of 788 KG

Possibile idea, add vendor to the Default order settings. And a parameter that it only applies for some items.

1. PurchLineType and method CalcDimensionsSpecificPurchQty()

Other solution might be add extra fields to multisourcing policie



1. Extend multisourcing policie

Currently Microsoft introduced new functionality related to multisourcing products.

When sourcing items by multiple vendors, it happens often that clients must be able to define different default order settings. Within the current solution this is not possibile.

For example:

Vendor A delivers in Tank of 591 KG

Vendor B delivers in Tank of 788 KG

Possible idea, add vendor to the Default order settings. And a parameter that it only applies for some items.

1. PurchLineType and method CalcDimensionsSpecificPurchQty()

Other solution might be adding extra fields to multisourcing policy



1. Extend multisourcing policy

With the current logic of planning optimization there is a gap for the firming of manual created planned (batch)orders. Those will not get exploded after firming.

As the production order is created in status sheduled you would expect planning arranged the explosion of the phanom items but it did not.

From that point you can decide to 're-schedule' The production order. Only the outcome is completely different on quantity/processing time aswell secondary planned resourced. Therefore this order must be deleted and recreated via masterplanning or created manually.

This proces has a big chance of making mistakes and therefore the proposed workaround (re-run the masterplan for every manually created order is very tricky.

Idea: Always explode items of type phantom during firming the planned batch order while using planning optimization.