Address issue in ESS

Hi Expert,
I encounter an issue in ESS when user try to create a new Address record.
In my case, Employee A already has a Address record effective from 1-1-2001to 31-12-9999
When Employee A try to follow the below step to create a new Address record, the issue will exist.
1. Select the country field
2. Select the validity period (by default, it is "Valid as of today" and I change it to "Valid from period") effective from 1-1-2010 to 31-12-2010
3. Save the record
The issue existed.
The record effective from 1-1-2001to 31-12-9999 will be deleted!!!! But instead, 2 record will be created. One is effective from today to 31.12.2009. And the other one is effective from 1.1.2010 to 31.12.2010.
My question is, is there any way to prevent such behaviour?
Best Regards,
KT

Hi,
You need to check the use cases for the infotype "0006" and "0009"
goto "SM30" give "V_T7XSSPERSUBTYP" and maintain
check the use cases set for the infotype "0006" and "0009"
some example as shown below
01 0006 1 A1
01 0006 4 A2
01 0006 5 A2
01 0009 0 B1
01 0009 1 B3
01 0009 2 B2
01 Country ( set the country code as per yourproject )
0006 infotype
1 Sub type
A use Case
( Note - use cases is also depends up on the Time contraint for the Infotype )

Similar Messages

  • Issue in ESS Personal Information iViews

    Dear Experts,
    I have an issue with ESS Personal Information details. The issue is the personal information related iViews such as Bank information , personal id, address iViews are only displays a road map and a button in disabled mode. Its doesn't display any data.
    But my Employee search iViews are working fine.;
    Any idea about this issue?
    Thanks,
    Ram

    Im getting exactly like below in Bank information iView
    [1] -
    [2]--[3][4]--
    Overview Edit Review and Save Confirmation
    <Previous Step> <Exit>.
    Please help me out!
    Ram

  • Issue in ESS - Single Signon

    Dear All,
    EP7.0 SP9, ECC5
    We have an major issue in ESS, The problem is with single sign on.
    Here are the scenario's we are using :-
    1. We are using "training1" as EP login id and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 The same ID "training1" (Same as EP log in), the portal is picking the data properly and working fine.
    2. If we use training1 as EP loginID and in PA30 in R/3 InfoType 105  and Sub Infotype 0001 if we use exeibckk (R/3 ID created for each individual user as communication user),
    we are getting error "User TRAINING1 does not exist in this period"
    we need to go ahead with the Step2, since all the EP login users are LDAP configured and,it has more than 15 characters, we cannot use EP login ID in InfoType 105 and Sub Infotype 0001
    since it is restricted to 12 Characters.
    e.g:
    EP user ID is  - shivakumar_ks ( taken from LDAP)
    where as his R/3 or ESS user ID is - P000000002
    since the login ID and R/3 ID are different,The system is throwing the error mentioned above.
    We map the Shivakumar_ks with P000000002 in the EP Personalize option. But it is
    not picking up the mapping. It tried to find the Shivakumar_ks in R/3 and fails.
    Even though we are giving the UIDPWD in the system Logon Method.
    Can anyone please give me the solution on the above.
    Thanks in advane
    Ponnusamy P

    I beleive you know how to map it ABAP UME - any how i enclose the details - may be useful to our friends
    Update Host file on Portal server with information of ABAP IP & Host Name
    Update Services file on Portal with entry  sapms<SID>  36<NR>/tcp
    Update Host file on ABAP server with information of Portal Server
    Create User ABAP Client with SAP_ALL & record password
    On Portal Server
    ============
    Open Configtool from
    <DRIVE>:\usr\sap\<SID>\JC<NR>\j2ee\configtool
    Expand - Global Service Configuration
    Expand - Services
    Click - com.sap.security.core.ume.service
    In Right Pane - Change the below things
    ==
    1
    ==
    UME_persistence.data_source_configuration
    from : dataSourceConfiguration_database_only.xml  (default)
    to    :  dataSourceConfiguration_abap.xml
    ==
    2
    ==
    ume.logon.r3.master.adapterid
    from : master
    to : 001
    ==
    3
    ==
    ume.r3.connection.001.user
    from : --
    to : <ABAP SUPER USER CREATED>
    ==
    4
    ==
    ume.r3.connection.001.passwd
    <PASSWORD OF ABAP USER>
    ==
    5
    ==
    ume.r3.connection.001.ashost
    from : --
    to : <ABAP SERVER HOSTNAME / FQDN>
    ==
    6
    ==
    ume.r3.connection.001.sysnr
    from : --
    to : <ABAP INSTANCE NUMBER>
    ==
    7
    ==
    ume.r3.connection.001.client
    from : --
    to : <ABAP CLIENT>
    ==
    8
    ==
    ume.r3.connection.001.group
    from : --
    to : <LOGON GROUP DEFAULT is SPACE or any You created >
    ==
    9
    ==
    ume.r3.connection.001.gwhost
    from : --
    to : <ABAP SERVER HOSTNAME / FQDN>
    ==
    10
    ==
    ume.r3.connection.001.gwserv
    from : --
    to : sapgw<NR>
    ==
    11
    ==
    ume.r3.connection.001.msghost
    from : --
    to : <ABAP SERVER HOSTNAME / FQDN>
    ==
    12
    ==
    ume.r3.connection.001.r3name
    from : --
    to : <ABAP SID>
    ====
    Above Configs Cahnges done as per below link and Note
    ====
    Useful Help Link :
    http://help.sap.
    com/saphelp_erp2005vp/helpdata/en/49/9dd53f779c4e21e10000000a1550b0/content.htm
    Alos Look at Note : SAP Note 718383
    Please mark the question answered
    Good Luck - Cheers
    PR

  • Error in the Address iview of ESS

    Hello all
    I am having problem with the address iview of ESS. The telephone no field is not being displayed in the edit mode of the iview i.e only the area code is being diaplyed and the rest of the no and the label is not there. From the previous thread I learnt that it might be because of some IMG customization but dont know how to solve it.
    I will greatly appreciate if anyone can take some time to tell me how to fix this.
    Thank you
    renu

    Hi sharadha
    Thank you so much for responding.
    Please send the document to [email protected]
    Thank you
    Renu

  • System Clean Install because of IP address issues

    HI,
    I just did a clean re-install of Snow Leopard as I had been having the self-assigned IP address issues that so many snow leopard users have been having. Before doing this I used time machine to make a backup of my HD on an external HD and synced my iphone 4 with the computer.
    Now I am hoping to get all of my music back, as well as my contacts, but can't seem to access either of those individually on my external HD using time machine or manually.
    Also I am worried about plugging in my iPhone to the computer and syncing with iTunes, as if I do, I may lose my lifetime's collection of music altogether. Clearly I should have backed up this music on an extra external HD in addition to the time machine backup, but didn't think to do that.
    What are my options? Will it erase the music on my iphone if I sync, or will it pull the music off of it and back into my library? What about Mail and Address book etc?
    any help would be appreciated

    Normal iTunes syncing with an iPhone is one-way - computer to iPhone. If you try to sync the iPhone without your old library then you will indeed wipe everything off the iPhone. There are numerous utilities around such as Pod To Mac - VersionTracker or MacUpdate - that can be used to transfer from the iPhone/iPod to the computer as well as ones that can mount the iPhone/iPod as a disk drive so you can transfer data between computer and iPhone/iPod. For example, PhoneDisk.

  • MAC address issue----Spearman

    Saw your comments on this in the post about the 1.9 bios for neo2platty ....
    I can confirm that My MAC address issue was caused by the bios that you sited in your comments....all F's were written to My nvidia lan too...
    only solution from what I have read is too rma it...'bummer'
    just thought You would like to know....  Your not alone

    I had the same problem yesterday and after many hours searching the web I ended up with this post that made me really desperate... But I didn't give up and while trying a new bios flash because of random crashes when in the bios, I noticed the obvious: you can change the MAC address when flashing 
    use the last version of the dos flasher with the parameters /nvmac:xxxxxxxxxxxx/wb after the name of the bios file; it's explained if you ask the help with the /help parameter. You can find the mac address on a stick on the parallel port.

  • Issue with ESS/MSS Business package 1.41

    Hi All
      I had an issue with ESS/MSS recently we deployed Business package 1.41 it contains HCM Forms and Process also,
    and we assigned the standard Manager-self-service role & Employee-self-service-role to test user but when the user is trying to access the standard application he is getting Portal runtime error.
       Is there any configuration is need from HRFunctional side and Basis side
    if any body have an idea please let me know ASAP.
    For every MSS standard applications like :work overview ,Recruiting,Team,Talent Management,Budjet,Projects,Planning ,Organization, leave
    I am getting like below error.
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 02:17_13/04/11_0031_116801250
    Refer to the log file for details about this exception.
    Thanks
    Renu.

    Hi All
        Here I am giving logs detail I got  two logs so giving both logs , can anybody help on this issue , if any configuration need please suggest.
    Full Message Text
    03:19_13/04/11_0045_116801250
    [EXCEPTION]
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;ProducerInfo&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#39;.
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(AccessController.java:246)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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(AccessController.java:219)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Next One
    Full Message Text
    Exception ID:03:19_13/04/11_0045_116801250
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.14.bp_folder/com.sap.pct.erp.mss.14.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : P00000531
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(AccessController.java:246)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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(AccessController.java:219)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;ProducerInfo&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#39;.
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    ... 29 more

  • Single Sign Issue in Ess

    Dear All,
    EP7.0 SP9, ECC5
    We have an major issue in ESS, The problem is with single sign on.
    Here are the scenario's we are using :-
    1. We are using "training1" as EP login id and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 The same ID "training1" (Same as EP log in), the portal is picking the data properly and working fine.
    2. If we use training1 as EP loginID and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 if we use exeibckk (R/3 ID created for each individual user as communication user),
    we are getting error "User TRAINING1 does not exist in this period"
    we need to go ahead with the Step2, since all the EP login users are LDAP configured and,it has more than 15 characters, we cannot use EP login ID in InfoType 105 and Sub Infotype 0001
    since it is restricted to 12 Characters.
    e.g:
    EP user ID is - shivakumar_ks ( taken from LDAP)
    where as his R/3 or ESS user ID is - P000000002
    since the login ID and R/3 ID are different,The system is throwing the error mentioned above.
    We map the Shivakumar_ks with P000000002 in the EP Personalize option. But it is
    not picking up the mapping. It tried to find the Shivakumar_ks in R/3 and fails.
    Even though we are giving the UIDPWD in the system Logon Method.
    Can anyone please give me the solution on the above.
    Thanks in advane
    Ponnusamy P

    Hi,
    As correctly mentioned here by debasish, most of the iviews in ESS and MSS use JCo Connections but there are some iviews which are IACs.
    In this case, you need to configure both JCo connections as well as user mapping. Incase of PA30, which could be an IAC or a transaction iview, <b>you may just focus on User Mapping</b>. But for the webdynpro applications, you would need JCo Connections.
    The link provided by Antonio clearly explains the steps. In brief, these are the steps involved:
    1) Create System and an alias. Make sure that you use the logon method UIDPW.
    2) Using the Personalization link, select a system and give the backend username and password. Save it.
    Log off and test if it works.
    Hope this helps.
    Regards,
    Sunil
    PS: Reward points for helpful answers.

  • Address Page in ESS show error

    Dear All,.
    we are implementing ESS and MSS
    system details are -
    ECC 6.0, EP 6.0
    BP applied on portal server are  ESS 600,MSS 600,PCUI 600 same sp levels
    we have create a zservice and zresource for address page.
    assigned to subarea then assigned subarea to area
    assigned area to personal info page ,
    and added address iview in the wokrset and assigned wokset to portal role.
    we are geting the below error when opening the address page -
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
        The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.per.fc.persinfo.FcPersInfo.initPernr(FcPersInfo.java:428)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.initPernr(InternalFcPersInfo.java:771)
         at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.initPernr(FcPersInfoInterface.java:166)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.initPernr(InternalFcPersInfoInterface.java:267)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.initPernr(InternalFcPersInfoInterface.java:431)
         at com.sap.xss.hr.per.in.address.overview.VcPerAddressINOverview.onInit(VcPerAddressINOverview.java:304)
         at com.sap.xss.hr.per.in.address.overview.wdp.InternalVcPerAddressINOverview.onInit(InternalVcPerAddressINOverview.java:262)
         at com.sap.xss.hr.per.in.address.overview.VcPerAddressINOverviewInterface.onInit(VcPerAddressINOverviewInterface.java:187)
         at com.sap.xss.hr.per.in.address.overview.wdp.InternalVcPerAddressINOverviewInterface.onInit(InternalVcPerAddressINOverviewInterface.java:152)
         at com.sap.xss.hr.per.in.address.overview.wdp.InternalVcPerAddressINOverviewInterface$External.onInit(InternalVcPerAddressINOverviewInterface.java:236)
         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:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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:869)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
    Request you help and suggestions to resolve the issue.
    Thank you,
    Regards,
    Gunja

    Dear
    What is the error in ST22...
    You must have deleted some of the subtypes of Infotype 0105 while configuring in R/3. Just check the error in ST22. Pls keep all the subtypes that are already provided by SAP and do not delete any of them.
    pls go through below thread
    ESS change OWN DATA ....HELP
    Thanks
    Keshari

  • Error in Address Iview in ESS role

    Hi,
    I have assigned a PERNER to portal user in 105 infotype, that portal user contains only ESS/MSS roles and when i am going to
    personel information  -> Address iview it showing folloing error
    Read of 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.addr/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.per_address_in failed.:com.sap.xss.config.FPMConfigurationException: Read of 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.addr/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.per_address_in failed.
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)
         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.xss.essservices.cc.ccesspcd.CcEssPcd.loadConfiguration(CcEssPcd.java:268)
         at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcd.loadConfiguration(InternalCcEssPcd.java:169)
         at com.sap.xss.essservices.cc.ccesspcd.CcEssPcdInterface.loadConfiguration(CcEssPcdInterface.java:115)
         at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface.loadConfiguration(InternalCcEssPcdInterface.java:124)
         at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface$External.loadConfiguration(InternalCcEssPcdInterface.java:202)
         at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:209)
         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:187)
         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)
    Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): 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.addr/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.per_address_in)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:422)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1248)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1353)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1300)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1067)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:72)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1060)
         at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)
         ... 74 more

    Hello,
    The error seems to look like a Permissions issue. Have you checked the Permissions assigned to the iView in the Permissions editor?
    Regards.
    Gopal.

  • ESS Workflow 10000015 Approve request for changing address thru Portal ESS

    Hi Experts,
    We want to implement ESS workflow 01000015 u201Cchange (infotype 0006) Address will be blocking until approved/rejected by Administratoru201D. The workflow is trigger OK from R3, user creates a new address and IT0006 is blocking till administrator approve or reject.
    What we want now is to trigger this workflow from Portal, but here is the problem:
    1.-  I do not see any option (button) for creating a new address from Portal iView, what else is missing??? I believe creating new address from Portal could trigger this workflow, but I am not sureu2026
    2.- If the first option does not work I would like to trigger this workflow by the event u201CChangeu201D, so I need to edit the address. From R3 is blocking IT0006 OK, but from portal is not blocking the address at allu2026 What else is missing??? I do not know if this could be an issue from R3 or Portalu2026.
    We already check u201CNote 495971 - Workflow 01000015 is not triggered when changing addressu201D and workflow is working ok only from R3.
    Regardsu2026..
    David Cortes

    Hi Swamy,
    I am a little confused of you requirement. The scenario here is that Person A (Any person using ESS) must not change any of his/her own personal data until Person B Approve/Reject the new Data. For example: if a user A want to change his/her address, personal data etc. must be approve or reject for another person B. This is a validation that most of the companies want to have in order to validate this information. Employees may change their personal data, but how HR area validates if this new information is real or not...  One way to verify this new information is a validation for a Person B who will be to approve or reject this information. Now if you do not have this scenario I believe you will not have to do this implementation class because ESS do not have this scenario. The standard ESS functionality is available for change any data without validation and this should be working right now on your Enterprise Portal.
    If you want to have a validation for a third User, Person B, you may check these points:
    1. Edit 2. New Permanent address
    Edit - Will change the record irrespective of dates. This will modify the current record which is valid as of today.
    New Permanent address - This will create a new record effective today and previous record will be delimited.
    If I use lock functionality in Edit scenario, then in the portal it will dispaly previous record which is not the correct data.
    For 2nd case, this will insert the new record, so Lock may work in this case. I will check this.
    I believe you will work most of the time with "Edit" button. If Person A edit address, the new register will be created and locked in PA30 Infotype  6 until person B Approve/Reject. How Person B knows if someone has edit his/her address?? You may achieve this using Universal Work List and notification. You may have to create a task for person B with email notification, so person B will be enter into Portal and check his/her new task from the UWL. This task will be ITS UI front end and from here person B decide if approve or reject. If Person B approve, the new register will be unlocked and replace the last one (Also in Portal). If person B reject, the register blocked will be gone and the last one remains.
    This should work for any infotype . Check only the type of event generated for any of them in order to trigger the workflow.
    Do you have any idea how to achieve this for Personal details where the Lock/Unlock functionality is not available.
    Standard ESS works without any lock/unlock functionality. remove the current workflow if you have used any.
    Regards
    David Corté

  • Spanning Tree and Admin mac address issues srw2048

    Ok, I have a somewhat complex problem and hopefully someone may shed some light or have an idea as to whats wrong.
    First the scenario:
    I have two Cisco Cat 6509's etherchanneled to each other via two fiber cables.  One of these is the STP/RSTP root.  I have two SRW2048's.. one trunked to each of these 6509 switches.  There is also a trunk between the SRW2048's.  All this is to create a redundant topology so that if one of the switches fail's the others can still forward packets to each other.  Of course the scenario described is in fact a loop that should be handled by STP/RSTP.  I have RSTP enabled on all the switches in the scenario (PV RSTP on the cisco switches as they only do Cisco's brand of per vlan spanning tree).  There are 3 vlan's configured on each of the srw2048's (2,55,96).  There are corresponding vlan's also on the 6509's.  I have put the srw2048's management interface into vlan 2.
    The problem:
    I need to forward packets between the srw2048's primarily and only use the 6509 that is not the root when a failure happens.  I have configured the non-root 6509's spanning tree cost on the etherchannel to be higher then the alternate path through the srw's to the root.  I can hook everything up and view the spanning tree and see that the srw2048's interface that goes to the non-root 6509 is blocked, and all other interfaces on the other switches are forwarding.  I can in fact ping and get to the admin interface on all the switches.  Then for some strange reason the admin interface of the srw2048 plugged into the non-root 6509 stops responding.  If I disable either the interface its plugged into on the 6509 or the other srw2048 everything starts working again.  Sometimes it responds after many failures for no apparent reason.  I looked into the mac-address table on the 6509's and they are conflicting, pointing to each other for the mac-address of the broken srw2048.  When I clear the mac-table the admin port comes back for about 5 seconds then again goes dark.  When reviewing mac-table on the 6509's they are back to pointing to each other.  The odd thing (although I haven't confirmed this completely) is that hosts placed into vlan 2 on that same srw2048 seem to work fine.  If there was an STP loop or something misconfigured, I would expect it to effect any host in vlan 2 or the other vlan's for that matter on the srw2048 that stops responding.  Alas, I am stuck because I need to manage this switch remotely.  My only thought is that for some reason even when the STP status is blocked the broken srw2048 is still sending out arp's of its admin interface and bypassing the STP protocol.  I have no way to confirm this, but maybe someone has an idea as to what I'm doing wrong, or otherwise offer a solution.  For now, I simply removed vlan 2 from the 6509 that the broken srw2048 is plugged into and everything seems fine.
    My apologies for such a long post, but this is somewhat complicated.  Thanks in advance for any info.
    -Geoff
    Message Edited by gmyers on 08-19-2008 10:35 PM

    To follow up, I had a ticket open with Linksys about this for about 3 months with no resolution.  I submitted packet captures, stp outputs, etc and no luck.  I gave up and basically had to revert to a manual failover for redundancy.  It's no perfect or fast, but it works every time.
    Unless linksys issues a firmware upgrade with this as a fix, I doubt we will be able to ever resolve this on our own.

  • Multiple IP Address Issues

    This has been driving me crazy for a while now.  Mainly because I solved this once for myself earlier this year!  I cannot find the solution again and I need help.  Two Snow Leopard clients I have, (10.6.6) are returning three IP addresses in DNS.  One for each is their correct static IP, the other two are odd. 
    For example (not actual IPs):
    PowerMac1.domain.com is returning 192.168.1.38 (correct), 192.168.242.1, 192.168.138.1
    iMac1.domain.com is returning 192.168.2.13 (correct), 172.168.28.1, 172.168.16.1
    This happens with Windows nslookup or Apple's dig, of course.
    Like I said, I managed to fix this on another system (running Snow Leopard server) a while back.  I believe it was an SMB issue?  Don't really remember.
    Any help is greatly appreciated!

    This has been driving me crazy for a while now.  Mainly because I solved this once for myself earlier this year!  I cannot find the solution again and I need help.  Two Snow Leopard clients I have, (10.6.6) are returning three IP addresses in DNS.  One for each is their correct static IP, the other two are odd. 
    For example (not actual IPs):
    PowerMac1.domain.com is returning 192.168.1.38 (correct), 192.168.242.1, 192.168.138.1
    iMac1.domain.com is returning 192.168.2.13 (correct), 172.168.28.1, 172.168.16.1
    This happens with Windows nslookup or Apple's dig, of course.
    Like I said, I managed to fix this on another system (running Snow Leopard server) a while back.  I believe it was an SMB issue?  Don't really remember.
    Any help is greatly appreciated!

  • Issue in ESS i.e. gives dump error while availing a leave through ESS

    Hi All,
    In My client place, system gives a dump error when employee is maintaining its leave in ESS system.Here TM is not integrated with payroll.
    Plz help me how to resolve the issue.

    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
         at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:259)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:104)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:842)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1072)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
         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:782)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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:869)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
         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:332)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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)

  • Time Capsule   Airport Extreme   Airport Express - IP Address Issues, Internet dropping...

    I have a brand new Time Capsule 3TB functioning as my main wireless router from a Motorola SB6141 Cable Internet Modem.  I have a Airport Extreme and Airport Express extending the network from my Time Capsule 3TB.  After the intial setup there were no connection issues for several days.  However, yesterday I began to experience issues where the Time Capsule starting telling me that other devices on the network were trying to assign IP Addresses to change from DHCPand NAT to Bridge Mode.  What is the best solution for this?  My temporary solution is just to do a hard reset of the SB6141 which seems to alleviate the issue until the next day.  Please help!

    There is definitely some issues with the SB6141 modem and the new AC version Extreme and TC.
    I have recommended to several people to use a crossover cable or a small 10/100 switch.
    Either is a very cheap item and I cannot promise a solution but it has helped.
    Net time it happens please login with airport utility and take a few screenshots of the TC summary page and internet tab and post them here.

Maybe you are looking for

  • [DWM] How to get window titles (w/xprop?)

    I'm trying to expand my "switch-to-tag"-script to include window titles, but have stumbled upon something I can't understand: If I issue "xprop" (with no arguments), and click on my firefox-window, I get the following output: user@host $ xprop (click

  • Snow Leopard installation on Mac Mini has failed

    Hi, Does anyone know whether Snow Leopard checks what hard disk is installed in order to satisfy installation requirements as I've fitted an SSD Hard Disk Drive in my Macintel Mac Mini and installing Snow Leopard has failed (no longer boots into any

  • Is backlit keyboard of 13-inch Macbook Pro with Retina display integrated English and Russian ?

    Is backlit keyboard of 13-inch Macbook Pro with Retina display integrated English and Russian ? I mean Russian is integrated on keyboard not by using stickers or installing font

  • Nav links not working in Blackberry

    I have put up some test pages for a client to view ( http://www.jescoconstruction.com/index2). When he is on his Blackberry, and he selects links from the navigation menu, he gets an error message which says it can't find the server for that page and

  • FDM Serious Error(Object variable or With block variable not set).

    Hi All Intelectual, When i was trying to upload data into FDM for checking application flow. i got the below mentioned error pops-up everytime. Error: An error occurred importing the file. Detail: Object variable or With block variable not set I trie