Language: Deutsch · English

4.9 DATEV: Specific extensions

4.9.1 Adjusting and extending the existing export formats

Adding and removing attributes to be considered in the export is done simply by adjusting the included table columns in the corresponding data source ("DATEV Client Export", "DATEV Client Billing Export" or "DATEV Turnover Export") under "Configuration > Data sources > Report & form".

4.9.2 Changing the export parameters

As a parameter list, the DATEV Nuclet normally only provides the pair "date from"/"date until" to select the period to be considered. If a different parameterisation is desired, the following steps must be carried out:

1. Adding/removing the parameters from the business object "DATEV Export" ("Configuration > Business object").
2. Adjusting the affected layout ("DATEV Client Export", "DATEV Client Billing Export" or "DATEV Turnover Export") under "Configuration > Layout".
3. Adjusting the parameterisation in the affected data sources ("DATEV Client Export", "DATEV Client Billing Export" or "DATEV Turnover Export") under "Configuration > Data sources > Report & form".
4. Overriding the method fetchResultList(DATEVExport) from the AbstractDATEVLogic class in the DATEVLogic class. Here the parameter values are accessed and passed on to the data source ("Configuration > Server rules").
   
   

4.9.3 Adding further export formats or export types

If further export formats (in addition to turnover, invoices and customers) are to be created, the following procedure is recommended:

1. Creating a new Nuclos action for the business object DATEV Export ("Configuration > Miscellaneous > Action").
2. Creating a master data record for the new export type ("DATEV > Master data > DATEV export type") with a reference to the action created in step 1.
3. Cloning the report data source "DATEV Client Billing", carrying out the desired adjustments in the cloned SQL.
4. Cloning the dynamic business object "DATEV Client Billing References", carrying out the desired adjustments in the cloned SQL.
5. Cloning a layout for a specific DATEV export (e.g. "DATEV Client Billing"), entering the dynamic business object from step 4 in the subform "References".
6. Extending the enumeration class ExportType (Java package "org.nuclet.datev.logic") with a further constant that represents the new export type.
7. Transferring the method fetchResultList(DATEVExport) from the abstract base class AbstractDATEVLogic into the specific DATEVLogic class.
8. Extending the switch statement in fetchResultList(DATEVExport) in the specific DATEVLogic class so that the new enum constant from step 5 is taken into account.
9. Extending the switch statement in getWrappedClass(ExportType) in the specific DATEVLogic class so that the new enum constant from step 5 is taken into account.
10. If applicable, adjusting the constructor of the ReferenceWrapper class if a further business object is to be used as a reference object for the new export type.

If the exports for the new export type are to be run automatically via the job control, the following is also recommended:

1. Creating a new Nuclet parameter for the prefix of the new export type (e.g. by cloning and adjusting the parameter "DATEV Client Billing Prefix").
2. Cloning the job rule CreateDATEVClientBillingExport and adjusting the two methods.
3. Cloning and adjusting the job "DATEV Client Billing" for the new export type.
4. Attaching the job rule from step 2 to the previously created job (via "Configuration > Rule management").

Related pages