In my last blog post I discussed some of the organization purposes and its use in building effective organization framework. This blog will focus on the remaining hierarchy purposes and its usage within D365 for Finance.
This purpose is used in setting up assortments for various retail channels like brick and motor stores, online stores by grouping the retail stores through organization hierarchy instead of assigning the assortment individually to each store. The assortment can be assigned to the high-level organization node. Then, whenever a new retail channel is added to the high-level organization node, that retail channel automatically inherits any assortments that were assigned to the higher-level organization node. Only the organization hierarchy assigned to this purpose can be used to setup retail channels to the assortments.
Retail > Catalog and assortments > Assortments
This purpose is used to group the stores that are replenished through retail hierarchies. The groupings can be based on the organization, size, turnover, or type of the stores and then setup the specific replenishment rules to hierarchies assigned to the retail replenishment purposes. The retail channel included in the hierarchy can be used to define replenishment rules.
Retail > Replenishment > Replenishment rules
This purpose is used in retail reporting such as channels sales by report, Top products report, Top customers report etc. based on organizational hierarchy which is configured with various retail channels and stores grouped together in an hierarchy.
Retail > Inquiries and reports > Sales reports
Retail POS posting:
This purpose is used to post inventory, calculate statement and post statements for the group of stores in a hierarchy when the batch job is defined. Only the associated organization hierarchy for this purpose can be used for retail postings.
Retail > Retail IT > POS posting
Benefit eligibility control
This purpose is used to define and exercise eligibility rules for each benefit that your organization offers to workers based on the organization hierarchy. Only the associated organization hierarchy for this purpose can be used in defining benefit policies in human resource module.
Human resource > Benefits > Eligibility
This purpose is used to define the budget planning process for the organization, a hierarchical relationship can exist between parent and associated budget plans. Different budgeting workflows can be defined by organizational unit in a budget planning process. Only the associated organization hierarchy for this purpose can be used in defining budget planning process in budgeting module.
Budgeting > Budget planning > Budget planning process
This purpose used to display projects by organization hierarchy from the All projects list page. There is a selection field ‘Legal entity’ in the All projects list page which provides the option for filtering by legal entities by default, if the organization hierarchy with this purpose is assigned, the lookup will be changed with the view by organization hierarchy
Project management and accounting > Projects > All projects
Premium earning policies:
This purpose is used to define the premium earning policies (US Payroll) to workers. The associated organization hierarchy for this purpose can be used in defining premium earning policies by organization hierarchy in Human resource module.
For this purpose, only the Legal entity organization type is allowed. However, the organization hierarchy here can be used to group legal entities and define policies.
Payroll > Setup > Earnings
You are all set to define right hierarchy purposes to the organization needs.
Please feel free to provide feedback or comments on this blog post.
This is a personal blog. Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated. All content provided on this blog is for informational purposes only. This blog makes no representations as to the accuracy or completeness of any information on this site.