LCR_GET_OWN_BUSINESS_SYSTEM - LD_ERROR

[Former Member]

HI

IN SXI_CACHE I AM GETTING THE ERROR

LCR_GET_OWN_BUSINESS_SYSTEM - LD_ERROR AND NO FILE IS PICKED.

REGARDS

VIJU

[Former Member]

Hi ,

Go to TCODE SXMB_ADM and Click on

Integration Engine Configuration

Check whether Role of Business system is Integration Server or not ? if it' s not

Go to Edit and Change Global Configuration data

then select and save it as Integration server.

[aashish_sinha]

Hi,

try executing.

SAI_CACHE_REFRESH

And once that completes..try scheduling ur automatic...sxi_cache

also check user priveleges for user who does manual sxi_cache and for user who does background..........

why do you need to run this program......this must run automatically........without being scheduled when any change is made in ir/id.

Also check at your exchange profile about some error, it is possible that there is some mismatch or some error is coming lets c.

Regards

Aashish Sinha

PS : reward points if helpful

[former_member189354]

Hi,

This is due to one of service user is locked. Try to run the report

RSUSR006 in SE38 to get the details of which service is locked.

Regards,

Rao.Mallikarjuna

[Former Member]

HI

Check for the following things

1) if every thing is green when u key in T coce - SLDCHECK

2) If the correct details are maintained in tcode SLDAPICUST.

3) check if the business system is present in the SLD. if not create one and try the Tcode SLDCHECK again

Regards

[nisarkhan_n]

The SLDCHECK is not working on the Business system which is pointing in the SLD...check the TC SLDAPICUST in R/3 it is pointing to right SLD on XI.

[manish_bhalla2]

This error means that the system is not able to recognise it's own Business System. Please check the config of the business system in the SLD.

Regards

Manish

[Former Member]

hi,

this means that your sld connection may not be working

check transaction sldcheck in XI

and also transaction sldapicust (if correct password is maintained)

Regards

R.Ragu

[Former Member]

this error occur when the client isn`t a Integration server. try in another client that is integration server