Material and vendor transfer to GTS sytem

[Former Member]

I am using GTS 8.0. We have a very peculiar issue. Newly cretaed vendor & material doesnot get transferred to GTS. Please provide the step by step configuration settings to transfer material and vendor master to GTS using rbdmidoc.eg. change pointers activation, message type, reduced message type, Distribution model, Idoc partner profile

[Former Member · Accepted solution]

You can follow the below steps to transfer data from R/3 to GTS system

1. Activate change pointers Globally

2. Activate Change pointers for message types ( for the material types)

2. Activate Change pointers for Reduced message types

Once the above is done, it is advisable to tranfer the data for the first time using the initial upload program - Tcodes for the same are /SAPSLL/MATMAS_DIRR3 for material master records and /SAPSLL/CREMAS_DIRR3

Regards,

Jasmit

[nagarjun_kalletla · Accepted solution]

Once this setting / configuration is done.

we are running RBDMIDOC program with message type  /SAPSLL/MATMAS_SLL

Can we expect the new Materials created will also flow to GTS.

Please let me know if you have any other solution.

[Former Member · Accepted solution]

Hi,

Yes, provided you have the KEY fields of MARA added to message type.

Are you seeing something different in system behaviour? If so, please let us know.

Thanks

Dhilipan

[Former Member]

Hi, Jasmit and grus..

I like to ask another question.

We use program RBDMIDOC with message type /SAPSLL/CREMAS_SLL to send vendor information to GTS.

Job is running every hour but sometimes, we find newly created vendor not transferred to GTS.

So, we use manual transaction /SAPSLL/MATMAS_DIRR3 for material master records and /SAPSLL/CREMAS_DIRR3

as Jasmit said. That causes process stop and delay.

Do you have experience like this? and if yes, anysolution to solve this missing records? or to reduce?

[former_member215181]

In Transaction BD60, make sure that the Function Module /SAPSLL/CREMAS_DISTRIBUTE_R3 is assigned for Message Type /SAPSLL/CREMAS_SLL. And in Transaction BD52 for that Message Type, make sure that fieldname 'KEY' is assigned for table LFA1, object KRED.

If those settings are already correct, then try to check whether the Change Pointer record is not being created, or if the CP record is not being sent to GTS. To do that; for a new Vendor not received in GTS, check for a corresponding entries in tables BDCP / BDCPV.

And of course, check for log entries in GTS (System Monitoring > Transfer Logs > Business Partners), and also check in SM58 for any RFC failures.

Hope that helps.

Regards,

Dave

[Former Member]

You might want to start looking backwards from GTS.

1. Check the application logs in the GTS system. They might let you know if the data indeed arrived and error'ed out or if the

transfer itself was not successful.

2. Check if the change pointer is indeed getting generated or not.

3. Check the status of the change pointer . If the same is not getting processed, there could be an error.

In case all the above looks good, check your config for the message type and change pointer configuration.

Regards,

Jasmit