cancel
Showing results for 
Search instead for 
Did you mean: 

SLDCHECK

Former Member
0 Kudos

Hi guys,

When I am doing an SLDCHECK from my R/3 system then this is almost correct:

- I Do get the properties of RFC destination SAPSLDAPI

- SLD server access settings: gives me the host name, portnumber and user

But the list with Business Systems is not retrieved--> The function LCR_LIST_BUSINESS_SYSTEMS part

The properties of it's own Business system is also not retrieved.

The SLD is running fine and I have an entry for SAPSLDCUST which is the same if I look in my XI system.

How can I fix this?

Best regards,

Guido

Edited by: G. Koopmann on Feb 27, 2008 4:37 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

1) Try this -- > go to CPA Cache and refresh it.

2) Earlier similar Kind of issue Michal refered

Note 809420

This problem occurs due to business systems and the RFC call not able to receive the data about business systems.

Try to delete the recently created Business systems and re-create it. This should slove your problem

Check this URL might help in solving your problem

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm

Answers (6)

Answers (6)

Former Member
0 Kudos

Thnx guys for all the help, I solved it based on SAP Help which I got from you:

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm

The user in SLDAPICUST didn't have the role SAP_XI_APPL_SERV_USER. I don't know why but it was not there. I added the role and did my SLDCHECK and it worked!

Thnx for all the help!

Former Member
0 Kudos
aashish_sinha
Active Contributor
0 Kudos

Hi,

The function module LCR_LIST_BUSINESS_SYSTEMS called in SLDCHECK generates an unnecessarily high number of HTTP requests to the SLD server. This causes long runtimes and also uses up the number of available user sessions in the J2EE Engine. In the latter case, the logon to the J2EE Engine fails with every additional request even if the receipt data is correctly maintained correctly in transaction SLDAPICUST.

Also check out the settings for XI access modules

LCR_GET_OWN_BUSINESS_SYSTEM

LCR_LIST_BUSINESS_SYSTEMS

LCR_GET_BS_DETAILS

to the SLD programming interface, which uses an access data record with user and password. The access data record can be maintained using transaction SLDAPICUST.

Hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

nisarkhan_n
Active Contributor
0 Kudos

Check the following:

I think as you mentieond LCRSAPRFC RFC dest is working fine? SAPSLDAPI is also working fine?

if you manually execute the LCRSAPRFC is it taking much time or faster execution?

I think it is related to the cache...goto the SXI_CACHE and run the complete cache also CPA Cache.....

then run SLDCHECK.

let me know if you get any error...

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi Guido.

to correct it follow this guide (post instalation of PI)

continue form point

Creating RFC Destinations in the ABAP Environment.

http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm

Rgds

inigo_sacramento
Participant
0 Kudos

Have you defined your XI as integration server? TCODE SXMB_ADM --> Integration Engine Config

Check your RFC's type TCP/IP

AI_DIRECTORY_JCOSERVER

AI_RUNTIME_JCOSERVER

LCRSAPRFC_DXI

SAPSLDAPI

Check RFC type H

INTEGRATION_DIRECTORY_HMI. Yoy have to get a error 500.

Check users. Maybe someone is locked

Reward points if useful

Former Member
0 Kudos

check if entries are correct, using Tcode: LCRSERVADDR

Edited by: Prema Boodi on Feb 28, 2008 1:31 AM