“Organizational Units” scenario
To describe the organizational structure of a company, organizational units are used, which are minimal structural units. For example, Accounting, Human Resources, or Purchasing are organizational units in Microsoft Dynamics Business Central terminology.
Each structural unit corresponds to one directory line.
The General tab contains the general information about the organizational unit, its opening date and status.
| Field | Description |
|---|---|
| Code | Organizational unit’s code. |
| Name | Short name of the organizational unit. |
| Full name | Full name of the organizational unit. |
| Parent code | The code of the parent organizational unit – organizational units of a higher level of the hierarchy to which this organizational unit belongs. Used to build a hierarchical structure of a company. |
| Level | Filled in when validating the “Type” and “Parent element code” fields, according to the following logic: By default 0; if the parent code is filled: level = parent level + 1; if there is no parent: level = Type – 1. |
| Manager code | Code of the organizational unit’s manager. The organizational unit’s manager code can be changed even for an organizational unit with the “Approved” status. |
| Type | An organizational unit can be of the following types: Header and Unit. Organizational units with the "Header" type are used solely to define the visual structure of organizational units and make them more clear. Field values defined in records with the “Header” type are not inherited to subordinate levels. In records of the “Header” type, it is enough to define the “Code” and “Name” fields. These types of units cannot have employees or vacancies. Organizational units with the "Unit" type correspond to actual operating organizational units of the company. |
| Start date | Start date of the unit’s operation according to the Staffing List order. Required field. |
| End date | The end date of the organizational unit’s operation. Typically, the date is filled in for units that are already closed and units that are opening for a specific period. Leave the date blank if you want to create the unit indefinitely. The end date can be specified when closing a unit. |
| Blocked | The field is used to block organizational units for selecting a position card. |
| Status | Displays the current status of the unit card: • Open – the unit card has been created and any changes can be made to it. • Approved – the unit card has been approved and included in the organization’s staffing list. You cannot make changes to the card. • Closed – the organizational unit has been closed. |
The Administration tab displays additional information about the organizational unit. Please note that the fields in the current version of Microsoft Dynamics Business Central are informational.
| Field | Description |
|---|---|
| Address code | Organizational unit’s address code. If the organizational unit’s address code is different from the main company address, select the appropriate address code in the field. |
| AT Codifier | Codifier of administrative-territorial units. |
| Calculation group code | Used to select the payroll calculation group. |
| Salary posting group | Used to select a salary posting group. |
| Employee Posting Group | Defines the employee type to associate business transactions carried out for the employee with the corresponding account in the general ledger. |
| Global Dimension 1 | The Global Dimension 1 value that will be transferred to the positions of this organizational unit. |
| Global Dimension 2 | The Global Dimension 2 value that will be transferred to the positions of this organizational unit. |
The "History" tab displays the history of changes to the organizational unit card.
Created by user – USER ID of the user is displayed during creation. Date of creation – displays the date of creation of the unit. Approved by user – USER ID of the user is displayed during approval. Approval Date – the Approval date is displayed. Closed by user – USER ID of the user is displayed during closing. Closing date – Closing date is displayed.
In order for the new organizational unit to be used in the formation of the staffing list and to hire employees in it, the organizational unit card must have the Approved status. Depending on the current HR and Payroll Setup (the Use Staffing List Orders field), each organizational unit card can be approved for the formation of the staffing list (Actions – Functions – * Approve* if the option is not enabled) or use Staffing List Orders (Staffing List scenario) for these purposes (if the option is enabled). If no position is associated with the organizational unit and no staffing list order has been created, the “Approved” status can be removed (Actions – Functions – Open).
To liquidate a unit, it must be closed (Actions – Functions – Close). Before an organizational unit is liquidated, all its positions must be closed. The close function records the date and user who performed the procedure. Such a unit cannot be selected in the staffing list, as well as when creating new positions.
On the Related tab:
For each organizational unit, Default Contract Terms can be defined, which will be used to generate labor contracts with employees of this organizational unit by default. The Working Conditions scenario contains more detailed information about defining working conditions for various elements of the organizational structure.
Name conjugation – for use in printed forms of HR orders, it is necessary to fill in the name conjugation. Select the case: generic, accusative and dative, and conjugate the organizational unit’s name line by line.
Dimensions – label dimensions that will be transferred for all positions in this organizational unit.