CALL transaction

[Former Member]

Hi All,

CALL TRANSACTION OPTIONS FROM opt ,

Can you plz explain

what for 1) RACOMMIT 2) NOBINPT stands in <b>Simple</b> Language.

I have checked help F1 but i am not able to get what exactly it is.

Thanks in advance,

Shital

Message was edited by:

shital phadake

[Former Member]

Hi,

A structure of the following type is used for Options in CALL TRANSACTION,

'CTU_PARAMS'.

Following are the fields in the Structure,

DISMODE UPDMODE CATTMODE DEFSIZE RACOMMIT NOBINPT NOBIEND

1. RACOMMIT field can be either 'SPACE'(default) or 'X'(means do not end transaction after COMMIT)

2. NOBINPT field also can be either 'SPACE'(default) or 'X'(There can be no Batch Processing).

The above structure needs to be populated before it is passed to CALL TRANSACTION. Please refer to the structure for more information on what values have to be provided to the fileds by forward navigatio.

Please let me know if you need any other information.

[Former Member]

RACOMMIT

Do not end transaction at COMMIT WORK

NOBINPT

No batch input mode (that is, SY-BINPT = SPACE)

NOBIEND

No batch input mode after the end of BDC data.

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

'X' Yes

' ' No

Reward if usefull..

[Former Member]

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

[Former Member]

Hi,

A structure of the following type is used for Options in CALL TRANSACTION,

'CTU_PARAMS'.

Following are the fields in the Structure,

DISMODE UPDMODE CATTMODE DEFSIZE RACOMMIT NOBINPT NOBIEND

1. RACOMMIT field can be either 'SPACE'(default) or 'X'(means do not end transaction after COMMIT)

2. NOBINPT field also can be either 'SPACE'(default) or 'X'(There can be no Batch Processing).

The above structure needs to be populated before it is passed to CALL TRANSACTION. Please refer to the structure for more information on what values have to be provided to the fileds by forward navigatio.

Please let me know if you need any other information.

[Former Member]

Can there be any effect of disabling NOBINPT on screen sequence of called transaction.

Thanks

[Former Member]

Hi shital,

1. Mostly, no.

2. In some cases, yes,

3. If the called transaction (program)

uses the variable sy-binpt

to decide some logic / some fields / some screen sequence,

Only then the behaviour will be different.

4. Most programs/transactions do not use

sy-binpt field to detect the running mode (online or batch input)

Hence, normally there is no need to use NOBINPT.

5. It the called transaction behaves different,

based upon sy-binpt,

then we can use

NOBINPT = 'X',

so that the system variable sy-binpt

will not be set to 'X'

and the called program will understand

that its a normal online transaction.

regards,

amit m.

[Former Member]

Last doubt

1) Batch mode processing means all the changes applied in a shot once we finish transaction, if anything update fail everything terminates

2) Online

as we process thru transaction it simultanouesly updates data

Is it correct???