![]() | ![]() | ![]() | ![]() | ![]() |
The realignment process is loosely defined as re-using old SKUs for new products (instead of adding a new SKU). In the event that the SKU has no siblings in the hierarchy (the SKU is only child of the higher level), the entire hierarchy is removed. This is due to the rule that states there must not be any partial hierarchy. No "dangling nodes" are allowed.
While the relationship chain is removed from PRODUCT_HEIR_ASSOC_DM, the PRODUCT_DM still contains all of the product information.
The unexpected results would be errors which look similar to:
While the use of realignment is not a common process, there are a couple of workarounds that will prevent the aforementioned error:1|3022XX-0099|11|70022-LVL42|;Parent ID is not Immediate Parent or not found in stage hierarchy|22JUL11:20:22:39
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Size Profiling | 64-bit Enabled AIX | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||
Microsoft Windows Server 2008 | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||
Microsoft Windows Server 2003 for x64 | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||
Microsoft Windows Server 2003 Standard Edition | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||
Microsoft Windows Server 2003 Enterprise Edition | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||
Microsoft Windows Server 2003 Datacenter Edition | 2.2_M1 | 3.2 | 9.2 TS2M3 | 9.3 TS1M1 |