Impact

Proper typing of location entities represent a standard configuration and the impact to existing implementations should be minimal. Furthermore, you can only generate schedules and forecasts within LFSO that adhere to this strict hierarchical standard (corporate entity -> store -> department). Attempting to generate a forecast or schedule for a store that has child stores will produce unexpected results.

After the upgrade script has run, if a situation is encountered where a store entity is created that is a parent to another stores, users will not be able to edit the child store within the Configuration Editor. (This strict validation is not enforced within the schema or the existing location configuration screens.) When attempting to edit a store with a parent store entity, an error message is displayed. The message states that the wrong parent type error has occurred when trying to edit the second store.

The LFSO Configuration Editor treats the internal type as read-only after the entity has been created. If this error is encountered during usage of the Configuration Editor, a correction should be made in the existing maintenance forms.