Changed business Partner not passing to GTS

[Former Member]

We are facing problems when trying to manually transfer a certain SAP customer master record (ICXXXX) from ECC to GTS using t-code /SAPSLL/DEBMAS_DIRR3 we get the error message

Of 1 selected partner(s), 0 were processed successfully

Message no. /SAPSLL/PLUGINR3111

Diagnosis

Not all partner masters have been processed successfully.

Procedure

You can access the process protocol in the Legal Service system. This protocol contains more information concerning the type of error that has occurred.

When our batch job runs for RBDMIDOC for /SAPSLL/DEBMAS/SLL the job logs states "RFC error (this object is not consistent)"

The log does not give any information (t-code /SAPSLL/PARTNER_APPL) even after changing /SAPSLL/TCOPAO to have GN_TST (General: Full Log) for Business Partner, sub-objects /SAPSLL/BP_DISTR and /SAPSLL/PARMA.

It appears to be an issue with this specific customer master. I have created a new customer master ((ICXXXXA) that appears to be identical to the origional one and that one passes to GTS without issue.

Any thoughts on where else to look?

[former_member284694]

Hello Vicky,

Go to GTS Client

Define a group of Logical system for Feeder & GTS via path SPRO --> SAP GTS --> System Communication --> Define Group of Logical Systems

Assign the Above group to Logical System via path SPRO --> SAP GTS --> System Communication --> Assign Logical System group to Logical System

The above configuration will resolve the issues.

Thanks & Regards

Rahul

[Former Member]

Hi,

As mentioned above, this seems like existing entry in pointer table.

After you delete Business partners in GTS with BUPA_DEL transaction, also execute report /SAPSLL/BP_DATA_CLEANUP to clean GTS specific tables.

Regards,

Branio

[Former Member]

Hi Branio & Eoin,

with continuation to above, i also have similar issue and i did above steps. However, even after executing the program, the link in the mapping table /SAPSLL/PNTBP is still there. Can you please help?

Regards

Sujay

[Former Member]

Hi Sujay,

I am sure you would have done this already. but just wanted to confirm.. Did you remove the test run flag in BUPA_DEL.

And did you get the information that partner has been deleted?

The above steps suggested should work. Can you please check once.

Regards

Dhilipan

[Former Member]

Hi Dhilipan,

Thank you for your reply.

I did not run the BUPA_DEL transaction. The BP was there 2 weeks back when we first screened order. However, now, same BP does not exist in GTS when searched in BP transaction, but mapping exist in

/SAPSLL/PNTBP table. So, i ran /SAPSLL/BP_DATA_CLEANUP program for that BP, and i got below result.

Business partner 123456 processed successfully

Delete SAP GTS Data for Business Partners

Business Partners       Remarks                                         Table Name

123456                  Archive the listed objects manually         /SAPSLL/CORPAR

123456                  Archive the listed objects manually         /SAPSLL/SPLAUD

Regards

Sujay

[Former Member]

Hi Sujay,

If this inconsistency is for single case, may be you can try removing the entries from /sapsll/pntbp in debug mode.

Regards

Dhilipan

[Former Member]

Hi Vicky,

Business partners may have been deleted on GTS side but their corresponding entries in mapping table /SAPSLL/PNTBP still exist. Therefore new business partners created in ECC with the same data cannot be transferred to GTS and this results

in the /SAPSLL/PLUGINR3111 message when using /SAPSLL/DEBMAS_DIRR3.

Check table /SAPSLL/PNTBP on GTS side and let me know the result.

Best Regards,

Eoin

[former_member215181]

Hi Vicki,

You appear to have two separate problems here:

1. No transfer of specific customer with Transaction /SAPSLL/DEBMAS_DIRR3.

2. No transfer of changed customers with RBDMIDOC.

For problem 1; set a break-point in Function Module /SAPSLL/DEBMAS_MASS_R3 at line 50. When the code stops, check the contents of table IT_KNA1. If there is an entry for your customer, then the problem is going to be in GTS, otherwise the problem is in the feeder system. Let's take it from there.

For problem 2; in Transaction BD60, please check that Function Module /SAPSLL/DEBMAS_DISTRIBUTE_R3 is assigned for Message Type /SAPSLL/DEBMAS_SLL.

Let us know how you get on with those checks, and I'm sure we can provide further guidance.

Regards,

Dave