Skip to Content

CC re transfer issue

Hello Friends,


I uploaded CC and then Classify and then  re-classify as well.

Next step I did Re-transfer  CC to Feeder system as you can see the screen shot.

Here I am not sure whether it re-transfered or not ?

Then I went to ECC system and runt the transaction /SAPSLL/SWN_RTR_R3 without simulation. Then I got this pop up.

No update in Material master no configuration table updated. So what I am missing.

Thanks

Ravi

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 22, 2016 at 08:54 AM

    Hi Ravi,

    hope you are using the latest version of GTS 11.0, i am not aware of this version.

    i am working currently on GTS 10.1, where we use the Program : /SAPSLL/STAWN_RETRANSFER in GTS and /SAPSLL/STAWN_RETRANSFER_R3 in ECC to retransfer the Commodity Codes from GTS to ECC.

    once we run the program in ECC the data will be updated in 3 Tables : T604,T604T and MARC . once the data updated in those tables, the below screen will appear.

    but i don't know what is the issue in new Program , which you used. are you facing this issue in Production system or all your Dev, Quality also have the same issue?

    Thanks,

    Srinivas Yellampalli

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ravi,

      hope you need to debug the program in GTS as well in ECC to understand where the issue exists.

      i suggest first make sure that when you execute the program in GTS , it should update the CC data in ECC in two tables initially and when you run the Program in ECC it will upload in tables : T604,T604T and MARC.

      so, you do classification for few products and try to transfer them to ECC from GTS and then ask the Technical Consultant to check whether the data is transferring from GTS to ECC or not. if it is flowing then no issue from GTS.

      Note: Date you have to mention is the date when you did classification and also check the Legal Regulation mentioned in the Program is the correct one.

      Thanks,

      Srinivas Yellampalli