Question:
Has anyone successfully loaded a .csv contatining hierarchy data into 3.0B?
In referencing McDonald's book, "Mastering the SAP Business Information Warehouse", page 141, we have concluded that our hierarchy has 6 levels and is a network hierarchy-stored. The 6 levels are Sales Org, Div, Broker, Zone, Region, District.
The .csv data is as follows:
NODEID,IOBJNUM,NODENAME,LINK,PARENTID,CHILDID,NEXTNODE,DATEto,DATEfrom
1,0HIER_NODE,~ROOT,,0,,,20001111,20991231
2,ZSALESORG,5410, ,1,3, ,20001111,20991231
3,ZSLS_DIV,53, ,2,5,4,20001111,20991231
4,ZSLS_DIV,52, ,2,, ,20001111,20991231
5,ZBROKER,22, ,3,8,6,20001111,20991231
6,ZBROKER,334, ,3,9,7,20001111,20991231
7,ZBROKER,209, ,3,10,,20001111,20991231
8,ZZONE,6, ,5,11,9,20001111,20991231
9,ZZONE,6,X,6,12,10,20001111,20991231
10,ZZONE,1, ,7,13,,20001111,20991231
11,ZREGION,6, ,8,,12,20001111,20991231
12,ZREGION,18, ,9,,13,20001111,20991231
13,ZREGION,12, ,10,14,,20001111,20991231
14,ZDISTRICT,12, ,13,,,20001111,20991231
15,ZBROKER,250, ,3,17,16,20001111,20991231
16,ZBROKER,40, ,3,18,,20001111,20991231
17,ZZONE,3, ,15,19,18,20001111,20991231
18,ZZONE,1,X,16,20,,20001111,20991231
19,ZREGION,3, ,17,,20,20001111,20991231
20,ZREGION,14, ,18,,,20001111,20991231
Answer:
I have loaded hierarchies thru flat files in 3.0B with no problems. In your file, the root node has childid and nextid both empty, so the hierarchy is empty.
Answer:
just be aware that if you create your file using excel then you may have problems. I believe that Excel has a problem creating .CSV files correclty to be read by any other system. Try going to the last line and to the end of the line and pressing del to ensure it knows its at the end of the file. Also try saving the file in Access then exporting to a .csv file i think Access works better.
_________________
life only sucks when you let it get that way!
Answer:
In your file the header row states Dateto before Datefrom, but your data is actually the other way around - Datefrom then Dateto.
Answer:
Thanks to all who have replied. I have now loaded data in the PSA and have even more questions. Any assistance would be greatly appreciated.
What should this hierarchy look like in the PSA?
5410 .................Org
53 52 .............Divisions, 52 has no children
6 .......................Zone
6 .......................Region
12......................District
22......................Broker
There’s a couple of other hitches, too:
- Zone, region and district are in R/3 and BW (because we extracted from R/3) prefixed by the Sales Org and Division, like 54105306 for Zone 06, where 5410 is the Org and 53 is the Division.
Region 6 is stored like 54105306.
- However, Division is referencing Customer Group for Zone, Region and District vs. referencing a newly created “sales division” for the Division level (53, 52).
Essentially then, the PSA contains the following data:
First line, has 1 entry under Sales Org ......5410
2nd line, has 1 entry under our newly created division (ZSLS_DESIG) .......53
3rd line, has 1 entry under our newly created division (ZSLS_DESIG) .......52
4th line, has 3 entries, 1 under Sales org ...5410, 1 under CustomerGroup ....53 and 1 under Zone ...06
5th line, has 3 entries, 1 under Sales org ...5410, 1 under CustomerGroup ....53 and 1 under Region ...06
6th line, has 3 entries, 1 under Sales org ...5410, 1 under CustomerGroup ....53 and 1 under District ...12
7th line has 1 entry under Broker .... 22