ABAP Outbound Proxy Error

Hi Everyone,
In PI ESR, I have update the data enhancement structure with new field and I have mistakenly activated standard service Interface which is refering to ehancement structure.
Now in the ABAP side in SPROXY transaction, Interface is showing red. Since its standard proxy I am unable to regenerate the proxy.
Please let me know your suggession.
Regards,
Sudheer

Hi,
Error is related to the connection set up done between ECC and PI.
Test the connection using sldcheck.
HTH
Rajesh

Similar Messages

ABAP Outbound Proxy: some messages stuck in CRM system

Hi all,
we've a strange issue with a ABAP Outbound proxy we've generated in our CRM 5.0 system (asynchronous interface).
Sometimes messages stuck in the CRM system. They are in status 'Scheduled' (green flag) in SXMB_MONI in the CRM system. When I have a look at the corresponding queue, there's no message within. Status in SMQ1 and SMQ2 is fine, too. All queues are registered. When I reprocess such a message manually in SXMB_MONI in CRM with the restart button, they're sent fine to XI.
Please note: it's NOT a general issue with that outbound proxy. In most cases the messages are sent immediately, just in some cases the messages stuck and I don't know why.
Is it possible to restart such messages automatically? I just know the report RSXMB_RESTART_MESSAGES, but that one just restarts messages in Error status. But the ones we have aren't in error status so they cannot be selected with that report.
Any idea where could be the problem / we should check?
BR
Holger

On which SP r u working correctly. May be an SP upgrade could help.
Regards,
Prateek

Sync abap outbound proxy steps

Hi friends,
Could you please help me to send the sync abap outbound proxy creation blogs.
advanced thanks
Rao

hi
check this
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
rgds
Arun

Outbound Proxy error when triggering from SPROXY

Hi Everyone,
I was working on outbound proxy from ECC to PI. I have generated the proxy and activated. When I am trying to test the proxy manually from SPROXY the message is not getting triggered to SXMB_MONI in ECC itself. But I didn't get any error message as well. When I am executing the proxy from SPROXY I was getting below message in the status bar. So can anyone help me with the possible solution why the message is not getting triggered.
Below is the options I have selected while executing the proxy.
This was the status message which was giving after execution of proxy from SPROXY. The same status was giving for all the Proxy interface which ever is executing from SPROXY.
Regards,
Kankipati.

Hi Kankipati
can you please try Commit work by navigating on test proxy screen .
Extra- Trigger Commit work .
Follow the below link .
SAP PI Reference: SAP PI ABAP Proxy Outbound settings, Triggering message to SAP PI(When many sap pi systems)
Best Regards
Srinivas

ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3

The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14. After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.
The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction". This error was resolved by manually putting the correct action in the SOAManager configuration.
Ran the same test again and then the service provider complained about the To field in the SOAP Header. The error message said "SoapHeaderException: SOAP header To was not understood".
Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:
<n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
http://localhost:50081/AddSix.asmx
</n3:To>
Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:
<wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
http://localhost:50081/AddSix.asmx
</wsa:To>
It looks like the issue is with the xmlns:soap-env element that has different values in these two systems. Searched in SDN but could not find any related information. Please help if anyone has experienced similar issue or knows how to fix it.
Thanks,
Jiannan

Got solution from SAP through an OSS message. Below is SAP's solution:
Either the Message ID protocol should be switched off on the SAP
consumer side or turn on this protocol support on the .NET provider.
To switch off the Message ID protocol:
1. start the soa manager
2. find the consumer proxy
3. find the corresponding logical port
4. jump to the 'Messaging' tab
5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field
Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration.

File - ABAP Server Proxy - Error - CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV

Hi,
I am working on File-ABAP Proxy(Server) scenario. I've created the repository and integration objects correctly and have activated them. When I do a Test Configuration in the Integration Directory, I am getting the below error:
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="2" type="T">......attachment XI_Context not found </Trace> <Trace level="3" type="T">Mapping already defined in interface determination </Trace> <Trace level="3" type="T">Object ID of Interface Mapping 50539A6C73A334AEA587C7CD0459B373 </Trace> <Trace level="3" type="T">Version ID of Interface Mapping 21A89031E65411DE9576D36A0A505355 </Trace> <Trace level="1" type="T">Interface Mapping urn:acc:pi:serverproxy OM_Member </Trace> <Trace level="3" type="T">Mapping Steps 1 JAVA_JDK com/sap/xi/tf/_MM_Member_ </Trace> <Trace level="3" type="T">MTOM Attachments are Transferred to the Payload </Trace> <Trace level="3" type="T">Dynamic Configuration Is Empty </Trace> <Trace level="2" type="T">Mode 0 </Trace> <Trace level="1" type="T">Field PARAMETRIZATION not a member of INPUT Thrown: com.sap.mw.jco.JCO$Exception: Field PARAMETRIZATION not a member of INPUT at com.sap.mw.jco.JCO$MetaData.indexOf(JCO.java:9897) at com.sap.mw.jco.JCO$Record.getTable(JCO.java:14710) at com.sap.aii.ibrun.sbeans.mapping.ParametrizationMap.newInstance(ParametrizationMap.java:64) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:111) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy376.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:266) </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
The above error says that the error is: "Mapping already defined in interface determination". But I've double checked my Interface Determination, it is correct.
And if I try to post the payload in the Integration Engine in RWB, I see the status as "Recorded for Outbound Processing" in SXMB_MONI. If I try to release the queue, the status is "SYSFAIL".
For your information, I'm working on SAP PI version 7.11 PI 7.1 EHP1 SPS 03.
Any inputs on this eror will be really helpful.
Thanks,
Vijay

Hi Vijaya,
-->Try to execute the end to end scenario with out testing it in the Integration Directory(ID).
-->Even i faced some problem in the ID while testing the scenario through the TEST CONFIGURATION,but when i execute the end to end scenario it is successful.
Thanks

ABAP Inbound Proxy Error !

Hi ,
I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.
<?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">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack> <SAP:Retry>M</SAP:Retry>
</SAP:Error>
Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application

Hi attached trace, kindly update wat could be the problem in case of EBP SUS Vendor replication
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<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 = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:21Z CET</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 = DD128437FD4A75F193690017A4F3435A</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</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</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="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<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 RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:24Z CET</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 external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <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="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o97" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o97">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o96" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o96">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
*<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 00000008 does not exist; check entries Programm:* CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

ABAP provider proxy error using Fault Message Type

Hello experts,
I'm using a provider ABAP proxy with a fault message type in the inbound service interface.
In the ABAP code on the backend system, I need to fill a database table.
in case the record exist --> fault + message back to SAP PI to be alerted.
I do this with a RAISE EXCEPTION TYPE.
I generated all necessary proxies.
The error I got on the backend system (SXMB_MONI) is this:
Application Error - Call Inbound Proxy
SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="xxxxx">FMT_xxxxxx</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
Can it be that I need to use something else instead of the RAISE EXCEPTION TYPE. to get something back to SAP PI?
Now the error is logged in SXMB_MONI on the backend system.
Please advice.
Thanks a lot
Dimitri

Hi Dimitri,
Check out these links -
1. /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
2. http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Sunil Chandra

ABAP Client Proxy error code: 401, error text: Unauthorized

Hi,
I have Client proxy in ECC for oubound interface in PI 7.0, when i look into SXMB_MONI of ECC i can see my message with Error "HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)".
As per few thread i already assign SAP_XI_APPL_SERV_USER role to PIAPPLUSER in ECC, still i am getting same eror.
I do not understand how this Proxy communication work, which ECC user will be use in communication and how this communcation link to RFC destination "SAP_PROXY_ESR" type G. Even i can not see type H in ECC so i created RFC destination of type G.
With Regards
Sunil

We were able to get it working by making a change in the Integration Engine Configuration (in sxmb_adm).
Changed "Corresponding Integ. Server" from "http://<server>:<port>/sap/xi/engine?type=entry"
to "dest://RFCdestinationName"

ABAP Outbound Proxy with multiple entries

I have message type as follows.
MT_Proxy_Matmas_out -- DT_Proxy_Matmas_out
Matnr         1..unbounded
   Material_Num   1..1
   Material_Dec    1..1
Message Inrerface: MI_proxy_Matmas_out.
Generated Proxy has following objects.
1. Class     ZMCO_MI_PROXY_MATMAS_OUT     Proxy Class (generated)
2. Structure     ZMDT_PROXY_MATMAS_OUT     Proxy Structure (generated)
3. Structure     ZMDT_PROXY_MATMAS_OUT_MATNR     Proxy Structure (generated)
4. Structure     ZMMT_PROXY_MATMAS_OUT     Proxy Structure (generated)
5. Table Type     ZMDT_PROXY_MATMAS_OUT_MATN_TAB     Proxy Table Type (generated)
Report Program ZB_Matnr_xport.
DATA: prxy TYPE REF TO ZMCO_MI_PROXY_MATMAS_OUT.
DATA: i_data_records TYPE TABLE OF ZMDT_PROXY_MATMAS_OUT.
DATA: wa_data_records TYPE ZMDT_PROXY_MATMAS_OUT.
DATA: it type ZMMT_PROXY_MATMAS_OUT.
CREATE OBJECT prxy.
Loop at itab
MOVE_Corresponding ......to XXXXXXXXXXXXXX // we tried several option with no success here in this Loop //
EndLoop
CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
     commit work
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
As you can see from above template I want move all the records of Internal table to Message Type structure before calling Proxy, CALL METHOD proxy->.........
Can someone provide me sample code how to achive this. We are on WEB AS 620.
Thanks a lot.
ST

suppose your table is it_datatable of type ZMDT_PROXY_MATMAS_OUT_MATN_TAB which contains matnr, description. Then try the following
data : l_var type ZMMT_PROXY_MATMAS_OUT.
l_var-MT_Proxy_Matmas_out-Matnr 1[ ] = it_datatable[ ].
then
CALL METHOD prxy->execute_asynchronous
EXPORTING
output = l_var.
commit work

SAP Upgrade issue ABAP-PI Proxy error

Hi Guys,
We have an issue in SAP R3 system after the recent SAP upgrade.
The proxy programs in R3 were using SAP Standard structure in their development.
Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
Kind Regards
Rajesh.S

Hi Harald,
Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
Best Regards,
Rajesh.S

Abap Proxy Errors

Hi Experts,
My scenario R/3->XI(ABAP Proxy)--->SUS Systems
Getting the following error in SUS system.XI system it doesn't throw any error in moni.
I am new to proxy concepts.Also please let me know any related blogs or suggestions in this regards.
<?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">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSIV_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Sudhansu

Hi Behera,
Can you debug your proxy using this blog:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f&overridelayout=true
Also please check few solutions given in this threads for the same issue:
Re: Messages waiting in SUS Moni
Re: ABAP Inbound Proxy Error !
Regards,
---Satish

Message has Error status on outbound side - in ABAP inbound proxy !!

Hi All,
One interesting question for you guys. I have got one of the scenarios like File to ABAP inbound proxy. Message are going properly, no errors in receiving system. But on PI moni I can able in "outbound status" column in red colored flag. No all the messages couple of them with u201CMessage has Error status on outbound side ". Why please?
Regards
San

Hi ,
Please check whether the correct data is coming from sender side . and check the j2ee engine runtime parameters.
Cheers,
Meera
Edited by: MeeravaliDudekula on Oct 18, 2010 2:36 PM

SPROXY error testing outbound proxy interface

Hi,
I am trying to test an outbound proxy interface using SPROXY but am getting the following error:
Apart from the above messages there is no more help available. When I try testing the generated XSLT program using SXSLT_TEST it gives an error "No valid XSLT program supplied". I have checked and the auto generated XSLT program does exist.
Any help appreciated.
Thanks
Che

Hi Che Eky,
Check out below helpful thread & doc:
SERIALIZE_APPLICATION_DATA Conversion error ABAP => XML: Request Message
Serialization issue in abap proxy
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a89312f8-0b01-0010-86b3-fdd7178e0534?QuickLink=index&…
Regards,
Krupa

ABAP client proxy 401 error

Hi i have generated a ABAP client proxy in my ECC system and sending an outbound message to XI. i get the following error.
HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)
I have tested the following.
1) My sld and ECC system have the integration engine and pipeline settings for the XI Server: http://server:8000/sap/xi/engine?type=entry
2) logon to the URL http://server:8000/sap/xi/engine with user XIAPPLUSER and pwd in the browser because of the error 'Der Aufruf der URL http://server:8000/sap/xi/engine wurde aufgrund fehlerhafter Anmeldedaten abgebrochen'
any sugestions ? using a proxy as target works fine

Hi ,
You seem to have a problem with the XIAPPLUSER logon. Can you check that the user has the appropriate authorizations? Maybe the user is locked? Maybe the password has been incorrectly entered?
XIAPPLUSER should have the role SAP_XI_APPL_SERV_USER.
Also, check that the XI engine service has been activated.
Transaction SICF. Default_host->sap->xi Activate the entire node with all subtrees.
Cheers
Manish

ABAP Outbound Proxy Error

Similar Messages

Maybe you are looking for