Application Development 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
Showing results for 
Search instead for 
Did you mean: 

Calling Bdc without pressing 'Enter' key in Transaction....

Former Member
0 Kudos

Hi all

I have got a requirement where i have call a transaction at the back ground without allowing the user to press enter key for the bdc ok code.

I have created the modulepool and also called the bdc to call transaction MB1B. But it is asking to press 'Enter' Key.

Is there any way that I can do so that the user should not press Enter Key.

Thanx in Advance.

Cheers

Christina

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi ,

what exactly u are going ? are u creating material document automatically of just u are taking users to MB1B screen ?

ucan use Call Transaction 'XXXX' skip first screen or

check the Mode of call transaction , Mode = E

The MODE addition determines the processing mode for batch input processing. As mode, you can specify a character-type data object. Its possible content and effect is displayed in the following table. Without use of one of the additions MODE or OPTIONS FROM, the effect is the same as if mode had the content "A".

mode Effect

"A" Processing with display of screens

"E" Display of screens only if an error occurs

"N" Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".

"P" Processing without display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger.

Others Like "A".

regards

Prabhu

4 REPLIES 4

Former Member
0 Kudos

Hi ,

what exactly u are going ? are u creating material document automatically of just u are taking users to MB1B screen ?

ucan use Call Transaction 'XXXX' skip first screen or

check the Mode of call transaction , Mode = E

The MODE addition determines the processing mode for batch input processing. As mode, you can specify a character-type data object. Its possible content and effect is displayed in the following table. Without use of one of the additions MODE or OPTIONS FROM, the effect is the same as if mode had the content "A".

mode Effect

"A" Processing with display of screens

"E" Display of screens only if an error occurs

"N" Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".

"P" Processing without display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger.

Others Like "A".

regards

Prabhu

former_member181995
Active Contributor
0 Kudos

call transaction MB1B skip first screen.

Amit.

rajesh_akarte2
Active Participant
0 Kudos

Hi ,

make the Mode of call transaction , Mode = N.

Regards,

Rajesh Akarte

Former Member
0 Kudos

Hi Christina,

U can go with follwing procedure>>>>>

1. Declare internal table <bdc_tab>.

2. Initialize the internal table before you call each new transaction.

3. At the beginning of each new screen, you must maintain the module pool name <program>, the screen number <dynpro> and a flag:

<bdc_tab>-PROGRAM = <program>.

<bdc_tab>-DYNPRO = <dynpro>.

<bdc_tab>-DYNBEGIN = 'X'.

APPEND <bdc_tab>.

4. For each field to which you want to assign values, insert an entry in the internal table. Specify the technical field name <fnam> and the field content <fval>:

<bdc_tab>-FNAM = <fnam>.

<bdc_tab>-FVAL = <fval>.

APPEND <bdc_tab>.

If the field is in a step loop or a table control, you must also specify the lines in which the input is to be entered. The field name extension displays the line number:

<bdc_tab>-FNAM = 'fieldx(5)'.

5. If you want to position the cursor on a particular field, enter the cursor position by filling field FNAM with the value BDC_CURSOR, and transferring into the field FVAL the technical name <tname> of the field where the cursor should be:

<bdc_tab>-FNAM = 'BDC_CURSOR'.

<bdc_tab>-FVAL = <tname>.

APPEND <bdc_tab>.

If you want to position the cursor on a field in a step loop or table control, you must also specify the lines in which the input is to be entered. The field name extension displays the line number:

<bdc_tab>-FVAL = 'fieldx(5)'.

6. Now specify which action is to be executed in this screen. You must determine the triggered function code <fcode> and assign this with the field FVAL. Note that the character '/' should always be placed before the function key number. The character '=' must be placed before all other function codes.

Assign value BDC_OKCODE to the field FNAM:

<bdc_tab>-FNAM = u2018BDC_OKCODEu2019.

<bdc_tab>-FVAL = <fcode>.

APPEND <bdc_tab>.

7. Execute steps 3 to 6 for each additional screen in the transaction.

8. After the last screen in the transaction, internal table <bdc_tab> is filled with all of the values required. You can now use this table to create an entry in a batch input session or to call the commands CALL TRANSACTION or CALL DIALOG.

The transaction to which a BDCDATA structure refers is identified separately. If your program writes data to a batch input session, then the transaction is specified in the call to the BDC_INSERT function module. This function module writes a BDCDATA structure out to the session. If your program processes data with CALL TRANSACTION USING, then the transaction is specified directly in this statement.

Hope this will help u.

Thnks

Anurodh