ESS Error in standard Address iView (2004s)

Hi All,
NW2004s SP9
The satandard Address application has a few errors am not sure if it is specific to our implementation as I did not find notes nor any SDN messages.
In the address application the "Address Line 2" is greyed out and is just a display field even in edit mode.
The phone number Label is not seen in the application. For the phone number just the area code is avialable for input and the 6 numbers plus the LAbel saying Telephone are not getting displayed.
Its like
Blank(Supposed to be Label "Telephone Number"      Area code(P0006-AREAC visible)  Blank(supposed to be P0006-TELNR}
So its
example
Space ..... 716 Space
when it should have been
Telephone number   716 123456
I have seen the web dynpro application source code and it does appear that the fields do exist and are in visible mode.
The same was the case with address Line 2 field, it was visible and input field, but is just display field when the application is run.
Did anyone face this issue???
regards
Sam

Shardha,
Thanks a lot for offering to help me out. my email id is
[email protected] / [email protected]
regards
Sammer
Message was edited by:
        sameer chilama

Similar Messages

  • 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

  • Javascript error in Standard MDM IViews on portal

    Hello Xperts,
    I have deployed standard MDM IViews on my  portal.
    In standard Resultset IView, there is a provision of saving results by using My Bags option. When I click on My Bags option and then New Bag, it throws javascript error.
    Details of systems are as below.
    MDM API version 5.5
    Portal Version EP 7 SP07.
    Appreaciate any inputs for this.
    Ashutosh

    Hi Anu,
    Thanks for the reply.
    we are able to login to Data Manager with Mapped ID's and I even tried creating new IViews. Nothing worked.
    As you suggested, will try restarting the portal server.
    Thanks
    Satish

  • Critical Error in ESS Addresses iView

    Getting the following error message when running the Address iView for employees
    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.uk/com.sap.pct.erp.srvconfig.addr/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.per_address_gb failed.

    Ashutosh is correct,
    This location in your PCD portal_content/com.sap.pct/srvconfig requires additional permissions to be set.
    Depending on how you want to go about this - you could start by assigning the Authenticated Users group to this directory.  Dont forget to reset all the child permissions to force the permissions down the tree.
    Haydn

  • 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: "WDDynamicRFCExecuteException" received when previewign Address iView.

    Hi
    We are starting to configure ESS portals on EP 7.0 to connect to ECC 6.0 system. While trying to check the connectivity from Portal to R/3 - SSO works fine.
    However, the Address iView when displayed gives the following error;
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
        at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:102)
        at com.sap.xss.per.fc.persinfo.FcPersInfo.onCleanup(FcPersInfo.java:618)
        at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.onCleanup(InternalFcPersInfo.java:807)
        at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.onCleanup(FcPersInfoInterface.java:246)
        at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.onCleanup(InternalFcPersInfoInterface.java:299)
    devjrfc.trc_           .      
    Error> occured [5] >Mon Nov 10 15:32:46,624<   
    RfcException:
        message: CPIC-CALL: CMRCV on convId: 89901816
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       connection to partner '172.16.6.11:sapgw00' broken
    TIME        Mon Nov 10 15:32:46 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -6
    MODULE      nixxi.cpp
    LINE        3948
    DETAIL      NiIWrite
    SYSTEM CALL WSASend
    ERRNO       10054
    ERRNO TEXT  WSAECONNRESET: Connection reset by peer
    COUNTER     3
        Return code: RFC_SYS_EXCEPTION(3)
        error group: 102
        key: RFCERROR_COMMUNICATION_
    Error> occured  >Mon Nov 10 15:32:47,139<    >RfcGetException rc (7) message: Access via 'NULL' object reference not possible.
    <RfcGetException
    u201D
    Here is the ST22 dump of the error on the ABAP system.
    u201CRuntime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO                              
    Exception              CX_SY_REF_IS_INITIAL                                        
    Date and Time          11/10/2008 15:32:46                                                                               
    An exception occurred that is explained in detail below.                      
         The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not     
          caught in                                                                    
         procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
          clause.                                                                      
         Since the caller of the procedure could not have anticipated that the         
         exception would occur, the current program is terminated.                     
         The reason for the exception is:                                              
         You attempted to use a 'NULL' object reference (points to 'nothing')          
         access a component.                                                           
         An object reference must point to an object (an instance of a class)          
         before it can be used to access components.                                   
         Either the reference was never set or it was set to 'NULL' using the          
         CLEAR statement.                                                                               
    How to correct the error                                                          
         Probably the only way to eliminate the error is to correct the program.                                                                               
    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:                                                                               
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"                       
         "SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"                                    
         "HRXSS_PER_CLEANUP"   u201D
    Has anyone else faced this error? Can you please suggest me a solution?
    Thanks,
    Raza.

    Hi Guys -
    I found the resoution to this problem myself..
    We had our ERP5COM @ SP 14 while all the other components ERP5ESS, ERP5MSS, etc were at a lower level ie SP 13.
    So, by downgrading the above component we could Preview the iViews.
    I am closing this post.
    Thanks,
    Raza.

  • ESS Address iView issue

    Hello all,
    I am facing problem with the address iview (for US country) of ESS. The telephone no. field is being displayed in the edit mode of the iview also the communication with 2 options. But in overview I am not able to see phone no. though value is present. I can see only Area code...
    for e.g. Expected: Telephone no. <area code> <phone no.>
                Current situation:  Telephone no. <area code> blank
    Same thing happens with Communication field. I can see F4 help, but not able to see Telephone no. fields at all in overview, whereas in Edit mode they are present.
    Saw some posts suggesting some doc for resolving this. /thread/302943 [original link is broken] , /thread/393598 [original link is broken]
    Personal information removed
    I will greatly appreciate if anyone can take some time to tell me how to fix this.
    We are on EP7 EHP1 SP3 and ESS 603 SP7
    Thank you,
    Amol.
    Edited by: Matt on Jun 8, 2011 11:22 AM

    Looks like ur trying to show the details on the overview.
    Try the above options, looks like in newer releases they are configurable but in older releases we need to change the Web Dynpro java code.
    In the BizCardsView, you have to modify the wdDoModifyView
    and add the fields that has to be shown in the Overview to the fieldInfo array.
    Note: If you modify the standard sap delivered code, at SP upgrade the changes would be over written, so u would have to do it again. If its mandatory better to create a new custom DC.
    Regards
    Yugandhar Reddy

  • Address iView not getting displayed in ESS

    Hello Everyone,
    When I am logging into ESS with an User of SAP systen, I am unable to see the Address iView of the corresponding employee to whom the user is assigned.A number of iViews is getting displayed for different countries but I am unable to get the iView which I am looking for.Even when I am clicking on the iViews which are getting displayed no data is getting displayed.I am using country grouping 40 i.e India.I have also set the parameter in the User profile(UGR 40 and UCN IN).
    Also for some of the links, when I click them the page is getting refreshed continuously without any display.Bu twhen I am tyring the view the same using the PZ screens it is coming properly.
    Please let me know what settings are required to get the proper iView.
    With Regards,
    Kaustuv Goswami.

    Hi Kaustav,
    Go to the portal->content administration->webdynpro and see in the left pane where all the deployed applictions will get displayed.You can chekc the same thru SDM also.
      For deployment, you can download the .SCA file from the service market place and deploy it thru SDM.
    Regards,
    Sharadha

  • ESS US ADDRESS IVIEW NOT SHOWING ALL OVERVIEW FIELDS

    NW2004s , EP 7 , MYSAPERP 5.0, ECC 6.0
    ESS ADDRESS IVIEW - ( UNDER PERSONNEL INFORMATION ) -
    The IView is not showing up few key fields in the Overview Part
    for instance - Name, C/O , State , Zip code fields are missing from the overview part, but when i go to Edit part these field show up ( having data in them ).
    The personalization option shows NO UI Element listed ( in the Overview - Transparent container ) in both Displayed and Hidden Column ( Yet few fields are showing up  - Street Address , Telephone without area code )
    I deleted all the personalizations from the iview and the corressponding page ( By reseting it - as advised by a fellow SDN'er ) , but it didn't fixed the issue.
    Backend is correctly configured and webdynpro code has the fields listed as well.
    There isn't any SAP Note on this, as well.

    what SP level ar eyou on. If you are not on EHP2 or EHP3 ( that is ESS 1.3), the fields on the overview overview are hard coded ( UI elements generated on runtime not during design time) and hence you will not be able to use personalization. You will have to add fields in wdDoModify method of the overview screen.
    I remember replying with a code of how to do this. Probably you may find it with a search on ESS forum

  • Problems with the postal code in address iview ESS.

    I would greatly appreciate if someone answer this threat. I am having this big problem with the address iview. It is not possible to change the postal code in the address iview.

    Can you explain the issue? Means for which country this issue is coming. We faced similar issue. There is some bug in ESS/MSS package itself. You send me details of issue at [email protected] I will reply you back with OSS message answered by SAP if that is a bug.

  • Erroneous standard address  error in BP t-code

    Dear All,
    Can any help me on this error in BP Tcode i am getting the error First maintain the erroneous standard address. How to resolve this problem.
    Please send the solution as P1.
    Regds,
    Govinda

    HI,
    Can u Please elobarate on the error , as when u r getting that speciifc error,
    Please check once in the img >Cross app components>sap business partner> Business partner>adress determination .
    regards
    Yash.k

  • Error in Standard MDM Search IViews

    Hi All,
    We are using MDM Standard search IViews in our project.
    From past 2 days all the search IView are giving  *Error performing search Can not authenticate user session *
    I tested the System Connection and it is working fine.
    I checked the user mapping and every thing is fine.
    and we have not done any changes too.
    can some one help me in knowing what could be the reason
    Regards,
    Satish

    Hi Anu,
    Thanks for the reply.
    we are able to login to Data Manager with Mapped ID's and I even tried creating new IViews. Nothing worked.
    As you suggested, will try restarting the portal server.
    Thanks
    Satish

  • ESS Error Sweden Address - NullPointerException

    Hi all,
    I am trying to enable the std transaction for ESS Sweden Emergency address for ESS603. Have done the spro config for overview screens and for the determination of active subtypes.The roles are assigned in the backend for the test user.Also IT105 is set up for the proper pernr.
    When I login with the portal test user and run the transaction, its giving the below error:
      java.lang.NullPointerException
        at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.getStartPerspective(FcXssPcd.java:260)
        at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.getStartPerspective(InternalFcXssPcd.java:182)
        at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.getStartPerspective(FcXssPcdInterface.java:148)
        at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.getStartPerspective(InternalFcXssPcdInterface.java:152)
        at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.getStartPerspective(InternalFcXssPcdInterface.java:244)
        ... 53 more
    I was able to enable Norway emergency address with the above same procedure.
    Please help!
    Thanks
    Kukku
    ESS Error -   java.lang.NullPointerException

    Dear Mohan,
    Thanks for your help.
    But the error :If using the "edit" button, it is possible to enter a new address, but when the review button is clicked, an error is displayed stating "Start date must be 05.01.2012 or later. , still persists.
    Can you help in this?
    Warm Regards
    Geeta

  • MDM 3.0: error when deleting a Standard Address

    Hi,
    when loading delections in MDM 3.0, the function module BUPA_ADDRESS_REMOVE can't delete addresses if in the table BUT021_FS the field XDFADU is = 'X'.
    This means that I can't delete a Standard Address.
    Do you know how can I by-pass this problem?
    I need to delete those addresses.
    Thanks in advance.
    Fabrizio Rubino

    Hi Fabrizio,
    first of all this is a correct behaviour of the SAP Business Partner (BP). The address handling is designed in a way, that you cannot delete a default address if a BP already had one. The question is what do you want to do with the addresses? Do you want to delete all addresses of a BP? Then the answer is that this is not possible (at least it is not possible without modifying SAP code). If you want to replace the standard address, the sollution is to import the new standard address first, change the "is standard address" flag and then delete the old one.
    Kind regards
    Michael

  • Standard address of a BP (FPP3) in BUT021_FS

    Hi,
    I know that std addesses of a BPart  are stored as indicated in table BUT021_FS-XDFADU  = 'X'.
    For a BP i am trying to change a street name which is a default address (which is NOT std address as shown in BUT021_FS).  i am getting an error "Address is standard address; restriction to validity not allowed"  even though its Not a std adrress.
    I am using the BAPI : BAPI_ISUPARTNER_CHANGE and I am getting this error from this BAPI.
    Is there any other way to find if the address is std address or not?
    thanks
    Ricky

    Hi,
    Rather than sing that field for finding Standard Address, use field 'ADR_KIND' and check for value 'XXDEFAULT' which is normally used for Standard Address.
    Thanks.
    Ravi

Maybe you are looking for