Error in Claim Advances in ESS

In ESS claim advances application page the following error is appearing : Reimbursement Type Customizing missing . Can any body suggest the solution how to proceed. Is it because of HR configurations or ESS service pack issue...?
Please Help.

Hi Simon,
Thanks for the info. Can any body give the details of necessary HR configuration in SPRO for the Claim Advances.I read in one document that for Claim Advances application we require ECC stack 15 . Now in our system we installed the business package SAP_ESS 600 sp 13 . Can anybody give the info about ESS version required for the ECC 6.0 . Please Help.
By doing some configurations we resolved the Reimbursements error but If we try to create new claim and go to next page following error is coming :    
Number Range Customizing is not maintained
Can any body help. Thanks in advance.

Similar Messages

  • Problem in Claim Advances in ESS

    Hi All,
    When we are raising a Claim Advance request in ESS It is giving the msg Sent for approval. But It is not coming to Approver's Inbox (UWL). What might be the reason . Please help.
    Thanks,
    Punam

    Hi Anil,
    We implemented the BADI also and it is perfectly working and giving the approver name and determining the approver group also. Actually we could able to raise the Claim request successfully and it is generating the claim number also. If we run the HINUACRP report there item is also present with the status " To be approved " by the determined approver by BADI. the problem is it is not triggering the workflow and the item is not going to Approver's workflow inbox and UWL to get the approval screen. Can any body help about the workflow settings ,Agent list and Probable agent list settings needed for this.?
    Please help.
    Thanks in advance.

  • Reimbursement Module - Claims / Advances in ESS BP 1.41

    Dear All,
    I am trying to implement Advanced Claims through ESS. Please let me know what are the required configurations from R/3 side as well as the Portal side. I wud really appreciate if anyone could share some configuration doc on the same.
    I am using :
    NW Stack 7.01 SPS05, ESS 600 SP05, BP ERP 05 ESS 1.41 SP05, EHP 4

    Hi,
    I have configured advanced claims now and the same are available in ESS also. Now i am facing the following problem:
    The requestor is able to view his claims eligibility & create request for a claim type from ESS. here the request phase & status are changing from new to 'in-process' & 'Approved'. we are using the standard workflow WS18900023 for whijch we have maintained the task id also TS18900010. The problem that i am facing now is that the approval workflow is not getting triggered and the claim request is directly getting approved. please let me know if anyone knows where the problem lies or have faced a similar problem and found a work around.
    Thanks in advance.

  • "Number Range Customizing is not maintained" error in Claim Advances

    Hi All,
    If we try to create New claim in Claim Advances It is going to the next page but throwing the following error :
    Number Range Customizing is not maintained
    Please help.

    Hi,
    Do one thing
    goto tcode HRPBSIN_NMBRNG click up on Change intervals ...........
    Then maintan number range screen you will get
    over thre select "ADD Intervals"  then over thre you need to give the New intervl for number ranges ......
    give as "1     99999999999999999999"  then select "Insert" and "SAVE"
    And check the process again.

  • Claim advance request ESS - Attachments

    Hello experts
    Actually we are uploding documents/attachments from portal while raising claims in HR ..now the issue is that the documents are stored in SAP ECC database and client want to divert to Content server ...we are unable to know where the documents being stored in sap database any help
    Pls help me.
    We are using the Advanced Claim Std ESS functionality/iView
    also i spoke with our DMS guy he is saying he checked the DMS tables but the documents are not storing in those tables
    Regards
    Vijay

    Hi deepak,
    Thanks for your response, i have already gone through this BADI, but i want to store the attachments into Open text server. But this badi is used to store in DMS, can u pls provide the sample code for storing into third party server like Open text. I have gone through the sap note but didnt found the sample code.
    Regards,
    Tony.

  • Claim Advance Request  in "Critical Error"

    Hi all,
    i launched the "Claim Advance Request" content porvided by the SAP, i got this error
      Claim Advance Request  
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator. An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.in/com.sap.pct.erp.srvconfig.claim_advance_request/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.claimadvancerequest_in does not exist.
    An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.in/com.sap.pct.erp.srvconfig.claim_advance_request/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.claimadvancerequest_in does not exist.:
    com.sap.xss.config.FPMInconsistentObjectException: An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.in/com.sap.pct.erp.srvconfig.claim_advance_request/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.claimadvancerequest_in does not exist.
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:90)
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
         at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
         at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
         at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
         at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)
         at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)
         at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)
         at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
         at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:172)
         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:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         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:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1244)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:191)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         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:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         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(Compiled Code))
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    can you please give me any solution
    Thanks and Regards
    Dileep

    Dear Mr. Jwala, (MALYADRI JWALA G )
    You are liking each and every comment / post of mine.... thanks for that but still if you see the recent trends in SCN members are most concerned about their and other reputation (Points). Yesterday I have gone through few threads about the same issue (Refer below link) I hope you are a part of the same thread.
    http://scn.sap.com/thread/3438686
    Hence request you to attention here.
    Because Even I have raised many issues may be few of them (around 2 to 4) are answered by Self. I have marked them as correct answer. But I am sure I didn't get any marks for those. I don't even mind my point are ZERO or a CRORE I am confident that people in SCN will help us if our post/ thread is genuine if we maintain good relation with members till we maintain mutual respect.
    My intention was to inform the correct answer for the people who is facing the same problem.
    It literally took 2 years time and two implementations effort to reach my current status (466 points).
    Never mind I am here to learn, grow and to help others. I hope you can understand.
    Regards,
    Srikanth Naidu. Akula
    Message was edited by: Srikanth Naidu Akula

  • ESS Claim Advance Approval screen showing incomplete list of requests.

    Hi Friends,
    In ESS Claim Advance Approval screen we are facing this issue.
    When approver opens the screen for approving the request.
    The list of requests appear but its not the complete list.
    There are also 2 sucess messages that get displayed.
    112 records found for the selection
    Only 10 of 112 records loaded which meet the selection criteria
    Users are able to see the rest of the request at r/3,
    also if they approve the first 10 request then they are able to view the next slot of requests.
    Any guidance as where the configuration for this could be checked.
    Regards.
    Edited by: SAP Portal Deve on Sep 20, 2011 2:41 PM

    you mean number of requests in UWL?
    Please specify
    http://help.sap.com/saphelp_afs64/helpdata/en/56/15681955744ec8877931c56607ec35/frameset.htm
    Edited by: Siddharth Rajora on Sep 20, 2011 8:08 PM

  • Need to add extra Payment modes in Claim Advance Request

    Dear Friends,
    I need to add extra Payment modes such as Corporate Credit Card and Company Card options in Payment mode option dropdown list  in ESS Claim Advance Request against a Reimbursement type.
    Below is the original thread created by me with screen shot. As per group members suggestion diverting this query from Travel mgmt forum to SAP HCM Forum
    Need to add extra Payment modes in ESS Travel management against a Reimbursement type
    Expecting solutions from HCM Experts !!
    Regards,
    Nayak

    Dear Experts,
    Any suggestions?
    Regards,
    Nayak

  • Error in printing reimbursement formin ESS portal 7.3

    Hello Experts,
    We are using portal 7.3 version and SP7.users got the error when click on Reimbursement module-claims/advances,if they want to print reimbursement form  then the user click on Mobile bill reimbursement after user got the below error screen shot as shown below screen shot.
    Please help me on this issue.
    Thank you in advance.
    Thanks and Regards,
    Jyothi

    you need to install the ACF components in your system.
    check below OSS notes.
    766191 - Active
      Component Framework Installation
    1781943
      - SAP ACF Client:SAP ACF Client support to Adobe Reader XI
    1556628
      - SAP ACF: SAP ACF Client support to Adode Reader 10.
    1776752
      - Employee gets blank screen while printing the Income Tax Declaration form
      in Portal

  • RFC Call Error - from Portal End - For ESS Personal Information service

    Hi,
    I am getting "Syntax error in program SAPLHRXSS_PER_MAC                       ., error key: RFC_ERROR_SYSTEM_FAILURE  " error Message on the portal (ESS--->Personal Information Screen).
    When I did RFC trace analysis (using ST 22) this is what i get.
    Can you let me know what could be the issue.
    We are running HR Backend(Support Pack 15,ecc 5.0).
    Portal (EP 6.0 SP19, ESS 100 (SP 10)).
    Could you please let me know what could be the issue ?
    Syntax error in program "SAPLHRXSS_PER_MAC ".
         What happened?
              Error in ABAP application program.
              The current ABAP program "SAPMSSY1" had to be terminated because one of the
              statements could not be executed.
              This is probably due to an error in the ABAP program.
              In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred
              in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:
              "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
              Author and last person to change the Include are:
              Author "SAP "
              Last changed by "C5069405 "
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "SAPLHRXSS_PER_MAC ".
              You can also perform the syntax check from the ABAP/4 Editor.
              If the problem persists, proceed as follows:
              Print out the error message (using the "Print" function)
              and make a note of the actions and input that caused the
              error.
              To resolve the problem, contact your SAP system administrator.
              You can use transaction ST22 (ABAP Dump Analysis) to view and administer
               termination messages, especially those beyond their normal deletion
              date.
              is especially useful if you want to keep a particular message.
         Error analysis
              In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred:
              "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              If you cannot solve the problem yourself and you wish to send
              an error message to SAP, include the following documents:
              1. A printout of the problem description (short dump)
                 To obtain this, select in the current display "System->List->
                 Save->Local File (unconverted)".
              2. A suitable printout of the system log
                 To obtain this, call the system log through transaction SM21.
                 Limit the time interval to 10 minutes before and 5 minutes
                 after the short dump. In the display, then select the function
                 "System->List->Save->Local File (unconverted)".
              3. If the programs are your own programs or modified SAP programs,
                 supply the source code.
                 To do this, select the Editor function "Further Utilities->
                 Upload/Download->Download".
              4. Details regarding the conditions under which the error occurred
                 or which actions and input led to the error.
         System environment
              SAP Release.............. "640"
              Application server....... "srv006"
              Network address.......... "167.116.230.56"
              Operating system......... "HP-UX"
              Release.................. "B.11.11"
              Hardware type............ "9000/800"
              Character length......... 8 Bits
              Pointer length........... 64 Bits
              Work process number...... 1
              Short dump setting....... "full"
              Database server.......... "srv006"
              Database type............ "ORACLE"
              Database name............ "H81"
              Database owner........... "SAPR3"
              Character set............ "en_US.iso88591"
              SAP kernel............... "640"
              Created on............... "May 21 2006 20:29:01"
              Created in............... "HP-UX B.11.00 A 9000/800"
              Database version......... "OCI_920 "
              Patch level.............. "129"
              Patch text............... " "
              Supported environment....
              Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
               10.2.0.."
              SAP database version..... "640"
              Operating system......... "HP-UX B.11"
              Memory usage.............
              Roll..................... 16128
              EM....................... 4189928
              Heap..................... 0
              Page..................... 0
              MM Used.................. 629192
              MM Free.................. 3558216
              SAP Release.............. "640"
         User and Transaction
         Information on where terminated
              The termination occurred in the ABAP program "SAPMSSY1" in
               "REMOTE_FUNCTION_CALL".
              The main program was "SAPMSSY1 ".
              The termination occurred in line 68 of the source code of the (Include)
               program "SAPMSSY1"
              of the source code of program "SAPMSSY1" (when calling the editor 680).
         Source Code Extract
         Line     SourceCde
            38     
            39     module %_rfcdia_call output.
            40         "Do not display screen !
            41         call 'DY_INVISIBLE_SCREEN'.
            42         perform remote_function_diacall.
            43     endmodule.
            44     
            45     module %_cpic_start.
            46       if sy-xprog(4) = '%RFC'.
            47         perform remote_function_call using rfctype_external_cpic.
            48       else.
            49         call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
            50         perform cpic_call using convid.
            51       endif.
            52     endmodule.
            53     
            54     
            55     form cpic_call using convid type c.
            56       communication send id convid buffer header.
            57       if sy-subrc eq 0.
            58         perform (sy-xform) in program (sy-xprog).
            59       else.
            60         message a800.
            61       endif.
            62     endform.
            63     
            64     form remote_function_call using value(type).
            65       do.
            66     *   test if sy-xprog and sy-xform are set
            67     *   sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
         >>>>>         call 'RfcImport' id 'Type' field type.
            69         perform (sy-xform) in program (sy-xprog).
            70         rsyn >scont sysc 00011111 0.
            71       enddo.
            72     endform.
            73     
            74     form remote_function_diastart.
            75       do.
            76         call 'RfcImport' id 'Type' field rfctype_rfcdia.
            77         perform (sy-xform) in program (sy-xprog).
            78         "Parking position for next request
            79         rsyn >scont sysc 00011111 10.
            80         "ALternativ : Free mode
            81         "COMMIT WORK.
            82         "SYSTEM-CALL FREE MODE 0.
            83       enddo.
            84     endform.
            85     
            86     form remote_function_diacall.
            87         sy-xcode = '%_@no@'.
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     2
         SY-TABIX     0
         SY-DBCNT     0
         SY-FDPOS     0
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     CPIC and RFC Control
         SY-MSGTY     
         SY-MSGID     
         SY-MSGNO     000
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             2 FORM         SAPMSSY1                            SAPMSSY1                               68
               REMOTE_FUNCTION_CALL
             1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
               %_RFC_START
         Chosen variables
         Name
             Val.
         No.          2     Ty.      FORM
         Name      REMOTE_FUNCTION_CALL
         %_DUMMY$$
                 2222
                 0000
         SY-REPID
              SAPMSSY1
                 5454555322222222222222222222222222222222
                 310D339100000000000000000000000000000000
         SYST-REPID
              SAPMSSY1
                 5454555322222222222222222222222222222222
                 310D339100000000000000000000000000000000
         %_ARCHIVE
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         TYPE
              3
                 0000
                 0003
         SY-XPROG
              SAPLSYST
                 5454555522222222222222222222222222222222
                 310C393400000000000000000000000000000000
         SY-XFORM
              HRXSS_PER_CLEANUP
                 455555545544444552222222222222
                 82833F052F3C51E500000000000000
         %_SPACE
                 2
                 0
         No.          1     Ty.      MODULE (PBO)
         Name      %_RFC_START
         %_PRINT
                  000                                                                                0 ##
                 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         RFCTYPE_INTERNAL
              3
                 0000
                 0003
         Internal notes
              The termination occurred in the function "ab_genprog" of the SAP
              Basis System, specifically in line 1374 of the module
               "//bas/640_REL/src/krn/runt/abgen.c#10".
              The internal operation just processed is "CALY".
              The internal session was started at 20070502223335.
              Program name.........: "SAPLHRXSS_PER_MAC ".
              Error message........: "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown.".
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         ( 0)  0x40000000016d6a8c   CTrcStack2 + 0x2bc  [dw.sapH81_DVEBMGS33]
         ( 1)  0x40000000016d67c0   CTrcStack + 0x18  [dw.sapH81_DVEBMGS33]
         ( 2)  0x4000000001d41438   rabax_CStackSave__Fv + 0x100  [dw.sapH81_DVEBMGS33]
         ( 3)  0x4000000001d4dbf8   ab_rabax + 0x1f68  [dw.sapH81_DVEBMGS33]
         ( 4)  0x40000000018cc09c   ab_genprog__FPcPvUii + 0xdbc  [dw.sapH81_DVEBMGS33]
         ( 5)  0x4000000000d3b4cc   newload__FPcP13TmpSubpoolDirUi + 0x29c  [dw.sapH81_DVEBMGS33]
         ( 6)  0x40000000016a7324   ab_LoadProg__FPcUi + 0xec  [dw.sapH81_DVEBMGS33]
         ( 7)  0x40000000016831fc   ab_link + 0x334  [dw.sapH81_DVEBMGS33]
         ( 8)  0x40000000015694d4   ab_rfcimport + 0xccc  [dw.sapH81_DVEBMGS33]
         ( 9)  0x40000000018cff98   ab_jcaly__Fv + 0x598  [dw.sapH81_DVEBMGS33]
         (10)  0x4000000000f98df8   ab_extri__Fv + 0x17a0  [dw.sapH81_DVEBMGS33]
         (11)  0x40000000016ab2d8   ab_xevent__FPCc + 0x38  [dw.sapH81_DVEBMGS33]
         (12)  0x400000000189c9a8   ab_dstep + 0x120  [dw.sapH81_DVEBMGS33]
         (13)  0x4000000000ed4c00   dynpmcal + 0xd0  [dw.sapH81_DVEBMGS33]
         (14)  0x4000000000ed1554   dynppbo0 + 0x1e4  [dw.sapH81_DVEBMGS33]
         (15)  0x4000000000ed0af4   dynprctl + 0x43c  [dw.sapH81_DVEBMGS33]
         (16)  0x4000000000ecb7a0   dynpen00 + 0x2118  [dw.sapH81_DVEBMGS33]
         (17)  0x4000000000fa598c   Thdynpen00 + 0x6a4  [dw.sapH81_DVEBMGS33]
         (18)  0x4000000000fa49b8   TskhLoop + 0x50d8  [dw.sapH81_DVEBMGS33]
         (19)  0x4000000000f999f8   tskhstart + 0x1e0  [dw.sapH81_DVEBMGS33]
         (20)  0x4000000000d42194   DpMain + 0x484  [dw.sapH81_DVEBMGS33]
         (21)  0x400000000220d41c   nlsui_main + 0x14  [dw.sapH81_DVEBMGS33]
         (22)  0x4000000000992794   main + 0x14  [dw.sapH81_DVEBMGS33]
         (23)  0xc000000000020ab0   $START$ + 0xa0  [/usr/lib/pa20_64/dld.sl]
         List of ABAP programs affected
         Index     Ty.     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPMSSY1          0     06.11.2003     20:53:07         18432     E
              1     Prg     SAPLSYST          1     10.05.2006     09:57:38         30720     E
              2     Typ     SYST          0     04.12.2000     14:54:51         27648     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPMSSY1
         SYST            .  .            :  :          00002404
         ABAP Control Blocks (CONT)
         Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     SourceCde
           118     CLEA     00     0035                                   SAPMSSY1
           119     CLEA     00     0036                                   SAPMSSY1
           120     CLEA     00     0037                                   SAPMSSY1
           121     MESS     00     001C                                   SAPMSSY1
           122     ENDF     00     0000                                   SAPMSSY1
           123     -
         00     0000                                   SAPMSSY1
           124     PERP     00     0001                                   SAPMSSY1
           125     PERP     02     0000                                   SAPMSSY1
           126     WHIL     00     0002     0000     0000     0000     0000     0000     0000     SAPMSSY1
           130     WHIL     00     0003     0000     0000     0000     0000     0000     0000     SAPMSSY1
           134     BRAN     05     000E                                   SAPMSSY1
           135     CALY     00     0003     0038     002A     0005     002B     0000     0000     SAPMSSY1
         >>>>>     CALY     02     0000     0039     8000     0000     0000     0000     0000     SAPMSSY1
           143     xper     02     0000     0010     0011                         SAPMSSY1
           145     PERP     80     0000                                   SAPMSSY1
           146     SYSC     1F     0000                                   SAPMSSY1
           147     BRAX     00     FFEF                                   SAPMSSY1
           148     WHIL     00     0004     0000     0000     0000     0000     0000     0000     SAPMSSY1
           152     ENDF     00     0000                                   SAPMSSY1
           153     -
         00     0000                                   SAPMSSY1

    Hi,
    The error is occuring in the program file SAPLHRXSS_PER_MAC.
    In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred 
    in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:      
    "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."    
    Information on where terminated                                              
        The termination occurred in the ABAP program "SAPMSSY1" in               
         "REMOTE_FUNCTION_CALL".                                                 
        The main program was "SAPMSSY1 ".
    This place  where it has terminated is highlighted in bold letters.                                       
    form remote_function_call using value(type).   
      do.                                          
      test if sy-xprog and sy-xform are set      
      sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
    <b>    call 'RfcImport' id 'Type' field type.     </b>
        perform (sy-xform) in program (sy-xprog).  
        rsyn >scont sysc 00011111 0.               
      enddo.                                       
    endform.                                       
    Thanks,
    Manoj

  • 500 internal server error when using attendance in ESS

    Hi All,
    when the user clicks on attendance & its related activities in ESS, the following error is displaying frequently and after sometime it is working properly.  why it is giving error frequently and how to avoid this error permanently? 
    Related Activities
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    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.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    ... 69 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    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.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Tue Oct 16 13:15:01 BST 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en_GB
    Time of Failure Thu Jan 24 11:58:41 GMT 2008 (Java Time: 1201175921417)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to read deployment descriptor.
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:297)
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getPart(AbstractDeployableObject.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObjectPart(DeployableObjectFactory.java:113)
    at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObjectPart(WDDeployableObject.java:62)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:921)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createVACComponentUsage(FPMComponent.java:745)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:562)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
    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:429)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
    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:860)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
    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.doApplicationProcessing(ClientSession.java:723)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
    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.WDRuntimeException: Failed to find deployment descriptor '.\temp\webdynpro\public\sap.com\msseeproarchiveddocuments\webdynpro\portalapp.xml' on the file system. Please check if the application 'sap.com/msseeproarchiveddocuments' is deployed correctly.
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:278)
    at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:259)
    ... 58 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected IO exception on GET<sap.com/msseeproarchiveddocuments>
    at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:209)
    at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeploymentDescriptor(WebDynproRuntimeServiceImpl.java:354)
    at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:274)
    ... 59 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
    at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
    at com.sap.engine.services.webdynpro.PApplication.load(PApplication.java:142)
    at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:204)
    ... 61 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
    ... 65 more
    Thanks in advance,
    v

    Hi,
    We  were also having the same problem; but we couldnt find a specific solution for that problem.
    But when we upgraded the ESS support packages to SP13 for some other reason this issue was also got resolved.
    May be helpful i guess.
    Regards,
    Vijay

  • Error in Deployment of SAP ESS 100 SP16 ess/au/addr

    Hello Gurus
    Greetings !..
    I am trying to Deploy SAP ESS 100 SP16 for Netweaver 2004s using SDM but getting error while i deploy in the phase ess/au/addr.
    Please check for the log below if any one can helpout soon....
    May 22, 2007 10:16:50... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:16:50... Info: Finished successfully: development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'680352'/'0', grouped by
    May 22, 2007 10:16:50... Info: Starting to save the repository
    May 22, 2007 10:16:52... Info: Finished saving the repository
    May 22, 2007 10:17:04... Info: Starting: Update: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0' updates currently deployed development component 'ess/at/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'766644'/'0'.
    May 22, 2007 10:17:04... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\at\pdata\MAIN_xss04VAL_C\0\680388\sap.com_essatpdata.sda
    May 22, 2007 10:17:04... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:04... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Begin of log messages of the target system:
    07/05/22 22:17:04 - ***********************************************************
    07/05/22 22:17:04 - Start updating EAR file...
    07/05/22 22:17:04 - start-up mode is lazy
    07/05/22 22:17:04 - EAR file updated successfully for 78ms.
    07/05/22 22:17:04 - Start updating...
    07/05/22 22:17:04 - EAR file uploaded to server for 219ms.
    07/05/22 22:17:05 - Successfully updated. Update took 734ms.
    07/05/22 22:17:05 - Deploy Service status:
    07/05/22 22:17:05 - Application : sap.com/essatpdata
    07/05/22 22:17:05 -
    07/05/22 22:17:05 - sap.com/essatpdata - WEBDYNPRO
    07/05/22 22:17:05 - ***********************************************************
    May 22, 2007 10:17:06... Info: End of log messages of the target system.
    May 22, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Finished successfully: development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0', grouped by
    May 22, 2007 10:17:07... Info: Starting to save the repository
    May 22, 2007 10:17:08... Info: Finished saving the repository
    May 22, 2007 10:17:21... Info: Starting: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0' will be deployed.
    May 22, 2007 10:17:21... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\MAIN_xss04VAL_C\0\681439\sap.com_ess~au.sda
    May 22, 2007 10:17:21... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:21... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Begin of log messages of the target system:
    07/05/22 22:17:21 - ***********************************************************
    07/05/22 22:17:21 - Start updating EAR file...
    07/05/22 22:17:21 - start-up mode is lazy
    07/05/22 22:17:21 - EAR file updated successfully for 188ms.
    07/05/22 22:17:21 - Start deploying ...
    07/05/22 22:17:22 - EAR file uploaded to server for 859ms.
    07/05/22 22:17:24 - Successfully deployed. Deployment took 2547ms.
    07/05/22 22:17:24 - Application : sap.com/ess~au
    07/05/22 22:17:24 -
    07/05/22 22:17:24 - sap.com/ess~au - WEBDYNPRO
    07/05/22 22:17:24 - ***********************************************************
    May 22, 2007 10:17:25... Info: End of log messages of the target system.
    May 22, 2007 10:17:25... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Finished successfully: development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0'
    May 22, 2007 10:17:25... Info: Starting to save the repository
    May 22, 2007 10:17:27... Info: Finished saving the repository
    May 22, 2007 10:17:39... Info: Starting: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' will be deployed.
    May 22, 2007 10:17:39... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\addr\MAIN_xss04VAL_C\0\681471\sap.com_essauaddr.sda
    May 22, 2007 10:17:39... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:39... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Info: Begin of log messages of the target system:
    07/05/22 22:17:39 - ***********************************************************
    07/05/22 22:17:39 - Start updating EAR file...
    07/05/22 22:17:39 - start-up mode is lazy
    07/05/22 22:17:39 - EAR file updated successfully for 94ms.
    07/05/22 22:17:39 - Start deploying ...
    07/05/22 22:17:40 - EAR file uploaded to server for 297ms.
    07/05/22 22:17:40 - ERROR: Not deployed. Deploy Service returned ERROR:
    java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
    Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    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.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
    ... 10 more
    For detailed information see the log file of the Deploy Service.
    07/05/22 22:17:40 - ***********************************************************
    May 22, 2007 10:17:40... Info: End of log messages of the target system.
    May 22, 2007 10:17:40... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Error: Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
    Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    May 22, 2007 10:17:40... Info: Starting to save the repository
    May 22, 2007 10:17:42... Info: Finished saving the repository
    May 22, 2007 10:17:54... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0' will be deployed.
    May 22, 2007 10:17:54... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Failed deployment of SDAs:
    development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' : aborted
    Please, look at error logs above for more information!
    Hope for a prompt response.
    Reply awaited urgently....
    Thanks in Advance
    Thanks & Best Regards
    Ashish

    Hello Gerard Christopher
    Yes i got the problem solved, actually SAP ESS 600 & SAP MSS 600 are the component we have to use. As we were on WAS 7.00 and ERP 2005 so
    SAP ESS 600
    SAP MSS 600
    SAP PSS 600
    SAP ASR 600
    SAP PCUI_GP 600
    Try with this you will able to solve.
    Thanks & best Regards
    Ashish

  • Error in Claims Approval Process

    Hi,
    I Configured ESS.I applied LTA Claim through portal.It went fot the approval to the approver.It is there in Universal Worklist of Approver but when he clicks on it to approve instead of opening WebDynpro iView it is giving an error that
    "Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapLaunch
    Component Name : com.sap.portal.appintegrator.sap.Transaction
    Exception in SAP Application Integrator occured: Application URL ':///sap(ZT1PNE82WFJ4RFI5enRIVHA4QkdKU1NBLS1lVGtQN0pUVDNUYzgyUlgxbG5MNmxnLS0=)/bc/gui/sap/its/webgui' is not valid! Please check the protocol and host entries for system 'SAP_XSS_WebDynpro'..
    Exception id: 10:37_12/08/08_0021_3487950
    See the details for the exception ID in the log file"
    It seems that it is trying to execute in SAP Gui for Windows, we can solve this problem by going to that iview and by changing it to Gui for Windows instead of Gui for HTML but actually it should execute a WebDynpro iview where we can approve this claims.
    Please guide me with a solution.
    With Regards,
    Praveen

    Hi Ravi,
    Thnaks for your help.I will add this code and i will let you know.
    But the thing is recently 3 months back i implemented this ESS part in one server it is working fine.I'am able to apply Leave,Claims,Loan,travel from EP and the approver is able to approve the requests from UWL.When clicking on the Request in UWL it is launching a webdynpro iview and i'am able to perform the actions.
    Now i'am facing the problem and i hope i did the same config which i did previuosly.
    What would be the reason any Patch levels?
    Thanks and Regards,
    Praveen

  • Error in check in the ESS in the development Tab of CMS

    In our project ESS/MSS is already implemented.
    We are to chnge some iview so we have implemented NWDI and Under XSSTrack i have checked in all the below .sca file.
    SAPESSXX_0-20000512.sca (&#56256;&#56518; SAP ESS 600)
    SAPPCUIGPXX_0-20001215.sca (&#56256;&#56518; SAP PCUI GP 600)
    SAPMSSXX_0-20000503.sca (&#56256;&#56518; SAP MSS 600)
    SAPBUILDTXX_1-10003479.sca (&#56256;&#56518; DI BUILD TOOL 7.00)
    SAPJEEXX_0-10003469.sca (&#56256;&#56518; SAP J2EE ENGINE 7.00)
    SAPJTECHSXX_0-10003467.sca (&#56256;&#56518; SAP JAVA TECH SERVICES 7.00)
    But in development Tab when i tried to import the ESS 600.sca then I got the below error:
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/_comp/src/packages/com/sap/xss/hr/skl/confirmation/Confirmation.wdcontroller
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/_comp/src/packages/com/sap/xss/hr/skl/confirmation/Confirmation.wdcontroller.xlf
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/cfg/_comp/src/_pcd/fpmviews_0_cd25f497ff392fad4592bc42e7d7b580/fpmviews_0.ept
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/cfg/_comp/src/_pcd/fpmviews_0_cd25f497ff392fad4592bc42e7d7b580/fpmviews_0.xlf
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/cfg/_comp/src/_pcd/skillsapplication_7b1a5642a463464d9f6b688af449d38f/skillsapplication.ept
    Info:conflict: conflict in workspace XSSTrack/sap.com_SAP_ESS/dev/inactive: /dtr/ws/XSSTrack/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/skl/cfg/_comp/src/_pcd/skillsapplication_7b1a5642a463464d9f6b688af449d38f/skillsapplication.xlf
    Info:Check for conflicts in XSSTrack/sap.com_SAP_ESS/dev/inactive
    Please give me sol to resolve this issue.

    Hi Mangesh,
    I'm facing the same problem, could you please give us some further explanations?
    ->Files are on the same server
    ->Checkin always fails (RFC-Callback not allowed)
    ->online works always fine (sure: with gui-download instead of FTP->No probs)...
    Does it mean, i need a special Storage category? the one i have has the vault-Indicator...
    Thanks in advance for any information and greetings from France...
    Guillaume Delorme
    Edited by: Guillaume Delorme on May 5, 2010 10:15 AM

  • Error in Form16 taken through ESS.

    Experts,
    While accessing Form16 through ESS, system shows an error. The error key is as follows:
    Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE  
    I check the Java connections and its working fine and there is no problem with the display of salary statement in ESS.
    Expecting your valuable inputs.
    Thanks in advance!

    yes. I have checked ST22 and found the run time error. it shows as follows
    Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY0" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
        During background processing, the system attempted to send a
        screen to a user.
        Current screen: "SAPMSSY0 " 0120.
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DYNPRO_SEND_IN_BACKGROUND" " "
    "SAPMSSY0" or " "
    "SYSTEM-EXIT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    er the short dump. Then choose "System->List->Save->Local File
    converted)".
    If the problem occurs in a problem of your own or a modified SAP
    gram: The source code of the program
    In the editor, choose "Utilities->More
    lities->Upload/Download->Download".
    Details about the conditions under which the error occurred or which
    ions and input led to the error.

Maybe you are looking for