Hierarchy to include WBS IM52

How can the PS Projects and WBS elements be included into creating a hierarchy using Transacion code IM52? IM is Investment Management. Can the PS Projects and WBS be included as nodes for this existing hierarchy?

Hi ,
The Positon IDs linked to Investment Programs in IM52 are assigned to WBS elements in Project Builder.
The assignment is ideally done to level 1 WBS element using EDIT > WBS element > Investment Programs.
This forms the Hierarchy for Investment Program > Position Id > WBS element.

Similar Messages

Product Hierarchy field in WBS

Hi Everyone
I have checked every where and still unable to find solution that whether can we add product hierarchy field in WBS or not? If yes then how can i?
I have already checked at spro>img reference>project systems>structures>operative structures>user interface settings> define layyout of WBS element deyail screens
But cannot get any answer or clue over there. I was wondering If the field Product heirarchy could add up (PRODH). please help

Hi Master mind,
What exactly do you mean by saying Product Hierarchy? As Ken said, its not a standard PS field. If you wish to add this field at the WBS element level you will need to go for an enhancement CNEX0007 Customer-specific fields in WBS elements
Regards
Varun

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

How do we get complete hierarchy for a WBS element??

Hi All,
Is there any FM to get complete hierarchy for a WBS element??
Or any other method that would achieve this requirement ??
Eg:
C.00103.1
C.00103.1.1
C.00103.1.2.3
C.00103.2
C.00103.2.1 etc
If i give C.00103.1, all the WBS elements in the hierarchy should be displayed.
Any pointers are of great help.
Regards
Prathima

Hi,
Available Methods
Getinfo : Read detailed information about WBS [ BAPI_PROJECT_GETINFO ]
Maintain : BAPI: Project maintenance [ BAPI_PROJECT_MAINTAIN ]
SaveReplica : Replicate work breakdown structure (ALE) [ BAPI_PROJECT_SAVEREPLICA ]
The WBS hierarchy object type defines the hierarchy of the WBSelements. A project definition always has exactly one hierarchy. If theposition of a WBS element changes, the whole hierarchy has to berebuilt. Therefore, the WBS hierarchy object type has only one command:
Create. Every WBS element receives exactly one entry in the table parameter IWbsHierarchieTable with which it defines its position.
Command: Create
Use this command to create or change a WBS element hierarchy for aproject definition. Enter the WBS hierarchy object type and the Create
command in the table of the IMethodProject parameter. The commandrefers to all entries in the table of the IWbsHierarchieTable parameterthat contains the data for the data for the hierarchy. Each entry inthe IWbsHierarchieTable refers to a WBS element that describes its position relative to the other WBS elements.
Example
- Positioning WBS elements TRAINING , TRAINING.1 and TRAINING.2 . (WBS elements TRAINING.1 and TRAINING.2 are subordinate toWBS element TRAINING. WBS element TRAINING1 is positioned on the left of TRAINING.2.)
IMethodProject
OBJECTTYPE = WBS-Hierarchy
METHOD = Create
OBJECTKEY =
REFNUMBER =
OBJECTTYPE =
METHOD = Save
OBJECTKEY =
REFNUMBER = I
ProjectDefinition
PROJECT_DEFINITION = PD-TRAINING
IWbsHierarchieTable
WBS_ELEMENT = TRAINING
PROJECT_DEFINITION = PD-TRAINING
UP =
DOWN = TRAINING.1
LEFT =
RIGHT =
WBS_ELEMENT = TRAINING.1
PROJECT_DEFINITION = PD-TRAINING
UP = TRAINING
DOWN =
LEFT =
RIGHT = TRAINING.2
WBS_ELEMENT = TRAINING.2
PROJECT_DEFINITION = PD-TRAINING
UP = TRAINING
DOWN =
LEFT = TRAINING.1
RIGHT =
Notes
Further Information
For more information, see the R/3 Library under PS Project System -> Structures -> EPS Interface
Regards,
Vijetha.

Problems with keywords assignment (hierarchy is included)

Hi group,
this probably happens after I was letting Lightroom to a catalog optimization, but I am not quiet sure about this.
So what happens: As you know, you can create a keyword tag hierarchy and sometimes LR does this automatically.
If I now do some keyword assignments in the library mode (right panel), then these keywords get replaced by a hierarchy-to-keyword string.
E.g. if I enter a keyword 'female' and LR has a hierarchy for this (e.g. female and male are sup-levels of person), then the keyword tag entry area contains the following: person > female. If e.g. I assign both male and female e to an image, then I get as result: person > female, person > male.
This blows up the list and does not make it very readable.
Does anybody knows how to stop LR doing this? If haven't found any flag value in the options.
Thanks in advance
John

John, I think this is just part of the poor design of the key-wording feature. There are many oddities. I got my initial keyword list from D65. I found that when I use the "Enter Keywords" view of the keywords assigned to a particular image, many of them show the hierarchy they are part of, as if I had selected the "Keyword & Containing Keywords" option, but some do not. Adobe told D65 that this is related to how you create the hierarchical entries. If you create a keyword and use the "Create keyword tag inside XXXXX" option, in use it will act differently than if you drag-and-drop a keyword into an hierarchical relationship. This is completely at odds with proper programming practice! I have also found today (in LR4, by the way) that if I sync from an image with keywords to an image without keywords immediately to its left, I get duplications of keywords in the rightmost image, as if the rightmost image had updated the left one, and it had reflected the sync back to the originating image. This does not happen if I sync from the leftmost image to the rightmost one. So I went into the keyword list and unchecked that keyword for the image that had the duplication. Now I have the keyword just once, but there's no check beside it in the keyword list showing that it is being used. I'm also getting duplicates of nested keywords popping up at the top level of the hierarchy. I've just realized that this has been happening for some time. The whole keyword feature is a mess. Adobe needs to:
1. fix the keyword feature so that it works in a simple, consistent and predictable manner
2. provide users with a documentation update to explain how it now works
3. provide a cleanup utility of some sort (if necessary) to let us get our keywords rationalized
Perhaps step 0. should be "stop ignoring and/or denying the keyword problem".
I've just gotten into such a mess with my latest batch of imported photos that I'm going to have to delete all assigned keywords, including those added on import, and start again. I am not amused.
JVH

Problem in Include WBS Element Screen

Actually i got some steps for CJ01(Create Project).
It is saying that after going to WBS Element Overview screen and making all the entries for WBS element and description select the INCLUDE button .
I tried a lot but i am unable to search that include button.
Please help me.

I also tried a lot but i didn't find any solution for this.
The step also says that a message will appear like(in case i have entered 6 WBS elements and after selecting INCLUDE button)
'6 WBS elements were included'
in the create project: project definition screen.
Can anyone tell me that when this type of message appears while creating WBS .

To suppress "WBS HIERARCHY" for every WBS Element Node

Hi All,
Below are WBS nodes in the report. For every node, "WBS HIERARCHY" is repeating.
WBS HIERARCHY
C-11-5210
WBS HIERARCHY
C-11-5214
WBS HIERARCHY
C-11-5216
WBS HIERARCHY
C-11-8521
WBS HIERARCHY
C-15-1000
Is there any way to suppress this, so that I can get output as follows?
WBS HIERARCHY
C-11-5210
C-11-5214
C-11-5216
C-11-8521
C-15-1000
Thanks in advance!
Ketan Zare

Hi Amer,
This is required in Analyser. But where do I find this setting in query designer?
Thank you,
Ketan Zare

Updating Prod Hierarchy field for all 2 & 3 level WBS Elements

Dear All,
My requirment is to update Prod. Hierarchy field for WBS element. Here in input i give 2 level WBS Element with respective Prod. Hierarchy then my program should update the Prod. Hierarchy for 2 level and 3 level WBS element under it automatically.
I hope we need to use bapi BAPI_PROJECT_MAINTAIN.
If any one had a sample code please reply with the attachment.
Thanks & Regards
NSK

Hi Afzal,
In which table the Left Right Up Down WBS elements are maintained.
Regards
Shashikanth Naram

WBS hierarchy not working in BAPI_PROJECT_MAINTAIN

I have created the following code. Before I added the section for the hierarchy table the structure was created ok, but with all WBS elements at level 1.
Now I have added the entries into the hierarchy table I am getting an error when I run BAPI_PROJECT_MAINTAIN.
The error message is CN 189 E - A reference object cannot be entered for the method 'Update'
I'd appreciate it if someone can see what I have done wrong.
Many thanks
Karen
Code **
wa_method_project-REFNUMBER = '00001'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs1.
append wa_method_project to i_method_project.
wa_method_project-REFNUMBER = '00002'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs2.
append wa_method_project to i_method_project.
wa_method_project-REFNUMBER = '00003'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs3.
append wa_method_project to i_method_project.
move-corresponding t_bid_definition to wa_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-PROJ_TYPE = 'BD'.
wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs1.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = t_bid_definition-DESCRIPTION.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs2.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS description 1'.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs3.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS Description 2'.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
clear wa_WBS_ELEMENT_TABLE.
wa_project_definition_upd-project_definition =
                                    t_bid_definition-PROJECT_DEFINITION.
append wa_project_definition_upd to i_project_definition_upd.
wa_method_project-METHOD     = 'Save'.
append wa_method_project to i_method_project.
clear: wa_method_project.
This is the section I added that stopped the thing working *****************
Create correct WBS Hierarchy
wa_method_project-OBJECTTYPE = 'WBS-Hierarchy'.
wa_method_project-METHOD     = 'Create'.
append wa_method_project to i_method_project.
clear: wa_method_project.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs1.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-DOWN = wbs2.
append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs2.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-UP = wbs1.
wa_wbs_hierarchie_table-RIGHT = wbs3.
append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs3.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-LEFT = wbs2.
append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
EXPORTING
    i_project_definition               = t_bid_definition
tables
    i_method_project                   = i_method_project
    I_WBS_ELEMENT_TABLE                = I_WBS_ELEMENT_TABLE
    I_WBS_HIERARCHIE_TABLE             = i_wbs_hierarchie_table
    E_MESSAGE_TABLE                    = i_bapi_message.

Here is the final code.
The Project Definition is created before you do this bit using BAPI_PROJECTDEF_CREATE which is where the entries for t_bid_definition come from.
I hope this helps
Karen
data: wbs1 type ps_posid,
      wbs2 type ps_posid,
      wbs3 type ps_posid.
clear: wbs1, wbs2, wbs3.
wbs1 = 'WBS1'.
wbs2 = 'WBS2'.
wbs3 = 'WBS3'.
wa_method_project-REFNUMBER = '00001'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs1.
append wa_method_project to i_method_project.
clear: wa_method_project.
wa_method_project-REFNUMBER = '00002'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs2.
append wa_method_project to i_method_project.
clear: wa_method_project.
wa_method_project-REFNUMBER = '00003'.
wa_method_project-OBJECTTYPE = 'WBS-Element'.
wa_method_project-METHOD     = 'Create'.
wa_method_project-OBJECTKEY = wbs3.
append wa_method_project to i_method_project.
clear: wa_method_project.
move-corresponding t_bid_definition to wa_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-PROJ_TYPE = 'XX'.
wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs1.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                    t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS 1 description'.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-WBS_PLANNING_ELEMENT = ''.
wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs2.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = ''WBS 2 description'.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs3.
wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_WBS_ELEMENT_TABLE-DESCRIPTION = ''WBS 3 description'.
append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
clear wa_WBS_ELEMENT_TABLE.
wa_project_definition_upd-project_definition =
                                    t_bid_definition-PROJECT_DEFINITION.
append wa_project_definition_upd to i_project_definition_upd.
Create correct WBS Hierarchy
wa_method_project-OBJECTTYPE = 'WBS-Hierarchy'.
wa_method_project-METHOD     = 'Create'.
append wa_method_project to i_method_project.
clear: wa_method_project.
wa_method_project-METHOD     = 'Save'.
append wa_method_project to i_method_project.
clear: wa_method_project.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs1.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-DOWN = wbs2.
ppend wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs2.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-UP = wbs1.
wa_wbs_hierarchie_table-RIGHT = wbs3.
append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
wa_wbs_hierarchie_table-WBS_ELEMENT = wbs3.
wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                  t_bid_definition-PROJECT_DEFINITION.
wa_wbs_hierarchie_table-UP = wbs1.
wa_wbs_hierarchie_table-LEFT = wbs2.
append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
clear wa_wbs_hierarchie_table.
CALL FUNCTION 'ZBAPI_PROJECT_MAINTAIN'
EXPORTING
    i_project_definition                = t_bid_definition
tables
    i_method_project                   = i_method_project
    I_WBS_ELEMENT_TABLE     = I_WBS_ELEMENT_TABLE
    I_WBS_HIERARCHIE_TABLE = i_wbs_hierarchie_table
    E_MESSAGE_TABLE            = i_bapi_message.
Message was edited by:
        Karen Dean

0WBS_ELEMT hierarchy through MDX universe populating random values in WebI

Hi Experts,
We are facing an issue in WebI 3.1, while creating a report on top of MDX universe with 0WBS_ELEMT hierarchy - coming from BEx query. All other hierarchies in other reports are working fine, but the issue seems to be particular to 0WBS_ELEMT hierarchy.
First of all, the WebI does not includes full project entries along with WBS hierarchy - this could be a limitation (2nd comment in https://cw.sdn.sap.com/cw/ideas/2084#comment-14280), and we found workaround as to display in seperate block.
Now the actual issue is, even hierarchy nodes of WBS element are not coming properly in the WebI. There are 5 nodes in universe (L00 to L04). We dragged all of them into the report and found that some nodes are missing. These are the L01 nodes which are not having any subordinate nodes.
Tried different combitions, and later found that if we are not keeping the nodes L02 to L04 in the query, all missing entries (in first report) are coming, but now some other nodes are getting dissapeared.
Can anyone tell the reason and/or solution for the issue. Is this the known issue with 0WBS_ELEMT hierarchy? If so, what SAP is recommending for this? This is really urgent, reply.
Regards,
Kshiteesh

Hi Henry,
Thanks for reply.
We are on BI 7.1 SP 07. We are having other hierarchies working in expected manner, but only WBS element hierarchy is having issue.
After posting to SDN, I saw some other posts on the forum and checked the note 1446246. This note points to others notes, and 2 notes (0001562173 - flattening unbalanced hierarchies & 1432162 - MDX Flattening problems when using hierarchies) which seems to be relevant.
It seems to be case of unbalanced hierarchies, but to be sure please suggest if we can go with these notes.
Regards,
Kshiteesh

What is the Tcode for WBS Hierarchies in R/3

Hi All,
What is the Tcode for WBS Hierarchies in R/3? and more over how can we include WBS element groups in our bw reports.
and one more does any relation between WBS element Hierarchy and WBS element Group
Regards,
Sekhar

Hi Shekar
CJE0    Run Hierarchy Report
CJE1    Create Hierarchy Report
CJE2    Change Hierarchy Report
CJE3    Display Hierarchy Report
In a work breakdown structure (WBS), you describe the individual tasks and activities in the
project as individual elements in a hierarchy.
Depending on the phase of your project, you continue to break down the tasks and activities in
your project, step-by-step, until you reach the level of detail necessary to carry it out.
The individual elements represent activities within the work breakdown structure. The elements
are called work breakdown structure elements (WBS elements) in the Project System. WBS
elements can be:
Tasks
Partial tasks which are subdivided further
Work packages

How to show the right ps-budget in an hierarchy

Hi Gurus,
I have got a question regarding to Budget for PS. We are loading this data (0CO_OM_WBS_8) to a Cube and
also load the hierarchy for the WBS-Element. The budget logic is that a budget of a certain level will be included
in the level above. For example, Level 3 gets a budget of 500,- EUR, then this 500,- EUR will also be booked to
level 2 and level 1. If I now create a query with the hierarchy for the wbs element, it sums the values over the hierarchy levels so that I get 1000,- EUR on level 1. What do I have to do to solve this problem ???
Level 1   1000,-
|----
> Level 2 500,-
                  |----
> Level 3   500,-
thanks for your contribution in advanced.
Daniel

Hi SDBI,
I am working with a characteristic hierarchy and the level are not adjacent to each other. The problem is that the
CO bookings on level 3 will be also included on level 2 and level 1 and therefore I can not use the sum function
of the hierarchy. Is there any other logic I can use ???
My example was not right here again.
Data in the cube
WBS-Element     Level    0Amount
PADE03.211.3      L3       1000, -
PADE03.211.2      L2       1500,-    (1000 from L3 + 500 spend on l2)
PADE03.211.1      L1       1500,-    (1000 from L3 + 500 from L1, no budget on L1)
Display in Hierarchy
PADE03.211.1   L1 4000,-
*PADE.03.211.2 L2 2500,-
**PADE 03.211.3   L3   1000,-
but I would like a display like
PADE03.211.1   L1 1500,-
*PADE.03.211.2 L2 1500,-
**PADE 03.211.3   L3   1000,-
Daniel
Edited by: Weilbacher Daniel on Jul 6, 2008 7:53 PM

Using a hierarchy but also showing work orders that are not in hierarchy

good morning bi people,
i have a requirement to show data from a hierarchy which includes Operation and Maintenance information. for example it has an account broken into labour/material/trucking and below this is the pm acivity type and secondary cost element (concatenated). this hierarchy is a manually created hierarchy that is uploaded to BW and is not in ECC. The users do not want to see the concatenated field at the end of the hierarchy, but instead, want to see the Work Orders that have the PM activity types.
At the present time, we have the report using the hierarchy but we need the work orders to replace the pm activity type/secondary cost element concatenated field. the work order field is a free characteristic and when we drag in the work order in analyzer, it works correctly.
1) is this possible to use the hierarchy and somehow map the work order field to the end of the hierarchy within crystal?
2) do you have a suggestion to change the hierarchy, without being a manual nightmare?
all conversations are welcome.
Erik

Good Day Ingo,
i have created a word document with screen shots of the hierarchy from BW, a screen shot of the BEx showing the free characteristic of Maintenance Order and a screen shot of the crystal report with the PM Activity type concatenated to the Cost Element. Once again, we do not wish to see the concatenated field, but rather see the Maintenance orders that have a PM Activity type the same as the concatenated field.
here is the link.
https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B1j5hXTptfntYWI1MDUzNGEtY2MxNy00YmMzLWJjZjEtZDA4OGZiYmMyNzFh&hl=en&authkey=CKq4xcgJ
thanks Ingo,
Erik

Error from loading Hierarchy data from BW

I am following the BPC NW online help to load the costcenter master data from BW, The members were successfully loaded, but
when I tried to load the hierarchy, I received the following message"
Task name HIERARCHY DATA SOURCE:
Info: Hierarchy node includes text node or external characteristics
Record count: 50
Task name CONVERT:
No 1 Round:
Record count: 50
Accept count: 50
Reject count: 0
Skip count: 0
Task name HIERARCHY DATA TARGET:
Hierarchy nodes include dimension members that do not exist
Submit count: 0
Application: CONSOLIDATION Package status: ERROR
I am pretty sure that all the dimension members were loaded in this herarchy. Since the hierarchy node I am trying to load only include 2 level, I have only 49 base member and 1 node which I can see from the BPC admin after master data,following is the.tranformation and conversion file:
*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER = ,
AMOUNTDECIMALPOINT = .
SKIP = 0
SKIPIF =
VALIDATERECORDS=YES
CREDITPOSITIVE=YES
MAXREJECTCOUNT=
ROUNDAMOUNT=
*MAPPING
NODENAME=NODENAME
HIER_NAME=HIER_NAME
PARENT=PARENT
ORDER=ORDER
IOBJNM=IOBJNM
VERSION=VERSION
*CONVERSION
HIER_NAME=HIER_NAME.xls
NODENAME=HIER_NAME.xls!NODE_NAME
PARENT=HIER_NAME.xls!NODE_NAME
CONVERION TAB:
EXTERNAL     INTERNAL     FORMULA
CC_Her     PARENTH1             where CC_Her is the name of the gerarchy in BI
NODENAME TAB:
EXTERNAL     INTERNAL     FORMULA
*     js:%external%.toString().replace(/\s+/g,"")
Did I miss anything?
Edited by: Jianbai on Jan 18, 2011 9:57 PM
Edited by: Jianbai on Jan 19, 2011 12:29 AM

Hi Jianbai,
The following link describes the steps to import master data/hierarchies from SAP BW into SAP BPC 7.5 NW..
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?quicklink=index&overridelayout=true
Hope this helps!
Thanks
BSV

Parent Child Hierarchy causes numbers to be different

Hello,
We have a parent child hierarchy in our chart of account dimensions. When the hierarchy is included in an analysis, the numbers are correct. If the hierarchy is not included in the analysis and a column from the dimension with the hierarchy is included, the numbers are very different. They are overstated by a large amount.
For Example, I have two analysis:
-In the first analysis the hierarchy is included and the grand total is 2,383,080,784.
-The second analysis has simply excluded the hierarchy from the analysis and the total shoots all the way up to 6,901,729,527.
I have screen shots but don't know how to include them in this kind of a post.
Has anybody else seen such behavior? This seems like it would be a big deal so either we are doing something wrong or this is a bug that needs fixed.
We are on 11.1.1.6
Thanks in advance,
Brian

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

Hierarchy to include WBS IM52

Similar Messages

Maybe you are looking for