Hierarchy level for Site hierarchy idoen't load in BI

Hi gurus,
I have created a new hierarchy level for Site hierarchy in transaction CL01 in R/3. But this level is not load in BI.
Site hierarchy and other levels load right, but no the new one.
Do you now anything to resolve my issue?
Any feedback will be really appreciated.
Thanks

Hi,
I think,you have to follow the old concept only.
Gana.

Similar Messages

Display different level for same hierarchy value in BO 4.0

Hi Expert,
I have one question for Webi for BO 4.0
We have one hierarchy in BW side and we hope to display differet level in same report for different column
For example, column A is for level 6. column B is for level 7.
Do you know how to releaze this in Webi side?
In the 3.X version, we have different dimension for different level.
But now in BO 4, it has been combined into one\
Thanks and best regards
Alex yang

Hi,
You can still do this in BI 4.0, if you use the old 'legacy' MDX OLAP.unv from Universe Designer tool .
Yes, with the BICS connection, you are getting a native hierarchy, as it would be displayed in an OLAP environment.
Cheers,
H

Unable to see hierarchy nodes for a hierarchy in Query designer

For IO 0GL_ACCOUNT, we have many hierarchies defined.
In the query designer when i am trying to restrict the 0GL_ACCOUNT with one of the hierarchy say Hier1 the corresponding hierarchy nodes should be displayed so that i can select any nodes of my choice and can restrict.
Strangley instead of showing hierarchy nodes,it is showing" [ ]" with out any values.Checked in RSA1 ,the hierarchy with all nodes visible perfectly.No authorization settings created on any of these hierarchies.
hierachy is in active state.
Appreciate any suggestions on this.
Regards,
Swapna.G

Before restricting you need to select hierarchy for the characterstic and tick the activate hierarchy display checkbox

Best Practice - HLevel for Alternate Hierarchy

Good morning,
Our Account dimension contains both a standard and alternate hierarchy. We currently use the HLevel property to drive a variety of formatting (hierarchy indentations, outline for "data bottom", bold for "parent", etc.). The formulas we've developed for the standard hierarchy work well, but they don't always work with the alternate hierarchy. I'm considering the creation of a new "Alt_HLevel" property that would contain the associated numerical hierarchy levels for the alternate. This would provide a level of simplicity in reporting as it would allow us to use consistent formulas. Downside is the added maintenance. Before proceeding, I'd like to know if anyone has a better solution. Thanks!

Hi Kim,
As far as my understanding says, HLEVEL will work with the 1st hierarchy of your dimension. So, if you want, you can definitely go ahead by adding another property for the second hierarchy. But yes, as you have already figured out, the cost would be at the maintenance. If you are having regular additions to your dimension, it might be difficult to maintain this property. If the addition of members is not frequent, then I dont see any challenge.
Alternatively, you can try using H2 when you are calling the HLEVEL property. I have never checked this, so not sure whether it will work or not. But worth trying.
Hope this helps.

Level in product hierarchy ??

Hi
Some body can explain me about the levelin product hierarchy ??
Diefinition of level ?
Purpose of level??
Thanks

Product Hierarchy:
Product hierarchies are the domain of materials management. A product hierarchy is assigned to the material master record. This hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. This hierarchy number may have a maximum of 18 digits with a maximum of 9 levels. The custom Product hierarchies can be maintained in V/76.
Product Hierarchy Number of chars at Various level
In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9.
You can define hierarchy nodes at the individual levels of the product hierarchy.
The product hierarchy can be structured via DDIC structure PRODHS. In the standard system, a product hierarchy can be created with up to three levels. The individual levels can contain the following number of digits:
Level number of allowed digits
1 5
2 5
3 8
This can be changed as of Release 3.0, where it is possible to extend the maximum number of levels to 9.
If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows:
1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length).
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS.
You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3. Proceed as follows:
Create the following domains:
ZPRODH3 with length 5, category CHAR,
ZPRODH4 with length 3, category CHAR,
Change structure PRODHS:
Structure PRODHS in the standard system:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
Changes according to example:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 5
ZZPRODH4 PRODH4 CHAR 3
please take help of ABAPER in extending the levels of Product hierarchy
Configure for Product hierarchy at
SPRO -> IMG -> Logistics - General -> Material Master -> Settings for Key Fields -> Data Relevant to Sales and Distribution -> Define Product Hierarchies

Defining hierarchy level keys

Hi,
What is the best practice regarding the level keys (used in the hierarchy level for dimensions)?
I had a problem with the numbers shown because the level key contained values with a mix of letters and numbers. If the level key only contains letters or numbers it worked as it should, but once there was a mix like this
0101
X010
the numbers for the balance sheet came out wrong (combined with a level based measure though).
To me it seems like the level keys ALLWAYS should be in Numbers but this is not stated anywhere. Only by experience. I have searched the forum for this but could not find any exact hit.

Hi,
I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
This is urgent. Any help will be most appreciated.
Thanks in advance.

Hierarchy Level Limit in BPC 5.1 Reports

Hello,
We are currently running BPC 5.1 SP7 and have a Account Hierarchy that has 15 levels. In the standard trend report, the control panel contains a drop-down list for rows and columns but is limited to 9 levels.
So we found the following formula in the row/column expansion and changed cell F21 which references the drop-down list of levels to "15".
=IF($F$26="ON",EVEXP($C$17,$F$19,C47:C58,D47:P58,TRUE,$C$2,$F$21,F22,$E$2),"OFF")
1. Is it ok to retrieve data at 15 levels down?
2. Does it slow down reporting? Is there any negative impact of doing this?
3. Is there a limit on the number of levels that a hierarchy can have?
We understand that we need to re-save all of these templates again in the wizard folder and increase the template version to trigger a download of the update.
Thank You,
Nikunj
Edited by: Nikunj Patel on Jun 5, 2009 2:49 PM

Limits of Hierarchy Levels for the dimension are bound by the size of the table (at least in the SQL version). So, if you have many levels, this plus the number of properties and their size will determine the amount of space taken up in the SQL table, which if exceeded, will drop the information.
So, the answer is; No there isn't a limit, and it should not slow your performance, but "YES" the is a limit depending on the size of the dimension components. There may still be a dimension calculator for size in the HELP files in the Admin console in version 5.1.
Hope this helps.

Hierarchy INT for 0GLACCEXT (Financial statement item)

Dear Friends,
I have a situation where i am modifying a standard BC query 0FIGL_VC1_Q0002 and i have to find equivalent nodes (equivalent to the standard SAP INT hierarchy) in my custom hierarchy for 0GLACCEXT (financial statement item). BW has a standard hierarchy INT for 0GLACCEXT (with nodes as numbers for example 3070000, 2030000 etc). With the custom hierarchy in my case how do i find the equivalent hierarchy nodes for this hierarchy while working with this query?
Any help would be highly appreciated.
Thanks
Raj

First of all, U cannot get balance sheet and income statement reports on DSO level... or even at cube level (0FIGL_C10)
Balance sheet and income statement logic is manipulated in function Module (RS_BCT_FIGL_DATA_GET_VC10) that pulls data from 0FIGL_C10 to 0FIGL_V10... Thats the reason why SAP provided all Balance sheet and income statement reports on 0FIGL_V10.. And u can see 0GLACCEXCT in 0FIGL_V10, but not in 0FIGL_C10, which provides income statements at aggregation (totals) level, but not at granular level..
Looks like u r trying for something (keeping 0GLACCEXT in 0FIGL_O10) which is not possible... If u want much detailed level of reports, u can create jump targets (RRI) from 0FIGL_V10 reports to 0FIGL_O10 reports (if u create any)

856 ASN Hierarchy level Mapping

HI Friends,
I need one help regarding ASN Mapping...
I want to map the below structure from IDOC to 856 ASN Map.
The Idoc Hierarchy Structure is
- Shipment ( repeats 1 time)
- Order ( repeats multiple time)
- Tare (Pallet) ( repeats multiple time)
- Pack (Case) ( repeats multiple time)
- Item ( repeats multiple time)
The EDI Hierarchy Structure is
G_HL ( 1 to many time - as group)
-HL ( 1 time)
I want to map (represent )the each Hierarchy level of Idoc hierarchy structure in the EDI HL segement.
How can i achive it...
Any help will be greatly appreciated....
Regards
Venkatesh

Hi Ravi, Ramu and Venkat,
I cant duplicate the G_HL segment.As because each level is dependent on above level.
like example
If input contains this data
Shipment SHP1
Orders ORD1
Tare TARE1
Pack PCK1
Item ITEM1
Item ITEM2
Pack PCK12
Item ITEM11
Item ITEM12
Orders ORD2
Tare TARE21
Pack PCK21
Item ITEM21
Item ITEM22
Tare TARE22
Pack PCK22
Item ITEM23
Item ITEM24
I want output to be generated like this
Note below REF segment is just reference..HL contains many segments...
HL1S
REF*SHP1
HL2O
REF*ORD1
HL3T
REF*TARE1
HL4P
REF*PCK1
HL5I
REF*ITEM1
HL6I
REF*ITEM2
HL7P
REF*PCK12
HL8I
REF*ITEM11
HL9I
REF*ITEM12
HL10O
REF*ORD2
HL11T
REF*TARE21
HL12P
REF*PCK21
HL13I
REF*ITEM21
HL14I
REF*ITEM22
HL15T
REF*TARE22
HL16P
REF*PCK22
HL17I
REF*ITEM23
HL18I
REF*ITEM24
If i duplicate the HL levels then i wont get the output in the above seqenece...I will get all Orders, Tare ,Packs and Items one by one...It wont work...
Regards
Venkatesh

Loading Hierarchy levels as Navigational Attributes of 0MATERIAL.

Hello Guys, 
bit of background about the issue: 
I am loading 0MATERIAL hierarchy from ECC using 0MATERAIL_LKLS_HIER Data source.(IS Retail). this job runs very fast.
We have a 8 level hierarchy in ECC/BI and the lowest level of hierarchy is 0MATERAIL. I am also loading 0MATERIAL_ATTR from ECC. While loding 0MATERAIL_ATTR into BI, i need to populate each hierarchy level of an artcile as navigation attributes of 0MATERIAL. 
For this requiremetn i wrote a start routine in the update rules and reading hierarchy levels and node names from /BI0/HMATERIAL table. the problem is the performance of the extractor is very very poor. It runs for more than 10 hours every day and it is causing many problems for our transactional data loads. 
Here is the code i am using in my start routine. 
I need suggestions on improving the performance of this extractor asap. are there any other best practices to load Article hierarchy levels as attributes apart from using ABAP lookups?? any help will be appreciated. 
TYPES: BEGIN OF TY_HIER, 
 MATERIAL TYPE /BI0/OIMATERIAL, 
 HIER_LEVEL1 TYPE RSSHNODENAME, 
 HIER_LEVEL2 TYPE RSSHNODENAME, 
 HIER_LEVEL3 TYPE RSSHNODENAME, 
 HIER_LEVEL4 TYPE RSSHNODENAME, 
 HIER_LEVEL5 TYPE RSSHNODENAME, 
 END OF TY_HIER. 
DATA: GT_HIER TYPE STANDARD TABLE OF TY_HIER, 
 WA_HIER TYPE TY_HIER. 
DATA: LT_MAT_HIER TYPE STANDARD TABLE OF /BI0/HMATERIAL, 
 WA_MAT_HIER TYPE /BI0/HMATERIAL, 
 wa_hier TYPE ty_hier. 
DATA: l_nodename TYPE rsshnodename. 
* Retrieving the whole hierarchy table into an internal table 
SELECT * FROM /BI0/HMATERIAL INTO TABLE LT_MAT_HIER. 
* Looping at the data package 
LOOP AT DATA_PACKAGE. 
 WA_HIER-MATERIAL = DATA_PACKAGE-MATERIAL. 
* Sort internal table for binary search 
 Sort LT_MAT_HIER by iobjnm nodename. 
 READ TABLE LT_MAT_HIER 
 INTO WA_MAT_HIER WITH KEY IOBJNM = '0MATERIAL' 
 NODENAME = DATA_PACKAGE-MATERIAL 
 binary search. 
 Sort LT_MAT_HIER by nodeid. 
 WHILE WA_MAT_HIER-TLEVEL > 1. 
 READ TABLE LT_MAT_HIER 
 INTO WA_MAT_HIER WITH KEY NODEID = WA_MAT_HIER-PARENTID 
 binary search. 
* IF SY-SUBRC = 0. 
 SHIFT WA_MAT_HIER-NODENAME BY 3 PLACES LEFT. 
 CASE WA_MAT_HIER-TLEVEL. 
 WHEN '07'. 
 CONTINUE. 
 WHEN '06'. 
 WA_HIER-HIER_LEVEL5 = WA_MAT_HIER-NODENAME. 
 WHEN '05'. 
 WA_HIER-HIER_LEVEL4 = WA_MAT_HIER-NODENAME. 
 WHEN '04'. 
 WA_HIER-HIER_LEVEL3 = WA_MAT_HIER-NODENAME. 
 WHEN '03'. 
 WA_HIER-HIER_LEVEL2 = WA_MAT_HIER-NODENAME. 
 WHEN '02'. 
 WA_HIER-HIER_LEVEL1 = WA_MAT_HIER-NODENAME. 
 WHEN OTHERS. 
 CONTINUE. 
 ENDCASE. 
 ENDWHILE. 
 APPEND WA_HIER TO GT_HIER[]. 
 CLEAR WA_HIER. 
ENDLOOP. 
SORT GT_HIER BY MATERIAL.
 
Thanks in advance 
Cheers 
POPS 

Any other thoughts guys...
is there a standard function module where we can specify the lowest level article detail as input and request for level 1 - 5 values ??

Aggregating data loaded into different hierarchy levels

I have some problems when i try to aggregate a variable called PRUEBA2_IMPORTE dimensinated by time dimension (parent-child type).
I read the help in DML Reference of the OLAP Worksheet and it said the follow:
When data is loaded into dimension values that are at different levels of a hierarchy, then you need to be careful in how you set status in the PRECOMPUTE clause in a RELATION statement in your aggregation specification. Suppose that a time dimension has a hierarchy with three levels: months aggregate into quarters, and quarters aggregate into years. Some data is loaded into month dimension values, while other data is loaded into quarter dimension values. For example, Q1 is the parent of January, February, and March. Data for March is loaded into the March dimension value. But the sum of data for January and February is loaded directly into the Q1 dimension value. In fact, the January and February dimension values contain NA values instead of data. Your goal is to add the data in March to the data in Q1. When you attempt to aggregate January, February, and March into Q1, the data in March will simply replace the data in Q1. When this happens, Q1 will only contain the March data instead of the sum of January, February, and March. To aggregate data that is loaded into different levels of a hierarchy, create a valueset for only those dimension values that contain data. DEFINE all_but_q4 VALUESET time
LIMIT all_but_q4 TO ALL
LIMIT all_but_q4 REMOVE 'Q4'
Within the aggregation specification, use that valueset to specify that the detail-level data should be added to the data that already exists in its parent, Q1, as shown in the following statement. RELATION time.r PRECOMPUTE (all_but_q4)
How to do it this for more than one dimension?
Above i wrote my case of study:
DEFINE T_TIME DIMENSION TEXT
T_TIME
200401
200402
200403
200404
200405
200406
200407
200408
200409
200410
200411
2004
200412
200501
200502
200503
200504
200505
200506
200507
200508
200509
200510
200511
2005
200512
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
2004 NA
200412 2004
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
2005 NA
200512 2005
DEFINE PRUEBA2_IMPORTE FORMULA DECIMAL <T_TIME>
EQ -
aggregate(this_aw!PRUEBA2_IMPORTE_STORED using this_aw!OBJ262568349 -
COUNTVAR this_aw!PRUEBA2_IMPORTE_COUNTVAR)
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 4,00 ---> here its right!! but...
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00 ---> here must be 30,00 not 10,00
200512 NA
DEFINE PRUEBA2_IMPORTE_STORED VARIABLE DECIMAL <T_TIME>
T_TIME PRUEBA2_IMPORTE_STORED
200401 NA
200402 NA
200403 NA
200404 NA
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 NA
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00
200512 NA
DEFINE OBJ262568349 AGGMAP
AGGMAP
RELATION this_aw!T_TIME_PARENTREL(this_aw!T_TIME_AGGRHIER_VSET1) PRECOMPUTE(this_aw!T_TIME_AGGRDIM_VSET1) OPERATOR SUM -
args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES
AGGINDEX NO
CACHE NONE
END
DEFINE T_TIME_AGGRHIER_VSET1 VALUESET T_TIME_HIERLIST
T_TIME_AGGRHIER_VSET1 = (H_TIME)
DEFINE T_TIME_AGGRDIM_VSET1 VALUESET T_TIME
T_TIME_AGGRDIM_VSET1 = (2005)
Regards,
Mel.

Mel,
There are several different types of "data loaded into different hierarchy levels" and the aproach to solving the issue is different depending on the needs of the application.
1. Data is loaded symmetrically at uniform mixed levels. Example would include loading data at "quarter" in historical years, but at "month" in the current year, it does /not/ include data loaded at both quarter and month within the same calendar period.
= solved by the setting of status, or in 10.2 or later with the load_status clause of the aggmap.
2. Data is loaded at both a detail level and it's ancestor, as in your example case.
= the aggregate command overwrites aggregate values based on the values of the children, this is the only repeatable thing that it can do. The recomended way to solve this problem is to create 'self' nodes in the hierarchy representing the data loaded at the aggregate level, which is then added as one of the children of the aggregate node. This enables repeatable calculation as well as auditability of the resultant value.
Also note the difference in behavior between the aggregate command and the aggregate function. In your example the aggregate function looks at '2005', finds a value and returns it for a result of 10, the aggregate command would recalculate based on january and february for a result of 20.
To solve your usage case I would suggest a hierarchy that looks more like this:
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
200412 2004
2004_SELF 2004
2004 NA
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
200512 2005
2005_SELF 2005
2005 NA
Resulting in the following cube:
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
200412 NA
2004_SELF NA
2004 4,00
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
200512 NA
2005_SELF 10,00
2005 30,00
3. Data is loaded at a level based upon another dimension; for example product being loaded at 'UPC' in EMEA, but at 'BRAND' in APAC.
= this can currently only be solved by issuing multiple aggregate commands to aggregate the different regions with different input status, which unfortunately means that it is not compatable with compressed composites. We will likely add better support for this case in future releases.
4. Data is loaded at both an aggregate level and a detail level, but the calculation is more complicated than a simple SUM operator.
= often requires the use of ALLOCATE in order to push the data to the leaves in order to correctly calculate the aggregate values during aggregation.

Change Hierarchy default level for PS Reports

Hi,
Can anyone advise how I can change the default hierarchy level when running a report painter report?
I would like the hierarchy level set to 4, so when I execute the report the display expands upto the network level.
I've tried to find settings in CJE2 and CJE5, but the herarchy maintenance was disabled.
If you could assist it would be greatly appreciated.
Thank you.

The maximum level was already set to 99 for the database profile that I was using.
I have two structure reports that use the same database profile.
One expands to the 4th level, and one does not.
Is there a place in report painter or report writer to set the default hierarchy level?
Thank you.

How to create infopackages for an Hierarchy (# Levels)+ transport

Hi experts,
i have create an Hierarchy with differents levels which i will like to load from R/3 to BI using a batch job and a process chain.
I would like after that creation to transport it in the Test system.
Could you please help me on that way?
Cheers
Gilo

Hi That means,
the hierarchy should be built in Test and in productiv system?
We dont have authorization ito do any change neither in Test nor in productiv system.
How to proceed?
Thanky
Gilo

BEx Analyser: How can I define colours for different levels of a hierarchy?

Hi everyone,
I have a report in BEx Anaylser that includes a hiearchy of 9 levels.
For a better overview, I want to define different colours for the cells of each level. In this way, the user should be able to see which numbers belong to which hierarchy level. How can I do this?
Best regards
Daniel

Dear Anujit,
Thanks for your answer.
Seriously? I cannot do this with BEx Analyzer other than using Excel VBA macro?
Cheers, Daniel

Unable to create site hierarchy for any variation label

I am unable to create a site hierarchy for our source variation and any subsequent variation labels we setup. The error when trying to do so is:
“An error was encountered performing this operation.
You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator. “
We have a test farm which didn't have this problem.
Any help gratefully received.

Thanks Mark. I'll certainly give that a try. But today I started digging into the SharePoint Logs and found this entry:
10/01/2007 11:42:59.28 w3wp.exe (0x1240) 0x17FC Windows SharePoint Services Runtime 8yr8 Exception An unhandled exception has occurred. Unable to cast object of type 'My.WebParts.ContactUsWebPart' to type 'Microsoft.SharePoint.WebPartPages.WebPart'. System.InvalidCastException: Unable to cast object of type 'My.WebParts.ContactUsWebPart' to type 'Microsoft.SharePoint.WebPartPages.WebPart'. at Microsoft.SharePoint.Publishing.PublishingPage.FixWebPartUrlsForVariation() at Microsoft.SharePoint.Publishing.Internal.DeploymentWrapper.CreateVariantPage(PublishingPage sourcePage, PublishingWeb targetArea, String destPageWebRelativeUrl, String pageLayoutName, String title, String description, Boolean copyResources, Boolean enforceMajorVersion, SPWeb& webToClose) at Microsoft.SharePoint.Publishing.PublishingPage.CreateVariationInner(VariationLabel varla...
10/01/2007 11:42:59.28* w3wp.exe (0x1240) 0x17FC Windows SharePoint Services Runtime 8yr8 Exception ...bel, String pageLayoutName, String destPageName, String title, String description, Boolean copyResources, Boolean overrideStopUpdate, Boolean isCreateHierarchies, Boolean enforceMajorVersion, Boolean skipIdentityTargetConflictChecks, Boolean stopAutoSpawnAfterDelete, Boolean sendNotificationEmail, LongRunningOperationJob lroLogger) at Microsoft.SharePoint.Publishing.PublishingPage.CreateVariationAuto(VariationSettings variationSettings, VariationLabel varlabel, Boolean isCreateHierarchies, Boolean enforceMajorVersion, Boolean skipIdentityTargetConflictChecks, LongRunningOperationJob lroLogger) at Microsoft.SharePoint.Publishing.PublishingWeb.CreateVariationsDeepForChildren(VariationSettings variationSettings, PublishingWeb sourceParentPubWeb, VariationLabel varlabel, Boolean isCrea...
10/01/2007 11:42:59.28* w3wp.exe (0x1240) 0x17FC Windows SharePoint Services Runtime 8yr8 Exception ...teHierarchies, LongRunningOperationJob lroLogger, List`1 errors) at Microsoft.SharePoint.Publishing.PublishingWeb.CreateVariationsDeep(VariationSettings variationSettings, ReadOnlyCollection`1 varLabels, Boolean isCreateHierarchies, Boolean recurse, LongRunningOperationJob lroLogger, List`1 errors) at Microsoft.SharePoint.Publishing.Internal.VariationSettings.CreateHierarchies(LongRunningOperationJob lroLogger, List`1 errors) at Microsoft.SharePoint.Publishing.Internal.WebControls.CreateVariationHierarchiesLro.CreateVariationHierarchies() at Microsoft.SharePoint.Publishing.Internal.WebControls.CreateVariationHierarchiesLro.DoWork() at Microsoft.SharePoint.Publishing.Internal.LongRunningOperationJob.<ThreadEntryPoint>b__11() at Microsoft.Office.Server.Diagnostics.Fir...
10/01/2007 11:42:59.28* w3wp.exe (0x1240) 0x17FC Windows SharePoint Services Runtime 8yr8 Exception ...stChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(ULSTagID tagID, ULSCat categoryID, String output, Boolean fRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.SharePoint.Publishing.Internal.LongRunningOperationJob.<ThreadEntryPoint>b__f() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(ULSTagID tagID, ULSCat categoryID, String output, Boolean fRethrowExcep...
10/01/2007 11:42:59.28* w3wp.exe (0x1240) 0x17FC Windows SharePoint Services Runtime 8yr8 Exception ...tion, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.SharePoint.Publishing.Internal.LongRunningOperationJob.ThreadEntryPoint() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
This exception totally amazes me because I thought from WSS 3.0/MOSS 2007 onwards all Web Parts could be derived from System.Web.UI.WebControls.WebParts.WebPart. So does this mean I will have to change all of them?
Did you run into anything similar?
Thanks.

Hierarchy level for Site hierarchy idoen't load in BI

Similar Messages

Maybe you are looking for