Introduction

The following documentation specifies new features and improvements for the release 45.3:6.4.0 in procedures, functions and programs that have been added to the Comarch Financials Enterprise (CFE) compared to previous versions. Some texts contain a number of technical information that may seem too specific to the “normal user”. Nevertheless, they are listed in order to give the interested party as much information as possible about the innovations.

Please observe the references in APP-003545.

Many new features, fixes and adjustments are from Financial accounting. But also from asset accounting and controlling processes were optimized and added. With these program supplements the Comarch Financials Enterprise is completed with additional demands in the programs of Financial accounting, Asset accounting, Controlling and Reporting as the result from daily use of the software. Thus, the Comarch Financials Enterprise is more perfect and leaves open only a few wishes.

Contents of the support delivery

With the download, you also get support deliveries to install Comarch Financials Enterprise version 45.3:6.4.0.
For running Financial accounting the following APPs are delivered:

• Comarch Financials Enterprise
  • com.sem.ext.app.fin (APP-003545)
  • Import files (APP-003555)
• Comarch Financials Enterprise Adapter
  • com.sem.ext.app.finadapt (APP-003545)
• Data processing
  • com.sem.ext.app.prepctrl (APP-003545)

The following chapters describe the system requirements.
At this point, once again it should be mentioned that with the release of Comarch Financials Enterprise version 45.3:6.4.0 the Comarch Financials Enterprise version 45.2:6.4.0 is no longer maintained.
The installation instruction is part of the support delivery INF-001955.
If we provide a new patchset you will be informed by the same way you got the information of this version.

Required code status of country versions

If there are country versions in use on the target system, the following versions are required:

• Comarch Financials Enterprise
  Country version Swiss 3:6.4.0
  • com.sem.ext.app.fin4ch (APP-003547)
  • Import data (APP-002102)
• Comarch Financials Enterprise
  Country version Italy 3:6.4.0
  • com.sem.ext.app.fin4it (APP-003546)
• Comarch Financials Enterprise
  Country version France 3:6.4.0
  • com.sem.ext.app.fin4fr (APP-003548)

If we provide a new patchset you will be informed by the usual way you got the information of this version.

Required code status of Comarch ERP Enterprise

This version of Comarch Enterprise Financials assumes that the code-level CEE640PB-Fix04 or newer is available in the Comarch ERP Enterprise.

Required version of ERP-System output manager 2.0

This version of Comarch Financials Enterprise requires at least Version 2.0 of the ERP-System output manager.
The JAVA-SOM requires a patch for CEE640PB-Fix04.
If you are using the JAVA-SOM please observe APP-001566.

Target groups

• System administrators
• Technical advisors
• Consultants

Dependencies

Using customer-adapting system

The software system in which you want to import the APP, must be a customer-adapting system (versioning level 6).
After an APP has been implemented in a customer-adapting system and the conflict job was released, the APP is then adapted by the known methods of logistics software via software updates into the follow-up systems such as test, demo and active system.
A direct installation in branch -/ partner-development systems (versioning level 3), or a demo system and / or an active system (versioning level 7) is not possible.

License key

For the operation of Comarch Financials Enterprise, you need the following fee-based license keys:

• sem.ext.app.fin.Finance
• cisag.app.FinancialsInterface
• cisag.app.Costing
• sem.ext.app.fin.AssetAccounting
• sem.ext.app.fin.Controlling
• sem.ext.app.fin.FinancialAccounting
• sem.ext.app.fin.BI

When you use a country version, you also need:

• sem.ext.app.fin4ch.Finance
  and / or
• sem.ext.app.fin4it.Finance
  and / or
• sem.ext.app.fin4fr.Finance

General and performance improvements

A special focus of the new CFE developments was placed on performance improvements, so that even extensive data quantities can be processed quickly and efficiently. For this purpose, technical adjustments were made in financial accounting, asset accounting and controlling, for example the storage of master data, the opening of the periods, etc. Such optimizations were also implemented in other applications, displays and processing steps (not mentioned below) in order to ensure quick handling and functionality of the applications.

In addition, new batch applications for data reorganization are available in financial accounting, asset accounting and controlling.

New features and improvements in Financial accounting

Optimizations and additions

Posting financial accounting

Posting is the central function within Financial accounting and therefore contains a variety of automatic functions, checks, dependencies, and settings to make the posting process simple and clear. Therefore, many new features, add-ons, and complex optimizations have been implemented to perfect the posting process.

• Invalid currency error
  If an invalid currency was entered in the Currency of currency difference field during a currency revaluation posting, an exception would occur. This has now been resolved.
• Correction for incorrectly replicated tax account in tax code
  It was possible to post with a tax code that contained an incorrectly replicated tax account from another organization. This has been corrected.
• Payment status of customer and supplier invoices
  The status of an invoice as paid or partially paid was no longer correctly transferred to CEE. This is now done correctly.

The correction application Update payment status in CEE was created to correct existing invoices. This is a batch application in the Financial accounting framework.

The application is called up separately for supplier and customer invoices and an invoice date (from/to).

• Correction for payments with freelancer deduction
  When paying an OI with a freelancer deduction in Italy, a crash could occur. This has been fixed.
• Extension for Poland for exchange rates in sales and purchasing vouchers

If a Polish organization is managed, the field Use CEE invoice amounts is activated in Customizing and the postings are made via the interface (SUPPLIER_INVOICE or CUSTOMER_INVOICE). Also, the following now applies:

• The local currency target amount in the line items and the local currency target tax amount can now be entered in the posting dialog.
• Furthermore, there is no amount smoothing in the above constellation, so a manual correction of the amounts in the posting dialog may be necessary.

Bank statement postings

If you canceled the deletion of a statement in ABB, the recorded postings would still be deleted in the background. This has been corrected.

In addition, the import of CAMT files via ABB tended to crash if the statement number was longer than five characters. This has also been corrected.

Edit payment proposal

An empty payment proposal caused a crash when the [Edit line item] button was pressed. This has been fixed.

If a new open item is to be added when processing a payment proposal, the new customizable assignment dialog from the posting dialog is now used for the [Add OI manually…] action.

Cockpit: Payments

The creation of a data medium for SEPA payments has been corrected. The <Document> tag is now output as required.

Partners/Bank details

Detailed errors are displayed in the bank details if there is only one bank and one payment method in the payment profile and this bank does not match the payment method. This allows you to check whether a BIC is required to create bank details. Otherwise, a general error message is displayed.

Edit dunning proposal

The following processing errors have been fixed for dunning proposals:

• If an open item was added to a dunning and then the dunning line items were expanded, only the added line item was displayed. As a result, the dunning level of the dunning from this OI was used when saving.
• If a dunning was loaded in the editor and then marked for deletion, the editor was not cleared when saving. The [Add OI] action could then be called up for the dunning still in the editor, which led to a crash.
• If a dunning proposal was being created, it could be loaded for processing. This then caused the application and the creation process to crash.

Generate dunning proposal

If an OI reached the highest dunning level and, according to the dunning profile, should only be dunned if another OI existed prior to the dunning end, the setting was not observed correctly and the OI was dunned. This has been corrected.

Reorganize dunning proposals

This application can be used to reorganize dunning proposals for fiscal years. The prerequisite is that the retention period for dunning proposals in years from Customizing has been reached and the reorganization status for dunning proposals has been set to Reorganizable in the fiscal year.

GDPdU Financial accounting

When outputting data in accordance with GDPdU, superfluous characters (&#xd;) were output in the Index.xml file, which could lead to problems during further processing. This has been corrected.

Output balance confirmation

In balance confirmations, all column headings are now formatted in multiple lines so that longer translations in correspondence language are output correctly.

Reorganize Z4-reports

The application can be used to reorganize Z4 reports for fiscal years. The prerequisite is that the retention period for Z4 reports in years from Customizing has been reached and the reorganization status for Z4 reports has been set to Reorganizable in the fiscal year.

Reorganize external CCI reportings

The application can be used to reorganize external CCI reports. The prerequisite is that the retention period for external CCI reports in years from Customizing has been reached.

Opening balance postings rebuild

The background application Opening balance postings rebuild led to program termination if the balances had not yet been transferred in the fiscal year. A corresponding error message now appears.

Fiscal years for financial accounting

The Financials tab shows whether or which financial accounting data can be reorganized or has already been reorganized for the fiscal year. The status information for the respective reorganization can now be displayed under the heading Reorganizations. The entries under this heading have been rearranged and supplemented with additional entries.

When changing the status of fiscal years, not only can the status of posting periods be changed, but the status of any existing closing periods is also taken into account.

Invoice receipt book

If the ISR/QR dialog was closed with the [Cancel] button, an exception occurred. This also happened with the [OK] button. This has been fixed.

If the person account was missing when saving an invoice receipt, this led to a program crash. This has also been fixed.

In addition, the fields OI text and VAT identification are now available in the invoice receipt book. In the posting dialog, these fields are transferred from the invoice receipt book to the fields provided for this purpose in the posting dialog when posting a supplier invoice.

Transaction codes invoice receipt book

The Transaction codes invoice receipt book application has been expanded to include fields for pre-assignment in the Invoice receipt book application.

Cockpit: Invoice receipt book

The new fields OI text and VAT identification from the invoice receipt book can be used in the Cockpit: Invoice receipt book application as search fields for the selection of data and as columns for the display.

Sending e-mail forms

When sending the following forms by e-mail, some selected placeholders from the forms can be used in the e-mail templates in the Text only format:

• Dunning
• Payment letter
• Return debit note
• Interest invoice
• Balance confirmation
• Payment difference note
• External CCI report

Customizing for financial accounting

Under the Retention periods function, you can now also specify the number of years that dunning proposals, Z4 reports, and external CCI reports should remain in the system after they have been completed before they can be reorganized.

Development object PreEntryItem

For the development object com.sem.ext.app.fin.financialaccounting.obj.PreEntryItem, the expected data volume has been changed from Large to Extra Large for performance reasons.

APP: Online check partner VAT ID numbers / Sales order

In the Online check partner VAT ID numbers app, the VAT ID number check in a sales order could crash if the address data of the delivery partner, invoice recipient, or customer could not be read correctly. This has been fixed.

External interface financial accounting

If a non-existent asset number and asset sub-number is transferred when importing the ExternalInterface, a corresponding error message is now displayed. The same applies to asset groups.

Transfer of customer invoices from CEE

It is possible that the transfer of CEE customer invoices to CFE may throw an exception. This has been fixed.

Invoice data assignment

The new object view Prepayment request has been added to the Invoice data assignment application. The attributes stored there are transferred to financial accounting.

Reports for financial accounting

Various reports

The reports Output open items, Output currency values of open items, Output open due dates and Output revaluation of open items contained two invalid instance variables. This has been corrected.

Country version for Switzerland

Transaction codes Invoice receipt book

The Transaction codes invoice receipt book application has been expanded to include fields for pre-assigning an OI text and a VAT identification for the Invoice receipt book application.

Country version for Italy

Invoice sums details

In the Invoice sums details application, a crash occurred when trying to select the document type in an empty record. This has been fixed.

Financials

Definition of rows

In a row schema type Debtor or Creditor, partners can also be assigned via a classification.

Master data replication

When saving a row schema, the system could come to a standstill if a delayed replication was set up. This has been fixed.

In addition, an individual index must be created on the attributes dataKey, dataObject, instance, and orgnaizationalUnit for the BO com.sem.ext.app.fin.general.obj.ReplicationDelayed so that the problem does not occur.

New features and improvements in Controlling

Optimizations and additions

Voucher references chain

The voucher references chain for a process split from a production order to the controlling posting voucher did not work in some cases. This has been corrected.

Fiscal years for controlling

The Controlling tab shows whether and which controlling data can be reorganized for the fiscal year or has already been reorganized. The status information for the respective reorganization can now be displayed under the Reorganizations tab.

When changing the status of the fiscal years, not only can the status of posting periods be changed, but the status of any existing closing periods is also taken into account.

Reorganization in Controlling

The following new batch applications are available in the Controlling framework to reorganize postings, balances, and reports in Controlling.

Reorganize entered controlling postings

This application can be used to reorganize controlling postings entered. The prerequisite is that the retention period for controlling postings in years from Customizing has been reached and the reorganization status for recorded controlling postings has been set to Reorganizable in the fiscal year.

Reorganize controlling postings

This application can be used to reorganize controlling postings. The prerequisite is that the retention period for controlling postings in years from Customizing has been reached and the reorganization status for controlling postings has been set to Reorganizable in the fiscal year.

Reorganize controlling balances

This application can be used to reorganize controlling balances. The prerequisite is that the retention period for controlling balances in years from Customizing has been reached and the reorganization status for controlling balances has been set to Reorganizable in the fiscal year.

Reorganize controlling daily balances

This application can be used to reorganize controlling daily balances. The prerequisite is that the retention period for controlling balances in years from Customizing has been reached and the reorganization status for controlling daily balances has been set to Reorganizable in the fiscal year.

Reorganize controlling reports

This application can be used to reorganize the data records of controlling reports. The prerequisite is that the retention period for controlling reports in years from Customizing has been reached and the reorganization status for controlling reports has been set to Reorganizable in the fiscal year.

New features and improvements in Asset accounting

Optimizations and additions

Posting asset accounting

• Incorrect values after simultaneous transfer postings
  If a cost type transfer posting was carried out on an asset and then a transfer posting of optional dimensions was carried out at the same time, the transfer posting values in the assets analysis could be doubled. This has been fixed.
• LVA with negative acquisition
  A negative acquisition in the amount of the original APC could not be posted for a normal LVA. This has been corrected.
• Warning on cancellation
  When canceling an asset receipt, a warning may have been issued that the new book value was below the target value. This warning has now been removed.
• Transfer posting of an asset cost type not possible
  If indirect depreciation was active (via a setting in Customizing), it was not possible to transfer an asset cost type. This is now possible.

• Error in inventory split posting in the first fiscal year
  An exception occurred during an inventory split posting in the first existing fiscal year. This has been corrected.

Transaction codes asset accounting

For transaction codes with the transaction types Change asset master or Change depreciation area, no transfer to Controlling should take place. Therefore, the Posting controlling field must not be activated for transaction codes of these transaction types.

Asset groups

Previously, an incorrectly replicated depreciation area from an asset group could be used in an asset. This is now prevented by a corresponding error message.

Periodic settlements

The depreciation was calculated with six decimal places in the case of an asset with a negative APC. This has been corrected.

In the case of a normal LVA asset with immediate depreciation, the full depreciation is calculated in the month of acquisition, even in the case of a subsequent depreciation in later months.

In addition, performance improvements have been implemented for periodic settlements.

Balance rebuilding for asset accounting

When balances are being rebuilt, the zero values are now also created again.

Asset mass date changes

When calling up a mass data change of the category Change of asset master without posting, a NullPointerException could occur. This has been fixed.

In addition, when creating a new mass data change with the category Change of asset master without posting via the [New mass data change] action from the Cockpit: Asset mass data change application, the changes were sometimes preset with the Remove value setting instead of No change. This has also been corrected.

Reorganization for asset accounting

New batch applications are available in the Asset accounting framework to reorganize postings, transactions, and various process data in asset accounting.

Reorganize asset voucher

This application can be used to reorganize asset accounting postings. The prerequisite is that the retention period for asset vouchers in years from Customizing has been reached and the reorganization status for asset vouchers has been set to Reorganizable in the fiscal year.

Reorganize asset transactions

This application can be used to reorganize asset accounting transactions. The prerequisite is that the retention period for transaction data in years from Customizing has been reached and the reorganization status for asset transactions has been set to Reorganizable in the fiscal year.

Reorganize process data

In order to be able to reorganize further asset accounting data, the following additional batch applications have been created to replace the previous Reorganize process data application:

• Reorganize periodic settlement
• Reorganize mass data change
• Reorganize allocation acquisition
• Reorganize valuation run
• Reorganize replacement cost
• Reorganize insurance values

The prerequisite for the reorganization of this data is also that the retention period for process data in years from Customizing has been reached and the respective reorganization status in the fiscal year has the setting Reorganizable.

Data update

The data update UPDFDV022505 is available for existing mass data changes of the category Change of asset master without posting.

Reorganize incomming voucher

The reorganization of incoming vouchers has been adapted to the standard and now offers the option to export data.

Reorganize issuance postings

The reorganization of issuance postings has been adapted to the standard and now offers the option to export data.

Customizing for asset accounting

A new entry for the retention period for process data has been added to the Retention periods section under the Asset accounting function. Here, you can specify the years that process data (e.g. periodic settlements) should remain in the system after completion before they can be reorganized.

Fiscal years for asset accounting

The Asset accounting tab shows whether or which asset accounting data can be reorganized or has already been reorganized for the fiscal year. The status information for the respective reorganization can now be displayed under the heading Reorganizations. The entries under this heading have been rearranged and supplemented with additional entries.

The status of the period may no longer be changed as long as the previous period does not yet have the appropriate status. It is now also checked across fiscal years.

When changing the status of fiscal years, not only can the status of posting periods be changed, but the status of any existing closing periods is also taken into account.

Reports for asset accounting

Output periodical values

With the new report Output periodical values, the periodic values of a year can be evaluated in the same way as the display of periodical values in the Asset accounting cockpit, e.g. for a cost center, inventory account, etc. Grouping is not possible in this report.

General

German and English documentation

Documentation adjustments due to changes, additions, and corrections have been integrated into the new Comarch Financials Enterprise release in both the German and English online documentation.

Numerous English documents – not yet translated and therefore missing – have been integrated into the online help.

Missing translations into English – especially those of the recent applications – are in progress and will be integrated as soon as possible.

Only the newly added or changed applications are currently not completely documented/translated. These missing documents are currently being created, revised, or updated to reflect the new features and corrections. They will soon be integrated into the system. Unfortunately, the online documentation of application developments, corrections, and improvements is always delayed, because many changes are completed shortly before the release. We try to keep this time as short as possible.

Data updates for Comarch Financials Enterprise

Generally, all data updates should be executed, which have not been processed before.
Please note that the data updates of all skipped versions must be made in case of skipped versions. Please also read chapter 5.3 and 5.3.1 in the INF-001955.

You can find a list of relevant data updates in chapter 5.1 in APP-003545 or APP-003547, APP-003546 and APP-003548 of country versions.