Prerequisites & Assumptions
Ensure that all tables and fields listed in the Data Model section are available.
Operation events are dependent on accurate confirmations, which are typically generated by an external Manufacturing Execution System. Verify the availability of confirmation data and a viable exchange of data between the MES and ERP (SAP).
Common OperationConfirmation issues:
Multiple confirmations for the same Operation: This occurs frequently and typically only one confirmation entry (single row in table AFRU) will contain the relevant information about that Operation (i.e. the time taken, scrap quantity, yield, etc.). The OperationConfirmation transformation already groups confirmations and brings relevant details on the Operation level, but it is important to validate with your customer whether these confirmations and their details are correct.
Sequences of operations with repeating confirmation times: For some systems / customers there might be a transaction code that identifies where all confirmation times are the same for specific routings or materials. It is important to exclude these from throughput time calculations, as they indicate the cycle time for all grouped operations.
Production Orders are assumed to contain only one item per order. This is the conventional set up in SAP. Execute the following query in Data Integration in your data connection schema to confirm the existence of additional items per order: SELECT DISTINCT “POSNR”, COUNT(*) FROM “AFPO” GROUP BY 1. If there are order item numbers apart from ‘0001’, confirm with your customer whether these are valid. Order item number ‘0001’ is filtered throughout the data model and Applications, so if these are used then the filters need to be removed.
Operations and Work Centers are defined as N Operations to 1 Work Center. This is an assumption that is broadly applicable, however it is not enforced in SAP ECC and it is certainly possible for a single Operation to span multiple Work Centers. Verify this assumption with your customer and update the object relationship if it is indeed an N:M relationship.
There are three kinds of scrap recorded in SAP: Component, Assembly, and Operation scrap. The “Total Scrap Quantity” on the Production Order should reflect the scrap value regardless of which scrap is used. Please validate what kind of scrap is used anyways, as there is no clear indicator of which “Planned Scrap” should be considered between the three, and the methods for recording actual scrap may vary.