General

Former Member — Wed, 29 Aug 2007 02:48:09 GMT

Difference between these.

get parameter & set parameter,

get cursor & set cursor,

sap memory & abap memory.

How to give points to u tell the procedure to u .

plz give in the brief and send to my mail id is sathish23.kk@gmail.com

Regards ,

Sathish.

Re: General

Former Member — Wed, 29 Aug 2007 12:29:22 GMT

SET PARAMETER

SET PARAMETER ID pid FIELD dobj.

This statement sets the content of the SPA/GPA parameter specified in pid to the content of the data object dobj. For pid, a flat character-type field is expected that can contain a maximum of 20 characters, which cannot be exclusively blank characters. pid is case-sensitive. For dobj, a flat, (as of release 6.10 character-type) field is expected, whose binary content is transferred in an unconverted format.

If the SPA/GPA parameter specified for the current user in pid does not yet exist in the SAP memory, it is created. If the SPA/GPA parameter has already been created for the current user, its value is overwritten.

In a program, SPA/GPA parameters can only be created or assigned values if a name exists for them in the table TPARA. The extended program check reports an error if it can statically determine that a name specified in pid is not contained in the database table TPARA. ist.

For a SPA/GPA parameter specified in pid to match a name in the database table TPARA, it must be entered in upper case.

GET PARAMETER

GET PARAMETER ID pid FIELD dobj.

This statement sets the content of the data object dobj to the content of the SPA/GPA parameter specified in pid. pid must be a flat character-type field that contains no more than 20 characters and does not consist solely of blanks; it is also case-sensitive. dobj must be a flat and (as of Release 6.10) character-type field into which the binary content of the SPA/GPA parameter is transferred unconverted.

If the SPA/GPA parameter specified in pid was not yet created in the SAP Memory for the current user, the data object dobj is initialized and sy-subrc is set to 4.

In a program, only those SPA/GPA parameters can be read for which there is a name in the table TPARA. The extended program check reports an error, if it can be statically determined that an ID specified in pid is not in the table TPARA.

System fields

sy-subrc Meaning 0 The SPA/GPA parameter specified in pid exists for the current user in the SAP Memory and its value was transferred to the target field.

4 The SPA/GPA parameter specified in pid does not exist for the current user in the SAP Memory.

An SPA/GPA parameter that is readable with GET PARAMETER can previously have been created in the SAP Memory using the SET PARAMETER statement or automatically during the event PAI of a screen or selection screen.

For an SPA/GPA parameter specified in pid to match a name in the database table TPARA, it must be specified in uppercase.

SET CURSOR

SET CURSOR { { FIELD field [LINE line] [[DISPLAY] OFFSET off] }

| { col lin } }.

During PBO processing, this statement sets the cursor in the screen layout of the current screen. The cursor can be positioned by entering a screen element after FIELD or by entering a specific position using col and lin. Outside of PBO processing, the cursor is positioned in the next list displayed on the screen.

If the SET CURSOR statement is not specified, depending on the definition of the screen, the cursor is set according to the following hierarchy:

On the cursor position determined statically in the screen properties,

On the first input field of the screen,

On the first screen element of the screen,

On the input field in the system toolbar.

GET CURSOR

GET CURSOR { { FIELD field [field_properties] }

| { LINE line } }.

If this statement is specified during PAI processing, depending on the specification for FIELD or LINE, it transfers either the name of the screen element or the number of the row of a table control or of the group of a step loop (on which the screen cursor is positioned after a user action) into the data objects field or line. For field, a character-type (before Release 6.10 flat) variable is expected. For line, a variable of the type i is expected. In field_properties, further properties of the screen element can be defined.

If the cursor is in the input field of the standard toolbar or on a pushbutton in the screen, the statement is ignored and the specified variables remain unchanged. If the cursor in the first variant is not in a screen element of the current dynpro but on a bar in the GUI status, the contents of field and the variables specified in field_properties are initialized. If the cursor in the second variant is not on a screen element that is part of a table control or a step loop, the variable line is initialized.

System Fields

sy-subrc Meaning

0 The cursor is on a screen element of the current dynpro, if FIELD is specfieid, or on the input field of the standard toolbar. If LINE is specified, the cursor is on a screen element within a table control or a step loop.

4 If FIELD is specified, the cursor is on a toolbar in the GUI status or, if LINE is specified, the cursor is outside a table control or a step loop.

In the second variant, the same additions VALUE, LENGTH, and OFFSET could be specified after LINE as specified for the use of the statement for lists. However, the variables specified during PAI processing are always initialized.

ABAP Memory

Memory area within every main session, which the programs with the statements EXPORT and IMPORT can access. This memory area is maintained via a succession of program calls (call sequence).

SAP Memory

Memory area of application server, which all main sessions of a user session access jointly. ABAP programs have access to SPA/GPA parameters stored in the SAP memory.

reward if usefull

topic Re: General in Application Development and Automation Discussions

General

Re: General

Re: General