Migration Cockpit in party creation and maintenance of party characteristics.
The following operations were carried out to create a batch of material on the Migration Cockpit screen and to maintain party characteristics.
One of the reasons for doing this in the migration cockpit is; due to the fact that I want to form a party for the same or more than one material and quickly fill the characteristic areas of the party.
In order to be able to perform the following operations, batch numbering must be defined as external in the system.
Access to the following migration cockpit with the LTMC t-code from the SAP GUI screen.
The following steps are followed to create a batch of material and to fill in the party characteristic data.
There are Batch (if Batch is unique at material level) from the Migration Objects field. To start the process, the document is selected and opened.
The order of the works to be done is as follows.
The Excel template is downloaded and fields on excel are populated as follows.
In the Batch Basic Data table, the material number, batch number, production date, expiry date, and batch class fields are populated.
The classification field has three input fields (characteristic, numerical and currency) according to the data type.
I have filled the relevant field from the Classification Pane tab because the preformed party characteristic is Char.
After these fields are filled, the following data is entered at the production level.
Excel After being saved, Migration is uploaded to the Cockpit.
After the excel template is loaded, respectively used “Activate” and “Start Transfer” button.
Then the data is uploaded to the system.
Process Task button is pressed after you select all to match values.
Or it can be done in manual matching by entering the values from the name field.
The Description field indicates whether there is an incorrect or missing data entry. If any, deficiencies are eliminated and the process is continued.
If there is no problem in step 4 of the process (Execute Import), press the end button. Then check whether there is data entry on the SAP GUI screen.
In order to check whether the transactions made with the Migration cockpit are also in the SAP GUI, the material and batch number used in the excel are entered into the corresponding fields in the MSC2N transaction code.
The data that is filled in the Batch Basic Data tab in Excel seems to have arrived here.
The classification data comes as follows. This field fills with the reference from Classification tab in excel.
With the Migration Cockpit, batches of materials can be created quickly and easily, and the party characteristics fields can be filled.
Hopefully, this blog will be helpful for everyone
Orhan Akman
Okumaya devam et...
The following operations were carried out to create a batch of material on the Migration Cockpit screen and to maintain party characteristics.
One of the reasons for doing this in the migration cockpit is; due to the fact that I want to form a party for the same or more than one material and quickly fill the characteristic areas of the party.
In order to be able to perform the following operations, batch numbering must be defined as external in the system.
Access to the following migration cockpit with the LTMC t-code from the SAP GUI screen.
The following steps are followed to create a batch of material and to fill in the party characteristic data.
There are Batch (if Batch is unique at material level) from the Migration Objects field. To start the process, the document is selected and opened.
The order of the works to be done is as follows.
The Excel template is downloaded and fields on excel are populated as follows.
In the Batch Basic Data table, the material number, batch number, production date, expiry date, and batch class fields are populated.
The classification field has three input fields (characteristic, numerical and currency) according to the data type.
I have filled the relevant field from the Classification Pane tab because the preformed party characteristic is Char.
After these fields are filled, the following data is entered at the production level.
Excel After being saved, Migration is uploaded to the Cockpit.
After the excel template is loaded, respectively used “Activate” and “Start Transfer” button.
Then the data is uploaded to the system.
Process Task button is pressed after you select all to match values.
Or it can be done in manual matching by entering the values from the name field.
The Description field indicates whether there is an incorrect or missing data entry. If any, deficiencies are eliminated and the process is continued.
If there is no problem in step 4 of the process (Execute Import), press the end button. Then check whether there is data entry on the SAP GUI screen.
In order to check whether the transactions made with the Migration cockpit are also in the SAP GUI, the material and batch number used in the excel are entered into the corresponding fields in the MSC2N transaction code.
The data that is filled in the Batch Basic Data tab in Excel seems to have arrived here.
The classification data comes as follows. This field fills with the reference from Classification tab in excel.
With the Migration Cockpit, batches of materials can be created quickly and easily, and the party characteristics fields can be filled.
Hopefully, this blog will be helpful for everyone
Orhan Akman
Okumaya devam et...