SLDAPICUST

Hi
I am on an ECC to XI to MDM scenario
I am not able to send from ECC to XI. This scenaio is running in QAS. I tried SLDAPICUST from ECC and I got the details of the XI DEV server. I should be ideally getting the details of the QAS.
How would I correct this so that my system will point to the correct QAS server?
Regards
Harish

Well,
RFCs:
● LCRSAPRFC
The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.
● SAPSLDAPI
The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.
Depending on your client settings, it may be necessary to log on to your Integration Server host as SAP system user with the authorization to maintain customizing tables and to release transport orders.
i dont remember i you test those RFC connection. if you run a TEST Connection for those RFC and everything is OK check whether the user PIAPPLUSER contain SAP_XI_APPL_SERV_USER role.
this issue is same as your other thread so, if you solve one of them both should be solve
Thanks

Similar Messages

RZ70 and SLDAPICUST

1.) Is it true that the tcode RZ70 tells a ABAP server which SLD to update?
2.) Is it true that the RFC connections SLDAPICUST and LCRSAPRFC tells a ABAP server which SLD to use?
3.) Is it true that in Visual Admin the service "SLD DATA SUPPLIER" the configuration of the HTTP SETTINGS tab tells the server which SLD to update AND which SLD to use?

Thank you. The reason I'm asking these questions is because I want my Solution Manager server to report to my XI server using RZ70, but I want the Solution Manager server to read the local SLD on the Solution Manager box.
1.) I set RZ70 on the Solution Manager box to point to my XI server.
2.) I created a bridge from the XI server to the Solution Manager box. This will keep the Solution Manager box up-to-date with changes in the SLD
3.) On the Solution Manager box ,the RFC connections LCRSAPRFC and SAPSLDAPI point to the Solution Manager box. I'm assuming this will force the Solution Manager server to use the local SLD.
For the Java engine running on Solution Manager I used Visual admin to set the "HTTP Settings" option in SLD Data Supplier to point to the XI server.
Is there a setting in the Java that tells it which SLD to read?

Error in Directory Cache Update

Hi,
because we changed from two SLDs (PROD & DEV) to one (DEV) we did all changes like given in note 720717.
Everything seems to run fine except the Adapter Engine - ok parts of it.
When checking the Cache-Infos in Integration Directory we get following error in Integration Server (Central Adapter Engine). What do we need to do?!
br
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.px1.sapru03, string], target element type: SAP_XIIntegrationServer)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:483)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:154)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
 at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
 at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
 at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
 at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
 at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:259)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
 at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:207)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Hi,
Hereu2019s a list of common errors/problems in SAP XI and their possible resolutions. This Guide will help you troubleshoot your integration scenarios in SAP XI/PI. This is in no way an exhaustive list. You can add your points/ideas to this list. Please feel free to post your inputs using the comments form at the end of this article.
Cache Update Problems
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment u2192 Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment u2192 Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
Routing Errors
NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
TOO_MANY_RECEIVERS_CASE_BE
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Mapping Errors
JCO_COMMUNICATION_FAILURE
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
NO_MAPPINGPROGRAM_FOUND
Ensure that mapping program exists and is activated. If it exists then update the cache.
EXCEPTION_DURING_EXECUTE
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Conversion Errors
Unable to convert the sender service XXXX to an ALE logical system
This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service u2192 Adapter Specific Identifiers. Click the button that says u2018Compare with System Landscape Directoryu2019 and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP systemu2019s partner profiles.
Errors on the outbound side
Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
Refer this article:
http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/content.htm
Refer this portal
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/pointers%2bfor%2btroubleshooting%2bportal%2bruntime%2berrors
Regards,
Suryanarayana

Can not see messages in SXMB_MONI of ECC

Hi Friends,
 Here I am facing some problem with SXMB_MONI of ECC. I am doing an XI upgrade from XI3.0 to PI 7.1.
when I am doing my interface upgrade I am unable to see messages in SXMB_MONI of ECC. As ECC is also got upgraded now BASIS is very confused about configuration.
 when I went through some blogs I came across some suggestions like configuration in SXMB_ADM. In ECC the integration engine configuration what I did is
 Role of Business System : Application System.
 Corresponding Integ. Server : dest://<HTTP DEST>
 One of my doubts:: Is <HTTP DEST> is the one which we are giving in XI/PI or the new one created for ECC. First BASIS set up <HTTP DEST> as the same one which was configured in PI. Then I went back to BASIS and tell them that ECC is having its own local Integration Engine, so we need to create <HTTP DEST> which connects to integration engine of ECC.
 Then they created one <HTTP DEST> for ECC. but when I am doing connection test, Http response is coming as 400 BAD HTTP Response :: protocol error. I have no idea why it is behaving like that.
 After when I go through some more blogs they are dealing with RFC destinations LCRSAPRFC and SAPSLDAPI. when I check it in ECC I didn't found RFC destination LCRSAPRFC but SAPSLDAPI is existing in ECC.
 more over some blogs deal with the configuration in Transaction SLDAPICUST. when I check it in ECC no configuration was done in SLDAPICUST.
 I already configured ENGINE_TYPE, IS_URL, LOGGING, LOGGING_PROPAGATION, LOGGING_SYNC under specific configuration data of SXMB_ADM of ECC.
 Please let me know what needs to be done and let me out of this confusion. As I am a PI developer I am unaware of all these configurations. expecting replies from gurus....
Regards,
DASARI

Hi Friends,
 Looking at some more blogs I got a doubt.
 Actually my scenario is File - XI - RFC.
 Now my doubt is whether we can see the messages which were going to ECC by RFC adapter ?
 Looking at a thread I got confused whether SXMB_MONI can capture messages only if they are coming from Proxy or IDOC . please clarify me.
Regards,
Dasari.

PI 7.11 sp6 system copy causes target sys to register with source

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I could not run the "wizard for post copy" since I'm on 7.11sp6. Yes, I know they "downported" it but I don't have those latest LMtools type packages. Anyway, I'm OK with that.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
RFC 399 unable to connect
I'm certain the user is NOT locked and the password is correct for PILDUSER.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
Also, now my PROD system shows the PIT system as a "non-central adapter engine".
Ughh! I'm totally stuck. I'm not sure what to do.
It's as if the PIT (PI training) system somehow is linked to PIP (PI prod). It's like PIT doesn't think he is his own box...
Any ideas? I'm resisting opening a message because this will be so hard to explain to sap support.
--NICK

Hi Nick,
We went thru the same issue. Fortunately, it was between Dev to sandbox. I stopped the dev system and changed the exchange profile parameters to sandbox hostname and brought the Dev up to fix the issue.
Prod showing as Non-Central Adapter engine :- Check your Business System in SLD and In CIM Instances in SLD, check your XI Integration server assigned to right Business System.
Note 764176 - Error in XI due to inconsistent SLD contents :- helped me come over PI post step issues.
Thanks,
Arjun

PI 7.11 sp6 system copy Exchange Profile error code: 399

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICK

Here is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException: <pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>

SRM 7.0 PO XML to PI to HTTP

Dear Experts,
My scenario is to get a PO out of SRM (which is coming over via XML) connect to PI and immediately pass that messages (without mapping) to an external HTTP destination.
Can you please help in outlining what is needed?
On our PI system we already have the SRM XI content. So in the ESR I see that we have the names spaces and the MT and Service Interface for Purchase Order Request.
I have already created a Business System for SRM and also created a Technical and Business system for our external HTTP party in the SLD.
There are 2 major problems:
1 - When sending PO out from SRM to PI - the message does not get transmitted. In SMQ2 when we look at the XML message - we see that it is reference an RFC destination that does not exist. Even when we create it in SM59 for connection to PI it still gets the same error. I assume this is configuraed somewhere in SRM but do you know where?
HTTP destination IntServer missing (system, transcation SM59)
2 - What steps are required to be configured in the Integration Builder and ESR in PI to send the XML messages as is (without transformation) from PI to the HTTP source (i.e. do I need to setup recevier agreement, sender agreements, Party, etc)
As you can see I am new and trying to work this out. This would be much appreciated!

Hi,
We had a similar interface scenario...
in this case we used proxy to populate the PO data which needs to be sent to the external vendor...
For proxy things you need some configuration settings in SRM...(even if you use the same approach...)
1. Need to configure the PI url in the tcode SLDAPICUST..
2. Need to create the http destination point out to the PI url (host/xi/engine?type=entry)
3. set the integration engine as the loc in tcode (SXMD_ADM->integration engine configuration) and provide the http entry over there..
4. Need to have two rfc destinations of type T (LCRSAPRFC..SAPSLDAPI..having the same progid as specified in PI..)
Once the configuration is done can check the same using SLDCHECK...
For more details on the above search SDN..
For passing the data as it is dont provide the mapping name in Interface determination provide the source and target message interface name as same..
need to create the receiver determination and recever agreement for the HTTP...
Gud luck
Rajesh

An SLD system has not been assigned to logical system TEC101

Hello all
We are trying to send an message RFC or IDOC from our SRM (5.0) system to the XI (7.0). But we allways get the error
"An SLD system has not been assigned to logical system TEC101". In the SLD the system is visible, sldcheck works.
Does anyone know this problem and can give me a hint how to fix this problem?
Thanks a lot
Stefan

Hi Stefan,
Is there a technical & Business System for SRM5.0 in SLD? If entry exists then confirm if the logical system name mentioned in Business System is TEC101.
If entry does not exist in SLD for SRM, then in SRM run t-code
1) SLDAPICUST .. Enter relevant details
2) RZ70 : Give XI Server details , activate and then Execute.
Once you do that you can see entry for SRM in SLD.
After that try running the schenario again.
Regards,
Sumit

** SPROXY is not working properly in Business System

Friend
My SAP Business System is having Ver 7.00. This system is already connected with our XI server. I face 2 problem when execute SPROXY tcode in this system.
1) System asks username & password for every click.
2) Whatever I have created SWCVs in IR, only SWCV names are displayed there are no objects under that.
I troubleshooted the following things.
I have run the following reports.
1) SPROX_CHECK_HTTP_COMMUNICATION - HTTP Communication is working fine.
2)SPROX_CHECK_IFR_RESPONSE - We get the response.
3)SPROX_CHECK_IFR_CONNECTION - Integration Builder connection is working properly and Data understood.
When I run the 4th report, SPROX_CHECK_IFR_ADDRESS, the data in the SPROXSET table is not shown.
Actually when I checked the data in the SPROXSET table, there is no data in that table.
Friends, how do enter data in SPROXSET table ? How to bring all the objects in SPROX under SWCVs.
Could you kindly help me to solve the above 2 issues ?
Thanks in advance.
Kind Regards,
Jegathees P.

Actually
when you run the SPROXY it does 2 things
1. can take the rep information from the table
2. can take the rep info from the exchange profile in the SLD
if you want the sproxy to take the data from the exchange profile do the following:
RFC Dest: should work fine.
LCRSAPAPI
SAPSLDAPI
SLDAPICUST should work fine?
Also in RZ70 TC you should point to the SLD.
This 2 RFC are Registered Programs, if this RFC is working then your Application system can ping to the SLD where the exchange Profile is present.
Message was edited by:
n Khan

SLD in R/3 4.6C and WebDynPro calling BAPI from EP7.0 to 4.6C

Hi,
First let's describe the landscape :
- EP7.0
- R/3 4.6C
Second, the goal : I want to do WebDynpro that will communicate with the R/3 4.6C.
To achieve that, a EP7.0 (based on NW2004s SR2 that was "upgraded" to SPS10) was recently installed.
No problem with this one. The SLD server (local server) is installed on this portal.
As there is no gateway on the portal, I took the gateway of the R/3 4.6C for the SLD server.
The ABAP system was created manually in the SLD server.
I then created the two JCo and it seemed to work fine (as least the tests were OK)
When I created a WebDynPro that I published on the portal I was able to retreive the BAPI of the R/3 server, I was able to send him my requests but I received nothing from the R/3.
I also noticed when I tried to configure SLD in the R/3 that the tcode SLDCHECK, SLDAPICUST were not present. Do you need a defined SP level to be able to run them ? Are they important for my use ?
The question is : is my configuration wrong (SLD...) or is my Java code in the WebDynpro wrong ?
TIA,
Denis.

Raghav,
The most common reason for this error is exactly what it says, you have somehow overlooked including a material/plant in a PR IM.
Go into the failed queue, find all material/plants that exist in the failed LUW. Enter these one by one into CFM5 in R/3. You should have one and only one active model for each of these materials. Inactivate all but one IM if there are multiple PR models active.
If this PR is for a STO, then you must have open active IMs for both the source and destination plant materials.
Now, you say that in SCM you cannot select the models, this means that they are not active and valid. If you can find the model in R/3, but Delta3 can't find it, it implies that there is some type of error with connectivity, perhaps in your system destination definitions. Wrong RFC connection name, wrong server id, wrong client, etc in SM59. Or, wrong logical system name. Check these on both sides.
More unlikely, but also possible, check is for inconsistencies in the IMs. In R/3, run RAPOKZFX. Regenerate your IM runtimes with RCIFIMAX.
Finally, it is possible that you have userexits that are impacting the CIF. Talk to your developers to see if any have been activated.
Best Regards,
DB49

ABAP Server Proxy: Message getting blocked in R/3 Application system

Dear All,
We have developed a FILE->XI->SAP R/3 (WAS 620) interface using ABAP Server proxies. Message gets successfully transferred to R/3 system using proxies but is getting stuck in inbound queues with green flag and message "message scheduled(commit follows)". In queue it displays status as "CPICERR" with description "connection closed(no data)". When trying to execute LUW manually from queue it throws message "Target system/gateway not active". I've checked queues they are registered properly, SLDAPICUST, SLDCHECK & Integration Engine Configuration checks are successful.
Can you please provide your valuable inputs?
Thanks and Best Regards
Prashant Rajani

Hi Stefan,
I am doing a submit to another report from ABAP proxy which inturn updates data in respective tables. Whether still commit work is required after submit?
The code was tested succesfully in Dev and in QA it started giving this problem.
Please let me know if we are missing on something.
Thanks & Regards
Prashant

RSPLAN is not working in Dialoginstance of SAP BI

Hi Experts.
After installing dialog instance for existing sap bi production systems.I could not able to open url for rsplan tcode.
In RSPLAN-->startmodeller it has to open url but in case of my dialog instance it is not working .
It's working in CI of our sap bi system.
could you please suggest me what are the prerequisites needs to be done to solve this problem.
do we need to change anything in visual admin jco rfc ,presently it is configured for specific application server of CI.
Is there anyway we can do loadbalancing for this rfc or do i need to run BI-Templete for additional Dialog instance again.
thanks&Regards
Janakiram

Hi Janakiram,
Please check the settings of SLDAPICUST trnx settings with the CI . Also check SLDCHECK trnx and check if its giving error.
Regards,
Anup

LANDSCAPE FETCH job gets cancelled

Hello Guru's,
The LANDSCAPE FETCH job gets cancelled on solution manager system due to the below mentioned error and in order to fix it
we have already applied the SAP note 1335225 but, the issue still persists.
Right now, we have come across the SAP note 1108071 which says the job will get cancelled "if you made adaptive computing
settings in SMSY and the SLD is not accessible".
can any one help me with how to check the adaptive computing settings in the header data of the system.
Also, the SLD check from system via tcode:sldcheck is sucessfull and we could access the SLD via browser. Please find the
details below.
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SAPSLDAPI_MP0
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   ashb01wa06pr.global.aes.com
port number: 59000
user       : SLDAPIUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access d
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     3
=> Check whether the SLD is running!
Immediate reponse is highly appreciated
Best Regards,
S.Viswanathan

Hello,
Could you include the Landscape_fetch error you mentioned in your message?
I think the issue is still your SLD. At the bottom of SLDCHECK it tries to retreive business systems in SLD.
If it is successfull you will see something like:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
   yoursystem1
   yoursystem2
   yoursystem3
(more...)
Your SLD check shows that it cannot retrieve systems from the SLD:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Please make sure that you have configured your SLD according to the post-installSLD setup and configuration guide. If you still have problems, follow this toubleshooting process...
http://help.sap.com/saphelp_nw70/helpdata/EN/78/20244134a56532e10000000a1550b0/frameset.htm
Best Regards.
Edited by: Phil May on Sep 2, 2009 10:31 AM

ERROR MESSAGE IN - SLDCHECK.

When i run the transaction SLDCHECK , i get the following error message.
>
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 4
=> Check whether the SLD is running!
Please let me know the importance of the customizing in transaction SLDAPICUST. ( all the parameters specified here).
should the user specified here have access to SLD?. I am asking this because i end up getting the below error message when i debug the Function module
LCR_LIST_BUSINESS_SYSTEMS from the application system
>
AbapSLDRequestHandler.getObjectServer(): User cred
entials are invalid or user is denied access
>
And below error message when i debug FM LCR_GET_BS_DETAILS in the
application system.
>
exception in SLD client: AbapSLDRequestHandler.execEnumerateInstances(): User credentials are invalid or user is denied access
>
Any help would be appreciated.

Go through this
http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Configuration/Post_Install_SLD_NW_2004s.pdf
http://help.sap.com/saphelp_nw2004s/helpdata/en/14/39084136b5f423e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/workingwithSystemLandscapeDirectory+%28SLD%29&
Regards,
Sarvesh

SPROXY not working in application system

Hello all,
I have been trying to make SPROXY work in my QAS ERP 2004 SPS23 system
for a few days now but I can not make it. I have
configured SPROXY in the past for my sandbox and DEV system with
success but I do not seem to have any luck in QAS.
My PI landscape consists of sandbox, developement, qa and production
systems. The version is PI 7.0 SPS21
My ERP landscape consists of the same 4 systems but in version 6.40 -
ERP 2004 SPS23
All non production systems use a central SLD that runs in the PI development
box (PID)
The error message I get is as follows:
When I run SPROXY in ERP QAS client 330, I get : "No connection to Integration
Builder (only local data visible)"
When I do Goto --> Integration Builder, I get the message "Integration
Builder address not maintained"
However, when I do Goto --> Connection Test, from the 4 reports I have
to run, two work and two do not work:
=>Check/maintain with report SPROX_CHECK_IFR_ADDRESS works and shows the correct address for Integration repository
=>Check with report SPROX_CHECK_HTTP_COMMUNICATION works
The other two reports
=>Check with report SPROX_CHECK_IFR_RESPONSE
==>Check with report SPROX_CHECK_IFR_CONNECTION
return: Integration builder data not undestood.
SLDCHECK runs fine: All green and invokes correct IE session with the correct SLD URL (central SLD)
SLDAPICUST shows the correct SLD (central)
SXMB_ADM --> Integration Engine Configuration shows the destination RFC
SAPIS_PIQ
which is defined in SM59 as type H and works fine
TCP RFCs LCRSAPRFC and SAPSLDAPI work
The corresponding JCos in Visual Administration look ok
I have registered the queues in SXMB_ADM and they registered ok .
The /sap/xi/engine service is active in both the application system and the PI system (QAs and PIQ)
Finally the exchange profile settings in PIQ are fine as well
com.sap.aii.connect.repository.name : piqas.finance.local
com.sap.aii.connect.repository.httpport : 50000
com.sap.aii.connect.repository.contextRoot :rep
com.sap.aii.connect.integrationbuilder.startpage.url : rep/start/index.jsp
com.sap.aii.applicationsystem.serviceuser.name: PIAPPLUSER
and the password is set.
PIAPPLUSER is service user and is not locked.
I have tested SLDCHECK in PIQ and SLDAPICUST and they look ok as well.
Any other clues? Any way I can investigate further via checking logs
and traces to find out what is wrong?
The "Data not understood" message is not helping me much in determining
what is wrong
Many thanks
Andreas

Hi Andreas,
Please go through the below blog which explains you step by step in proxy connectivity.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Naveen.

SLDAPICUST

Similar Messages

Maybe you are looking for