UCCHECK error in upgrade: Data type and structure not mutually convertible.

Hi ABAPers,
We have upgraded our system from 4.6c to ECC 6.0. We are at the unicode check stage. I am getting an error " 'V_LEV' and 'T_RES_TOTALS' are not mutually convertible in a Unicode program."
The structure of T_RES_TOTALS is like this:
BEGIN OF T_RES_TOTALS OCCURS 0,
    FLD1TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD1        LIKE ZTQ_VBKA-ZZREP_FLD1,
    FLD2TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD2        LIKE ZTQ_VBKA-ZZREP_FLD2,
    FLD3TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD3        LIKE ZTQ_VBKA-ZZREP_FLD3,
    FLD4TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD4        LIKE ZTQ_VBKA-ZZREP_FLD4,
    FLD5TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD5        LIKE ZTQ_VBKA-ZZREP_FLD5,
    FLD6TEXT    LIKE ZTQ_REPVAL-VTEXT,
    FLD6        LIKE ZTQ_VBKA-ZZREP_FLD6,
    VTEXT    LIKE ZTQ_SRCET-TXT,
    SOURCE    LIKE ZTQ_SRCET-SOURCE,
    NAME1    LIKE KNA1-NAME1,
    RAREA     LIKE KNA1-KUNNR,
    TOTAL     TYPE I,
    LEV(2)      TYPE N,
END OF T_RES_TOTALS,
V_LEV is declared as this:
V_LEV(2)      TYPE N,
Below is the code and the line (marked in bold) which gives the error:
LOOP AT T_RES_TOTALS.
    *V_LEV = T_RES_TOTALS.*
    AT NEW FLD1.      PERFORM FLD1_START.    ENDAT.
    AT NEW FLD2.      PERFORM FLD2_START.    ENDAT.
    AT NEW FLD3.      PERFORM FLD3_START.    ENDAT.
    AT NEW FLD4.      PERFORM FLD4_START.    ENDAT.
    AT NEW FLD5.      PERFORM FLD5_START.    ENDAT.
    AT NEW FLD6.      PERFORM FLD6_START.    ENDAT.
    AT NEW SOURCE.    PERFORM SOURCE_HEADER. ENDAT.
    AT END OF RAREA. PERFORM RES_AREA_LINE. ENDAT.
    AT END OF SOURCE. PERFORM SOURCE_TOTAL. ENDAT.
    AT END OF FLD6.   PERFORM FLD6_END.      ENDAT.
    AT END OF FLD5.   PERFORM FLD5_END.      ENDAT.
    AT END OF FLD4.   PERFORM FLD4_END.      ENDAT.
    AT END OF FLD3.   PERFORM FLD3_END.      ENDAT.
    AT END OF FLD2.   PERFORM FLD2_END.      ENDAT.
    AT END OF FLD1.   PERFORM FLD1_END.      ENDAT.
ENDLOOP.

write as below ...
LOOP AT T_RES_TOTALS.
 V_LEV = T_RES_TOTALS-LEV. <----
AT NEW FLD1. PERFORM FLD1_START. ENDAT.
 AT NEW FLD2. PERFORM FLD2_START. ENDAT.
 AT NEW FLD3. PERFORM FLD3_START. ENDAT.
 AT NEW FLD4. PERFORM FLD4_START. ENDAT.
 AT NEW FLD5. PERFORM FLD5_START. ENDAT.
 AT NEW FLD6. PERFORM FLD6_START. ENDAT.
 AT NEW SOURCE. PERFORM SOURCE_HEADER. ENDAT.
 AT END OF RAREA. PERFORM RES_AREA_LINE. ENDAT.
 AT END OF SOURCE. PERFORM SOURCE_TOTAL. ENDAT.
 AT END OF FLD6. PERFORM FLD6_END. ENDAT.
 AT END OF FLD5. PERFORM FLD5_END. ENDAT.
 AT END OF FLD4. PERFORM FLD4_END. ENDAT.
 AT END OF FLD3. PERFORM FLD3_END. ENDAT.
 AT END OF FLD2. PERFORM FLD2_END. ENDAT.
 AT END OF FLD1. PERFORM FLD1_END. ENDAT.
ENDLOOP.

Similar Messages

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.

BDoc: Related Data Type and Message Structure

Related Data Type and Message Structure are two attributes of a BDoc. Can anyone tell what they are used for?
Thanks in advance.
Regards,
Hui
BTW: Mush reward for good answers.

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstract types that are not yet fixed to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message.
A message type does not define the direction of the message exchange, in other words, whether it is a request or a response. In exceptional cases you can use the same message type for both the request and the response message.

Replicat : GGS ERROR 171 Unknown data type received 0x54 49 .

I am trying to run an initial load as shown in the tutorial at http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/goldengate/11g/GGS_Sect_Config_WinUX_ORA_to_WinUX_ORA.pdf and I am seeing this error in the REPLICAT process.
I have tried using the SOURCEDEFS clause as well (Even though the source and Target structures are exactly similar), but I run into the same issue.
** Run Time Messages **
*2011-04-14 12:02:15 GGS ERROR 171 Unknown data type received <0x54 49>.*
The only other Indication that I see in the report file is the following Warning message
*2011-04-14 12:02:15 GGS WARNING 201 Rounding up LOBWRITESIZE 32528 to be a multiple of LOB chunk size (16324).*
LOBWRITESIZE = 32648 bytes.
Here are the other details. If you need any more information, please let me know
GoldenGate Delivery for Oracle
Version v9.5.1.31 Build 003
HP-UX 11.23 (optimized 64-bit), Oracle 10g on Jun 24 2008 13:43:23
Copyright GoldenGate Software, Inc. 1995-2008
Starting at 2011-04-14 12:02:09
Database Version:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
I'd appreciate any advice on fixing this issue.
Thanks,
Rajesh.

Looks like the error is because we have ASM set up at our place.. and I did not pay enough attention to this part of the tutorial Guide..
Note: When Oracle Automatic Storage Management (ASM) is in use, the TRANLOGOPTIONS ASMUSER and ASMPASSWORD must be set in the Extract parameter file. For more information refer to the GoldenGate for Windows & UNIX Administrator and Reference manuals.
Posting the reply here so that It'd be useful for anyone running into the same issue later.
Cheers!
Rajesh.

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 type and Data object

Hi Friends,
        What is the difference between Data type and Data object?
Best Regards,
VRV Singh

hi
good
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
Constructing New Data Types
The TYPE addition allows you to construct new data types in the TYPES, DATA; CONSTANTS; and STATICSstatements. In the TYPES statement, these are local data types in the program. In the other statements, they are attributes of new data objects, meaning that the newly defined data types are not free-standing. Rather, they are linked to database objects.This means that you can refer to them using the LIKEaddition, but not using TYPE.
To construct new data types, the addition TYPE can be used with the following type constructors:
·        Construction of reference types
REF TO type|dobj
·        Construction of structured data types
BEGIN OF struc_type.
END OF struc_type.
·        Construction of table types
tabkind OF linetype
These data types only exist during the runtime of the ABAP program.
Referring to Known Data Types or Data Objects
Using the additions TYPE or LIKE in the TYPESstatement, local data types in a program can be referred to known data types or data objects. This is mainly the case with user-defined elementary data types. If you declare variables using the additions TYPE type or LIKE dobj with statement DATA, the data type of var is already fully defined before the declaration is made.
The known types or data that are referred to must be visible at the point where the data type or variable is declared.
A known data type can be any of the following:
·        A predefined ABAP type to which you refer using the TYPE addition
·        An existing local data type in the program to which you refer using the TYPE addition
·        The data type of a local data object in the program to which you refer using the LIKE addition
·        A data type in the ABAP Dictionary to which you refer using the TYPE addition. To ensure compatibility with earlier releases, it is still possible to use the LIKE addition to refer to database tables and flat structures in the ABAP Dictionary. However, you should use the TYPE addition in new programs.
The LIKE addition takes its technical attributes from a visible data object. As a rule, you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The data object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.
·        In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.
·        You can also refer to the data objects of other visible ABAP programs. These might be, for example, the visible attributes of global classes in class pools. If a global class cl_lobal has a public instance attribute or static attribute attr, you can refer to it as follows in any ABAP program:
DATA dref TYPE REF TO cl_global.
DATA: f1 LIKE cl_global=>attr,
       f2 LIKE dref->attr.
You can access the technical properties of an instance attribute using the class name and a reference variable without first having to create an object. The properties of the attributes of a class are not instance-specific and belong to the static properties of the class.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
thanks
mrutyun^

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

Line type and structure.

What is the difference between line type and structure?
one real time use of both.
instead of line type we can directly use the corresponding tables.
Points assured.
regards,
Prabhu.

Hi
The line type of a table type can be defined by:
Specification of a type that already exists (data element, structure, table type, table, view) whose properties are then copied as properties of the defined table line.
Direct type input, where data type, number of positions, and, if required, decimal places, are entered directly.
Specification of a reference type.
structure
The table category defines how the logical table description defined in the ABAP Dictionary is represented in the database.
There are the following table categories:
transparent table
structure
append structure
For internal purposes, such as storing control data or update texts, there are in addition the following table categories:
pooled table
cluster table
generated view structure
reward if usefull

Difference Between Data type and message type

Hi,
    i have doubt on data type and message type.why we are mapping the message type why not data type?wht is the difference between data type and message type?

Hi Narayanana,
Data type defines the structure of your xml message.Message type is the wrapper of data type.You will be using your message type while mapping and not the data type.Its the abstraction concept used in oops
kanan thiyam
Posts: 28
Questions: 7
Registered: 1/8/07
Forum points: 24
   Re: What is deffernce b/w Data type and message type
Posted: Jun 13, 2007 8:05 AM    in response to: suresh k         Reply      E-mail this post
Hi Suresh,
Data Type defines the structure of the message and it will be wrapped under Message Type.
Hope the details below will clearify your doubts.
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store.
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
Details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
kanan

Resources for designing data types and message types

Hi
I wanted to know if anyone can recommend me some good resources which can explain the design considerations for designing data types and message types in XI which can help promote reusability.
Thanks.
Best Regards,
Kiran

hi,
there no rare rule whe you define your data type, why i tell you this, because you define a data type since the documentation that sender sistem team gives to you. so you only have to copy this structure to PI.
now about Message Type less problems, because, you a Data type is assign to a Message Type, whats it means.
when you define a DATA type you are defining the structure of you XML, que you assing the data type to a message type this structure pass to be an xml document.
Thanks you
Rodrigo

Simple types and structure

Hi
can any one tell me Difference between simple types and structure ?
Thanks,
Kiran

Hi Ravi,
As my concern there is difference between simple type and structure.
1SIMPLE TYPEit behave as TYPE proprty of value attibute .suppose you will create on value attribute as simAtt.then you can put that simple type in your attribute TYPE property .actualy it treated as data type like string,integer........
one more thing you want to change data type in your application then you will create SIMPLE TYPE..then put it TYpe property of value Attribute
Ex--you want to change the format of double value using "," then you will change only by using simple type.
STRUCTURE---Basically it use for creating for context value node in any context of controller(View,component )if you creat one structure then add number of attribute .when you create context value node then you binding the structure then automatically it will populate with value node as structure name and attribute .
SIMPLE TYPE---only put as Data type of Attribute and simple type also use within Structure at time of creation
STRUCTURE---you can use for DAta type of Apptibute..
thanks
Jati

Mapping between oracle data types and ms sql server data types

hello
i need mapping between oracle data types and ms sql server data types
where can i find them ?

read this
http://download.oracle.com/docs/cd/E10405_01/doc/appdev.120/e10379/ss_oracle_compared.htm

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

Create dynamic data type in structure

Hi Experts,
I am new to ABAP.
In my scenario data type is varying for the field. for that I need to create dynamic data type in structure, this structure I am using for internal table for OVS search input.
Please suggest the solution for this.
Advance thanks,
Regards,
BBC

Thanks for your quick reply,
I used your logic like this.
data:
ls_component type abap_componentdescr,
lt_component type abap_component_tab.
*... (1) define structure components :
clear ls_component.
ls_component-name = 'NVALUE'.
ls_component-type ?= cl_abap_typedescr=>describe_by_name( <fs_seg_v>-fieldname ).
insert ls_component into table lt_component.
*... (2) create structure
data lr_strucdescr type ref to cl_abap_structdescr.
data lr_data_struc type ref to data.
lr_strucdescr = cl_abap_structdescr=>create( lt_component ).
create data lr_data_struc type handle lr_strucdescr.
field-symbols <fs> TYPE any.
assign lr_data_struc->* to <fs>.
your logic is working fine.
here I am getting feild name (<fs_seg_v>-fieldname) from internal table.
But I need to assign same field name structure to query parameter.
FIELD-SYMBOLS: <ls_query_params> TYPE lty_stru_input.
Please can you suggest how I can refer the field name structure?
Regards,
BBC

UCCHECK error in upgrade: Data type and structure not mutually convertible.

Similar Messages

Maybe you are looking for