Importing XSD to Create a Msg Type.

Hi All,
Can anyone plz tell me how to create a msg type based on external XSD.I hav gone thru help.sap.com. there it is mentioned for Data Type.It is given that to go for Tools->Import XSD.but i din't find any such option there.Instead, i hav gone for creating External Definition and was successful in creating a DataType using External Definition.But to my surprise, the created Data type is not listed under Data types.Instead it is listed under External Definitions. This is for Data Types.But i need for Message Type.Plz help me out as i hav very severe dead lines.
Thnx in Advance.
Anil.

Hi Anil,
You could create Message Type (MT) in 3 ways :
1. Manual: Create Data Type (DT) & Create MT refering to it.
2. Import XSD as DT: Create a new DT by giving a name. The structure can be imported from a XSD. Tools-> Import XSD. (Note: the name of DT here should match the 'complex type' name in XSD). Then create a MT refering to this DT.
3. Import XSD as External Definition: An XSD can be imported into External definitions, and this creates the MT directly, and no DT required. They appear only under 'External Definitions'. Note: This XSD should contain a 'complex type' definition, which stands for DT. And also a root element declaration refering to this type, which stands for MT. In this case, we can have one XSD containing multiple DTs and MTs within it. All these MTs can be seen under the 'Messages' tab within an External Definition.
Once an MT is created in one of these 3 ways, the other concepts of Interfaces, mappings etc. remain the same.
Hope this gives the differences, and clarifies your concerns.
regards,
Pops V

Similar Messages

  • Import  XSD to create Data type in Design

    hi,
      I know that we can import XSD in Design and create data type,my question is:
    1.  Can i import an XSD thats been created in message mapping and use that to create my data type in design.
    (or)
    2.Should i have to write an XSD on my own and then import it to create my data type, and is there any standard format to write it.

    Hello Prashanth,
    For your first question: i don't know exactly what you mean that the the xsd you create in the data mapping steps. So can you explain it in details?
    For your 2nd question:  Sure you can write your own XSD to create a data type. And i will give you an example xsd file format. Then you can import it in the XSD tab view.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/hansteel" targetNamespace="http://sap.com/xi/XI/hansteel">
         <xsd:complexType name="CustomerInfo">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   a6c26c80000f11dac45e00096b1669b3
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="ID">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             dfe699c0e7bc11d9c736d51c0a0013e1
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:length value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="NAME">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             dfe82060e7bc11d9b2efd51c0a0013e1
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:length value="35" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="CUSTTYPE">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             dfe82061e7bc11d9c193d51c0a0013e1
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:length value="4" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="POSTCODE">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             e93039a0e7bc11d9c7c6d51c0a0013e1
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:length value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="CITY">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             f0122850e7bc11d99189d51c0a0013e1
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:length value="35" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    Hope this will be helpful.
    Eric Ma

  • Import XSD to create datatypes

    Hello Everybody-
    I want to create a datatype that is specific for my outbound message,i have the xsd of that structure,i was trying to import the xsd to form a XI structure.Here is what i have done.
    1.Right clicked datatypes and clicked on new
    2.It asked me for a name and i gave a name "venkat".
    3.Then from menu-tools, i clicked import xsd and selected my xsd. Then i got a message that Schema to be handled does not contain a definition of type venkat.
    4.So what i did this time i gave the name as OrderRelease instead of venkat(as stated in step 2) and still i get the error.
    I am pasting a snippet of my xsd.
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:element name="OrderRelease">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="ShipNodePersonInfo" minOccurs="0">
                    <xsd:complexType>
                      <xsd:attribute name="Suffix" type="xsd:string"/>

    hi,
    1. you need to import it as an external definition
    2. you need to close the tags
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="OrderRelease">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ShipNodePersonInfo" minOccurs="0">
    <xsd:complexType>
    <xsd:attribute name="Suffix" type="xsd:string"/>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • IDOC - XI - IDOC scenario. I can't import XSD to Data Type

    Helo!
    I have some problem with creating data tape. I have to create data type similar to IDOC structure which i imported from SAP system. Similar becouse in this DT I need to add some more elements. Becouse the IDOC structure is large I wont to import IDOC structure to this DT automaticly. I try to eksport XSD structure of my IDOC and then import to data type but i can read the monit:
    The tag <element> is not allowed at <<xsd:schema><xsd:element><xsd:element>>.
    I'm beginer in XSD so I don't now how to change this file.
    Can somebody help me on that or explain whot I can do to make this DT.
    Thanks for answer!

    Hi,
    U can import the IDoc XSD to External defination and use it in your Message Mapping and Interfacing Mapping.
    There is no need to create a data type of message type for IDoc.
    External Defination
    <b>External Definition</b> enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to be used as a description for a message.
    U can use this ED as
    1.Inbound/Outbound in the Message Interface.
    2.Source/Target structure for the Message Mapping.
    In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC steps u perform is.
    1.Import the IDoc to XI.
    2.Export the IDoc(i.e XSD format) and save it to the local machine.
    3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
    4.Save it as an XSD file Itself.
    5.Import the XSD file in the IR under the External Defination.
    6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
    Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
    Regards
    Santhosh
    <a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
    Use a Good Subject Line, One Question Per Posting - Award Points

  • Imported xsd's not installed in Service Registry

    Folks:
    I am using the AIA2.2 vmware image. I am wondering why and how core xsd's are not searchable in Services Registry (Business Service Control). First, the import statement of an xsd like "invoice.xsd" has a realtive path in it like "../../../../CommonComponents.xsd". Obviously, this is invalid when you import the schema into a JDEV project. One would think that the xsd's would be available in a services registry and have a http location to be of any use so JDEV can add an invoice schema to a project and be able to build a mapping. Without the ability to see these imports, JDEV chokes on the invoice.xsd and you cannot do a simple thing like transform one variable into another.
    What am I doing wrong here? Why are things like "CommonComponents.xsd" not searchable in the services registry? This looks like a big oversight because I wonder how anyone can use a xsd that has imports which are not visible to JDEV (at least without hacking the file system to find the core component). The steps to rep[roduce are simple:
    1) Create a BPEL project (Asynchronous)
    2) Create a UDDI connection to Services Registry (BSR)
    3) Add any xsd that imports "CommonComponents.xsd" to your BPEL project
    4) Try to change the payload of the request or response message for the BPEL project to one that takes my imported xsd such as invoice
    5) JDEV will give you an error because it does not have access to the imported schema and thus cannot interpret the types correctly and therefore you cannot do step 4 above or even do an XSLT mapping.
    Thanks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    So, my oversight -- you can view these xsd's properly by simply accessing them via Apache url which is the better way to go. They are, in fact, in the registry albeit the search feature does not seem to function properly.
    In any case, just putting this in the thread so others find it easier to do AIA development from the start.

  • Error when Import XSD file

    Hello expert,
       During creating Data Type in the build, I try to import XSD file, but system says:" XSD schema containing the construct "choice" are not permitted here"!
       I found in the XSD, there are this definition:
                                  <xsd:element name="EmploymentInfo" minOccurs="0">
                                       <xsd:complexType mixed="true">
                                            <xsd:choice>
                                                 <xsd:element name="FullTimeEquivalence" type="xsd:decimal"/>
                                                 <xsd:element name="WorktimeInfo" maxOccurs="unbounded">
                                                      <xsd:complexType>
                                                           <xsd:sequence>
                                                                <xsd:element name="Duration" type="xsd:duration"/>
                                                                <xsd:element name="Period" type="xsd:duration"/>
                                                           </xsd:sequence>
                                                      </xsd:complexType>
                                                 </xsd:element>
                                            </xsd:choice>
                                       </xsd:complexType>
                                  </xsd:element>
         Could anybody tell me how to handle this? I am not quite familiar with XSD. Thanks a lot.
    Best regards,
    Shouxin

    Hi,
    replace choice with sequence
    <b><xsd:complexType>
         <xsd:choice>
              <xsd:element name = “A” type=”xsd:string” />
              <xsd:element name= B” type=”xsd:string” maxOccurs=”unbounded” />
         </xsd:choice>
    </xsd:complexType></b>
    is handled identical to
    <b><xsd:complexType>
         <xsd:sequence>
              <xsd:element name = “A” type=”xsd:string” minOccurs=”0” />
              <xsd:element name= B” type=”xsd:string”
    minOccurs=”0” maxOccurs=”unbounded” />
         </xsd:sequence>
    </xsd:complexType></b>
    Regards
    Tarun Telang

  • XSD to create Message interface

    Hi,
    Is is possible to use the XSD imported from the data type and create the external definition to create the message interface directly without creating the message type.
    shree

    Hi,
    I have a xsd exported from a R3 System and it seems that xsd doesn't have a message definition.
    How can I add a message definition by hand?
    Thanks,
    Pedro Leal
    Edited by: Pedro Leal on Feb 27, 2008 4:19 PM

  • Importing xsd problems

    I'm  using two xsd.
    The first one is like  a dictionory the second one form specific.
    In the form specific xsd  I use restriction from the dictionary
    for eg: dictionary.xsd is like this
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://www.example.org/Base"
    targetNamespace="http://www.example.org/Base"
    elementFormDefault="unqualified">
    <xs:element name="A" type="AType" />
    <xs:complexType name="AType">
    <xs:sequence>
    <xs:element name="title" type="xs:string" />
    <xs:element name="name" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    </xs:schema>
    form.xsd is
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://www.example.org/Restriction"
    targetNamespace="http://www.example.org/Restriction"
    xmlns:base="http://www.example.org/Base"
    elementFormDefault="unqualified">
    <xs:import namespace="http://www.example.org/Base"
    schemaLocation="dictionary.xsd" />
    <xs:element name="ARestricted" type="ARestrictedType" />
    <xs:complexType name="ARestrictedType">
    <xs:complexContent>
    <xs:restriction base="base:AType">
    <xs:sequence>
    <xs:element name="name" type="xs:string" />
    </xs:sequence>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    </xs:schema>
    when i import this into livecyle  I'm expecting to see only restricted elements but i see all the elements from dictionary.
    Here in this case I want to see in dataview only "name", but i see both "title" and "name"
    In my actual forms "dictionary xsd" is so big which makes my livecycle designe very slow.
    As a result i get this error message, if i remove some of the elements then livecycle can import.
    Can somebody help me please.

    EMF doesn't provide any tools for doing DTD to XML Schema conversion.
    The first error sounds like there are things with names that aren't well
    formed and the second sounds like references either to a namespace that
    isn't imported or that doesn't define the referenced name.
    as13 wrote:
    > Hello,
    > I got a problem by importing an xsd schema.
    > I converted a dtd to a xsd schema first by Stylus Studio. After that i
    > tried to create a new EMF project by importing the xsd schema.
    >
    > Allways got problems like that:
    >
    > "Problems were detected while validating and converting the XML Schemas
    > Error: XSD: The value 'xxx' of attribute 'name' must conform to
    > pattern '(\i\c*) & ([\i-[:]][\c-[:]]*)' as constrained by
    > 'http://www.w3.org/2001/XMLSchema#NCName' : URI
    > file:/C:/.../EnterpriseDTD.xsd Line 21 Column 4
    >
    > or
    >
    > Error: XSD: Element reference 'UML#xxx' is unresolved : URI
    > file:/C:/.../EnterpriseDTD.xsd Line 569 Column 5
    >
    >
    > Because of the xsd Schema is about 700kB, these problems appears round
    > about 3000 times!!!
    >
    > Does anyone has an idea? I think it´s about a not valid xsd schema,
    > but I don´t know, how i can generate a valid xsd schema out of a DTD.
    > I tried it with stylus Studio an XMLSpy. Couldn´t get a "valid" Schema...
    >
    >
    >
    > greets
    >

  • Importing XSD

    Hello Gurus,
    I am using XI2.0 and now I want to import an XSD. I have been reading around and saw that the best way to do this is, importing an External Definition ot the type XSD. So I have imported my XSD as an External Definition. Now I do not have to create a data type and message type and go directly to my Message infterface definition. When I want to select my message, I go to external definitions but now I can only select elements and not the complete message. I want to select the complete message with all elements as a Message.
    Hope some can help me out!

    Hi,
    at the external definition, go to tab "messages". Check if there's a definition for the whole message, like you expect. If not, try the following things:
    1. Open the XSD with an tool other then XI und check if there is an element definition which has a reference to the root of the message. If not, create it and re-import the XSD. Now you should see it on tab "messages".
    2. If you work with namespace check for the length. If it is longer than 60 characters XI will not show you the message definition.
    Best regards,
    Karlheinz

  • Import XSD from BAPI structure

    Hi all,
    I have a problem when export XSD scchema from BAPI structure and use this schema to create a data type using import XSD schema. The error is following displayed:
    Schema to be handled does not contain a definition of type BAPI_SALESORDER_CREATEFROMDAT2.
    Any idea?????
    Thanks in advance,
              Michele Lazzarato

    Hi Stephan,
    I have created an Abap Proxy and the error message in English as follow:
    Message Interface prova   http://xtel.com/xi/Sales Order references RFC  
    Message BAPI_SALESORDER_CREAT EFROMDAT2   urn:sap-                       
    com:document:sap:rfc:functions    BAPI_SALESORDER_CREATEFROMDAT2.Response
    and the                                                                               
    Message no. SPRX000                                                                               
    Thanks,
                Michele.

  • Getting response object field value as null when importing xsd file in wsdl

    I have created a java webservice using X-Fire 1.2.6 framework and deployed on Tomcat 6.0 server. The response of the service is a java object named LoginDetail.
    Inorder to reuse the basic elements and types we have defined them in a separate Types.xsd file which have been imported in the WSDl file using xsd:import by giving the path to the xsd file.
    Below you can see the portion of the wsdl file
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                   attributeFormDefault="qualified" elementFormDefault="qualified"
                   targetNamespace="http://webservices.gtl.de/xsd">
                   <xsd:import namespace="http://webservices.gtl.de/xsd"
                        schemaLocation="file:///D:/wsdl/LoginTypes.xsd"></xsd:import>
              </xsd:schema>
         </wsdl:types>
    After deploying the application on Tomcat I could access the WSDL using a web browser and after that I could successfully generate webservice client code using using XFire wsgen ant build.
    But when tried to call the service the fields of the response object(in my case it is LoginDetail object) returns null.
    Follwing are the main class used for running the client and the output received as webservice respone.
    Main class
    public static void main(String[] args) {
    CCLoginNewClient client = new CCLoginNewClient();
    CCLoginNewPortType service     = client.getCCLoginNewHttpPort();                         
    LoginDetail loginDetail = service.getLogin("CCLoginNew", "DE", "DE", "100", "0", "CC", "15","9344");
    System.out.println("service got in response : "+loginDetail.getService());                    
    Output
    service got in response : null
    is this the right way to import an xsd file in a wsdl file?
    Any input would be appreciated!
    Thanks in advance

    PramodDas wrote:
    Output
    service got in response : nullCheck with Apache TCPMonitor what response you are receiving from web service.
    is this the right way to import an xsd file in a wsdl file?Make sure that you really need import, not the include. However, I guess it has nothing do with the actual issue. It just to make sure that you are using right option.

  • To Import XSD file along with WSDL file in ED

    Dear All,
    I am doing a scenario web service1 —XI—RFC—web service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.
    My client (web service2) has given me the web service (WSDL) file along with XSD file.
    In the wsdl file there are number of elements and complex types.
    <xs:element name="GetCustomer">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="authentication" type="xx:AuthInfo"/>
                   <xs:element name="CompanyName" type=" xx:AuthInfo "/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.
    My questions are
    1)     Do I have to import the XSD file in ED or not.
    2)     How do I map this XSD
    3)     As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    4)     Can some one help with any docs please..
    Thanks in advance

    Hi,
    >>Do I have to import the XSD file in ED or not
    If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.
    >>How do I map this XSD
    XSD are same as Message Types. So create a MM and choose your XSD.
    >>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    Yes you have to because you are taking the responce from RFC and going to give it to WS2.
    BPM steps:
    1) receive (open sync bridge)
    2) transformation 1
    3) send (snyc)
    4)transformation 2
    3) send (close sync bridge)
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    Regards
    Suraj

  • How to import  XSD?

    Hi Friends,
    I have export the IDOC to XSD. If i want to import XSD, i get this Error:
    - <b>Schema to be handled does not contain a definition of type ....</b>
    How do you import a XSD structure?
    Thanks in advance
    Fatih

    Can you test it?
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema targetNamespace="urn:cts-com:BPM" xmlns="urn:cts-com:BPM" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:element name="BANK_CREATE01">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element name="IDOC" type="BANK_CREATE.BANK_CREATE01"/>
                   </xsd:sequence>
              </xsd:complexType>
         </xsd:element>
         <xsd:complexType name="BANK_CREATE01.E1BANK_CREATE">
              <xsd:annotation>
                   <xsd:documentation>Header segment</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="BANK_CTRY" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>Bank country key</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BANK_KEY" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>Bank Keys</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BANK_METHOD" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>Check digit calculation method</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BANK_FORMATTING" minOccurs="0">
                        <xsd:annotation>
                             <xsd:documentation>Format of File with Bank Data</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="E1BP1011_ADDRESS" type="BANK_CREATE01.E1BP1011_ADDRESS" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
                   <xsd:element name="E1BPADR1" type="BANK_CREATE01.E1BPADR1" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
              </xsd:sequence>
              <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
         </xsd:complexType>
         <xsd:complexType name="BANK_CREATE.BANK_CREATE01">
              <xsd:annotation>
                   <xsd:documentation>Create Bank</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="EDI_DC40" type="EDI_DC40.BANK_CREATE.BANK_CREATE01"/>
                   <xsd:element name="E1BANK_CREATE" type="BANK_CREATE01.E1BANK_CREATE" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
              </xsd:sequence>
              <xsd:attribute name="BEGIN" type="xsd:string" fixed="1" use="required" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
         </xsd:complexType>
    </xsd:schema>

  • How to create a generic TYPES?

    hello!
    what i try to do is following
    eg:
    when i call my function the user has the possibility to check the flag "show_button = 'X', and exports a table
    when this flag is checked i want to display an icon in the first row of this table, so i need to extend the table structure which i import and add another attribute.
    what i actually tried to achieve is this (but this is not working of course)
    function
    import:
          i_outtab type standard table.
    field-symbols:
          <itab> type standard table.
    assign i_outtab to <itab>.
    TYPES: begin of mytyp.
       types: i_bt type iconname.
      INCLUDE STRUCTURE <itab>
    TYPES: end of mytyp.
    and then i create a table with the type mytyp (which is not working, but i shows what i try to do)
    so is there a way to do this genericly?

    You can do that using the ABAP Run Time Type Services.
    Example:
    I have a function module Y_TEST with one Importing Parameter:
    *"  IMPORTING
    *"     REFERENCE(IP_IT_DATA) TYPE  ANY TABLE
    I have no idea about the table-structure and I want to add a field X_SELECTED of type XFELD to the end of the table to display it using CL_SALV_TABLE or something - this is how I do it:
    FUNCTION y_test.
    *"  IMPORTING
    *"     REFERENCE(IP_IT_DATA) TYPE  ANY TABLE
      DATA:
        gr_tabtype TYPE REF TO cl_abap_tabledescr,
        gr_struc   TYPE REF TO cl_abap_structdescr,
        lr_itab    TYPE REF TO data,
        it_component TYPE cl_abap_structdescr=>component_table,
        wa_component LIKE LINE OF it_component.
      FIELD-SYMBOLS:
        <wa> TYPE ANY.
    * Reading 1st line of itab and getting structure ->
      LOOP AT ip_it_data ASSIGNING <wa>.
        gr_struc ?= cl_abap_typedescr=>describe_by_data( <wa> ).
        EXIT.
      ENDLOOP. "ip_it_data
    * Getting all components ->
      CHECK gr_struc IS BOUND.
      it_component = gr_struc->get_components( ).
    * Adding new field (X_SELECTED) to Component-Table ->
      wa_component-name = 'X_SELECTED'.
      wa_component-type ?= cl_abap_typedescr=>describe_by_name( 'XFELD ').
      INSERT wa_component INTO TABLE it_component.
    * Creating new structure-ref ->
      CLEAR gr_struc.
          CALL METHOD cl_abap_structdescr=>create
            EXPORTING
              p_components = it_component
            RECEIVING
              p_result     = gr_struc.
    * Creating new table-ref ->
          CALL METHOD cl_abap_tabledescr=>create
            EXPORTING
              p_line_type  = gr_struc
            RECEIVING
              p_result     = gr_tabtype.
    * Creating itab with our table-ref ->
      CREATE DATA lr_itab TYPE HANDLE gr_tabtype.
    ENDFUNCTION.
    Hope that helped ...

  • XSD file Created in PI 7.0 is not working in MDM

    Hi Experts,
    Need your help on the below scenario:
    I have created the data types in in PI 7.0 and exported XSD file but, while connecting to syndicator (by using XML Schema file option)  system  is giving root element is missg error message. But, if i create the XSD file By using 3rd party XSD tools that XSD file working fine..
    Can any one let me know the reason why the XSD file created by PI System is giving the Problem ?
    Thanks in Advance
    Mahesh

    Hi Mahesh,
    usually XSDs from PI do not contain the <xsd:element>Name your Root Element</xsd:element> definition that is required for MDM Syndicator. If you compare the files as suggested, you'll notice something like that in the XSD of the third party tool. Still you could add this definition manually to the XSD from PI. Then the XSD will work, too.
    Best regards
    Michael

Maybe you are looking for

  • IPod Calendar events 1 hour off

    Recently all the calendar events on my iPod's calendar are an hour before all the events in iCal. I've tried replacing all the calendars on the iPod, but the problem persists. Any ideas?

  • Photoshop cs6 could not complete new video layers from file command because the footage is not a recognized format

    I am getting this message when importing stills into photoshop CS6 Extended to make a time lapse video. I have watched many tutorials and follow them but always get stuck at this point. I have tried various formats and sizes TIFF JPEG etc. The files

  • Recieved quantity

    hai gurus, I need to generate a report for list of GR balances. i need what is recieved quantity, n Qantity invoiced.. how to calculate them. any idea plz help me. regards Priya

  • Premiere Elements 10, unable to launch projects...

    Hi there, first post. I've managed to sort out one problem already this morning - I've now got virtualdub set up for processing files before I import them to PE. However I'm still stumped on why it (at the moment) still crashes (just 'stopped working

  • Replicat Abend (error COLMAP)

    Hi all, anybody can help me to resolv this error. when i try to start replicat on target DB with cancatenates,,i got this message error,, 2011-02-11 16:53:18 INFO OGG-01298 Column function diagnostic message: could not find column TGL_MSK. ...L = @ST