Problem Note 44332: Using realignment process can show unexpected results in the form of "Parent ID is not Immediate Parent or not found in stage hierarchy"
 |  |  |  |  |
When using SAS® Size Profiling, performing a "realignment" might cause unexpected results.
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
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
- Before you run the purge job, you could pull the complete hierarchy for all products to be purged. This information would be appended to the STG_PRODUCT and STG_PRODUCT_HIERARCHY tables using the Load_STG_product_parent job ensuring that there are no duplicates. From a code standpoint, this is very involved.
- The easiest way from a coding perspective would be for each product you are purging/replacing, add a dummy sibling to all of the products being purged. Go through your defined process of realignment, and then delete all of those dummy products. Using this method means that you do not have to worry about removal of the dangling nodes. The processing overhead for adding/removing the dummy products will also be very low.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| 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 | ||
A fix for this issue for SAS Merchandise Intelligence 4.2_M2 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/D81.html#44332| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2012-11-14 11:20:52 |
| Date Created: | 2011-09-19 10:50:59 |