Proxy-to-idoc

hi,
my proxy-to-idoc is working fine and i checked runtime workbench and sxmb_moni,
but the idoc is not see updated in reciever system.
plz provide solution to trouble shoot idoc receiving.
thanks and regards
vijedner

Hi,
For Your scenario
1) Check in the Sender system(Proxy) at SXMB_MONI, are you able to see the success message or not
2)There by check in XI side in SXMB_MONI for the xml message.If the message is not come means check in SMQ2 of XI and also in IDX5 for the same
3) If the message is there in XI and not come to R/3 means,
check in SM58 of XI for any error entries and also check in SMQ1 of XI
Any one of the above mentioned places you shld see your Message
REgards
Seshagiri

Similar Messages

  • Pipeline error for abap proxy to IDoc scenario

    hi experts,
    i am getting the following system error in moni for my proxy to idoc scenario.
    In error it shows :
    "Receiver service cannot be converted into an ALE logical system"
    but i have checked adapter specific attributes of both receiver
    and sender sys and they both have logical systems ( SO this is not the problem)
    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>
    pls suggest .
    Appropriate points will be awarded

    Hi,
    Copy the payload from moni and test the mapping.
    The error may be due to XML file generated by sender channel is not proper.
    and also look at this blog
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Please reward points if it helps
    Thanks
    Vikranth

  • Async Sync Bridge without BPM (Proxy-Soap-Idoc)

    Hi,
    I have read some blogs how to do the Async Sync Bridge without BPM for JMS adapters. I have a requirement that I am getting a Async Proxy message to PI and then PI makes Sync Soap call then the result need to send through the Idoc adapter.
    Proxy - Soap- Idoc
    Here Proxy is a sender so no adapter required in the Config and also Soap is java based adapter and Idoc adapter is a ABAP based so I am not sure this is possible but I just wanted to check with you.
    Please let know if this is possible or not?
    PI 7.1 with EHP1
    Thanks,
    Laxman
    Edited by: Laxman  Molugu on Oct 14, 2010 2:15 PM

    The mapping programm can be defined as a user defined function. As sample of mine is "getGoogle()", which is doing some kind of address validation. The input parameter URL[0] contains source address. For that you need to import:
    org.apache.commons.logging.*;
    org.w3c.dom.*;
    javax.xml.parsers.*;
    org.xml.sax.SAXException;
    org.apache.commons.httpclient.*;
    org.apache.commons.httpclient.methods.*;
    org.apache.commons.codec.*;
    org.apache.log4j.*;
    Example code for UDF "getGoogle()" is:
    String sUrl = "http://maps.google.de/maps/api/geocode/xml?address=" + URL[0] + "&sensor=false";
    HttpClient client = new HttpClient();
    GetMethod method = new GetMethod(sUrl);
    byte[] responseBody = null;
        try {
    //      int statusCode = client.executeMethod(method);
    //      byte[] responseBody = method.getResponseBody();
    //     result.addValue(new String(responseBody));
    String sResponse = "initial";
    int statusCode = client.executeMethod(method);
    responseBody = method.getResponseBody();
    ByteArrayInputStream bis = new ByteArrayInputStream(responseBody);
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder db = factory.newDocumentBuilder();
    Document doc = db.parse(bis);
    doc.getDocumentElement().normalize();
    NodeList nodeLst = doc.getElementsByTagName("formatted_address");
    Node formAdr = nodeLst.item(0);
    NodeList nlFormAdr = formAdr.getChildNodes();
    sResponse = ((Node) nlFormAdr.item(0)).getNodeValue();
          // Deal with the response.
        result.addValue(sResponse);
        } catch (Exception e) {
          result.addValue(e.toString() + "######## exhrenda - googleResponse:############### URL=" + sUrl+"###########"+new String(responseBody));
        } finally {
          // Release the connection.
          method.releaseConnection();

  • Proxy to IDOC for BP Data

    Hi Experts,
    I am working on a Proxy to IDoc Interface for Business Partner data.
    Sender : ECC 6.0 (Proxy)
    Receiver: 4.6c (Idoc)
    I have used standard Message type "ABABusinessPartner" as sender.
    And i am mapping this message to DEBMAS and ADRMAS idocs (splitting).
    After making the changes for business partner in transaction BP, It is creating one XML file in sender and splitiing in PI and creating 2 idocs in receiver.
    The problem is, the ADRMAS idoc is not getting any data. Its blank.
    It is fine with DEBMAS, it contains the expected data.
    I have tried passing the control record as constants and selected the option to take the control data from payoad in Cc.
    If required any other info. please let me know.
    Waiting for your inputs , Thanks.
    Regards,
    Naveen

    Thanks for your replies.
    Yes, i am able to see the payload in MONI.
    i have done all the IDX stuff. and i am able to see the idoc in my receiver side.
    i have tested my mapping. Even i am able to see the data in receiver payload.
    and tested the scenario in ID using 'Test configuration'. it is fine.
    I am able to see the idoc in receiving system, but it is failing with error
    "No appropriate entry found in table TSADOBJ".
    I had a check in table TSADOBJ. It contains the entries for BUS1006 (BP Address).
    Regards,
    Naveen

  • ABAP Proxy Vs IDOC

    What are all the advantages ABAP Proxy has over an IDOC?
    When to go for an ABAP Proxy?

    Pete,
    <b>Proxy and Idoc:</b>
    IDOC : After recieving the strucutred data It processes it using a Function Module associated with it. If you have a standard Idoc for your requirement then you should go with Idoc only.
    Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
    This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
    Also go through this urls which may help you:
    /people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
    RFC VS PROXY
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    Re: IDOC and RFC
    Re: Proxy Vs IDOC
    ---Satish

  • Serialize ---- Proxy to Idoc scenario

    Hi Folks,
                I m using Proxy to Idoc scenario and am trigerring proxy messages one after other from my function module on the outbound side. However sometimes idoc2 gets posted before idoc1.
    My requirement is that idoc2 to be processed only after idoc1 is successfully posted. Where and how do I serialize the idoc processing?
    --- AKJ

    Hi,
    This issue is basically at ur receiver IDoc side, when its getting processed.
    To ensure, ur IDoc 2 gets processed only after IDoc 1, changes can be done during message mapping.
    During mapping, inside control records of target IDoc, there is an 'serial' field. Fill this 'serial' field with a new unique number which increases with each and every new IDoc creation.
    This serial field with increasing number will be used during processing of IDocs in a sequence.
    Refer SAP Note - 752194 & 152239 for more details..
    Please let me know if still there are any issues.
    Thanks,
    Anoop

  • Proxy to IDoc -  IDoc error 51

    Hi Experts,
    I am  working on the Proxy to Idoc interface . here message is successfully processed through SAP PI  but giving an error on IDoc side.
    Error : IDoc  status record  - 51
    Enter date in the format __/__/____
    I maintained the date format  as shown above and mapping is also working fine,  i can see the  correct data in  Sxmb_Moni (Receiver Payload). But some how when the data is send to  HCM  system,  IDOC is generating this error.
    Thanks in advance,
    Kiran

    Hi,
    "personnel number(s) could not be locked" comes when the employee is already being access by some other process or report while your interface was trying to access it.
    Have you used function module to like enque/dequeue to lock/unlock the employee? If yes then when the function module was trying to lock the pernr so that no one else can edit it simultaneously, it coulnt lock it and hence gave the error.
    Also Make sure that you are not accessing the employee via transaction PA20/PA30 while triggerinf IDoc from WE19.
    regards,
    Deepak.
    Edited by: Deepak  Shah on Feb 17, 2011 10:31 AM

  • ABAP Proxy or IDOC Adapter?

    Hi all,
    In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
    1. Oracle ->PI ->SAP R/3
    Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
    2.VAN->PI->SAP R/3
    VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver  shall i go for IDOC Adpter or ABAP proxy?
    3.SAP->PI->VAN
    Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
    Please suggest me which one is better in all the scenarios.
    How to decide which is better for the above scenarios?
    Thanks In advance
    Venkatesh

    >
    venkatesh bs wrote:
    > Hi all,
    >
    > In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
    >
    > 1. Oracle ->PI ->SAP R/3
    > Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
    >
    > 2.VAN->PI->SAP R/3
    >
    > VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver  shall i go for IDOC Adpter or ABAP proxy?
    >
    > 3.SAP->PI->VAN
    > Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
    > Please suggest me which one is better in all the scenarios.
    > How to decide which is better for the above scenarios?
    >
    > Thanks In advance
    >
    > Venkatesh
    Material Master - MATMAS
    Invoice - INVOIC01
    PO - ORDERS
    wouldnt the above IDoc suit you?

  • Need the approach for passing source to proxy and idocs

    Hi PI mates,
    i  was struck in implementing one scenario.here is my scenario..i am getting source message (webservice call) and i need to pass it to table fields and as well standard idocs at the same time...for updating tables we are going with proxy.any how idocs will get update once we pass message.My question is how to go this approach..? we can create 2 structures at target  but we dont have any conditions for routing .
    is there any approach..pls light me.
    thanks in advance,
    Loordh

    Hi Loordh
    If you have an option of suggesting a change in SAP, this scenarios can be handled easily in SAP (ABAP).
    I have seen cases when SAP does internal IDOC posting .So its possible for them to receive as proxy and call the FM to update the tables and  IDOC creation/posting at the same time provided the structure you are using have all the fileds to create IDOC and update tables.
    Else if its not an option open for you then you can create 2 operations mapping and call them in interface mapping ,standarted Interface determination should work given timing of posting is not very critical here(may be a sec or two delay in operations)
    Best Regards
    $rinivas

  • ABAP proxy - XI - IDOC

    Hi,
    I built a new interface: ECC ABAP proxy - XI - CRM IDOC and tested it in DEV systems(ECC, XI, CRM) - it works well. I transport it to QA systems(ECC, XI, CRM). Everything  seems OK, but when I do Proxy test from ECC QA system, I don't see message in XI QA. I receive - Services Processed Without Error
    This ECC QA client was copied from ECC PROD client.
    What definition I have to check in ECC QA system?
    Thank you, Natalia.

    Hi,
    to see where your message is going,
    execute the transaction SXMB_ADM,
    select Integrtion Engine Configuration and check the RFC details.
    The role of business system should be application system
    and below that you have the RFC destination for integration system.
    Just check if this RFC destination is pointing to XI QA.
    I think this solves your problem.
    Regards
    Pushkar Anand

  • Error in receiver determination - Client proxy to IDOC using PI-IS

    Hi,
      I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    I am using the standard SAP message interface in the sproxy.
    Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
    Thanks,
    Menaga

    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    The above error occurs due to:
    1) You have configured a wrong receiver service in the Receiver Determination
    2) You have configured the correct receiver but the cache is not updated
    So check if the receiver service exists and the cache is updated.
    Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
    be created without DT".
    Check if you get any lead from this thread:
    Failed to time to generate proxy - TRX SPROXY
    Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
    Regards,
    Abhishek.

  • Wheh to use abap proxy and when to use idoc

    Hi All,
    Please provide some clarifications for the below points :
    What is Sproxy?
    2.     Why we are using Sproxy instead of Idocs
    3.   When we are going Proxy ?
    4.   What are the types of proxy ?
    5.   How to Create to Proxy ?
    6.   What the Difference between SProxy  and Idocs
       7.   What is SOAP file? When we are using SOAP file ?
    Thank you.
    Regards,
    Bharat

    Hi Bharat,
    You seem to have a range of Questions. I will try and answer as many as possible.
    What is Sproxy?
    SPROXY is a transaction [T-Code] on the SAP ECC/CRM etc side where you can see the objects designed in SAP PI ESR and develop its corresponding ABAP code. SPROXY T-Code displays the Service Interface. You can read more about it in the following site:
    **************** - XI - ABAP Proxy communication
      2.     Why we are using Sproxy instead of Idocs
    For Certain implementations Standard IDocs may not be available and it is quite tedious to create a Z- IDoC and therefore it is advantageous to use Proxy. You can read more about this doubt in the following links:
    Choosing to use IDOC standard or ABAP Proxy?
    IDOC vs Proxy
    ABAP Proxy Vs IDOC
    3. When we are going Proxy ?
    When there are no Standard IDocs available. Please refer above links to get an answer for this.
    4.   What are the types of proxy ?
    5.   How to Create to Proxy ?
    Again the following link has the answers for both these questions:
    **************** - XI - ABAP Proxy communication
    6.   What the Difference between SProxy  and Idocs
    Difference is in the way the communication happens. Standard Idocs are already provided and you can use them directly while Proxy you will require to write the code on ECC side. You can refer the following link to understand more:
    Advantage of ABAP proxy over BAPI
    7. What is SOAP file? When we are using SOAP file ?
    I have not heard of anything called SOAP file. SOAP is a protocol used for communication and you can send files as attachment in your SOAP to Any(file/idoc/Soap etc) or vice Versa Interfaces. Infact Proxy itself is SOAP based communication with XI 3.0 Protocol.
    Please explore SCN to know more about the various scenarios. There are endless possibilities in SAP PI.
    Hope this Helps.
    Thanks &  Regards,
    Tejas Bisen

  • Regarding Error handling and customisation in RFC, Idocs and Proxy

    Hi,
    I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
    Please let me know in detail if possible.
    Regards,
    Sampada

    Hi ,
    Check this blog to know when to use which adapter:
      /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    we use proxy in sap 6.0 version or higher.
    Basically used for adapter less communication
    & very high volume of data has to be transfered.
    Step for Configuration fo IDOC in R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
                                                                                    Regards,
                                                                                    Vinod.

  • Idoc to Proxy Scnerio

    Dear All ,
    We are having one ECC--PI-SUS Scneriao . We triggering an Idoc from ECC named "Z_CREMAS_SUSMM.CREMAS03" and on receiver side having Inbound Proxy. Idoc is getting successfully trnasfered from ECC to Pi but in PI Sxmb_moni we are getting below error "<SAP:Code
    area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code">.
    When we test the payload in INtegratation Directory using      test configuration it successfully passes all the steps mention.
    Please help.

    Hi,
    Have you gone thru these links below?
    error message : RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC
    RCVR_DETERMINATION -  NO_RECEIVER_CASE_ASYNC
    NO_RECEIVER_CASE_ASYNC
    NO_RECEIVER_CASE_ASYNC
    RCVR_DETERMINATION
    RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC
    Please also search SCN before asking this commonly asked question. If you did search. Copy the links that you used and which links did not resolve your issue.
    Regards,
    Jannus Botha

  • RFC or IDOC or ABAP Proxy

    Hi,
    What is the best way(R3 Side) for standardization?
    R3 <-> Legacy.
    I've read all related article on sdn, but i am not still clear on which best way RFC or ABAP Proxy or IDOC in real life.
    if you are, what is suggestion?
    thanks
    dennis

    Ogawa,
    There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
    <i><b>RFC and Proxy:</b></i>
    RFC/BAPI has its own overhead of function call.
    Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
    ABAP Proxies uses Webservice and Http Protocols.
    If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
    <i><b>Proxy and Idoc:</b></i>
    IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
    Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
    This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
    Also go through this urls which may help you:
    /people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
    RFC VS PROXY
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    Re: IDOC and RFC
    Re: Proxy Vs IDOC
    ---Satish

Maybe you are looking for