Skip to Content
0

WBS Element Planning in SAP BPC

Feb 05, 2017 at 11:38 PM

327

avatar image
Former Member

Dear team,

I would like to gather experience from those who have implemented WBS Element planning in SAP BPC.

Background

Project systems stores WBS Elements that are used in some organisations are reporting differentiation. Often there are a large number (tens of thousands) and the 'mask' has business coding to distinguish information. E.g. 'RG-1000-A-1000' could be a format, where 1000 is the Profit Centre, and 'A' relates to Capital projects.

From some limited experience with SAP PS, I am aware that most organisations do not permit the changing of WBS number after release, to avoid data integrity issues downstream. SAP will permit change of WBS number (POSID) due to the Object Number (PSPNR) being a table key.

Although it might be possible to stop users from being able to change it once released, this will still present the business with a problem in that re-coding existing projects is part of their restructure activities.

The only alternative I can see is creating new WBS Elements and moving balances which is a significant amount of effort in SAP ECC (there are thousands to be changed).

It appears that other teams have faced similar challenges before (topic is archived), but did not have BPC consider.

Problem & Question

Changing the WBS number (e.g. from RG-1000-A-1000 to RG-9999-A-1000) to reflect profit center re-structures etc.will work perfectly well in SAP, updating all reports and selections.

The implication I can see on SAP BW is that there may be data integrity issues without a full re-load of data.

Furthermore, in SAP BPC, we use the WBS Element number as a primary key, and as you will know; just because now BW has two WBS Elements (RG-1000-A-1000 and RG-9999-A-1000) does not mean that plan transnational data is modified in any way - it is still stored against the previous code.

Ideas for resolution

A 2008 SAP note identifies this as a "design problem" for BW, however although not ideal, full re-loads can resolve the problem. For SAP BPC this is a much larger problem, as data migration must be performed to 'move' data from the old WBS to the new WBS.

Your review and thoughts on the above would be most appreciated,

Regards,

Nick

capture.png (12.7 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers