Skip to Content

SWFVISU question for approval step in MSS (JSP)

Dear all,

I am trying to set up PCR's with approval tasks. After sending the request a task has been created for the manager for approval (listed in UWL).

If the manager clicks on the task, the page crashes. I know I can define it with the SWFVISU transaction, but I don't know what to fill in.

Since it is JSP technology, I assume the view type is iVIEW. For an iView there are two parameters to pass, the ID and the CONFIRM parameter. For the ID I have used:

Do you know if we need to set it up as an iVIEW type? If yes, what exactly do we need to fill in for ID and CONFIRM?

Kind regards,


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 07, 2004 at 03:18 PM

    Hi Noel,

    I have not tried the SWFVISU approach with the .jsp PCR forms (the PCRs predate the SWFVISU technique of launch customization), but from what I understand, you have to put the entire PCD path to the iView, not just the technical name in the ID field. This means, unfortunately, that with EP 6, since the isrdispatcher is a "utility" iView, which is to say that it was only ever a master iView in the EP 5 world without any assignment to a page, etc., that addressing it in this manner is not really possible. To see what I mean, go into the portal in the Content Admin workset and navigate down to the MSS iViews (non-ERP) Migrated Content -> EP 5.0 -> iViews -> Manager Self-Service: My Staff. Note that you cannot find the isrdispatcher. Nor can you see any of the forms, delivered or custom. However, if you select any iView, you can see the ID in the Quick Info pane below. This is the information that SWFVISU wants.

    If you are determined to go this route, you could try creating an iView based upon the isrdispatcher, then point the SWFVISU customizing at your custom iView. I imagine that this might work, but have never tried it.

    I would recommend instead that you go the route of a UWL override XML file as described in note 646601.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Noël Hendrikx

      Hi Noel,

      Yes the development guide is valid for all portal releases.

      In the guide, the syntax you refer to reflects the delivered .jsp files in the business package for MSS. If you take a look at any of the ISRMain.jsp files for standard PCRs, they will match the guide. The generated code from QISRSCENARIO is different, yes. Does this matter? Only in relative terms to your .jsp file. If you are copying code from delivered PCRs, then whenever you come across a statement which wishes to make use of the ISR resource bundle (texts mostly), then the name has to be consistent and you should either update the .jsp code or change the bean name.

      If you are developing custom PCRs which are somewhat close to standard SAP PCRs, you will probably by better off following the development guide and using the delivered PCR .par files as a basis for your development rather than using the generation capability of QISRSCANRIO.



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.