Financial Management Blogs by Members
Dive into a treasure trove of SAP financial management wisdom shared by a vibrant community of bloggers. Submit a blog post of your own to share knowledge.
Showing results for 
Search instead for 
Did you mean: 

Hello all.

Many a time while Transferring Materials to  GTS   not all materials  get successfully transferred / processed.

These transfers may be using  the  Intial Transfer  of  Material Master or using change pointers  via RDMIDOC.

In this document, I  attempt to  address one such Unit Conversion issue.  This issue has been asked in  forums  multiple times, hence creating this document to share our experience.

We are doing the initial transfer of material master  using transaction code /SAPSLL/MATMAS_DIRR3  (program: /SAPSLL/MATMAS_DISTRIBUTE_R3)

In such cases, where  all materials are not transfered,  the message "Of X selected material(s), Y were processed successfully" is displayed.

To identify the reason / error,  run transaction code SLG1  in GTS

Double Click on the appropriate log to  display all the messages.

Deselect the  Information (Green) and  Warning (Yellow) Buttons so that only error messages are displayed

This is particularly  useful if you are transferring a large number of materials, or the number of messages are huge ( for eg: a lot of warning messages)

As can be seen in the above screenshot,  the error is in unit Conversion.

Conversion error in module API6850_HDR_PROD_MAP, field API6850_HDR-WEIGHTUNIT_ISO,  value <Unit>

The  unit  is missing in GTS, the entry can be maintained in Transaction Code CUNI.

The same can be accessed in SPRO ->  SAP Netweaver -> General Settings ->  Check Units of Measurement.

If it is issue with a particular unit then it can be resolved by simply maintianing the same in the above path.

However if Multiple units are going to be used in Live System, then it becomes imperative to ensure that all those units are also present  in GTS PRD.

To ensure this the easiest method  is to adjust  GTS  tables with ECC tables. 

In GTS open the transaction Code CUNI.

The Dimensions and ISO Codes can be easily synced between GTS and ECC using the Adjust Feature.

However for Units of Measurement, you will have to create a transport Request.

To Sync Dimensions,   open it  and  then select  Utilties-> Adjust.

Select a RFC Connection to  ECC System.

Note: SAP   provides such  tables fully filled in 000 Client.  So  you can sync both ECC and GTS to  your 000 Client in the  begining.

In the Filter settings, Select  Different and only in Compare Client. This will display only the missing entries.

You can select all the displayed entries  by going to EDIT -> Select All,

Then clicking  on Adjust  will show you entries one by one.

You can chose to either  Copy  or Delete the entry , or  to copy or Delete  individual fields in the entry, in which you will have to select the field.

There is also an option to copy all  the entries at once,

On saving all the missing entries are updated in  respective Tables in the logon Client (GTS client in our case).

The above exercise can also be done using Sm30  and the views: V_T006D for Dimensions and  V_T006I  for ISO Codes.

However the same sync cannot be done directly  for Units of Measurement.

The workaround we used was to  include all the entries of  Units of Measurement in ECC in  a transport request and  Import that TR into GTS system.

Open each Dimension in  Units of Measurement and  select all entries and Include them in a transport request by clicking on transport Button.

The TR can be placed into the GTS  import Queue with help of Basis.

This ensures that Units are in sync in both GTS and ECC.

This ensures that there will be no unit conversion issue during  Material master transfer (atleast due to this cause).

Do share  your comments and suggestions if  you have faced similar issues.

Looking forward to update this document with other  issues we faced in Initial transfer of Master Data.

Top kudoed authors