| Release | Comarch ERP Enterprise 6.5 |
| Release date | 09.01.2026 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.5.
This fix comprises the following support deliveries: RFR-016593 – RFR-016595
Information about the features of Comarch ERP Enterprise 6.5 (release news): · INF-002815 Release-News: Betriebswirtschaftliche Lösungen (wird nachgeliefert) · INF-002814 Release-News: Technische Lösungen (wird nachgeliefert) System requirements: · INF-002813 Systemvoraussetzungen Comarch ERP Enterprise 6.5
To install the support deliveries, please use the following documentation: · “Introduction: Software Logistics” (German language version) · „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.
The cumulative installation of support deliveries is described in INF-000228.
In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”. |
1 Information about support deliveries
The “Query support deliveries” application in the support system allows you to download directly from Comarch ERP Enterprise the support deliveries with their corresponding delivery documentation as well as further information.
The following types of support deliveries are relevant for you:
- RFR
This type of support delivery comprises a software upate or a file delivery as well as the corresponding delivery documentation.
- INF
This type of support delivery is used to provide FAQ-like information in a document.
- LNG
This type of support delivery is used to deliver language updates that can be installed in addition to German (de).
- 900
This type of support delivery comprises adaptors for the communication with third-party systems. - APP
This type of support delivery comprises installable Apps as well as the corresponding delivery documentation.
The available support deliveries are displayed in the “Query support deliveries” application according to the selected release, delivery, or delivery date. You can search for support deliveries and download their content. You can also find out whether new support deliveries are available. The application keeps a log on who has displayed which information or downloaded which software update, and when.
2 Installation of software updates
Follow the instructions given in the documentation “Introduction: Software Logistics” to install the software updates that are contained in the support deliveries. If there are deviating instructions to be followed, they are provided in chapter “Information about CEE650PB-Fix03”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE650PB-Fix03
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE650PB-Fix02 will be upgraded to CEE650PB-Fix03.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CEE640PB and CEE640PB-Fix12, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE650PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.3 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
3.4 Cumulative installation of support deliveries
Code status CEE640PB is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.4 and Comarch ERP Enterprise 6.5 at the same time. Support deliveries for Comarch ERP Enterprise 6.5 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
4 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
With the “Query data updates” application, you must schedule the following batch data updates, for any point in time.
Items – update inheritance
This application will update organization depending item data. It will remove inherited purchase, sales, inventory, production and planning data, that must not exist because the corresponding functions are not released in the application “Customizing.” Moreover, it checks for production- and planning data if inventory data exists for an item / organization combination. If not, production- and planning data will be also removed.
5 Contained changes and extensions
5.1 Application development
RFR-016595 Correction
Framework: n.a.
Application: Other fields in applications
View: n.a.
Action: n.a.
Using other fields of type valueset
Category: Unexpected behavior
Problem: If the display language deviates from the standard, the correct entries are not displayed in the value set.
Correction result: The valueset shows the correct translated entries.
RFR-016595 Correction
Framework: General
Application: Items
View: n.a.
Action: Accept data for the selected organizations and for their subordinate organizations
Category: Invalid data / Unexpected behavior
Problem: As an error the action created inherited data for organizations, where these data were not allowed, because the corresponding functions in the application “Customizing” were not released or no corresponding inventory data exist.
Correction result: From now this action will inherit data for organizations only, where these data be allowed allowed.
Data update: com.cisag.app.update.log.UPDBUG030255
RFR-016595 Correction
Framework: Software Development
Application: Supportrequest
View: n.a.
Action: Adding an upload to a text.
Category: Exception
Problem: In rare cases, exceptions may occur during the upload process.
Correction result: The exception no longer occurs.
5.1.1 Base
RFR-016595 Correction
Framework: Base
View:n.a.
Action: Import data/com. cisag.app.general.log.SingleObjectEntityController
Category: Exception
Problem: An exception occurred if an organization is needed to create an instance via import as background process, but the attribute ‘organizationalUnit’ is not part of the primary/business key.
Correction result: The problem is fixed and it is now possible to import data without exception, even if the import is done as a background process.
5.1.1.1 Currencies
RFR-016595 Correction
Framework: General
Application: Cockpit: Exchange rate history
View: n.a.
Action: Load, Switch between applications
Category: Unexpected behavior / Ergonomics
Problem:
1. The value in the “Valid until” date field increased 1 day every time if the user switched to another application and turned back afterwards.
2. The search result range did not match the value of the “Valid from” field. The search result moreover contained results from 12 hours earlier than the date in “valid from”.
Correction result: From now the application will work as expected.
5.1.1.2 Partners
RFR-016595 Correction
Framework: General
Application: Import data
Filter: com.cisag.app.general.obj.Partner
Action: Import data
Category: Unexpected behavior
Problem: Trying to delete a region of an address data using an empty association (i.E. ) in XML-file failed.
Correction result: From now deleting a region of an address data using an empty association in XML-file will work as expected.
5.1.2 Inventory management
5.1.2.1 Delivery orders
RFR-016595 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: After clicking this action confirming a warning because of a delivery block for the customer has no effect, … even if the delivery should be allowed because confirming the warning is allowed in the application “Customizing” (Function “Finance).
Correction result: From now after clicking this action confirming a warning works as expected.
RFR-016595 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: In the delivery slip report (pdf) the unit of measures (UOM) of order quantities of delivery slip detail lines were not displayed in the right way. That was the case if the displayed UOM has a system unit of measure that is different of it.
Correction result: From now the unit of measures of order quantities of delivery slip detail lines will be displayed as expected.
5.1.2.2 Inventory management – General
RFR-016595 Correction
Framework: Inventory Management
Application: Transaction date determination rules
View: n.a.
Action: Determine last transaction date
Category: Exception
Problem: If the rule considered loading unit packaging posting that did not have any item an exception would be caused.
Correction result: The data will be detected as expected.
5.1.2.3 Inventory query
RFR-016595 Correction
Framework: Inventory Management, Storage Location Control
Application: Cockpit: Inventories, Cockpit: Storage location inventories
View: n.a.
Action: n.a.
Field/Column: Verpackt (german description)
New sub detail search Ladeeinheiteninformation-Ladeeinheiteninhalte (german description)
Category: New field / New sub detail search
Description: Cockpit: Inventories:
– New column (icon and tool tip) to display whether a stock is packed partially or completely (not displayed as default).
– New sub detail search to display the loading unit content especially for not pure loading units (not displayed as default). Sub Detail search based upon the parent search “Item loading unit information.”
– Some layout changes for a better overview of loading unit stock data
Cockpit: Storage location inventories:
– New column (icon and tool tip) to display whether a stock is packed partially or completely (displayed as default)
– New sub detail search to display the loading unit content especially for not pure loading units (not displayed as default). Sub Detail search based upon the parent search “Item loading unit information”.
– Some layout changes for a better overview of loading unit stock data.
5.1.3 OLAP
5.1.3.1 Sales statistics
RFR-016595 Correction
Class: com.cisag.app.statistic.ui. StatisticViewerList
Method: n.a.
Description: From now the list will display all month rows of a year on one page.
5.1.4 Planning
RFR-016595 Extension
Framework: Purchasing, Production
Application: Cockpit: purchasing recommendations, Cockpit: distribution recommendations, Cockpit: production recommendations
View: n.a.
Action: Mark for deletion, Unmark for deletion
Category: New actions
Description: In recommendation cockpits new actions to mark for deletion and unmark for deletion have been added.
RFR-016595 Correction
Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: New and Accept in detail editor
Category: Exception
Problem: Trying to create new purchasing recommendation manually triggers exception during accept action if validation finished successfully.
Correction result: Exception does not occur anymore and new recommendation is properly created.
5.1.4.1 Planning conflicts query
RFR-016595 Correction
Framework: Planning
Application: Cockpit: Planning conflicts
View: n.a.
Action: Refresh
Category: Exception
Problem: Picking order from delivery order for sales order needs to be generated for item with at least one packaging unit. Unit of total quantity and reported quantity of delivery order needs to be different, but both acceptable for chosen item.
After performing planning which starts after voucher date of delivery order for that item the planning conflict about “Finished/Semi-finished goods demand in previous period” should be generated. Opening “Cockpit: planning conflicts” for that item caused exception due to different unit of measurement for total and reported quantity of a delivery order detail.
Correction result: Now units are properly converted to the total quantity unit and exception does not occur anymore.
5.1.5 Production
RFR-016595 Correction
Framework: Production
Application: Data updates
View: n.a.
Action: Run application
Category: Unexpected behaviour
Problem: Calling the data update multiple times resulted in “Canceled with error”.
Correction result: Calling the data update multiple times succeeds.
5.1.6 Sales
5.1.6.1 Sales fast entry vouchers
RFR-016595 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Apply defaults
Category: Exception / Unexpected behavior
Problem: If the value “Binding” is determined for the attribute “Binding unit” an exception occurs.
Correction result: Now the exception does not occur anymore.
5.1.6.2 Sales orders
RFR-016595 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: Detail line items of type ‘service’ weren’t be delivered if no picking order was created (and completed) for the delivery order and the detail line items warehouse attribute is set to a warehouse with location organization.
Correction result: From now, as expected, the open deliver quantity of a detail line item of type ‘service’ will be delivered in that case.
5.2 System development
RFR-016594 Correction
Framework: System Management
Application: E-Mail server
View: n.a.
Action: Validate, Save
Category: Unexpected behavior
Problem: User and password fields, one of them can be empty and the other one not empty.
Correction result: It is allowed both fields are either empty or not empty. Not allowed is that one field is empty and the other one not empty.
RFR-016594 Ergonomics
Framework: Software development
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics
Problem: There was no parallel development for tasks created using the editorial cockpit.
Correction result: Parallel development is now active for tasks created within the context of editorial cockpits. Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.
RFR-016593 Ergonomics
Framework: Software development
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics
Problem: There was no parallel development for tasks created using the editorial cockpit.
Correction result: Parallel development is now active for tasks created within the context of editorial cockpits. Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.
RFR-016593 Correction
Framework: All
Application: All cockpits
View: n.a.
Action: Searching
Category: Exception
Problem: An exception may occur if a search is performed in a customizable cockpit with detailed search enabled, and then a search is performed without detailed search enabled.
Correction result: The exception no longer occurs.
Terminus objects are part of parallel development.
RFR-016593 Correction
Framework: Software development
Application: Cockpit : production level development objects
View: n.a.
Process: Transfer objects
Category: Exception
Problem: if the cross reference is wrong a null pointer exception occurs when trying to check an object from cross reference.
Correction result: An extra check now prevents this null pointer exception.
RFR-016593 Correction
Framework: n.a.
Application: n.a.
View: n. a
Action: n.a.
Category: Unexpected behavior
Problem: Sometimes Method “com.cisag.pgm.base. CisApplication.setObjectDescription(String)” will be called with too long parameter string.
Correction result: “com.cisag.pgm.base.CisApplication.setObjectDescription(String)” will reduce the input parameter string to length 1000, if it is longer than 1000.
RFR-016593 Correction
Framework: System Management
Application: E-Mail server
View: n.a.
Action: Validate, Save
Category: Unexpected behavior
Problem: user and password fields, one of them can be empty and the other one not empty.
Correction result: It is allowed both fields are either empty or not empty. Not allowed one field empty and the other one not empty.
5.2.1 Application server
5.2.1.1 StartUp
RFR-016593 Correction
Framework: Software development
Application: Update destination system
Category: Unexpected behavior
Problem: The batch application may abort with an exception message “java.lang.NullPointerException (…) at com.cisag.sys.sis.log.RefreshTargetSystem. checkWritingRemote” if the execution begins at start of the application server.
Correction result: The problem is resolved.
5.2.2 Configuration
5.2.2.1 Tools
RFR-016593 Correction
Framework: System Management
Application: Tool chkcnf (Check configuration)
View: n.a.
Action: Execute the tool
Category: Exception
Problem: When executing the toolshell command chkcnf -displayLostDependents, the following exception message may be displayed: SQLServerException: Ungültiger Objektname “PROXYUSERGROUPASSIGNMENT” (or similar).
Correction result: The problem is resolved.
5.2.3 Data exchange
RFR-016593 Correction
Framework: System management
Application: Import data
View: n.a.
Action: Import data
Category: Unexpected behavior
Problem: Setting a foreign key to NULL value, could not remove it from its Business entity.
Correction result: Foreign key on a business entity can be removed.
RFR-016593 Correction
Framework: System Management
Application: Import data
View: n.a.
Action: Import data
Category: Exception
Problem: If an XML import file contains an empty XML element for a supplement business object, an import may abort with an exception message “java.lang.RuntimeException: Attribute or association without Target or Source”.
Correction result: The problem is resolved, the exception does not occur.
Technical information: A workaround for this problem is to either remove the XML element from the import file, or to make the XML element non-empty.
5.2.4 Knowledge Store
RFR-016593 Correction
Framework: Document Management
Application: Documents
View: n.a.
Action: Generate document file from template
Category: Unexpected behavior
Problem: Paragraphs in table cells that contain only empty merge fields were not automatically removed.
Correction result: Fixed.