Integrating with Middleware by ABAP Proxy.

Hi Guys,
i am created abap proxy in CRM 2007 by calling Wizard.Now after creation of proxy a class is generated with its method PROCESS.then did some coding in extract program for the requirement and used the method of the created class.
        Now the problem is after successful execution of the exraction program nothing is appearing in middleware.
            i couldn't understand why it's happening?Please suggest me anything i am missing or anything more i need to do.
     Good solution will be rewarded.
Thanks
snehasish Das

Hi Stefan,
in response to your questions:
What exactly is the mapping error?
In transaction SXMB_MONI I have the following error:
> A semi colon character was expected. Error processing resource 'file:///D:/Documents and Settings/Administrator/Local Setti...
If I test my mapping with the xml message returned by SAP (via abap proxy) I have the following parsing error:
>...Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity Reference must end on ;(:main:, row:2, col:26482)
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity Reference must end on ;(:main:, row:2, col:26482)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
Root Cause:
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity Reference must end on ;(:main:, row:2, col:26482)(:main:, row=2, col=26482) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity Reference must end on ;(:main:, row:2, col:26482) ...
> For instance, in the xml message, in short_text I have a & and not the escape:
<SHORT_TEXT>WHISKY J&B RARE 70CL</SHORT_TEXT>
The same example with escape
<SHORT_TEXT>WHISKY J& amp ;B RARE 70CL</SHORT_TEXT>
What version has the application system where the proxy is running?
Component SW -
Release----Support Package
SAP_BASIS--620--SAPKB62043
SAP_ABA -
620----SAPKA62043
SAP_APPL -
470----SAPKH47021
SAP_HR--470--SAPKE47017
Regards

Similar Messages

Using of Integration Scenario in a Abap Proxy to JDBC receiver synchronous

Hi ,
Can any one help me out how to go about for creating Integraion scenario in ESR as i'm new to the use of Integration scenario..
its an Abap proxy to Jdbc synchronous scenario... kindly help in this regards.

Hi Indudhar,
Right click on the namespace where you want to create the IS and say new, Select process integration scenario option, give a suitable name and say OK.
In the Component View section right click on the first grey column and Insert a sender Application component. Enter ur product and the software component version. Like wise in the next grey column enter the target Application component.
Now go to the top level menu and click on view and select grid.
Now right click on each App. component and insert the created actions. If the scenario is sync then the actions will be side by side otherwise the target one will be in the next grid of the target app. component.
After entering the actions click on the source action then press shift and click on the target action, right click and choose create connection between the two actions.
Fill in the info and then save.
Regards,
Anshul

Sliver light integration with web dynpro abap

Hi All,
I was trying to integrate silverlight with web dynpro. Does any one has any document to start with..??
Where can i design silverlight application to upload in web dynpro..??
Thanks and Regards,
Vishesh,

Hi,
We faced a similar problem with BSPs and had to change the definition of the area link type entry.
I am assuming you have set the area link type to WebDynpro for ABAP and the resource is calling an Iview/page that has the WD ABAP application configured.
To get around the error, change the Area Link type to Calls a Portal page and make sure the resource calls an Iview/Page that has the WD ABAP application configured.

Integration with middleware

Hello
Can anyone help me with information about how integrate Wonderware Software Inbatch with SAP ERP.
Any experience?.
Any consultant in Barcelona?
Thanks.

Hi Dario
I am gathering information on possible developments. XMII not know beyond what I have read on the net. I've seen, you should install SAP NetWeaver to provide xMII.
I know that I can not get to make SAP NetWeaver, and depending on that input, if the ROI to justify the investment.
Nor do I know the steps to follow, whether we should hire a new server, which means that the approximate cost in the contract and maintenance ...
Thanks

Office (Open or MS) integration with Webdynpro for ABAP

Hi Guys,
I want to ask:
- how may I read an Excel file (contains a few worksheets) into internal table type string, so I can manipulate what user has input in the file ?
I know it can be done by converting the Excel file into XML file and read the file.
The thing is, I don't want to have go by using XML file.
Is it possible to be done ?
Thanks a lot,
Tony

Hi Tony,
Am not so sure if this requirement is 100% feasible. But you can check out the
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/d1/af8841349e1909e10000000a155106/frameset.htm">Office Controls</a> in WDA.
Regards
Raja Sekhar

PI 7.0 ABAP Proxy Wrong Namespace after Client copy

Hello,
i am looking for an PI expert because we have some problems with a standard ABAP proxy interface.
We use the FSCM Module and we send Credit Commitment Notification from a SAP ECC 6.0 to PI 7.0.
We use the Interface CreditCommitmentNotification_Out and it works fine on the Development System (D46). But on the integration system (Q46) it doesn't work. The Q46 is build up from our production system (P46) by a system/client copy.
We get the error:
The payload include a wrong namespace for the proxy interface.
wrong: xmlns:prx="urn:sap.com:proxy:P46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
correct: xmlns:prx="urn:sap.com:proxy:Q46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
I dont know why we get the wrong namespace. I check the transaction SICF, SPROXY and SXMB_ADM and compare it with the customizing on our development system. I didnt find any gap.
Please help me if you have some ideas what is wrong on our system.
Regards
Jürgen 8-))

Hi,
We experience the same problem after an upgrade from ECC 5.0 to 6.0
How did you solve this?
Ron

Testing a abap proxy

Hi,
can anyone let me know how to test abap proxy?
regards,
somu

HI
DEBUGGING ABAP PROXIES
https://weblogs.sdn.sap.com/pub/wlg/4098--Debugging [original link is broken] [original link is broken] [original link is broken]
TESTING ABAP PROXY
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
ABAP Proxies:
https://weblogs.sdn.sap.com/pub/wlg/2828--Integration [original link is broken] [original link is broken] [original link is broken] Builders through proxy server
https://weblogs.sdn.sap.com/pub/wlg/4224---EOIO [original link is broken] [original link is broken] [original link is broken] in ABAP Proxies
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachmentsRFC or ABAP Proxy ?ABAP Proxies with attachments
https://weblogs.sdn.sap.com/pub/wlg/5447--How [original link is broken] [original link is broken] [original link is broken] to raise alerts from ABAP Proxy
https://weblogs.sdn.sap.com/pub/wlg/4100--Smarter [original link is broken] [original link is broken] [original link is broken] Approach for coding ABAP Proxies
regards
Kishore

How Abap proxy works?

Hi friends,
Can anybody explain me that how actually ABAP proxy works(in both cases clent and server proxy). when shuld we go for proxy.And how proxy seprates business application from technical infrastructure?
If u have any presentation or document on ABAP proxies ,plz send me
Thanks in advance
Shweta

Hi
Adapters are part of the Adapter Framework. Adapters provide the technical connectivity to enable the integration of SAP and non-SAP applications through XIs Integration Engine.Again, Adapters are used for connectivity from and to external systems with XI that cannot communicate via proxies.Adapters are only required in SAP systems older than 6.20 and external systems.
Systems based on 6.20or higher can communicate directly with proxies.
Proxies
The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages.
Proxies are generated from Message Interface in IR.
The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with. The Proxy Runtime currently has the following components available: 1. ABAP Proxy Runtime Communication using XI or Web Services a. Web Service Runtime 2. Java Proxy Runtime Communication using XI (J2EE) The objects that the Proxy Runtime then controls are created via Proxy Generation, for both ABAP and Java. In the following sections a client proxy is used by an application to send messages outside of the system it resides in (normally to the IS in this context). Conversely, a server proxy is used by an application to receive messages from sources outside itself (again, normally the IS in this context).
Proxies are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions. You can use proxies for systems with WAS >=6.20
XI will communicate in native language with SAP systems via proxies. Proxies uses XML - SOAP based communication for both ABAP and Java Proxies.
mainly we go for proxies for adapters less communicaton there
Client Proxy: Proxies created out of Outbound message Interfaces.Here XI is receiving some information and is
acting as a client.
Server Proxy : Proxies created out of Inbound message Interfaces.Here XI sends the information to some other system acting as the Server.
we can create the ABAP proxy in ABAP workbench.
Use
Using ABAP the proxy generation function you can generate ABAP proxy objects to an SAP system from an interface description in the SAP Exchange Infrastructure Integration Repository.
Prerequisites
ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.
The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 u2013 see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
How to Activate Proxy.
How do you activate ABAP Proxies?
ABAP Server Proxies (Inbound Proxy)
ABAP Server Proxies
OutBound Proxy (Client Proxy)
Smarter Approach for coding ABAP Proxies
ABAP Proxies in XI(Client Proxy)
File to R/3 via ABAP Proxy with good example
File to R/3 via ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
go thru the weblog How do you activate ABAP Proxies? which explains how to activate proxies
Check this for Use Of Proxies
Choose the Right Adapter to integrate with SAP systems
Hope this is useful and clears your doubts
Thanks
Saiyog

PCK XI adapter - ABAP Proxy to File Scenario How to?

Hi there,
We want to implement the following sceanrio; SAP ABAP outbound proxy to Flat-File scenario. A (sender) SAP system will trigger an outbound proxy which will send outbound data to a (receiver)file system via the PCK and Central Integration Server.
SAP (ABAP proxy) -> PCK-> XI -> File System
My question is; The PCK documentation suggests that the XI adapter included in the PCK can only be used to send/forward messages to the central integration server.
Does that means that one cannot use the same XI adapter on the PCK to redirect ABAP proxy messages to the Integration server?
Thanks,
Roberto

The PCK cannot be used as a replacement for XI Integration server. PCK is only a type of adapter engine that can run independantly. It is intended for partners who cannot use XI server. So PCK can not in itself execute interfaces. It can just forward all the messages received to the XI Integration server. PCK can only run your sender or receiver adapter all the mappings can only be executed on the integration server. So PCK just converts from the native format to XI format and forwards to the Integration Server.
Hope that carifies your question .
Thanks,
Kalyan Musunuri

ABAP Proxy not generate in QAS

Hi All,
I´m with problem in Abap Proxy objects, I developer and transported to QAS environment but has not generate in QAS.
I checked this objects in environment QAS and all were transported.
When I go to transaction SPROXY, it´s with not generate.
Can someone help me?
tks

Hi,
probably your developer forgot.... a few things while developing the proxy
they are mentioned here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/content.htm
Regards,
Michal Krawczyk

Timeout Error in Call Transaction on Asynchronous Abap Proxy

Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

Bapi call in abap proxy reaching dialog timeout in async scenario

Hi all,
We have an XI interface to create sales orders. Legacy app sends a soap message async to XI with a group of orders. XI sends this group of orders to an Abap proxy async on ECC side. Into this Abap proxy we have a loop to process each order received in the group with BAPI_SALESORDER_CREATEFROMDAT2. Ending the loop, abap proxy start another async process to send the response to XI with an outbound abap proxy, and the response is redirected by XI to Legacy app.
The problem is, this group of orders can have two or two thousand orders... so, the async process guarantee that no timeout limit will be reached. This is working for the whole process. But when this BAPI is creating an order, the time out of BAPIs execution seems to be the same as the timeout of dialog processes (now set to 10 minutes). This is our problem. Some orders spend more than 10 minutes to process (orders with five hundreds items, for example)... when this occurs, BAPI throws a time out reached error and the async process stops on the inbound queue with status sysfail.
We are now trying to understand why this timeout is been triggered by the BAPI. As it is running into an Async process, it should execute without any kind of timeout limits...
If anybody has any idea, please, help us.
Thank you.
regards.
roberti

May be I was not so clear... the total spent time in the process can be many many hours, days, etc... no timeout is reached. I can post 10.000 orders, no timeout is reached. The problem is that if the processing of only one order with BAPI_SALESORDER_CREATEFROMDAT2 takes longer than 10 minutes, then the timeout is reached. This is the strange part. The processing of the bapi seems to get the same timeout of dialog processes, we already tested increasing the dialog process timeout and the timeout of bapi execution was the same...
We already monitor on SE66 to see if it opens a dialog process to execute the bapi call function, but it does not.
If anyone has any tip, please, provide us.
Thanks!
roberti

ABAP Proxy sender possible in integrated configuration AAE with PI 7.11

Hi guys,
we are running PI 7.11.
We have serveral scenarios where the senderis an ABAP proxy and the receiver is reached by a jave adapter.
With Ehp1 the SOAP adapter offers the possibilty to chose XI 3.0 as message protocol.
We use this feature already in scenarios where ABAP proxy is receiver.
But is it also possible to use it at sender side?
Kind regards
Jochen

Hi Volker,
thanks for your help.
You could also use ABAP proxy at sender side during integrated configuration.
Prerequisite is to implement SAP note 1349125 and use following url for acessing the PI from SAP backends.
http://<host>:<port>/XISOAPAdapter/MessageServlet?ximessage=true
With this URL you could ABAP proxies in normal scenarios where integration server is involved as well as in integrated configurations.
Kind regards
Jochen

Error with ABAP proxy

Hi all,
I have an ABAP proxy - XI - Webservice scenario, in the XI side we are getting error saying input data not coming in. How to check weather proxy is triggering the actual payload or data?
There has been a change in the WSDL from the Webservices side, they have changed the data type, so we too updated the mapping in XI. So do we need to change anything in the ABAP program which triggers the proxy,
how do I check weather proxy is triggering data or not?
I want to see weather its problem with the ABAP trigger program.
Thanks,
Srinivas

Hi ramakrishna,
Does R/3 side SXMB_MONI give successful chequered flag when the message is processed?
Because for correctly processed message, the data is being updated in the table, but I can't see the chequered flag on the R/3 side.
But for the wrongly processed ones its showing PL_TIMEOUT error and showing red flag on R/3 side, this is what I see on the R/3 side:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

Integrating with Middleware by ABAP Proxy.

Similar Messages

Maybe you are looking for