| Name | | Clients |
| Description | A user may wish to be a member of a client that has more than one Company (or Ministry). |
| | The Ministry Years Table contains Client ID for company links. |
| Name | | Correspondance Type Codes |
| Description | Correnpondance tracking classification of correspondance. |
| | Only Budget Office/Officers should have write access to these tables. Most will not change from year to |
| Name | | Correspondances |
| Description | User assigned and generated correspondances/letters. |
| | They contain comments and can point to records and images/documents. |
| | Pointers to cost centres, and optional modificaiton item, and sub-standard codes. |
| Name | | Cost Centres |
| Description | Organizational Node if children exist for it, else the old equivalanet of Cost Centre. This table also stores the |
| | budget and expenditure roll-ups/summaries for production, |
| | - NOT for scenarios/playgrounds. |
| | |
| | User Adding Cost Centres: |
| | |
| | A user can add a cost centre only as non-production. The user must indicate the parent cost centre. |
| | Budget Office/Officers must make it production for the process of integrating into the system, since |
| | the system must then examine the organizational tree, to make adjustments to the roll-up sums. |
| | There are activity and project selection for every cost centre added, unless the cost centre is not an |
| | end-of-tree node. Only Bottom levels of cost centres are allowed to have budget modifications (accounting |
| | of budget and expenditure details). All others are defined to be divisions, branches, responsibility, etc. nodes |
| | within the organization. |
| | |
| | The Level-nos and breakdown of budget control is done by the system utilities, activated by parent change |
| | event. |
| Name | | Cost Centres NON-Production |
| Description | Organizational Node if children exist for it, else the old equivalanet of Cost Centre. This table also stores the |
| | budget and expenditure roll-ups/summaries for production, |
| | - NOT for scenarios/playgrounds. |
| | |
| | User Adding Cost Centres: |
| | |
| | A user can add a cost centre only as non-production. The user must indicate the parent cost centre. |
| | Budget Office/Officers must make it production for the process of integrating into the system, since |
| | the system must then examine the organizational tree, to make adjustments to the roll-up sums. |
| | There are activity and project selection for every cost centre added, unless the cost centre is not an |
| | end-of-tree node. Only Bottom levels of cost centres are allowed to have budget modifications (accounting |
| | of budget and expenditure details). All others are defined to be divisions, branches, responsibility, etc. nodes |
| | within the organization. |
| | |
| | The Level-nos and breakdown of budget control is done by the system utilities, activated by parent change |
| | event. |
| Name | | Directives |
| Description | Upper level Directive for multi-user tasks. |
| | Ex: 10% reduction |
| Name | | Documents |
| Description | For Document handling, this table contains the actual file name. |
| | The file may be a TIF image or a WP document as indicated by filename suffix. |
| Name | | Folders |
| Description | Server Volume Sub-directories for finding Documents. |
| | It can refer to a real folder whose contents have been scanned into. |
| | Thus physical folder location is documented for the originals. |
| Name | | Function Codes |
| Description | Function Codes attribute of Cost Centres. |