Decimal data type

Hi,
I know this is a very silly thing to ask.
But i got a doubt regarding the data types.
look at this:
tables: zap. " this is a custom table
in this custom table "zap" the field "price" is defined like this:
field| field type| data type| length| dec. point|
price| zap_price| dec | 11 | 6
now in the program there is a field declared like this:
data: zap like zap-price.
now my doubt is:
for the field zap-price is the value can be like this?
a) 46578.654876
or
b) 4687.645478
which one is correct.
Please let me know.
thnx for the help.,

Hi,
You a) point is right & so is point b).
Your definition means..
the total length of the field is 11,out of which a max of 6 places for decimals & ofcourse 1 will be assigned to the sign(- or +).
Message was edited by: Phani Kiran Nudurupati

Similar Messages

Dynamically Find out the Integer and Decimal Data Type of a Column

Table: test (INTE number, DECI number(7,2))
Try to dynamically determine the column type.
Using select data_type from user_tab_columns. It only returns NUMBER which does not indicate if the column is an integer or decimal data type.
Is there a way to dynamically determine if a column is integer or decimal type?
Thanks

First of all your column INTE stores not just integers but any franctional numbers too:
SQL> create table test(INTE number, DECI number(7,2))
2 /
Table created.
SQL> insert
2    into test
3    values(
4           10.99,
5           10.99
6          )
7 /
1 row created.
SQL> select *
2    from test
3 /
      INTE       DECI
     10.99      10.99
SQL>If you want to declare column as integer you use either NUMBER(n) or INTEGER. And, as others already pointed out, you can check DATA_PRECISION & DATA_SCALE in data dictionary view USER/ALL/DBA_TAB_COLUMNS.
SY.

Decimal data type multiplied by quantity data type

Hi all,
i have a requirement where i have to multiply 3 fields, and get that result into fourth field.
example:
data: f1 type dec,    [Data type - Decimal; length 7]
        f2 type dec,    [Data type - Decimal; length 7]
        f3 type quan. [Data type - Quantity; length 17]
data: f4 type ??
f4 = f1 * f2 * f3.
what will the data type of field f4?
Will field f4 be of decimal type. If yes, then what is the declaration syntax of f4.
can i declare it as:
data: f4 type dec.
When i do this, i get an error saying type DEC is unknown.
NOTE: For your information.I AM IMPLEMENTING THIS IN A method inside a BADI.
Points will be rewarded.
Thanks in advance.

Hi
U need to use a reference to a dictionary field (like MSEG-MENGE) because there isn't an abap type to be used, the data type are only these:
C     Character
N     Numeric string
D     Date        (YYYYMMDD)
T     Time:            HHMMSS)
X     Byte (hexadecimal)
I      Integer
P     Packed number
F     Floating point number
STRING String         Variable empty string
If there isn't a dictionary field good for you, u can only use the type P.
So or:
DATA F4 TYPE MSEG-MENGE. (this field has 3 decimals)
or
DATA F4(16) TYPE P DECIMALS 2.
Max

Assigning a string value to a decimal data type field.

Hi,
I want to assign a value 'N/A' to an internal table field 'itab-field1' which is of data type dec.
How can I do this?.
Your help is really apprieciated
Thanks & Regards,
Soumya.

hi,
on what condition do u want N/A to be displayed, i hope when ever that field is empty...
so u can do in this way..in stead of changing in internal table...
when ever u r writing the values from internal table to output list..
ther put a check like if itab- field1 = 0.
                                  write :/ 'N/A'.
                              else.
                                 write : itab-field1.
hope this is helpful, because we can not pass char values to internaltable field of type dec..
Rgds.,
subash

Decimal data type package name oracle 9i

Dear Friends,
Can any one tell me , Package name of decimal datatype in oracle 9i.please........
Thank you

not clear
check to this
ANYDATA TYPE A self-describing data instance type containing an
instance of the type plus a description
ANYDATASET TYPE Contains a description of a given type plus a set of data
instances of that type
ANYTYPE TYPE Contains a type description of any persistent SQL type,
named or unnamed, including object types and
collection types; or, it can be used to construct new
transient type descriptions

Decimal data type with negative sign

Hi Gurus,
I wanted to created a z table with a filed of type decimal with sign. What I did is I created a field in predifined type with dec type, but -ve sign is not taking at the time of entering the data in SM30. Its saying only +ve values are allowed. Please let me know how can I achieve this. My data will be like -4.1242.
Thanks,
David.

Hi..
Try using another field as an indicator for negative fields so that you can consider those signs in your program.
Regards,
Karthik

How to give decimal data type in abap

hi
i m getting all the data from table
and doing calculation
i m using field TOTAL field for doing total
total = neter + kbetr
total = 150.50 + 120.20
here in my out put answer is coming like below
total = 270
but i want
total = 270.70
THANKS IN ADVANCE.

hi,
declare the field in this way ..
data : total type p decimals 2.

Data type for decimal value

I am making my own database table.which data type shuld I use to display decimal values.I used FLTP but its display is not very clear.
My values are like1234.56
Thanks

assign decimal place while creating domine.
as per ur req.....
if it is usefulll.Plz Reward
Regards
Anbu

Conversion of Packed Decimal Numbers to Java Data Types

Hi all,
I'm working with a mainframe file which contains datas in Packed Decimal Numbers.My requirement is to convert these datas to Java datatypes and also to convert the Java datatypes to Packed Decimal Numbers before storing them in the mainframe.
Can anyone help me out with any code for converting Java data types to/from other data formats such as: EBCDIC, IBM370 COMP (binary numbers up to 9 digits), and COMP-16 (packed decimal numbers)?
I would hugely appreciate any response to my query.
Thanking you all,
Kaushik.

Rather than go that route, I'd instead look into providing a "service" on your mainframe to:
1) provide a textual representation of the numbers (from native to text)
2) read text, converting to native numeric storage
And use that service to retrieve that information by your Java app (1)Similarly, instead of trying to write natively-formatted numbers from your Java app, I'd write it as text and make that same "service" read the text (2)
This is the kind of thing XML is for.

Wat should be data type for negative and decimal values (eg: -1.2222)

What should be data type for negative and decimal values (eg: -1.2222)

Hi
U can use the data type DEC while creating the DOMAIN and in the domain u have sign check box at the left corner of the screen, click that check box , u can assign negative values for the field which refers this domain.
REWARD IF HELPFULL
Anees.

SharePoint 2013 List - Multiple Data Types in the Same List

In the same SharePoint 2013 list in Data Sheet View, I want to have one column where my end users enter inputs for KPIs. There are 3 groups of KPIs (A, B and C) and they each have different data types (A-string, B-decimal, C-percentage) and I want to be
able to base their input options off of the KPI type
Does anyone have any suggestions on how I can leverage my parent-child relationships so when an end user...
1. Picks KPI type A, they can select from a choice filed (Green, Yellow, Red)
2. Picks KPI Type B, they can enter a decimal (-1.000 to 2.000)
3. Picks KPI Type C, they can enter a percentage (-100.00% to 100.00%
I'm using if I want to keep this in one list, one column and in data sheet view that the out of the box solutions won't meet my requirements. I was looking at some solutions from Bamboo (Lookup Selector Column) but don't think that applies here.
Thanks!
Johnny

Hi Johnny, you can accomplish this using cascading lookups in InfoPath if that program is available to you. Otherwise, if you want a 3rd party product, we use the Kwiz cascading lookup and it's worked wonders for us:
http://www.kwizcom.com/sharepoint-add-ons/sharepoint-cascading-lookup-plus/overview/
Note: I have no relationship with Kwiz, just vouching for the product.
cameron rautmann

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Problem in F data type

Hi experts...
I am using F data type and it gets value 5.50000000000E+10.
but I want value like 5.500.
I don't want to use P data type.
Please Help me.
thanks in advance.

Ankita,
Try declaring it as type quann and check.
Some additional info:-
Type F values range from /- 2.2250738585072014E-308 to 1.7976931348623157E308, as well as the number 0, with an accuracy of at least 15 decimal places.
You cannot enter floating point numbers directly in your programs. Instead, you must use text literals that can be interpreted as floating point numbers. You may use the following formats:
Decimal numbers with or without sign, with or without decimal point. The form <mantissa> E<exponent>, where the mantissa is a decimal. The exponent may be specified either with or without sign. You may also use spaces before or after the number. Examples of text literals with "floating point numbers":
'1', '-12.34567', '-765E-04', '1234E5', '12E34', '+12.3E-4', '1E160'.
Use floating point arithmetic if you need a very large value range or you are making decimal calculations, but be aware of the following features of floating point arithmetic.
Internally, the exponent and the mantissa of floating point numbers are stored separately, each in two parts. This can lead to unexpected results, despite the high degree of intrinsic accuracy. These occur mainly when performing conversions from and to type F.
For example, the number 1.5 can be represented exactly in this notation, since 1.5 = 120 + 12**(-1), but the number 0.15 can only be represented approximately by the number 0,14999999999999999. If you round 0.15 up to 1 valid digit, the result is 0.1 rather than 0.2 as you would expect. On the other hand, the number 1.5E-12 is represented by the number 1.5000000000000001E-12, which would be rounded to 2E-12.
Another example which actually occurred is the calculation of 7.27% of 73050 to an accuracy of 2 decimal places. The intermediate result 5.3107349999999997E+03, since the correct result, 5310.735, cannot be represented exactly in two parts with 53 bits. (If the hardware cannot represent a real number exactly, it uses the next representable floating point number. After rounding, you therefore get 5310.73 rather than 5310.74 as you would expect.
The ABAP runtime system calculates commercially and not "numerically" like the underlying machine arithmetic. According to the rounding algorithm of the latter, the end digit 5 must always be rounded to the nearest even number (not the next largest number), i.e. from 2.5 to 2, 3.5 to 4.
You should also note that multiplication using powers of 10 (positive or negative), is not an exact operation. For example, although 100.5 can be represented exactly in two parts, after the operation
F = F / 100 * 100
F has the value 100.49999999999999.
As well as rounding errors, the restricted number of decimal places for the mantissa can lead to the loss of trailing digits. For example, 1 - 1.0000000000000001 results in zero.
This means that you cannot rely on the last digits in floating point arithmetic. In particular, you should not usually test two floating point numbers for equality; instead, you should check whether the relative difference abs((a - b)/a) is less than a predefined limit, e.g. 10**(-7).
K.Kiran.

Liquid data type updates

Hi everyone,
With the next release (to go out on Monday) we're adding proper date format support in liquid for all modules. Besides all the improvements and additions made available with this release, one important note, which requires you to do some updates after the release, is that we're breaking backwards compatibility for liquid date tags by outputting the dates in ISO 8601 format ("yyyy-MM-ddTHH:mm:ss") instead of current format(“yyyy-MM-dd”).
Here is a brief overview of the changes:
All module fields which represent date or date times are now passed to Liquid as date time objects (previously they were passed as strings). This brings the following benefits:
Comparison between date time objects works correctly
It is possible to compute the difference between two date time objects using the minus filter. Example: {% assign dateDiff = Globals.Site.DateNow| minus: myDate %}
We added the means for obtaining the current date time: Globals.site.dateNow. The returned date is in the site’s time zone.
By default, when no filter is applied, all date variables will be output in the following ISO 8601 format: “yyyy-MM-ddTHH:mm:ss”. For example {{ myDate }} would output something similar to: “2014-12-12T07:19:49”. (Note: this is a backwards compatibility breaking change, as previously we outputted dates using the following format: “yyyy-MM-dd”. The breaking change only affects Liquid tags). Following the release, you should update your sites using the provided date filters to format the dates as you need.
The output of date time variables can be formatted using the following filters:
date (with no parameters)– displays a nice to read string representing just the date part from the date time variable. The date is formatted in the site’s culture. This compatible with the way older BC tags display dates. For example {{ myDate | date }}, in the English US culture will output a string similar to: “12-Dec-2014”.
datetime (new filter) – displays a nice to read string of the date time variable using the site’s culture. This compatible with the way older BC tags display date time. For example {{ myDate | datetime }}, in the English US culture will output a string similar to: “12-Dec-2014”.
date “format” (existing filter, nothing updated, mentioned here just for consistency) – displays the date in the site’s culture using a format specified by the format variable. The list with the available formats is available here: http://msdn.microsoft.com/en-us/library/8kb3ddd4%28v=vs.110%29.aspx. Note that the date filter can also be used to format objects that result as a difference between two date time objects, however, in this case the format string will respect a different set of rules as defined here: http://msdn.microsoft.com/en-us/library/ee372287%28v=vs.110%29.aspx. The following example demonstrates how to display just the number of days in the difference between two dates: {{ Globals.Site.DateNow| minus: myDate| date: "%d" }}
We added the Convert filter which can be used for converting variables to a certain type. The syntax is: variable | convert: “type”. Below are the values supported by the type parameter:
“date” – converts a variable to a date time instance. We only support the following formats for strings that are converted to date time: “yyyy-MM-ddTHH:mm:ss” and “yyyy-MM-dd”.
“number” – converts a variable to a number instance. If converting from string, only period “.” is supported as a decimal separator. This filter will probably be most useful when trying to convert GET query parameters: {% assign pageNumber = Globals.get.pageNumber | convert: “number” %}. The previous example assumes that URL that loaded the page contains a parameter named pageNumber. The convert numeric filter is an alternative to the rather hack-ish approach of converting to numbers using mathematical operators: {% assign myNumber = variable | plus: 0 }. Please note that it is not recommended to use the convert numeric filter just to assign numeric constants. For example, this approach is not recommended: {% assign myNumber = “3.14” | convert: “number” %}. Use the following approach instead: {% assign myNumber = 3.14 %} (note the lack of quotes around 3.14 in the second example).
“boolean” – converts a variable to a boolean instance. Please note, that just as it is the case with numerics, it is not recommended to use the “boolean” filter for declaring a boolean constant. For example this is not recommended: {% assign myBool = “false” | convert: “boolean” %}. Use the following syntax instead: {% assign myBool = false %}
“string” – converts a variable to its string representation.
We added implicit casting to the most relevant type in comparisons and inside filters representing mathematical operations (plus, minus, times, divide, modulo). With implicit casting, if one of the two operands is of type string and the other is of a different type (for example numeric or date time), we will attempt to convert the string operand to the type of the other. The conversion will fail if the string is not in an appropriate format for the type it is converted to (same rules as in the Convert filter are applied). In comparisons, if the implicit casting fails, the comparison is made with both operands converted to strings. Additional notes:
Implicit casting allows using date time literals directly in comparisons if the other operand is of date time type. For example, this will work correctly since "2015-01"15" will automatically be converted to date time before making the comparison: {% if myDate > "2015-01-15" %}Some message{% endif %}
Date parts obtained using the date filter can be used directly in comparisons with numerics. For example:
 {% assign daysDiff = Globals.Site.DateNow| minus: myDate| date: "%d" %}
 {% if daysDiff < 10 %}
 A message
 {% endif %}
With the implementation of implicit casting we also fixed some rather funny bugs related to comparisons and mathematical operations. For example, previously, 5 < 5.5 was evaluated as false, but 5.5 > 5 was evaluated as true. Also the result of 5| plus: 5.5 was 10, but the result of 5.5| plus: 5 was 10.5 (now 10.5 is the result of both operations, as expected).
As a potential caveat, note that implicit casting will bring the operands to the relevant type only if one of them is actually of that type. If both operands are of type string, the comparison is made as of between strings. This means that following condition is evaluated as false {% if "3" < "15" %}, because as a string "15" is smaller than "3".
Implicit casting from string to numeric only works if the string represents just a numeric. If the string contains additional characters, like a currency symbol, the conversion will fail. For example, this will not work correctly {% "$15" < 20 %}. Our goal, in the next releases, is to update all modules containing price related tags to have them in plain numeric format.
We added the following filters for easily formatting numeric values representing prices.
number - displays numbers with a fixed number of two decimals using the decimal separator appropriate to the site's culture. For example, in the English US culture, {{ 99| number }} will display 99.00
currency - displays numbers in the same way as number but also inserts the currency symbol at the beginning of the returned value. The currency symbol respects the site's culture. For example, in the English US culture, {{ 99| currency }} will display $99.00
In the next release or releases, we're going to focus on fixing the remaining data types for modules.
Cristinel

Liam, the server date isn't helpful for converting timezones. We would need a direct date filter. With a filter for UTC and one for the user we should be able to do quite a bit from there.
The most powerful things that could be implemented for date time are the following:
• moment.js and Moment Timezone built into the filters.
• the ability to add time info into date time fields
But I know that's a tall order.

Schema Data Type in SOAP Web Service while using Integration Gateway in SMP 3.0

Hi Experts,
I was working on Integration gateway component of SMP 3.0.3 where we can have oData services which connect to different data source from SMP and finally we have to consume from SMP. Here I have an SOAP Web service where there is Schema Data type which is an xml structure and because of that while doing the data modelling with Design time tools I am not able to map the properties as there aren't any as only the parent level Schema type is available in the SOAP Web Services. Please see the below image for reference :
So now I have 2 inputs no problems for design as such then I have the schema for that which comes as a output response which is where I am facing the issue as we don't have that Data Structure itself so how are we going to map that. I have seen some thin possibilities with Custom Scripts with SMP SP06 where this will help us to process the request and response at runtime with JS/Groovy. So needed some lights on this schema data type on Integration Gateway component of SMP 3.0.3 which we are planning to upgrade to SP06 as well so it will be a good starting point for this as well
Also have concerned my good friend Rakshit Doshi for this as well.
Regards,
Fenil.

Hi All,
Sorry for the late response guys was stuck somewhere else and so couldn't reply to this, see I have below response in SOAP UI
There if we see we have the schema as the whole structure being defined under which we have all the child elements, am also posting the raw response from the soapUI below for better understanding
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <soap:Body>
 <GetMSUserLoginDetailsResponse xmlns="http://tempuri.org/">
 <GetMSUserLoginDetailsResult>
 <xs:schema id="MemberDetails" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
 <xs:element name="MemberDetails" msdata:IsDataSet="true" msdata:UseCurrentLocale="true">
 <xs:complexType>
 <xs:choice minOccurs="0" maxOccurs="unbounded">
 <xs:element name="Table">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="RECID" type="xs:string" minOccurs="0"/>
 <xs:element name="FNAME" type="xs:string" minOccurs="0"/>
 <xs:element name="LNAME" type="xs:string" minOccurs="0"/>
 <xs:element name="CUSTNO" type="xs:decimal" minOccurs="0"/>
 <xs:element name="MEMTYP" type="xs:decimal" minOccurs="0"/>
 <xs:element name="MEMTYPENAME" type="xs:string" minOccurs="0"/>
 <xs:element name="CUSTTYP" type="xs:decimal" minOccurs="0"/>
 <xs:element name="EMAIL" type="xs:string" minOccurs="0"/>
 <xs:element name="MEMPASSWORD" type="xs:string" minOccurs="0"/>
 <xs:element name="ISDEBIT" type="xs:decimal" minOccurs="0"/>
 <xs:element name="PARENTID" type="xs:string" minOccurs="0"/>
 <xs:element name="CHILDOF" type="xs:string" minOccurs="0"/>
 <xs:element name="CUSTTYP1" type="xs:string" minOccurs="0"/>
 <xs:element name="ZONEID" type="xs:int" minOccurs="0"/>
 <xs:element name="EMAILFOOTERDETAIL" type="xs:string" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="Table1">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="ErrorCode" type="xs:string" minOccurs="0"/>
 <xs:element name="ErrorDesc" type="xs:string" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:choice>
 </xs:complexType>
 </xs:element>
 </xs:schema>
 <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
 <MemberDetails xmlns="">
 <Table diffgr:id="Table1" msdata:rowOrder="0">
 <RECID>97101-101-0000057069</RECID>
 <FNAME>Fenil</FNAME>
 <LNAME>Doshi</LNAME>
 <CUSTNO>1042231</CUSTNO>
 <MEMTYP>42</MEMTYP>
 <MEMTYPENAME>Management</MEMTYPENAME>
 <CUSTTYP>8</CUSTTYP>
 <EMAIL>[email protected]</EMAIL>
 <MEMPASSWORD>as</MEMPASSWORD>
 <PARENTID>97101-101-0000057069</PARENTID>
 <CUSTTYP1>Zone</CUSTTYP1>
 <ZONEID>2</ZONEID>
 <EMAILFOOTERDETAIL><![CDATA[ ]]></EMAILFOOTERDETAIL>
 </Table>
 <Table1 diffgr:id="Table11" msdata:rowOrder="0">
 <ErrorCode>100</ErrorCode>
 <ErrorDesc>Login Successful.</ErrorDesc>
 </Table1>
 </MemberDetails>
 </diffgr:diffgram>
 </GetMSUserLoginDetailsResult>
 </GetMSUserLoginDetailsResponse>
 </soap:Body>
</soap:Envelope>
So we have the data but as a xml Structure which is nothing but schema and is my Eclipse while mapping while defining response type it gives me just an schema as the property.
Regards,
Fenil.

Decimal data type

Similar Messages

Maybe you are looking for