Question Re: Auto generated fiori app for ECC transaction code in Technology Q&A

Auto generated fiori app for ECC transaction code

TMNielsen — Tue, 08 Dec 2020 15:31:29 GMT

I know nothing about Fiori so maybe the title of this thread is nonsense, but I hope my question will clarify.

I am ABAP developer and I have developed some classic transactions with dynpros.

Now some consultants are creating fiori apps on top of my transactions (I have no idea how).

It works in something they call Fiori launch pad. So far so good.

Now they want me to make a change in the the business logic, but these changes should not work if the transactions are called via SAPgui.

Can I in ABAP determine if a transaction is called from SAPGui or Fiori?

Re: Auto generated fiori app for ECC transaction code

Kevin_SAP — Tue, 08 Dec 2020 20:56:34 GMT

It sounds like they may be using SAP Personas to "Fiorize" Web Dynpro/GUI apps. I doubt if there is a way to monitor if the request came through Personas or Web GUI though. You can look at Personas here https://community.sap.com/topics/screen-personas.

Regards,

Kevin

Re: Auto generated fiori app for ECC transaction code

mail2guptar51 — Wed, 09 Dec 2020 17:08:58 GMT

Well. You can use SY-CPROG field to see who is the calling program. For Fiori Launchpad value will be "SAPMHTTP" and for GUI it will be different.

Cheers!

Re: Auto generated fiori app for ECC transaction code

former_member6508 — Wed, 09 Dec 2020 20:52:48 GMT

something like this?

https://answers.sap.com/questions/3989218/in-abap-if-we-came-in-from-bsp-or-sapgui-.html#:~:text=3%20Answers&text=You%20could%20check%20if%20the,background%20task%2C%20or%20WDA).

Re: Auto generated fiori app for ECC transaction code

TMNielsen — Thu, 10 Dec 2020 07:58:49 GMT

Thank you all for god suggestions. 🙂

I will do some tests and come back with results.

Re: Auto generated fiori app for ECC transaction code

gregorw — Fri, 11 Dec 2020 22:38:25 GMT

Hi Thomas,

can you please ask the other consultants what technology they are using to embedd your Transactions into the Fiori Launchpad? If they simply embedd them into the the Launchpad using SAP GUI for HTML (WebGUI) then I wonder why the business logic must be different. If they are building real Fiori apps using SAPUI5 and OData services I'm wondering if you provided them maybe function modules that they can use in newly generated OData services. There you might need some additional logic to avoid calling functionality that is only available in SAP GUI.

Best regards
Gregor

Re: Auto generated fiori app for ECC transaction code

OlegBash — Fri, 11 Dec 2020 22:43:21 GMT

You can create a Fiori Launchpad tile for tcode as described here

https://blogs.sap.com/2016/12/21/open-your-sap-gui-transaction-in-fiori-launchpad/

So in that case you will get your tcode in Launchpad. There are some limitations but mostly it would work as expected.

Re: Auto generated fiori app for ECC transaction code

TMNielsen — Mon, 14 Dec 2020 07:47:52 GMT

Hi Gregor

Yes this is WebGui, they add the transaction to Fiori Launchpad in a way similar to what is described in the link supplied by Oleg Baskatow (blog by Jerry Wang).

"Business Logic" may not be the exact description. My transactions are old RF transactions similar to the SAP standard LM* tranactions. They are programmed in a special way where some of the F-key have different meaning than in other transactions and many of the F-keys are also visible as a pushbutton on screen.

This is particularly a problem with the F3 button. If you, for example, in the entry screen to transaction LM05 press the F3 button, you will not just go back to where you called the transaction. LM transactions will always return to the LM menu (transaction LM01). This will also happen in browser (Fiori), but here they don't want to use the LM menu, So they want the F3 button to simly return the the Fiori Launch Pad. I hope I can achieve this by simply use "LEAVE TO SCREEN 0.".

But first I have to identify when to use "LEAVE TO SCREEN 0." and when to use original code.

And if "LEAVE TO SCREEN 0." doesn't bring them back to the Fioril Launchpad, the I will simply hide the F3 button, because they also have "Fiori back button".

Also we have another problem, but so far that is not my problem. When using Fiory Launchpad in this way, they want to control which transactions can be accessed via Fiori Launchpad by creating catalogs and roles, but so far I have easily succeeded in breaking out of the Fiori Launchpad to the WEBgui main menu giving med acces to all that is allowed according to authorisations.

Am I right to assume that the Fiori catalogs and roles are not a limitation of access, it its simply a tool to build a menu - similar to the old LM menu system

Best regards

Thomas

Re: Auto generated fiori app for ECC transaction code

TMNielsen — Tue, 15 Dec 2020 09:33:00 GMT

I just found that I need to correct the info I have given. The Apps in the Fiori Launchpad is not running WEBgui, but something called Slipstream, so I guess the answer from Kevin Bates is more accurate - the transactions are somehow "Fiorized" by Screen Personas Slipstream.

I have performed first test and can see that SY-CPROG is not the answer. With transaction LM05 started from Fiori Launchpad, the value is exactly the same as when started from SAPgui. (RLMOB001).

Next test was the function module GUI_IS_AVAILABLE. This also is not the answer. GUI_IS_AVAILABLE returns true in both Fiori Lanchpad and SAPgui scenario.

Further more my tests shows that the problem is not just with the special RF transaction LM*.

With all Slipstream Fiorized SAP standard transactions it is very easy to break out of the transaction and return to the SAP standard main menu instead of the Fiori Launchpad. In fact this will happen if I just leave the APP in peace and wait

So I wonder - is this just what we must expect from from a Slipstream setup or can we do better?