This business process allows you to move objects in a hierarchical class type provided by SAP (class type 035, the site hierarchy, for example) or objects in a user-defined class type to new positions within the hierarchy (reclassification).

Each object in a class type is assigned to precisely one class. Classes can, in turn, be assigned to other classes. The result is a class hierarchy.

This structure makes it easier to monitor and control the activities of your company and reduces the volume of data (such as site group data) that has to be maintained. In addition, the class hierarchy structure enables descriptive characteristics (the region for a site, for example) to be inherited by subordinate levels from superior levels.

Most companies need to restructure existing hierarchies every once in a while, however; in other words, sites may have to be moved from one class to another within the class type. The reasons for this reorganization can include the following:

• Object restructuring has been prompted by efforts towards ECR (Efficient Consumer Response) or the introduction of Category Management.
• A store has grown and can no longer justify its assignment to a "Small stores" site group. It must be reclassified (moved into the "Medium-sized stores" site group).

Reclassification should, however, only be possible if certain system checks have been carried out successfully.

This business process allows you to plan your reclassification for a specific date initially without actually carrying out the restructuring. The checks run as planned on this date. You can save this simulation with a change number and then change it at any time and run new checks. Once you have decided on a definite reclassification, you can activate it.

• Class type
• Classes and objects

3. The system checks the characteristics of source and target objects: reassignment is only possible if the characteristics and characteristic values of the source also exist in the target.
4. You edit the error log and change the reclassification, if necessary.
5. You save the reclassification version. This is a simulation version, which means that it does not take effect until it is actually activated. You can change this version right up until its activation date.
6. You activate ("update") the reclassification version; the relevant objects are then moved on the date specified.
7. If necessary, you update the Information System (manual function).