Changing Validity Data in a Customer Hierarchy in SAP SD

Use

When you create or make changes to a hierarchy node, you specify a valid-from date. For example, a customer advises you that the buying structure of his organization will change, effective the beginning of next year. You want to restructure the customer hierarchy in advance.

You maintain the hierarchy, changing the assignment of nodes as necessary and entering the valid-from date that corresponds to the change at the customer. Until that time the existing node assignments continue to function as before. In addition, you can also specify a valid-to date for a node. If you leave the valid-to date blank, the system automatically proposes 12/31/9999.

You may want to define a temporary reassignment for a node for which you have already defined a future change. The following example shows how the system automatically redetermines the validity period in such a situation. Two assignments exist for node 4712: a current assignment and an assignment that comes into effect 01/01/1995. The validity periods before the temporary reassignment look like this:

4712 ® 4711 (01.01.1993 - 31.12.1994)
4712 ® 5000 (01.01.1995 - 31.12.9999)

You now create a third, temporary reassignment: 4712 ® 4000. The system automatically redetermines all three validity periods. The resulting validity data looks like this:

4712 ® 4711 (01.01.1993 - 30.06.1994)
4712 ® 4000 (01.07.1994 - 31.12.1994)
4712 ® 5000 (01.01.1995 - 31.12.9999)