Why should we create data type

Hi all,
I have a basic question!
why do we create data type and then wrap it as message type?
why dont we directly create a message type and use that ?
please give the answers. Thanks in Advance.

Hi Seshu,
Please go through below links, you get answer
message type and datatype
Difference between Data type and Message type - Process Integration - SCN Wiki
Regards,
Krupa

Similar Messages

  • Why need message type when u create data type...

    why need message type when u create data type...

    Hi,
    A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
    ·        More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
    ·        When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
    For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstract types that are not yet fixed to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message.
    A message type does not define the direction of the message exchange, in other words, whether it is a request or a response. In exceptional cases you can use the same message type for both the request and the response message.
    A message type has the following characteristics:
    ·        It comprises exactly one data type, which determines the content of the message to be transferred.
    ·        It is identified by a name and an XML namespace. The name (together with the namespace) of a message type is located in the uppermost tag of the message to be exchanged. This is an element tag.
    You have defined a message type GreetingRes that references a simple data type of type xsd:string. The XML namespace of the message type is http://sap.com/xi/myExample. The corresponding payload might look like this:
    <?xml version="1.0" encoding="utf-8" ?>
    <ns1:GreetingRes xmlns:ns1="http://sap.com/xi/myExample"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       Hello Mrs. Miller
    </ns1:GreetingRes>
    You can specify how a message type is used in more detail in the description
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • Why should we create index on  the table after inserting data ?

    Please tell me the Reason, why should we create index on the table after inserting data .
    while we can also create index on the table before insertion of the data.

    The choice depends on a number of factors, the main being how many rows are going to be inserted in the table as a percentage of the existing rows, or the percentage growth.
    Creating index after a table has been populated works better when the tables are large or the inserts are large for the following reasons
    1. The sort and creation of index is more efficient when done in batch and written in bulk. So works faster.
    2. When the index is being written blocks get acquired as more data gets written. So, when a large number of rows get inserted in a table that already has an index , the index data blocks start splitting / chaining. This increases the "depth" of the inverted b-tree makes and that makes the index less efficient on I/O. Creating index after data has been inserted allows Orale to create optical block distribution/ reduce splitting / chaining
    3. If an index exists then it too is routed through the undo / redo processes. Thats an overhead which is avoided when you create index after populating the table.
    Regards

  • Error while creating data type

    Hi
    I am creating data type for the scenario from File to IDOC
    Namespace urn:xiworkshop:groupxx:legacy is not defined in the software component version NEWPRODUCT , 100 of sap Object Message Type Vendor | urn:xiworkshop:groupxx:legacy references the inactive object Data Type Vendor | urn:xiworkshop:groupxx:legacy
    Please help me

    Hi;
    First activate your namespace and then create the data type.
    Namespace + default datatypes should be activated together.
    Then your data type
    Mudit

  • 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

  • Create Data Type from XSD

    Hey guys
    i need to create Data Type from and XSD,in the beginning i had an XML document which i converted to XSD using Altova ,then i imported this XSD in IR under External definition,now how should i go ahead with creating Data Type?
    my sample XSD is something like this
    <?xml version="1.0" encoding="UTF-8"?>
    <!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
         <xs:element name="WorkOrderNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:short">
                        <xs:enumeration value="10942"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="VendorNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:int">
                        <xs:enumeration value="109845"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
    Its not the complete XSD,just the first few lines.
    thanx
    Ahmad

    Hey Prabhu
    my XSD looks like this
    <?xml version="1.0" encoding="UTF-8"?>
    <!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
         <xs:element name="WorkOrderNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:short">
                        <xs:enumeration value="10942"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="VendorNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:int">
                        <xs:enumeration value="109845"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="UnitPrice">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MonetaryAmount"/>
                        <xs:element ref="UnitOfMeasureCode"/>
                        <xs:element ref="CurrencyCode"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="UnitOfMeasureCode">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="EA"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="TotalLineItems">
              <xs:simpleType>
                   <xs:restriction base="xs:byte">
                        <xs:enumeration value="6"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="TaxTypeCode">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="GoodsAndServicesTax"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="TaxReference">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="GST"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="TaxAmount">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MonetaryAmount"/>
                        <xs:element ref="CurrencyCode"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="Tax">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="TaxTypeCode"/>
                        <xs:element ref="TaxAmount"/>
                        <xs:element ref="TaxReference"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="Requisition">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="Number"/>
                        <xs:element ref="LineItemNumber"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="Quantity">
              <xs:simpleType>
                   <xs:restriction base="xs:decimal">
                        <xs:enumeration value="1.0"/>
                        <xs:enumeration value="2.0"/>
                        <xs:enumeration value="6.0"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="PrimaryCurrency">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="CurrencyCode"/>
                        <xs:element ref="ExchangeRate"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="Pricing">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="UnitPrice"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="PaymentTerms">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="NT30"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="Number">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="Q173849"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="MonetaryAmount">
              <xs:simpleType>
                   <xs:restriction base="xs:decimal">
                        <xs:enumeration value="1.98"/>
                        <xs:enumeration value="12.48"/>
                        <xs:enumeration value="12.63"/>
                        <xs:enumeration value="16.75"/>
                        <xs:enumeration value="24.96"/>
                        <xs:enumeration value="240.0"/>
                        <xs:enumeration value="33.84"/>
                        <xs:enumeration value="43.83"/>
                        <xs:enumeration value="5.64"/>
                        <xs:enumeration value="74.81"/>
                        <xs:enumeration value="87.66"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="LineItemTotal">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MonetaryAmount"/>
                        <xs:element ref="CurrencyCode"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="LineItemNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:byte">
                        <xs:enumeration value="10"/>
                        <xs:enumeration value="20"/>
                        <xs:enumeration value="30"/>
                        <xs:enumeration value="40"/>
                        <xs:enumeration value="50"/>
                        <xs:enumeration value="60"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="LineItemMaterialNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="108739"/>
                        <xs:enumeration value="192740-A"/>
                        <xs:enumeration value="380495"/>
                        <xs:enumeration value="43998"/>
                        <xs:enumeration value="54727S"/>
                        <xs:enumeration value="5746"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="LineItemInformation">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="LineItemMaterialNumber"/>
                        <xs:element ref="LineItemDescription"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="LineItemDescription">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="ABSRBT PAD 17 IN X 19 IN X 3/8 IN UNIV P"/>
                        <xs:enumeration value="BSHG HEX 1 IN X 1/2 IN THD FS A105N"/>
                        <xs:enumeration value="GGE 4 IN 1M / 7000 DL SCALE 1/2 IN LM WI"/>
                        <xs:enumeration value="PEN REC RD MED GRAPHIC 39-202"/>
                        <xs:enumeration value="PL ORF 3 IN .5 IN ORF SER 500 316 SS"/>
                        <xs:enumeration value="WPR F-200 FLC NOV LABEL 20"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="Invoices">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="Invoice"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceTypeCode">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="ProductOrService"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="InvoiceTotal">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MonetaryAmount"/>
                        <xs:element ref="CurrencyCode"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceSummary">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="TotalLineItems"/>
                        <xs:element ref="InvoiceTotal"/>
                        <xs:element ref="Tax"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceQuantity">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="Quantity"/>
                        <xs:element ref="UnitOfMeasureCode"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceProperties">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="InvoiceNumber"/>
                        <xs:element ref="InvoiceDate"/>
                        <xs:element ref="VendorNumber"/>
                        <xs:element ref="InvoiceTypeCode"/>
                        <xs:element ref="PrimaryCurrency"/>
                        <xs:element ref="PaymentTerms"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceNumber">
              <xs:simpleType>
                   <xs:restriction base="xs:int">
                        <xs:enumeration value="98815236"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="InvoiceLineItem">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="WorkOrderNumber"/>
                        <xs:element ref="LineItemNumber"/>
                        <xs:element ref="InvoiceQuantity"/>
                        <xs:element ref="LineItemInformation"/>
                        <xs:element ref="Pricing"/>
                        <xs:element ref="LineItemTotal"/>
                        <xs:element ref="Requisition"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceDetails">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="InvoiceLineItem" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="InvoiceDate">
              <xs:simpleType>
                   <xs:restriction base="xs:date">
                        <xs:enumeration value="2007-01-25"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="Invoice">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="InvoiceProperties"/>
                        <xs:element ref="InvoiceDetails"/>
                        <xs:element ref="InvoiceSummary"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="ExchangeRate">
              <xs:complexType/>
         </xs:element>
         <xs:element name="CurrencyCode">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="CAD"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
    </xs:schema>
    can you please tell me how to nest the structures,i m fairly new to XSD and stuffs
    thanx
    ahmad

  • Problem in creating data type

    hi..
    i've problem in creating data type in xi after importing idoc from the R/3 sender
    plz tell me the basic steps for creating data type in the receiver i.e xi.....
    thanks in advance

    Hi,
    You don't need to create a data type after importing the IDOC.
    Idoc itself acts as message type and message interface.
    check this for creating a data type..
    http://help.sap.com/saphelp_nw70/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
    Thanks,
    Vijaya.

  • Validation while create data type

    HI All ,
    I have a pop-up in my report that user can create data type in  didc,
    There is a simple way to support validation for data types ,
    I have pop-up where the user need  to provide name of attribute
    he need to create and the data type for it (char ,string ,int etc )
    and he also need to provide the leng of the attribute he want to create
    (e.g. char10 ) and also decimal places .
    the issue here that i need to do some validation in the pop-up
    for e.g. if user choose
    case 1
    name     - attribute1
    datatype  - string
    leng   - in this case he dont need to provide leng (string )
    dec - dont need to provide (string )
    case 2
    name     - attribute1
    datatype  - char 
    leng   - 10
    dec - dont need to provide (char )
    Any idea how to do this validation in a simple way  (maybe to use standard functionlity)
    Regards
    Alex

    HI Keshav.
    What i did is created a popup with FM in the popup i have 4 field
    the field with the data type which i want to trigger event to it is domain and not ref to FM
    The ppoup have 4 field
    attr name
    datatype
    length
    decimal
    so from what you are say there is not option to trigger event when the user press F4
    and choose a entry from it ,
    since what i want to do is that if user for instance chose string i want that the next to fields (length and dec ) will be
    remove from the popup since he dont need them .
    and for he choose char the the decimal field will remove from the popup
    Any idea how to solve this issue ?
    Regards
    Alex
    Edited by: Alex Dean on Oct 12, 2010 3:02 PM

  • What should be the data type for a field in ztable?

    i am desing a ztable , wht should be the datatype for a field if i want to enter values like -1.5 and -2.5 , negative values with decimals what should be the data type???

    declare as P type. TYPE P DECIMALS 1
    Type P data allows digits after the decimal point. The number of decimal places is generic, and is determined in the program. The value range of type P data depends on its size and the number of digits after the decimal point. The valid size can be any value from 1 to 16 bytes. Two decimal digits are packed into one byte, while the last byte contains one digit and the sign. Up to 14 digits are allowed after the decimal point. The initial value is zero. When working with type P data, it is a good idea to set the program attribute Fixed point arithmetic.Otherwise, type P numbers are treated as integers.
    You can use type P data for such values as distances, weights, amounts of money, and so on.
    Also check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb2fd9358411d1829f0000e829fbfe/content.htm
    Regards,
    Maha

  • How  create data type for coulmn name having special characters in IR

    hi ,
    any idea how to create how to do create data type for coulmn name having special characters

    Hi Amit,
    Can you ellaborate ?
    Actually if you are reading a file(or anything else) which contains special characters, the data type can be created as done for other interfaces. But it is in the adapters that we actually take care of handling these special characters.
    ShabZ

  • Why should we create Product.......

    Hi experts,
    Why should we have to create Product? what is the use?
    In IR we have to Import SoftwareComponent then in whole senario we dont use it then why should we create it........
    what is the use of version?
    usefull answer will be rewarded.
    Regards,
    Phani

    HI,
    The classes of the SAP schema, the software components and their versions, and the software products and their versions are the basis for the component information
    Product: Represents a collection of all versions of a product. A product is a unit that can be delivered, is visible to the customer, and that is installable and renewable. In an SAP environment, a product corresponds to an SAP technical component.
    ·        Product Version: Represents a particular version of a product.
    ·        Software Component: Represents a collection of all versions of a software component. Software components represent the reusable modules of a product. They can be upgraded or have patches installed.
    ·        Software Component Version: Represents a particular version of a software component.
    ·        Software Feature: Represents a particular aspect of the product functions. It is a logical link between Product Version and Software Component Version
    http://help.sap.com/saphelp_nw04/helpdata/de/29/17647d028113439108ce1161263b6e/content.htm
    Regards
    Chilla

  • Creating data types

    Hi
    How do u create a data type when u get an input file.
    How do u know when to create header , footer n all?
    Can some one tell me or send a url on how to create data types. would be of great help!
    Thanks!

    HI,
    Generally identifying the structure from the input file need  some analysis work.
    You may refer some of the below tips while creating the data types
    1. List down the input structure of data fields  from input file.
    2. Decide the Header and detail information based on the data and go for sub-structure.
    3. With File adapter try to maintain the structure level max. upto 2.
      i.e. Root>Header>Fields etc.
    4. Try to avoid the substructure for the internal fields.
    5. Decide the Occurances fo every root and sub structures and fields.
    6. Identify if there any relations within Header and detail fields.etc.
    Check with SAP Help for various activities
    http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/content.htm
    Thanks
    Swarup

  • Create data type string

    HI
    There is a way to create date type string using the command
    Create data type "string"...
    I know that I can create data type C but string dont have any restrication so how I can hanlde it ?
    Regards
    Joy

    Hi,
    You can use the create data statement:
    DATA: lo_data TYPE REF TO data.
    FIELD-SYMBOLS: <str> TYPE ANY.
    CREATE DATA lo_data TYPE string.
    ASSIGN lo_data->* TO <str>.
    Here <str> will be of type string.
    Kr,
    m.

  • NWBC:CREATE DATA:Type WDR_APP_PROP_DISP_LOADINGPAGE is no valid data type

    HI Experts,
    We want to access our servers through NWBC. All setting and configuration related is done also services in SICF are activated.But when we are in to NWBC it shows following error. Kindly help to resolve this
    Error when processing your request
    What has happened?
    The URL https://hpi-dev.domainname.local:44301/sap/bc/webdynpro/sap/powl was not called due to an error.
    Note
    The following error text was processed in the system ERD : CREATE DATA: The specified type WDR_APP_PROP_DISP_LOADINGPAGE is no valid data type.
    The error occurred on the application server HPI-DEV_ERD_01 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CONVERT_XML_TO_STRING of program CL_WDR_CONFIGURATION_UTILS====CP
    Method: CONVERT_XML_TO_STRING of program CL_WDR_CONFIG_APPL_PARAM======CP
    Method: READ_DATA of program CL_WDR_CONFIG_APPL_PARAM======CP
    Method: INIT_DATA of program CL_WDR_CONFIG_APPL_PARAM======CP
    Method: GET_DATA of program CL_WDR_CONFIG_APPL_PARAM======CP
    Method: CONSTRUCTOR of program SAPLWDR_RUNTIME_REPOSITORY
    Function: WDR_GET_REPOSITORY of program SAPLWDR_RUNTIME_REPOSITORY
    Method: IF_WDR_RUNTIME~GET_RR_APPLICATION of program CL_WDR_MAIN_TASK==============CP
    Method: CREATE_APPLICATION of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system ERD in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server HPI-DEV_ERD_01 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server HPI-DEV_ERD_01 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-https -c: 100 -u: SRAUT -l: E -s: ERD -i: HPI-DEV_ERD_01 -w: 0 -d: 20111220 -t: 003857 -v: RABAX_STATE -e: CREATE_DATA_UNKNOWN_TYPE
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team

    Hi,
    Regarding the issue reported by you kinly refer in detail the solution section of the following SAP Note:
      1432358 - Starting application with Loading Animation
    It seems that the data element WDR_APP_PROP_DISP_LOADINGPAGE is not created in your system.
    This note should help you out.
    Regards,
    Abhishek

  • How to do create data type for coulmn name as QS$FGD .

    hi ,
    In my database i have a column as QS$FGD.
    How do i map it in XI , since $ is not accepted when u create a data type.
    One way is to give alias at the databse level for the column . is there any other way to slove it .
    Thanks
    amit

    Hi Amit,
            Were you able to solve your issue? I'm facing the similar issue now. My DB table contains field names with '.' i.e. say xyz.abc. How to solve this??
    I feel SP could be an alternative??
    Thanks,
    Hussain.

Maybe you are looking for

  • Sub ledger Postings - EBS

    Hi All, I wanted to confirm whether sub ledger posting through Bank Statement upload works only in case of customers and not in case of vendors. I m trying the carry out sub ledger posting for vendors. however SAP is determining account type D only f

  • Upgrade MS Outlook, all info missing

    Help!!! Upgrade my Microsoft Office Outlook recently and all my meetings and appointments missing for Outlook calendar. Even if I add new appointment it still won't show in my outlook calendar.. Wonder where i did wrong..

  • Tree Nodes

    Hi, I have Tree Node UI Element with 5 Nodes. Tree   |   |- Node 1   |- Node 2   |- Node 3   |- Node 4   |- Node 5 When I click on the page and the Tree UI shows up, I would like Node 3 to be expanded and not any other node. Is there any way I could

  • Problem about aix and java.util.Date

    Hello, I am using AIX 5.1 with JDK 1.4 and i got a problem using this JDK 1.4 I was using the jdk 1.2.2 and it gets to me the correct date from the system ... i've never exported any environment variable like lc_type, lang , etc ... but now, using jd

  • How to get into SAP Career when having 10 year experience in sales?

    Dear all, Please suggest me how to get into SAP career, I have 10 year exp in sales specialized in Channel sales in consumer durable industry in India, Is there any scope for sales professional in SAP? I dont have any experience in SAP, but want to l