SAP Dynpro Automation

[nicolai.albrecht]

Hi together,

I’m currently automating some SAP transactions.
Unfortunately our current SAP Setup contains many Dynpro views and as well
nested Dynpros. When trying to create Element Selectors for items inside those
Dynpros, I can’t get any reliable results. Maybe someone of you encountered already
a similar problem and could share your solutions/ideas for this problem.

I already tried OCR or Image Recognition but since we use differenty SAP themes and
languanges this creates (unnecessarily) complex flows.

SAP Gui Version 740
Latest Studio

Thanks in advance for your help!

[LevKushnir]

Hi @nicolai.albrecht

Please be so kind and give me a few screenshots to understand, what you have in mind with “Dynpro Views” and “nested Dynpros”

Thanks, Lev

[nicolai.albrecht]

Hi @LevKushnir,

thanks for your quick response. Sure I can try to explain as good as possible,
tbh I’m not a SAP dev but I’ll try my best.

A Dynpro in SAP is a dynamic application inside an SAP Transaction. It is based on
an UI that is connected to an underlying ABAP code. In my project I need to check
and update information about new components for our product. Therefore we have
a Transaction that contains all information about the component, including the materials used for the component. To display the information from other transactions based on the information
I passed into the Transaction our SAP Devs created a Dynpro.

Now if I try to select a row in the table, the UI Explorer gives me the following result:

Unfortunatly without any controls or elements beside some containers.

Thanks a lot, Nico

[LevKushnir]

@nicolai.albrecht

This is an easy fix, follow the Docu and enable SAP scripting, than you would be able to automate any SAP element in SAP WinGUI in a proper way.

Configuration Steps

Best regards, Lev

[nicolai.albrecht]

@LevKushnir

I already followed the docs and just had a look at our setup and it is exactly as described.
Yet it is not working

[LevKushnir]

Hi @nicolai.albrecht

Please follow the docu and prove all steps! Not only scripting, but every single step.

In your case the issue can be here: Configuration Steps

Best regards, Lev

[nicolai.albrecht]

Hi @LevKushnir

I did follow and checke all steps. Everything is setup fine.

• Sever scripting is enabled (checked ALL variables, all are set to false)
• Client scripting is enabled
• Modals are enabled
• Highspeed connection is enabled
• Authorization Rights are not possible, since sapgui/user_scripting_per_user is set to false

I’ve already automated some other SAP Transactions without a problem, there the Studio gets
the correct selectors. Only the transactions that contain Dynpro interfaces are my problem, so
I’m pretty sure that is not a configuration issue.

Thanks a lot and best regards,
Nico

[LevKushnir]

@nicolai.albrecht

The correct SAP selector has SAP TAG inside (see bloew), on the screenshots above you see a lot of “AFX*”, it means the SAP scripting is not correctly enabled.

The right selector for the transaction is here.

SAP scripting allows the stable and reliable automation. We know everything about the elements on the screen such as SAP ID, column name, row number.

Please investigate further.

And I would check the authorization anyway

Best regards, Lev

[nicolai.albrecht]

@LevKushnir

Hmm ok, I will have a look at the authorization and will check the server configuration with our
SAP Administrator and will check the Dynpro stuff again with some SAP developer. Maybe there
is an implementation issue or something

Thanks again!

BR,
Nico