During the Inspection lot generation especially the 03 lots are not getting generated and below message are noticed:
Inspection lot not created automatically via transaction CO01/CO02
Warning message CO548 raised in production order release
Production order has status ILNC – Inspection lot not created
Warning raised in production order release – ‘Material &1: automatic generation of inspection lot failed’
The below message is displayed:
Material XXXXXXXXX: automatic generation of inspection lot failed
Message no. CO548
Diagnosis
The system tried to create an inspection lot, but failed.
System Response
Processing is continued without creating an inspection lot.
Procedure
Check, whether the quality inspection data is maintained in the material master.
When you have maintained all the necessary data, you can also create the inspection lot in a production order / process order at a later date by calling up the screen ‘main header’ again.
⚡This APP helps to get the information about the every MRP run that is complete in the System. ⚡This has a status for us to track the progress of the MRP Run – Finished or In-Progress ⚡Shows a table of all the MRP runs which have been triggered as per the filter applied ⚡There are multiple filter available to find the completed MRP Jobs ⚡It gives the detail in the Information and settings on the details given during the MRP RUN ⚡It also gives the details of the Processed Materials and the duration in the seconds ⚡The Low level Code steps , Provides detailed information about the low-level code and type of MRP step including the number of materials planned per low-level code. It gives details about how many orders were created or deleted and how much time was required for each step. ⚡The All live MRP steps Provides detailed information about each individual step performed in MRP live including how many materials were planned in this step, how many orders were created or deleted and how much time was required for each step. ⚡For each step there are multiple key figures related to the steps, all these are detailed to analyze the performance of the MRP run in the system
➡️Do leave a comment if you are using this Display Key figures app – Effectively !!
⚡In SAP Materials may appear in several products and in several production levels of a product.
⚡The low-level code represents the lowest level of usage of a material within all product structures.
⚡Key Points on Low Level Code:
📍Purpose: The low-level code ensures materials are planned in the correct order, respecting dependencies.
📍MRP Run: During MRP runs, materials are planned starting from the lowest level code to the highest.
📍Hierarchy: Lower-level codes (higher numbers) indicate materials used in higher-level assemblies or subassemblies.
📍Automation: The system sets the low-level code automatically based on the BOM structure.
⚡In the SAP material master record, each material is allocated one low-level code which is determined by the bill of material management program and automatically updated in the MARA Table.
⚡You can also display the low-level code in the material master in the information Icon
There are few new BOM Transactions in S4 Hana (onPrem) as listed below
CS11H Display BOM level by level-SAP HANA
CS12H Display multilevel BOM – SAP HANA
CS13H Display Summarized BOM – SAP HANA
These Transactions use the CS_BOM_EXPL_MAT_V2_HANA and not the classical Function module. SAP Has done Time consumption between classical and S4 Hana and concludes When the Data set or the complexity of the BOM is more then only the Improved Performance can be noticed.
Curious about the details? Dive into the comprehensive time comparison study at https://me.sap.com/notes/0002469718
If you’ve had hands-on experience with these transactions or the function module, I would love to hear your insights! Drop a comment below and share your thoughts
Once when you open the link then , this will provide you all the information.
As you enter the migration object , 1st you need to apply the filter in the top portion for the version and the language. As SAP is continously releasing new objects in subsequent releases , you need to ensure which exact version you are working on.
Also Note the SAP DMC has been introduced only from 1909 so make sure you are on version above 1909 to use this DMC features.
Once you have selected the correct Version then you will see the list of the all the migration objects .. Here you can filter with the migration object and you can also filter based on the Object type- if it is master data or the transaction data. The important attention is to be given to the available migration approach if it can be done through the File/Staging table or direct transfer. Also note DMC is widely used on ERP / EWM / AFS so kindly make sure you are checking the releavant application here. Filter can also be applied on the components.
With this information provided now you will be able to identify the migratoin object with approach. This should help you to plan your data migration approach of the Project.
Do leave your comments/ query.As we are continiously learning i will update if there is any correction or any topics to be covered.
In the Previous post , we saw about the SAP DMC introduction, In this post we will see the pre-requisities for migrating the data from the existing ECC System.
Do kindly review the previous post before you start on this Post.
There are many SAP projects which are now on the verse of migration. And SAP DMC till 1909 has offered only the below methods for migration
1)Transfer data using files
Download template file for relevant migration object
Populate file with relevant business data
Upload file to the SAP S/4HANA migration cockpit
2)Transfer data using Staging Tables
Staging Tables are created automatically (in an SAP HANA DB schema)
Populate Staging Tables with business data
Transfer data from Staging Tables to target SAP S/4HANA system
SAP Has provided this Transfer data directly from SAP System (new with SAP S/4HANA 1909).
Transfer data from SAP ERP source system to target SAP S/4HANA system
Access source system through RFC connection
Supports data migration scenarios from other applications for example, from SAP Apparel and Footwear (SAP AFS) to SAP S/4 Fashionand Vertical Business, SAP Extended WarehouseManagement (SAP EWM) to Decentralized EWM
You want to migrate data from an SAP ECC 6.0 system or an to an SAP S/4HANA On-Premise system using Migration Cockpit,then one of the below Prerequisitie is to have DMIS installed in the ECC system.
The Below notes gives detailed information of the Complete Pre-Requisites.
2973957 – SAP S/4HANA Migration Cockpit: Composite Note for Transfer Data Directly from SAP System – SAP ERP or SAP AFS to SAP S/4HANA