How to design an IDOC-XI-JDBC interface

Hello Experts!
I'm looking for some guidance on how to design an interface where R/3 is sending an IDOC to XI (via IDOC Adapter Receiver), then XI transforms this data into a JDBC database INSERT action.
I want to make to make the JDBC request a SYNC interface so that I can capture the number of rows inserted into the database and do some appropriate action when the insert count returns a zero value.
Since the IDOC to XI interface is ASYNC, how do I design my link so I can redirect the JDBC response out to a different adapter?
Thanks for your help!
XI Rookie

Hi,
This will help you
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
/people/laxman.molugu/blog/2006/08/13/integration-with-databases-made-easy-150-part-1
Re: Idoc triggering from a transaction
Message Mapping - JDBC to IDoc
Re: JDBC - System/Application Acknowledgement
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards
Agasthuri Doss

Similar Messages

  • Mapping Issue for IDoc to JDBC interface

    Hi All,
      I am having problem in implementing logic in IDoc to JDBC interface where I have to filter out E1WBB07-KSCHL = VKP0.
      Source IDoc structure is like ->
    E1WBB01(occ 0 -1000)
      |-> E1WBB03 (occ 0-100)
                |-> E1WBB07(occ 0-1000)
                         |-> KSCHL
                              DATAB
                              DATBI
    Now, For each KSCHL = VKA0 there should be a duplicate VKP0 record. From these 2 records only the VKA0 should get processed and VKP0 ignored.
    Duplicates for VKP0 and VKA0 can be identified by identical DATAB and DATBI.
    Suppose, in one  E1WBB03 segment,there are 4 E1WBB07 segment having following values.
    1: KSCHL=VKP0, DATAB=20102011, DATBI=25102011
    2: KSCHL=VKP0, DATAB=26102011, DATBI=30102011
    3: KSCHL=VKA0, DATAB=26102011, DATBI=30102011
    4: KSCHL=VKP0, DATAB=01112011, DATBI=31129999
    2 & 3 are duplicates. From these, 2 should get dropped.
    As a result only 1, 3 and 4 should get  processed.
    How can I proceed with this..?...I have tried some work around but not able to do it successfully. Is a UDF required to compare DATAB and DATBI. If yes how it can be written.?
    Thnx in advance,
    Praveen.

    chk below mapping:
    change the context of DATAB, DATAB1 and KSCHL to E1WBB03 (right click-> context) in all the mappings shown below
    1)
    DATAB
    ------------concat-----sort----splibyvalue(value change)-----collapse context---TargetNode
    DATBI
    2)
    DATAB
    ------------concat-----sortbykey \
    DATBI                    /        \
    KSCHL------------/                 \
    ----------------------------------------FormatByExample----sort-----UDF1----Target KSCHL
    DATAB                                    /
    ----concat---sort--splibyvalue(value change)-
    DATBI
    3)
    DATAB
    ---concat ( ; )-----sort-splibyvalue(value change)---collapse context--splitbyvalue (each value)--UDF2---TargetDATAB
    DATBI
    4)
    DATAB
    ------------concat ( ; )-----sort----splibyvalue(value change)-----collapse context--splitbyvalue (each value)--UDF3---TargetDATABI
    DATBI
    UDF1: execution type : all values of a context...input: var1
    int a=var1.length;
    int count=0;
    if(a>=2)
    for(int i=0;i<a;i++)
    if(var1<i>.equals("VKA0"))
    count= count+1;
    else
    result.addValue(var1[0]);
    if(count>1)
    for(int i=0;i<count;i++)
    result.addValue("VKA0");
    UDF2:execution type: single value...input: var1
    String [] temp= var1.split(";");
    return temp[0];
    UDF3: execution type: single value...input: var1
    String [] temp= var1.split(";");
    return temp[1];

  • IDoc to JDBC  and JDBC to IDoc Scenario

    Dear All,
    I am working on IDoc to JDBC and JDBC to IDoc Scenario.
    I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
    Does anyone have completed STEP by STEP scenario document for this?
    How my Idoc will sent to XI?
    How XI will pick up data from IDoc?
    How XI will Convert data to JDBC and UPDATE in Oracle Database?
    And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
    Where and When i can watch my process and data?
    How can i test the whole integration?
    I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE  it gives me error
    "Unable to refresh cache "NO_BUSINESS_SYSTEM"
    "Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
    Please solve all the above problems i will reward u points
    thanks,
    RP

    Hi,
    While we working on IDOC to JDBC interface..
    We have to deploy JDBC Drivers?
    Go through this links,
    /people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
    To install JDBC driver follow the how to guide.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
    Configuration of JDBC Adapter for SQL Server
    JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
    UserID and Password.
    If the connection is not working find the correct port number.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
    JDBC- X I -  R/3 Scenario
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Please check the driver path as mentioned below.
    JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
    Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
    No JDBC driver required.
    Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    follow this thread
    Re: Problem when connecting to MS Access through JDBC Adapter.
    SAP Note 850116 has details
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Configuring the Sender JDBC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
    Configuring the Receiver JDBC Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
    Idoc Reveiver adapter..
    http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Thanks,
    Satya Kumar
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

  • Need information regarding IDOC to JDBC Scenarios.

    Hi,
    Kindly help me with the pre-requisites inorder to start with a scenario of IDOC to JDBC and also the scenario of JDBC to IDOC.
    Regards,
    Sreedhar, Av

    Hello Sreedhar,
    While we working in JDBC or JMS Adapters we should deploy the Drivers..
    Go through this links,
    /people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
    To install JDBC driver follow the how to guide.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
    Configuration of JDBC Adapter for SQL Server
    JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
    UserID and Password.
    If the connection is not working find the correct port number.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
    JDBC- X I -  R/3 Scenario
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Please check the driver path as mentioned below.
    JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
    Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
    No JDBC driver required.
    Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    follow this thread
    Re: Problem when connecting to MS Access through JDBC Adapter.
    SAP Note 850116 has details
    2)  While we working in IDOC  Adapters we should do  ALE Config of IDOC Settings .
    Do these configurations in R/3 and in XI...
    SAP XI
    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.
    Here in IDOC to JDBC interface we need not to config sender Adapter..
    1) The main usage of a sender adapter is to convert the input format into the XI supported XML format.
    Once the conversion is completed the sender agreement appends the header with the sender details.
    In case of these adapters we wont require sender agreement and sender communicationchannel for the
    following reasons.
    Sender agreement is associated with a namespace when we shoot an idoc frm r/3 if already contains its standard sap namespace. so those is need of sender agreement
    The sender communication channel use is to identify the sending system and adapter, as the idoc header contains the details there is no need to sender.
    These adapters resides on ABAP stack here the integration server takes care of IDOC/HTTP to XML conversion without requirement of adapter.
    The business system that is sending the adapter has already been assigned to a techinical system which normally acts as an integration server...
    IDOC to xi links
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Hope this explanation is useful to u..
    Thanks,
    Satya Kumar
    Edited by: SATYA KUMAR AKKARABOYANA on Jun 3, 2008 9:57 AM

  • IDOC to JDBC using Synchronous

    Hi all,
    I am working idoc to jdbc interface,here i have to get response from reciever jdbc when iam creating vendor details in jdbc system.My requirement is i have to get this by using synchronous message.
    Please help me on this.
    Thanks in Advance.
    Regards,
    Ravi

    Hi Ravi
    Follow these it will help
    Step by Step JDBC Synchornous
    JDBC Receiver Adapter -- Synchronous Select – Step by Step
    Integration with database made easy
    Integration with Databases made easy – Part 1.
    SOAP <=> JDBC Synchronous
    SYNCHRONOUS SOAP TO JDBC - END TO END WALKTHROUGH
    Serialize IDOC XML
    How to serialize IDoc XML messages fed into XI
    For special problematic of IDOC -> JDBC and sending back acknowledgement have a look to One Logical System Name for serveral BPM Acknowledgements
    One Logical System Name for serveral BPM Acknowledgements
    Thanks
    Gaurav

  • IDOC to JDBC Synchronous interface

    Hi Experts,
    I am using PI 7.1.
    Having requirement of IDOC to JDBC synchronous scenario. When data is coming from SAP to DB it is updating data in to u201CXu201D table, when data response from DB is u201CYu201D table.
    How can I configure this interface, Please suggest me.
    Best Regards,
    Pasi...

    Hello,
    For special problematic of IDOC -> JDBC and sending back acknowledgement have a look to One Logical System Name for serveral BPM Acknowledgements
    One Logical System Name for serveral BPM Acknowledgements
    Step by Step JDBC Synchornous
    JDBC Receiver Adapter -- Synchronous Select – Step by Step
    Integration with database made easy
    Integration with Databases made easy – Part 1.
    SOAP <=> JDBC Synchronous
    SYNCHRONOUS SOAP TO JDBC - END TO END WALKTHROUGH
    Serialize IDOC XML
    How to serialize IDoc XML messages fed into XI
    Regards,
    Phani

  • How to import the IDOC into Seeburger BIC mapping designer

    Hi All,
    Can u please tell me how to import the IDOC into Seeburger BIC mapping desginer.
    I have scenario My scenario is SAP GTS 7.0.....>Seeburger BIS.....>Atlas customs system for Germany
    Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send
    to Atlas systeam.
    Regards,
    Ramesh.

    Hi Ramesh
    BIC is a tool from Seeburger to transmit the XML data to EDI and EDI to XML.
    Seeburger mapping programs for transferring the XML data to EDI data and EDI data to XML data, but not for the structure changing, in the IR your mapping program is same.
    Receiver side you need AS2 Adapter for converting data to EDI target structure. we have many EDI versions are available, for converting the EDI to XML or vice versa AS2 gives some default mapping programs, xml to EDI or EDI to XML convertion done through this mapping programs.
    Seeburger AS adapter provider provides some mapping programs(for example EDI4010 version or other), if you are using the same EDI version(4010) then you can use that mapping programs, if the version is different then we can manually generate the Seeburger X2E and E2X mappings for the corresponding version and signal(850 or 810 or ..), for this seeburger provides the mapping designer tool (BIC), there we can develope the X2E and E2X mapping programs and configure this in the Seeburger work bench.
    Regards
    Ramesh

  • How to design the user interface for Indesign cs6 plugin ?

    Designing user interface using custom c++ library(SDK) for pluging is very tedious work .so when I search the net than i found that we can do it using Adobe Creative Suite Extension Builder but i dont know how to use it to develop user interface for plugin and to how to enable event handling in this UI .I read lots of document regarding this on net but they all created lots of confusion in my mind  so can anyone help me to know steps which i must follow to develop plugin using this or whatever technology (action script,java script etc)

    If you want to develop Extensions using Creative Suite Extension builder then i think this is not the right forum for you. Please post your specific queries regarding this at the below mentioned link
    http://forums.adobe.com/community/creativesuites/cs_sdk
    To give a brief of how to develop UI using JS you can use ScriptUI to develop your UI, it is a fast and OS independent approach to UI development. The UI created using JS is native in look. You can refer the following link for some help on ScriptUI
    http://www.kahrel.plus.com/indesign/scriptui.html
    I don't have much info regarding development in CS SDK, but i can point you to one more direction of dev called as hybrid plugins wherein the UI is created in CS SDK, and appropriate methods are exposed from the C++ plugin(enhancing the script object model) to be called up by the CS code for too and fro communication between these two modules of code.
    Hope these pointer help you in getting started.
    Thanks,
    -Manan

  • PI : Idoc to JDBC scenario : repeating segments mapping issue

    Experts
    Please help.
    Question reg. mapping for ECC idoc to JDBC scenario.
    I am using the ORDRSP idoc which has multiple segments as below.
    IDOC -> multiple E1EDK14 segments with 2 fields (QUALF and ORGID)
    Depending on the value of the QUALF field i need to populate the column in my target structure.
    QUALF 001  => Colmn a
    QUALF 002 => Colmn b
    For now my graphical mapping is very simple - QUALF => column a (done just to find out how PI mapping works)
    What happens in my case, is the PI Payload shows all the E1EDK14 segments however only the value 006 present in the first occurence goes into the target column.
    How do I repeat a mapping between QUALF and target col. for multiple occurences of the same segment?
    Please can you guide me reg. use of context, loop over segment, UDF = which will be the best solution to achieve this?

    Hi
    My mapping is as below. I will take an example of a sales order that has 2 line items 00010, 00020. The payload is as follows
    I see this payload in the SXMB_MONI transaction => Receiver grouping => Payloads
    - <ZORDRES>
    - <IDOC BEGIN="1">
    + <EDI_DC40 SEGMENT="1">
    + <E1EDK01 SEGMENT="1">
    + <E1EDK14 SEGMENT="1">
      <QUALF>006</QUALF>
      <ORGID>01</ORGID>
      </E1EDK14>
    + <E1EDK14 SEGMENT="1">
      <QUALF>007</QUALF>
      <ORGID>01</ORGID>
      </E1EDK14>+ <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDK02 SEGMENT="1">
    + <E1EDK02 SEGMENT="1">
    + <E1EDK17 SEGMENT="1">
    + <E1EDK18 SEGMENT="1">
    + <E1EDK18 SEGMENT="1">
    + <E1EDP01 SEGMENT="1">
      <POSEX>000010</POSEX>
    + <E1EDP01 SEGMENT="1">
      <POSEX>000020</POSEX>
      </E1EDP01>+ <E1EDS01 SEGMENT="1">
      <SUMID>001</SUMID>
      <SUMME>2</SUMME>
      </E1EDS01>
    + <E1EDS01 SEGMENT="1">
      <SUMID>002</SUMID>
      <SUMME>1100.00</SUMME>
      <SUNIT>GBP</SUNIT>
      </E1EDS01>
      </IDOC>
      </ZORDRES>
    There are 2 problems. First one which I discovered after posting the query. I can see only the line item 10 in the query that gets contructed in PI to insert the data into the target jdbc table. Please see jdbc receiver communication channel log below
    If you see above there are 2 E1EDP01 segments for line 00010, 00020.
    INSERT INTO  tblOItem  (IDocDate, IDocTime, SalesOrderNo, ItemNo, Plant, ItemCategory, UnitSellPrice, QuantityOrdered, QuantityAllocated, ScheduledDeliveryDate) VALUES (20111206, 135530, 0015002085, 000010, 0086, ZTAN, 0.00, 1.000, 1.000, 20111201)
    My source and target mappings are as below.
    ZSALORD
        IDOC
           BEGIN
             E1EDK01
             E1EDP01
               POSEX               =============>  SalOrdItm table column itemno
    My target side structure (idoc to jdbc scenario is as follows)
    I have mapped the E1EDP01 to Statement - I thought this will build one query per line item (per occurence of E1EDP01) but this is not working.
    MT_OITEM
      Statement
        dbtablename       ============> SalOrdItm
          action      =================> Insert
          table
          access
            Itemno      (this is one of the columns from the table)
    The occurence of E1EDP01 is 0..9999999 while the occurence of Statement node is 1...unbounded.
    Please is there any email address where I can send you screen shots if the above is not clear.
    I need to get this interface delivered as soon as possible but am STUCK.
    Edited by: gary jojo on Dec 6, 2011 3:06 PM

  • File to Idoc and Jdbc

    Hi Guys,
                 Can I implement a scenario wherein the data is sent to Idoc and JDBC parallelly without using BPM?
    Regards,
    Ashish

    Ashish,
    ><i>If i add multiple recievers in receiver determination step without any condition, then how do i add multiple interface determinations in the area below?</i>
    Once you add multiple Receivers and save the same, the Receivers will be available in the Window Below and you would need to create an Interface Determination for each of these Receivers.
    As you do not have any condition, no need to add conditions.
    ><i>created seperate Receiver determinations</i>
    You would need only ONE RECEIVER DETERMINATION and this receiver determination would in turn have multiple Interface Determinations.
    Like mentioned, add multiple receivers save the Receiver Determination and in the window below, you will nopw be able to add an Interface determination for each of the receiver.
    Regards,
    Bhavesh

  • IDoc to File interface

    Hi Experts Team,
    My scenario is IDoc to File interface. I need to create 12 different files based on the Plant code (WERKS). At the end of the day, i need to ftp the file to different locations. How can I do the design and is there any need for BPM here?
    Please explain..
    Thanks & Regards,
    Kanda

    Hi S.P ,
    You may use the variable substitution functionality of receiver file adapter and can generate the file based on the xml payload content which contains your WERKS field.
    You may refer the following blogs for the understanding of the concept.
    An interesting usage of Variable Substitution in XI
    Thanks & Regards
    Prabhat

  • IDOC to JDBC - Multiple Inserts

    Hi  ,
    I have an idoc to JDBC scenario.
    Here is idoc structure.
    E1MASTL 1...1
              |-->  E1STOKL 0....9999
                 |--->E1STOPL 0....9999
    my table struture expects data  from 2 segments in the E1MASTL and 4 segments from E1STOKL and 3 segments from E1STOPL.
    when i trigger the idoc which has 5 line items in E1STOPL and 5 line items in E1STOKL but only one from E1MASTL.
    Now, when this idoc is triggered, the table is updated with all the first line items from each segment, instead i want all the 10 lines to be updated in the table.
    I  have tried mapping the Statemetn and access tags to the all the possible nodes on the Idoc side but could not succed in inserting multiple lines in the table though i had multiple line items in the idoc.
    Please help me how do i do it.
    Thanks in advance.
    Regards,
    Kalpana.
    Edited by: Kalpana Timmapuram on Nov 27, 2009 9:58 PM

    Now, when this idoc is triggered, the table is updated with all the first line items from each segment, instead i want all the
    10 lines to be updated in the table.
    The Statement node should be repeating.....now only first instance is getting mapped because the Context is not handled properly.
    If you test the mapping in Message Mapping/ Interface Mapping Test tab then too the same thing will happen...only first line item is considered.
    You either need to raise the Context of the respective Source nodes to a higher node (right-click on the source node in mapping editor--> Context --> raise it to higher node)
    OR
    You need to make use of the standfard functions Collapse Context & Remove Context in the mapping logic.
    Regards,
    Abhishek.

  • Scenario IDOC to JDBC

    Hi experts,
    i've scenario IDOC to JDBC:
    the interface receive two idoc's:
    IDOC1: 1field1, 1field2, 1field3
    IDOC2: 2field1, 2field2, 2field3
    and give the data to only one table in the receiver, ie, the table is equally filled by the contents of both idocs,
    the data in this table must be storage by follow:
    field ->       field1        field2        field3
    values ->    1field1      1field2      1field3
                     2field1      2 field2     2 field3
    ¿how can i do this whe i realize the mapping ?
    ¿Is it possible, or it's better to use two interface, one for each idoc?
    very thanks

    If both the idocs are of same basic type, then you may perform Idoc packaging at the sender side. Due to this you could receive idoc at XI with multiple Idoc nodes having data from different idocs. Then you may map directly till node level and achieve the output.
    If the type of idocs are different, use two interfaces or go for BPM to collect.
    Regards,
    Prateek

  • How can i transfer IDOC to XML format?

    Hi,
    How can i transfer IDOC to XML format?
    Is there some some mechanism to transfer IDOC to XML format to be used by XI system?
    Pls help.
    Regards,
    Kanwar

    Ravi,
    If you want to pick the IDOC in an XML format, you can do that from WE60 transaction. Here a XML of the IDOC MATMAS05 that I could generate out WE60 transaction. If the XML format is required at design time to pass on the middleware consultant, how can I use the function module.
    You can get the XML schema by going to the Menu
    Documentation --> XML Schema.
      <?xml version="1.0" encoding="utf-8" ?>
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0">
    - <xsd:element name="MATMAS05">
    + <xsd:annotation>
      <xsd:documentation>Enhancement: Distribution of Single-Level Variants</xsd:documentation>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="IDOC">
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="EDI_DC40">
    - <xsd:annotation>
      <xsd:documentation>IDoc Control Record for Interface to External System</xsd:documentation>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="TABNAM" type="xsd:string" fixed="EDI_DC40">
    - <xsd:annotation>
      <xsd:documentation>Name of table structure</xsd:documentation>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="MANDT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Client</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="DOCNUM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>IDoc number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="16" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="DOCREL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>SAP Release for IDoc</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STATUS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Status of IDoc</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="DIRECT">
    - <xsd:annotation>
      <xsd:documentation>Direction</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
    - <xsd:enumeration value="1">
    - <xsd:annotation>
      <xsd:documentation>Outbound</xsd:documentation>
      </xsd:annotation>
      </xsd:enumeration>
    - <xsd:enumeration value="2">
    - <xsd:annotation>
      <xsd:documentation>Inbound</xsd:documentation>
      </xsd:annotation>
      </xsd:enumeration>
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="OUTMOD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Output mode</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="EXPRSS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Overriding in inbound processing</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="TEST" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Test flag</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="IDOCTYP" type="xsd:string" fixed="MATMAS05">
    - <xsd:annotation>
      <xsd:documentation>Name of basic type</xsd:documentation>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="CIMTYP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Extension (defined by customer)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="30" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MESTYP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Message type</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="30" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MESCOD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Message code</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MESFCT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Message function</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>EDI standard, flag</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STDVRS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>EDI standard, version and release</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STDMES" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>EDI message type</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDPOR">
    - <xsd:annotation>
      <xsd:documentation>Sender port (SAP System, external subsystem)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDPRT">
    - <xsd:annotation>
      <xsd:documentation>Partner type of sender</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDPFC" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Partner Function of Sender</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDPRN">
    - <xsd:annotation>
      <xsd:documentation>Partner Number of Sender</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDSAD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Sender address (SADR)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="21" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SNDLAD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Logical address of sender</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="70" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVPOR">
    - <xsd:annotation>
      <xsd:documentation>Receiver port</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVPRT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Partner Type of receiver</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVPFC" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Partner function of recipient</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVPRN">
    - <xsd:annotation>
      <xsd:documentation>Partner number of recipient</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVSAD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Recipient address (SADR)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="21" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RCVLAD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Logical address of recipient</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="70" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="CREDAT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Created on</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="CRETIM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Time Created</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="REFINT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Transmission file (EDI Interchange)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="REFGRP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Message group (EDI Message Group)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="REFMES" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Message (EDI Message)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ARCKEY" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Key for external message archive</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="70" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SERIAL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Serialization</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="20" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
      </xsd:sequence>
    - <xsd:attribute name="SEGMENT" use="required">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:enumeration value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:attribute>
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="E1MARAM" maxOccurs="9999">
    - <xsd:annotation>
      <xsd:documentation>Master material general data (MARA)</xsd:documentation>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="MSGFN" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Function</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MATNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERSDA" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Creation date</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERNAM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Name of Person who Created the Object</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="12" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="LAEDA" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Date of Last Change</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="AENAM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Name of person who changed object</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="12" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="PSTAT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Maintenance status</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="15" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="LVORM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Flag Material for Deletion at Client Level</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MTART" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Type</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MBRSH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Industry Sector</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MATKL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Group</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="9" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BISMT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Old material number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MEINS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Base Unit of Measure</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BSTME" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Order unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ZEINR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Document number (without document management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="22" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ZEIAR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Document type (without Document Management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ZEIVR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Document version (without Document Management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ZEIFO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Page format of document (without Document Management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="AESZN" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Document change number (without document management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BLATT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Page number of document (without Document Management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BLANZ" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Number of sheets (without Document Management system)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="FERTH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Production/Inspection Memo</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="FORMT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Page Format of Production Memo</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GROES" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Size/dimensions</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="32" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="WRKST" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Basic material (basic constituent of a material) - obsolete</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="NORMT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Industry Standard Description (such as ANSI or ISO)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="LABOR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Laboratory/design office</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="EKWSL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Purchasing Value Key</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BRGEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Gross weight</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="NTGEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Net weight</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GEWEI" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Weight Unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VOLUM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Volume</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VOLEH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Volume unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BEHVO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Container requirements</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RAUBE" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Storage conditions</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="TEMPB" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Temperature conditions indicator</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="TRAGR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Transportation group</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STOFF" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Hazardous material number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SPART" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Division</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KUNNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Competitor</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="WESCH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Quantity: Number of GR/GI slips to be printed</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BWVOR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Procurement rule</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BWSCL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Source of Supply</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SAISO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Season category</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ETIAR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Label type</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ETIFO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Label form</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="EAN11" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>International Article Number (EAN/UPC)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="NUMTP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Category of International Article Number (EAN)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="LAENG" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Length</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BREIT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Width</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="HOEHE" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Height</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MEABM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Unit of dimension for length/width/height</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="PRDHA" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Product hierarchy</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="CADKZ" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>CAD indicator</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERGEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Allowed packaging weight</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERGEI" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Weight Unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERVOL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Allowed packaging volume</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="14" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ERVOE" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Volume unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GEWTO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Excess Weight Tolerance for Handling unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VOLTO" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Excess Volume Tolerance of the Handling Unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VABME" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Variable order unit active</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KZKFG" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Configurable Material</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="XCHPF" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Batch management requirement indicator</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VHART" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Packaging Material Type</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="FUELG" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Maximum level (by volume)</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="STFAK" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Stacking factor</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="5" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MAGRV" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Group: Packaging Materials</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BEGRU" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Authorization Group</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="QMPUR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>QM in Procurement is Active</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RBNRM" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Catalog Profile</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="9" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MHDRZ" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Minimum remaining shelf life</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MHDHB" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Total shelf life</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="6" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MHDLP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Storage percentage</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="5" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VPSTA" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Maintenance status of complete material</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="15" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="EXTWG" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>External material group</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MSTAE" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Cross-Plant Material Status</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MSTAV" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Cross-distribution-chain material status</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MSTDE" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Date from which the cross-plant material status is valid</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MSTDV" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Date from which the X-distr.-chain material status is valid</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KZUMW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Indicator: Environmentally Relevant</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KOSCH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Product allocation determination procedure</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="NRFHG" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material qualifies for discount in kind</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MFRPN" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Manufacturer part number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="40" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MFRNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Manufacturer number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="BMATN" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>To material number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MPROF" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Mfr part profile</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="PROFL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Dangerous Goods Indicator Profile</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="IHIVI" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Indicator: Highly Viscous</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ILOOS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Indicator: In Bulk/Liquid</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KZGVH" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Packaging Material is Closed Packaging</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="XGCHP" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Indicator: Approved batch record required</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="COMPL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material completion level</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="KZEFF" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Assign effectivity parameter values/ override change numbers</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="RDMHD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Rounding rule for calculation of SLED</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="IPRKZ" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Period indicator for shelf life expiration date</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="PRZUS" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Indicator: Product composition printed on packaging</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MTPOS_MARA" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>General item category group</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GEWTO_NEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Excess Weight Tolerance for Handling unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="5" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="VOLTO_NEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Excess Volume Tolerance of the Handling Unit</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="5" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="WRKST_NEW" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Basic Material</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="48" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="AENNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Change Number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="12" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="MATFI" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Is Locked</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="CMREL" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Relevant for Configuration Management</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SATNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Cross-Plant Configurable Material</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SLED_BBD" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Expiration Date</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GTIN_VARIANT" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Global Trade Item Number Variant</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="GENNR" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Material Number of the Generic Material in Prepack Materials</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="SERLV" minOccurs="0">
    - <xsd:annotation>
      <xsd:documentation>Level of Explicitness for Serial Number</xsd:documentation>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:eleme

  • IDOC to JDBC scenario in case of Cost Element Group IDOC.

    This is an IDOC to JDBC scenario.
    The Cost Element Group IDOC is having different segments. The main segment E1COGH (1...unbound) is consisting of different subsegment like E1OGS (0...unbound) & E1COGV (0...unbound). The main segment (E1COGH) along with subsegments E1OGS & E1COGV) is occuring more that 1 times. I have to insert data into the table, which we can do in single rows (no hierarchy  is possible in tables). I have used "use one as many" in message mapping. Now if E1OGS or E1COGV is repeating in a single E1COGH segment then we dont get any error. But if I duplicate the main segment then I am getting runtime exception.
    Please suggest about how to map in this case.

    In my scenario:
         E1COGH
         |
          -> E1COGS
             E1COGV
    where     E1CGH -> Main segment
         E1COGS & E1COGV -> sub segment
    E1COGH -> 1..unbound
    E1COGS -> 1..unbound
    E1COGV -> 1..unbound
    At the target side I have created two Statement Structure (ie.Statement & Statement_1) . One for E1COGS (ie. Statement) & the other for E1COGV (ie. Statement_1).
    Case 1 ->  If E1COGS is present in the main segment E1COGH then it is mapped AS IS.
    Case 2 -> If E1COGS is not present in the main segment E1COGH then it is mapped as blank.
    This will be mapped with Statement & in the absence of E1COGS this Statement structure is SUPPRESSED.
    Similarly,
    Case 1 -> If E1COGV is present in the main segment E1COGH then it is mapped AS IS.
    Case 2 -> If E1COGV is not present in the main segment E1COGH then it is mapped as blank.
    This will be mapped with Statement_1 & in the absence of E1COGV this Statement_1 structure is SUPPRESSED.
    All the elements of the segment E1COGH, E1COGHT & E1COGHR are replicated in all the rows for X (no. of occurance of E1COGS) + Y (no. of occurance of E1COGV).
    While testing in Message Mapping, I am able to get the output as for multiple occurence of E1COGS & E1COGV in a single E1COGH.
    But if I increse the occurence of E1COGH the it is giving the following error :
    Runtime exception during processing target field mapping /ns0:MT_Cost_Element_Group_Response/Statement/DBtablename/access/GROUPNAME. The message is: Exception:[com.sap.aii.mappingtool.tf3.IllegalInstanceException: Too few values in first queue in function useOneAsMany. It must have the same number of contexts as second queue.] in class com.sap.aii.mappingtool.flib3.NodeFunctions method useOneAsMany[com.sap.aii.mappingtool.flib3.CollapseContexts@51197231, , ]
    Please suggest how to map the occurence of E1COGH simultaneously with the occurence of E1COGS & E1COGV.

Maybe you are looking for

  • Removing Display resolution

    I have an odd acer monitor that gets detected as a TV. Makes sense since it connects via hdmi In the display settings, 1080i(PAL television) 1080i(television) and 1080p(television) are available options. I have no issue with running my monitor in 108

  • Problem in standard in cluded RSSTATDA

    Hi gurus in my report CALL FUNCTION 'SAPWL_INST_LONG'        EXPORTING             inst_short                    = rsystem        IMPORTING             inst_long                     = long_instance           HOST_LONG                     =        EXC

  • Connection pool replacement in NW

    hi, does anyone know if the connection pools that could be created in EP6SP2 via System Configuration->Knowledge Management->Content Management->Utilities->Connection Pool have been replaced in NW? I've noticed they are no longer available, so does a

  • Don't want incoming mail

    I have mail coming from a server without POP. I have it auto forwarding to another account that does have POP and I get it into Mail through that account. BUT, when I reply, I want it's FROM address to be the original account. Thus, I need to create

  • Adding keywords in Bridge, causes illegal operand i.e. corrupts the illustrator files.

    Upon adding keywords to a large amount of illustrator files in Bridge (mainly .eps but also some .ai), more than half of the files are now corrupt, giving me the following message: Can't open the illustration. The illustration contains an illegal ope