If you are new to any Iron or Steel Projects or if you like to know more about this industry, this is the magic wheel, that you should be looking for.
This gives you on the fundamentals of each process/ product as you click on them
In case if you are facing the below error , espcially in case if you are using the IS-Mill functionality or the single unit batch concept.
factor of single-unit batch Message no. MILL101.
This message is received if there is any inconsistency in the Batch specific unit of measure that has been adopted in the batch classification, Especially when you make return delivery or other cancellations if the Batch specific uom characteristics is not empty then this error will occur.
In the following section we will see the usage of this FM to create a simple Customer Independent requirement (MD81) with the variant configuration values passed on to the same.The below are the fM structure you need to work with
Note: In this structure the “common mistake” most of them do is not filling in the po_itm_no- if this is not filled then the SO will not be created with the characteristics values
|OBJ_KEY||Dynamic-This will be Material Number|
|OBJECT_GUID||Dynamic-This will be Material Number|
|`000001||`00000001||Charcteritics 1||Value 1|
|`000001||`00000001||Charcteritics 2||Value 2|
|`000001||`00000001||Charcteritics 3||Value 3|
In this post we will understand what are all the migration objects that Standard SAP is offering us as part of the Data Migration cock Pit.
In case if you have landed to this post directly do check the previous post for easy understanding.
To access the standard list kindly click here and in case if the Link is not working then do copy and post the below link in the browser.
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
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
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
What is SAP DMC ?
SAP DMC Stands for the SAP Data Migration Cockpit. SAP is Sunsetting the support of LSMW and other upload tools in the Hana Envirornment.
Earlier the Data migration was done using the LTMC. SAP offered the features of migrating or uploading the data for the S4 hana system with the predefined objects like Materail master, BOM , Routing etc.
It has options to Upload the data using files or staging tables this was available in the S4 Hana version 1909.
But From S4 Hana (OP) 2020, it is strongly bringing the SAP DMC is the only source ( Same as LTMC) but the addittional feature here is we can directly connect the ECC system to S4 Hana system through this SAP DMC and perform the required data migration.
This also provides features to do the Mapping ( Transformation) in case if there is any changes in the master data, etc if the costcenter is changed then we can provide the source vs target and which help to create the new cost center in the S4 Hana system.
The intent of this post is to bring awareness on this tool and further topics will be detailed in the subsequent Posts.
More details about this SAP DMC is available in this link https://www.sap.com/documents/2017/07/26113ac0-c47c-0010-82c7-eda71af511fa.html and also keep watching this space for more updates on this topic
Generally, when we have a system and users working in multiple time zone, consultants/businesses need to understand the below basics:
Below SAP Notes will be of quick help.
If you are working in a Variant configuration environment, then one of the best practices to transfer the VC – Master data between the Clients / Box is to use the ALE Methods.
The below list of message types can be a quick reference for Inward / Outward.
MATMAS – Material master
BOMMAT -BOMs: Material BOM
CHRMAS -Class system: Characteristics master
CLFMAS -Class system: Classification master
CLSMAS -Class system: Classes master
CNPMAS -Configuration profile
ECMMAS-Engineering Change Management
KNOMAS -Global object dependencies
UPSMAS -ALE Distribution Unit (MASTER)
VFNMAS -Variant function
VTAMAS -Structure of the variant table
VTMMAS -Contents of variant table
MATMAS -MATM -Material Master
BOMMAT -BOMM -BOMs: Material BOM
CHRMAS -CHRM -Class system: Characteristics master
CLFMAS -CLFM -Class system: Classification master
CLSMAS -CLSM -Class system: Classes master
CNPMAS -CNPM -Configuration profile
DEPNET -DEPN -DEPNET
ECMMAS -ECMM -Engineering Change Management
KNOMAS -KNOM -Global object dependencies
UPSMAS -UPSM -ALE Distribution Unit (MASTER)
VFNMAS -VFNM -Variant function
VTAMAS -VTMAM Structure of variant table
VTMMAS -Contents of variant table
You will be surprised to know that with single T.code we will be able to get the list of all reports across all modules in SAP. Watch this video to find it and also how to use it.
When we start the MRP live in S4 hana, we may notice some of the materials are not being planned by MRP live. during such instances it is good to check with the given report to find the reasons for not planned.