topic Re: ddic in Application Development and Automation Discussions

ddic

Former Member — Thu, 10 Aug 2006 06:21:12 GMT

1)In locking there is one type of lock called exclusive but not cumilative.wht do u mean by tht.

2)THERE are different ways to call a subroutine.Below are some of the ways.CAll By VALUE ,CALL BY REFERENCE AND CALL BY VALUE AND RESULT.Wht do u actually mean by this.

3)Wht do u mean by set parameter id and get parameter id.

Could anyoone explain this with a good example.

Re: ddic

dani_mn — Thu, 10 Aug 2006 06:28:07 GMT

HI,

CALL BY VALUE: in this case a local copy of the parameter is created for called function and changes make in the variable are local in function they will not change the actual variable.

CALL BY REFERENCE: The address of actual variable is passed to called function and changes made in function will change the actual variable.

CALL BY VALUE AND RESULT: Local copy will be made for the variable and at the end of called function the changed value will be written back to original variable.

SET/GET PARAMETER: used to write and read memory in SAP MEMORY AREA. sap memory is global area which can be shared between different session.

Regards,

HRA

Re: ddic

Former Member — Thu, 10 Aug 2006 06:29:18 GMT

Alex

Addressing your 3rd que>>>

Set parameter is storing the value for the screen field in a variable (parameter id).

Get parameter is used to retrieve the value from the variable (parameter id) to the screen field during runtime.

Perfect example would be .. as soon as you execute some t-code you ll find some fields populated automatically.. this cox of get parameter from your previous usage of the same t-code or related screenfield.

Reward points if it answers ur que..>

Regds

Karthick

Re: ddic

Former Member — Thu, 10 Aug 2006 06:30:46 GMT

go through this thread

http://help.sap.com/saphelp_47x200/helpdata/en/9f/db975c35c111d1829f0000e829fbfe/frameset.htm

kiran kumar

Re: ddic

former_member628175 — Thu, 10 Aug 2006 06:34:42 GMT

Hi Alex ,

Q1 :

Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. Each further lock request will be rejected.

Your rest of the questions has been answered above .

Hope this helps .

Thanks ,

Shounak M.

Re: ddic

Former Member — Thu, 10 Aug 2006 06:47:07 GMT

SAP Provide three type of Lock objects.

- Read Lock(Shared Locked) protects read access to an object. The read lock allows other transactions read access but not write access to the locked area of the table

- Write Lock(exclusive lock) protects write access to an object. The write lock allows other transactions neither read nor write access to the locked area of the table.

- Enhanced write lock (exclusive lock without cumulating)

works like a write lock except that the enhanced write lock also protects from further accesses from the same transaction.

Regards

Subbu

Re: ddic

sridharreddy_kondam — Thu, 10 Aug 2006 06:54:44 GMT

Hi Alex,

Exclusive but not cumulative lock

Exclusive locks can be requested by the same transaction more than once and handled successively, but an exclusive but not cumulative lock can only be requested once by a given transaction. All other lock requests are rejected.

SET PARAMETER ID <pid> FIELD <f>.

This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.

To read an SPA/GPA parameter, use:

GET PARAMETER ID <pid> FIELD <f>.

This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.

To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.

The relevant fields must each be linked to an SPA/GPA parameter.

EXample

REPORT BOOKINGS NO STANDARD PAGE HEADING.

TABLES SBOOK.

START-OF-SELECTION.

WRITE: 'Select a booking',

/ '----

SKIP.

GET SBOOK.

WRITE: SBOOK-CARRID, SBOOK-CONNID,

SBOOK-FLDATE, SBOOK-BOOKID.

HIDE: SBOOK-CARRID, SBOOK-CONNID,

SBOOK-FLDATE, SBOOK-BOOKID.

AT LINE-SELECTION.

SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,

'CON' FIELD SBOOK-CONNID,

'DAY' FIELD SBOOK-FLDATE,

'BOK' FIELD SBOOK-BOOKID.

CALL TRANSACTION 'BOOK'.

Check this link

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9e0435c111d1829f0000e829fbfe/content.htm

Regards,

Sridhar