Vendors: Changing Validity Data in a Vendor Hierarchy
When you create or make changes to a hierarchy node, you specify a valid-from date. Your vendor advises you that the sales structure of its organization will change at some point in the future. You want to restructure the vendor hierarchy in advance.
Until that time the existing node assignments remain the same.
If you leave the valid-to date blank, the system automatically proposes 12/31/9999.
You may want to define a temporary reassignment of 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/1999. The validity periods before the temporary reassignment are as follows:
4712® 4711 (01.01.1997 - 31.12.2002)
You now create a third, temporary reassignment: 4712 -> 4000. The system automatically redetermines all three validity periods. The resulting validity data is then as follows:
4712® 4711 (01.01.1997 - 30.06.2002)