The configuration relationship diagram illustrates how different configuration elements can affect the user experience. The arrows on the diagram leading away from a configuration circle represent direct relationship. Even though you are reading the diagram in a downward fashion, this doesn’t represent the order of configuration.
The Employee (User) is the primary connection for configuration. The configuration elements in deep blue represent data that is assigned directly to the user’s profile upon account creation.
Every user must have one Locale, Group (Employee and Invoice), and Ledger assigned, and can only have one assignment at a time.
The Group is the second largest connection on the diagram and controls all items in blue. Groups are created to separate the user’s experience. For example, one set of employees could be assigned a different set of policies, adhere to different audit rules, or use a different employee form. Groups are often named after countries; however, they can be named after user categories. For instance, AP Group, Executive Users, or Services.
The items in light blue are considered group aware and may have multiple assigned to one group. For example, groups may have multiple policies assigned to one team of users. It would be the user’s responsibility to select the appropriate policy when creating a purchase request, purchase order, or invoice.
The last major connection is Policy configuration, and the policy controls the configuration items in teal. Policies represent the purchase request, purchase order, or invoice experience. There are three main drivers of policies Forms and Fields, Expense Types, and Workflows. If a user needs a different form, expense type or workflow you will need a separate policy, because only one of these items can be assigned to a single policy at a time. The expense type selects the appropriate Account Code based on the Ledger assigned to the employee’s profile. Also, that PO Matching and Bill to Addresses are assigned to the Purchase Request Policy.
At the bottom of the diagram, you will notice the custom fields and lists. Note that Fields are assigned to all forms for data entry. Also, lists are configured in the List Management area, but they must be assigned to a form to function. List Management is also used in other areas like Group Configuration and Feature Hierarchies.