XI settings, change of Data Types and XI still maps old structures

Hi,
I have defined XI scenario, where synchronous WebService is being called, and XI calls RFC function module, which returns data. It was working perfectly, until
I have changed the order of few fields in Data Type and added a few new (exactly as the changes in RFC function module).
And now the WebService returns exception, on the first field added to the interface:
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:MT_BMS_Response/CUSTOMERS_PERSON/TITLE. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at
TITLE is added field.
I have reactivated everything one by one again, clear cache from Integration Builder and Integration Directory, but it does not help and still old structures are being used in XI.
I have tested the Interface Mapping and all fields are transformed correctly.
Please help as it comes a little urgent and I have run out of ideas what to do to refresh the customizing of data types?
Thank you in advance!

Hi Peter,
Yes, I am calling RFC function module from XI.
After I changed the interface of RFC in SAP, I have imported this RFC once more to XI in Integration Builder and new structures appeared.
And exception returned is that first new field added to the RFC and Data Type and so on, returns an exception.
And returned XML structures (in message monitoring) appears to be still old structures.

Similar Messages

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

Can we change the data type of a field based on the value of the field

HI Gurus,
My Requirement is as below -- Could you please guide me
in the Printable Adobe form -- for ex - as usual for dates fields in the Object Pallette the object type is a date/time field and for quantity/currency fields corresponding fields are taken
now in case the either the date, quantity or currency is initial in place of displaying 0.00 or empty date we need to display N/A (Not Applicable)
for this I would like to change the data type of the field
to put it simply --
we need to change the data type of date field from DATE&TIME to Char type to hold N/A or Quantity field to Char field to hold N/A
how can we realize this in SAP adobe forms
Thanks in Advace
Ramchander Rao.K

Hello Ramchander,
     You cannot change the data type of the field at run time in Adobe forms because the type of field you choose at the time of design level is associated with the data type itself.
If you want to achieve your requirement, then your main idea should be to set the data type as CHARACTER itself while designing the field in the adobe form itself. CHAR field will comfortably hold the value of Calculation/amount field, Currency field, Amount, Date, Time HHMMSS, Unit Accuracy, Currency key, Floating point number, Numeric text, Client, Language and many other data types.
After designing the field as TEXT field in Adobe form you have two options.
Option 1:
Select the Date field initially as type TEXT field or CHAR field in Adobe forms.
Suppose the name of the field is TEXTFIELD1, then write the Javascript code on this field in Initialize event as below.
if ( this.rawvalue == null )
     this.rawvalue = "N/A";
If the field is not blank, then it will show the date. Else it will show "N/A".
Option 2:
Select the Date field initially as type TEXT field or CHAR field in Adobe forms. Do the formatting part in ABAP itself. It will increase the performance. Avoid Javascript as much as possible.
Suppose you have a DATE variable l_dats of type DATS. Then take another variable l_date of type CHAR. Then write the below ABAP code.
MOVE l_dats TO l_date.
IF l_date IS INITIAL.
     l_date = 'N/A'.
ENDIF.
Bind the l_date to the TEXT field in the form.
Even in this case, if the field is not blank, then it will show the date. Else it will show "N/A".
But I will suggest you to use Option 2 of keeping the AMOUNT, QUANTITY, DATE, TIME fields etc as CHAR or TEXT fields in Adobe form and do the required formatting in ABAP itself.

How to Change the data type of infoobject from NUMC to CHAR

Hi Experts,
I have created an infoobject with data type as NUMC, i used in DSO as a key figure and i have loaded data up to PSA.
Now i want to change the data type of this Info Object from NUMC to CHAR.
Can anyone suggest me the solution for this issue.
Regards,
Venu Gopal.K

Hi pavan/binu,
I have not loaded data into DSO i just added IO in Key fields and i started editing this IO then im facing error like
1.Master Data Table /BIC/PZCUSTOMER contains data: Characteristic ZCUSTOMER cannot be activated
2.SID Table /BIC/SZCUSTOMER contains data: Characteristic ZCUSTOMER cannot be activated
Im also unable to edit the P & S tables in SE14.
NOTE:I have data only in PSA and when im trying to load data to DSO Im facing these issues.

Change the Data Type of a Standard Required Field

Hello Experts,
Need to know if is it possible to change the data type of a standard field. The field is marked as a required field.
For example: If a standard field is an Object Picker and I would like to change it to a string field. Is it possible? How can I do it?!
Many thanks,
Igor Nakamura

Hi Igor,
Since you cannot hide a required field, what you can do is move the standard required field to someplace less noticable (like the bottom of the page) and then use a validation script to set it to some benign value.
-Howie

Activation error while changing the data type of a field of a table

hi friends,
i am facing one problem while changing a data type of a field of a table.
i just created one table(Yqm32) .i have assigned charcter data type to one field(ztotal_count) .now i want to change this charcter data type to numeric data type.
while changing to NUMC data type activation error is comming as below.
Table is not yet classified
Field ZTOTAL_COUNT: Type change
ALTER TABLE is not possible
Structure change at field level (convert table YQM32)
Check on table YQM32 resulted in errors
Table YQM32 could not be activated
(E- Structure change at field level (convert table YQM32)
plz suggest.i need to change the data type from char to numc.
Thanks & Regards

Hi Pabitra......
From the SE11 change the table as u wanted and then from menubar select
UTILITIES--> DATABASE UTILITY
It will open database utility
there u select the Activate and adjust database button.
then the database table will get adjusted.
just try it once.........
Suresh......

Change Cluster Data Type

I might be asking a really silly school boy question here and to some degree I hope I am but could somebody tell me if its possible to change the data type of a cluster element? Let me explain.
Here is a screen shot of my code:
I read back my test data as an array of strings which I convert to a cluster, bundle then send off on its merry way to do other stuff, however the first element in the cluster is actually a path. As you can see I currently unbundle all elements, change the first to a path then re-bundle with the correct data types. Whilst somewhat messy, this used to be acceptable as I only had two other strings in the cluster, however due to expansion I now look at it and think that there must be an easier, more elegant way to do this if I just want to change one element.
If this is the only way (or at least if no other simpler solution exists) then I could potentially keep the path a a string and do the conversion at the points that require it, however that would now require a bit of re-coding which I would like to avoid if possible.
Hopefully I'm just not thinking hard enough on this one.
Cheers for looking
Mitch
Solved!
Go to Solution.

I have no idea what the rest of the code looks like and how much you can change so a few options:
1. Keep them all as strings, do the path conversion when you actually need the path. I'll show you the trick I use to convert arrays to nicely labelled clusters below.
2. Make the cluster an object, keep the data as a string array and the accessors deal with indexing and path conversion.
3. Make the cluster hierarchial, separate the path and have a second cluster which is all strings.
4. If you want you can jigger the string array and use some flatten and unflatten action.
The top of the snippet is one way to jigger the string array to get a path for the first element in a flat cluster (should wire seamlessly to the rest of your code). The lower code shows how I would convert a string array to a cluster so the labels are useful, same idea works for clusters which are given useless labels such as those from Array to Cluster. (Fixed sized clusters with brown wires are easier to handle, simply Type Cast to the cluster with the same types and appropriate labels).
Judging from your original post, you know when and how to Type Def the various clusters I show.

My typewriter toolbar is graying out the ability to change font size, type, and color.

My typewriter toolbar is graying out the ability to change font size, type, and color.

Here's what I have done in the past. Maybe not elegant, but
it works. (I
use PHP, but I'm sure you can modify for ASP.)
In the HEAD of each web page, include regular old embedded
STYLE tags,
but INCLUDE an external PHP file:
<head>
<style type="text/css">
<?php include('styles/testcss.php'); ?>
</style>
</head>
Now in that included PHP file, just have CSS code which pulls
in your
dynamic data. Here's an example snippet:
body {
color: #600;
background-color: <?php echo
$row_recordset['bgcolor'];?>
Of course, you'll need the code for the recordset somewhere
too.
Alec
Adobe Community Expert

Data types and data objects

diff b/w data types and data objects

hi prasanth,
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
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
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
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
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.
regards,
sravanthi

How to use same Data Type and Length for two fields

How to use same data type and length for two fields when using 'FOR ALL ENTRIES IN' in a select statement? For instance the select queries are :
SELECT bukrs gjahr belnr lifnr budat bldat zlspr dmbtr waers shkzg
FROM bsik
INTO TABLE it_bsik
WHERE bukrs = p_bukrs
AND lifnr IN s_lifnr.
IF it_bsik IS NOT INITIAL.
SELECT belnr gjahr awkey awtyp
FROM bkpf
INTO TABLE it_bkpf
FOR ALL ENTRIES IN it_bsik
WHERE belnr = it_bsik-belnr
AND gjahr = it_bsik-gjahr.
IF it_bkpf IS NOT INITIAL.
SELECT belnr gjahr lifnr xblnr
FROM rbkp
INTO TABLE it_rbkp
FOR ALL ENTRIES IN it_bkpf
WHERE belnr = it_bkpf-awkey+0(10)
AND gjahr = it_bkpf-awkey+10(4).
ENDIF.
ENDIF.
Here it gives an error in the 3rd select query that 'When you use the addition "FOR ALL ENTRIES IN itab", the fields "GJAHR" and "IT_BKPF2-AWKEY+10(4)" must have the same type and the same length.'
Kindly clarify.

Hi Saurabh,
Please see the example code that I have developed for you. It will help you solve the problem.
REPORT ZTEST_3 .
tables : BKPF.
data : begin of it_bkpf occurs 1,
         belnr type RE_BELNR,
         awkey type awkey,
         awtyp type awtyp,
         gjahr type GJAHR,
       end of it_bkpf.
data : begin of it_bkpf1 occurs 1,
         belnr type RE_BELNR,
         awkey type gjahr,              " change the data type
         awtyp type awtyp,
         gjahr type GJAHR,
       end of it_bkpf1.
data : begin of it_rbkp occurs 1,
         belnr type BELNR_D,
         gjahr type gjahr,
         lifnr type LIFRE,
         xblnr type XBLNR,
       end of it_rbkp.
select belnr
       awkey
       awtyp
       gjahr
       from bkpf
       into table it_bkpf
       where BUKRS = 'TELH'.
loop at it_bkpf.
it_bkpf1-belnr = it_bkpf-belnr.
it_bkpf1-awkey = it_bkpf-awkey+10(4).           "Here only append the required length.
it_bkpf1-awtyp = it_bkpf-awtyp.
it_bkpf1-gjahr = it_bkpf-gjahr.
append it_bkpf1.
clear it_bkpf1.
endloop.
select belnr
        gjahr
        lifnr
        xblnr
        from RBKP
        into table it_rbkp
        for all entries in it_bkpf1
        where belnr = it_bkpf1-belnr
This is just an example. Change the fields according to your requirement.
Regards
Abhii
Edited by: Abhii on Mar 9, 2011 9:08 AM

Info Object: Change of Data Type (NUMC to CHAR)

We have a scenario wherein one of the Info objects is defined currently as NUMC. Due to the change in the Source system, the info object is now defined with data type as CHAR. The info object in consideration is the "Cost element".
As the current info object contains data, it will not be possible to change the data type from NUM to CHAR.
Is there any pre-defined way of doing this data type change without loss of data (in the info object as well as the info cube(s) where the info object is used)?
Regards
Bala

Hi Balakrishana,
Try this:
Insted of changing the definition of infoobject(NUMC to CHAR), why cant you change the data itself from CHAR to NUMC...?? If length is same.
You can write a simple routine in transfer rules and you can convert.
Hope it Helps
Srini

Can't change column data type

Hi, i am using Sybase IQ 16.0
I have created a table, when I want to change one of the data type for a column for example from char to varchar, the list box is grey color and not allow me to change.
Right click table > Properties > Columns > Data Type
I have granted all permission for dba, but still not able to edit. (please see the attached file)
Any help?
Thanks.

Hi Nelson.
You can not change the datatype of an existing column.
The doc reference is here: Altering Tables
"After you create a column, you cannot modify the column data type. To change a data type, drop the column and recreate it with the correct data type."
If you already have data in the column, you can try this:
create the new column with a slightly different name
copy the data in to the new column
drop the original column
rename the new column to the old column's name.
--Kirby

Changing Chart Data Types

Hi,
I know this is a stupid question, but I can't figure for the life of me
how to do it. I want to create a histogram, so I stick a waveform chart
onto my VI. Fine, now I found the Moving Histogram PtByPt.vi example
(ships with LabView 7). It creates a histogram and the data it sends to
it is a cluster. This is very convenient because you just wrap your XY
data up into a cluster and send it into the chart. Right now I can cut
and paste the chart from this example, but if I didn't have the example
I'd create a waveform chat, create my cluster with my xy data and pass
it in. However, LabView complains about bad data types, because the
default input data type is a 2D array of doubles. HOW DO I CHANGE THE
DATA TYPE THE CHART ACCEPTS? I've been through every menu and property
that I can think of, what's the secret? I've had this problem happen a
couple of times and usually gotten around it by right clicking my lead
and then picking to create something from a list and when it's created
it's created with the right data type. However, it doesn't have that
option in this situation. So what do I do? I've included a junk of my
code for you to see if you want.
Thanks for any help,
Chris
Attachments:
Coincidence_v1.vi ‏53 KB

You've got two different types of graphs. You have the XY graph wired to the cluster and you have a regular (not XY) graph. The regular graph does not accept the same type of input as the XY graph. It accepts a 1D x array, 2D array (multichannel) a waveform data type, an array of waveforms (multichannels), and a cluster that contists of a y array, x0, and dx (essentially a waveform data type)

The output of my mathscript node is not changing the data type ?

hi
iam attaching my .vi iam having problem that my math script function is not changing it data type in its output
iam uisng labview 2009
what reason it will be?/
thanks
Attachments:
mathfunct.zip ‏4 KB

First off, there is a dedicated mathscript forum that might be better to get your problems answered. (I see if I can have this thread moved from the LabVIEW board, else you can re-post over there.)
I see the same problem that (1) the outputs have no datatype and (2) all datatypes are greyed out, so they cannot be selected manually. (The input is trivial, just wire something and it will adapt).
I am not a text programmer, but I suspect that there is something wrong or incompatible with your code. I have not looked at the statements. Is this copied from an existing matlab program, for example?
LabVIEW Champion . Do more with less code and in less time .

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) 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.
5) 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).
6) 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).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

XI settings, change of Data Types and XI still maps old structures

Similar Messages

Maybe you are looking for