|
|
|
|
|
Let’s start from the top – the user or recipient name. Only one user should be defined at the highest level of the recipient tree. This is usually an operations user who is (by default) authorized to see all reports.
In our example, the branches are organized in groups under regional management. Each branch is composed of a few functional departments (for example, foreign currency, stock exchange, loans, and so on). A functional department is usually composed of one or very few bank workers. Therefore, in many cases, a department is the final destination of the report. The division of the reports between two workers in the loans department of a bank branch is done manually by the workers themselves. However, in the main branch, each department is quite large, and there are functional differences which justify putting specific workers as the designated report recipients in the tree.
Concerning naming conventions, branches are usually assigned a number. You can decide that the name of the branch is the number itself (for example, 129). However, this can lead to ambiguity problems, for example, if there is also a section 129. Each user name must be unique; therefore, confusion can be caused by a report decollating statement such as:
DO USER 129
It is recommended that all the branches start with a fixed prefix (for example, BR129, BR130, BR135, and so on). This enables easy and unique identification of the user in all the screens and reports.
Let’s now review the use of the Recipient Tree by report decollating missions.
Parent Topic |