PCR Application - RFCs

Hi,
I opened the Webdynpro application mss/pcr and found 3 RFCs.
HRWPC_RFC_PCR_GET_SCENARIOS - returns the PCR scenario ids available for the user.
HRWPC_RFC_GET_OBJECTS (dunno what this is for)
ISR_LAUNCHPAD_SCENARIO_CHECK (dunno what this is for)
My Question is:
What are the above said RFCs for? Which RFC returns the adobe form? Could someone explain the application flow if possible?
Looking forward for replies.
Regards
Ak.
PS: Points assured for useful answers.

Hi Suresh,
I truely appreciate the effort you are putting to help me out in this.
I looked at the scenarios using t-code qisrscenario. there were lots but the scenarios which i need on the PCR application are only 5. One is standard (SPSD) the others are Zxxx. i could locate them there. i clicked on a scenario and tried to open the adobe form. but there was some problem with the layout editor of that form.
The FM - i coudn't understand the input parameters. I'm a WDP-Java resource. i can debug abad code to an extent. The Input for the FM looks like a structure. but i couldn't make out anything more than that.
You mentioned a view - how do i see it? i tried SE11 and the view parameter there. but such a view didn't exist.
Am i moving on the right direction?
Regards
Ak.
PS: Sorry for all the silly questions i asked above. But i'm new to HR-ABAP.

Similar Messages

MSS/ESS - PCR application

Hi all,
I'm new to the BP MSS/ESS and before make any change on WD applications, I would like to read your advices.
We need to create a validation on PCR(everytime a PCR is submitted several Infotype fields must be checked), where should I go for these changes? Straight on STD Web Dynpro application(in this case is MSS/PCR application) or is there a t table on SIMG_SPORT customization which I can provide this validation? How would you guys proceed on this case?
Thanks,
André

Hi Andre
This is part of the J2EE setup, you need to create an HTTP setup using Visual Administrator as described in the following link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/27098edb036025e10000000a422035/frameset.htm
Thanks
Michael

Adobe Exception when Opening Pcr Application in MSS

Hello,
We are on EP7.0 NW04s and when we try to open the Adobe form in MSS to make a Personnel Change Request we get the following exception:
com.tc.webdynpro.services.exceptions.PDFDocumentCreationException...
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.sal.deployment.api.WDDeploymentException: Failed to get deployable object part for application 'sap.com' of deployable object 'sap.com/mss~pcr'.
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getApplication(AbstractDeployableObject.java:158)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:408)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:344)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:145)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
... 17 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0010.20070424104658.0000 (release=NW04S_10_REL, buildtime=2007-04-24:09:31:29[UTC], changelist=25820, host=pwdfm114), build date: Thu May 10 17:29:41 CDT 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_US
Time of Failure Thu Oct 18 16:57:28 CDT 2007 (Java Time: 1192744648480)
Web Dynpro Code Generation Infos
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'sap.com/mss~pcr' and application 'sap.com' are not deployed on the server. Please check the used URL for typos.
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:410)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:344)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:145)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:174)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.services.sal.deployment.api.WDDeploymentException: Failed to get deployable object part for application 'sap.com' of deployable object 'sap.com/mss~pcr'.
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getApplication(AbstractDeployableObject.java:158)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:408)
... 20 more
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF
at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:392)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:887)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:728)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:663)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:78)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
I wonder for the cause for this as it was working earlier in the day.....
Ant help would be highly appreciated.
Message was edited by:
SubhashTripathi

Hello
Thanks for the reply guys. The ADS has been activated and was working earlier.....The Adobe Credential file exists at the path :
\usr\sap\*sys-id*\SYS\global\AdobeDocumentServices\TrustManagerService\trust\credentials which is a .pfx -file of type P12-record and which is valid till 2023. Do we still need to order the credentials....?
Looking forward to your reply.
Message was edited by:
SubhashTripathi

PDFDocument Exception in MSS-PCR

Hello ,
We are on EP7.0 and configured ADS server successfullt with our DEV and QAT system but the PCR application was working successfully in these systems...but now all of a sudden when we try to create a new PCR in QAT it blows with the following exception:
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/msspcr/PcrApplication/wd_key41_1194013279594/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=DefaultExternal1194012746990&sap-ext-sid=HG0eF8QM883ta%2B5igpTM2g%3D%3Dgn0nJ2IIuGlVKF5fdTKsJQ%3D%3D%2Fpcd%3Aportal_content%2Fcom.adc.root%2Fmgrtool%2Froles%2Fcom.adc.mgrtool.mgrtool_rl%2Fmss_ws%2FTest%2Fcom.sap.pct.erp.mss.pcrapplication_page%2Fsap.com%2Fmss%7Epcr%2FPcrApplication%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200702010738
    at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:379)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
    ... 41 more
See full exception chain for details.
Correction Hints
PDF Document Render Exception.
Please check the following:
Template file is not corrupted.
Data being passed is a vaild XML.
You have configured the web service client proxy properly.
Adobe Document Service (ADS) is configured properly (follow the configuration guide available at SAP service market place to check with all the supported configuration options).
If the problem still persists, report it to us. We need the following information to investigate the problem further:
Click here to download the error pdf that has been generated instead of the actual pdf. This is an important document to analyse the problem further.
Follow the steps below to get the system information where web dynpro is running:
Go to : http://host:port/sap/monitoring/SystemInfo
Log on as Administrator user.
Click on link all components... there. This will take you to the system information page that lists the version information of all the componenets installaed on your server.
Save this entire page (containing the version information of all the componenets installed on your server)
Follow SAP notes mentioned below to get the trace files for web dynpro and ADS. Then run your application again. Get the latest updated trace files from the server. If webdynpro and ADS are not running on the same server, then you need to turn on the tracer for the respective servers:
#742674 to turn on the web dynpro trace on the server where web dynpro is running.
#846610 to turn on the ADS trace on the server where ADS is running.
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:18:32[UTC], changelist=434634, host=pwdfm101), build date: Wed Apr 18 21:55:17 CDT 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_US
Time of Failure Fri Nov 02 09:21:19 CDT 2007 (Java Time: 1194013279625)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:392)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
     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:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:779)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:714)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:69)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1259)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:324)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:830)
     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:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/msspcr/PcrApplication/wd_key41_1194013279594/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=DefaultExternal1194012746990&sap-ext-sid=HG0eF8QM883ta%2B5igpTM2g%3D%3Dgn0nJ2IIuGlVKF5fdTKsJQ%3D%3D%2Fpcd%3Aportal_content%2Fcom.adc.root%2Fmgrtool%2Froles%2Fcom.adc.mgrtool.mgrtool_rl%2Fmss_ws%2FTest%2Fcom.sap.pct.erp.mss.pcrapplication_page%2Fsap.com%2Fmss%7Epcr%2FPcrApplication%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200702010738
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:379)
     ... 45 more
Although it is still working in DEV system.....Please help.
Any help would be highly appreciated.

Dear Raja,
I loggged into Visual Admin to change the value of sap.ADSCallingMode", from "http" to "soap. but that particular property is not maintained in the default property sheet in the following path
Server -> Services -> Configuration Adapter -> webdynpro -> sap.com -> tcwddispwda.
but you can see in the error trace i have given above that it is a SOAP based request. I am on EP 6 SP 9; will I have to upgrade or is it any other problem?
Regards,
Shyam

MSS Webdynpro Applications

Hello,
I am on EP7.0 and want to know the technical names of the webdynpro applications for MSS relating to PCR Status Overview,Reporting, Employee General Information and Time Approval...
Can any please help me with this..
Any help would be highly appreciated.

this is available on help.sap.com
refer <a href="http://help.sap.com/erp2005_ehp_02/helpdata/en/73/8eaf40a90c952ae10000000a155106/frameset.htm">leave approval</a>
There itself you can browse for name of WebDynpro applications...
for PCR application is sap.com/mss~pcr/PcrApplication
for PCR overview: sap.com/pcui_gp~isr/IsrStatusoverview
General information: sap.com/msseeproGeneralInformation
leave approval: sap.com/ess~lea/LeaveRequestApprover
Hope this helps,
Rgds

Webdynpro abap application for HCM

Dear all,
In enterprise portal->Content Administration->PortalContent->Content provided by SAP->line_manager->Manager Self-Service->iviews->HCM-> there is a PCR application by name "personnel change request". this is a webdynpro java application.
I have installed latest business package of ESS/MSS. so there should be both dynpro java and dynpro abap application. kindly tell me that for the personnel change request PCR application in which package can i find the wendynpro abap application.
Regards,
Bharath

Dear Bharath,
I am no expert on the topic but i can definitely answer your last question.
Yes, Webdynpro ABAP applications are available in the latest versions.I have seen this in ECC Enhancement Package 3 (ECC 603).
I can't really tell you much abt PCRs but the Requisition forms(SRQ3) in 603 are based on WDA application.If interested you can check the Recruitment work center in MSS.
Also, please ensure that the relevant Business Function/Services are activated when using the enhancement packages to see the relevant functionalities.
I think you need to activate the HCM administrative services BF available as of 602 . This definitely uses webdynpro ABAP applications in the portal.
Regards,
Sowmya
Edited by: Sowmya Kadambi on Dec 23, 2008 3:23 PM

Connect from SAP gateway to RFC server failed - Java StandAlone app X SAP RAC System

Dears,
I'm developing a Java application (RFC SERVER) with JCo3 and I need to connect to SAP RAC system.
I have configured the TCP/IP connection via transaction SM59, but when I try to start my server I face the error below (dev_jco_rfc.trc):
==========================================================================================
**** Error file opened at 20140714 112024 Brasilia Time Rel 3.0.10 (2013-08-08) [720.440]
Error: >Mon Jul 14 11:20:24,636<    RfcException: [null]
    message: Connect from SAP gateway to RFC server failed
Connection parameters: TYPE=A DEST=VSPAGUE ASHOST=cpe1601 SYSNR=01 SAPROUTER=/H/155.56.49.28 PCS=1
LOCATION    SAP-Gateway on host ld7624.dmzwdf.sap.corp / sapgw01
ERROR       hostname 'cpe1601' unknown
TIME        Mon Jul 14 16:20:25 2014
RELEASE     740
COMPONENT   NI (network interface)
VERSION     40
RC          -2
MODULE      /bas/740_REL/src/base/ni/nixxhl.cpp
LINE        193
DETAIL      NiHLGetNodeAddr: hostname cached as unknown
COUNTER     3
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
==========================================================================================
This problem happens when my app executes the line:
JCoServer myServer = JCoServerFactory.getServer(myServerName);
My system properties:
jco.client.lang=EN
jco.destination.peak_limit=10
jco.client.client=800
jco.client.passwd=********
jco.client.user=********
jco.client.sysnr=01
jco.destination.pool_capacity=3
jco.client.ashost=/H/155.56.49.28/H/cpe1601
jco.server.connection_count=3
jco.server.gwhost=/H/155.56.49.28/H/cpe1601
jco.server.progid=VSPAGUE
jco.server.gwserv=sapgw01
jco.server.repository_destination=VSPAGUE
Using SAP Logon i can connect to server cpe1601 system E16 without problems.
Please, I really need some help, because my knowledge on SAP platform is minimum.

Hi Markus,
Changing ASHOST=ld7624.dmzwdf.sap.corp as you have suggested, I got the error message: Connect to SAP gateway failed ...
As you could see, the host I'm connecting is from SAP RAC Service.
Here in our company we have only SAP Logon and my RFC Application, and I can connect to SAP remote system via SAP Logon with this settings:
System Connection Parameters
Description: SAP ECC 6.0
Application Server: cpe1601
Instance Number: 01
System ID: E16
SAProuter String: /H/155.56.49.28/H/
Below the connection information I received from SAP RAC SUPPORT for testing purposes:
    E16 System:
    SID: E16
    Client: 800
    System Number: 01
    Server: cpe1601
    Component Version: SAP ERP Central Component 6.0 Enhancement Pack 6 Suite on HANA
    User: ********
   Password: ********
   SAProuter String:
   If you don't plan to use SAPRouter at your end,
   /H/155.56.49.28/H/

Find Dependent DC's for PCR request in mss~pcr

Hi All,
Need help in finding the dependent DC's for mss~pcr application.
Why this becasue I need to check the code behind event the " Refresh" link in Create Application of Employee Change request.
Thanks
Gansa

Hi Gansa,
wrong forum!
this is Web Dynpro ABAP floorplan manager - not WD Java!
Suggest you search in WD Java forum, then if you don't find anything, post there!
Cheers,
Chris

WDP to RFC error...

Hi All,
I created a RFC which is working perfectly fine in R/3. But when i use the same from WDP application RFC is going into a dump.
Name of runtime error is : DBIF_RSQL_INVALID_CURSOR
Exception raised is : CX_SY_OPEN_SQL_DB
What i understood from the dump is that RFC could go into error while we debug it. But in my case we are not debugging it. And i have simply used a single select statement, then inserted some records in a custom DB table and then again a single select statement.
Please advice.

Hi,
Check if there are any active "External Breakpoints" in the RFC for the user with which you are running the WDP.
Regards,
Chen

MSS mySAP ERP 2004 - PCRs

Hi,
Has anybody used JSP PCRs in MSS version ERP 2004, instead of Adobe forms? We'd like to keep the same webdynpro screens to select forms but after form selection instead of opening adobe forms, it opens JSP forms. I am wondering if this is possible with configuration or we need to do some customization in web dynpro.

Hi Santhosh,
while MSS supports different UI technologies, one of the novelties of ERP 2004 is the use of an interactive PDF form as part of the PCR applications. If you wish to use and extend the processes and forms shipped by SAP, you need to install the NetWeaver infrastructure of Interactive Forms, in particular the server component 'Adobe document services'. Check the MSS/PCR installation documentation in Service Marketplace at http://service.sap.com/mss -> Documentation -> Personnel Change Requests.
Hope this helps.
Markus Meisl
SAP NetWeaver Product Management

RFC with CHANGING parameter

Hi All,
When creating an RFC, if i add a parameter in CHANGING tab, it is giving an Information message that `CHANGING is not allowed in RFC`. Is it true ?
If yes, that what is the alternative to pass a parameter which can be changed from SAP as well as the Other system using the RFC.
Thanks,
Best regards,
Prashant

Hi,
User enters MATNR on screen-other application, RFC is called. If field STATUS is blank(will be blank for 1st RFC call), then data would be validated and MATERIAL related data is sent back with value in STATUS as 01(success) else appropriate error message no. is sent.
Other application will check If STATUS NE 01, then error message description is fetched locally by the application and displayed on screen else the material related data is displayed on screen. User would click on confirm. Again the same BAPI would be called. If validations are fine, then COMMIT work would be done.
So the purpose is that, data is fetched in 1st RFC call and displayed on screen. Then user would click confirm and then same RFC would be called.
COMMIT WORK should not be executed for the 1st call to RFC but later it should be executed.
Best regards,
Prashant

App RFC Reader can't use

Hi
I use iphone4s ios5.1 ,download application RFC Reader but can't use
pleace check it

You can download directly from this page.
Adobe Reader is the only free PDF application available from Adobe - there are mobile versions for compatible devices, but no "lite" version.

SAP Web Service error text : The database returned a value containing an error , type CX_SY_OPEN_SQL_DB

Hello Guru's,
we are creating sales order in SAP from a quote created in .NET, through Web Service created in SAP, and consumed in .NET.
When ever a order is created in SAP for a given quote, SAP returns the sales order number to .NET.
Orders are getting created as expected, but once in a while we are getting the following error from webservice :
Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
But the problem is order is getting created in SAP for the perticular quote for which we are getting the above error and this order number is not getting returned to .NET.
Upon analysis in TCODE SRT_UTIL for the above transaction ID, has the following details , which are hardly help full to resolve the error.
----TYPE                                  CX_SY_OPEN_SQL_DB
----ERROR_TEXT                   The database returned a value containing an error
----CX_SY_NO_HANDLER
-----CLASSNAME                     CX_SY_OPEN_SQL_DB
This Exception raised by Web Service application
Could you please help in resolving this issue or alteast provide an approach for the same.
Thank you,
Suresh.

Thank you Bhaskar,
How can we clarify whether the error is from SAP or Web part.
I have checked ST22, but there is not entry for the perticular exception transaction ID
My exception time stamp is
-------------------START-------------6/9/2014 1:34:33 PM
Error :Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
-------------------END-------------6/9/2014 1:34:33 PM
In al11, i found the following for the perticular exception time stamp
**** Trace file opened at 20140609 133431 Eastern Daylight Time, by disp+work
**** Versions SAP-REL 720,0,500 RFC-VER U 3 1442251 MT-SL
XRFC> Begin of user trace
XRFC> ---------------------------------------------------------------------
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - header                                         <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> REQ_SIZE   : 2685                                                   <
XRFC> RESP_SIZE : 0                                                      <
XRFC> PARENT_ID : ROOT_CALL_ID                                           <
XRFC> TRC_KEY    : 40FCEFE3BD6EF184B5CE00155D0B4530                       <
XRFC> REQ_BASED :                                                        <
XRFC> SESSION_ID : 0003925540FCEFE3BD6EF17DB5CE00155D0B4530               <
XRFC> TS_CALL    : 20140609173408.2880000                                 <
XRFC> SY_UNAME   :                                            <
XRFC> HOSTNAME   :                                              <
XRFC> SY_SID     : PRD                                                    <
XRFC> SY_MANDT   : 300                                                    <
XRFC> SYS_NR     : 19                                                     <
XRFC> APPLSERVER :                                      <
XRFC> ISPRESCHED : X                                                      <
XRFC> DURATION   : 21810                                                  <
XRFC> NETHDRTIME : 21810                                                  <
XRFC> CALL_STATE : 2                                                      <
XRFC> ERRORTYPE : APPLFAIL                                               <
XRFC> ERRORAREA : APPL                                                   <
XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
XRFC> SYNC_ASYNC : S                                                      <
XRFC> LOCATION   : P                                                      <
XRFC> DIRECTION : I                                                      <
XRFC> REQ_ID     : 91C57815916E421CA9F3D652FFACE9C7                       <
XRFC> RESP_ID    : 00155D0B45301EE3BBFF89A0267EB5CE                       <
XRFC> MSG_STATE : 114                                                    <
XRFC> IF_NAME_I : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> IF_NS_E    : urn:sap-com:document:sap:soap:functions:mc-style       <
XRFC> IF_NAME_E : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> ISSHORTCUT :                                                        <
XRFC> TRC_PATT   : WSTEST                                                 <
XRFC> TRC_SSID   : PRD_19                                                 <
XRFC> TRC_USER   :                                           <
XRFC> TRC_TS     : 20140609173409                                         <
XRFC> TRC_COUNT : 99                                                     <
XRFC> TRC_EXT    :                                                        <
XRFC> COMPLETE   : OK                                                     <
XRFC> CALLEDPROG : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:rfc:710           <
XRFC> CONF_ID    : 00155D0B45301EE3AEFDAD78756555CE                       <
XRFC> BIND_ID    : 00155D0B45301EE3AEFDAD787565B5CE                       <
XRFC> OP_NAME    : ZsdCsCreateSalesorder                                  <
XRFC> COMM_PATRN : Method:ZsdCsCreateSalesorder                           <
XRFC> OP_NS      : urn:sap-com:document:sap:soap:functions:mc-style       <
XRFC> REMADDRESS : 172.16.11.43                                           <
XRFC> DT_OBJ     : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> MEMCONSUMP : 296291                                                 <
XRFC> WSHOST     :                                                        <
XRFC> WSPORT     :                                                        <
XRFC> WSPROT     :                                                        <
XRFC> WSCLIENT   :                                                        <
XRFC> WSPATH     :                                                        <
XRFC> PXYHOST    :                                                        <
XRFC> PXYPORT    :                                                        <
XRFC> USEDRFCDES :                                                        <
XRFC> BONAME     :                                                        <
XRFC> PROCCOMP   :                                                        <
XRFC> DEPLOYUNIT :                                                        <
XRFC> ------------------------------------------------------------------ <
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - trace records                                  <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING Exception handling for IF "ZSD_CS_CREATE       <
XRFC> _SALESORDER_SERVI" OP name "ZsdCsCreateSalesorder" MSG ID           <
XRFC> "91C57815916E421CA9F3D652FFACE9C7" user "STULZWEBSERV"              <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7240000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SOAP_ROOT : An exception has occurred. |    <
XRFC> program: CL_SOAP_RUNTIME_ROOT==========CP include: CL_SOAP          <
XRFC> _RUNTIME_ROOT==========CM004 line: 120                              <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SY_NO_HANDLER : An exception with the type <
XRFC> CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor    <
XRFC> declared in a RAISING clause | program: SAPLSTXD include: LSTXDFDB <
XRFC> line: 200                                                           <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SY_OPEN_SQL_DB : The database returned a    <
XRFC> value containing an error | program: SAPLSTXD include: LSTXDFDB     <
XRFC> line: 227                                                           <
XRFC>                                                                     <
XRFC> ---------------------------------------------------------------------
XRFC> End of user trace

Breakpoints not working when debugging OC4J web service

I am attempting to debug the PL/SQL web service autogenerated as part of the EMP_FETCHER tutorial example. My code has been compiled with debug information and the classes I wish to debug are not in my exclusions list.
When using the embedded OC4J container, I've verified that it is starting up in debug mode in the log. Setting breakpoints in the Emp_Fetcher class on the line commencing
__sJT_st = __sJT_ec.prepareOracleCall...
however seems to have no effect. Running my web service client does not cause the web service to stop on the selected breakpoint.
I've also tried remote debugging of the same web service on a separate database server. While I have been able to start OC4J on the server in debug mode, and connect to it from JDeveloper, setting of breakpoints seems to have no effect. I've monitored the TCP traffic on port 4000. It shows activity during the initial connection, but no traffic when I manipulate breakpoints in JDeveloper. I would have expected some traffic as breakpoints are added and removed.
Any assistance would be appreciated.
Regards
Michael

Hi Mithun Dha
I am facing same problem !
please let me know what is SICF user name and how to change it ?
I am using MSS PCR application (MSS role, Personal Change Request which is standard application on portal and it calls BADI at backend, it was working fine till yday suddenly its not stopping at the ext breakpoint in BADI)
thank you
b

Create web service for /POSDW/CREATE_TRANSACTIONS_EXT

Hello Experts,
In our POSDM implementation, we are trying to connect third party POS to POSDM via custom Middleware (.net application). I am trying to create a webservice for /POSDW/CREATE_TRANSACTIONS_EXT function module so that via middleware we can upload the T-log into POSDM.
While creating a web service we are getting an error "
SOAP application
"urn:sap-com:soap:runtime:application:rfc:710"
does not exist"
I have also checked the function module is RFC enabled. If anybody can put some light on how to solve this problem would be really appreciated.
Thanks
Mayank

Hi Mayank,
Use transaction ST22 in R3 (where you have created the RFC) and see what error has occoured. This will help you to solve your problem.
Since you got RFC_ERROR_SYSTEM_FAILURE exception, therefore have a look at the dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation.
Thanks and Regards,
Ramesh D

PCR Application - RFCs

Similar Messages

Maybe you are looking for