We are in the process of deep-diving the design based on the client's requirements for a sales management system, and are considering how to reflect the following requirements in the design of tables and other aspects of the system.
I may not have a good understanding of SAP to begin with, so please forgive me if this is an out of line question.
The basic perspective of the question is about the data model for handling inventory (how to have data).
In particular, I am interested in how SAP is designed to handle the following aspects of inventory.
* For example, if we want to calculate the forecasted inventory number of product X at a certain future date, we need to aggregate the data model of each of these processes across all the processes. Data model design for such a case
* Continuing from the above, for example, 100 units were ordered in the PO, but only 60 shipping instructions were issued in the communication with the vendor, but 100 units were eventually received (40 of them were delivered after many years of unanimity, although no shipping instruction slips were made for them.
However, the receiving process was the same number as the PO (100 units)). How rigorously is the system designed for such common operational errors (?)? Especially in the case of this example, if shipping instructions are used in the aggregate to forecast inventory, etc., it is likely that unintended forecasted inventory numbers will be aggregated.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.