IT105 subtype 0001 & relation to portal (teamcalendar, leave request, etc.)

Hi SAP Experts,
Could you provide me some Informations/Documentations about the relationship between IT105 0001 (Systemuser) and the standard time management iViews in portal, e.g. Team calendar, Leave Request etc.
Background is, that we use the same System user id's for different persons in different periods. I want to obviate that this could cause errors in Enterprise Portal (EP7.0, ESS/MSS 1.0, NW04s, ERP2005, SP 13). 
I will reward points for helpful answers.
Best Regards,
Nadin

Achim,
Maybe you are right but im not sure.
My problem is that we have a problem in a productive system: A manager looks into his team calender and all seems to be ok and then he goes back to an other month and there comes the error message infotype 105 does not exist.  I do not know what exactly was made but in IT105 subtype 0001 there is entered a system id that was deleted in su01.
So because of the error there seems to be any relationship between the IT105 and team calender at all.
We tested different combinations with persons that leave the company and give the user to another person and we also tested persons without a systemuser. And we were not able to force any error message in any combination.
We go to SAP Support and ask for this relationship and told them the problem but they answered:
<i>Hi Nadin
This will not be possible to analyse without reproduction of
the exact steps that cause the error
SAP recommend that when a employee leaves his user
or employee number cannot be re-used - the historical
data of that person has to be linked to only one user
to avoid confusion
The Portal user is associated with a back-end user which
in turn is associated to an employee via IT0105 - all
associations must exist without delimitation
Please also clarify the business impact given there is
no way to reproduce the issue</i>
I want to understand why and when does IT105 has some impact to team calender.
So could you or anybody else give me a hint.
Best Regards,
Nadin

Similar Messages

  • Idea for Extensibility and Leave Requests | Fiori Apps RDS |  Fiori Apps RDS General

    Hi everyone,
    I have an idea and some questions in relation to Extensibility and Leave Requests... etc.

    Shoot them

  • Relation into P_ORGIN and INFOTYPE 105 SUBTYPE 0001

    Hello, at the moment I have a problem, I add the user's name in the infotipo 105 and subtype 0001 but this cause that the user can see his data in the infotipo 0001, when at level of P_ORGIN one has specified that alone he can see personal to his position by means of the organizational key.
    Does this infotipo have some precedence on the P_ORGIN?

    when at level of P_ORGIN one has specified that alone he can see personal to his position by means of the organizational key.
    At VSK1 level
    P_ORGIN
    INFTY   - Info type
    SUBTY
    AUTHC- Authorization Level
    PERSA u2013 Personnel area
    PERSG u2013 Employee group
    PERSK- Employee sub group
    VDSK1- Org Key

  • Cancel leave requests via ess portal

    hi experts,
    i am very new to workflow so any help would be appreciated. can some one please provide a detailed step by step guide on how to create a workflow for canceling leave requests (must go thru manager's approval first before the cancellation to be applied) via portal?

    Hi,
    If you go with the standard, you don't have to create any workflow, you can use the existing one. The approach is exactly the same as implementing a workflow for new leave request. Basically in the SPRO you need to go to the ESS area and find the Leave request related configuration there. You will find that you can define for each absence type a workflow which will start (and you can define them both for new request and cancellation requests). With proper configuration, everything will work without any WF development effort.
    If you find out that the standard solution does not fulfill the requirements, return to this thread for more detailed questions.
    Regards,
    Karri

  • User unable to access Leave Request in Portal

    Hello guys,
    A user can't access the leave request via Enterprise Portal 7.0 - the view works perfectly with the other users thus the issue seems to be isolated to this particular user. IE version being used is IE 6.0 - so that shouldn't be the cause of the problem. Also, the roles have been cross-checked and synchronized with the other users who are able to access the Leave Request function. Yet, it appears the roles are correctly assigned
    Could it be possible that this is a problem with the user's data? Which component should I also look into?
    Thank you in advance!
    Regards,
    Jan

    As for the IE patch problem, we're conducting an http-trace to check with this. But I see this as very unlikely, since the user also tried accessing it via a different workstation but the problem persists.
    The 'resolution' for similar cases was to recreate a user account - even just a direct copy of the same user works. This could be an SAP application bug perhaps? The target is for a long term fix to the problem.
    Thanks!
    Regards,
    Jan

  • How to run a search query for a particular folder in KM related to portal

    Hi,
    Can any one tell me the steps for : how to run a search query for a particular folder in knowledge management related to portal.
    Answers will be rewarded.
    Thanks in advance.
    KN
    Edited by: KN on Mar 18, 2008 6:33 AM

    Ok u may not require a coding
    But u req configuration
    U should first make a search option set
    Link: [Search Option set|http://help.sap.com/saphelp_nw04/helpdata/en/cc/f4e77ddef1244380b06fee5f8b892a/frameset.htm]
    Then u need 2 duplicate a KM Command by the name Search From here
    and customize it to include the Search Option that u have created
    Link: [Search from here|http://help.sap.com/saphelp_nw04/helpdata/en/2a/4ff640365d8566e10000000a1550b0/frameset.htm]
    Then in the layout add this command.
    Regards
    BP

  • Java.lang.NullPointerException Error in Leave Request tab of ESS in Portal

    Hello All,
    I have configurted ESS/MSS on EP 7.01 SP03, but it is giving error in almost every tab.
    When i navigate in to Employee Self Service < Working Time < Leave Request tab it ends up with error pasted below.
    java.lang.NullPointerException
    Same error appears for other tabs like Employee Self Service < Working Time <Quote Overview/Clocl In/Out Corrections
    Any help to solve this issue will be highly appretiated.
    Thanks
    Vinit

    Full exception chanin from NWA is as below
    Exception occured during processing of Web Dynpro application sap.com/ess~lea/LeaveRequest. The causing exception is nested.
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290)
    at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173)
    at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelection.onInit(VcCEAssignmentSelection.java:235)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelection.onInit(InternalVcCEAssignmentSelection.java:174)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelectionInterface.onInit(VcCEAssignmentSelectionInterface.java:162)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface.onInit(InternalVcCEAssignmentSelectionInterface.java:144)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface$External.onInit(InternalVcCEAssignmentSelectionInterface.java:220)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    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:1289)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
    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:319)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Edited by: Vinit Soni on Aug 27, 2010 7:59 AM

  • Providing Calender option for dates in Leave Request form in ESS Portal

    Hello All,
    Can anyone tell me how to get the calender option for the From date and To date fields in the craete leave request iview in ESS ?
    In the backend R/3 transaction, we are able to see the calender option. But it is not visible in the portal.
    Thanks for your help...
    Regards,
    Bindu

    Go to:
    IMG > Personnel Management > Employee Self-Service (Web Dynpro ABAP) > Service-Specific Settings > Working Time > Leave Request > Processing Processes > Define Processing Processes for Each Rule Group
    Select your Rule Group
    Under Record Partial-Day Absences in   you have three options: Hours and Clock Times / Hours / Clock Times
    You should select Hours and save the record.
    With this, you will only have the duration and clock times will not be displayed.
    Regards,
    Harshal

  • Multiple Leave Request iviews in 1 portal instance

    Hi Guys,
    We are working on EP 7.0, I have 2 questions:
    1st question:
    current our portal is shared by 3 agencies (A, B,C), which maps with 3 clients (100, 200, 300) in R/3, and the three ESS Leave Request should looks different.e.g: for agent A, he wanna the input field changed to drop down, B wanna add radio button, C wanna add check box, which results in 3 different copies of standard DC "sap.com/esslea" which is the standard DC imported from NWDI, we may need to rename the copies into "AAA.com/esslea" , "BBB.com", "CCC.com/ess~lea", etc, as long as we have 3 different iviews for leave request, anyone knows how to do it? Keep the original DC unchanged, while create extra copies to add customized code.
    2nd, any one knows where we can change the client that the Web Dynpro Java iview points to? Can we change in the source code?
    Thanks with Rewarding points.
    Regards,
    Guo Feng

    No one answer, I closed it.

  • Delimit Infotype 0105 Subtype 0001

    Hi All
    I am new to ABAP so need help.
    We need to delimit Infotype 0105 subtype 0001 records.
    I tried vai a number of ways but facing issues in someway or the other.
    When I try to do the same via FM: BAPI_HRMASTER_SAVE_REPL_MULT, it creates a new entry for the same record with end validity day as system date (the old record which has end validity date as 31.12.9999 remains).
    When i try to do the same via FM: BAPI_EMPLCOMM_DELIMIT, it throws an error 'EPG                  009No data stored for 0105 in the selected period' even though the record exists.
    CALL FUNCTION 'BAPI_EMPLCOMM_DELIMIT'
      EXPORTING
        employeenumber       = '00000049'
        subtype              = '0001'
        objectid             = 'P'
        lockindicator        = ''
        validitybegin        = '20100701'
        validityend          = '99991231'
        recordnumber         = '000'
        delimit_date         = '20120219'
    *   NOCOMMIT             =
    IMPORTING
       RETURN               = return.
    *   EMPLCOMMKEY          =
    Not sure how to go about it. I searched the forum which suggested to use Function Modules, but even then the issue isn't getting resolved.
    Please help.
    Martin

    Hi
    Your problem is the parameter OBJECTID It doesn't make sense to pass a 'P'.
    Other than that, you just have to lock and unlock the Personnel Number accordingly.
    Regards
    data: return type BAPIRETURN1.
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
      EXPORTING
        number        = '00000224'
    * IMPORTING
    *   RETURN        =
    CALL FUNCTION 'BAPI_EMPLCOMM_DELIMIT'
      EXPORTING
        employeenumber       = '00000224'
        subtype              = '0001'
        objectid             = ''
        lockindicator        = ''
        validitybegin        = '20070101'
        validityend          = '99991231'
        recordnumber         = '000'
        delimit_date         = '20120219'
    *   NOCOMMIT             =
    IMPORTING
       RETURN               = return.
    *   EMPLCOMMKEY          =
    BREAK-POINT.
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
      EXPORTING
        number        = '00000224'
    * IMPORTING
    *   RETURN        =

  • ESS Leave Request - Portal Runtime Error when the "Cancel" button is hit

    We have configured the Leave Request application, created a custom workflow, created security roles, and we are now testing in our quality environment. 
    We are encountering a very strange "Portal runtime error" which we cannot resolve - When you come into the Leave Request application, and then, without completing the request, just hit the "Cancel" button, the runtime error is generated.
    We have run a trace of authorizations and everything has come up clean.  Everything is configured, and there are no problems actually creating, approving and posting requests. 
    Any ideas?

    Hi,
    please check whether the user is authorized to cancel the request.
    and take a look at this WS12300111
    Regards
    Manohar

  • ESS Leave Request error when launched from the portal

    Hi guys
    When i try to launch the Leave request from ESS tab in portal i am getting the following error
    I have checked the backend and i can process a leave request from there. It is failing on the portal side.
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    Index: 0, Size: 0  
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
         at java.util.ArrayList.RangeCheck(ArrayList.java:507)
         at java.util.ArrayList.get(ArrayList.java:324)
         at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
         at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
         at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2549)
         at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
         at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
         at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
         at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
         at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
         at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
         at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
         at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
         at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)

    This error occurs due to the following customisaton, Please
    check this :
    Check the Feature WEBMO is activated or not?
    Is the pernr assigned correctly?
    Please can you check if the Pernr used
    has correct information like It0105 etc, also the rules are
    correctly defined.
    For the Employee, First of all check the Period Work Schedule also
    the Quotas of the pernr needs to maintained in 2006, Please do
    this customisation and it should solve the issue.
    Maintain the absence quota in the IT2006 and then try once.
    Also make sure that the Settings in Webmo and PTARQ etc all is done
    The pernr belongs to the a Rule and have absences defined for him.

  • Create Leave Request In portal doesn't load  after logging in

    He All,
    we are facing an issue with some of the users of the E portal , after they log in and click on create leave request  the loading icon appear and the portal stuck at that and nothing else happen like in the attached image  , this issue happen with some users not all of the users however it was working with them before.
    Please advice
    Thanks in advance

    Hi Ahmed,
    I didnt suggest a browser issue.
    But using such tool when problem happens can show your the exact request url that hangs.
    Then from this, you can reach to where the problem resides on the server.
    Google chrome contains it already (just click on F12) , you can see all requests:
    When you see a request that doesnt have status 200 or without status, this can give you focus on where is the issue.
    Best regards,
    Tal

  • Error message for Leave request (Related to some Old Question)

    Hi Experts,<br />
    <br />
    We are facing an Error when only 1 employee in the company opens his Leave request page, the same page is working for others perfectly.<br />
    <br />
    this Error is the same as the one in the below posts:<br />
    <br />
    1. Link: Re: Error message for Leave request<br />
    <br />
    and I tried going through their solutions such as:<br />
    <br />
    1. Please check if you have the leave config done on ECC side under Personnel Management --&gt; Employee Self services --&gt; Service Specific settings --&gt; Working time --&gt; Leave request .<br />
    2. At the least you should have assign the default rule to your PSG to the standard leave type given. Otherwise create your own rule groups and Specify Processing processes for type of leave set up.<br />
    3. explicitly activate WEBMO Feature although it was activated<br />
    <br />
    But the Error is still coming for this specific Employee, even though his Vacation Quota is created and available for deduction.<br />
    <br />
    Please Help me in solving this issue.<br />
    <br />
    Regards,<br />
    Abdulrahman

    Index: 0, Size: 0:
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
         at java.util.ArrayList.RangeCheck(ArrayList.java:507)
         at java.util.ArrayList.get(ArrayList.java:324)
         at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
         at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
         at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2549)
         at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
         at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
         at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
         at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
         at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
         at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
         at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
         at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
         at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         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:1288)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)
         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:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

  • IT 0105 subtype 0001. Assign one System user to more than one person?

    Hello, Gurus!
    We are maitaining Hr master data (infotype 0105 - Communication, subtype 0001 - System User name). We have two person: person A and person B. Person A have communication with system user C. When we communicate person B with same system user C, we gettin error:
    "ID/number already used for person A".
    The time constraint is set to 3 (Record may include gaps, can exist more than once"
    Is it possible to assign one system user more than one person?
    This condition is checked by FM CHECK_USRID. We assume, what the result of this checking can be changed from "Error" to "Alert", if we will change one record in table T77S0:
    Current value:
    GRPID=MAIL
    SEMID=SAPSY
    GSVAL=0001
    Table record after modification:
    GRPID=MAIL
    SEMID=SAPSY
    GSVAL=0002 (or any digital value, which is iffer from "0001"
    Should we expect negative consequences of similar modification?
    Please, advice.

    Thanks for explanation.
    But there is a little moment, that I can not understand ((
    We check PAI module of CHECK_USRID (include MP010530, screen 2000) and find folowing fragment of ABAP code:
      CALL FUNCTION 'RH_GET_HR_USER_SUBTY'                       "YRAK040203
           EXPORTING                                                     "YRAK040203
                 mandt                 = sy-mandt                     "YRAK040203
            IMPORTING                                                     "YRAK040203
                 hr_subty              = hr_subty                         "YRAK040203
            EXCEPTIONS                                                    "YRAK040203
               SUBTYPE_NOT_AVAILABLE = 1                                "YRAK040203
                 OTHERS                = 0.                               "YRAK040203
        IF p0105-usrty = hr_subty.                                        "YRAK040203
        MESSAGE E900 WITH  PA0105-PERNR.                           "YRAk028906
          MESSAGE e900 WITH object_found double.                     "YRABEWERBER
        ELSE.                                                                  "YRAK040203
        message W900 with pa0105-pernr.                                 "YRAK040203
          MESSAGE w900 WITH object_found double.                     "YRABEWERBER
        ENDIF.                                                                 "YRAK040203
    where p0105-usrty=0001 and hr_subty is equivalent field GSVAL=0001 in table T77S0. In other terms, when we are
    maitain subtype 0001, the first condition (marked bold) is always executed.
    For what the "else" condition is used, if it never be executed? If we will change value GSVAL from 0001 to 0002, theoretically, we will get "warning" instead "error", because p0105-usrty = hr_subty=false and code MESSAGE w900 WITH object_found double will be executed.
    Any ideas?
    Regards.

Maybe you are looking for