Benjamin Eber

Hello everybody,

I suggest a improved net requirement screen:

• View of all items, not only 1 item
• quick filters and functions to filter on specific transactions, like demand forecast, sales order etc.
• Functionality to include/exclude specific transaction types from calculation. For example only include purchase orders, but not planned purchase orders. Or even more specific, confirmed purchase orders.
• It would be helpful to have the historical demand/transactions available in this screen too. So you can compare future demand with historical demand. Historical demand could be summarized and displayed using the period templates.

It would be very nice if a functionality is added to show the demand coming from demand forecast, even if the forecast is on a higher level. E.g.: Forecast for sales item is exploded into 5 levels. On level 5 you have the raw material that you have to purchase. It would be great if the forecast demand is exploded and displayed on every level.

I am looking forward to your feedback.

Best regards,

Ben

We are looking for a possibility to setup a “default description” (General Ledger 🡪 Ledger Setup 🡪 Default description)

for journal entries of cost invoices (directly received invoices from vendors w/o PO-number) if the description field remains empty.

Hi everybody,

we are looking for a possibility to setup a “default description” (General Ledger à Ledger Setup à Default description)

for journal entries of cost invoices (directly received invoices from vendors w/o PO-number) if the description field remains empty.

Best regards,

Benjamin

Hi all,

we use product variants with versions. We need a feature that helps us consume on-hand inventory of older versions, before consuming and/or planning the new version.

Example: We have a bom with component ABC001. ABC001 has the version 002. Our bom already has the new version 003, but we want to make sure that we consume the older version 002.

With planning optimization there is a feature "Item substitution for bill of materials in Planning optimization". The problem is, that we have to put the priority to the older version. Master planning then makes sure that production use the older on-hand inventory. That is great.

But.... with prioritizing the older version in the bill of material, master planning creates planned orders for the old version.

So what we need is a feature that helps us consume the old version, but won´t create planned orders for the old version.

Unfortunately there is no possibility to switch the version of the item of a planned purchase order. If we block purchasing the old version and manually create purchase orders for the new version, net requirement does not show any pegging demand.