If you generate the report in 1C:Enterprise mode, you will see that no recalculations have been performed yet. You need another Employee accrual document to test recalculations.
- Start 1C:Enterprise in the debug mode.
- Create the Employee accrual #2 document with September bonuses for Jonnson and Walkman (fig. 18.10).
Fig. 18.10. Employee accrual #2 document
This document records the fact that bonuses are due to employees named Johnson and Walkman based on their work in September. Since you do not know the bonus amount (it will be calculated based on a certain algorithm), leave the Accrual field empty. - Click Post and close.
- Open the Employee accrual # 1 document and change Johnson’s salary from 10 000 to 7 000.
- Click Post and close.
- Generate the Recalculation report (fig. 18.11).
Fig. 18.11. Recalculation report
As you see, it now has some data.
This is because the Bonus calculation type depends on the Salary calculation type by base period. Once you modify the existing records of Salary type, the platform generates a set of recalculation records (because their base is changed).
You may be wondering why the Walkman's record is present in the report, since you only changed Johnson’s salary. The reason is that the platform does not track the specific changes to document records. The only thing it tracks is the fact that posting (reposting) a document changes a calculation register record set.
Therefore the recalculation record set includes ALL register records whose values MIGHT change after reposting a document that creates base records in the register. - Repost the Employee accrual # 2 document (the one that accrues bonuses), and generate the Recalculation report.
The report is empty again, as the platform has noted the fact that you recalculated the dependent records and therefore cleared the recalculation table.
In this example you have studied calculation register dependency by base period.
