Diagnosis
Deactivating an active article hierarchy can impair operational andplanning processes that directly access an active article hierarchy.
Examples:

• There are applications, such as the Price Planning Workbench, which
depending on the Customizing settings, require an active articlehierarchy in the system for the determination of articles. If thearticle hierarchy is deactivated, existing price plans in the system canno longer be processed.

• An active article hierarchy is required for processing purchasing lists.
If the article hierarchy has been deactivated, existing purchasing listscannot be processed and no new lists can be created.
If you intend to activate a new article hierarchy after deactivating anactive one, it may be the case that the previous operational processesare impaired and that certain manual activities are necessary.
Examples:

• If the categories are not numbered identically in the old and new
article hierarchies, all existing shops have to be closed and new shopshave to be created for the new categories. Accordingly, when using thearticle hierarchy in other subsystems, for example, POS, the new dataneeds to be loaded. For performance reasons, an initialization or a fullversion should be used rather than change messages.

• If you use markdown budgets at article hierarchy level in the Price
Planning Workbench and have planned the budgets using the old articlehierarchy ID, you have to create a new budget type in SAP BI andtransfer it to the ERP system.

• If you perform planning in SAP BI at article hierarchy level, you have
to extract the new active hierarchy to SAP BI and create the plans (forexample, markdown plans, OTB plans) accordingly.