BCWP Not Updating on Project Server 2010 PDP

Ajukan pertanyaan

11 Oktober 2011 22:39

0

I have a PDP that I have configured to include CPI, SPI, BCWP, ACWP, EAC, VAC, and other fields. Although all fields are updated and display properly in Project Pro, their behavior on the PDP is strange. The CPI and SPI do not pull in values until the PDP is edited and saved. More disappointing is that the BCWP value is never loaded into the field -- regardless of saving the PDP or otherwise. I'm looking for insights into what may be going astray here, and what I need to investigate. Thanks.

Jim
JB Fink
- Balas
- Kutip

Semua Balasan

11 April 2012 16:16

0
Indeed, I have almost the same symptoms: (except CPI and SPI: theys are working properly...)

(I did the test with CU Oct 2011)

Regards
Wim
- Diedit oleh Wim Van Den Bergh [MCTS] 11 April 2012 16:16
- Balas
- Kutip
16 Mei 2012 19:47

0

Wim, have you had any luck in correcting the issue you're seeing?

Jim
JB Fink
- Balas
- Kutip
17 Mei 2012 7:31

0
Jim & Wim,

I had the similar issue on PS2010 (RTM , as well as SP1+June CU2011) PDP page which doesn't show BCWP/BCWS values on that. To troubleshoot more, Initially, I thought that data is not updated or corrupted in Published database so tested with few queries in Published/draft & Reporting. Unfortunatley, data was all correct but somehow while PDP page doesn't get that while loading.
```
--In Reporting database
select t.ProjectUID,p.ProjectName,t.TaskUID, t.TaskIndex, t.TaskACWP, t.TaskBCWP, t.TaskBCWS 
from  dbo.MSP_EpmTask_UserView t
 JOIN MSP_EpmProject p
 ON t.ProjectUID = p.ProjectUID 
 where TaskBCWP<>0 AND TaskBCWS <>0
AND p.projectUId = '84EEAB2E-B301-4529-8937-22CC6CA133DE'
AND t.TaskIndex =0
-- In published database
SELECT A.PROJ_UID, A.PROJ_NAME, B.TASK_UID, b.Task_ID,B.TASK_NAME, B.TASK_ACWP, B.TASK_BCWP, B.TASK_BCWS
 FROM MSP_PROJECTS A, 
MSP_TASKS B, MSP_TASK_BASELINES 
WHERE A.PROJ_INFO_STATUS_DATE IS NOT NULL AND A.PROJ_UID = B.PROJ_UID 
AND B.TASK_UID = MSP_TASK_BASELINES.TASK_UID 
AND MSP_TASK_BASELINES.TB_BASE_NUM = 0 AND (task_outline_level LIKE '0') 
AND A.PROJ_UID = '84EEAB2E-B301-4529-8937-22CC6CA133DE'
```
Luckily, I was working on a customized pdp page, so I was able to pull the values in reporting store without any issues as a workaround.

May be not lot of user reported this to Microsoft. Also, I have not tested this with Feb/Aril 2012 CU. Hope MS or someone who was able to do this, will provide an update. Just thought to provide a workaround not the fix.

If you found this post helpful, Please "Vote as Helpful";. If it answered your question, Please "Mark as Answer".
Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
- Diedit oleh Amit Khare - Project Management Consultant 17 Mei 2012 7:33
- Balas
- Kutip
18 Mei 2012 15:55

Moderator

0

You could always use an InfoPath query against the RDB as a workaround I suppose:

http://azlav.umtblog.com/2011/05/04/making-a-read-only-pdp-with-infopath-forms/
Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
- Balas
- Kutip
18 Mei 2012 15:56

Moderator

0
Actually, come to think of it....

Just create an Enterprise Custom Field called BCWP2 and set it to =[BCWP]. Add BCWP2 to the PDP.

That might be a bit simpler. :-)
Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
- Ditandai sebagai Jawaban oleh Brian Smith - MSFTMicrosoft Employee, Moderator 22 Mei 2012 22:34
- Balas
- Kutip
19 Mei 2012 11:23

0

Agreed Andrew simple by using a calculated CF but BCWP/ BCWS display seems to be bug? isn't it?
If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”. Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
- Balas
- Kutip
20 Mei 2012 1:38

Moderator

0

Sounds like a bug to me....
Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
- Balas
- Kutip
22 Mei 2012 22:34

Pemilik

1

Sounds like it could be - but just a reminder that just mentioning on the forums doesn't mean that a 'bug' will miraculously be fixed in a future cumulative update. If this is something you would like to see reviewed and potentially changed then best to leverage your Premier support contracts. However, looks like there is at least a workaround for this one.

Best regards,

Brian.
Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
- Balas
- Kutip