Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

re: ctu_parameters structure

Former Member

‎2005 Oct 13 7:14 AM

0 Likes
382

Hi,

what are the advantages we can get by using this ctu_parameters structure, if we use with call transaction. Please give clear details.

2 REPLIES 2
Read only

former_member225448
Participant

‎2005 Oct 13 12:26 PM

0 Likes
351

Hi Paluri,

by using <b>CTU_PARAMS</b> you are able to control, how the transaction is called.

DISMODE: A,E,N

and

UPDMODE: A,S,L

are as usual.

DEFSIZE if 'X': use standard screen size in BDC session, instead of the users current screen size.

RACOMMIT if 'X': do not end BDC after COMMIT WORK, which is the standard behaviour.

NOBINPT if 'X': do not set SY-BINPT flag, or in other words: don't tell the called transaction about BDC.

NOBIEND if 'X': reset SY-BINPT flag, if no more screen recorded. In combination with DISMODE 'E' you run some screens via BDC and then do the rest with normal user dialog.

If you find my answer useful, please don't forget the reward.

Regards,

Juergen

Read only

Former Member
In response to former_member225448

‎2005 Oct 13 12:34 PM

0 Likes
351

Hi,

You can set additional parameters which you cannot directly do in call transaction except DISMODE & UPDMODE. If you dont specify these parameters using CTU_PARAMS they take the default value. If you want to change any of these you should use CTU_PARAMS.

<b>DISMODE

Processing mode (comparable with the MODE addition)

UPDMODE

Update mode (comparable with the UPDATE addition)

CATTMODE

CATT mode (controlling a CATT procedure)

The CATT mode can have the following values:

' ' No CATT procedure active

'N' CATT procedure without single screen control

'A' CATT procedure with single screen control

DEFSIZE

Use standard window size

RACOMMIT

COMMIT WORK does not end CATT procedure

NOBINPT

No batch input mode, that s SY-BINPT = SPACE.

NOBIEND

No batch input mode after BDC data has been read

The components DEFSIZE , RACOMMIT, NOBINPT, NOBIEND always take the following values:

'X' Yes

' ' No

If the OPTIONS addition is omitted, the following settings are valid for the control parameters:

DISMODE from the MODE addition

UPDMODE

from the UPDATE addition

CATTMODE

No CATT procedure active

DEFSIZE

Do not use standard window size

RACOMMIT

COMMIT WORK ends procedure successfully

NOBINPT

Batch input mode, that is SY-BINPT =X.

NOBIEND

Batch input mode also active after BDC data has been read</b>

Cheers