Receive idocs from SAP in XML format

Hi everyone.
Currently, to receive idocs, what we're doing is, we create an external RFC server, and listen to invocations of the RFC IDOC_INBOUND_ASYNCHRONOUS and IDOC_PROCESS_INBOUND. However, this leads us to receive idocs in EDI_DD/EDI_DD40 and EDI_DC/EDI_DC40 formats.
Is it possible to receive idocs in XML format via the RFC Server interface?
Thanks,
Mustansir

hi shreya,
function Module            Short text for function mod
HR_BE_DMFA_XML_DOWNLOAD    Register XML conversionca
    HR_PT_TAX_XML_DOWNLOAD
SDOK_LOIO_XML_DOWNLOAD_PUBLISH
SPRX_XML_DOWNLOAD              Displaying the Payload
DMEE_DOWNLOAD_XML_TREE
DMEE_DOWNLOAD_XML_TREE_ABA     DMEE: Download format tree
JITOUT10_DOWNLOAD_XML
GLOS_DOWNLOAD_XML
this function module you can use.
regards,
sandeep
Edited by: Sandeep patel on Jul 7, 2008 6:36 PM

Similar Messages

  • Warnings while receiving IDOC from SAP

    Hi All,
    I am running BTS 2010. I configured recieve location to recieve ORDERS05 Idocs. But I am receiving below mentioned warning.
    1) In SAP the Idoc shows as successfully sent
    2) On the BizTalk side we cannot find the Idoc anywhere
    3) In the EventLog of our BTS we get the following errors (the errors are raised exactly at the same time when the Idoc which “disappears” is sent from SAP to BizTalk )
    Error 1:
    Event Type: Warning
    Event Source: BizTalk Server 2010
    Event Category: (1)
    Event ID: 5740
    Date: 1/10/2014
    Time: 12:38:59
    User: N/A
    The adapter "WCF-Custom" raised an error message. Details "Microsoft.ServiceModel.Channels.Common.XmlReaderGenerationException: The segment or group definition E1234 was not found in the IDoc metadata. The UniqueId
    of the IDoc type is: IDOCTYP/3/ORDERS05//700. For Receive operations, the SAP adapter does not support unreleased segments.
       at Microsoft.Adapters.SAP.TypedIdocBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
       at System.ServiceModel.Channels.BodyWriter.WriteBodyContents(XmlDictionaryWriter writer)
       at System.ServiceModel.Channels.BodyWriterMessage.OnWriteBodyContents(XmlDictionaryWriter writer)
       at System.ServiceModel.Channels.Message.WriteBodyContents(XmlDictionaryWriter writer)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessageStream(Message wcfMessage, IAdapterConfigInboundMessageMarshalling config)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessage(IBaseMessageFactory messageFactory, IAdapterConfigInboundMessageMarshalling marshallingConfig, Message wcfMessage)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkSubmitMessage(IBaseMessageFactory factory, String inboundTransportLocation, String inboundTransportType, RLConfig config, Message wcfMessage,
    String ssoToken)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmitBase..ctor(Message message, BizTalkEndpointContext endpointContext, ControlledTermination control, AsyncCallback realCallback, String ssoToken)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmit..ctor(Message message, AsyncCallback callback, Object state, BizTalkEndpointContext endpointContext, String ssoToken, ControlledTermination control)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkOperation.Create(Message message, AsyncCallback callback, Object state, String ssoToken, Boolean bizTalkOneWay, BizTalkEndpointContext endpointContext, ControlledTermination
    control)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.BeginOperation(Message message, AsyncCallback callback, Object state, Boolean bizTalkOneWay)".
    Error 2:
    Event Type: Warning
    Event Source: BizTalk Server 2010
    Event Category: (1)
    Event ID: 5740
    Date: 1/10/2014
    Time: 12:38:59
    User: N/A
    The adapter "WCF-Custom" raised an error message. Details "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_INVALID_HANDLE. AdapterErrorMessage=An exception has occurred on the listener while executing
    RfcWaitForRequest..
       at Microsoft.ServiceModel.Channels.Common.Design.AdapterAsyncResult.End()
       at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& requestContext)
       at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1.System.ServiceModel.Channels.IReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& context)
       at System.ServiceModel.Dispatcher.ReplyChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
       at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)".
    Error 3:
    Event Type: Warning
    Event Source: BizTalk Server 2010
    Event Category: (1)
    Event ID: 5740
    Date: 1/10/2014
    Time: 12:38:59
    User: N/A
    The adapter "WCF-Custom" raised an error message. Details "The WCF service host at address sap://CLIENT=100;LANG=;@a/SAPD.corp.int/10?ListenerDest=BIZTALKD&ListenerGwServ=sapgw10&ListenerGwHost=SAPD.corp.int&ListenerProgramId=BIZTALKD&RfcSdkTrace=False&AbapDebug=False
    has faulted and as a result no more messages can be received on the corresponding receive location. To fix the issue, BizTalk Server will automatically attempt to restart the service host.".
    Error 4:
    Event Type: Warning
    Event Source: BizTalk Server 2010
    Event Category: (1)
    Event ID: 5740
    Date: 1/10/2014
    Time: 12:38:59
    User: N/A
    The adapter "WCF-Custom" raised an error message. Details "System.ServiceModel.CommunicationObjectFaultedException: The communication object, Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1[System.ServiceModel.Channels.IReplyChannel],
    cannot be used for communication because it is in the Faulted state.
       at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Close()
    at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.Close()".
    http://social.msdn.microsoft.com/Forums/en-US/57a18e78-d902-4a39-a99f-95ef732792f7/adapter-pack-20-sap-adapter-problem
    As per the replies in the above link i made the changes but still warning continues.
    Please suggest
    Thanks,

    The IDOC has not arrived in BizTalk, that's why you do not see it. The problem is that the IDOC fails at adapter level, when the SAP RFC Library is called.
    The actual problem is that the IDOC you are receiving is containing unreleased segments and that's not supported, you should contact your SAP administrator to get this problem resolved.
    If I'm not mistaken it's transaction WE30 in SAP, there you have to select the IDOC type (ORDERS05 in your case) and then you can set the release. But your SAP administrator will probably know better how to do this
    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

  • Send idocs to SAP in SAP's XML format

    Hi!
    currently we are sending idocs to SAP using the RFC IDOC_INBOUND_ASYNCHRONOUS. this requires us to break up the data so that we can populate rows in the EDI_DC40 and EDI_DD40 table.
    Is it possible, via a RFC call, (or rather, via some programmatic interface if via RFC is not possible) to send idocs to SAP in XML format?
    Thanks,
    Mustansir

    Hi Satish,
    Thanks for the reply. Do I need to do event driven message processsing in XI for this? The other way is to schedule the RBDAPP01 in R/3 to post idocs in sequence based on the message type and Partner number
    Does this makes sense?
    And any idea bout the second question for roll back?
    Thanks

  • In sap 4.7 ver i want to  dispatch an Idoc through http in xml format

    Hi
    Here i am giving the brief scenario of about my
    requirements "::::
    Our organization need to receive an IDoc through
    HTTP into XML format  then we have to send an acknowledgement  back to USA (external  system
    located)
    then we hav eto process tha tIDoc an dsend it back
    to the edi 850 ...
    we are not using Sap Business Connector
    Plz send the suggestions as soon as possible
    I really appreciated if u can give the suggestions
    regarding my  business scenario ..
    without using any thirdparty tool in sap 4.7 version it is possible how can i do that ??
    Thanks & Regards ,
    bak

    The exact error message I'm getting is :
    ABAP XML formatting error in XML node of type "element", name: "abap"

  • Receiving IDocs from non-SAP system ...

    Hello guys,
    I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
    Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
    In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
    Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
    Thank you in advance!
    Regards
    Zbynek

    Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
    The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
    05/29/09 16:09:19.482 idoup2 Logon...
    05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
    05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
    05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
    05/29/09 16:09:19.607 idoup2 Handle=1
    05/29/09 16:09:19.607 idoup2 key............:
    05/29/09 16:09:19.607 idoup2 status.........:
    05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:19.607 idoup2 internal status:
    05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
    05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
    05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
    05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:20.607 idoup2 internal status:
    05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
    05/29/09 16:09:21.607 idoup2 Logoff...

  • Is it possible to receive IDOCs from a non-SAP system?

    Hi,
    I'm facing a problem where I have to configure SAP MII (12.0) to receive IDOCs from a non-SAP client. Is it possible? I'm dealing with a system named Hydra (developed by MPDV) and I'd like to know what I should configure in Hydra systems in fields like: PROGID, GWHOST, GWSERV, SYSNR, CLIENT etc.
    Anyone can help me?
    Thanks a lot in advance

    Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

  • Post Idoc from SAP to Thirdparty using XI

    Dear Friends,
      My requirement is sending the Idoc from SAP to Thirdparty system,but Thirdparty system also receive the Idoc format only.
    so IDoc to Idoc scenario but SAP to Thirdparty system it is possible or not.
    please tell me how ?
    Regards,
    Shalini Shah

    You can use SAP Business Connector(BC) to convert IDOC to IDOC-XML at the third party legacy system.
    With Business Connector see the below links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://www.erpgenie.com/mysap/bus_connector.htm
    WAS - Business Connector
    business connector documentation
    SAP Business Connector
    Business connector
    Will Business Connector 4.6 be affected by new  Daylight savings changes
    Business connector
    More info on XI can be found at https://service.sap.com/xi
    and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
    Check this also-
    http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm

  • How to Trigger an IDOC from SAP R/3 to two systems at a time

    Hi experts,
    Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
    My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
    I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
    Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
    Can any one tell me how can we do that ?
    Regards
    Ram.

    Hello Ram,
    Do you have connectivity between your production & XIQ?
    What does "connectivity" mean?
    1. RFC destination is maintained.
    2. Port defined for the RFC destination.
    If no, create these. (Search in SDN for details).
    If yes, proceed:
    1. Define the logical system for XIQ.(BD54)
    2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
    3. Create a distribution model view with sender as "your production" & receiver as XIQ.
    3.1. Add the messages which you want to distribute.
    3.2 Generate Partner profiles.
    No coding is reqd. for this.
    BR,
    Suhas

  • Problem in  Outbound IDOC from SAP R/3

    Hi,
    I am working on to send an IDOC from SAP R/3 to XI.
    I configured all necessary things as follows:
    1. Created for XI in sender system -- RFC dest, PORT and a partner profile with an outbound parameters and reciever port as XI port.
    2. created for sender system in XI -- RFC dest, PORT(as SAP<SID>) in IDX1 and assigned an idoc type(coming from sender system) to the port.
    Now I am trying to push the IDOC from sender system using Test IDOC transaction and gets success message as data is passed to port.
    My problem is I am not able to see any message in SM58 of XI server.
    Could anyone help me out?
    Thanks In Advance.
    Yaseen.

    Yasseen,
    you hardly see the idocs in Xi in sm58. Try sxmb_moni.
    If you see anything there try sm58 on the sending R/3. There you see if you have connection problems (eg authorization in XI or missing receiver determinitions).
    Hope it hellps,
    helge

  • Problem when pushing IDOC from SAP to XI

    Hi,
        I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

    Hi,
    It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
    Can u check Receiver Determination  created in the XI once again. And also check for RFC destinations created in the R/3.
    Hope it helps ..
    -Moorthy

  • Send IDOC from SAP system to IX but can't see any message in SXI_MONITOR

    Hi all,
    I have built up an XI system and configured an IDOC to IDOC scenario between two SAP Systems. After completed all configuration necessary:
    1. Configuration on Source Side (SAP System that send IDOC) and on Target Side (SAP System that receive IDOC) is OK.
    2. SLD is OK: Technical System and Business System are correct for these two SAP System.
    3. Integration Repository: all designed Object is OK.
    4. Integration Directory: all configuration is OK. "Test Configuration" Function is OK.
    5. Runtime WorkBench: is OK. "Test Message"  Function of "Integration Server" is OK.
    In general, it is all OK.
    But when i send an IDOC from SAP System Sour Side (Outbound IDOC from Source Side is OK), on the XI server i can't see any message in Tcode SXI_MONITOR. In this case, my XI server didn't receive any IDOC Message from  this Source Side, and so that my XI server can't process and exchange any IDOC sent from Source Side.
    Anyone can please help me to explain this problem: why my XI server can't receive any IDOC message from SAP System Source Side when all configuration is OK? Do anyone see the same case as this case?
    Thanks a lot for all in advance,
    Best regards,
    Vinh vo

    Hi,
    Possible checks
    At R/3 side
    1) Check in SMQ1 and SM58
    At XI Side
    1) Check in SMQ2 and IDX5
    Check this
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
    Regards
    Seshagiri

  • Missing IDOCS from SAP to BODI

    I have an issue of missing idocs from sap going to BODI.
    Idocs are received by BODI trough adapter, but there are idocs that are missing but are successfully sent by SAP. When trying to resend the idocs it was successfully received by BODI.
    We thought that it is an intermittent connection issue, so we try to send idoc from SAP while the adapter was down. The idoc was successfully sent from SAP. Then we try to start again the adapter and it was loaded after sometime.
    Iu2019m now out of idea on why does the idocs went missing. Can someone help me?
    Thanks in advance.

    Hi Parida,
    IDoc Status 03...Green Status... wills not guarantee you that IDoc reached EDI subsystem...
    Run the Program RBDMOIND in SE38...
    Changed on                               :<Date>
    IDocs/Commit Work                   :100
    Display IDoc not sent- Check the Check Box.
    Now you will get list of un posted IDocs
    Ramesh

  • Limit send of IDoc from SAP-ERP to SAP-XI or a Non-SAP

    Hi guys,
    I send the following IDocs from SAP-ERP over SAP-XI to Non-SAP for an initialload: Artmas, Bommat, Infrec, Cond_a, Mmaddi, Cremas
    Example: Artmas with TA: BD10.
    Problem: SAP-ERP send all 25'000 IDoc to SAP-XI. The effect is that the qRFC and tRFC in SAP-XI is full, because the Non-SAP is not fast enough to takeover the Idocs. From then other systems can't send out or get in Idocs.
    I tried to limit in WE20, but it didnt work. TA: RSEOUT00 ist not so useful, because of the quantity of the IDocs.
    Is in SAP-ERP a possibility to limit the sending of IDocs to SAP-XI or Non-SAP?
    Example: Automatic sending of 200 Idocs every 2 Minute.
    Thanks

    may be u can write a wrapper above BD10 this way
    report zaRs message-id b1.
    select-options: matsel for marav-matnr matchcode object mat1.
    parameters: receiver like tbdlst-logsys no-display.
    start-of-selection.
      select * from mara into i_mara where matnr in matsel.
      refresh : matsel.  
      v_no = 0.
      loop at i_mara.
        move i_mara-matnr to matsel-low
    * fill up sign option etc.
        append matsel
      do.
       move mara
       if v_no = 200.
        submit rbdsemat  " Program behind BD10
              with logsys eq receiver
              with matsel in matsel
              with mestypat eq 'ARTMAS'
              and return.
              wait 20 seconds
        exit.
        clear v_no.
       endif.
      enddo.  

  • Ale settings when receiving idoc from xi

    Hi friends,
    I wan o confirm that the settings I had done in my R/3 system for receiving idoc from Xi are correct.
    Third party is goin to send message to my Xi system, from there I have to send that message to my R/3 system.
    In R/3 I had created 2 logical system,one for r/3 itself and other for my XI system.
    I assigned  client to this systems.
    I created RFC and port for XI.
    Then created distribution model, with sender as xi logical name ,receiver as R/3 logical name.
    Is this configuration correct?or I need to create the thirdparty logical system also in my R/3 system?

    Hi,
    Your steps looks fine to me. I think distribution model is not required for inbound case.
    just check the below configuration once again.
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Also look at the step by step process.
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    chirag
    Edited by: Chirag Gohil on Nov 24, 2008 1:23 PM

  • Idoc be converted into XML format

    Hi,
    Can  idoc be converted into XML format? If yes guide me the path , how to do?
    Thanks
    Avi

    <b>Hi,
    we can .
    Follow the link
    http://www.erpgenie.com/sap/sapedi/Conversion%20of%20IDOCs%20to%20XML%20format.pdf</b>
    Thanks
    Manju
    <u><b>Don't repeat the Questions</b></u>

Maybe you are looking for