Conversion of a data object of type "C" to type "l" is not supported

Experts:
i have below code in my FM; defined as remote-enabled module.
when i execute i get the error analysis as:
You attempted to move one data object to another.
This is not possible here because the conversion of a data object
of type "C" to type "l" is not supported.
This at the line move <FS2> TO <wwa_mdm_name_value_pair>-VALUE .
what are the steps to debug this? Thanks!
DATA: tt_mdm_name_value_pair_table TYPE mdm_name_value_pair_table.
FIELD-SYMBOLS : <wwa_mdm_name_value_pair> LIKE LINE OF tt_mdm_name_value_pair_table.
FIELD-SYMBOLS <FS1> TYPE ANY.
FIELD-SYMBOLS <FS2> TYPE any.
data:st_mdm_name_value_pair type mdm_name_value_pair.
assign st_mdm_name_value_pair to <wwa_mdm_name_value_pair>.
assign st_mdm_name_value_pair-code to <FS1>.
assign st_mdm_name_value_pair-value to <FS2>.
clear wa_ZSTRESULT.
loop at T_UPDATE into wa_ZSTRESULT.
 assign wa_ZSTRESULT-field to <FS1>.
 <wwa_mdm_name_value_pair>-CODE = <FS1>.
 assign wa_ZSTRESULT-VALUE to <FS2>.
 move <FS2> TO <wwa_mdm_name_value_pair>-VALUE .
 append <wwa_mdm_name_value_pair> to tt_mdm_name_value_pair_table.
endloop.

resolved using GET REFERENCE.. code looks as below: Thanks!
DATA: tt_mdm_name_value_pair_table TYPE mdm_name_value_pair_table.
FIELD-SYMBOLS : <wwa_mdm_name_value_pair> TYPE LINE OF mdm_name_value_pair_table.
FIELD-SYMBOLS <FS1> TYPE ANY.
FIELD-SYMBOLS <FS2> TYPE DATA.
TYPES t_dref TYPE REF TO DATA.
DATA dref TYPE REF TO DATA.
DATA: TT_UPDATE TYPE ZTYRESULT.
FIELD-SYMBOLS : <WA_UPDATE> LIKE LINE OF TT_UPDATE.
data: st_mdm_name_value_pair type mdm_name_value_pair.
assign st_mdm_name_value_pair to <wwa_mdm_name_value_pair>.
assign st_mdm_name_value_pair-code to <FS1>.
assign st_mdm_name_value_pair-value to <FS2>.
clear wa_ZSTRESULT.
TT_UPDATE = T_UPDATE.
loop at TT_UPDATE assigning <WA_UPDATE>.
 assign <WA_UPDATE>-FIELD to <FS1>.
 <wwa_mdm_name_value_pair>-CODE = <FS1>.
 assign <WA_UPDATE>-VALUE to <FS2>.
 GET REFERENCE OF <WA_UPDATE>-VALUE INTO dref.
* MOVE dref TO <wwa_mdm_name_value_pair>-VALUE.
 <wwa_mdm_name_value_pair>-VALUE = dref.
 append <wwa_mdm_name_value_pair> to tt_mdm_name_value_pair_table.
endloop.

Similar Messages

System.Data.SqlClient.SqlException: The locale identifier (LCID) 16393 is not supported by SQL Server

I have SQL Server 2005 Developer Edition. And my operating system is Windows Vista.
I have written a procedure in C# and deployed it on SQL Server. However when i try to run it i get the following error.
System.Data.SqlClient.SqlException: The locale identifier (LCID) 16393 is not supported by SQL Server
Also I tried using same procedure in Windows XP machine and it workd fine. Can anyone help me what could be the problem?

Hi Jonathan
I tried posting the error box here but it is not allowing me.
Here is the error coming up:
A .NET framework error occured during execution of user-defined routine or aggregate.
System.Data.SqlClient.Sqlexception:The locale identifier (LCID)1153 is not supported by SQL Server.
System.Data.SqlClient.Sqlexception:atSystem.Data.SqlClient.SqlConnection.OnError(SqlExceptionexception, Boolean breakConnection) atSystem.Data.SqlClient.SqlInternalConnection.OnError(SqlExceptionexception, BoleanbreakConnection) atSystem.data.SqlCleitn.SqlInternalConnectionSmi.EventSink.ProcessMessagesandThrow(Boolean ignoreNonFatalMessages) atMicrosoft.SqlServer.Server.SmiEventSink_Default.ProcessMessagesandThrow(Boolean ignoreNonFatalMessages) atSystem.Data.SqlClient.SqlCommand.RunExecuteNonQuerySmi.(BooleansendTo Pipe) atSystem.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResultresult,StringmethodName,BooleansendToPipe)
atSystem.Data.SqlClient.SqlCommand.ExecuteNonQuery()
I hope this will shed some light.
Cheers

DPM console not connecting . Error- Cannot connect to Data Protection Manager. This version of DPM is not supported with Central Console Client (ID : 33345) DPM console not connecting

I am having problem connecting the DPM console to ther server. It gives me following error -
"Cannot connect to Data Protection Manager. This version of DPM is not supported with Central Console Client (ID : 33345)"
The server is DPM R2 and the same console is working on one other computer.
Any idea how to solve the problem?
Thanks

Hi
Please make sure you have both versions of Microsoft Visual C++ 2008 Redistributable installed..
Also make sure you have .netframework 2 installed. If you look at the dpm logs it should say what is missing.

Master Data loading got failed: error "Update mode R is not supported by th

Hello Experts,
I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
"Update mode R is not supported by the extraction API"
Can anyone tell me what is that error for? how to resolve this issue?
Regards,
Nirav

Hi
Update mode R error will come in the below case
You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
This time the load will fail with update mode R.
As repeat delta is not supported.
So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
example your fiorst delta failed with replication issue.
only replicating and repeaing will not solve the update mode R.
you will have to do both replication of the data source and re-int for the update mode R.
One more thing I would like to add is.
If the the delat which failed with error the first time(not update mode R), then
you have to do init with data transfer
if it failed without picking any records,
then do init without data transfer.
Hope this helps
Regards
Shilpa
Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.

Hello all,
I have SQL express 2014 advance edition installed ..
and i am connecting SQl server 2008 r2 instance which is in network
while creating datasource in Reportserver which has Express installed ..
got this error ..
please help me how to connect to remote server
Dilip Patil..

Error message says it all.
With SQL Express, Data source should be local SQL DB.
With SQL Enterprise, Standard, BI edition, you can create Data soruce which are hosted on other servers.
Please refer similar thread:
https://social.msdn.microsoft.com/Forums/en-US/c0468e3f-bad7-47a7-a695-75c13762280a/the-feature-the-edition-of-reporting-services-that-you-are-using-requires-that-you-use-local-sql?forum=sqlreportingservices
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]

Types that clientgen 7.0b does not support

clientgen 7.0b has problems with simpleTypes like restriction, list and enumeration
that manifest themself when clientgen throws an exception and fails ant build
script. The workaround for those types of problems is to change WSDL to use simpleTypes
like string instead of lists, restrictions, etc.
However there is another situation when clientgen have a huge problem and unlike
scenario described above this situation is not noticeable till runtime. Generally
clientgen cannot properly
handle types like the following (reffer to attached WSDL for more examples)
<s:element name="CustomerInfoFindHeader" type="s0:CustomerInfoFindHeader" />
<s:complexType name="CustomerInfoFindHeader">
<s:complexContent mixed="false">
<s:extension base="s0:CustomerInfoHeader" />
</s:complexContent>
</s:complexType>
For the CustomerInfoFindHeader type above clientgen generate service methods that
instead of using CustomerInfoHeader interface uses javax.xml.soap.SOAPElement.
During runtime that result in
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ UNIMP ]
 at weblogic.webservice.core.encoding.stream.JavaSoapElementSerializer.serialize(JavaSoapElementSerializer.java:34)
 at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:215)
 at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:265)
 at weblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation.java:259)
 at weblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation.java:246)
 at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:141)
 at mappoint.findservice.FindServiceSoap.FindAddress(FindServiceSoap.java:57)
The workaround for that AssertionError is to once again modify the WSDL not to
have complex types with extensions.
Hopefully those problems will get fixed in future versions of clientgen. hint
Aleksey
[Copy of findservice.wsdl]

Thanks for the detailed posting.
We use javax.xml.soap.SOAPElement when we encounter
a schema that we do not understand and i guess there was
a bug in beta which caused ser/deser of soap element to
fail.
regards,
-manoj
"Aleksey" <[email protected]> wrote in message
news:[email protected]...
>
clientgen 7.0b has problems with simpleTypes like restriction, list andenumeration
that manifest themself when clientgen throws an exception and fails antbuild
script. The workaround for those types of problems is to change WSDL touse simpleTypes
like string instead of lists, restrictions, etc.
However there is another situation when clientgen have a huge problem andunlike
scenario described above this situation is not noticeable till runtime.Generally
clientgen cannot properly
handle types like the following (reffer to attached WSDL for moreexamples)
>
<s:element name="CustomerInfoFindHeader" type="s0:CustomerInfoFindHeader"/>
<s:complexType name="CustomerInfoFindHeader">
<s:complexContent mixed="false">
<s:extension base="s0:CustomerInfoHeader" />
</s:complexContent>
</s:complexType>
For the CustomerInfoFindHeader type above clientgen generate servicemethods that
instead of using CustomerInfoHeader interface usesjavax.xml.soap.SOAPElement.
During runtime that result in
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ UNIMP ]
atweblogic.webservice.core.encoding.stream.JavaSoapElementSerializer.serialize
(JavaSoapElementSerializer.java:34)
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:215)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:265)
atweblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation
.java:259)
atweblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation
.java:246)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:141)
atmappoint.findservice.FindServiceSoap.FindAddress(FindServiceSoap.java:57)
>
The workaround for that AssertionError is to once again modify the WSDLnot to
have complex types with extensions.
Hopefully those problems will get fixed in future versions of clientgen.
hint
>
Aleksey

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

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

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and 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 an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data object as well as the name of a data type.
Data Types:
 As well as occurring as attributes of a data object, data types can also be defined independently. 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 TYPES statement) 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.
 Data types can be divided into elementary, reference, and complex types
Data objects:
 Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their 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.
ABAP contains the following kinds of data objects
Literals
 Named Data Objects
Predefined Data Objects
Dynamic Data Objects

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

Differences between DATA TYPE and DATA OBJECTS

I am new to ABAP,I want to know the differences between DATA TYPE and DATA OBJECTS with some examples.
please help me regarding this.

Hi Ashish,
Data Types:       Are pure descriptions.
               No memory is associated with data types.
               Describes the technical properties of data objects.
EX.
1.     C-CHARACTER
2.     D-DATE
3.     F-FLOAT
4.     I-INTEGER
5.     N-NUMERIC TEXT
6.     T-TIME
7.     P-PACKED NUMBER
8.     X-HEXADECIMAL
9.     STRING-Variable length string.
10.     XSTRING-Variable length byte string.
Data Objects: Are created during runtime.
                They cannot exist without the data Types.
                Occupies memory space.
EX:
1.     INTERNAL DATA OBJECT- Internal Data objects
     LITEERAL- A literal has a fixed value.Ex: WRITE:u201DWORK HARDu201D.
     VARIABLES: Data statement is used to create variables.
EX.DATA: NUM TYPE I.
NUM: VARIABLE defined by data statement.
EX: DATA: PRICE LIKE NUM.
     CONSTANT-It is a data object, which contains a constant value throughout the program.
Can be declared in program by using CONSTANT statement.
EX:CONSTANT: INT TYPE I VALUE 15.
2.     EXTERNAL DATA OBJECT: Are defined in tables i.e In ABAP/4 dictionary you can access this data from table.
         EX: TABLES: SFLIGHT
          DATA: SEATS LIKE SFLIGHT-SEATSMAX.
3.     SYSTEM DEFINED DATA OBJECTS:Space & system variables like SY-UNAME,SY-DATUM, SY-REPID.
4.     SPECIAL DATA OBJECTS:
     PARAMETERS: Are Variables ,which can accept value from user.
      SELECTION SCREEN : Are special internal tables to accept value ranges from user.
3 APPROACHES TO DEFINE DATA OBJECTS.
1.     ELEMENTARY TYPES
DATA: Customer _Name (25) TYPE C,
               Vendor_Name (25) TYPE C.
2.     REFRENCE TO AN EXISTING FIELD:
DATA: Customer _Name2 (25) TYPE C,
              Vendor_Name2 (25) LIKE Customer_Name2
3.     REFRENCE TO NON-ELEMENTARY TYPE:
TYPES: T_NAME (25) TYPE C
DATA: CUSTOMER_NAME TYPE T_NAME
               VENDOR_NAME TYPE T_NAME
4.     RECORD-Information in rows & columns.
DATA: BEGIN OF BOOKING,
                                ID (4) TYPE C,
                                FLIGHT_DATE TYPE D,
                                NAME LIKE CUSTOMER_NAME,
                                END OF BOOKING.
You can also look into SAP help for more information.
Regards,
Indu.

Drop Indexes from Data Object in DOE

Hi,
I have created the index for data object by using Mobile Appli Attrib tab in DOE workbench. But now I need to remove it. Everytime I remove checkbox and index name and save it. Now I open the data object again index will be there,it will not be removed.
Thanks & Regards,
Manisha Dabour.

Hi Monisha,
I tried the same in 710 SP11 system and I could delete the index name and uncheck check boxes.
Below are the steps I did.
-- Selected the root node of a DO.
-- Clicked on "Mobile Appln Attribute.
-- Chose client type in the popup as "JAVACLNT" .
-- Checked few fields and entered a index name.
-- Saved the changes.
-- repeated the above and uncheckd fields/removed index and did some changes.
Observed that everytime my latest changes were captured.
Can you please open a OSS message for the same.
Regards
Rohith

Converting Date.toString() back to a Date object for compare

I know this is beating a dead horse to death but I have wasted a whole day trying to get this to work. Here is the problem.
I need to convert a Date().toString (format returned: Dec 19, 2006 3:39:58 PM EST) back to a Date object. What I am doing is writting this string a text file and then revisiting it to compare later to a current Date object to find the difference in the two stamps in milliseconds.
J2SE 1.4.2 being used
Date date = new Date();
String newDateStr = log[1].trim(); // entry from log file
SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss");
Date logDate = dateFormat.parse(newDateStr);
// get difference between the two
long timeSpan = date.getTime() - logDate.getTime();
if(timeSpan > 60000){
// TO DO
}So should I look at a different approach at either:
A) Storing the date/time stamp in the text file
B) The conversion back to Date object is wrong
Really appreciate any insight on this.
Thanks
JLW
Message was edited by:
jlwestsr

Then my friend you are in the same status as Tim.:o)
I don't know as much as him and I don't care to write
an elaborate reply most of the time. :D
Merry ChristmasSame to you.I don't pretend to know that much, but When I see something I do know, I tend to give examples.
Most probably that is because at the present time I am in a situation where most of my time is spent waiting for a call from the customer, and the app I am supporting works so well that those calls are few and far between. Lucky for me, they pay me for sitting around and answering questions on a forum.
At least it is a java forum, where I can justly claim that I am improving my knowledge of java.
~Tim

Data object is not being populated in BAM

We are putting the data in JMS Queue. We have created an EMS in BAM. It is picking the data from JMS Queue, but the data object is not being populated. The request we are using here is given below:
Request:
<?xml version="1.0" encoding="UTF-8"?>
<Test xmlns="http://education.com/OrderImport">
<OrderLineReferenceNumber>abcad</OrderLineReferenceNumber>
<WebOrderNumber>cccccg</WebOrderNumber>
<OrderLineCount>gn</OrderLineCount>
<LineNumber>4</LineNumber>
<ISBN10>46564574</ISBN10>
<ISBM13>6767</ISBM13>
<ID>67</ID>
<Status>78768</Status>
</Test>
Does anybody has any idea on that?
Regards,
Chandrachur.

Hi Arun,
Thanks for your prompt reply.
We are not using any trasfomation here. We have created thje Data objects as per the message type in the request.
Please find the dataobjects details we are using:
Field name Field ID Field type Max length Scale Nullable Public Lookup Calculated Tip Text
OrderLineReferenceNumber _OrderLineReferenceNumber string 100 - No Yes - - -
WebOrderNumber _WebOrderNumber string 100 - Yes Yes - - -
OrderLineCount _OrderLineCount integer - - Yes Yes - - -
LineNumber _LineNumber integer - - Yes Yes - - -
ISBN10 _ISBN10 string 100 - Yes Yes - - -
ISBM13 _ISBM13 string 100 - Yes Yes - - -
ID _ID string 100 - Yes Yes - - -
Status _Status string 100 - Yes Yes - - -
Thanks again,
Chandrachur.

BRFplus: Adding Intermediate Data Objects to Expression Workarea

Hi all,
running BRFplus on NW 70105.
I have a Step Sequence Expression with multiple steps calling various Functions. Some of the Functions return intermediate results which must be stored in the context workarea.
I would like to add these Data Objects to the workarea. However the system will not allow me to do this without first adding the Data Objects as signature parameters of the calling Function, even though this does not make sense for intermediate values.
Clicking the "Add existing Data Object" button for the workarea only allows me to add Data Objects which are in the context of the calling Function.
Conversely if a Data Object is deleted from the calling Function's signature, then when checked the Function issues error message "Assigned expression uses Element CUSTOMER/Customer which is not in the context".
Is the requirement to add all Expression workarea Data Objects to the calling Function's signature intended, or is this a bug ? Or is there some other way of doing it that I am missing ??
Thanks & regards,
Grogan

This is a restriction in NW 701. This restriction is removed in NW 702.

Conversion of a data object of type "C" to type "l" is not supported

Similar Messages

Maybe you are looking for