Version Compatibility on Type Specification Like

Hi,
I'm Copying one Z Function Module from 4.6 version to 4.7 version. In 4.7 version the Type Specification Like is not allowed. When i'm using the Like type Specification the Internal table which i refered is not holding the value.
Anyone can suggest me how to overcome this problem.
Regards,
Gopal

Hi ,
Are you talking about the interface of the FM , i.e. the parammeters .
If yes , then ony way is ti define a table type of the internal table you want to pass to the FM , and use it.
Regards
Arun

Similar Messages

Data Vs Types and Type Vs Like

hi frds can you send main diffrences between
Data Vs Types   and     Type Vs Like.
some what briefly explanation.......... i am in confusion in this

Hi Madhu,
Data is used to create data object ( means memory will be allocated)
Types is used to create structures
Type is used to refer to Predefined data types ( like n,i,f,d,t,p,x....)
Like is used to refer the local variables.
All ABAP programs can define their own data types. Within a program, procedures can also define local types.
You define local data types in a program using the
TYPES .
TYPES: spfli_type TYPE spfli,
       surname(20) TYPE c,
       BEGIN OF address,
             name       TYPE surname,
             street(30) TYPE c,
             city       TYPE spfli_type-cityfrom,
       END OF address,
       town TYPE address-city.
This example shows the definition of two structure types in a program - SPFLI_TYPE and ADDRESS. The structure of the data type SPFLI_TYPE is taken from the database table SPFLI in the ABAP Dictionary. The components of SPFLI_TYPE are the same as the columns of SPFLI. The individual data types of the components are the ABAP equivalents of the data types of the columns of the database table. The structure type ADDRESS is newly defined. The component ADDRESS-NAME takes the data type of the previously-defined type SURNAME, the component ADDRESS-STREET is newly-defined, ADDRESS-CITY takes the data type of column CITYFROM of the structure type SPFLI_TYPE.
TYPES: BEGIN OF struct1,
         col1 TYPE i,
         BEGIN OF struct2,
           col1 TYPE i,
           col2 TYPE i,
         END OF struct2,
       END OF struct1.
TYPES mytype TYPE struct1-struct2-col2.
The example shows how you can construct a nested structure type STRUCT1 with a complex component STRUCT2 by nesting TYPES BEGIN OF ... TYPES END OF blocks, and how you can address the inner components.
local types in program
referring to predefined ABAP types:
TYPES: surname(20) TYPE c,
       street(30)   TYPE c,
       zip_code(10) TYPE n,
       city(30)     TYPE c,
       phone(20)    TYPE n,
       date         LIKE sy-datum.
local structure in program
referring to the above types
TYPES: BEGIN of address,
         name TYPE surname,
         code TYPE zip_code,
         town TYPE city,
         str TYPE street,
       END OF address.
local nested structure in program
referring to the above types
TYPES: BEGIN of phone_list,
         adr TYPE address,
         tel TYPE phone,
       END OF phone_list.
This example shows how to create complex data types from simple type definitions. After a set of simple data types are created with ABAP predefined types, a structured type ADDRESS is defined using the data types defined earlier. Finally, a nested structure type, PHONE_LIST, is created, whose first component has the type ADDRESS.
Table types
Local tables in a program are called internal tables. To construct a new internal table type, use the syntax:
TYPES can be any known data type. Specifying the key is optional. Internal tables can thus be generic. For more information, refer to Internal Tables.
DATA
The Statements TYPES and DATA
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.
TYPES: BEGIN OF struct,
         number_1 TYPE i,
         number_2 TYPE p DECIMALS 2,
       END OF struct.
DATA: wa_struct TYPE struct,
       number    LIKE wa_struct-number_2,
       date      LIKE sy-datum,
       time      TYPE t,
       text      TYPE string,
       company   TYPE s_carr_id.
This example declares variables with reference to the internal type STRUCT in the program, a component of an existing data object wa_struct, the predefined data object SY-DATUM, the predefined ABAP type t and STRING, and the data element S_CARR_ID from the ABAP Dictionary.
Referring to Generic Data Types
If you refer to one of the generic predefined ABAP types of fixed length (c, n, p, x) in the TYPES or DATA statement, you must specify the undefined technical attributes.
TYPES|DATA var[(length)] TYPE type ...
TYPES|DATA var TYPE type ...
DATA: text1,
      text2 LENGTH 2,
      text3 TYPE c LENGTH 3,
      pack TYPE p DECIMALS 2 VALUE '1.225'.
This example creates three character variables with field lengths of one, two, and three bytes respectively, and a packed number variable with field length 8 bytes and two decimal places. If the attribute Fixed point arithmetic is set, the value of pack is 1.23.
This example shows how to declare elementary data objects with reference to predefined ABAP types.
PROGRAM demo_elementary_data_objects.
DATA text1 TYPE c LENGTH 20.
DATA text2 TYPE string.
DATA number TYPE i.
text1 = 'The number'.
number = 100.
text2 = 'is an integer.'.
WRITE: text1, number, text2.
This program produces the following output on the screen:
The number              100 is an integer.
In this example, the data objects text1, text2 and number are declared with the DATA statement. The technical attributes are determined by referring to the predefined ABAP types c, string, and I. Values from unnamed literals are assigned to the data objects. The contents of the named data objects are displayed on the list.
Specifying a Start Value
When you declare an elementary fixed-length variable, the DATAstatement automatically fills it with the type-specific initial value as listed in the table in the Predefined ABAP Types section.
However, you can also specify a starting value of a fixed-length elementary variable (also within a structure declaration) using the VALUE addition in the DATAstatement:
DATA var ... VALUE val|{IS INITIAL}.
Specifying start values:
DATA: counter TYPE p VALUE 1,
      date    TYPE d VALUE '19980601',
      flag    TYPE n VALUE IS INITIAL.
After this data declaration, the character string flag contains its type specific
Initial value 0.
Difference Between TYPE & LIKE
Difference between TYPE & LIKE

Help with TYPE and LIKE statements

HI guys,
I know this is really novice stuff, but I am a little confused.
Can anyone please explain the exact difference between TYPE and like with the help of a program, to understand it.
What situation would demand the use of each of the LIKE statement, since I can do all these things using the TYPE ?

Hi Akhil,
I summarized the info in SDN posts and SAP Help, to make it easier for you to understand. I also included some code snippets. Hope these prove to be helpful to you.
The following is from SAP Help:
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
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.
Example
TYPES: BEGIN OF struct,
         number_1 TYPE i,
         number_2 TYPE p DECIMALS 2,
       END OF struct.
DATA: wa_struct TYPE struct,
       number    LIKE wa_struct-number_2,
       date      LIKE sy-datum,
       time      TYPE t,
       text      TYPE string,
       company   TYPE s_carr_id.
This example declares variables with reference to the internal type STRUCT in the program, a component of an existing data object wa_struct, the predefined data object SY-DATUM, the predefined ABAP type t and STRING, and the data element S_CARR_ID from the ABAP Dictionary.
The following info is from various posts:
--> Type: It is used when userdefined object link with SAP system data type.
Local types mask global types that have the same names. When typing the interface parameters or field symbols, a reference is also possible to generic types ANY, ANY TABLE,INDEX TABLE, TABLE or STANDARD TABLE, SORTED TABLE and HASHED TABLE.
--> Like: It is when data object link with the other data object.
--> 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.
you can refer to all visible data objects at the ABAP program's positon in question. Only the declaration of the data object must be known. In this case it is totally irrelevant whether the data object already exists physically in
memory during the LIKE reference. Local data objects mask global data objects that have the same name.
--> 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.
Types: var1(20) type c.
data: var2 type var1. ( type is used bcoz var1 is defined with TYPES and it
does not occupy any memory spce.
data: var3 like var2. ( like is used here bcoz var2 is defined with DATA
so it does occupy space in memory ).
data: material like mara-matnr. ( like is used here bcoz mara-matnr is stored in memory)
--> Type refers the existing data type
--> Like refers the existing data object
Please Reward Points if any of the above points are helpful to you.
Regards,
Kalyan Chakravarthy

Photoshop Extended version compatability

I have Photoshop CS3 Extended on both PC (Windows XP) and Mac (OS X Leopard). I'm able to upgrade the PC to CS5 Extended but not the Mac.
My questions are:
1 - Will Photoshop CS5 extended work on Windows XP?
2 - Are CS3 and CS5 backwards compatible - if I work on a document in PC CS5 will the Mac CS5 version be able to open it? I know there will be some things that would not translate backwards, such as Puppet Warp and some of the newer masking and layers features, but I'd still like to be able to work on more basic functions of masking, cloning, etc. on both computers.
Thanks for any help,
Marcy

Noel Car boni wrote:
For the most part, a document saved from Photoshop CS5 will be no problem to open in CS3. There's a "Maximize Compatibility" setting in Edit - Preferences - File Handling section that you'll want to set to "Always".
-Noel
My take is that the compatibility setting should be set based on the kind of work one does. I have it set to "Never". When you check this setting ON you tell Photoshop to save along with all your layers another entity, which is a flattened version of the image. This, makes every PSD file you save larger by a non trival amount.
So this setting should have no effect regarding Photoshop to Photoshop version compatibility. All Photoshop versions understand layers and do not need a flattened version. It's intended to maximize the compatibility between Photoshop and any other program that does not know about layers but reads PSD files. If you have many of your PSD files going to, for example, Lightroom or Premiere then set it to "Always". If not, you can set it to "Ask" or "Never" and save yourself a lot of storage space.
Paulo

A newer version of data type BBP_PDS_HSS_IC was found than one required

Hi,
When I create a SC, it is automatically approved but the PO is not created.
If I check TRX SM58 I get the message:
"A newer version of data type BBP_PDS_HSS_IC was found than one required"
Any ideas?
Carlos Durazo

Hi
Which SRM version are you using ?
By an chance have you created any new fields in the standard structure
'BBP_PDS_HSS_IC' using SE11 Transaction in SRM system. Please confirm the same by taking help of ABAP person here. Seems to be like the structure is not Activated completed.
Related SAP OSS Notes ->
Note 758067 - SRM 4.0: Change documents of new sets (DynAttr, Weight)
Note 820201 - Document changes for attachments does not work
Hinweis 691880 - Changes in tolerances not displayed in purchase order
Note 1018714 - Change documents: Time stamp of the application server
Note 1006898 - Deleted vendor not displayed in Change hist of Shopping cart
Do let me know.
Regards
- Atul

Any idea when GTX 970's will be added to the supported list in the latest version of premiere? id like my cuda.

Any idea when GTX 970's will be added to the supported list in the latest version of premiere? id like my cuda.

I Too would like to know. I've finally finished upgrading my rig with a 970, and as far as I know, there's been some good things and not so good things. (I'm on CC 2014.1 with Windows 8.1 Pro) I'll post screenshots when I get back to my computer.
FIrst things first: Make sure to install the CUDA specific to the 970/980. They have their own toolkit, that I believe people miss. I installed this, and then manually added my card to te supported cards file in the Premiere, AE, and Speedgrade files. When I opened Premiere, it's automatically set to use CUDA acceleration, so I believe it's supported there. I wasn't able to test this, unfortunately. I will confirm this soon.
Second, when I open After Effects, the Previews preference pane states my card is supported, and all the info below it seems correct, like the shader model. The only thing that seems off is the OpenGL, which is set to 2.1.2 NVIDIA or something of the like instead of 4.x, but I believe its an NVIDIA optimized driver, so I'm not too concerned. The big thing for me is the error message that I recieve when I try to enable Ray-traced 3D. I recieve a compilation error, followed by another message, and I have no clue what to do with them.
I'm really hoping Adobe releases an updates that bring full native support for these cards, as I'm running an class at my high school where I need to build three machines, all of which will have a 970 inside, and if Adbe doesn't support these cards, I'm kind of screwed as the pipeline is based completely in Adobe with its Dynamic Link and CUDA acceleration. Come on Todd, we believe in you!
TL;DR Yes, CUDA acceleration should work within Premiere Pro CC 2014.1, but make sure to install the correct CUDA drivers from NVIDIA (they should be in the yellow boxed text on the downloads page)

Currently running Mac OS X version 10.5.8, would like to update to 10.8.2 in order to also upgrade to itunes 10.7. Any suggestions ?

currently running Mac OS X version 10.5.8, would like to update to 10.8.2 in order to also upgrade to itunes 10.7. Any suggestions ?

Upgrade Paths to Snow Leopard, Lion, and/or Mountain Lion
You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
Upgrading to Snow Leopard
You must purchase Snow Leopard through the Apple Store: Mac OS X 10.6 Snow Leopard - Apple Store (U.S.). The price is $19.99 plus tax. You will be sent physical media by mail after placing your order.
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
     Snow Leopard General Requirements
       1. Mac computer with an Intel processor
       2. 1GB of memory
       3. 5GB of available disk space
       4. DVD drive for installation
       5. Some features require a compatible Internet service provider;
           fees may apply.
       6. Some features require Apple’s MobileMe service; fees and
           terms apply.
Upgrading to Lion
If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
You can purchase Lion by contacting Customer Service: Contacting Apple for support and service - this includes international calling numbers. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
     Lion System Requirements
       1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
           or Xeon processor
       2. 2GB of memory
       3. OS X v10.6.6 or later (v10.6.8 recommended)
       4. 7GB of available space
       5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
     OS X Mountain Lion - System Requirements
       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer)
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer)
         3. MacBook Pro (Mid/Late 2007 or newer)
         4. MacBook Air (Late 2008 or newer)
         5. Mac mini (Early 2009 or newer)
         6. Mac Pro (Early 2008 or newer)
         7. Xserve (Early 2009)
     Are my applications compatible?
         See App Compatibility Table - RoaringApps.
     Am I eligible for the free upgrade?
         See Apple - Free OS X Mountain Lion upgrade Program.
     For a complete How-To introduction from Apple see Upgrade to OS X Mountain Lion.

Hi. I am working on a Mac OSX 10.10.2 Yosemite. I'm working remotely with a woman who is using indesign CS8.2 I'm still on CS6.8 and can't open her files. I would like to upgrade to the latest version and I'd also like to know why these upgrades are not a

Hi. I am working on a Mac OSX 10.10.2 Yosemite. I'm working remotely with a woman who is using indesign CS8.2 I'm still on CS6.8 and can't open her files. I would like to upgrade to the latest version and I'd also like to know why these upgrades are not automatic as i pay a monthly subscription to the cloud. Thanks.

A Cloud subscription SHOULD always show you the most recent updates, so you may then choose to do the install
CC desktop lists applications as "Up to Date" when they are not
-http://helpx.adobe.com/creative-cloud/kb/aam-lists-removed-apps-date.html
-and added step https://forums.adobe.com/thread/1529654
Yosemite sometimes has problems, often related to "default" permissions needing to be changed
-one person's solution https://forums.adobe.com/thread/1689788
-and a Java update https://forums.adobe.com/thread/1507936
-update breaks things https://forums.adobe.com/thread/1772260
-http://blogs.adobe.com/creativecloud/creative-cloud-and-yosemite/
-https://helpx.adobe.com/x-productkb/global/mac-os-yosemite-compatability.html

NWDS version compatibility !!

Dear Friends,
I would like to pose a simple question on the compatiblity of the NWDS version with my Portal version
My client set up has Portal version of NW 7.0.1 SP3 .The information i get from the SLD has the following info
Software Components all components...
Name Version Applied
sap.com/SAP-JEECOR 7.01 SP3 (1000.7.01.3.0.20081208163400) 20090713142753
sap.com/SAP-JEE 7.01 SP3 (1000.7.01.3.0.20081208163400) 20090713142549
Now the client says it has an NWDS version with 7.01.03
Now we need to set up a system at offshore as well.I couldnt find an NWDS version of the afore said 7.01.03 so i got NWDS 7.1 EHP1 SP4 Preview version from SDN .I would like to ask you if this version is compatible with the NW 7.0.1 SP3. You can also suggest me a more compatible version of NWDS or a place in SDN where i can look up for the compatibility between NWDS and the NW .
Kindly do the needful.

Hi Nishita,
I agree with Gilles... You can not use NWDS 7.1 for your portal 7.0.1. it wont support.
Always see to it that ur portal version matches with NWDS (even lower version of NWDS works).
For confirmation check below threads...
/thread/1551768 [original link is broken]
NWDS Compatability issue
Thanks,
pradeeP

TYPE vs LIKE

Hi, would like to know what is the different btw the 2 declaration below: Which one is better? How the memory allocated for both?
MATNR TYPE MARA-MATNR.
MATNR LIKE MARA-MATNR.
Thank you.

Hi,
LIKE means the datatype of the variable is similar to the referenced variable.
TYPE means it is a predefined data type.
Diff bn TYPE N LIKE.
If you are refering to a Data object use LIKE
And if you are refering to a Data type use TYPE
You can create a variable that inherits exactly the same technical attributes as an existing data type or data object as follows:
DATA <f> [TYPE <type>|LIKE <obj>]...
If you use the TYPE addition, <type> is any data type with fully-specified technical attributes. This can be a:
Non-generic predefined ABAP type (D, F, I, T, STRING, XSTRING)
Any existing local data type in the program.
Any ABAP Dictionary data type
If you use the LIKE addition, <obj> is a data object that has already been declared. This can also be a predefined data object. The variable <f> adopts the same technical attributes as the data object <obj>. You can also use LIKE to refer to a line of an internal table that has already been declared as a data object:
DATA <f> LIKE LINE OF <itab>.
To ensure compatibility with previous releases, <obj> can also be a database table, a view, a structure, or a component of a structure from the ABAP Dictionary.
The data types to which you refer can be elementary types, reference types, or complex types (structures or tables). For elementary field types, the variables are a single field in memory. When you declare a data type with fixed length (D, F, I, T) the system fixes the amount of memory that will be assigned. When you declare an object with a variable length (STRING, XSRTING), the system only assigns enough memory to administer the object. The length of the data object is managed dynamically at runtime. For structures, the variables are a sequence of variables, which may themselves also be included in further complex structures. The individual components take their name <ci> from the type <type> or object <obj>, and can be addressed using <f>-<c i> For tables, the memory contains administration entries that can be filled dynamically at runtime.
Go through the link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
For TYPE
http://help.sap.com/saphelp_47x200/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm
For LIKE
http://help.sap.com/saphelp_47x200/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb367a358411d1829f0000e829fbfe/content.htm
Regards,
Priyanka.

RoboHelp Version Compatibility

Hello everybody from Greece,
I want to ask about version compatibility. I've got RoboHelp
HTML 5.0.2 and my client has RoboHelp HTML 3.1. He asks if I can
compile his project, but I wnt to know if he will be able to work
with the project that I will work with in version 5.0.2.
Is there a way to save the project to an older version?
Is there a compatibility problem in general?
Is there going to be a problem if I compile the project in
the newer version? (Will he see any differences?)
Any help would be appreciated.
Thanks in advance.

Hi Tansou and υποδοχή,
You should be able to open up the X3.1 in X5.02 without a
problem. X5 will preserve all the feature used in X3.1. Are you
compiling HTML Help? My guess is that you won't see any difference
in the output when you compile.
However, the problem comes when you try and do this the other
way around. Robohelp is not backward compatible. So you won't be
able to pass a modified project back to your client. Rick the
robowizard has a few tricks to help with backward compatibility if
you don't mind going under the hood. However, not sure if this
works with X3.1 jumping to X3.1.
What type of output are you generating?
Hope that helps
Craig

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

Version compatibility of 10G Application Server 10.1.2.0.2 with JDK 1.5.

hi buddies,
I want to know that whether
10G Application Server 10.1.2.0.2 with JDK 1.5. is Version compatibility
pls do send ur replies if known to you.

Hi ,
As far as I know AS 10.1.2.0.2 is Not certified with JDK 1.5.
Please see below some links where you can double-check this
1. OC4J with JDK 1.5 JSP compilation error
2. http://docs.huihoo.com/oracle/docs/B14099_19/web.1012/b14011/chap1.htm
"Only the JDK 1.3.1 and JDK 1.4 compilers are supported and certified by OC4J. It is possible to specify an alternative compiler by adding a <java-compiler> element to the server.xml file, and this might provide a workaround for the "classes not in packages" issue, but no other compilers are certified or supported by Oracle for use with OC4J."
3. "Certified JDKs" from
http://www.oracle.com/technology/software/products/ias/files/as_certification_r2_101202.html
BR,
Mihai

Document Type specific to Application Type

Dear All,
Can any one guide me how to configure Document Type specific to Application Type in DMS.
What I mean, Doc Type 'DRW' should be used only ACAD Drawings, user should not able to attach or check in word document to it.
same time Doc Type 'DOC' should be used only word document , user should not able to attach or check in ACAD Drawings to it.
Thanks & Rgds,
Sukan
[email protected]

Hi Sukan,
Go to Tcode "DC10" i.e. Define Document types
here you find the two fields "Def WS Appl." and "Dis WS applic."
these two fields are for specifying the Application you need for a particular document types.
so when you try to create a DIR and attach the Original by create or open then
by default you see the application what you have set in the DC10 for that particular document type but can be changed.
So you need to put a check on field "DAPPL" i.e. Authorization check through Object "C_DRAW_DOK"[/i]
Regards
Rehman
Reward Your Points If Useful

Version compatibility for installing WLS and ADR for ADF 11.1.2.0

Hi,
Can anyone pls let me know what versions of Weblogic server, Application Development Runtime (ADR) is required to install Oracle JDeveloper 11.1.2.0
B'coz currently I am trying to install Weblogic server, ADR and ADF separately and try to deploy and publish an application in ADF 11.1.2.0 verison.
I am trying this for the past 4 days, but still can't deploy an application successfully in ADF 11.1.2.0 version. Pls let me know the version compatibility.
Thanks,
Aparna

Hi John,
Even I saw the link that u had mentioned. From where can I install these ?
I had downloaded WLS 10.3.5 and ADR 11.1.1.5 separately. But from where do I install the patch ?? I didn't find a proper source to download.
Pls help.
Thanks,
Aparna

Version Compatibility on Type Specification Like

Similar Messages

Maybe you are looking for