ProjectWith this function, you put on a project and you are able to define the allocations, which can be made in this project, in a second step,.for example which application or cost center has to be assigned. Which is defined as project in the enterprise, depends on the account data and the necessary allocations. Each allocation to a project has either the status 'valid' or 'invalid' (entry J/N in the field ' valid '). If you put on an allocation, this field with ' J ' is reserved. When implementing, the allocation procedures consider only the valid sentences. Thereby, it is possible to exclude an invalid project (for example an account number) which starts from a certain time from the accounting. Projects can be developed hierarchically. This can be helpful with large-scale projects. Subordinate projects can be separately charged, but it's possible to get in an analysis an overview of the whole project. If you work with a project hierarchy, proceed top-down during the collection, the superior project has to be admitted to the system as project. In the highest hierarchic level or if no hierarchy is to be illustrated, the superior project is equal to the project. The superior project does not have influence on the account, it serves only purposes of analysis. An application and/or a cost center can be assigned to a project. At least, one of these values must be indicated. Application and/or the cost center must be defined before, because it will be proofed. For assistance, it is possible to copy allocations on another project and/or another period. The copied allocations are indicated in the dialogue- ' allocation to put on ' . Are some allocations not possible in another period, f.e. because the cost center is not valid, the sentences will be marked with a ' D '. These sentences can be corrected now before storing. Actions (procedures) in the flow control:
Dialog fields:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||