Team Creation and Management

Teams are always used by the application when working with locations. All locations require a team because teams control the security for a location. We recommend that you follow the best practice where the location hierarchy (tree) and the team hierarchy (tree) are identical.

This requirement is not strictly necessary because it is possible to have team structures that are bigger and more complex than their location counterpart’s structure. However, you must always ensure that parent and child relationships are consistent between the location and team trees, and that their ancestry is structured to be consistent. Consistent ancestry means that, for every ancestor location in the location tree, there must also be an ancestor team (for the location’s team) in the team tree.

If the team tree is not identical to the location tree, the structure must remain the same and only vary by having additional nodes. You could transform the location tree into the team tree by simply inserting additional nodes.

The Configuration Editor’s default behavior attempts to ensure that the structure of the team hierarchy mirrors the structure of the location hierarchy. When you create a location, the application checks for an existing team with the same name within the hierarchy. If it exists, that team is used for the new location. If it does not exist, the application creates a corresponding team (with that name) in the hierarchy.

When adjusting location hierarchy (for example, by moving a parent location), the application tries to keep team management in synchronization with the hierarchy. If the hierarchies get out of synchronization because of your action, Infor assumes that your choice should take precedence.

Since the application cannot determine what you did to cause the hierarchy to become out of sync, you are responsible for team configuration being correct for your organization. Therefore, if you make changes to your location structure, you may need to make corresponding changes to the team.