Skip to Content
avatar image
Former Member

Datatypes in InterfaceObjects

Hi,

Today while creating a scenario just gone through types of datatypes avaliable in while creating datastructure. And suprised to see it was around 44 as mentioned below.

<b>xsd:string>>use:to specify string >> value:" Hi"</b>

<b>xsd:integer>>use: to specify integer>>value:123</b>

<b>xsd:boolean>>use: to specify boolen value>>value:true/false or 0or1</b>

<b>xsd:short>>use:to specify short value>>value:123

xsd:byte>>use:to specify byte value>>value:123

xsd:float>>use:to specify integer with decimal>>value:123.05

xsd:base64Binary>>use:to specify base64Binary>>value:456789AB

xsd:hexBinary>>use:to specity the binaaryvalue>>value:010101</b>

xsd:decimal

<b>xsd:double>>use:tospecify double value>>value:-3.140...0E+02

xsd:time>>use:to specify the time>>value:20:15:01

xsd:dateTime>>use:to specify the timewithdate>>value:2002-02-0420:15:01</b>xsd:duration

<b>xsd:date>>use:to specify the date>>value:2002-02-04</b>

xsd:gMonth

xsd:gYear

xsd:gYearMonth

xsd:gDay

xsd:gMonthDay

xsd:QName

xsd:anyURI

xsd:NOTATION

xsd:normalizedString

xsd:token

xsd:unsignedByte

xsd:positiveInteger

xsd:negativeInteger

xsd:nonNegativeInteger

xsd:nonPositiveInteger

xsd:int

xsd:unsignedInt

xsd:long

xsd:unsignedLong

xsd:unsignedShort

xsd:Name

xsd:NCName

xsd:language

xsd:ID

xsd:IDREF

xsd:IDREFS

xsd:ENTITY

xsd:ENTITIES

xsd:NMTOKEN

If don't mine like to know the details when we will be using and few which I marked in bold was know by me as it was come in common scenario. Like to know the same way which would be help for me in future reference.

the below is not given much detail i suppose

http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/content.htm

http://help.sap.com/search/highlightContent.jsp

Regards,

Senthil.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 06, 2007 at 01:59 PM

    Hi,

    <b>anyURI</b>

    The data must conform to the syntax of a Uniform Resource Identifier (URI), as defined in RFC 2396 as amended by RFC 2732. Example: "http://www.nmt.edu/tcc/" is the URI for the New Mexico Tech Computer Center's index page.

    <b>base64Binary</b>

    Represents a sequence of binary octets (bytes) encoded according to RFC 2045, the standard defining the MIME types (look under “6.8 Base64 Content-Transfer-Encoding”).

    <b>boolean</b>

    A Boolean true or false value. Representations of true are "true" and "1"; false is denoted as "false" or "0".

    <b>byte</b>

    A signed 8-bit integer in the range [-256, 255]. Derived from the short datatype.

    <b>date</b>

    Represents a specific date. The syntax is the same as that for the date part of dateTime, with an optional time zone indicator. Example: "1889-09-24".

    <b>dateTime</b>

    Represents a specific instant of time. It has the form YYYY-MM-DDThh:mm:ss folowed by an optional time-zone suffix.

    YYYY is the year, MM is the month number, DD is the day number, hh the hour in 24-hour format, mm the minute, and ss the second (a decimal and fraction are allowed for the seconds part).

    The optional zone suffix is either "Z" for Universal Coordinate Time (UCT), or a time offset of the form "hh:mm", giving the difference between UCT and local time in hours and minutes.

    Example: "2004-10-31T21:40:35.5-07:00" is a time on Halloween 2004 in Mountain Standard time. The equivalent UCT would be "2004-11-01T02:40:35.5Z".

    <b>decimal</b>

    Any base-10 fixed-point number. There must be at least one digit to the left of the decimal point, and a leading "" or "-" sign is allowed. Examples: "42", "-3.14159", "0.004".

    <b>double</b>

    A 64-bit floating-point decimal number as specified in the IEEE 754-1985 standard. The external form is the same as the float datatype.

    <b>duration</b>

    Represents a duration of time, as a composite of years, months, days, hours, minutes, and seconds. The syntax of a duration value has these parts:

    If the duration is negative, it starts with "-".

    A capital "P" is always included.

    If the duration has a years part, the number of years is next, followed by a capital "Y".

    If there is a months part, it is next, followed by capital "M".

    If there is a days part, it is next, followed by capital "D".

    If there are any hours, minutes, or seconds in the duration, a capital "T" comes next; otherwise the duration ends here.

    If there is an hours part, it is next, followed by capital "H".

    If there is a minutes part, it is next, followed by capital "M".

    If there is a seconds part, it is next, followed by capital "S". You can use a decimal point and fraction to specify part of a second.

    Missing parts are assumed to be zero. Examples: "P1347Y" is a duration of 1347 Gregorian years; "P1Y2MT2H5.6S" is a duration of one year, two months, two hours, and 5.6 seconds.

    <b>

    float</b>

    A 32-bit floating-point decimal number as specified in the IEEE 754-1985 standard. Allowable values are the same as in the decimal type, optionally followed by an exponent, or one of the special values "INF" (positive infinity), "-INF" (negative infinity), or "NaN" (not a number).

    The exponent starts with either "e" or "E", optionally followed by a sign, and one or more digits.

    Example: "6.0235e-23".

    <b>gDay</b>

    A day of the month in the Gregorian calendar. The syntax is " -DD" where DD is the day of the month. Example: the 27th of each month would be represented as " -27".

    <b>gMonth</b>

    A month number in the Gregorian calendar. The syntax is " MM ", where MM is the month number. For example, " 06 " represents the month of June.

    <b>gMonthDay</b>

    A Gregorian month and day as " MM-DD". Example: " 07-04" is the Fourth of July.

    <b>gYear</b>

    A Gregorian year, specified as YYYY. Example: "1889".

    <b>gYearMonth</b>

    A Gregorian year and month. The syntax is YYYY-MM. Example: "1995-08" represents August 1995.

    <b>hexBinary</b>

    Represents a sequence of octets (bytes), each given as two hexadecimal digits. Example: "0047dedbef" is five octets.

    <b>ID</b>

    A unique identifier as in the ID attribute type from the XML standard.

    Derived from the NCName datatype.

    <b>IDREF, IDREFS</b>

    An IDREF value is a reference to a unique identifier as defined under attribute types in the XML standard. An IDREFS value is a space-separated sequence of such references.

    Derived from the NCName datatype.

    <b>int</b>

    Represents a 32-bit signed integer in the range [-2,147,483,648, 2,147,483,647]. Derived from the long datatype.

    <b>integer</b>

    Represents a signed integer. Values may begin with an optional "+" or "-" sign. Derived from the decimal datatype.

    <b>language</b>

    One of the standardized language codes defined in RFC 1766. Example: "fj" for Fijian. Derived from the token type.

    <b>long</b>

    A signed, extended-precision integer; at least 18 digits are guaranteed. Derived from the integer datatype.

    <b>Name</b>

    A name as defined in the XML standard:. The first character can be a letter or underbar “_”, and the remaining characters may be letters, underbars, hyphen “-”, period “.”, or colon “:”.

    Derived from the token datatype.

    <b>NCName</b>

    The local part of a qualified name. See the NCName definition in the document Namespaces in XML.

    Derived from the name datatype.

    <b>negativeInteger</b>

    Represents an integer less than zero. Derived from the nonPositiveInteger datatype.

    <b>NMTOKEN, NMTOKENS</b>

    Any sequence of name characters, defined in the XML standard: letters, underbars “_”, hyphen “-”, period “.”, or colon “:”.

    A NMTOKENS data value is a space-separated sequence of NMTOKEN values.

    Derived from the NMTOKEN datatype.

    <b>nonNegativeInteger</b>

    An integer greater than or equal to zero. Derived from the integer datatype.

    <b>nonPositiveInteger</b>

    An integer less than or equal to zero. Derived from the integer datatype.

    <b>normalizedString</b>

    This datatype describes a “normalized” string, meaning that it cannot include newline (LF), return (CR), or tab (HT) characters.

    Derived from the string type.

    <b>positiveInteger</b>

    An extended-precision integer greater than zero. Derived from the nonNegativeInteger datatype.

    <b>QName</b>

    An XML qualified name, such as "xsl:stylesheet".

    <b>short</b>

    A 16-bit signed integer in the range [-32,768, 32,767]. Derived from the int datatype.

    <b>string</b>

    Any sequence of zero or more characters.

    <b>time</b>

    A moment of time that repeats every day. The syntax is the same as that for dateTime, omitting everything up to and including the separator "T". Examples: "00:00:00" is midnight, and "13:04:00" is an hour and four minutes after noon.

    <b>token</b>

    The values of this type represent tokenized strings. They may not contain newline (LF) or tab (HT) characters. They may not start or end with whitespace. The only occurrences of whitespace allowed inside the string are single spaces, never multiple spaces together. Derived from normalizedString.

    <b>unsignedByte</b>

    An unsigned 16-bit integer in the range [0, 255]. Derived from the unsignedShort datatype.

    <b>unsignedInt</b>

    An unsigned 32-bit integer in the range [0, 4,294,967,295]. Derived from the unsignedLong datatype.

    <b>unsignedLong</b>

    An unsigned, extended-precision integer. Derived from the nonNegativeInteger datatype.

    <b>unsignedShort</b>

    An unsigned 16-bit integer in the range [0, 65,535]. Derived from the unsignedInt datatype.

    <b></b>

    anything missing ?

    regards,

    Robin

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 06, 2007 at 01:53 PM

    Hi Senthil,

    here is everything you need:

    <b>XML Schema Tutorial:</b>

    http://www.w3schools.com/schema/default.asp

    Regards Mario

    Add comment
    10|10000 characters needed characters exceeded