Skip to Content
author's profile photo
Former Member

Advice required on what is possible - iViews, BAPIs, Java/ABAP

Hi All.

I have several theoretical questions, as we are at the planning/design stage for some future additions to our Enterprise Portal (EP).

We have 2004 Net Weaver EP version 6.0. We are using SAP R/3 4.7c.

Currently the only iViews and workflows we have deployed in the EP are the standard packages for ESS and MSS, for requesting and approving holidays, etc.

We know how to add basic 'SAP GUI transaction' style iViews via ITS with an 'R/3 look and feel' and 'R/3 as is functionality'. We don't know how to create/amend more sophisticated iViews, or even what standard tools are available to do this.

We would like to achieve the following:

- Enhanced/Amended look & feel in Portal iViews for standard transactions e.g. ME28 PO approval, ME2N list of POs, ME23 display PO.

- Action trigger driven changes to data (e.g. approve POs) in the R/3 backend, from web gui events (e.g. button click) in the Portal iViews

- We believe that we can achieve the former by writing and deploying our own custom iViews using Java or ABAP.

- We believe that we can achieve the latter by calling (in Java or ABAP) the standard BAPIs for Purchase Order reading/writing with parameters from our custom iViews.

We also understand that there are some standard packages out there (like those we used for ESS/MSS) that will achieve something similar. But suspect that the GUI and functionality are unlikely to meet our needs.

Is anybody able to confirm for us:

- Is this kind of functionality possible to achieve with our current Portal / R/3 set up?

- What standard tools (NetWeaver Visual Composer, Java Connectors, BAPI Connectors, Web Dynpro, etc.) are available to help us do this?

- Good sources of 'architecture overview' and 'specific how to' documentation for these tools? Have found a few so far that seem useful on sdn.sap.com and help.sap.com.

Sorry for a relatively vague and wide reaching post. Any help or advice that you can offer will be much appreciated. It is a new area for us and we are still learning.

Regards, Tom Cadmore.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Former Member
    Oct 16, 2007 at 02:24 PM

    Hi Thomas,

    Please find answers for your questions based on my experiences.

    -<b> Is this kind of functionality possible to achieve with our current Portal / R/3 set up?</b>

    Ans. You have different options ( technical) to develop iviews which can do same as your ME28 PO approval, ME2N list of POs, ME23 display PO transactions.

    First Option: Use JspDynpage (JSP + Htmlb) technology which can interact with SAP BAPI's from back end . ( this is out dated )

    Second Option: Use Webdynpro (Java webdynpro or ABAP webdynpro) technology which can interact with BAPI's from back end.

    My suggestion is to go for Webdynpro technology , b'z it is latest and all SAP developments are going to be in webdynpro

    With above two options you can archive good look and feel and easy navigation, custom design.

    <b>- What standard tools (NetWeaver Visual Composer, Java Connectors, BAPI Connectors, Web Dynpro, etc.) are available to help us do this?</b>

    (Ans) Tools required: you require Netweaver developper studio to create both Jspdynpage based applications and webdynpro based application. For ABAP webdynpro you need ABAP workbench.

    -Good sources of 'architecture overview' and 'specific how to' documentation for these tools? Have found a few so far that seem useful on sdn.sap.com and help.sap.com.

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e807d090-0201-0010-c785-f56cea815f7f

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Aravinda.

      Thanks for your feedback. Much appreciated.

      We are currently experimenting with SAP Visual Composer.

      We will also look at Netweaver developer studio and webdynpro in the near future.

      Thanks, Tom.