MSS Reporting Workset

Please could someone give me a list of all the standard reports (Not BI) contained in the MSS Reporting Workset.
Thanks!

Hi Bob,
Do you have the full path to your webgui service in your system's "ITS" settings in the portal? If so, try removing the /webgui/ from your system ITS Path and make it just "/scripts/wgate/"
Hope this helps.
Marty

Similar Messages

MSS Reporting Workset : Selection Criteria iview

Hi All,
We have a requirement to not allow the Selection Criteria iview of MSS Reporting workset to get displayed, when the user selects a specific report from Reports iview.
Any pointers regarding the issue would be of great help.
Thanks in advance,
Anupama

It is not possible to avoid the display of Selection Criteria view at the call of a report that is part of MSS Reporting Workset.
The report was called in different workset
Edited by: AnupamaD on Nov 22, 2010 11:19 AM

Using MSS Reporting Workset with SAP Queries

Hi,
we have created a number of SAP Queries and added them to the reporting tree shown in the MSS Reporting Workset.
We have created these queries to "Execute only with variant" and created the variant STANDARD for them to be run with.
If we then subsequently run the reports from the portal the variant is ignored. Does anyone know if this is the way it's supposed to work? and if there's a way to get the reporting workset to look at variants?
Many Thanks,
Paul

Which I agree with. I think it provides limited formatting feature. But in cases where you need ad-hoc report which needs minimal formatting. This is a good way.
Coming to Cross-tabs I noticed the difference here that. In OLAP Grid I got the hierarchy in a cross tab with expand and collapse feature.I am not able to do that in cross-tab. This is a kind of limitation for me as my requirements need that kind of a layout wherein you have a hierarchy in a cross-tab like layout. Is there a way that I can achieve that in cross-tab report using MDX.
Regards
Varun

: MSS 60.1.20 Reporting Workset

Please could someone give me a list of all the standard reports contained in the MSS Reporting Workset.
Thanks!

Hello Stuart,
The following link contains al the details about Report Workset of MSS.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/2f/d7844205625551e10000000a1550b0/frameset.htm -
> Click on "Workset Reports" from Left Hand bottom of the page.
Regards
Deb
[Reward Points for helpful answers]

MSS Reports

Hi Experts,
This query is regarding MSS reports. Initially we did not want all standard functionalities, so we deleted all iviews, worksets and assignment to roles.
Now we are implementing Report launchpad. I wanted to know if we have to reinstall Business package for MSS...since we have deleted standard functionalities.
Please let me know..
Thanks!

Swetha,
Only way you can get all those iviews is transport those iviews from other systems like QA ,Prodif they are already installed on them.
I suggest you create a copy of standard role and work on it
Thanks
Bala Duvvuri

Portal runtime error while trying to run a MSS report

Hello gurus!!
   I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
The trace file shows the following errors:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[17, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.16.trc]/>
<!NEXTFILE[defaultTrace.18.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
     at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
     at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
     at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 64 more
Could anybody please guide me how to fix this error and get the reports working properly?
Any help with this is much appreciated.
Thank you!
~Maria Kutty~

Hi,
Please refer to note 878440.
Thanks
Prashant

No reports displayed in MSS Report Launchpad

Hello everybody,
We set up ESS/MSS on a distributed environment.
Backend:
     ECC 6.0 EhP 3
     Single-ABAP Stack
     Installed Backend Component EA-HR 603
     Activated Backend Function EA_FIN_1
Portal:
     NW 7.0 SPS 17
     Single-Java Stack
     Installed Components: SAPPCUI_GP 603 SP4, SAP_ESS 603 SP3, SAP_MSS 600 SP15
Problem
The configuration works fine for a couple of ESS and MSS iViews and pages, but we get the following problem with MSS Reports:
-> When calling the Launchpad no reports are displayed and an info message is shown telling "No objects were personalized".
-> When clicking on "Change Launchpad" you see several reports sorted in groupings. They are already listed in the table of shown reports but are not displayed in the launchpad.
-> When clicking on "Save and Exit" you get two additional info messages telling "No Applications entered", but no reports are displayed. When you then open "change launchpad" screen again the reports totally disappear from table of shown reports.
Portal Launchpad Configuration:
-> pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.common
-> The launchpad iView connects to the backend via SSO which works fine for a lot of other ESS/MSS iViews
-> As application parameters the following is configured: "class=CL_FPB_SNI_ACCESS&role=MSS&instance=REP&display_external=X"
Backend Customization:
-> When launching transaction "fpb_launchpad_cust" with role MSS and instance REP you can see all the reports which are displayed in "change launchpad" screen.
-> All the reports are Transaction Reports
-> The Manager's Desktop (MDT) is not used
So:
1.) Why are the reports not displayed in the launchpad, but in the "Change Launchpad" screen?
2.) Did we forget any customizing?
3.) Why do we see such info messages like "No objects were personalized"?
4.) And what refers the application parameter "class=CL_FPB_SNI_ACCESS" to?
Please help me,
Dennis

Hi everybody,
finally we managed to fix this bug on our own.
We set up the Managers Desktop (MDT) as suggested by SAP. But the MDT's reports could not be converted to the launchpad.
Then we recognized via debugging that for any reason the following entries were missing in table FPB_LP6_SNI_REQ:
- Role ROLE C 3 MSS
- Instance INSTANCE C 3 REP
Adding these entries manually fixed the problem.
Regards,
Dennis Bohlmann

Customizing MSS reporting selection period dropdown list

We have diffrent ABAP programs that uses the PNP logical database and we want to customize the period selection dropdown list on the MSS reporting iview. In same scenarios we want to display only 'Today'. In these scenarios we use the report together with a variant.
When the user execute the report, the selection period on the variant is used and that is 100% correct. The problem is that the user change the selection period on the frontend (on the Iview) and this is not what is reflected on the output of the report, becasue the report uses a variant.
Therefore we want to customize the period selection dropdown list on the Iviewin the scenarios where a report uses a variant.
I know that we cannot customize the perido selction on the Iview, beacue we cannot set the properties on the Iview.
Is anybody familiar with how we can accomplish this.
Regards
Margariet
<< moved by moderator - check out the list of other forums on top of portal forum >>
http://forums.sdn.sap.com/thread.jspa?threadID=1239838&tstart=0
Edited by: Anja Engelhardt on Feb 9, 2012 11:42 AM

Hi Darren,
We do have a property in the iview for which you can set the period. You need to know the name of the property. Give us the iview name so that we can have a look.
Cheers,
Sathya

Error in MSS Report (Using MSS Reporting Launch Pad)

Hello,
I'm currently using the convert manager's desktop data to MSS report launch pad for the portal.
When trying to run the report in MSS, I'm getting the error below:
"Error in Manager Self Service. When calling the report, the following error occured. Error when executing query Z_ABCD." This is from an SAP Query report and I could not determine what caused this error.
Have anyone encounter this and if you are able to resolve it?
Any information would be greatly appreciated.
Thank you,
Tam Ly
County of Sacramento

hi,
Go to transaction RSCUSTV27 and check if any standard template is maintained.
Use
In this activity you can make the following settings (for systems with a Release higher than SAP BW 3.x):
You can set your own Web template as the standard Web template for ad hoc analysis.
You can set your own Web template as a standard Web template for BEx Broadcasting.
You can set a Web template that is used during BEx Broadcasting for queries for generating documents.
You can specify a Web template that is used during BEx Broadcasting for enterprise reports.
You can set your own Web template as a standard Web template for reports.
Standard settings
The delivered standard Web template (0ANALYSIS_PATTERN) is used for ad hoc analysis.
The delivered standard Web template 0BROADCASTING_TEMPLATE is used for BEx Broadcasting.
The delivered standard Web template 0QUERY_TEMPLATE_BROADCASTING70 is used for broadcasting queries.
The delivered standard Web template 0REPORT_TEMPLATE_BROADCASTING is used for broadcasting reports.
The delivered standard Web template 0REPORT_DEFAULT_TEMPLATE is used for executing enterprise reports.
Activities
To set your own Web template as a standard Web template for ad-hoc analysis, enter the technical name of the Web template under Ad-hoc Analysis. If you do not specify anything, the delivered standard Web template (0ANALYSIS_PATTERN) will be used for ad-hoc analysis.
To set your own Web template as a standard Web template for BEx Broadcasting, enter the technical name of the Web templates under Broadcasting.
To set your own Web template as a standard Web template for BEx Broadcasting for queries for the generation of documents, enter the technical name of the Web templates under Query Precalculation.
To set your own Web template as a standard Web template for reports, enter the technical name of the Web template under Enterpr. Reports.
Note that if you change settings, you have to restart the J2EE Engine before the changes become effective.
Regards,
Kams

No data found in MSS Reports.

Hi All,
I've configured the MSS business package in my EP.I've done all the required configuration to get it work.But in all my MSS reports it is showing "NO DATA FOUND".Even the employee search is showing the same message whereas in ESS the employee search and other views are showing proper data.
Can anyone suggest what could be the issue?
Your efforts would be rewarded.
Regards.

hi,
MSS now use Launchpad for reporting which u need to configure from the backend system.
You need to customise the Launchpad reportfrom the backend uding t-code FPB_LP_MSS_REP_CUST. this t-code will initialise ure Launchpad report. Check that table FPB_LP6_SNI is no
longer empty, and has the required entry. Then run the transaction to
convert.
Manually add the line to table FPB_LP6_SNI. The values are role = 'MSS', instance = 'REP', and sni_used = ' ' (blank). Then run the transaction to convert.
Also try to run run program #PWPC_CONV_MDT_TO_LPA# with type #RPT0#.
If you want only MDT report's...i.e only HR report..you can include Reporting iView from SAP provided content folder...this is standard iView which will display Manager Desktop.
Thnaks and Regards,
Jigar OZa

SSO for MSS Reporting doesn't work

Hello Experts!
I've a litte Problem: When a Portal-User (Manager) wants to call a Report from MSS Reporting, there comes a litte popup where he has to fill in his logon data for the HCM-System (target system).
I have already imported the certificates from Portal into the target system (Transaction strustsso2) as describes in this weblog (Connecting SAP systems to Enterprise portal with SSO.). The portal user and HCM-System user names are indentical, too.
do you have any suggestions?

Hi Matthias,
Let me know which version of MSS and HCM system are you using. I assume that your you are using saplogonticket in the system property.
Few questions:
- Is that appearing for all the screens or applications in MSS business package ?
- Are you using the standard SAP business package or have you customized it ?
- As mentioned in your message, you have imported the certificates but have you added them to ACL and set the value in 2 parameters login/create_sso2_ticket and login/accept_sso2_ticket and restarted the target system (HCM system) ?
Regards,
Sunil

Custom Reports in MSS Reports iView

I've looked all over for the answer to this. I've pulled a custom report through the MSS Reports iView, however, the selection criteria (personnel numbers and orgs) are not being passed. The custom rpt is being displayed at the selection screen for the custom rpt. Do I have to do something additional on the custom rpt, like remove the select screen? Is there something I'm missing in the config for the iView? Thanks!

check these links
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/88/266a3e54a2e946e10000000a114084/frameset.htm">Help link</a>
Hope this helps.
Warm regards,
Sudhir

Bypassing selection screen in custom reports added to MSS reporting

I have created a custom report (using PNP) in R/3 and added it to the MSS reporting (not Launchpad). Even though the manager is selecting his subordinate employee and clicks report result, he still sees a selection screen which i have defined in the custom report.
When the manager runs a sap standard report RPTABS50, he sees data of the employee only he selects.
How do i bypass the selection screen in the custom ABAP report i have added to the MSS?
Thanks.

Has to take an alternate approach. Picked a standard report by SAP and modified to our requirements.

Reg MSS Reports

Hi All,
I am trying to verify the MSS Reports from the portal side. When I click on the links in the reports (Employee Data -- Birthday List,Age/Gender etc......) I am able to get the selection screen pop up window with Launch Pad Reporting.
When I select the list and clicked on Report Result push Button getting the error as follow.
Reporting IAC
Portal Run Time Error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 08:34_25/09/10_0011_2097150
Refer to the log file for details about this exception.
I have followed the same steps mentioned in the link
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=199820849 provided by Siddartth Rajora.
Still getting the same problem.
Could any one please help on this.
Regards
KP

as i siad you arre not using RPTO scenario which is standard
or converted to LPTA
the issue is caused by the Report category
type. The Reporting Iview in the portal has the Report category type,
by default the report category type is set to "RPT0". Therefore, when
the application is launched, the reporting category type is also sent
as URL parameter to the backend system. As of ECC 6.0 only the reporting
category type "RPT0" is supported. There are two ways to handle this
issue, you can either changed the Iview property to "ZMSS" in the portal
, or Therefore the best option would be to change the report category to
"RPT0" in the backend system for all your reports.
check your scenario., read the wiki again as listed steps and spro to chekc this

MSS reports displaying Employee Information iView

Hi all,
I'm currently working on MSS project where I'm trying to show reports on MSS portal.
I have done the neccessary configurations regarding tables:
T77MWBS (Manager's Desktop Senarios)
T77MWBFCD (Function Code Definitions)
T77MWBFCO (Object-dependent Function Codes)
T77MWBFCH (Function Code Hierarchies)
and also converted MDT data to MSS Reporting Launch Pad using RPT0 senario.
The reports are showing in the MSS portal but when i click on for instance Birthdays, a new window pops up showing Launchpad for Reports page but I'm not able to define selection criteria i.e. select an employee from a list but instead I'm redirected to General Information page where General Data and Personal Data iViews are displayed. I clicked the Options button on the popup window to view Details and I'm able to see:
Portal Components: com.sap.portal.wdintegrator.WebDynproIntegratorPage
Object ID: pcd:portal_content/com.customer.customer_content/com.customer.customer/com.customer.roles/com.customer.mss/com.sap.pct.erp.mss.general_information
A theori i have is that Launchpad for Reports is redirecting me to General Information page and maybe the issue lies here. If that's the case, where do i change the pcd path to the correct Launch pad?
I'm missing some configuration but can't seem to figure out what.
Now, I'm hoping for you experts to guide me and show me the way to a successful and working portal solution.
Points will be rewarded to helpful answers.
Thanks in advance.
Regards,
Messay
Can somebody please help me with this issue, it's urgent!!
Edited by: Messay on Dec 1, 2011 11:09 AM

Hello,
Yes, you can build a WDA application to pick up the events from the WDJ application if and only if the events are portal events - quite a few of the WDJ apps actually share information through using a common component - not events.
I would also check however, that there is not an easier way of picking up which employee has been selected - you may be able to within the RFCs that are being called add an enhancement to export the selected person to a shared memory object, which could be read by the WDA component.
I've used this in the past to allow a WDA report to be launched from a WDJ application - taking the details of the selected item (in particular this was for WDA reporting on MSS ECM).
Not sure what you mean with respect to the eventing of the FPM.
You cannot include a WDA component as a Java FPM VC - so there is no way of having the WDA within your Java FPM application - events you raise to the FPM are only handled within the application.
An alternate approach is to use the OADP views for selection and configure the columns to have links that open new windows, use the proxy class of the HPF link to embed in each link the personnel number of the employee selected - pass this as a URL parameter to the new page, this can then be picked up by both WDA applications.
Hope this helps,
Cheers,
Chris

MSS Reporting Workset

Similar Messages

Maybe you are looking for