cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Fiori GUI transactions - Automatic execution when passing parameters

pearlalex
Explorer
0 Kudos
4,493

Hi,

We are using SAP GUI for HTML in Fiori 2.0 and are passing/prefilling fields in a transaction via URL parameters. When we're passing parameters, the transaction automatically executes.

How can we pass url parameters without executing the transaction on startup?

I guess I have to set some parameters in the Target Mapping. Startup action can be set with the parameter DYNP_OKCODE. Setting this to false does not help.

Accepted Solutions (1)

Accepted Solutions (1)

alexey_arseniev
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Guys,

removing of the DYNP_OKCODE, in general, may help. But only if the target transaction is *NOT* an ABAP Report (Selection Screen transaction). If it is a selection screen app, the way to skip the initial screen is different from using DYNP_OKCODE and would be always executed as far as you pass ANY startup parameter. That is a limitation, no way to avoid now.

BR, Alexey

alexey_arseniev
Product and Topic Expert
Product and Topic Expert
0 Kudos

There is a solution, which may be OK as a workaround or test, but not to be delivered by SAP. It is calling of GUI Transaction using LPD_CUST (select this option in Target Mapping definition). In this case, it is possible to disable the option for skipping selection screen in LPD_CUST transaction settings. But the price you pay for use of LPD_CUST is performance lose, by FLP start, due to LPD_CUST data parsing.

Answers (3)

Answers (3)

0 Kudos

Hello @Alexander Schinnes

I have similar scenario. Are you able to read Fiori URL parameters and execute the transaction by using those parameter values? Please guide me how to achieve this.

former_member489109
Participant
0 Kudos

Hello @Alexander Schinnes

Did you find a solution?

kammaje_cis
Active Contributor
0 Kudos

What if you remove DYNP_OKCODE parameter itself?

pearlalex
Explorer
0 Kudos

Hi Krishna,

If I remove the DYNP_OKCODE parameter, it will still go to the next screen. I think parameter DYNP_OKCODE with value "/08" (F8/execute) is set as default, and that I have to turn this off in a way.