Describe Object Type / Difference between desc & USER_TYPE_ATTRS ?

Hi,
1)Can someone show me how to use the sql+ 'desc' functionality in plsql? I need
to descrive Object Types in a plsql procedure.
2)What is the difference between using the 'describe' function - for describing an object type-and doing a select on USER_TYPE_ATTRS etc..?
Sometimes desc gives an error while querying user_type_attrs works fine!
db.version: 8.1.7.4
best regards
B.

describe instruction is a SQL*Plus feature not PL/SQL
Rgds.

Similar Messages

OSB to Object Types: difference between NULL value and not available

Hello all,
I have a question about Object Types. More specifically, how to differentiate between an empty value (null) and a string not available.
This is my case:
I have created an object type with three parameters.
CREATE OR REPLACE TYPE OSB_EMP_OBJ_TYPE AS OBJECT
(EMP_ID NUMBER
,DEPT_ID NUMBER
,ORDER_ID NUMBER
,CONSTRUCTOR FUNCTION OSB_EMP_OBJ_TYPE
RETURN self as result
/I would like to see what happens when I put an empty string into emp_id, NULL into DEPT_ID and nothing into ORDER_ID.
To do so I have this test script:
declare
p_emp OSB_EMP_OBJ_TYPE := OSB_EMP_OBJ_TYPE();
begin
p_emp.EMP_ID := '';
p_emp.DEPT_ID := null;
-- p_emp.ORDER_ID := null;
if p_emp.EMP_ID is null
then
    dbms_output.put_line('Empty');
end if;
if p_emp.DEPT_ID is null
then
    dbms_output.put_line('NULL');
end if;
if p_emp.ORDER_ID is null
then
    dbms_output.put_line('Not available');
end if;
end;The result of this is:
Empty
NULL
Not availableIt seems that Oracle treats all three situations alike. What I would like to achieve is a way to see that p_emp.ORDER_ID was not initialized.
To elaborate a bit: in our production system this procedure would be called from OSB and the object type would by the input for that procedure. Our database version is 10.2.0.5.0.
Our procedures look something like this:
procedure p_procedure ( p_emp in osb_emp_obj_type )
is
begin
do_something;
end;Can anyone tell me if there is a way to achieve this, so I can see whether or not a value in the object type was filled?
Thanks in advance!

Darn...
Eventually we want to use this for an update procedure. The client gets all current data from the database by calling a webservice that (using OSB) selects the data from our database. What we want to achieve is that the client can update that data, by returning only the changed fields to an update procedure.
We then handle an empty tag to update the field to null, and we ignore missing tags.
OSB itself can handle this, but PL/SQL can't.
I'm now thinking of adding an indicator to each optional field (clear_field_yn). OSB can still check for empty tags or missing tags. When a tag is empty, it's corresponding indicator will be set to 'Y'. If the tag is missing, then it will be set to 'N'.
Is that a solution to consider, or is there a much simpler approach possible?

DESCRIBE FIELD statement difference between structure & Itab

Hai ,
I am trying to read field attributes using DESCRIBE FIELD satement & I am getting the field type
in SYDES_DESC-types.
When I am trying to read the attributes of a structure like the one below,
data : begin of STRUCT ,
           field1 type c,
           field2 type c,
        end of STRUCT.
and the table like below,
data : begin of TAB1 occurs 10,
           field1 type c,
           field2 type c,
         end of TAB1.
that is ,
describe field STRUCT in w_sydes_desc.
describe field TAB1 in w_sydes_desc.
( w_sydes_desc is of type sydes_desc).
my question is,
for the above 2 stements the table W_SYDES_DESC-TYPES contains same values
though one is plain structure & another one is internal table with header line.
can any one tell how can we distinguish between the above fields?
or is ther any other approach to find wheter a variable is a struct or table?
Regards,
Bhaskar M

Hello,
describe field STRUCT in w_sydes_desc.
describe field TAB1 in w_sydes_desc.
When you use an int. table with HEADER LINE, then TAB1 represents the HEADER LINE & not the entire table body. To access the whole table you have to use TAB1[].
So you are getting the same results.
Try this coding:
TYPE-POOLS: sydes.
DATA : BEGIN OF struct ,
field1 TYPE c,
field2 TYPE c,
END OF struct.
DATA:
w_sydes_desc TYPE sydes_desc,
w_sydes_desc1 TYPE sydes_desc.
DATA :
BEGIN OF tab1 OCCURS 10,
field1 TYPE c,
field2 TYPE c,
END OF tab1.
DESCRIBE FIELD struct INTO w_sydes_desc.
DESCRIBE FIELD tab1[] INTO w_sydes_desc1.
IF sy-subrc = 0.
WRITE: 'Hurray !!!'.
ENDIF.
BR,
Suhas

Difference between standard edition and enterprise edition?

Is there any document describing the feature differences between Oracle 9i standard edition and enterprise edition?
Specifically is Oracle Text bundled with the standard edition?
Thanks a lot
James

Hi,
Check this document:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=112591.1
Apart from the features that are present in E.E. and not in S.E., there is little difference (except the license price...).
Note that some seperately purchased options are only available with E.E., not S.E. (e.g. Partitioning, Enterprise Manager Packs).
MB

Difference between 4.7 version and 6.0 version

what is the difference between 4.7 version and 6.0 version particularly as far as SD is concerned?

dear vinayak
There are so many differences between the version in different objects
I will explain in two or more objects the difference
1 in the customer master in 4.6 version there is no partner function tab in the customer in xd01 t-code
and also there is no CIN tab in that version
but it is there in the 4.7 EE version
This is the major change from the 4.6cc to 4.7EE
2. in 4.7EE there is some settings that are related for CIN
which cannot be done in 4.7EE that means they need some patches for doing the configuration setting for the CIN
But we can do the same in the 6.0 version
These are the some of the settings that are differed in the two versions and in that two objects
Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
Re: SAP version differences 4.5b, 4.6c and ECC6.0
You can find the difference in release notes of each SAP version.
Here are the links.
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
rewards if it helps
siva

Difference between 4.7, ECC 5.0 and 6.0

Hi
Can some one explain the basic difference beteween the latest three versions in SAP i.e., 4.7, ECC 5.0 and 6.0.
Regards
Venkat

HI
HI
There are so many differences between the version in different objects
I will explaint in two or more objects the differece
1 in the customer master in 4.6 version there is no partner function tab in the customer in xd01 tcode
and also there is no CIN tab in that vrsion
Re: differnce b/n 4.7 and ecc 6.0
but itis there in the 4.7 EE version
This is the major change from the 4.6cc to 4.7EE
2. in 4.7EE there is some settings that are related for CIN
which cannot be done in 4.7EE that means they need some patches for doing the configuration setting for the CIN
But we can do the same in the 6.0 version
These are the some ofthe settings that are differed in the two versions and in that two objects
Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
Please follow the link below, you can download the Release notes for each realease of R/3 and ECC.
https://websmp210.sap-ag.de/releasenotesRelease Notes
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Do award points if you found them useful.
you can study the differences between versions with the following link
http://solutionbrowser.erp.sap.fmpmedia.com/

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.

What is the difference between the DataSource types in BI?

Hello,
Can someone please explain what is the difference between the four types of DataSources: DataSource for transaction data and DataSource for master data which contains DataSource for attributes, DataSource for texts and DataSource for hierarchies and explain and demonstrate at which scenario I will use each one?

When you load data into Cube/ODS, i.e. Transactional data, and you load data into it from Transaction Datasources.
For every Infobject there is Master data associated with it, and Attributes, Texts and hierarchy are types of Master Data.
Say Vendor is InfoObject, and its master data:
Vendor Vendor Desc
1 One
2 Two
Now in Transactional data Vendor 1 can be having multiple entries, and master data contacin master data of that person. Like if u go to some store, your address and personal info is going to save ones, and master data, and next time when you order something your personal details comes from master data, and whatever you buy comes under transaction data. Now with respect to you there may be many attributes, like address, contact number, and so on....and text is what which is going to describe in short who is this person. HIerarchy could be some chain, will tell how you r related to some other person, may be like if someone referred you.

Difference between DEclaring Itab with DATA & TYpe Statement?

HI Friends,
What is the Difference between Declaring Itab with DATA & TYpe Statement?

Hi,
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
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.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
 "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
 types : begin of ts_reclist,
mso-bidi- style='mso-tab-count:2'> receiver type somlreci1-receiver,
mso-bidi- style='mso-tab-count:2'> style='mso-tab-count: 1'> rec_type type somlreci1-rec_type,
mso-bidi- style='mso-tab-count:2'> end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal"> types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
 data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]> <![endif]> data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
 s_reclist-receiver = '[email protected]'. "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi- s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
 append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1"> style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
 EXPORTING
style='mso-tab-count:2'> document_data = docdata
style='mso-tab-count:2'> DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'> PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'> COMMIT_WORK = 'X' "used from rel.6.10
 TABLES
mso-bidi-font-size: style='mso-tab-count:2'> receivers = t_reclist
class="style1"> <![if !supportEmptyParas]> <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

Difference between abap object and function

hi all,
i read the book on abap object of the difference between abap object and classical abap.
i know that there is only 1 instance of a specific function group but somehow i still not so clear why subsequent vehicle cannot use the same function. i also can use the do and loop to call the function? if cannot then why?
hope can get the advice.
thanks
using function *********
function-pool vehicle.
data speed type i value 0.
function accelerate.
speed = speed + 1.
endfunction.
function show_speed.
write speed.
endfunction.
report xx.
start-of-selection.
*vehicle 1
call function 'accelerate'.
call function 'accelerate'.
call function 'show_speed'.
*vehicle 2
*vehicle 3
*****abap object*******
report xx.
data: ov type ref to vehicle,
 ov_tab type table of ref to vehicle.
start-of-selection.
do 5 times.
create object ov.
append ov to ov_tab.
enddo.
loop at ov_tab into ov.
do sy-tabix times.
call method ov->accelerate.
enddo.
call method ov->show_speed.
endloop.

Hi
Now try this:
REPORT ZTEST_VEHICLEOO .
PARAMETERS: P_CAR TYPE I,
 P_READ TYPE I.
* CLASS vehicle DEFINITION
CLASS VEHICLE DEFINITION.
PUBLIC SECTION.
 CLASS-DATA: MAX_SPEED TYPE I,
 MAX_VEHICLE TYPE I,
 NR_VEHICLES TYPE I.
 CLASS-METHODS CLASS_CONSTRUCTOR.
 METHODS CONSTRUCTOR.
 METHODS ACCELERATE.
 METHODS SHOW_SPEED.
 METHODS GET_SPEED EXPORTING E_SPEED TYPE I.
PRIVATE SECTION.
 DATA: SPEED TYPE I,
 NR_VEHICLE TYPE I..
ENDCLASS.
* CLASS vehicle IMPLEMENTATION
CLASS VEHICLE IMPLEMENTATION.
METHOD CLASS_CONSTRUCTOR.
 NR_VEHICLES = 0.
ENDMETHOD.
METHOD CONSTRUCTOR.
 NR_VEHICLES = NR_VEHICLES + 1.
 NR_VEHICLE = NR_VEHICLES.
ENDMETHOD.
METHOD ACCELERATE.
 SPEED = SPEED + 1.
 IF MAX_SPEED < SPEED.
 MAX_SPEED = SPEED.
 MAX_VEHICLE = NR_VEHICLE.
 ENDIF.
ENDMETHOD.
METHOD SHOW_SPEED.
 WRITE: / 'Speed of vehicle nr.', NR_VEHICLE, ':', SPEED.
ENDMETHOD.
METHOD GET_SPEED.
 E_SPEED = SPEED.
ENDMETHOD.
ENDCLASS.
DATA: OV TYPE REF TO VEHICLE,
 OV_TAB TYPE TABLE OF REF TO VEHICLE.
DATA: V_TIMES TYPE I,
 FL_ACTION.
DATA: V_SPEED TYPE I.
START-OF-SELECTION.
DO P_CAR TIMES.
 CREATE OBJECT OV.
 APPEND OV TO OV_TAB.
ENDDO.
LOOP AT OV_TAB INTO OV.
 IF FL_ACTION = SPACE.
 FL_ACTION = 'X'.
 V_TIMES = SY-TABIX * 2.
 ELSE.
 FL_ACTION = SPACE.
 V_TIMES = SY-TABIX - 2.
 ENDIF.
 DO V_TIMES TIMES.
 CALL METHOD OV->ACCELERATE.
 ENDDO.
 CALL METHOD OV->SHOW_SPEED.
ENDLOOP.
SKIP.
WRITE: / 'Higher speed', VEHICLE=>MAX_SPEED, 'for vehicle nr.',
 VEHICLE=>MAX_VEHICLE.
SKIP.
READ TABLE OV_TAB INTO OV INDEX P_READ.
IF SY-SUBRC <> 0.
 WRITE: 'No vehicle', P_READ.
ELSE.
 CALL METHOD OV->GET_SPEED IMPORTING E_SPEED = V_SPEED.
 WRITE: 'Speed of vehicle', P_READ, V_SPEED.
ENDIF.
Try to repeat this using a function group and I think you'll undestand because it'll be very hard to do it.
By only one function group how can u read the data of a certain vehicle?
Yes you can create in the function group an internal table where u store the data of every car: in this way u use the internal table like it was an instance, but you should consider here the example is very simple. Here we have only the speed as characteristic, but really we can have many complex characteristics.
Max

The difference between FIELD-SYMBOL and normal DATA TYPE

Dear experts,
Please see the example below, both are output the same result.
DATA: EXTERNAL_RECORD(4000),
 POSITION TYPE I,
 LENGTH TYPE N,
 ENTRY TYPE STRING.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
 EXIT.
ENDIF.
ADD 4 TO POSITION.
MOVE EXTERNAL_RECORD+POSITION(LENGTH) TO ENTRY.
WRITE ENTRY.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
 EXIT.
ENDIF.
ENDDO.
--OR It can be written as--
DATA: EXTERNAL_RECORD(4000),
 POSITION TYPE I,
 LENGTH TYPE N.
FIELD-SYMBOLS <ENTRY>.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
 EXIT.
ENDIF.
ADD 4 TO POSITION.
ASSIGN EXTERNAL_RECORD+POSITION(LENGTH) TO <ENTRY>.
WRITE <ENTRY>.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
 EXIT.
ENDIF.
ENDDO.
Is there any special circumstances we need to use FIELD-SYMBOL?
Why is FIELD-SYMBOL is introduce in the first place?
Kindly advice with example.
Thanks in advance for those who can help me on this.

HI,
You can use field symbols to make the program more dynamic. In this example the name of a table control is substituted by a field symbol. Thus you cal call the form with any internal table, using the name of the table control as a parameter.
Example
form insert_row
using p_tc_name.
field-symbols <tc> type cxtab_control. "Table control
assign (p_tc_name) to <tc>.
insert 100 lines in table control
<tc>-lines = 100.
Field symbols allow you to:
** Assign an alias to a data object(for example, a shortened
 name for data objects structured through several hierarchies
 - <fs>-f instead of rec1-rec2-rec3-f)
** Set the offset and length for a string variably at runtime
** Set a pointer to a data object that you determine at runtime (dynamic ASSIGN)
** Adopt or change the type of a field dynamically at runtime
** Access components of a structure
** (from Release 4.5A) Point to lines of an internal table
 (process internal tables without a separate work area)
Field symbols in ABAP are similar to pointers in other programming
languages. However, pointers (as used in PASCAL or C) differ from ABAP
field symbols in their reference syntax.
The statement ASSIGN f to <fs> assigns the field f to field
symbol <fs>. The field symbol <fs> then "points" to the
contents of field f at runtime. This means that all changes to the
contents of f are visible in <fs> and vice versa. You declare
the field symbol <fs> using the statement FIELD-SYMBOLS: <fs>.
Reference syntax
Programming languages such as PASCAL and C use a dereferencing symbol
to indicate the difference between a reference and the object to which
it refers; so PASCAL would use p^ for a pointer instead of p, C would
use *p instead of p. ABAP does not have any such dereferencing symbol.
** In PASCAL or C, if you assign a pointer p1 to a pointer p2,
you force p1 to point to the object to which p2 refers (reference semantics).
** In ABAP, if you assign a field symbol <fs1> to a field
symbol <fs2>, <fs1> takes the value of the data object to
which <fs2> refers (value semantics).
** Field symbols in ABAP are always dereferenced, that is,
they always access the referenced data object. If you want to
change the reference yourself in ABAP, you can use the ASSIGN statement
to assign field symbol <fs1> to field symbol <fs2>.
Using field symbols
You declare field symbols using the FIELD-SYMBOLS statement.
They may be declared either with or without a specific type.
At runtime you assign a field to the field symbol using the ASSIGN
statement. All of the operations on the field symbol act on the field
assigned to it.
When you assign a field to an untyped field symbol, the field symbol
adopts the type of the field. If, on the other hand, you want to assign
a field to a typed field symbol, the type of the field and that of the
field symbol must be compatible.
A field symbol can point to any data object and from Release 4.5A,
they can also point to lines of internal tables.
The brackets (<>) are part of the syntax.
Use the expression <fs> IS ASSIGNED to find out whether the field
symbol <fs> is assigned to a field.
The statement UNASSIGN <fs> sets the field symbol <fs> so
that it points to nothing. The logical expression <fs>
IS ASSIGNED is then false. The corresponding negative expression
is IF NOT <fs> IS ASSIGNED.
An unassigned field symbol <fs> behaves as a constant with
type C(1) and initial value SPACE.
MOVE <fs>
TO dest Transfers the initial value SPACE to the variable dest
MOVE 'A' to <fs>
Not possible, since <fs> is a constant
(runtime error).
To lift a type restriction, use the CASTING addition in the
ASSIGN statement. The data object is then interpreted as though
it had the data type of the field symbol. You can also do this
with untyped field symbols using the CASTING TYPE <type> addition.
The danger with pointers is that they may point to invalid areas.
This danger is not so acute in ABAP, because the language does not
use address arithmetic (for example, in other languages, pointer p
might point to address 1024. After the statement p = p + 10, it would
point to the address 1034). However, the danger does still exist, and
memory protection violations lead to runtime errors.
A pointer in ABAP may not point beyond a segment boundary. ABAP does
not have one large address space, but rather a set of segments.
Each of the following has its own segment:
* All global data
* All local data
* Each table work area (TABLES)
* Each COMMON PART
You should only let field symbols move within an elementary field or
structure where ABAP allows you to assign both within the global data
and beyond a field boundary.
Rgds
Umakanth

What are the differences between PD objects and PA objects?

can any one tell me What are the differences between PD objects and PA objects?

PA is based on Infotypes 0000-0999. PD is based on Infotypes 1000-1999, chief being Objects Infotype 1000. Objects Infotype is the source of different Object Types such as Person, Position, Org Unit etc. You can check that through transaction OOOT.
Regards
Lincoln

Differences Between Object And System Privileges

Hi,
Whats the difference between object and system privileges in oracle?
Cheers
Paul

System Privileges
A system privilege is the right to perform a particular action, or to perform an action on any schema objects of a particular type. For example, the privileges to create tablespaces and to delete the rows of any table in a database are system privileges.
Schema Object Privileges
A schema object privilege is a privilege or right to perform a particular action on a specific schema object:
For example, the privilege to delete rows from the departments table is an object privilege.
Some schema objects, such as clusters, indexes, triggers, and database links, do not have associated object privileges. Their use is controlled with system privileges. For example, to alter a cluster, a user must own the cluster or have the ALTER ANY CLUSTER system privilege.
A schema object and its synonym are equivalent with respect to privileges. That is, the object privileges granted for a table, view, sequence, procedure, function, or package apply whether referencing the base object by name or using a synonym.
Granting object privileges on a table, view, sequence, procedure, function, or package to a synonym for the object has the same effect as if no synonym were used. When a synonym is dropped, all grants for the underlying schema object remain in effect, even if the privileges were granted by specifying the dropped synonym.

Describe Object Type / Difference between desc & USER_TYPE_ATTRS ?

Similar Messages

Maybe you are looking for