Following reclassification in SAS^® Markdown Optimization, SAS^® High-Performance Markdown Optimization, SAS^® Regular Price Optimization, or SAS^® Promotion Optimization, the database table that controls user application component access is not correctly updated. If reclassification affects the ancestry of a user's root product or geography hierarchy access node, the access permission issues might result.

There are no error, warning, or note messages to indicate that a problem has occurred, but incorrect markdown calculations or fields might be displayed in the UI.

To circumvent this issue, you must manually remove authorizations (via the SAS^® Merchandise Intelligence Plug-ins for SAS Management Console) at all lower hierarchy levels (i.e. authorize only at the highest hierarchy level) when read authorization occurs at multiple levels within a hierarchy after reclassification.

For example, if you had read authorization for a specific child at hierarchy level 7 and it is moved during reclass to a different level 6 parent for which you also have read authorization, then the application component access tables become incorrect. You cannot be given access at level 7, if you also have access at level 6.

NOTE: In SAS^® High-Performance Markdown Optimization 4.3, this issue might manifest itself during optimization. Plans might fail to optimize and an error similar to the following is generated in your TKMI grid server log:

NOTE: The Hot Fix associated with this SAS Note ONLY fixes the issue that causes optimization to fail in SAS^® High Performance Markdown Optimization 4.3.

Operating System and Release Information

A fix for this issue for SAS High-Performance Markdown Optimization 4.3 is available at: