Skip to Content
avatar image
Former Member

Call FPM application from ABAP program through portal

Scenario - I have written report in ABAP and attached that report in Portal. The main functionality of this report is to open FPM application on click of e.g. on Requisition number to display the document.

Issue -

I am using CL_GUI_ALV_GRID class to display ALV. Now when I run report from portal and after click on one of the document number then my FPM application gets open properly. But when I am trying to open another document then I am not able to select that document. Nothing gets opened. It is working for first time only. I am using Google Crome brower.

Same thing working fine in IE but when FPM application gets open, some portion of my alv belomes blank as shown in below -

If I use List view then it is working fine for multiple documents across browsers. One more thing if I run same report in R/3 then the functionality is working fine for both list view and grid view.

Could you please tell me the reason behind this scenario happening in ALV grid ?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 10, 2017 at 09:33 AM

    IE screen after calling FPM application -

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 10, 2017 at 01:45 PM

    You are going from web to gui to web. Would it not make more sense to have the middle bit on the same platform?

    If you're not familiar with Web Dynpro, this sounds like a perfect justification to learn it.

    The ALV Grid is deprecated, and even SALV should only be used where you have a good reason to. From the docu on Classic Dynpro Programming:
    When user interfaces are created for new applications, Web Dynpro ABAP should be used instead of the classic UI technologies. If classic dynpros are still required, SAP List Viewer (ALV) should be used instead of classic lists.

    Add comment
    10|10000 characters needed characters exceeded

    • I'm sorry to say, but to me that just sound bad on so many levels...

      • Talk to your users, this sounds very much like a "because we've always done it this way" requirement. There are better alternatives.
      • Yes both are possible using WDA
      • Discuss this with your solutions/enterprise architects concerning standards. If users require a SAPGUI application then they should be using SAPGUI. If portal is a mandated technology then it should apply to all custom applications and WDA or other web technologies should be the standard and users should not get special treatment without good reason. It's just bad if one part of the company uses one standard and another is allowed to do their own thing. It just gets very very messy very quickly (as you are finding out).