| Release | Comarch ERP Enterprise 6.4 |
| Release date | 08.08.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.4.
This fix comprises the following support deliveries: RFR-016563 – RFR-016565
Information about the features of Comarch ERP Enterprise 6.4 (release news): · INF-002734 Release-News: Betriebswirtschaftliche Lösungen · INF-002735 Release-News: Technische Lösungen System requirements: · INF-002736 Systemvoraussetzungen Comarch ERP Enterprise 6.4
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 CEE640PB-Fix11”.
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 CEE640PB-Fix11
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix10 will be upgraded to CEE640PB-Fix11.
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 CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
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 Cumulative installation of support deliveries
Code status CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or 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.4 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.
4 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016565 Ergonomics
Update of the English language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016565 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016565 Correction
Framework: Production
Application: Operations, Routings, Bills of materials, Bills of resources, Resource lists
View: n.a.
Action: Create document
Category: Exception
Problem: Performing action “Create document” in mentioned applications for object that has not any released version caused exception.
Correction result: Now exception is not thrown and proper document is generated and opened.
RFR-016565 Correction
Framework: Purchasing
Application: Cockpit: Suppliers
View: n.a.
Action: Load
Category: Performance
Problem: Loading a supplier takes too much time.
Correction result: From now loading a supplier will be faster than before
Technical information: From now a condition, former placed in the where clause of the search object, is moved and added in a join condition directly.
Framework: Sales
Application: Cockpit: Customers
View: n.a.
Action: Load
Category: Performance
Problem: Loading a customer takes too much time.
Correction result: From now loading a customer will be faster than before
Technical information: From now a condition, former placed in the where clause of the search object, is moved and added to a join condition directly.
5.1.1 Base
5.1.1.1 Classifications
RFR-016565 Correction
Framework: Base
Application: Classifications
Action: “Delete”, “Mark for delete”
Category: Exception / Unexpected behavior / Ergonomics
Problem: If a specific classification type is maintained on the organization level and a new relevant organization was added (status “Entered”) and a node has no data for such organization an IllegalStateException (“Classification was not replicated for organization …”) occurs during the try to delete or set a deletion marker for such a node.
Correction result: Now instead of the exception an error message will be send (existing error message “GEN-07115”).
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016565 Extension
- Classes: “com.cisag.app.sales.proposal.log. ProposalEntity”, “com.cisag.app.sales.order.log.OrderEntity” and “com.cisag.app.multiorg.order.log. OrderEntity”
new methods:
– public final void setAvailabilityValidationDisabled(boolean availabilityValidationDisabled)
– public final boolean isAvailabilityValidationDisabled()
Description:
Theses new methods can be used to disable the availability validation even if it is enabled with respect to the relevant document type instance and item master data.
This is useful if the availability validation is not needed in some cases (e.g. import or document generation).Hint: Please note that an “availability inquiry/validation” might be performed in some cases also if “availability validation” is disabled by this new property (e.g. because of item property “replaced/deleted if availability is zero”).2.
The new method “setAvailabilityValidationDisabled” is used now in the following classes (together with “entity. getReservationLogic().disableTemporaryData(true)”): – com.cisag.app.inventory.receipt.log. SalesOrderGenerator
– com.cisag.app.multiorg.order.log.OrderBatchLogic
– com.cisag.app.multiorg. order.log.OrderImportController
– com.cisag.app.sales.customerreturn.log.AbstractOrderGenerator
– com.cisag.app.sales.order.log.OrderBatchLogic
– com.cisag.app.sales.order.log. OrderImportController
– com.cisag.app.sales.proposal.log.ProposalBatchLogic
– com.cisag.app.sales. proposal.log.ProposalImportController
– com.cisag.app.sales.rapid.log.TargetEntityFactory3.
Class: “com.cisag.app.general.order.log.ReservationChangeData”.
methods: public void change(…, boolean newInstance, …)
The java documentation of the “newInstance” parameter has been corrected.
5.1.1.3 Items
RFR-016565 Correction
Framework: General
Application: Items, Import processes with items
View: n.a.
Action: n.a.
Category: Performance
Technical information: From now several classes regarding to the item import process will be performance-optimized.
RFR-016565 Correction
Framework: General
Application: Items
View: Base
Action: Validate / Update
Category: Exception
Problem: An exception occurred if the user tried to create inventory packaging definitions using not defined unit of measures.
Correction result: From now this situation will be validated as expected and an error message will be displayed.
5.1.1.4 Partners
RFR-016565 Correction
Framework: General
Application: Partners, Partner templates
View: n.a.
Action: Import, Import with template, Create partner from template
Category: Performance
Problem: The processes partner import, partner import with template and creating a partner from template were to slow.
Correction result: From now these processes will be much faster.
RFR-016565 Correction
Framework: General
Application: Partners
View: Financials data
Action: Switch organization via organization selector
Category: Exception
Problem: The exception occurred if the user is not authorized to load the company data and the current organization is not a sales organization and not purchasing organization.
Correction result: From now switching between organizations will work as expected.
RFR-016565 Correction
Class: cisag.app.general.partner.log. OrganizationalUnitPartnerEntity
Method: retrieveOtherSalesOrganizationalUnitPartner(byte[], byte[]), retrieveOtherPurchasingOrganizationalUnitPartner(byte[], byte[])
Description: Improving performance.
5.1.2 Calculation
RFR-016565 Correction
Framework: Calculation
Application: Output product cost calculations
View: n.a.
Action: Output report document in batch, Output report document immediately and display output to file
Category: Unexpected behavior
Problem: Selecting and outputting multiple product cost calculations is allowed and results in headers for all but the first product cost calculation missing from the output.
Correction result: Prevent selection of multiple product cost calculations at once. Add validation and error messages for the single selected product cost calculation.
5.1.2.1 Calculation – General
RFR-016565 Correction
Framework: Calculation
Application: Product cost calcultion maintenance
View: Total sum view
Action: Calculate…
Category: Unexpected behavior
Problem: Toggle button “Total” is clicked and total sums are displayed. Next button “Create simulation costs” is clicked.
Result: Beneath column “Simulated value” the total sums of simulated cost must be displayed. After creation of simulated costs simulated sums must have the same values as its counterparts of column “Total costs”. But “Labor costs” of simulated sums is missing.
If “Simulate with changed costs” is clicked “Labor costs” of simulated sums is displayed with correct calculated value.
Correction result: If in above described sequence button “Create simulation costs” is clicked “Labor costs” of simulated sums is displayed with correct value (same value as its counterpart of column “Total costs”).
Please note:
Product cost calculations calculated before this correction has been activated still show the incorrect behavior. This behavior changes after a calculation is performed anew.
5.1.3 Inventory management
5.1.3.1 Availability query
RFR-016565 Correction
Framework: Inventory Management
Application: Availability queries
View: All views
Action: Load
Category: Exception
Problem: Although the selection data were not valid it was tried to load data or execute list actions.
Correction result: If the selection data is not valid the list will be disabled as expected.
5.1.3.2 Inventory management – General
RFR-016565 Correction
Framework: Inventory
Application: Delivery orders, Cockpit: delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Exception
Problem: The completion of a delivery order failed (in a second try after a cancelation) because of an IllegalStateException because of a wrong inventory status of a loading unit, that contains to the delivery order.
Correction result: From now the completion of a delivery order will not crash because of a wrong inventory status of a loading unit, … even if it is the second try to complete the delivery order after a cancelation in the first try.
5.1.3.3 Reservations
RFR-016565 Correction
Framework: Inventory management
Application: Picking orders
View: n.a.
Action: Generate inventory order…
Category: Exception
Problem: If the reservation data were not correct (over reservation) because of an inventory count process and the concerned item supports inventory packings the inventory order generation could cause an exception.
Correction result: The inventory orders can be generated for the existing available warehouse stock as expected.
RFR-016565 Correction
Class: com.cisag.app.inventory.stock.log. WarehouseStockStorage, com.cisag.app.inventory.reservation.log.FixedReservationWorker
Method: WarehouseItemStockDynamicStorage.loadStockData(CisList), FixedReservationWorker.Context.Transaction. begin()
Description: (WarehouseStockStorage) The OQL to detect the warehouse stock data was changed to improve the performance.
(FixedReservationWorker) The internal transaction handling within the fixed reservation logic was changed to improve the performance.
Several other little changes were made that belong to new not persistent availability and demand data to improve the performance.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016565 Correction
Framework: Purchasing
Application: Distribution order generation
View: n.a.
Action: Generate distribution orders
Category: Exception
Problem: In case there are no existing distribution recommendations in the DB (not even ones marked for deletion), a NullPointerException was thrown when Distribution order generation was run as a batch application via “Development objects”.
In case in distribution recommendation a batch job to create distribution orders was used as a time series, the first execution of the job worked normal (created distribution order and marked the used recommendations as deleted) but subsequent executions created further distribution orders from the same recommendations.
Correction result: In case there are no existing distribution recommendations in the DB (not even ones marked for deletion), instead of an NPE, info message “PUR-01109 No distribution generated. The selection provided no data.” is displayed.
In case in distribution recommendation a batch job to create distribution orders was used as a time series, the first execution of the job works normal: it creates a distribution order and marks the used recommendations as deleted, subsequent executions will not create distribution orders from the recommendations that have been marked for deletion.
5.1.4.2 Distribution recommendations
RFR-016565 Correction
Framework: Planning
Application: Distribution recommendations
View: List of recommendations
Action: Save
Category: Ergonomics
Problem: If user is editing delivery date AND availability date a transition time goods receipt is calculated out of the difference of the edited dates when recommendation is saved. If subsequently only one of the dates delivery date / availability date is changed, the corresponding date is calculated from the before achieved transition time goods receipt. This behavior also occurs when transition time goods receipt originally had a value greater zero due to transition time goods receipt of item -> planning view -> internal purchasing data.
If the user wants another relation between delivery date and availability date than the current one (that means another duration between these dates) he must (again) change both dates.
It can happen that the user erroneously changes these dates so that delivery date is after availability date which leads to an error message. Up to now this also leads to a negative value of transition time goods receipt and correction only works by changing both dates. This happens because calculation is done before validation and negative value thus remains.
Correction result: If user changes both delivery date and availability date and delivery date is after availability date the transition time goods receipt keeps its value. It will only be changed after user corrects his input so that saving is successful.
5.1.5 Planning
RFR-016565 Correction
Framework: Planning
Application: Material requirements planning, Generate purchasing recommendations, Generate distribution recommendations
View: n.a.
Action: Transfer planning data and execute planning, Generate purchasing recommendations, Generate distribution recommendations
Category: Unexpected behavior
Problem: If “availability date” was set to non-working day and:
1. “Transition time goods receipt” for the corresponding items was set to 0 days then the calculated delivery date was after availability date and displayed transition time was negative.
2. “Transition time goods receipt” was bigger than 0 days then the calculated delivery date was transitional time plus one working days before availability date and displayed transition time in purchasing/distribution recommendations application was always one day bigger then corresponding item “transition time goods receipt”.
Correction result: If “availability date” for recommendation is set to non-working day and:
1. “Transitional time goods receipt” in item planning data is 0 the calculated delivery date is on first working day before availability date which means negative transition time and wrong order of dates is not generated anymore.
2. “Transitional time goods receipt” is bigger than 0 days the distance between availability date and delivery date in recommendations is always equal to the one specified in item planning data.
RFR-016565 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning
Category: Unexpected behavior
Problem: Context: Planning parameter “Plan inventoried packaging units” is active, Items ->Planning view “Plan inventoried packaging units” is active for some items. These items must have defined some inventoried item packaging units.
Planning is executed.
Result: For one or more of the items an error message is output in log file: “PRD-02532 The inventory-managed packaging units of article AX_10122 cannot be converted to the first article unit. Article is not planned.”
This is due to a wrong transfer of inventoried packaging. For specific sets of inventoried packaging units, a necessary transfer of first unit of item is missing which causes the error.
Correction result: In above described context transfer of inventoried packaging units together with first unit of item works properly. No such error message is output and items are planned properly.
5.1.6 Production
RFR-016565 Correction
Framework: Production
Application: Production Orders, Cockpit: Production Orders
View: n.a.
Action: Release, Dispatch and release
Category: Unexpected behavior
Problem: No error message is displayed, when item identifier creation fails, e.g., because the number-range ran out of numbers.
Correction result: An appropriate error message is shown.
Additionally, some potential problems with locking and saving have been fixed.
5.1.6.1 Bills of material
RFR-016565 Correction
Framework: Production
Application: Operations/ Operations templates Bills of materials / Bills of resources / Routings
View: n.a.
Action: Use value assistant in version field
Category: Unexpected behavior
Problem: When searching for a version of a ProductionPlan (i.e. bill of material, operation, etc.), all versions for all existing production plans independent of type were displayed, even if the code of a ProductionPlan was already typed into the corresponding field.
Correction result: Only the versions of the corresponding ProductionPlan (and ProductionPlanType) are displayed.
5.1.6.2 Resource groups
RFR-016565 Correction
Framework: Production
Application: Resource groups
View: n.a.
Action: n.a.
Open application
Category: Unexpected behavior
Problem: Even though resource groups with capacity category “unlimited” are not allowed, it was possible to select this a field in application “Resource groups”. When trying to save, this led to error “PRD-02338 – A resource group may not be unlimited”.
Correction result: The field has been removed. Capacity category of resource groups is now “time-dependent” by default.
5.1.7 Purchasing
5.1.7.1 Supplier invoices
RFR-016565 Correction
Framework: Purchasing
Application: Supplier invoices (additional costs)
Action: Assign orders
Category: Exception / Unexpected behavior
Problem: In contrast to normal invoices additional cost invoices support the usage of orders with a different currency. If such a different order currency cannot be converted into the supplier invoice currency an exception occurs before this correction.
Correction result: Now the exception does not occur any more.
RFR-016565 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Apply defaults
Category: Invalid data / Unexpected behavior
Problem: In a supplier invoice contains a kit main detail and the “cash discount base” of this kit main detail is maintained manually the kit component “cash discount base” value might be wrong if the “cash discount base” of this kit main detail was changed multiple times.
Correction result: Now the error does not occur any more.
RFR-016565 Correction
Framework: Purchasing
Application: Cockpit: Supplier invoices
Action: Mark for delete (reorganization)
Category: Invalid data / Unexpected behavior
Problem: In contrast to the supplier invoice application the deletion (here: reorganization) marker can be set by mistake since 6.2 for supplier invoices by the cockpit also for open invoices.
Correction result: Now the behavior is again as expected.
Hints: – In contrast to 6.1 the check with the message “PUR, 1267” will be performed now only if the message “PUR, 1264” was not send.
Hint: In the same way now also the customer invoice check with the messages “SAL, 8152” and “SAL, 8153” will be performed now only if the message “SAL, 2049” was not send.
– Also in contrast to 6.1 the checks that belong to the messages “PUR, 1268”, “PUR, 1269”, “PUR, 1269” and the “InternalInvoicingData”-validations will be performed only at reorganization time (as for customer invoices).
5.1.8 Sales
5.1.8.1 Sales quotations
RFR-016565 Correction
Framework: Sales
Application: Customer proposals
Action: Copy or create by source, Import, …
Category: Invalid data / Unexpected behavior
Problem: In contrast to other order types the “customer proposal header source data” was not created correctly before this correction.
Especially the “com.cisag.app.general.order.hook.log. HeaderSourceState” was created after building the “com.cisag.app.sales.proposal.model. CustomerProposalAccess” so that for example a “com.cisag.app.general.order.hook.log.HeaderSourceState” implementation was not present as expected within a “com.cisag.pgm.base.hook.DataAccessInitializerHook” implementation.
Correction result: Now the behavior is as expected.
5.1.9 Storage Location Control
5.1.9.1 Inventory order types
RFR-016565 Correction
Framework: Storage Location Control
Application: Inventory order types
View: n.a.
Action: Save
Category: Exception
Problem: If a supplement was created for the inventory order type business object (TransportOrderType) an exception could be caused at save.
Correction result: The inventory order type can be saved as expected.
5.2 System development
RFR-016563 Correction
Framework: System management
Application: Individual indexes
View: both
Action: load
Category: Unexpected behavior
Problem: When the user types the name of an index and presses enter, the application reports that data has changed, even though nothing has changed.
Correction result: The application loads the specified index on enter.
RFR-016563 Correction
Framework: System management
Application: System cockpit
View: Application Server, Tab Database connections
Action: Double click on an active connection.
Category: Invalid data
Problem: The dialog shows the active SQL statement. In rare cases, it may happen that the current SQL is not displayed here, but an older one.
Correction result: The dialog shows the current SQL statement.
RFR-016563 Extension
Framework: All
Application: Cockpit applications
View: n.a
Action: “Export objects according to search criteria” and “Copy hyperlink with search criteria”
Columns in REST export dialog in adaptable cockpits are now ordered in the same way as visible in the cockpit (left to right, top to bottom).
RFR-016563 Correction
Fixes to Software Development customizing.
RFR-016563 Correction
Framework: System management
Application: Output manager configurations
View: n.a.
Action: Modifying a persistent instance
Category: Unexpected behavior
Problem: A persistent instance cannot be changed because of a bug in the validation.
Correction result: Persistent instances can be changed.
RFR-016563 Correction
Optimizing CisConnectionPool
RFR-016564 Correction
Deletion marker for help object “com.cisag.sys.help. systemmanagement.startup.StartRedirectService” (Umleitungsdienst für Demo-Systeme starten) has been set.
5.2.1 Application server
5.2.1.1 Batch
RFR-016563 Correction
Framework: System Management
Batch application dialogs
Category: Ergonomics
Problem: The notification options “only in case of errors” in the batch job submit dialog, tab “Background settings”, does not result in a notification if the batch job has error messages in the job log, but the job is finished in “Completed” state.
Correction result: The behavior is correct because of the “Completed” status. The option labels were changed to “in case of an abort” to clarify how the notifications work.
RFR-016564 Correction
Framework: System Management
Batch application dialogs
Category: Ergonomics
Problem: The notification options “only in case of errors” in the batch job submit dialog, tab “Background settings”, does not result in a notification if the batch job has error messages in the job log, but the job is finished in “Completed” state.
Correction result: The behavior is correct because of the “Completed” status. The option labels were changed to “in case of an abort” to clarify how the notifications work.
5.2.1.2 Chat
RFR-016563 Extension
Framework: All
Application: ChatERP
View: ChatERP
Action: Show follow-up suggestions
Category: New features
Description: At start (or starting a new conversation), ChatERP now shows some example prompts. Additionally, a new button below each answer provides suggestions for follow-up prompts. These follow-up suggestion will be computed based on the actual conversation.
RFR-016564 Extension
Framework: All
Application: ChatERP
View: ChatERP
Action: Show follow-up suggestions
Category: New features
Description: At start (or starting a new conversation), ChatERP now shows some example prompts. Additionally, a new button below each answer provides suggestions for follow-up prompts. These follow-up suggestion will be computed based on the actual conversation.
5.2.2 Data exchange
RFR-016563 Correction
Framework: System Management
Application: Simplified data export, Simplified data import
Category: Unexpected behavior
Problem: In a BIS Lite export or import, an “IllegalOperationException” message could appear if the underlying BIS controller is extended using hook contract “com.cisag.pgm.bi.Controller”, hook “DependentAssociationHook”.
Correction result: The problem was resolved by modifying a detail in the extended part of the BIS controller’s ObjectInfo.
RFR-016563 Correction
Framework: Import data automatically
Execution of batch application
Category: Unexpected behavior
Problem: When the automatic data import is run to create batch jobs for files to import, the main batch job could have an unusual high CPU utilization.
Correction result: The problem is resolved.
5.2.3 GUI
RFR-016563 Correction
Framework: Software development
Class: com.cisag.pgm. gui.CalendarComponent and related
View: n.a.
Action: n.a.
Category: Unexpected behavior
Issue: Month view: Misplaced events (not placed at the top of each day).
Correction result: Fixed.
5.2.4 System – General
RFR-016563 Correction
Framework: Software Management
Application: Debug classes
View: n.a.
Action: Save and pin query template
Category: Unexpected behavior
Problem: Query templates do not work for this application, and the application’s history is not recorded.
Correction result: The problems are resolved.
RFR-016564 Correction
Framework: Software Management
Application: Debug classes
View: n.a.
Action: Save and pin query template
Category: Unexpected behavior
Problem: Query templates do not work for this application, and the application’s history is not recorded.
Correction result: The problems are resolved.
5.2.5 Web server
RFR-016563 Correction
Framework: System Management
Application: Swagger UI web application and Service for Swagger UI integration
Category: Exception
Problem: Swagger service returns code 500 when trying to load webservice classes that are not present.
Correction result: Webservice returns json file containing all properly loaded webservice classes, information about missing webservices is present in debug mode.