Record Working time as a standalone system

Dear all,
we have a requirement of recording working times of employees through Portal (ESS) and approve working time. i checked the CATS (Configure ESS for Time Entry) and our requirement is similar to it  but in CATS i read " after its approved it is transferred/updated  to HR systems".  we dont want to update any existing systems (HR/MM/PS) the data should exist as a standalone and report will be generated on periodic basis without effecting any other systems. is there any possibility in CATS or ESS to achieve this.
Thanks,
mahesh.

CATS is standalone system!
If you dont want to update HR system just dont schedule CAT6 or Rptextpt and ensure CATS profile in CAC1 doenst have immediate transfer to HR checked!
Thats it! Data will remain in CATS alone only ie CATSDB, if you need to transfer we use transfer reports or CAC1 customisation!

Similar Messages

  • Record working times with CATS

    Hello experts,
    I am a beginner and I really need your help regarding this point. we want to start recording working times in our PPM system. In our system we have the integration of our  ERP system with CATS. We can easily registrate in ERP  working time on each personnel number, on a specific cost center for cProjects, on activity type special defined for each role. We also transfer this costs with resources to controlling - so, in ERP system everything works fine.
    But, when I go to PPM system - I'm lost. all that I maintained on ERP system is available on Accounting Tab in Detail Data -which is good. But, I am not able to see the confirmed work on task level, tab "Dates and work" (see screenshot attached). Do I miss some customizing? or how should I proceed in order that this field "confirmed work" to be filled with the data registrated on ERP?
    Thanks a lot!
    Best regards,
    Ruxandra P.

    Hello Cassoké,
    have you enabled CATS-integration with cProjects in customizing?
    1) Customizing CATS-Integration for your project type in PPM
    Checkbox "Time/Travel Expenses Rec. CATS/SRM/FIN". Setting up "Accounting Integration".
    2) Customizing CATS-Integration from CATS-profile-customizing
    For your CATS Data Entry Profil you have to select the Checkbox "From Project Assignment" to get your worklist populated from cProjects (task is released, person assigned to task, etc...)
    3) Only entries with status '30' from CATSDB will be transferred to DPR_CONF_LI by the report "DPR_CATS_CPR_TRANSF"
    4) And of course, don't forget to uncheck "Test" :-) when running "DPR_CATS_CPR_TRANSF".
    regards,
    Peter

  • Enhance legend in Record Working Time IView

    Hi,
    I am working on SAP NetWeaver Portal 7.0(Service Pack 4). New NetWeaver functionality in Record Working Time section(of ESS>Working time ) allows employees to enter their working times for different attendance/absence types showing different colours in calendar for Rejected and Not Released statuses. Now the requirement is to include one more colour to show the approved times in the calendar. Ie, Currently legend has two colors with text,  like  (  <Red box> Rejected           <Light Red box>  Not Released), now i have to add   ' <Green box>  Approve '  beside   'Not Released' text,    and if manager approves the time sheet then those dates will be displayed in green color.
    If any body worked on the similar type of requirement or having knowledge....please let me know how to achieve this req.
    Thanks in advance.

    HI,
    You need to implement BADI for this ..
    BADI name : "PT_ABS_REQ"
    In the BADI "PT_ABS_REQ" interface "IF_EX_PT_ABS_REQ" you can find the method
    "SET_CALENDAR_COLOR" in that you can set the colure for the Absent type ......
    Adjust Colors of Calendar and Team Calendar
    Functionality
    You can use this method to change the colors in the team calendar.
    In the standard system, the different statuses for requests have different colors. You can use this method to differentiate the colors of requests depending on the following aspects:
    Status of requests (status)
    Action that an employee has executed: new request, delete, change (UIA operation)
    Subtype of absence (SUBTY)
    Full-day or partial-day absence (BEGMT, where BEGMT = 0 signifies a full-day absence)
    Application mode ( mode). You specify the application mode in the Select Employees for the Team Calendar IMG activity.
    Color Display of Status of Leave Requests(COLORS_ACTIVE). You specify this status in the Specify How Leave Is Displayed and Default Values IMG activity.
    Available Colors
    You have a choice of 16 colors. The 16 colors are hard coded, that is, you cannot change them or add other ones.
    The available colors are stored with their RGB value as constants of the CL_PT_REQ_CONST class. Use these constants if you want to change the colors.
    Notes
    If you change the colors in the team calendar, you should also adapt the legend accordingly. You can use the Adjust Legend for Calendar and Team Calendar method to do so.
    Hope this work!!!

  • How to change colors for record working time calendar

    Hi,
    I would like to change the colors in the calendar displayed in record working time based on some conditions.
    How do i do that is there any BADI associated with that
    Thanks
    Bala Duvvuri

    Hi Bala ,
    Yes its possible to change that .
    You need to implement BADI for this ..
    BADI name : "PT_ABS_REQ"
    In the BADI "PT_ABS_REQ"   interface "IF_EX_PT_ABS_REQ" you can find the method
    "SET_CALENDAR_COLOR" in that you can set the colure for the Absent type ......
    Adjust Colors of Calendar and Team Calendar
    Functionality
    You can use this method to change the colors in the team calendar.
    In the standard system, the different statuses for requests have different colors. You can use this method to differentiate the colors of requests depending on the following aspects:
    Status of requests (status)
    Action that an employee has executed: new request, delete, change (UIA operation)
    Subtype of absence (SUBTY)
    Full-day or partial-day absence (BEGMT, where BEGMT = 0 signifies a full-day absence)
    Application mode ( mode). You specify the application mode in the Select Employees for the Team Calendar IMG activity.
    Color Display of Status of Leave Requests(COLORS_ACTIVE). You specify this status in the Specify How Leave Is Displayed and Default Values IMG activity.
    Available Colors
    You have a choice of 16 colors. The 16 colors are hard coded, that is, you cannot change them or add other ones.
    The available colors are stored with their RGB value as constants of the CL_PT_REQ_CONST class. Use these constants if you want to change the colors.
    Notes
    If you change the colors in the team calendar, you should also adapt the legend accordingly. You can use the Adjust Legend for Calendar and Team Calendar method to do so.
    Hope this work!!!

  • Enabling "Daily View" on Record Working Time iView

    My company uses ESS Portal - Record working Time screen.
    We only see Weekly view tab... is there a way to enable the Daily view tab...
    how do I go about changing the iView for Daily View... any help is appreciated... I am new to portals so I need expert advise on this..
    Thanks a lot

    HI,
    You need to implement BADI for this ..
    BADI name : "PT_ABS_REQ"
    In the BADI "PT_ABS_REQ" interface "IF_EX_PT_ABS_REQ" you can find the method
    "SET_CALENDAR_COLOR" in that you can set the colure for the Absent type ......
    Adjust Colors of Calendar and Team Calendar
    Functionality
    You can use this method to change the colors in the team calendar.
    In the standard system, the different statuses for requests have different colors. You can use this method to differentiate the colors of requests depending on the following aspects:
    Status of requests (status)
    Action that an employee has executed: new request, delete, change (UIA operation)
    Subtype of absence (SUBTY)
    Full-day or partial-day absence (BEGMT, where BEGMT = 0 signifies a full-day absence)
    Application mode ( mode). You specify the application mode in the Select Employees for the Team Calendar IMG activity.
    Color Display of Status of Leave Requests(COLORS_ACTIVE). You specify this status in the Specify How Leave Is Displayed and Default Values IMG activity.
    Available Colors
    You have a choice of 16 colors. The 16 colors are hard coded, that is, you cannot change them or add other ones.
    The available colors are stored with their RGB value as constants of the CL_PT_REQ_CONST class. Use these constants if you want to change the colors.
    Notes
    If you change the colors in the team calendar, you should also adapt the legend accordingly. You can use the Adjust Legend for Calendar and Team Calendar method to do so.
    Hope this work!!!

  • Issues in Recording working time

    Hi experts!
    I have a problem in Recording working time. It display "The attendance/absence type 99/0800 does not exist on 01.01.2009".
    Help me!
    Regards Huy!

    Hi,
    When you are applying att./absence in the master data, system is telling there is 0800 att/absence type with 99 psg .grouping.
    Which one you are applying whether absence or attendance.
    either it is absence , create one absence type 0800 with 99 psg. grouping
    either it is attendance, create one attendance type 0800 with 99 psg. grouping .
    After creation of 0800, assign the screen no, TC, couning rules.
    Then your problem will resolve.
    Regards
    Devi

  • How to implement Manager Selfservice - Recording Working Time - BP

    Hi!
    I would like to have a stepby step approach to implement business package for recording working time.
    What I need is the following information?
    1. Pre-requisites
    2. How to create the iview ?
    3. What R3 configurations need?
    you can email if you have good documentation on this to [email protected]
    Thank you
    Ramesh

    The primary limitation you will encounter when trying to do high speed
    digital I/O using your E-Series hardware is that the digital lines are
    all software timed.  This means that for each and every digital
    read it is necessary for your software to issue a command to your
    hardware, read a single point, then receive the response from the
    board.  This prevents you from performing digital operations at
    very high speed.  In general, I would say that 100 microseconds is
    a very good response using software-timed digital I/O on a Windows
    computer.
    It is difficult to make a good recommendation without more detail about
    what you are trying to do.  You may need to consider switching to
    a Real-Time operating system, or upgrading your DAQ hardware to a board
    that will allow you to time your digital acquisitions on the board
    itself.  These devices, such as the m-Series DAQ or the PCI-653x
    series, would allow you to use hardware triggers for your digital
    acquisitions, change detection, and buffered data acquisitions to
    reduce the software overhead involved in a rapid acquisition.

  • Dump in Record working time aplplication

    Hi,
    Getting dump as shown below in Record working time appli
    HRESS_C_CATS
    Category               ABAP Programming Error                                                      
    Runtime Errors         UNCAUGHT_EXCEPTION                                                          
    Except.                CX_SALV_WD_NC_PROGRAM_ERROR_UI                                              
    ABAP Program           CL_SALV_WD_C_TABLE============CP                                            
    Application Component  BC-WD-CMP-ALV                                                               
    Date and Time          09/01/2011 21:55:11
    Short text                                                                               
    An exception occurred that was not caught.                                                    
    What happened?                                                                               
    The exception 'CX_SALV_WD_NC_PROGRAM_ERROR_UI' was raised, but it was not                     
         caught anywhere along                                                                        
        the call hierarchy.                                                                               
    Since exceptions represent error situations and this error was not                            
        adequately responded to, the running ABAP program                                             
         'CL_SALV_WD_C_TABLE============CP' has to be                                                 
        terminated.                                                                               
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                        
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   
        at and manage termination messages, and you can also                                          
        keep them for a long time.

    Category               ABAP Programming Error
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_SALV_WD_NC_PROGRAM_ERROR_UI
    ABAP Program           CL_SALV_WD_C_TABLE============CP
    Application Component  BC-WD-CMP-ALV
    Date and Time          09/02/2011 04:31:37
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SALV_WD_NC_PROGRAM_ERROR_UI' was raised, but it was not
    caught anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SALV_WD_C_TABLE============CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SALV_WD_NC_PROGRAM_ERROR_UI', was
    not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Data no longer available when SALV_WD_TABLE GET_MODEL called
    How to correct 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:
    "UNCAUGHT_EXCEPTION" "CX_SALV_WD_NC_PROGRAM_ERROR_UI"
    "CL_SALV_WD_C_TABLE============CP" or "CL_SALV_WD_C_TABLE============CM01D"
    "IF_SALV_WD_COMP_TABLE_IF~GET_MODEL"
    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
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    Server-Side Connection Information
    Information on Caller of "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. " "
    Caller Port........... " "
    Universal Resource ID. "/sap/bc/webdynpro/sap/hress_a_cats_1"
    Program............. "CL_SALV_WD_C_TABLE============CP"
    Screen.............. "SAPMHTTP 0010"
    Screen Line......... 2
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. " "
    Caller Port........... " "
    Universal Resource Id. "/sap/bc/webdynpro/sap/hress_a_cats_1"

  • ESS Timesheet - Record Working Time application partialy in german

    I initially deployed the ESS BP and the Time Entry -> Record Working Time application was comming completely in english.
    Then I changed the JCO references of ess/cat DC to some other backend, still the app was english.
    When I changed the JCO reference back again this time the Record Working Time application was half in german langauge.Text on tab strip, all buttons are in german.
    I even changed ProjectProperties.wdproperties property masterLanguage="en", earlier this was masterLanguage="de"
    Still half the app is in german. I even deployed the standard ess/cat DC again still no luck.
    How do I make it english back and what is the reason for random behavior?
    Regards,
    Vishal

    Make sure you have no language set up with Jco connection
    it should be blank!
    Normally no language should be maintained for the above mentioned JCO's
    If you have maintained any language for the JCO's ,kindly put it
    blank.
    http://help.sap.
    com/saphelp_nw04/helpdata/en/49/e607426338da6fe10000000a1550b0/
    frameset.htm
    Please have a look at  the Note  947081
    this is how language are set
    the  hierarchy of what locale a component will be shown in the portal,
    will be :
    1)component- if he have a locale define
    2) portal mandatory locale -( that's what we suggest)
    3)user locale
    4)browser locale
    5)Portal default locale
    6) system locale

  • Print record working time

    I have configured record working time, everything looks EXCEPT there is no option to PRINT, how can we handle this ,
    Version ep7 sp13...
    Thanks in Advance.
    Gareth

    I did open a message with SAP regarding the missing print button and the fact that employee indicative data has also been removed from the time sheet in SAP's latest release.  After much back and forth, SAP has concluded that this is missing functionality and they directed me to the infamous Note 11.  Here is the text of Note 11 for anyone who may not be familiar with it:
    <i>Dear Customer,
    We regret to inform you that the function you require is not included in the SAP standard system.
    If you consider filing a development request, we recommend that you either contact your Customer Competence Center (CCC) or one of the User Groups to place a stronger emphasis on your request. A list of SAP User Groups is available at http://service.sap.com/communities.
    For more information, see http://service.sap.com/rollin.
    Best regards,
    SAP Active Global Support</i>
    There is a "print" option on the iView which, when enabled, opens a new window for printing purposes.  However, this provides a PageBuilder rendition of the timesheet which is not sized or oriented properly for printing.  The result, therefore, is basically a truncated screenshot.  Even after manually re-orienting the page to landscape, the timesheet is truncated so no hours show.
    I recommended to my client that a development request be filed.
    Another perspective that I have been told is that SAP's intent was to replace the Print Time Sheet functionality with the Time Statement functionality.  This did not come from SAP, however.
    In my opinion, this is an important feature that SAP should re-release as quickly as possible.

  • Record Working Time(WDJ) error

    Hi,
    I keep getting this "TARGET_HOURS_ERROR" error, when I access the ESS
    page in my Portal.. but if I fill the buffer by executing the
    READ_TARGET_HOURS Method of the Class CL_XSS_CAT_EMPLOYEE in the
    backend (in Test Mode) & then access the Record Working Time iView,
    the error is gone.. I'm not sure why the buffer isn't getting filled
    when I access the iView directly.The following is our system configuration..
    SAP_ABA - SAPKA70012
    SAP_BASIS - SAPKB70012
    PI_BASIS - SAPKIPYM01
    SAP_HR - SAPKE60018
    EA-HR - SAPKGPHD18
    SAPEP - NW04s SP13
    ESS - ERP1.0
    Any suggestions/experiences on this error pl?
    ~Suresh

    the WDJ appalication expects a months time when reading the Target Hours.. We had a User Exit to populate the time for only 14 days.. this was causing an exception in the backend whie reading the Target Hours.. Once the User Exit was deactivated, the iView came up as expected..
    Thanks to Sireesh ( SAP Development ) for identifying the issue..
    ~Suresh

  • Record working time in ESS window collapsed

    Dear all,
    after we implemented EHP6 in our environment we have a strange issue with the Record working time window in ESS portal.
    When a user log in to the portal and go the Record working time the record working time window initial state is collapsed. He need to expand the window manually (see the screenshot).
    Does anyone of you have / had same issue? Are you aware of any SAP notes we can consider to solve the issue?
    Everything is standard , nothing customized.
    Thank you
    Vladimir
    BR

    This is because end users do personalization in that page. In this case when they logon next time always it will display the based on his personalization in previous logon.
    You can clear all personalization's for users in System Administration tab
    Clear all personalization for users from System Administration in portal.
    System Administration -> Support
    -> PCD Tools
         -> Personalization Data Cleanup
    Here Remove personalization data of all users for all portal objects or specific to user / specific to portal object

  • Record Working Time Error on Portal

    Hi Experts,
    I am getting following error which try to do record working time from portal. Need your kind solution to resolve the issue..
    Thanks in advance.
    Errors:
    Record Working Time   
      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.
      The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE   
      The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:468)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:822)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
         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: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.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         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:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:730)
         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:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:180)
         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.aii.proxy.framework.core.BaseProxyException: The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:221)
         at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:468)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:822)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
         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: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.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         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:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:730)
         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:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:180)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Check transaction ST22 for exceptions/errors (that is usually the first place...thanks to Barin Desai for drilling that into my head long ago...haha...make sure you set the dates to check correctly). If nothing there (there should usually be with this kind of error), then also check your JCO connetions for the WebDynpro (you can do this in the portal or through Visual Admin but you will need J2EE admin permissions).

  • Extra fields in search help window in Record working time EHP5

    Hi Experts,
    Can you please let me know how to add additional fields/select options in search help window for Record Working Time ?
    My system is EHP5 NW 7.02
    I have added the custom search help for the respective filed in table " TCATS_SHLP_ITS".
    I can see this table is having entry for only 4 selection options and 6 value fields for search help display.
    But in my custom search help programme is having 8 select options(for advance search) and 10 display fields on the search window. It's working from CAT2 transaction but when I am running through webdynpro timesheet, I can only get 4 select options and 6 value fields.
    Please let me know how to make the other fields available.
    Thanks in advance.
    Sonia

    Hi Siddharth,
    Thanks for your response. In that modify possible entries screen (Details view) I can see the search help is only having 4 select options and 6 display fields.
    So as per my understanding max 6 display fields/4 select options can only be displayed on search window.
    My requirement is to display more fields on search help OVS window.
    Can you please suggest.
    Thanks ,
    Sonia

  • Record Working time issue

    We are facing issue in Record working time where there are users who belong to Org unit "70001573u201D. The chief position of org unit 70001573 is not occupied.
    70001573 Org units are belonging to Org unit 70001601 which is occupied by EMMA POWELL.
    So now the user whose belongs to 70001573 org unit, when they raise the record working time and release the same, Since 70001573 is not occupied by any person the request should go to Org Unit 70001601.
    Currently the system not functioning as per the said requirement.
    The user whose belong to 70001573 org unit, when they raise the record working time and release the same , the request not going any manager for the approval which shout not be case .
    We even though implement Note 595073 - Workflow behavior with vacant chief positions
    But we still are facing the issue.

    which TASK are you using for CATS? Also have you implemented the badi_cats_approval to check for this scenario ie vacant position etc or exit cats00008
    also
    The actual user to who's inbox the workitem should be routed to is only
    determined in subsequent processing. Further, it is not mandatory that a
    user is actually assigned. Please note that workitems in general may be
    assigned to users, positions, work center etc. It is therefore by
    intention that an error is not raised in the scenario under
    consideration.
    best option is BADI_CATS_APPROVAL

Maybe you are looking for

  • Error 'Specify account number' while posting a parked document through FBV0

    Hi, I am getting an error 'Specify account number' while posting a parked document through transaction FBV0. I am not able to figure it out as to what account number it is referring to. Since the document is parked I assume the GL account used has no

  • Is there a way to use an Ipod as a flash drive?

    I have some pictures on my computer that I want to bring into school for Graphic Arts but I'm wondering if I could bring them in on my Ipod, rather than burning a CD. Can the Ipod work like a flash drive without having Itunes installed? It won't let

  • ITunes Store Metadata with iTunes 9

    How do you get metadata for items in the iTunes Store using iTunes 9? In iTunes you can select an item and choose Get Info to see all the metadata. This could be done for items that you owned and items in the iTunes store. With iTunes 9 I can no long

  • Change the range of dchp addresses to a unlisted range - 10.31.1.x

    i wish to use a new ABSE to run dhcp on my network and act as my wan router. i have a 30 node windows network with one lonely mac (mine) and another 30 statically set devices. the i.p. address range in use currently is 10.31.1.1 - 10.31.1.254. the 30

  • Problems Scripting a NumericField event...

    Hello, I do have a problem scripting an event for my numericField - I want the numericField to hide another object if the user enters 0 in the numeric field. Unfortunately this script does not work correctly - and I do not know why and need assistanc