File to Server Proxy Scenario

Hi,
I am working on ABAP (server)Proxy scenario. My servers are SAP PI 7.1 EHP1 and SAP ECC 6.0 running on HP-UX. I have gone through the Configuration steps for Proxy scenarios document. In that I found I need to create LCRSAPRFC and SAPSLDAPI RFC connections in ECC system and maintain the Program ID which is maintained in the J2ee Engine of ECC server.
But my issue is - ECC system is running on only ABAP Engine.
1. Can I configure Proxies with ECC systems which are running on only ABAP engines?
2. I have ignored LCRSAPRFC and SAPSLDAPI steps and completed other configurations. I am able to see SWCV and Message Interfaces created in PI in ECC (SPROXY Transaction). Does this mean that I can ignore these 2 RFCs and go ahead with Proxy configurations?
Thank you.

>>I have ignored LCRSAPRFC and SAPSLDAPI steps and completed other configurations. I am able to see SWCV and Message Interfaces created in PI in ECC (SPROXY Transaction). Does this mean that I can ignore these 2 RFCs and go ahead with Proxy configurations?
Why we need SM59 destinations SAPSLDAPI and LCRSAPRFC (on ECC) :
LCRSAPRFC reads the exchange profile,
SAPSLDAPI is used by the ABAP API.   Maintain the destinations as type T destinations to the registered server program with the program ID SAPSLDAPI. The program ID corresponds to the SLD data bridge.
When using the destinations, the back-end system uses the parameters maintained in transaction SLDAPICUST.
thanks
BJagdishwar

Similar Messages

  • File to ABAP Proxy Scenario

    Hi All,
    I am  doing File-to-ABAP Proxy Scenario, in the sender side side it is picking the file, but in sxmb_moni it is giving the error:
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Adapter*
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
      <SAP:P1>4CFF4691EEE211DC85E30019D1522982</SAP:P1>
      <SAP:P2>CENTRAL</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Message ID 4CFF4691EEE211DC85E30019D1522982 already exists in called system (pipeline CENTRAL)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Can u plz tell me why this error is occurring and how we can resolve this error.
    Thanks & Regards,
    Vikas

    Hi Vikas
    make a dummy change and activate your object then make a full refresh
    you can make it through in 3 ways
    1) tcode SXI_CACHE
    2) go to ID -> environment and make a full cache refresh
    3) http://<host>:5<sys#>00/CPACache/refresh?mode=full     Full CPA cache refresh
    when you do the developement then these are stored in ABAP data dictionary table which can be refreshed by delta cache
    while full cache will delete this temporary object and make this cahe into runtime
    hope this will help you
    thanks
    sandeep
    if helpful reward points

  • File to ABAP Server Proxy Scenario

    Hi 2 all,
    I am running File to Server(ABAP) Proxy scenario...
    I have checked the ABAP Server Proxy at application server only and it is working fine....But when i am running the whole scenario my server proxy is not getting executed..( i.e my file is being picked up but proxy is not getting called ..:(( )
    Can i expect some valuable inputs regarding this issue..?
    Regards,

    to debug the problem....
    first check SXMB_MONI of R3 system... where proxy has been created.
    1 .check whether your proxy has been called ... it will be evident you get any message in moni for you interface or namespace..
    2. check you proxy message has not got stucked in queue... sometimes message get stucked in queue and hence proxy are not called.. release the messaeg using smq2.
    ELSE
    1 .go to SXMB_MONI...of XI..
    2. select 'Call Adapter'  in right hand of monitor.
    3. check the 'trace' under Call Adapter.
    4. if you go at end of trace or somewhat near to end.. there should trace like...this ...
    Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">Addressing mode: destination</Trace>
      <Trace level="3" type="T">Destination = D67CLNT103_HTTP</Trace>
      <Trace level="3" type="T">Attributes of destination: D67CLNT103_HTTP</Trace>
      <Trace level="3" type="T">Type = H</Trace>
      <Trace level="3" type="T">Pipeline = ENTRY</Trace>
      <Trace level="3" type="T">Action = EXECUTE</Trace>
      <Trace level="3" type="T">Host = XXXXXXX</Trace>
      <Trace level="3" type="T">Port = XXXX7</Trace>
      <Trace level="3" type="T">Client = 103</Trace>
      <Trace level="3" type="T">User = XIAPPLUSER</Trace>
      <Trace level="3" type="T">Language = E</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">SSL not active</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
    check whether connection establishment between XI and R3 is successful or not...
    if you are getting same message as above ,,that means ur RFC is working fine...
    problem is on r3 side.. for this go to r3 and check moni...

  • Structure Conversion in Fileadapter in a server proxy scenario

    Dear all,
    i'd like to do the follwoing thing in XI:
    1. Receive a structured text file
    2. Make an content conversion:
    File is structured in the following way:
    - all records have fixed field length, there are two possible types of record, indicated by the first 2 characters e.g.
    AA Recordtype 1
    BB Recordtype 2
    BB Recordtype 2
    BB Recordtype 2
    BB Recordtype 2
    AA Recordtype 1
    BB Recordtype 2
    So each record of type 1 is followed by 0 - n records of type 2.
    3. Send the converted message into an ABAP inbound proxy
    I have some questions regarding that scenario:
    a) Can i use the flag "Recordsets per message" in XI to control if my message should contain multiple recordsets (one recordset would be associated with one record of type 1 and N of type 2)
    b) How will i access in the server proxy class the records. Will I have a field for the recordset (or a table of recordsets if i don 't use the flag "Recordsets per message" in XI ).
    What about the subfield? Will I have a table structure for the record of type 2?
    c) Is the file content conversion I described feasible?
    Many thanks in advance for your replies
    Best regards
    Florian
    Edited by: Florian Wittke on Jul 28, 2008 5:31 PM

    Hi,,
    a) Can i use the flag "Recordsets per message" in XI to control if my message should contain multiple recordsets (one recordset would be associated with one record of type 1 and N of type 2)
    why? i dont see any productive for this.
    b) How will i access in the server proxy class the records. Will I have a field for the recordset (or a table of recordsets if i don 't use the flag "Recordsets per message" in XI ).
    to integrate with a proxy see nexts PDFs, is the same for BW,BI,R3.
    follow this guide
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e698aa90-0201-0010-7982-b498e02af76b
    or this
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/18dfe590-0201-0010-6b8b-d21dfa9929c9
    What about the subfield? Will I have a table structure for the record of type 2?
    c) Is the file content conversion I described feasible?
    hi, yes it can be done.
    see this link
    File content conversion for Pipe delimited file
    in this link some blogs
    fcc
    Thanks
    Rodrigo

  • SAP XI- File to ABAP Proxy scenario

    Hi SDN,
    I have a FILE to ABAP proxy scenarioin SAP+XI can you guide me how to procede in that, what should be my ESR and ID objects and how to use the sproxy transaction.
    Regards,
    Aniruddha Bhattacharya

    Hi,
    please check out the search option on SDN forum first - there are tons of blogs with step by step on the same
    come back with more detailed questions ok ?
    thank you,
    Regards,
    Michal Krawczyk

  • File to Abap Proxy Scenario : No message log in SXMB_MONI

    I have a PI Scenario in which a FTP server is polled every 5 minutes, and when it receives any file,  file is archieved and abap proxy is called. Few days back it was running perfectly fine. But For last couple of days I am facing strange error.
    My File is archived but abap proxy isnot called, neither I get any message in SXMB_MONI.
    any guesses what should I do?
    Jawed Ali

    Hi Jawed,
    HOLD means you have given QoS as EOIO in sender channel and the first message got failed and hence all messages are waiting..
    Check this thread
    Re: PI 7.1 Messages stuck into the Queue of the Adapter Engine
    Try resending the messages through runtime workbench->message monitoring->adapter engine
    Regards
    Suraj

  • 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

  • Performance problem in File to ABAP Proxy scenario

    Hi gurus,
        I have a scenario where the sender is sending a file and the receiver is ABAP Proxy.The file is a simple DAT file containing banking data.The file sample is as belo
    00000MM21901 PYM0901021531     
    704401020100005510000040000D0002
    704401020127147391000033500D0003
    704401020127147391000045000D0004
    704401020109341157000038800D0005
    70420!!!!10200000182174D
    704401021100006040000015158D0001
    704401021100006040000005034D0002
    7042010210000020192D
    The above file need to be split and mapped to the fields of the ABAP Proxy after doing some validations.
    Is Receiver Determination using mapping required? What is the most efficient way of splitting the file?
    Please give your replies keeping better performance of the interface in mind.What is the best way of doing the validations?
    regards
    Debansu

    Hi Satish,
        As you can see in my question above,the sender side contains a flat file(the file format is given in the question),I need to split the file into strings which can then be mapped to specific fields of the ABAP Proxy.A sample output of the xml file that is passed on to the ABAP proxy after mapping transformations is given below:
    <BATCH_TOTAL_RECORD_420>
      <BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
      <KEY_VALUE>420</KEY_VALUE>
      <BATCH_NUMBER>1021</BATCH_NUMBER>
      <BATCH_TOTAL>0000020192</BATCH_TOTAL>
      <FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
      <FILLER />
      </BATCH_TOTAL_RECORD_420>
    - <BATCH_TOTAL_RECORD_420>
      <BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
      <KEY_VALUE>420</KEY_VALUE>
      <BATCH_NUMBER>9999</BATCH_NUMBER>
      <BATCH_TOTAL>0000202366</BATCH_TOTAL>
      <FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
      <FILLER />
      </BATCH_TOTAL_RECORD_420>
    I hope now you can provide me some answers.
    Regards
    Debansu

  • IDoc to ABAP Server Proxy scenario

    HI Experts,
    Recently our client has upgraded his R/3 system. From this R/3 system, IDocs are posted to SRM system thorugh XI.
    On receiver side we are implementing ABAP Server Proxies.
    We have recomended our client with all necessary changes to be done on XI Server during change over from old to new R/3.
    After change over, they have tested the scenario,  posting the IDocs to the SRM system. We found the follwing error in SXMB_MONI, Could some one tell me where exactly to look in to it.
    An error occured within an XI interface: The reference to a source object via the object number is different than the reference via the GUID Programm: SAPLBBP_BD_API; Include: LBBP_BD_APIF39; Line: 175
    Regards
    Praveen

    Hi,
    Pl implement note 1052569.
    And run report "RPODDELVRY",
    MM-SUS scenario mapping of the Goodsreceipt for inbound delivery @SUS
    Thanks
    Swarup

  • File to ABAP Proxy (problem with inbound queues in R3)

    Hi,
    In File-XI-ABAP proxy scenario, XI is successfully picking up file and sending it to R3.
    But in R3, an inbound queue is created in SMQ2 transaction code and I solved the same to automatically process the Queue by registering that in SMQR transaction code. But even though the inbound queue doesn't appear in SMQ2 (which means that it is processed successfully) it doesn't call the method EXECUTE_ASYNCHRONOUS. Can anyone help me whether I need to do any settings to run that method?
    Also can anyone help me, after the inbound queue is successfully processed in SMQ2 transaction, what would be the next step to watch what exactly that queue has done?

    Hi,
    Please check the program code for Server ABAP proxy.
    This will show you the trigerring of Proxy on inbound side.
    ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
    For Queues, you can go to SMQR and check for the register queue. Select and double click on it. If anything is stuck up then you can see in it. Even same with SMQ2
    Thanks
    swarup

  • ABAP server proxy help required

    Hello,
    I want to make two simple ABAP server proxy scenarios
    1. File to ABAP server proxy (async scenario)
    2. File to ABAP server proxy (sync scenario)
    Pls send me the blogs/docs for the above scenarios.
    Regards

    Henry,
    Please go through the below links.
    <b>File to R/3 via ABAP Proxy with good example</b>
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    <b>Synchronous Proxies:</b>
    <b>Outbound Synchronous Proxy</b>
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
    <b>Inbound Synchronous Proxy</b>
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
    Also go through this, if you have problems in your proxy connection.
    <b>How to Activate Proxy.</b>
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Regards,
    Sarvesh

  • File to ABAP proxy with EOIO

    Hi Experts,
    I am working on File to ABAP proxy scenario. The requirement is to have EOIO from end to end.
    Which means the files have to be sent to target system (R/3) in the same order as they are placed in the file location. I have two questions regarding this.
    1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
    2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
    Please provide your valuable inputs.
    Thanks and regards,
    Prasad

    Hi,
    1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
    1 queue is okay. Just specify it in the Sender File CC.
    2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
    Processing Sequence is not supported for FTP and is only for NFS.
    If you have to use processing sequence, then do an FTP, bring the files to an NFS directory and then use the processing sequence accordingly.
    Hope this helps.
    Regards,
    Neetesh

  • File to ABAP proxy via AAE

    Hi All
    Am doing a file to ABAP proxy scenario and using SOAP adapter(XI protocol 3.0) at target side in order to make use of AAE.
    But while testing am getting the following error at both the channels(file and soap) :
    Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out.
    SOAP channel configuration :
    Target URL : http://X.X.X.X:8001/sap/xi/engine?type=entry
    Logon language : en
    X.X.X.X  being the IP address of the target system which is BW.
    Appreciate any help.
    Regards
    Soumen

    Re-Iterating my 1st post : Am using SOAP( Message Protocol : XI 3.0 ) as I want to make use of the AAE. XI adapter is not supported by AAE.
    Followed this : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true
    Anyways, found out I was having some error in teh IP I was using ...corrected it and now my error is changed to :
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden
    Now since my source is File which goes through mapping, what do I need to do for this error?

  • INTERNAL - AMF_ERROR in XML -- ABAP proxy scenario

    Hi Experts,
    Can any one help me to solve this following issue please, it is happening while I am executing the scenario between XML File to ABAP Proxy scenario.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">AMF_ERROR</SAP:Code>
      <SAP:P1>1</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error when processing message number 1 in package No object type found for the message. Check that the corresponding process is activated An exception has occurred.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>.
    This XML message has got 5 Lines Header and more than 100 Lin Items, this kind of Header and Lin item message 3 to 4 in one XML, I am using multi mapping. Message mapping shows working fine, OM also shows working fine. BPM is splitting messages to send messages to ABAP Proxy on SNC 7.0. After I have done all with SDN experts support, still I am having the above issue. can any one experties might help to resolve this?
    I will appreciate your support.
    Thanks & Regards
    San

    Can you please explain the solution.
    Regards,
    Rashi

  • How to debug XI--- R/3 (abap server proxy) code,  SYSFAIL in SMQ2

    Hi
    i have a XI (BPM) to R/3 (ABAP server proxy) scenario,
    when the data goes from XI to R/3, it is getting stuck at R/3 inbound queue (SMQ2), with status : SYSFAIL and error text: "No roll storage space of length
    3391496 available for internal storage",
    we tried activating the queue/ reexecute the LUW, but it still shows the same error status after running for some time,
    how can i debug the ABAP server proxy,
    pls tell me how can i debug the ABAP proxy code in the R/3
    very critical issue

    Have a look at SAP Note 17965 - No storage space available
    Regards,
    Prateek

Maybe you are looking for