BPC 7.5NW Performance Document

Hi Experts,
Please help me to get BPC 7.5NW performance document or related document if anyone has.
Thanks in Advance,
regards,
Hari

Hi,
The following document might have some pointers that you are looking for
performance analysis and tuning guide for BPC - Link below.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e08c2aa2-6c58-2e10-3588-e6ed2e7c04f8?QuickLink=index&overridelayout=true]
Thanks,
Sreeni

Similar Messages

Transport of Security objects in BPC 7.5NW

As a part of NW BPC transports, changed the entries in table UJT_TRANS_CHG. For the 1st transport (from DEV to QA)wanted to transport ALL objects including Security and Teams. So, selected 'Development' for ALL objects under this table.
After the transport collection via tcode UJBPCTR and importing into QA, found that 'Users', 'Teams' and 'Task Profiles' did NOT transport. 'Member Access Profiles' did transport to QA.
I expected 'Users', 'Teams' and 'Task Profiles' also to be transported. We are on SAP BPC 7.5NW, SP4.
Am I missing something here ?
Thanks in Advance.

Hi
we had the same problem and didn't know if Security objects could be transported, but we found the BPC User Mass Management Tool.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0cdbccf-0def-2d10-298d-f4223de9a6ed&overridelayout=true
This could help you to export the security objects in DEV and import the objects in PRD.
The transports you need for the ZUJE_MASS_USER_MGMT Programm you found on page 46 in the document mentioned above.
Please let me know if we could help you.

Using a variable in an allocation routine in SAP BPC 7.5NW

Below is a very simple BPC allocation routine I wrote. The data originally sits on a dummy profit center and needs to be allocated to all itu2019s relevant profit centers. These relevant profit centers can be derived from the profit center hierarchy (BPC_ + ID of entity).
When I hardcode the Profitcenter and the entity, the routine works (as below). But what I really want is that it works variable as in the line that I commented out. Any idea whether this could work (BPC 7.5NW) ? If not, I am afraid I need to go to ABAP, which is really a pitty
//ALLOCATION PROCEDURE CONVERSION RATE
//=====================================
*RUNALLOCATION
*FACTOR=1
*DIM SEBACCOUNT WHAT=CONV_RATE; WHERE=<<<; USING=<<< ; TOTAL=<<<
//*DIM PROFCENT WHAT=DUMPC; WHERE=BAS(BPC_"%ENTITY_SET%");USING=<<<; TOTAL=<<<
*DIM PROFCENT WHAT=DUMPC; WHERE=BAS(BPC_OKB);USING=<<<; TOTAL=<<<
*DIM ENTITY WHAT=OKB; WHERE=<<<; USING=<<< ; TOTAL=<<<
*ENDALLOCATION
Thanks
Nico

Gersh,
It works now. I have implemented the below code (ENTITY needed to contain the variable as well). The relationship profitcenter and entity is very important as it derives the relevant profitcenters from the profit center hierarchy (e.g. all profitcenters under the legalentity node).
//ALLOCATION PROCEDURE CONVERSION RATE
//=====================================
*FOR %ENT% = %ENTITY_SET%
*RUNALLOCATION
*FACTOR=1
*DIM SEBACCOUNT WHAT=CONV_RATE; WHERE=<<<; USING=<<< ; TOTAL=<<<
*DIM PROFCENT WHAT=DUMPC; WHERE=BAS(BPC_%ENT%);USING=<<<; TOTAL=<<<
*DIM CATEGORY WHAT=FCSTCUR; WHERE=<<<; USING=<<< ; TOTAL=<<<
*DIM ENTITY WHAT=%ENT%; WHERE=<<<; USING=<<<; TOTAL=<<<
*ENDALLOCATION
*NEXT
Thanks
Nico

BPC 7.5NW Report Issues When Requesting Year To Date Data

Dynamic reports built with 2 row expansions (Cost Ctr, Account) up to 3 columns (not expansions, set to different categories with excel formulas for variance calculations...Act vs. Bud for example) result in error messages (error retrieving data and another related error messge) when requesting YTD data vs. Periodic data. The report runs fast and properly with Periodic measure. When running with the YTD measure, attempts to reduce the report data volume by removing comparative categories and removing formatting (after ranges) still results in YTD data retrieve errors.
Has anyone else had similar issues with BPC 7.5NW, SP9, and YTD data not pulling into reports? What are the common causes for issues with YTD data retrieval? Given the design by SAP of the BPC NW product and promotion of using BPC for both Periodic and YTD data, should I expect this report to work properly, meaning that I can get output with YTD data without long runtimes or errors that result in terminating the report? Thank you.

Hi,
This would do it :SQL> !cat q.sql
with t (dt, val) as (
     select to_date('2011/01/04','yyyy/mm/dd'), 123 from dual union all
     select to_date('2011/04/09','yyyy/mm/dd'), 234 from dual union all
     select to_date('2011/06/28','yyyy/mm/dd'), 345 from dual union all
     select to_date('2011/10/18','yyyy/mm/dd'), 456 from dual union all
     select to_date('2011/12/23','yyyy/mm/dd'), 567 from dual union all
     select to_date('2012/01/07','yyyy/mm/dd'), 678 from dual union all
     select to_date('2012/05/13','yyyy/mm/dd'), 789 from dual union all
     select to_date('2012/07/19','yyyy/mm/dd'), 890 from dual union all
     select to_date('2012/08/30','yyyy/mm/dd'), 901 from dual union all
     select to_date('2012/09/22','yyyy/mm/dd'), 012 from dual
------ end of sample data ------
select *
from t
where dt >= trunc( add_months(trunc( &&dateexec. ,'month'),-1) ,'year')
and dt < trunc( &&dateexec. ,'month')
undefine dateexecThe dateexec parameter is just here to "simulate" sysdate of different points in year.
<i>(your actual query would have sysdate where the dateexec parameter appears)</i>
SQL> @q
Enter value for dateexec: sysdate
DT                         VAL
07/01/2012 00:00:00        678
13/05/2012 00:00:00        789
19/07/2012 00:00:00        890 sysdate does the current year up to previous month.
SQL> @q
Enter value for dateexec: to_date('20120122','yyyymmdd')
DT                         VAL
04/01/2011 00:00:00        123
09/04/2011 00:00:00        234
28/06/2011 00:00:00        345
18/10/2011 00:00:00        456
23/12/2011 00:00:00        567when ran in january, it retrieves all the previous year.

Error in "Maintain Performance Documents" Iview

Hi,
I have a Iview in MSS - "Maintain performance documents".
When I open the Iview(Status Overview) through MSS it shows the documents link.But when I click on the links in Status Overview I am getting the following error.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 01:13_06/09/10_0031_8961850
Refer to the log file for details about this exception.
After checkign the portal log I can see teh error as follows
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/<CustomerNamespace><ESID>/bc/bsp/<Namespace>/<Application>/<PageId>?<UseNoCookie[IF_true]>sap-client=<System.client>&sap-language=<Request.Language>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap_ep_version=<Portal.Version[url_ENCODE]>&sap_ep_baseurl=<Portal.BaseURL[url_ENCODE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 161. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
Which system attribute it is talking about? Not getting from where its showing SAP_Localsystem..I checked the system object used in Iview.It is working fine.
There are no authorization errors also.
When I chekced the iview being opened after clicking on link in "Status Overview",
it is pointing to standard iview.How do I make it point to customized iview pointing to my client at R/3.
Please suggest what might be the solution.
Thanks and Regards,
Sumangala
Edited by: Sumangala Byali on Sep 6, 2010 10:04 AM

Hi Suman ,
Have you performed the connection tests for your system object ? Please share the results . Make sure that you are pointing to the correct client in your backend .
I hope you are using system alias name in the property of the iview . To me it looks that there is something wrong with system object or may be an improper configuration .
Regards
Mayank

Authorization object to view Maintain Performance Documents on MSS

Hi Experts,
Would like to know which authorization object would require to view Maintain Performance Documents on MSS. Currently, we removed SAP_ALL access from MSS user and not able to peform Maintain Performance Documents.We are on EP 7 and ECC 6.
It gives following error :
java.lang.NullPointerException
     at com.sap.xss.hr.mbo.blc.BMboStatusComp.resetGlobalMboR3Data(BMboStatusComp.java:260)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusComp.resetGlobalMboR3Data(InternalBMboStatusComp.java:195)
     at com.sap.xss.hr.mbo.blc.BMboStatusCompInterface.resetGlobalMboR3Data(BMboStatusCompInterface.java:150)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:168)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface$External.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:224)
     at com.sap.xss.hr.mbo.vac.VMboStatusComp.onBeforeOutput(VMboStatusComp.java:227)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusComp.onBeforeOutput(InternalVMboStatusComp.java:185)
     at com.sap.xss.hr.mbo.vac.VMboStatusCompInterface.onBeforeOutput(VMboStatusCompInterface.java:143)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface.onBeforeOutput(InternalVMboStatusCompInterface.java:136)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface$External.onBeforeOutput(InternalVMboStatusCompInterface.java:212)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
     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: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.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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)
Would appreciate kind guidance to resolve issue.
Thanks in advance.
Aashish

I am closing this thread as opened at wrong place.
Thanks,
Aashish

BPC 7.5NW consolidation error

Hi,
We are using BPC 7.5 NW version (7.50.04). We changed standard dimension 'GROUPS' to dimension type 'R' and included it in our legal applications.
We are using below logic to run both currency conversion and legal consolidation.
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY = %C_CATEGORY_SET%
      GROUP = %GROUPS_SET%
      TID_RA = %TIME_SET%
      RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
*RUN_PROGRAM CONSOLIDATION
    CATEGORY = %C_CATEGORY_SET%
    GROUP = %GROUPS_SET%
    TID_RA = %TIME_SET%
*ENDRUN_PROGRAM
The standard data manager package with process chain 'LEGAL_CONSOLIDATION' fails with error message 'Member "G_CG2" not exist'. G_CG2 is a member of GROUP dimension. When we executed the below logic (with hardcoded variables) in BW transaction UJKT, it worked fine and posted values correctly.
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY = C_100
      GROUP = G_CG2
      TID_RA = 2008.DEC
      RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
*RUN_PROGRAM CONSOLIDATION
    CATEGORY = C_100
    GROUP = G_CG2
    TID_RA = 2008.DEC
*ENDRUN_PROGRAM
Any idea, why system is not able to recognize 'G_CG2' when we use data manager package? In BPC 7.5NW, is it mandatory to use both 'R' and 'G' type dimensions? SAP Help has different contradictory views !!!

Hi Nilanjan,
We are using 'GROUPS' dimension of type 'R'.
The above dimension has members of both GROUPS and CURRENCY (ex: G_CG1, G_CG2, LC, USD etc).
1) Run currency translation for 'USD'. The logic works fine if i change it as follows:
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %C_CATEGORY_SET%
CURRENCY = %GROUPS_SET%
TID_RA = %TIME_SET%
RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
2) Run currency translation for 'G_CG2'. The logic works if i change it as follows:
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %C_CATEGORY_SET%
GROUP = %GROUPS_SET%
TID_RA = %TIME_SET%
RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
3) Run COI for 'G_CG2'. The logic works if i change it as follows:
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %C_CATEGORY_SET%
GROUP = %GROUPS_SET%
TID_RA = %TIME_SET%
RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
4) The logic is executed successfully from BW UJKT if i hardcode the values for 'GROUPS' dimension.

Performance Document Status Overview

We have implemented ESS/MSS on EP7.0 on ECC6.0 and for MSS --> Maintain Performance Documents, we have used a custom BSP Application. Eveything is working fine except the 'status overview' doesn't show status info under correct column for old appraisals. But it shows relevant appraisal status under correct column if we choose 2008 appraisal. By default the portal shows 2006 Performance Appraisal in the drop down but dates are showing 01/01/2010 to 31/12/2010. We've changed the date from 01/01/2006 to 31/12/2006 but still employees appraisal status are not showing under correct column. All 2006 appraisal has "Close Approved" but for all them its showing under "In Preparation" column. But when we select 2008 Performance Appraisal, they work fine.
Any ideas how to fix that? We first thought we need to upgrade to higher SP level and we applied SP12. But still the status for 2006 or any other old appraisal is not pulling right.
Can anyone help?
Thank you,

""" On the portal "Status Overview" I-View for MSS --> Maintain Performance Documents, there is a property for employee evaluation period which needs to be set to "Yes". ""
how to change this property?
under content admin????
Thanks in advance.

Error in Maintain Performance Documents under Team in MSS

Getting below error when i click Maintain Performance Documents under Team in MSS
java.lang.NullPointerException
     at com.sap.xss.hr.mbo.blc.BMboStatusComp.resetGlobalMboR3Data(BMboStatusComp.java:260)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusComp.resetGlobalMboR3Data(InternalBMboStatusComp.java:195)
     at com.sap.xss.hr.mbo.blc.BMboStatusCompInterface.resetGlobalMboR3Data(BMboStatusCompInterface.java:150)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:168)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface$External.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:224)
     at com.sap.xss.hr.mbo.vac.VMboStatusComp.onBeforeOutput(VMboStatusComp.java:227)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusComp.onBeforeOutput(InternalVMboStatusComp.java:187)
     at com.sap.xss.hr.mbo.vac.VMboStatusCompInterface.onBeforeOutput(VMboStatusCompInterface.java:143)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface.onBeforeOutput(InternalVMboStatusCompInterface.java:136)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface$External.onBeforeOutput(InternalVMboStatusCompInterface.java:212)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
     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.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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)
Regards
Karthi D

Hi Karthi,
Did u check below thread?
check the notes mentioned in that and suggested steps as it applies to your issue also
Re: MSS - Maintain Performance Document iView
Koti Reddy

MSS - Team - Performance Management - Maintain Performance Documents

Hi,
When I click on the Maintain Performance Documents the page opens and shows only one iView - 'Status Overview'. As I understand it, this page is supposed to have two iViews on it, but the other iView 'Performance Management Document' is missing. So I can see my list of employees, but when I click on them, nothing happens. Anyone else run into this problem?

Hello Kenneth,
As sujan said is right, When you click on Maintain performance Document it opens Status Overview Iview
its display list of employees , initial if you have no appraisal its display blank cell In preparation colume,
if you have appraisal it display Performance Maintain Document iView(BSP) is App - HAP_DOCUMENT with all list of option for approval.
You can also create appraisal in Create Appraisal Document in ESS.
Please points if helpful.
Please close thread if problem solved
Thankyou
Regards
Vijai

Can we add customer logo in performance document printable page in Fusion Performance management Release 9

Can we add customer logo in performance document printable page in Fusion Performance management Release 9

Yes - this is a BI Publisher report and you can edit the template to format per your customer requirements. I'd suggest that you save a copy of the changes to file because the report may or may not be overwritten during upgrades.
John

BPC 7.5NW - Client SP6 - Unable to log in to clients on older versions

REPOSTED UNDER BPC 7.5NW FORUM
Edited by: Sunil Narahari on Mar 7, 2011 2:04 PM

I'm having a similar problem with 10.5.2 Leopard server and client -- no Tiger involved.
I have the green light on the login screen and am able to log in as an OD administrator, but regular OD users are rejected with a login window shake. I never specified any home directories because they were auto-generated on machines locally when I logged in with the OD administrator.
Apple phone support were able to duplicate my problem and had me do an Enterprise Data Capture. Apple engineers were also able to duplicate my problem. Here is some of what phone support emailed me:
+I got a reply from engineering. They said they were able to duplicate the issue with a 10.5 up to a 10.5.2 client with no home directory specified. The only current workaround is to set up an automount location for home directories and specify a home location place for the users. The clients do not have to be bound to the server, they just need to have a home folder directory specified.+
+Engineering is aware of the issue and are working on it. For now this is the only workaround we have.+
I haven't had a chance to try this Apple workaround, but maybe it will help you.

Maintain Performance Documents

Hello Everyone,
The 'Maintain Performance Documents' iView appears, but nothing shows inside. I gave the users SAP_ALL and SAP_NEW and I believe all the required permissions on the portal content are set.
What can be causing this?
Regards,
Motaz

Hi,
There may two type of error. One from Portal Content and 2nd from backend content. Please check whether everything is fine from portal end. IF it is fine then check the backend role. At the time of execution of the activity please on the transaction ST01 in backend this will help you to check the authorization in backend. After finishing the activity execute transaction SU53 in backend.Check whether any error thre or not.
If everything is fine then you can ask some ABAPer to debugg the code.
Hope this will help you.
Thanks & Regards,
Sandip Biswas.

Status overview iView not refreshed for performance documents on MSS

Hi Experts,
We are using the standard portal business package for Manager Self Service. However, recently, we found out that one iView was working before suddenly stopped working. This is the Status Overview iView for Maintain Performance Documents. When searching for the performance appraisal documents for a group of direct report employees, the status overviewtable is not refreshed. Although we do have the appraisal documents in
R/3, the iView shows 0 results.
we use MSS 600 SP 8 BP
Please help.
Thanks.

Hi
Can anyone please provide an input on this.
Regards
Sasha.

MSS: Maintain Performance Documents

I am trying to implement MSS for ERP. When I click on 'Team->Maintain Performance Documents' the 'Status Overview' window opens. But when I click on the hyperlink under 'In preparation' so I can create a new appraisal, nothing happens. Anyone know why the hyperlink is not working?

Hi Kenneth,
Have you checked the Data provider under OADP in SPRO to see what service key is the 'In Planning' column mapped to. I suggest check the behavior of the service key if it has been modified.
Hope it helps,
Prathamesh

BPC 7.5NW Performance Document

Similar Messages

Maybe you are looking for