Texts in IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202

Hello,
We are using the IDoc SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202 for creating Salesorders in our SAP R/3 system. We want to enter texts on header and on item lines in the salesorder with this IDoc. In the IDoc structure there is a segment for text called "E1BPSDTEXT" with different subsegments. I filled these fields with following data:
E1BPSDTEXT
- TEXT_ID       0001
- TEXT_LINE       Test Line 1
But when I took a look into the created salesorder, this text didn't appear. Has anyone an idea why this didn't work? Are these the correct fields to get text into a salesorder? 
Thanks for help.

Hi Stefan,
Thank you.Your solution was helpful.
Regards,
Dedeepya

Similar Messages

  • SALESORDER_CREATEFROMDAT2 / SALESORDER_CREATEFROMDAT202

    Hi,
    This is just requesting a general information / clarification on sales order inbound IDOC.
    We are in version ECC 6 and in the process of configuring inbound IDOC.  When we had a look on the relevant IDOC version, the SALESORDER_CREATEFROMDAT2 / SALESORDER_CREATEFROMDAT202 seems to be the relevant version. But when we check in the SAP notes or forums I can see lot are mentioned about the IDOC u2013 ORDERS / ORDERS05 and limited for SALESORDER_CREATEFROMDAT2.
    I understand that ORDERS05 is using the call transaction method and SALESORDER_CREATEFROMDAT202 is using the BAPI method, just wondering which IDOC to be used for our version and what would be the advantage on a long term basis like SAP support point of view etc.
    Also consider we are using heavily customised variant configuration in the sales order.
    Regards.

    Hi,
    I have no experience in this. However as 202 is the latest version, it is always better to go for that version.
    I would advise you to look both the versions, find out the difference between them in the segments used, fieds in the segments and the application of additional fields to your need. If you really need those fields which are only in 202, then you can go for it. Otherwise 2 or 202 is not going to make any difference to you for now. At later point of time, if at all you have to add some mroe fields to the segments, the latest version will be of much use to you. Hence my suggestion.

  • Transmitting text in IDoc

    Hello,
    I have a scenario wherein I have text object (like sales text in Material master) attached to an IDoc.
    I want to transfer text that the user enters (within SAP) via IDoc to XI. XI then need to call a webservice and post this text information to the webservice.
    Later the legacy application returns some text back and this needs to be mapped by XI to inbound Idoc which will be posted within SAP.
    Can you propose some protocol/mechanism to handle such scenario.
    I looked at the MATMAS03 Idoc. There we have segments E1MTXHM (long text header) and E1MTXLM (long text line). Within the E1MTXLM we have TDFORMAT which will take care of formatting the text.
    Now I need to put some logic in XI mapping or within legacy application to read these formatting information in IDoc and make full text lines out of it and post it into legacy application.
    Similarly in the inbound side the Legacy text needs to mapped to the incoming idoc (with proper codes filled in TDFORMAT) and posted into SAP.
    How feasible is this approach? Any other better way to handle text transmission?
    Any help in this regard is highly appreciated.
    Regards,
    Gajendra.

    >1) Where to put the logic for decrypting the text in idoc to proper text lines which legacy can understand and post.
    I dont understand this part. Data from IDOC is in text format only.
    In XI you can do data conversion (mapping) which is transforming the data in Sender format to a format readable by the receiver. There are different mapping techniques available. Use the one that suits you better.
    >2) On the inbound side somewhere we need to map the text which legacy sends into IDoc.
    Again this is done with in XI mapping.
    >3) Is this a good approach?
    Yes it looks to be. But this has to decided based on the business process. So I cant comment on this with out a good understanding of your business requirement.
    Regards,
    Jai Shankar

  • How to create customized long text in IDOC status record in WE02?

    Hi,
    In WE02 you can see the status of the idoc. If you double click on the short text that is coming in the status, you can see the long text. How do i customized my long text to that screen?

    To create a message long text in SE91:
        1. Place the cursor on the corresponding message.
        2. Click the Long text pushbutton.
        3. Enter the long text.
        4. Save the data.
    Edited by: YTL on Jun 27, 2011 5:51 PM

  • Problem in populating the delivery text in Idoc

    Hi Experts,
           We are using a custom EDI output type for VT02n transaction. Currently we are encountering a problem when we set the dispatch time as 'Send immediately'.
           The problem is some of the characters in delivery texts are missing in the segment of the idoc generated.
           The problem does not occur when we set the dispatch time as 'send with application own transaction'.
           But we did not do any coding based on the dispatch time.
           Please provide us suggestions to solve this problem.
    Regards
    K Arasu.

    Hi,
    Check whether you have maintained the condition records for output for the above combination & also the Print device in the Communication tab & Print immediately settings.
    If you haven't maintained the above, do the same & check.
    Thanks & Regards,

  • Qualifcation text in IDOC HRMD_A07

    Hi Gurus,
    We are able to trigger IDOC HRMD_A07 with message type HRMD_A. The integration switch between PA & PD is active (PLOGI Quali). Now whenever qualification is deleted, the idoc records only the object id of qualification. Is there any way for getting text of the qualification along with the object id.
    We are avoiding customization, hence please share only a standard way ( without abap code) to resolve the issue.
    Regards
    Minal

    Dear Minal,
    the idoc inbound process does not need a text for deletion, the key is sufficient, but I think your intension is something different.
    I asume you want the text to be part of the idoc for identification (nobody remembers the id of a qualification, but the description).
    In that case I have bad news.
    As the idoc creation process (e.g from change pointers) is executed after the deletion has taken place and change pointers do not contain data like text, no text is present anymore that could be added to the idoc.
    Regards,
    Michael

  • How to put long text by idoc into FB01?

    Hi,
    I am using Idoc ACC_DOCUMNENT to create FB01 transaction but there is place to put the long text for the item.
    Do you know how to update the long text using an Idoc?
    please do Not reply "try using function SAVE_TEXT".
    Thanks guys...

    I'm having what I think is a similar problem but haven't found a soulution...
    I have a phone number for a contact that is 41 characters long (it's numbers and a couple commas (",") for pauses.
    When I touch the number to have my iPhone dial it - the iPhone does nothing.
    If I touch other numbers for the same contact (that are shorter) - it works.
    Is there a maximum lengh for phone numbers?
    Or is there something I should do? (ie. is there a way to dial the first half, and then press something ?? that would have the iPhone dial the remainder of the number?)
    Thanks!

  • Passing header text into Idoc(Idoc type orders05)

    Hi,
      we have header text, header note etc in text tab(under details) in  PO.
           now i have to pass the data's from the header text into the IDoc(idoc type Orders05),
    In which segment the data's will be populated, How to shall i go.

    Hi,
    if you are using idoc PORDCR102 or PORDCR101, header texts are populated in E1BPMEPOTEXTHEADER and both position & header in E1BPMEPOTEXT.
    Then you are using ORDERS01-05 Idoc types, header texts were filled in E1EDKT1 & E1EDKT2 while texts are filled in E1EDPT1 & E1EDPT2.
    The PO header texts are stored in the segments E1EDKT1 whose child segment is E1EDKT2 in IDoc type ORDERS05.
    The actual text will be found in E1EDKT2 and the text id will be found in E1EDKT1.
    You have to do some config so that The segment gets update
    in the IDoc.
    go to SPRO  MM->Purchasing ->messages->Text for messages->Define texts for PO. Here you can find out on the left side of the window.In  Header texts & supplements text.
    Add the text IDF01( with all  details like your document type, object for PO will be EKKO) in header text .
    Then Add all other to the supplement texts(details).
    It is now the IDoc should update the segments.
    Regards
    Raj.
    Moderator message:
    Warning. Reason: plagiarism, this is a copy-paste answer from:
    PO texts in purchase order idoc*
    Edited by: Csaba Szommer on Nov 8, 2011 2:00 PM

  • Have to pass header text on IDOC - PREQCR02 ( Purchase Requisition Create )

    Hi Experts,
    During this week, I've been searching some way to pass Long text to the header through IDOC PRECR02, but i can't find any solution.
    I'd like to know if somebody have some idea to help me, I've tried to use BADI, Exits but no results.
    Regards.

    Hi,
    Check the "IS_SC_DOCUMENT" structure in the BADI BBP_CREATE_BE_RQ_NEW. In this structure you will have LONGTEXT.
    In this you can do..
    Thanks
    Venaktesh P

  • Mapping text in IDOC to IDOC scenario

    Hi,
    I have to map the source tdline field of IDOC segment E1EDPT1 to target IDOC Tdline field. Currently few tdline brings more than 31 chars but target should have only 31 and if it's more than 31 should roll over to next line.
    I can able to truncate 31 chars using substring and if coneditions, but chars from 31 to rest couldnt be mapped, I tried a duplicate subtree in target and didnt work, used global variables to store the remainins but still didnt work.
    Any suggestion would be greatly appreciated.
    Thanks,
    Menaga

    Menaga,
    Create a udf with name addnode and Queue as  cache. Have one parameter as input:
    Imports:  java.;*
    Add this code:
    for (int i=0; i<input.length; i++)
    String str=input<i>;
    while(str.length()>31)
    result.addValue(str.substring(0,31));
    str=str.substring(31,str.length());
    result.addValue(str);
    Now map like this:
    For e1edkt2:
    tdline(change context to idoc) --> addnode udf --> e1edkt2
    For tdline:
    tdline --> removecontext --> addnode --> splitbyvalue --> tdline
    Regards,
    ---Satish

  • Mapping from nested to one table (sales order) XML to IDOC

    Hello,
    I have to map a xml file to the IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202.
    How I can map the the longtext from the XML file to the IDOC struktur.
    Part of the XML file, there could be n times BPosition with n times longtext. The longtext must be map with a table. I some case its a mapping from nested to mornal table.
        <BPosition>
             <lpos>1</lpos>
             <bbl_sap_nr/>
             <milvonr/>
             <kurztitel/>
             <anzbest/>
             <anzliefer/>
             <kostenpflichtig/>
             <longtext>
                <line>pos1 zeile1</line>
                <line>pos1 zeile 2</line>
             </longtext>
          </BPosition>
    thanks for your help.

    Hi, I have to map this 1 XML to 1 IDOC
    XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Milver xmlns:ns0="http://ccssap.bfi.admin.ch/milver">
       <bestellung>
          <besteller>
             <bestellnr/>
             <auftragdefit/>
             <wempfdebit/>
             <bestelldat/>
             <lieferdat/>
             <anzpos/>
             <language/>
             <adrzeile1/>
             <adrzeile2/>
             <adrzeile3/>
             <adrzeile4/>
          </besteller>
          <Kopf>
             <Lkopf>Kopf1 zeile1</Lkopf>
             <Lkopf>Kopf1 zeile2</Lkopf>
          </Kopf>
          <BPosition>
             <lpos>1</lpos>
             <matnr/>
             <milvonr/>
             <kurztitel/>
             <anzbest/>
             <anzliefer/>
             <kostenpflichtig/>
             <bemerkung>
                <line>pos1 zeile1</line>
                <line>pos1 zeile 2</line>
             </bemerkung>
          </BPosition>
          <BPosition>
             <lpos>2</lpos>
             <matnr/>
             <milvonr/>
             <kurztitel/>
             <anzbest/>
             <anzliefer/>
             <kostenpflichtig/>
             <bemerkung>
                <line>pos2 zeile1</line>
                <line>pos2 zeile 2</line>
             </bemerkung>
          </BPosition>
       </bestellung>
    </ns0:MT_Milver>
    IDOC:
    The Idoc have a segment for the longtext (table).I have to map, lpos, line into  E1BPSDTEXT from SALESORDER_CREATEFROMDAT2. Its now more clear?

  • Mapping Problem. Do I need a UDF?

    Hello,
    I have the following scenario.
    Source File
    <ORDER>
      <ITEMS>
        <ITEM>
           <NUM>10</NUM>
           <CONDITIONS>
             <CONDITION>
                <TYPE>T1</TYPE>
                <VALUE>V1</VALUE>
              </CONDITION>
             <CONDITION>
                <TYPE>T2</TYPE>
                <VALUE>V2</VALUE>
              </CONDITION>          
         </ITEM>
      </ITEMS>
    </ORDER>
    I have to map this to an IDOC with the structure
    <E1BPITEM>
      <NUM>10</NUM>
    </E1BPITEM>
    <E1BPCOND>
      <NUM>10</NUM>
      <TYPE>T1</TYPE>
      <VALUE>V1</VALUE>
    </E1BPCOND>
    <E1BPCOND>
      <NUM>10</NUM>
      <TYPE>T2</TYPE>
      <VALUE>V2</VALUE>
    </E1BPCOND>
    I am using graphical mapping. everything works well until I have an order with no conditions at all.
    in that case in all subsequent orders the NUM fields are mapped incorrectly.
    my mapping:
    <NUM> ... THIS IS MY PROBLEM
    <TYPE> (in context items) -> exists -> createif -> E1BPCOND
    <TYPE> (in context items) -> splitbyvalue (each) ->TYPE
    <VALUE> (in context items) -> splitbyvalue (each) ->VALUE
    Do I need a UDF or can I solve this using graphical mapping? I have never written a UDF that uses Reultlist. what do I need to know?
    Thanks,
    Yoni

    Thanks for the helpful answer. It looks nicer than my graphical mapping but still the same problem. When there is an order with no conditions one SUPPRESS is added to condition type and value queues but not to the NUM queue.
    Source XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="com:post:sd:sales" targetNamespace="com:post:sd:sales">
    <xsd:element name="sales_new_MT" type="sales_new_DT" />
    <xsd:complexType name="sales_new_DT">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    e1cb7e20f38211dcb9b00019bb2d97c0
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="FILE_HEADER">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de0557311dccef00019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="SYS_CODE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de1557311dc87e70019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="HAFK_CASH" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c00771411dcc5c80019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="HAFK_CH" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c01771411dcbef00019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="HAFK_CR" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c02771411dc8ecf0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="SUM_NO_ORD" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c03771411dcb4f00019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="WORK_DATE" type="xsd:date">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c04771411dc8f860019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="MAAZAN" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c05771411dc8b240019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="SNIF" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c06771411dcbe960019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ASHNAV" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c07771411dcc16e0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="ORDERS">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de4557311dcb4530019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ORDER" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de5557311dcb61a0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="SERV_DATE" type="xsd:date" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de6557311dccabe0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="PRICE_DATE" type="xsd:date" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de7557311dca7f20019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="SNIF" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de8557311dcc78b0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ASHNAV" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c08771411dc8b350019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ORDER_ID" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c09771411dcbfef0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="USER_ID" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0a771411dca75c0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="INVOICE" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0b771411dcc40f0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ORD_TYPE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0c771411dccc710019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ORD_TEXT" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0d771411dcb34c0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="MAAM_ORDER" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    6d52d3f0ac7811dca1640019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="CUSTOMERS">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82de9557311dca4d70019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="CUSTOMER" minOccurs="0" maxOccurs="10">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82dea557311dc9f370019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="PARTN_ROLE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82deb557311dc93ef0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="PARTN_NUMB" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82dec557311dc98400019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="NAME" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0e771411dc8c650019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="COUNTRY" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c0f771411dc9e620019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="CITY" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c10771411dc856a0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="POST_CODE1" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c11771411dcb0840019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="STREET" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c12771411dc91cd0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="HOUSE" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c13771411dc964f0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="ITEMS">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82ded557311dc94570019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ITEM" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82dee557311dc9bbd0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="CONDITIONS" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    ab4c79b0ac7111dc9f0e0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="CONDITION" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    ab4c79b1ac7111dccbef0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="COND_TYPE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    4379b3c0ac7611dc8f8f0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="COND_VAL" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    4379b3c1ac7611dc80610019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="CNDS" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    9fca6e70ce7d11dcb57a0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="CND" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    9fca6e71ce7d11dc88aa0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="CNDT" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    9fca6e72ce7d11dcb18a0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="CNDV" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    9fca6e73ce7d11dcb4760019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="MKT_SAP" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82def557311dca2150019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="NUM" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    844eb460c37611dc97ff0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ITEM_CATEG" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c14771411dca0a30019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="QTY" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c15771411dcbf590019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="LEGACY" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c16771411dcb8e20019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="STOCK" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    6d4040e0ac7911dc8caf0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="MAAM_ITEM" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    2af82df2557311dc921c0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ITEM_TEXT" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c19771411dc96fa0019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="REF_NUMBER" type="xsd:string" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    987d6c1a771411dcce450019bb5c48d9
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Target XSD is IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202
    with maxoccurs changed for multiple idoc scenario.
    sample file (2 orders , first with no conditions and second with 3 conditions):
    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <ns0:sales_new_MT xmlns:ns0="com:post:sd:sales">
      <FILE_HEADER>
        <WORK_DATE>20080310</WORK_DATE>
        <SYS_CODE>Z02</SYS_CODE>
      </FILE_HEADER>
    <ORDERS>
        <ORDER>
          <SERV_DATE>20080310</SERV_DATE>
          <SNIF>101</SNIF>
          <ASHNAV>131</ASHNAV>
          <ORDER_ID>20080310101</ORDER_ID>
          <USER_ID>40076416</USER_ID>
          <ORD_TYPE>ZOR1</ORD_TYPE>
          <MAAM_ORDER>A</MAAM_ORDER>
          <CUSTOMERS>
            <CUSTOMER>
              <PARTN_ROLE>AG</PARTN_ROLE>
              <PARTN_NUMB>40000001</PARTN_NUMB>
            </CUSTOMER>
          </CUSTOMERS>
          <ITEMS>
            <ITEM>
              <NUM>10</NUM>
              <MKT_SAP>Z230000163</MKT_SAP>
              <QTY>1</QTY>
              <LEGACY>163</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
            </ITEM>
          </ITEMS>
        </ORDER>
    <ORDER>
          <SERV_DATE>20080310</SERV_DATE>
          <SNIF>101</SNIF>
          <ASHNAV>301</ASHNAV>
          <ORDER_ID>20080310101</ORDER_ID>
          <USER_ID>32547747</USER_ID>
          <ORD_TYPE>ZOR1</ORD_TYPE>
          <MAAM_ORDER>A</MAAM_ORDER>
          <CUSTOMERS>
            <CUSTOMER>
              <PARTN_ROLE>AG</PARTN_ROLE>
              <PARTN_NUMB>40000001</PARTN_NUMB>
            </CUSTOMER>
          </CUSTOMERS>
          <ITEMS>
            <ITEM>
              <NUM>10</NUM>
              <MKT_SAP>Z220000060</MKT_SAP>
              <QTY>1</QTY>
              <LEGACY>160</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
            </ITEM>
            <ITEM>
              <NUM>20</NUM>
              <MKT_SAP>Z220000071</MKT_SAP>
              <QTY>1</QTY>
              <LEGACY>171</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
              <CONDITIONS>
                <CONDITION>
                  <COND_TYPE>ZST1</COND_TYPE>
                  <COND_VAL>433.67</COND_VAL>
                </CONDITION>
              </CONDITIONS>
            </ITEM>
            <ITEM>
              <NUM>30</NUM>
              <MKT_SAP>Z220000074</MKT_SAP>
              <QTY>6</QTY>
              <LEGACY>174</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
              <CONDITIONS>
                <CONDITION>
                  <COND_TYPE>ZST1</COND_TYPE>
                  <COND_VAL>1296.33</COND_VAL>
                </CONDITION>
              </CONDITIONS>
            </ITEM>
            <ITEM>
              <NUM>40</NUM>
              <MKT_SAP>Z220000075</MKT_SAP>
              <QTY>10</QTY>
              <LEGACY>175</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
              <CONDITIONS>
                <CONDITION>
                  <COND_TYPE>ZST1</COND_TYPE>
                  <COND_VAL>17221.00</COND_VAL>
                </CONDITION>
              </CONDITIONS>
            </ITEM>
            <ITEM>
              <NUM>50</NUM>
              <MKT_SAP>Z220000076</MKT_SAP>
              <QTY>41</QTY>
              <LEGACY>176</LEGACY>
              <MAAM_ITEM>1</MAAM_ITEM>
            </ITEM>
          </ITEMS>
        </ORDER>
    </ORDERS>
    </ns0:sales_new_MT>
    Thanks,
    Yoni

  • Idoc: Send all text in REQOTE.

    Hi,
    Actually the idoc send part of text in the reqote, but my requirement is send all header and position text of the order.
    The segment E1EDPT1 send text A05 and A01, but i need add text A04, A06..etc
    How add this text in IDOC (Segment) ?.

    Stephen,
    I am trying to do the same thing. I am sorry no one is commenting but that tends to be because what you are doing is a workaround and making Mail do something it is not intended to do.
    In other words, I also want to do the same thing (send mail at 2 times per day, and create drafts to send in one batch, without me hitting the 'send' button.)
    The scripts currently in Automator do not have any sort of clear method to do this. Help!

  • Which field from idoc INVOIC01 maps to Item Text field in MIRO transaction?

    Hi
    Will anybody please tell me which of the field in which segment of IDOC INVOIC01 maps to Item text (INVFO-SGTXT) field in Basic data tab of MIRO transaction

    Thanks Ravi for your response.
    But I have tried with all fielsd related to texts in IDOC but it is not being filled in transcation .
    If you see the F4 help in text field then Text Id is four character and when I manually assign this in transactin then it is putting = symbol in fron of the id. And then if we save or go to other tab then it is filling text.
    I am not able to find the error bcoz document is being posted through idoc but text field is not getting filled.

  • Message type and IDoc type to update a sales order

    I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
    Thanks in advance....
    Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

    At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
    Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

Maybe you are looking for

  • Image Processor Not Working

    Hi, I used the Image Processor feature to resize and save in a separate folder all the time in Bridge CS3. I recently upgraded to CS4 and I can't get the Image Processor to work. When I select the feature, it opens photoshop but nothing happens...it

  • Manipulati​ng 2D arrays

    I'm fairly new to labview and working on a VI that I am taking over. The VI has channels 0-31 (channels 0-3 are being used for a photo sensing diode).  In a while loop I am oversampling data at 1000 points/sec and the plan is to average 1000 pts and

  • Problem with Adobe Flash Player.pkg

    Hello Chris, Thank you for your reply. I have managed to get to "Adobe Flash Player.pkg" but have got stuck again! It says "Select a Destination" and shows an icon of iBook HD together with a big red exclamation mark. When I click on to this, it says

  • Aperture 3 update.  Why is there still no eraser for the retouch tool?

    Perhaps I'm missing something, but: Why is there still no eraser for the retouch tool? I realize you can delete retouch strokes, but they are in linear order so you often have to delete useful ones to go far enough back to get the one that you've dec

  • Time missing from clip view

    Im trying to edit a video for work and i have already gone through and marked time segments to reject clips from becasue of speaking errors. The issue is that in this new version of iMovie i cant figure out a way to view the clip time so i can easily