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: 

Batch-Input data on function-pool dynpros

Former Member
0 Kudos

Hi All,

I want to call a transaction (e.g. SWI14) with skipping the first screen but setting values on it. Unfortunatly 'CALL TRANSACTION <tc> USING <bdcdata>' doesn't work, maybe because the underlying program is a function pool (e.g. SAPLSWI2)(?). The GET-Parameter is not defined in the dynpro definiton so SPA/GPA doesn't work either. Any ideas how to solve the problem without modifications?

Thanks in advance.

Gunnar

1 ACCEPTED SOLUTION

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

You should be able to do a BDC in mode 'E'. Just do the recording for SWI14, filling in your fields, and clicking execute. Calling transaction with mode 'E' will stop the program after clicking execute.

Doesn't matter that the program is a function pool.

I have done BDCs over transaction CO11N many times, no problems.

Regards,

Rich Heilman

4 REPLIES 4

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

You should be able to do a BDC in mode 'E'. Just do the recording for SWI14, filling in your fields, and clicking execute. Calling transaction with mode 'E' will stop the program after clicking execute.

Doesn't matter that the program is a function pool.

I have done BDCs over transaction CO11N many times, no problems.

Regards,

Rich Heilman

Former Member
0 Kudos

Hi Gunnar,

my advice is:- create a Z* transaction with parameters, which calls transaction SWI14. In the definition of the Z* transaction, fill the values for the fields on the first screen.

Please let us know if it helped. Best regards,

Alvaro

Former Member
0 Kudos

Thanks for the advices.

@Rich: Blinded by the fact that there is a function-pool I had overlooked to set the correct mode. Now it works.

@Alvara: The parameter transaction doesn't work, although all values and the flag 'Skip initial screen' is set. Maybe it does matter here that there is a dynpro instead of a selection screen behind the transaction because it works with a 'normal' transaction.

0 Kudos

Hello Gunnar,

You have been able to solve your problem, right? And it seems that Rich's answer was useful to you. Could you please reward him the appropriate points and close the thread?

Regards,

Anand Mandalika.