call a transaction code

[Former Member]

how to call a transaction code from within a abap program

[Former Member]

Hi,

ex:

CALL TRANSACTION 'SE38' USING BDCDATA MODE 'N'

MESSAGES INTO ITAB.

[Former Member]

Hi

Hope it will help you.

Pls reward if help.

WT IS CALL TRANSACTION METHOD? WT IS SYNTAX/PROCEDURE?

CALL TRANSACTION :

1. It is compatible for small amount of data only.

2. It process the data Synchronously. i.e., The data is updated

at the time of execution.

3. It updates data both Synchronously and Asynchronously. When

we use Synchronous mode, it always verify all the data updated

successfully in the database.

When we use Asynchronous mode, the system can not wait till

all the data updated in the database.

4. It can handle only one application at a time.

5. It does not have Log file, we need to design logfile explicitly

using BDCMSGCOLL stucture.

Syntax :

CALL TRANSACTION <T.Code> USING <BDCTAB> MODE <A/N/E> UPDATE <S/A>

MESSAGES INTO <BDCMSGCOLL Int.Table>

Parameter 1 : Transaction Code

Parameter 2 : It is name of BDCDATA table.

Parameter 3 : Specifying Mode in which you execute transaction.

A - All screen mode. All the screen of transaction

are displayed.

N - No screen mode. No screen is displayed when you

execute the transaction.

E - Error screen. Only those screens are displayed

where you have error record.

Parameter 4 : Specifying Update type by which data base table is

updated.

S - It is for Synchronous update in which if you

change data for one table then all the relacted

tables gets updated. And then sy-subrc is returned

i.e., sy-subrc is returned for once and all.

A - It is for Asynchronous update, when you change

data of one table, the sy-subrc is returned. And

then updation of other affected tables takes place

If system fails to update other tables still

sy-subrc returned is 0.

Parameter 5 : When you update database table, operation is either

successful or unsuccessful or operation is successful

with some warning. These messages are stored in

internal table which you specify along with MESSAGE

statement. This internal table should be declared like

BDCMSGCOLL structure.

Steps for CALL TRANSACTION Method :

1. Interanal table for the data (structure similler to local file)

2. BDCTAB like BDCDATA.

3. Use UPLOAD/WS_UPLOAD/GUI_UPLOAD or DATASETS for upload data from

local file to internal table (i.e. ITAB).

4. LOOP at Itab.

Populate BDCTAB table.

CALL TRANSACTION <T.Code> USING <BDCTAB> MODE <A/N/E>

UPDATE <S/A> MESSAGES INTO <BDCMSGCOLL Int.Table>

Refresh BDCTAB.

ENDLOOP.

[Former Member]

call transaction 'tcode name'.

ex.

call transaction 'SE38'.

[Former Member]

CALL TRANSACTION <transaction name>.

[Former Member]

Hi

Use 'CALL TRANSACTION' followed by the TCODE.

Eg. Call Transaction mm01.

Thanks & Regards

Haritha.

[Former Member]

hi,

When you use the LEAVE TO TRANSACTION '<T_CODE>' statement, the system terminates the current

program and starts the transaction with transaction code <T_CODE>. The statement is the equivalent of

entering /n<T_CODE> in the command field.

CALL TRANSACTION '<T_CODE>' allows you to insert an ABAP program with a transaction code into the

call chain.

To terminate an ABAP program, use the LEAVE PROGRAM statement. If the statement occurs in a

program that you called using CALL TRANSACTION '<T_CODE>' or SUBMIT <prog_name> AND

RETURN, the system resumes processing at the next statement after the call in the calling program. In all

other cases, the user returns to the application menu from which he or she started the program.

If you use the …AND SKIP FIRST SCREEN addition, the system does not display the screen contents of

the first screen in the transaction. However, it does process the flow logic.

If you started a transaction using CALL TRANSACTION that uses update techniques, you can use the

UPDATE… addition to specify the update technique (asynchronous (default), synchronous, or local) that

the program should use.

When you call a transaction using the statement CALL TRANSACTION '<T_CODE>' USING <bi_itab>…

you can run the transaction <T_CODE> using the values from <bi_itab> in the screen fields. The

internal table must have the structure bdcdata.

The MODE addition allows you to specify whether the screen contents should all be displayed ('A' - the

default setting), only when an error occurs ('E'), or not at all ('N'). You can use the MESSAGE INTO

<mess_itab> to specify an internal table into which any system messages should be written. The

internal table must have the structure bdcmsgcoll.

You can find out if the transaction was executed successfully from the system field

sy-subrc.

You might use this technique if

You are processing in the foreground, but the input fields have not been filled using GET parameters,

You want to process the transaction invisibly. In this case, you normally have to pass the function codes

in the table as well.

Hope this helps, Do reward.

[Former Member]

hi

hope it will work for u.

reward if help.

CALL TRANSACTION 'MB1B' USING BDCDATA MODE W_MODE UPDATE 'S'

[Former Member]

Hi

use this syntex to call transaction

CALL TRANSACTION <TCODE>

USING <BDCDATANAME>

MODE <N/A/E>

UPDATE <S/A>

MESSAGE <BDCMSGCOLL>.

in the above syntax provide transaction code and ur internal table BDCDATA structure

MODE is N - no screen mode i.e, noscreen is displayed when u excute the transaction

A - is all screen mode i.e, all the screens of the transaction are displayed

E - is error screen i.e, only those screens are displayed where in u have occured error

UPDATE S- synchronous update

A- asynchronous update

MESSAGE is used to catch the errors i.e, log display

reward if it is useful

thanks,

S.Gangi Reddy

[Former Member]

Hi,

Type CALL into your ABAP editor.

Place your cursor on the word CALL and press F1.

Select the CALL TRANSACTION documentation

Cheers,

Chaitanya