Skip to Content
author's profile photo Former Member
Former Member

unusual question


i have to develop a program where you can display and change some data in R/3. this program will be only called in enterprise portal 6.0.

my question:

should i develop this program as normal dynpro in se80 and integrate it after in the portal with a r/3 iview or

is it better to develop it directly in the portal or

can i develop a web service in r/3 which i call from the portal with an iview.

how is it usual?

if you prefer the second possibility, how can i do this?

(web dynpro, java iview, use the connector framework ...)

lots of possibilities?

can anybody help me????



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Mar 31, 2004 at 07:46 PM

    Hello Daniel,

    I think you should develop a RFC enabled Function Module which encapsulates the required functionality. For the frontend application I think that it depends on the know how you have.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 05, 2004 at 07:26 AM

    thanks for your answer.

    perhaps any other opinions?

    is it true that any development in the portal should be restricted to build the interface and connect to the back-end systems? the logic should always be developed in the concerning back-end systems.

    but why develop such special interfaces (dynpage with htmlb, jsp...) when it is much easier to create a R/3 iview with a wizard in the content studio or gui machine?

    can somebody give me a szenario where it is necessary to work with the pdk? i simply want to find in which cases to use the pdk.

    some other opinions would be great.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      why use the pdk:

      -can perform complex state based iviews (for example time writing system ++). especially if the do not connect to SAP or other well know backend system

      -client side scripting between iviews through epcm (or is this available in content studio gui machine)

      -Lots of code is written in java allready. Iviews provide an easy way to integrated them

      -when development on R/3 is restricted (usually much stricter change routines)

      -when you want to use advanced htmlb elements (tree view, tab view, table view, etc.)

      -Interaction with multiple systems at the same time

      -Interaction with portal services

      probably lots of other reasons as well, but a lot of it depends on your personal preferences

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.