A CALDEP mask is opened for each depreciation plan to be calculated. A line of this mask corresponds to a record of the DEPREC table. Each plan has a specific abbreviation and the corresponding mask contains the data as they exist in the DEPREC table.
The period charge for a fiscal year is stored in the [F:DEPC]PERENDDPE, [F:DEPC]DPET, [F:DEPC]DPEI field if it is the period charge calculation for the "Actual", "Theoretical", "Initial" tracking. The exceptional depreciation of the period is stored in the [F:DEPC]PEREXCDPR, [F:DEPC]PEREXCDPRT, [F:DEPC]PEREXCDPRI depending on the tracking.
The fields of the [F:DEPC] class other than those mentioned above can be modified in the case of a "specific" mode. However, people who are not sufficiently familiar with how calculation processing works and with the consequences and impacts of such modifications are strongly advised not to make any modifications. In addition, it is imperative to control the validity of the results obtained through the different cases of management covered by the calculation: Total re-generation, method changed based on the different effective dates, reevaluation, depreciation, issue, retroactive issue, .... results that may be inadequate.
[M:DIV]: CALDIV screen containing different data used for the calculation
[M:DIV2]: CALDIV2 screen containing different data used for the calculation
[M:FIY]: CALFIY screen containing the fiscal years/periods of the context to which the plan to be calculated belongs
[M:DEP]: CALDEP screen containing the data of the depreciation plan to be calculated
[M:PPL]: CALPPL screen containing the data of the production plan
[M:TAB]: CALTAB screen containing the data concerning the vehicle reintegration cap.
[F:DEPC] : File class of the fiscal year to be calculated
The G_SKPSTD global variable must be initialized to 1. This makes it possible to skip the processing for "standard" depreciation modes.
The GOK variable can take the value 1 or 0 (1 by default). The GOK variable must be set to 0 if an error is detected and the calculation processing must be stopped. In this case, the 9100 error appears in the log file.