Idoc syntx error me21 , abap proxy call transaction

Hi Experts,
I am struck with the below problem, could you please shed some light on the issue, appreciate your help and rewarded.
scenario:
XI sends NEW PO message to abap proxy, in abap proxy we populate bdc_tab
and call ME21 as below
CALL TRANSACTION 'ME21' using bdc_tab mode 'N' update 'S' messages into messtab.
problem:
EKSEKS01 idoc is getting created with syntax error status code :26 in ECC5.0
only 5 sigments are generated in the idocs. the three segments ( E1PISHO, E1PISIO,E1PISSO not generated).
after transaction executed it returns subrc 1001, msgid--> ME, MSGNO --> 218.
Thanks In Advance.
Ranjit.

Hi Atish and Nishant,
Thanks much for the immediate response.
1.Would like to know what is the mandatory data to be passed for PO creation in BDC table.
2. Is there any user exit or where the idoc creation happens during me21 execution.
I have verified the po in we02 , as before mentioned the three sigments are not getting created and i am not sure the reason.
Note: We didnot have any output configured in ECC 5.0 for this idoc to be created.
I am really not able to locate in debug mode FOR ME21, where this ekseks01 idoc getting created and triggered.
Appreciate your help.
Thanks in Advance.
Ranjit.

Similar Messages

System exception after a succesful synchronous ABAP Proxy call

Guys,
I have the following scenario:
1) From an R/3 box I initiate a synchronous ABAP proxy call
2) On XI everything works fine, the http request is sent out (using the http adapter), the response comes back succesfully and it is transfered back to the R/3 box - no error whatsoever
3) On the R/3 box however the EXECUTE_SYNCHRONOUS method throws a system exception BUT the returning (input) parameter holds the response message!
So in the end if I catch this exception (CX_AI_SYSTEM_FAULT) then I could be happy and just ignore the exception, but I don't feel comfortable leaving it this way. Why is the exception and how can I eliminate it?
Any help would be greatly appreciated.
Thanks a lot,
Viktor

Joel/Jörg,
Thank you for your response, indeed I ended up debugging it and found my error deep down:
Error code: ABAP_PROXY.PARSE_APPLICATION_DATA
Error text: Error handling Response Message; XSLT error: CX_XSLT_DESERIALIZATION_ERROR: XSLT program and source line: /1SAI/XS00000000000000000088: 0000000122; Tree Position: abap.values.1.1.1.6.1.5 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: WINDSOR CT 06095-1712
The data field defined in SAP was too short for the field.
Thanks a lot,
Viktor

CX_BGRFC_INVALID_DESTINATION during outbound abap proxy call on 7.1

Hi guys,
I'm trying to set up a scenario with outbound abap proxy call using the new WS adapter and when I execute the report with the proxy call I'm getting the CX_BGRFC_INVALID_DESTINATION exception.
I've generated proxy w/o problems, I've set up everything in SOAMANAGER.
Have you experienced this issue?
Thanks for your help,
Olian

Hi guys,
so my connection to SLD works fine now and I'm still getting the error. Any other ideas?
Just in case: this is my proxy code. Is this correct for using with 7.1 and WS adapter?
REPORT Z_PI_PROXYTEST.
data sender_object type ref to ZCO_PROXYTEST_OUT.
data out type ZMT_PROXYTEST_OUT.
data lo_sys_exception TYPE REF TO cx_ai_system_fault.
data err_result type string.
out-ZMT_PROXYTEST_OUT-data = 'sample'.
try.
    create object sender_object
      EXPORTING
        logical_port_name = 'PROXYTEST'.
    call method sender_object->PROXYTEST_OUT
      EXPORTING
        output = out.
    commit work.
catch cx_ai_system_fault into lo_sys_exception.
    call method lo_sys_exception->IF_MESSAGE~GET_TEXT
      RECEIVING
        result = err_result.
    write err_result.
endtry.
write 'Data has been sent to PI'.
Thanks for your help, Olian

User-exit/BADI during outbound ABAP proxy call

Hello,
I want to introduce certain check during outbound ABAP proxy calls to PI. This is a generic check, failure of which would stop the proxy call to proceed and raise an exception.
I would like to place this at the generic place which is called for all the outbound ABAP proxy calls, rather than coding this in each and every outbound proxy class as the check is generic.
Is there some user-exit/BADI where i can introduce this? Maybe within class CL_PROXY_OUTBOUND or somewhere else where i can introduce this check.
Any help in this regard would be appreciated.
Best Regards,
Gajendra.

Dear Gajendra ,
i agree with sabrish, you must be having a z report on the application system that must be calling that outbound proxy...may be if the check is generic it may not be related to a proxy so you can code a FM and then call it before you call that proxy in the z report
Giving points is another way to say thanks

RFC (using AAE) vs IDoc (Using IE) vs ABAP Proxy (using IE) in PI7.1

Hi All,
In previous versions of SAP PI, SAP recommends the use of IDoc or Proxy over RFC mainly due to performance reasons, but with PI 7.1, RFCs can use AAE which significantly boost its processing.
So the question is, with PI 7.1, is the performance of RFC adapter using AAE good enough that is should be considered over IDocs (using IE) & Proxies (using IE)? Please provide elaborate reply.
Thanks,
Rahul

>>>>>So the question is, with PI 7.1, is the performance of RFC adapter using AAE good enough that is should be considered over IDocs (using IE) & Proxies (using IE)? Please provide elaborate reply.
Answer: If your major objective is only the performance factor then you can go for AAE using RFC. But RFC's individual processing performance is slightly lower than idocs and proxy.
Though AAE monitoring is just only in RWB, But due to less persistence steps involved in the entire processing, RFC with AAE supercede other options.
IDOc using IE vs Abap Proxy using IE --- I would recommend only Abap Proxy using IE. Plus you get all the monitoring features here.

Abap proxy call : synchronous / background ?

Hi,
I use currently abap proxy call to send data from ECC to XI, and it works fine ! But... I would like to know two points :
1. Is it possible to execute SYNCHRONOUSLY this call abap proxy and not only in asynchronous...
2. Is it possible to execute in BACKGROUND this call abap proxy, because it seems it use a dialog process, even if the call is inside an abap program executed in background
I will appreciate your feedbacks on these both points ?
Regards.
Mickael

Hi,
Yes, we can do Sysnchronous call in Proxy.
and we can do the Background job schedule also in Proxy .
Reffer this help file
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Reffer this BLOG also
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

ABAP proxy call to eBay webservice

Hi,
I'm trying to configure an ABAP proxy call to the eBay SOAP web services using ECC6 (SP14).
Has anyone had any experience they can share on how to configure the security for the proxy endpoint in SOAMANAGER to use the ebay services?
Thanks
Tim

Hi,
Yes, we can do Sysnchronous call in Proxy.
and we can do the Background job schedule also in Proxy .
Reffer this help file
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Reffer this BLOG also
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

Error Records in BDC Call transaction

Hi.....
     I am new to BDC concept... Can any of u tell me how to collect error records in BDC Call transaction... I already collected error messages through BDCMSGCOL... but i dont know how to collect those error records... here i am using two different flat files for header and line item... and kindly tell me if there is an error in line item how to get it so with relevent header details...
thanks,

Hi,
      LOOP AT t_bdcmsgcoll INTO w_bdcmsgcoll.
        PERFORM f_format_msg USING w_bdcmsgcoll CHANGING w_return.
     ENDLOOP.
Form format_msg
DATA : l_mstring(480).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      id        = w_bdcmsgcoll-msgid
      lang      = w_bdcmsgcoll-msgspra
      no        = w_bdcmsgcoll-msgnr
      v1        = w_bdcmsgcoll-msgv1
      v2        = w_bdcmsgcoll-msgv2
      v3        = w_bdcmsgcoll-msgv3
      v4        = w_bdcmsgcoll-msgv4
    IMPORTING
      msg       = l_mstring
    EXCEPTIONS
      not_found = 1
      OTHERS    = 2.
End format_msg
you can use the l_mstring to process further and pass to the bapiret2 table
Regards,
Vijaya

Transaction Update Error using ABAP Proxy

Hi Experts,
I am facing an issue using ABAP Proxy.
File is coming from PI to SAP system and it will update the Transaction IE02 using this inbound ABAP Proxy. If records fails then a mail is going to concerned team.
Issue:
When File has been sent from PI to SAP through ABAP Prxoy, it shows that record has been updated in the Transaction IE02 but when I checked manually the record, it has not updated the same. But when I test the same record through my ABAP Prox, it updates the record and when I checked it, Reocrd hs been updated.
Can anybody help me in this case?
Regards
Sachin

Hi Anup,
Can you please explain me for the same? If I need to put External Commit then how It is working when I running it manually
Regards
Sachin

Error in ABAP Proxy generation?

hai pals,
my intention is to push the data from XI to SAPBWSEM system throgh an ABAP PROXY.
       but , here i got an error which i already mentioned in the forum, that is " no connection to integration builder(only local data visible) ".
        i went to the integration engine configuration in "SXMB_ADM" transaction in SAPBWSEM server.
        in sxmb_adm transaction ,the system ask for the "specific configuration data-catagory" like TUNNING , MONITOR,RUNTIME,TRACELOG,DEBUG and RFCADAPTER.
         im little bit confused in choosing the "catagory of configuration data".so can u pls help me in this error.
with cheers.
rajesh

Did you create the RFC Destinations LCRSAPRFC and SAPSLDAPI to point your SLD ? If not do that.
Then create RFC Dest INTEGRATION_DIRECTORY_HMI type H. Look at your XI box and make these 3 RFC Dests.
Then use the following thread to fix your IFR_ADDRESS
Values for table SPROXSET
regards
SKM

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>

SAVE_STYLESHEET RC_6 error in ABAP proxy- CRM

Hi,
I developed a POC with just 2 fields in DT,for sender SOAP adapter and reciver ABAP proxy. It is running successfully.
But when i developed a actual scenarios with big structure it is giving the following error.
<?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="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">STYLESHEET_GENERATION_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Attempt to generate transformation required for rendering/parsing failed (, class , method ) STYLESHEET_GENERATION_FAILURE Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS) Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The only difference in both cases is, i developed everything in client 120 for POC. For actual scenario i created proxy class in client 110 and Technical system and everyting is pointing to client 120. Is it causing any problem?
Everyting is fine in XI but in CRM SXMB_MONI i can see the above error...
How to solve this issue.
Message was edited by:
ashok sri

i tired again.. i regenerated the proxy ... but still same problem..
i dont think internal framework problem.. because it worked for other scenario ( test scenario). I think i only messed it up some where.. but i dont know how to find out or how to debug the problem..
I have a doubt on package structure in which i am saving the proxy class.
i created a structuer package( level1) for which i assigned SAPPINT and for all other packages( level2- main package,level3-non main package, level4-non main package)i assigend SAI_SXMS, SAI_TOOLS, SAPPINT. I am saving the proxy class in level4 package. I am not able to assing SAI_SXMS,SAI_TOOLS to structure package. Is it causing any problem???????
any help please...
Message was edited by:
ashok sri

Abap proxy call failed

Hi,
I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.
Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,
an error occured on the R3 system:
PROTOCOL.LOOP_IN_MESSAGE_ROUTING
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:Context></SAP:Context>
               <SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>
               <SAP:Text language="EN"></SAP:Text>
            </SAP:ErrorHeader>
            <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type></SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type></SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>2.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>PROXY</SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
            </SAP:HopList>
            <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">
               <SAP:From>
                  <SAP:Name>WebServer</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>
               </SAP:From>
               <SAP:To>
                  <SAP:Name>UPG</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>
               </SAP:To>
               <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
               <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
               <SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>
               <SAP:Direction>Response</SAP:Direction>
               <SAP:Document></SAP:Document>
            </SAP:MessageHeader>
            <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
               <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
            </SAP:InternalAttributesHeader>
         </SOAP:Header>
         <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
            <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
               <SAP:Payload xlink:href="cid:[email protected]">
                  <SAP:Document>TraceDocument</SAP:Document>
               </SAP:Payload>
            </SAP:Manifest>
         </SOAP:Body>
      </SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:[email protected]
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
         <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
            <Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <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 = UPG</Trace>
            <Trace level="1" type="T">client = 100</Trace>
            <Trace level="1" type="T">language = E</Trace>
            <Trace level="1" type="T">user = YLEBLEVEC</Trace>
            <Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">**************************************************** </Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>
            <Trace level="1" type="T">PLNAME = SENDER</Trace>
            <Trace level="1" type="T">QOS = BE</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="T">URL for integration server read from global configuration </Trace>
            <Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>
            <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>
         </SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END
I guess the error occurs before the call of my proxy. Can anyone help?
Thanks,
Yann

Hi,
>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?
I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right
further reference (XI configuration guide):
<b>Connecting Business Systems with an Integration Engine to the Central Integration Server</b> <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)
>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?
yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)
no need for a second client on R3 side:)
sorry if I confused you with my response
Regards,
michal
Message was edited by: Michal Krawczyk

File to custom IDOC or File to abap proxy

Hi there,
I would like to know best approach for the following scenario.
1) i have file coming from legacy system
2) On target side SAP , I have BAPI's available (Create, Save, Commit )(No standard IDOC available)
I can create Custom IDOC and call those BAPI's in Custom Function Module
or
I can use ABAP proxy and call BAPI's
What is the best way of doing this? and Is there any other way?
Thanks
Kumar

hi,
Abap Proxy is better than RFC in terms of performance.
proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
In your case , if there want to crate idoc from scratch level then we go for proxy and proxy support large volume of data (more than 5 mb).
One more reason is RFC , the data is converted between RFC and XML in RFC adapter. In proxy XI communicates with the R/3 in native XI language (SOAP XML).

Error in ABAP Proxy

Hi ,
I am getting an error in the proxy , it was working fine but today only it is throughing the following error :
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>CREATE_OBJECT_CLASS_NOT_FOUND</SAP:P1>
<SAP:P2>ZZCL_MIIA_UKEUROPE_TLOG</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing</SAP:Stack>
Please let me know the reason of this .
Thanks in anticipation
Anita

Hi,
I am assuming you have a server proxy (Inbound interface).
Your proxy objects have not been created properly.
To check this, send a message to XI.
Either XI itself will throw an error message, or running SXI_MONITOR in receiving SAP application will show you the error . If you do not see any entry for corresponding interface, then proxy objects have not been created properly.
Regards,
Puloma.

Idoc syntx error me21 , abap proxy call transaction

Similar Messages

Maybe you are looking for