IDoc Tunneling and XML_CONVERSION

Hi,
I'm developing a File 2 IDoc / IDoc 2 File Scenario.
The Partner who receives and send files wants to use the idoc flat table structure.
I noticed that wasn't so easy to convert IDoc XML to flat file, till i found IDoc Tunelling which perfectly fits my scenario!
The research i've done, explains that we just have to set the IDOC / XML_CONVERSION  parameter:
Possible Values
<i>'0' Every IDoc is saved as a table; no IDoc-XML conversion
'1' Every IDoc is converted to IDoc-XML
<b>'2' An IDoc is converted to IDoc-XML if requested by the service</b></i>
But, setting value to '2', how can i control if i want or not Xml conversion to occur? Is a setting made in R/3 or XI?
I have scenarios where i really need XML (to use mapping features). Value 2 looks perfect, but where is this controlled?

Hi Jose,
Sounds good idea and approach..
Check out this blog by Michal..you will get all your answer on idoc tunelling..
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Hope this will help.
Let me know if you need more details.
Nilesh

Similar Messages

  • IDoc tunneling (Parameter  XML_CONVERSION)

    The parameter in the SXMB_ADM transaction defines whether the IDoc is transported as a table and is not converted to IDoc-XML in the IDoc adapter. This is only recommended if IDocs are received and sent as IDocs in the Integration Server. If none of the services in the Integration Engine use IDoc-XML, you can avoid unnecessary conversion from and to XML, thereby improving system performance.
    Possible Values
    '<b>0</b>' Every IDoc is saved as a table; no IDoc-XML conversion.
    '<b>1</b>' Every IDoc is converted to IDoc-XML.
    '<b>2</b>' An IDoc is converted to IDoc-XML only <i>if requested by the service</i>.
    The question is: does anybody know what "<i>if requested by the service</i>" exaclty means ?
    Regards,
    Sandro

    Think about a scenario SAP-XI -JMS (or Flat file) vice versa . I will do the transformation with ABAP-Mapping in both direction and theres no need for receiveing an XML-Stream from IDOC-Adpater or send an XML-stream to IDOC-Adpater.
    We would receive a better performance if we could avoid the expensive XML-Transformation.
    There is a check of an existing Mapping for Sender-Message in the Table SMPPREL3 .
    There could be an special XML-flag in this Table and in the Receiver-Determination you could set this flag or not . 
    XI uses CL_IDX_IDOC_RESOURCE for the IDOC-Tunnel. In this class  EDIDC and EDIDD are serialized in an XSTRING . In my ABAP-Mapping first i would check Content_Type via  PARAM->GET.  For transforming the binary Content into  EDIDC and EDIDD a static method should be implemented by SAP in CL_IDX_IDOC_RESOURCE  . I think I could implement such a method myself, but its risky if SAP changes their ITAB_TO_BINARY-method in an incompatible way.  
    In the XI-SAP -direction  I would like  to set the content_type in ABAP-Mapping to bin and convert the EDIDC and EDIDD  in X-string  (like in CL_IDX_IDOC_RESOURCE ->ITAB_TO_BINARY ).
    Regards Josef

  • Idoc to idoc scenario with idoc tunneling

    IN idoc to idoc scenario with idoc tunneling  the XML_CONVERSION parameter to value 2  is set whish means An IDoc is converted to IDoc-XML if requested by the service
    I want to know where we specify this and how we specify?

    1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
    ref these weblogs.
    It is given under;
    <i>TCODE - SXMB_ADM
    - Integration Engine configuration
    - set the XML_CONVERSION parameter to value 2</i>

  • IDoc Tunnelling

    All,
       I was going through the Michals Blog for IDoc tunnelling and I'm little confiused here. As per the blog,
    setting the "XML_CONVERSION parameter to value 2" enables the IDoc tunnelling.
    1) Does all the IDocs coming out of R3 will be in the flat file format.
    2) Also the blog says as per SAP help "2 - An IDoc is converted to IDoc-XML if requested by the service" - Can someone tell me what service request that we need to use for IDoc - XML conversion with a value of 2?
    Thanks.

    My question is
    1) if we set the XML_Conversion parameter to 2, are all the IDocs coming out of ECC will be in the flatfile   
       format?
    2) If all the IDocs coming into XI are flatfile's, what service do we need to request for the IDoc to be in IDoc XML format with the XML_Conversion parameter set to "2"
    Thanks.

  • IDOC "Tunneling"

    Hello all,
    We are currently implementing a IDOC->XI->JMS scenario.
    We would like to use the IDOC Tunneling option:
    SXMB_ADM -> Integration Engine Configuration
    IDoc -> XML Conversion = 2 or 0
    2 questions:
    When setting the XML_Conversion parameter to 0 XI seems to be ignoring our request and the IDOC is still being converted to XML.
    Does anybody have any idea why this happens?
    When setting the XML_Conversion parameter to 2 how do we get the service NOT to request the IDOC conversion?
    Thanks in advance.
    Claus

    Hi Holger,
    Thank You for Your answer.
    We have tried the IDOC->XI->IDOC scenario.
    However the payload shows that the IDOC is converted to XML.
    Can we expect to see a non-converted IDOC in the payload if we use the XML_CONVERSION parameter value 0 or 2?
    Regards
    Claus Borre Nielsen

  • IDoc-Tunnel - IDoc is rejected

    Hi guys,
    well i have an internal EDIserver which will send IDoc native via XI (IDoc-Tunnel) to a R/3 target System. Therefore for EDIserver a RFC-Destination of type TCP/IP exists where a registered Serverprogram is applied, also with given gateway values from the XI-System.
    After configuring an IDoc-Channel in the Integration Directory the testing of the SM59 RFC-Destination works fine. Well because of Michal's Blog for IDoc-Tunneling i already did the configuration of the integration engine (XML CONVERSION).
    Ok i imported the IDocs in IR, announced them in IDX2 and did the ID-Part with Sender-Agreement and so on.
    But when we try to send an IDoc from EDI to XI we get following error:
    <i>rfc_error_info.message="No service for system SNDPOR, client 100 in Integration Directory"</i>
    The EDI-Consult thinks that he needs the Header-data from the IDoc like RCVPOR, RCVPRT, RCVPRN but i think we don't.
    So where could be the problem?! perhaps at the registered server program of the EDIServer?!
    br

    Hi Udo, thx for ur reply.
    Well that might be the problem. I have applied an EDI_Test in SLD for EDIServer but the EDI-Consultant might not have used this field so that there is a standard value in it (SNDPOR) which indicates what kind of info is needed there.
    So he should enter EDI_Test for let XI accept the IDoc when it is posted!
    br

  • IDoc-Tunneling -- No Receiver Agreement

    Hi, i am trying to do the IDoc-Tunneling scenario from Michal.
    Well everything looks fine so far except that i get following error:
    +<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="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>-Q01CLNT010</SAP:P1>
      <SAP:P2>0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -Q01CLNT010 zum Empfänger 0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01 gefunden werden</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>+
    Well i have Receiver Agreement that looks like:
    Sender Service: Q01CLNT010
    Receiver Service: EDI
    Interface: DELFOR.DELFOR02
    Namespace: urn:sap-com:document:sap:idoc:messages
    CC: IDOC_RECEIVER_EDI
    In this Receiver-CC i also activated
    - Apply Control Record Values
    - Take sender from payload
    However, i have no clue what is wrong.
    Can somebody help? br Jens

    Hi Jens
    (6) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
    The problem is in Technical routing.
    Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
    check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
    Please refer the follwoing blog for details
    <b>/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Thanks
    AbhishekMahajan
    *****Please reward points if helpful*********

  • ASA 5505 site-to-site VPN tunnel and client VPN sessions

    Hello all
    I have several years of general networking experience, but I have not yet had to set up an ASA from the ground up, so please bear with me.
    I have a client who needs to establish a VPN tunnel from his satellite office (Site A) to his corporate office (Site Z).  His satellite office will have a single PC sitting behind the ASA.  In addition, he needs to be able to VPN from his home (Site H) to Site A to access his PC.
    The first question I have is about the ASA 5505 and the various licensing options.  I want to ensure that an ASA5505-BUN-K9 will be able to establish the site-to-site tunnel as well as allow him to use either the IPsec or SSL VPN client to connect from Site H to Site A.  Would someone please confirm or deny that for me?
    Secondly, I would like to verify that no special routing or configuration would need to take place in order to allow traffic not destined for Site Z (i.e., general web browsing or other traffic to any resource that is not part of the Site Z network) to go out his outside interface without specifically traversing the VPN tunnel (split tunneling?)
    Finally, if the client were to establish a VPN session from Site H to Site A, would that allow for him to connect directly into resources at Site Z without any special firewall security rules?  Since the VPN session would come in on the outside interface, and the tunnel back to Site Z goes out on the same interface, would this constitute a split horizon scenario that would call for a more complex config, or will the ASA handle that automatically without issue?
    I don't yet have the equipment in-hand, so I can't provide any sample configs for you to look over, but I will certainly do so once I've got it.
    Thanks in advance for any assistance provided!

    First question:
    Yes, 5505 will be able to establish site-to-site tunnel, and he can use IPSec vpn client, and SSL VPN (it comes with 2 default SSL VPN license).
    Second question:
    Yes, you are right. No special routing is required. All you need to configure is site-to-site VPN between Site A and Site Z LAN, and the internet traffic will be routed via Site A internet. Assuming you have all the NAT statement configured for that.
    Last question:
    This needs to be configured, it wouldn't automatically allow access to Site Z when he VPNs in to Site A.
    Here is what needs to be configured:
    1) Split tunnel ACL for VPN Client should include both Site Z and Site A LAN subnets.
    2) On site A configures: same-security-traffic permit intra-interface
    3) Crypto ACL for the site-to-site tunnel between Site Z and Site A needs to include the VPN Client pool subnet as follows:
    On Site Z:
    access-list permit ip
    On Site A:
    access-list permit ip
    4) NAT exemption on site Z needs to include vpn client pool subnet as well.
    Hope that helps.
    Message was edited by: Jennifer Halim

  • Transparent Tunneling and Local Lan Access via VPN Client

    Remote users using Cisco VPN 4.2 connect successfully to a Cisco Pix 515 (ver. 6.3). The client is configured to allow Transparent Tunneling and Local Lan access, but once connected to the Pix, these two options are disabled. What configuration changes are required on the Pix to enable these options? Any assistance will be greatly appreciated.
    Mike Bowyer

    Hi Mike,
    "Transparent Tunneling" and "Local Lan Access" are two different things. "Transparent Tunneling" is dealing with establishing an IPSec Tunnel even if a NAT device is between your client and the VPN-Headend-Device. "Local LAN Access" is dealing with access to devices in the LAN your VPN-Client-Device is connected to.
    What do you mean exactly with "disabled once the connection is made" ?
    You can check the local LAN Access by having a look at the Route-Table of the VPN-Client:
    Right Click the yellow VPN-lock Icon in System-Tray while the VPN-Connection is active and select "Statistics ...". Have a look at the second register page "route details".
    Are any local LAN routes displayed when your are connected ?
    And - always remember two important restrictions the Online Help of the VPN-Client is mentioning:
    1: This feature works only on one NIC card, the same NIC card as the tunnel.
    2: While connected, you cannot print or browse the local LAN by name; when disconnected, you can print and browse by name.
    Carsten
    PS: Removing Split Tunnel won't enable local LAN access as all traffic would be sent into the IPSec tunnel.

  • R/3 to XI manually IDOC sending and problem:

    <u><b>R/3 to XI manually IDOC sending and problem:</b></u>
    I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    I check XI (sxmb_moni) but there is nomessage there.
    <b>Problem 1:</b> I don't want R/3 ask me UID and password for XI access
    <b>Problem 2:</b> I want to see message in XI (sxmb_moni)
    Thanks

    Hi Cemil,
    >>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    check the RFC destination from R3 to XI (SM59)
    you will find the right one from your port (We21)
    you can also check step by step procedures
    for IDOC - XI in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Compare two Idoc's and send to te recievers as per the Condition.

    Hi,
    Scenario: Sender are a Idoc's and Receiver is Mail and File.
    Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2. If the Condition satisfy send the data to file and mail reciever else send to only mail reciever.
    I tried using a BPM. Steps used in BPM are as follow:
    Step: 1
    Fork -- with two branches.
    Branch 1:loop1-- reciever1 -- container
    Branch 2:reciever2
    Step2:
    Switch with two branches: Check the compare condition of the two Idoc
    Branch 1:
    Fork with two branches with send step with mail and file recievers
    branch 2: Only mail reciever.
    However if the condition is true or false the information is send mail to reciever.
    I tried with the above steps, but failed.
    Any changes required, please let me know.
    Regards,
    Manoj

    sumit,
    I recieve N number of IDOC1. I need Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2.
    I tried using a BPM . Steps used in BPM are as follow:
    Step: 1
    Fork -- with two branches.
    Branch 1:loop1-- reciever1 -- container
    Branch 2:reciever2
    Step2: Transfomation with Mapping program, source and Target message
    Step3:
    Switch with two branches: Check the compare condition of the two Idoc
    Branch 1:
    Fork with two branches with send step with mail and file recievers
    branch 2: Only mail reciever.
    When i checked with workflow i observe that that the message is not moving out of transformation step.But the message mapping is succesfully tested
    Thanks,
    Manoj

  • LSMW - Report to get IDOC failures and its external reference number

    Hi All,
    I'm currently using LSMW for data migration in CRM, for Business Partner and transaction data.
    I need to generated a report which covers the idocs which have failed and the external identifier for which it has failed. Currently the IDOC reports that are available OOB provide the IDOC number and the reason for failure. It will be great if I can get the external identifier of the transaction as well.
    I searched for a report in SAP but could not find any which gives this functionality.
    Please advice.
    Thanks in advance.

    Hi,
    1.)If you want the ouput in the same report program which triggers the idoc, it is better to use the control record information.
    You will get IDoc Number from XEDIDC(check the below code) and you can store the idoc number into an internal table if more idoc is expecting to be triggered.
         call function 'MASTER_IDOC_DISTRIBUTE'
              exporting
                MASTER_IDOC_CONTROL        = EDIDC
              tables
                COMMUNICATION_IDOC_CONTROL = XEDIDC
                MASTER_IDOC_DATA           = XEDIDD
              exceptions
                others                     = 5.
       read table xedidc index 1.
      append xedidc-docno to it_docno.
    And finallly use this to display in the output.
    2.) if u want it in a seperate report, then select based on date, idoctype, messagetype
    Regards,
    Sajith

  • Need IDOC inbound and outbound programs

    hi,
    i am new to xi.
    i want IDOCs , inbound and outbound / function module  programs for    PURCHASE ORDER
    and GOODS RECEIPT.
    ex:  BD10 for material master (matmas01).
    thanks and regards
    v ijender

    for purchase order.
    ORDERS / ORDERS04
    ORDCHG / ORDERS04
    ORDRSP / ORDERS04
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    and also check the below link
    http://www.erpgenie.com/sapedi/message_types_masterdata.htm
    regards
    kummari

  • Urgent - Idoc type and the Message type

    Hello
    Its very urgent. I want to know the basic idoc type and the message type used for EDI 894 transmission (Delivery / Return Base Record). Please respond at the earliest.
    Thanks in advance

    HI
    Pratibha
    How are you ?
    Please check the below links:
    http://scn.sap.com/thread/990524
    http://www.erpgreat.com/pm003.htm
    http://scn.sap.com/thread/1386811
    http://scn.sap.com/thread/1078741http://www.erpgreat.com/plant/what-is-equipment-master.htm
    http://benxbrain.com/en/index.do?onInputProcessing%28brai_object_thread%29&001_threadid=0000835100&001_boardtype=01&sysid=PI1&pgmid=R3TR&object=TABL&obj_name=EQBS&child_param=
    Mutti

  • IDOC number and status

    Hi All,
    i am using Function Module IDOC_INBOUND_ASYNCHRONOUS to post inventory records.
    its posting the data sucsessfully but it does not return IDOC number and status.
    i can see the status and number in WE02 but please tell me how can i get that in my program.
    Thakns and regards
    Pankaj

    Hi friend,
           U can get the status and number of IDOC in WE05 and WE07.
           Once u get the number of IDOC got to table EDIDC(Control Rec table),
           EDID4(Data Rec table) and EDIDS(status Rec table) to get the information
           related to status and content of idoc.
           Directly, u can specify it in ur program as Tables:EDIDC,EDID4,EDIDS
           and get the info according to ur idoc number.
    Thanks N Regards,
            Manian.

Maybe you are looking for