PDFObject Exception in MSS PCR Forms

Hi All,
I am running MSS 60.1 on EP 6 SP 9 with ECC 5.0 as the backend.
I am having an error with the Adobe based PCR Forms in MSS which goes like this:
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (302) Found.
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:201)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:142)
     at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:398)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:104)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1085)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:393)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
I have installed ADS with credentials and configured it as per SAP Note:813800 and the ADS Config Guide.I have created a User with Basic Authentication and I have created destination FP_ICF_DATA in Java Environment as well created User in ECC 5.0 and assigned SAP_BC_FP_ICF roles as well as activated neccessary paths.
When I test the service using the URL http://<host>:<port>/AdobeDocumentServices/Config (no data inout in the fields but only with User ID and Password); I get the same error as Invalid Response Code:302
Is there any other configuration or steps that I should follow. Has anyone faced the same Problem befoer. Kindly help.
Points will be awarded.
Thanks & Regards,
Shyam.

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

Similar Messages

  • How to add table data to an MSS PCR form?

    Hi All,
    I am new to Adobe Interactive Forms and I need to add a table of information to an existing form. This form is a customized version of an MSS PCR form Request for Termination. Currently the form fields are populated by an implementation of BADI QISR1. It is a copy of implementation HRWPC_PCR and uses the internal table special_data. All the fields currently on the form are single fields and I can see how they are populated. However I now want to add the contents of an internal table. I have read through the ISR cookbook but I cannot work out how to get this data onto the form and how or if it should be stored in the special_data table. The table (LOAN) has been added to the context and has 4 fields. Would anybody be able to provide some direction to me? Please let me know if I have not provided enough information.
    Thanks very much!
    Ashley

    Hello Ashley,
    you are already close to the solution. In BADI QISR1 you simply fill the
    table SPECIAL_DATA e.g.like
      fieldindex = 1
      fieldname = 'FIELD1'
      fieldvalue = 'Value1'
      fieldindex = <n>
      fieldname = 'FIELD1'
      fieldvalue = 'VALUE<n>'
    Then on the Adobe form layout (Adobe Designer), you have to use the table control XFO from the standard library. Here you have to bind then the corresponding column to FIELD1.
    Best regards,
    Simon

  • MSS PCR form

    Hi gurus,
    I am having problem with custom made PCR forms in MSS.We added fields for the PCR in MSS and implemented the BADI QISR1 to bring the values to the form.But when the user clicked on the review button the custom fields are not returning the data back to the BADI.I had already created the binding and everything in Adobe form.Please help me it's very urgent.
    we are in ECC 6.0 and using MSS 1.0 version.
    Thanks,
    Rao.

    Hi
    Did you get a chance to look at the OSS notes.
    Pl do reward, if helpful.
    Thanks
    Narasimha

  • MSS PCR form in german in production system

    Hi gurus,
    We are having a problem with the PCR Change Employee group and sub group.
    The adobe forms is coming out in English in both Development and Quality.But in production it's comin in german.We haven't changed anything in the form.But when we change it and transported it .Then also it's coming in english in Dev and Quality but in production it's still comin in german only.
    We are in ERP 2005 and we are using the MSS 1.0 BP.
    Any help is really appreciated.
    Thanks,
    Rao.

    Hi,
    Could you please let me know if you have resolved  it.
    I want to see the PCR forms in some local language. I am able to see the other contents in local language but not the PCR Form.
    Thanks
    Regards
    Santosh

  • MSS-PCR Forms Screen-shots

    Pls help.
    Anybody has MSS PCR Adobe forms screenshots? Pls send to me.
    Thanks in advance.
    Rick.

    can anyone help me .
    in mss -pcr i have requirement i have to show some zfields which are in infotype pa0002, in the pdf form.
    for this i have created a custom scenario, giving all the fields in the characterstics.
    now this form is called and showing all the fields...but the values are not there , can anybody help me how to populate the vlaues in some form fields and then update the infotype with the entered values in the form.
    thanks in advance

  • Adobe for MSS PCR forms with 46C back-end???

    Hi all,
    A quick question - is it possible to use Adobe document services for PCR forms when the back-end R/3 system is 4.6C? Or do we need to be on Enterprise or ERP?
    From what we've seen it appears that the ISR functionality in 46C is not enabled to allow selection of an Adobe form - thus ruling this form option out for 46C PCRs, meaning we'll use JSP forms instead.
    Can anyone confirm whether this is the case, and/or provide details of what they have done for PCR forms in 46C?
    (we do have a WAS 6.40)
    Many thanks
    Ross

    Hi Markus,
    Your response does not line up with information that I have found on SDN:
    10. Can Interactive Forms work within, for example, an SAP R/3 Enterprise or 4.6C system? Is it alternatively possible to run an external SAP Web Application Server 6.40 instance with a lower-release SAP system?
    Interactive Forms is shipped as a part of SAP Web AS 6.40. SAP Web AS 6.40 can be connected to lower-release backend systems to exchange data (using RFC).
    If you want to use forms in interactive scenarios, you can use technologies such as an RFC connection to exchange data between your application system (for example, SAP R/3 4.6C) and the SAP Web AS 6.40, which includes the required Adobe technology.
    If you are working with high-volume printing scenarios, consider that the customization of print forms is optimized for use within SAP applications.
    This means:
    ·At design time, you create relations between application data and form objects based on a common SAP dictionary.
    ·Form templates are available within their corresponding SAP applications. Templates are delivered by SAP only as part of an application.
    ·Performance is optimized for bundled systems, i.e. an SAP application system and its technological platform.
    SAP recommends that customers
    ·Use the same system for application and form printing services in high-volume scenarios
    ·Work with SAP-delivered form templates in the corresponding application. (If you use SAP NetWeaver for form printing services only, you will need to build your scenario from scratch.)
    Please note: If you are planning a high-volume printing project using SAP Web AS 6.40 and an existing, lower-release SAP solution, please turn to your SAP consulting contact for detailed guidance.
    If I am reading this correctly, you just need to install WAS 6.40 with the Adobe Services on it and then cerate an RFC to the 4.6 SAP system. Is this correct?
    Regards,
    Todd

  • 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

  • ESS/MSS PCR Forms Portal 7

    We plan on having a requisition form created which will have a number of fields including position and job information.  Once the requisition is approved, then the user can begin completing the new hire form.  When they come to the position field on the new hire form, can we default the position number entered on the requisition form?  Somehow we need to link the position number with the created requisition. 
    We were not sure you could pull data from one form to another or if everything has to come from the SAP backend.

    Hi
    Please search on SDN for integrating SRM, ESS/MSS in Portal.
    Regards
    Arun

  • MSS PCR form not pulling data for a user

    Hi All,
    On Organizational/Position Change Form(on Portal)  one of the user don't see the data in the dropdowns in this form.
    But for other users it is working just fine. The user not able to see the data in drop down can access other PCR's.
    I was wondering if there is a way we can test the form for the same user in the backend. If we can test him in the backend and the values are being populated for this user then there is a Portal problem.
    Can you please tell me how can we test this form for this user in the backend.
    Thanks in Advance,
    Joe

    hi ,
    You can put external breakpoint in the BADI method and try debugging it  by opening adobe form from
    portal.
    thanks ,
    sahiba

  • Custome MSS Webdynpro form and update & approvel process.

    Hi,
    I developed MSS form using Webdynpro Java and want to add the submit (not for actual update)  as well as approvel / rejection process.
    what is standard process is to route the PCR Notifications through the HR Administrator who will then process them in the backend, to facilitate any audits & validations before actual update.
    so where to store the data , before actual update? we i need to use xml ? how to get the notification no in this case ?
    is the are way to store data directly in r3. and get those data from iqs_special_data_get, if it is good practice.
    what is solution of my requirement, please guide me.
    Thanks
    Ali

    Hi  raza ,
       To study  the standard MSS PCR process , please study the development guide for PCR available at SAP
    Service marketplace .
                       Standard MSS PCR forms are designed at SFP in ABAP  and are processed through BADI QISR1.
    for PCR workflows refer -
    WS31000009 ISR_CONTROL
    WS31000010 ISR_APPROVE
    WS31000011 ISR_PROC
    I would suggest to study the standard process first before doing any customizing .
    Thanks,
    sahiba

  • MSS PCR --- PDF forms probmlem

    Hi.
       We are in the process implmenting ESS and MSS on EP NW04 SP11. We have installed Xss 7.0,  ESS/MSS business package   and ADS on Portal J2EE engine.
       After PCR configuration we got following error message while accessing forms.
    com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (302) Found.
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:268)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:209)
         at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:417)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:161)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1088)
    Did anyone have come accross this kind of problem ?
    Thank
    BD

    I checked the message with our Q team. This is probably not only related to Adobe document services, but involves the Portal or one of the other components of MSS PCR. Please create a customer message on the MSS PCR component to speed up resolution.
    Kind regards,
    Markus Meisl
    SAP NetWeaver Product Management

  • Adobe form MSS PCR senarios  not working with Portal SSL

    Hi All,
    we have implemented MSS PCR  senarios Nw04 with ERP2004 system.
    every thing is working fine when use http protocal for portal acess.
    Now we try to implement ssl for portal. so started implemnation and done in portal side, after that when try access any senario forms , The adobe form is not opening for editing, its throwing  error
    <b>The initial exception that caused the request to fail, was:
       java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:461)
        ... 47 more</b>
    its very urgent anybody can help out this, what settings ot be done on R/3 server and Portal and ADS server
    Thanks in advance
    Gopal

    Hello Gopal,
    You would only need an https connecion between the browser and the portal server if you are only concerned with the MSS applications. You need to have SSL configured from the portal to ADS server had you implemented some custom scenarios like certification, digital signature etc. But, considering your MSS issue, you do not need to worry about it untill and otherwise your landscape demands you to do so for any security reason.
    Well, you might have already gone through the following link, incase not, please go through the link to find out more on how to confugre SSL on the j2ee engine:
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm<a href="http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm</a>

  • PCR Forms not shown in MSS

    Hi All,
    We are on ESS webdynpro 600, EP 7.0, ECC 6.0 and trying to implement the PCRs (standard) in MSS.
    As per [this documentation|http://help.sap.com/saphelp_erp60_sp/helpdata/en/02/560f41ca73d349e10000000a1550b0/frameset.htm], we have configured the ADS with J2EE stack of Portal and tested the same from Portal using webservice navigator - it is successfull.
    However, it is giving the same error message as shown below :
    com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException
    The above error message is same for other E-recruitment applications which uses the Adobe forms.
    P.S : We have not done necessary configuration settings in ECC backend for connecting ECC ABAP system to ADS and Is it necessary to do this ? since, the Adobe forms are based on Java WD and will run on Webdynpro runtime of J2EE stack.
    When we run the report (FP_TEST_00) in backend, it gives the error message "http SOAP exception error" message - which reveals that the connection to ADS is not successfull. We have raised an OSS note with SAP and SAP has told that - since we are on X86 hardware platform where our ECC server is installed.
    Pls shade some light - how to run this PCR forms succesffully !!! I am I missing any steps ?
    Awaiting for your valuable inputs in advance.
    Regards,
    Anil Kumar.

    Hi Anil,
    It will be sufficient if you configure ADS on J2EE server only for Portal apps, no need for doing settings for ABAP .
    From the error it seems ADS is not working properly on the J2EE engine, try configuring & testing ADS using the guide below:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6
    Hope this helps!!
    Regards,
    Arafat

  • Unable to modify Adobe Forms for MSS-PCR

    Hi All,
    I have deployed the MSS BP on EP7.0.
    All the functionalities are working fine except the PCR forms. I have made the necessary configurations for ADS and also imported the ReaderRights credentials. I am also able to view the standard forms (transaction:SFP form:ISR_FORM_SPEG etc.) also I can see the forms from EP however, I am not able to make any field changes (eg. Date etc.) in the forms.
    Any idea what the reason could be?
    Thanks for the help,
    Rahul.

    I just wish I could give points to myself for this one. Found the solution in SAP Notes 1101340 & 955795...
    Cheers,
    Rahul.

  • 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

Maybe you are looking for