| Release | Comarch ERP Enterprise 6.4 |
| Release date | 14.11.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-016584 – RFR-016586
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-Fix13”.
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-Fix13
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix12 will be upgraded to CEE640PB-Fix13.
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
Mithilfe der Anwendung „Datenaktualisierungen abfragen“ müssen Sie alle in diesem Abschnitt aufgeführten Datenaktualisierungen für einen beliebigen Termin zur Ausführung einplanen.
UPDBUG030140
Loading units – Creating loading unit status objects
This update application will create a loading unit status object (com.cisag.app.shipping.obj.UnitLoadStatus) as 1:1 Dependent for all actual loading unit objects (com.cisag.app.shipping.obj.UnitLoad with UnitLoad:version = 0) that don’t have any. It is required, that the data update application com.cisag.app.update.log.UPDADV103530E, that is part of the update from CEE6.3 to CEE6.4, run before.
UPDSUP122635
UPDSUP122696
SalesDetailGroupDocumentData: Initialisiert die fehlenden Hauswährungs-Attribute
Versehentlich wurden Instanzen des BOs „SalesDetailGroupDocumentData“ mit leeren Werten für die internen Attribute „_organization“, „_conversionDate“ und „_currencyCombo“ erstellt. Diese Datenaktualisierungsanwendung füllt leere Attribute mit den Werten des entsprechenden Besitzer-BOs (CustomerProposal, SalesOrder oder Confirmation).
5 Contained changes and extensions
5.1 Application development
RFR-016586 Correction
Framework: Base
Application: n.a.
View: n.a.
Action: n.a.
com.cisag.app.general.item.log.ItemPropertyVirtualTable
Category: Unexpected behavior
Problem: Due to the data model change for item characteristics, the virtual table no longer worked.
Correction result: The virtual table works as expected.
RFR-016586 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-016586 Correction
Framework: Base
Application: Items
View: n.a.
Action: Opening field search for item properties
Category: Unexpected behavior
Problem: Long text fields cannot be used in searches because their content is stored in a blob. Nevertheless, the field was displayed in the item properties search. However, input had no effect on the search.
Correction result: The field is displayed as Disabled. A tooltip indicates that the field cannot be used in the search.
RFR-016586 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-016586 Correction
Framework: Base
Application: n.a.
View: n.a.
Action: n.a.
com.cisag.app.general.item.log.ItemPropertyVirtualTable
Category: Unexpected behavior
Problem: Due to the data model change for item characteristics, the virtual table no longer worked.
Correction result: The virtual table works as expected.
RFR-016586 Correction
Label correction for “Complete loading” (com.cisag.app. shipping.shippingload.Complete) from “Verladung abschließen” to “Verladungsstatus prüfen und auf „Verladen“ setzen”, German only.
What’s this help and tooltip have been added.
5.1.1 Base
RFR-016586 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 backround 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 backround process.
5.1.1.1 Base – General
RFR-016586 Correction
Framework: v
Application: Export data
Object: com. cisag.app.purchasing.obj.PriceDefinition
Category: Unexpected behavior / Ergonomics
Problem: The label of the “Supplier price hierarchy” field has the wrong text “Customer price hierarchy”.
Correction result: Now the label is as expected.
RFR-016586 Correction
Frameworks: Purchasing/Sales
Applications: Purchase price lists, Sales price lists
Action: Import correction mode
Category: Exception / Unexpected behavior / Ergonomics
Problem: If the import file contains a wrong organization an “java.lang. IllegalArgumentException: organization does not exists! 000000000000000000000000000000F0” will be thrown so that the application closes with this error.
Correction result: Now – in analogx to the error messages within the import error file – a message will be send instead.
Hint: Please note that application does not support a correction of the organization – so, you have to correct the import source data.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016586 Ergonomics
Frameworks: Purchasing, Sales
Applications: “Simulate purchasing/sales prices” and “Price origin dialog” of purchasing/sales documents
Action: Display calculation data
Category: Ergonomics
Description: The price calculation will be performed in this order for the following discount types:
1.) detail discounts
2.) header discounts
3.) classification discounts
4.) order value discounts
If any of these types has some non empty discounts a “sub total” will be calculated and used for the following discount types.
Before this extension such a “sub total” line was not displayed – so, it was difficult to unterstand which base value was used for a discount.
==> Up from now a “sub total” line will be displayed before the consideration of a “discount type” that has any “none empty data” (only if at least one previous “discount type” has also any “none empty data”).
Please note that – as before – there might be some more “sub total” lines if for the same “discount type” multiple discounts with different “calculation reference” values are present.
Further change if “Price displayed as” (“kind of pricing”) has the value “net”: If no “detail discounts” are present now a further information will be shown that displays the change from the “price level” to the “value level”.
Before this change this information was shown only if at least one detail discount was present.
In addition to that the “toString” logics of some data (e.g. foreign amounts) that are used for the “debug” functionality will be performed now only if the “debug” functionality is enabled.
RFR-016586 Correction
Frameworks: purchasing and sales
Applications: proposals and orders
Action: refresh
Category: Unexpected behavior
Problem:
1.) Purchasing and sales: The used “currency converter” and “price calculation” will be refreshed with respect to a changed “price date”.
2.) Sales only: The used “price calculation” will be refreshed with respect to a changed “kind of pricing”.
In some cases this refreshment was not performed or performed to late so that in some cases the wrong data was used – especially during the header discount values calculation.
Also the “load” step does not initialize in case of sales the “kind of pricing” of the “price calculation”.
Hint: Normally these errors does not have any negative effect because any relevant detail change will also trigger a refreshment of this data and also of the header discount values.
Correction result: To avoid problems the correct initialization and refreshment will be performed now.
Hint: If needed you can recalculate wrong proposals/orders.
5.1.1.3 Partners
RFR-016586 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 Calculation
RFR-016586 Extension
Framework: Calculation, Base
Application: Items, Import data
View: Financials
Action: Creating, Saving or Importing an Item with one or many Financial views
Category: Performance
Description: Creating a new Item through Items application or Import takes a lot of time to save the item prices of each Financial view to the history of item prices. This can take around 100ms per Financial view.
Performance is now improved by a factor of 5 to around 20ms per financial view, especially helping batch import of lots of items and lots of financial organizations.
5.1.2.1 Calculations
RFR-016586 Correction
Framework: Calculation
Application: Cockpit: Purchase items
View: n.a.
Action: Generate calculations…
Category: Unexpected behavior
Problem:
A.
Context: A calculation schema has set: “Supplier origin” = “Alternative supplier according to allocation data”. Some items have set a main supplier in applicaltion “Items” -> view “Planning data”. They do not have set an alternative supplier. Additionally each item has a supplier view specified with main supplier of planning view.
From “Cockpit: Purchasing Items” action “Generate calculations..” is started. In the dialog to this action no supplier is specified.
Result: Purchasing specific values for calculation are retrieved from main supplier according to planning data of calculated item. But it is expected that purchasing specific values are retrieved from purchasing data of calculated item as calculation schema requires alternative supplier which is not specified in planning data. Also purchase price will be retrieved from item + supplier if a price at this level is specified.
Please note: If alternative supplier is defined in planning data but has no supplier view defined in application “Items” purchasing specific values must also be retrieved from purchasing view. But purchase price may be retrieved from alternative supplier if one is specified at level item + supplier.
B.
Field “Supplier origin” is only editable if field “Valuation price” = “Price from price listing” is set. This is an unneccessary limitation.
Please note: field “supplier” is only editable if “Supplier origin” = “Manually defined suplier” is set.
Correction result:
A.
In above described context purchasing specific values are retrieved from purchasing data of calculated item. Also purchasing price is retrieve from item level.
B.
Field “Supplier origin” is editable without restriction.
5.1.3 Financials
5.1.3.1 Debitoren-Guthaben
RFR-016586 Correction
Framework: Financials
Application: Debtor credits
Action: Reduce unallocated credit reservations
Category: Unexpected behavior
Problem: The “Reduce unallocated credit reservations” logic considers a “isReducible” functionality that is based on a “DebtorCreditReservationReducibleHook”. This hook is implemented for “sales orders” by “com.cisag.app.sales.debtorcredit.log.SalesOrderDebtorCreditHookImpl”.
By mistake “SalesOrderDebtorCreditHookImpl” returns false also for “debtor credit reservation details” that does not have the order type value “sales order”. As result all other order type value can not be reduced.
By mistake the “com.cisag.app.sales.debtorcredit.log.SalesOrderDebtorCreditHookImpl” returns .
Correction result: Now the “SalesOrderDebtorCreditHookImpl” returns true if the “debtor credit reservation detail” does not have the order type value “sales order”.
So this hook implementation does not prevent any more the reduction of “debtor credit reservation details” that belong to other order types.
5.1.4 Inventory management
5.1.4.1 Delivery orders
RFR-016586 Correction
Framework: Planning
Application: Production recommendations
View: n.a.
Action: All generate/create production orders actions that dispatch order
Category: Unexpected behavior
Problem: Production recommendation of quantity 1 is generated for item with “Identifier category” set to “Serial number with inventory management” and “Creation methods” of “Identifier defaults” set to “Automatic”. Production order type used for generation has field “Time of determination of identifier” set to “When dispatching the production order”. Trying to perform generation of production order with dispatching for that configuration displayed multiple errors about not existing identifier, but production order was generated and dispatched, but without identifier.
Correction result: Identifier is now correctly created and set to newly generated production order without any errors.
RFR-016586 Correction
Framework: Purchasing
Application: Delivery orders
View: n.a.
Action: Complete external delivery…
Category: Exception
Problem: An exception occurred running the action “Complete external delivery…” for an external delivery order.
Correction result: From now running the action “Complete external delivery…” will work as expected.
RFR-016586 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-016586 Correction
Framework: Inventory, Sales
Application: Cockpit: Delivery orders
View: n.a.
Action: Create picking orders …
Category: Exception
Problem: An exception occurred creating a picking order for more than one selected delivery order.
Correction result: From now creating a picking order for more than one selected delivery order will work as expected.
5.1.4.2 Identifiers
RFR-016586 Correction
Framework: Inventory Management
Application: Identifier Tracking Inquiry
View: Origin
Action: Load identifier tracking data for “ALL” levels
Category: Unexpected behavior
Problem: The creation and sorting of the list took to many time (CPU usage).
Correction result: The identifier tracking data chains will be displayed as expected.
5.1.4.3 Inventory management – General
RFR-016586 Correction
Framework: Inventory
Application: Delivery orders / Packing dialog
View: n.a
Action: Generate, assign and display loadings units …
Category: Exception / Invalid data
Problem: When packing with a loading unit template that contains additional loading unit templates as detail lines, loading units are created without an associated status object. The loading units created are therefore invalid and cannot be loaded.
Correction result: From now packing with a loading unit template that contains additional loading unit templates as detail lines will work as expected.
Data update: UPDBUG030140
5.1.4.4 Loading units
RFR-016586 Correction
Framework: Production
Application: Inventory postings
View: n.a.
Action: Post
Category: Exception
Problem: Context: Production order detail has an item of type identifier. Issue warehouse and production warehouse differ. That means: picking is necessary.
A material issue posting is performed by application “Inventory postings” (field “Special process” = “material issue posting”). Instead of production warehouse the issue warehouse is specified. That means: no picking previously done.
Result: Posting fails due to an exception.
Correction result: In above described context a material issue posting via application “Inventory postings” succeeds without exception.
5.1.4.5 Loads
RFR-016586 Correction
Framework: Inventory
Application: Cockpit: Shipping loads
View: n.a.
Action: Mark as deleted
Category: Unexpected behavior
Problem: It was possible to mark a shipping load as deleted, that is not shipped already.
Correction result: From now marking a shipping load as deleted, that is not shipped already, will cause an error message.
5.1.4.6 Picking orders
RFR-016586 Correction
Framework: Inventory Management
Application: Picking orders
View: n.a.
Report set item and its kit items
Category: Exception
Problem: If a set item was reported that was supporting fixed reservations save would cause an exception.
Correction result: The set item and its component can be reported as expected.
5.1.4.7 Receipts of goods
RFR-016586 Correction
Class: com.cisag.app.inventory.receipt.log. ReceiptOrderAssignmentValidation
Method: Constructor, #validate(ReceiptDetail, ReceiptDetail, boolean), #validate(ReceiptDetailOrderAssignment), #validateDelete(ReceiptDetail persistentDetail)
Description: The declaration of the class, constructor and the listed methods is changed from ‘package private’ to ‘protected’
5.1.4.8 Warehouses
RFR-016586 Correction
Framework: Inventory Managment
Application: Warehouses
View: n.a.
Import changes of the inventory owner group
Category: Unexpected behavior
Problem: Import changes of the inventory owner group members were always denied.
Correction result: The members of an inventory owner group can be updated per import as expected.
5.1.5 OLAP
5.1.5.1 Vertriebs-Statistik
RFR-016586 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.6 Planning
RFR-016586 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: In case the planning Server is started in update mode with regular intervals and during the update it runs into a serious problem during the data transfer, because data was changed that cannot be reloaded in update mode, it will immediately try the next update which will also fail for the same reason again and again and again. This can happen when organizations were changed after the initial full data transfer.
Correction result: The completion of data transfer is internally tracked. If a data transfer was aborted, and an update should occur, the planning server will switch to full data transfer mode for one interval, then go back to update mode in the next intervals.
RFR-016586 Correction
Framework: Purchasing
Application: Distribution recommendations
View: n.a.
Action: Generate distribution orders
Category: Unexpected behavior
Problem: If an error occured during the generation of orders from distribution recommendations, the entire process was canceled, including for valid recommendations.
Correction result: The error handling now operates differently based on the level at which an error occurs: – header level error: If an error is found in the order’s header, the entire order and all of its corresponding recommendations are skipped.
– detail level error: If an error occurs in a specific detail line, only the recommendation associated with that detail is skipped. The rest of the order will continue to be processed.
A new validation for detail level errors has been introduced, controlled by new system property that is enabled by default. If this property is disabled, any detail level error is treated as a header-level error, causing the entire order to be skipped.
Technical information: New system property has been added to control detail validation during creation of distribution orders from recommendations: com.cisag.app.purchasing.log.GenerateDistributionOrder_ValidateDetails
5.1.6.1 Material requirements planning
RFR-016586 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning, Re-execute planning
Category: Unexpected behavior
Problem: Material requirements planning took a long time when a lot of items were planned, especially when planning multiple sites at once.
Correction result: Material requirements planning is faster, especially with many items and many sites.
RFR-016586 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem:
A: When an item was planning with delivery calendar and a recommendation was created for a delivery date, only the demands to the next delivery date were included, even in case the item had a demand coverage time range configured that should require to cover also demands after the next possible delivery date.
B: The planning automatically extends the demand period by non working days that immediately follow the currently planned day. In case a demand coverage time range is also configured, it also started immediately after the currently planned date, also covering the demands of the non-working days following the planning day. Thus, the demands of the extended planning period were counted twice, resulting in too high recommendations. This problem can only appear in case there are demands at non-working days.
Correction result:
A: After the planning decides that a recommendation is necessary considering the demands until the next possible delivery date, it will additionally find demands after the next delivery date until the end of the demand coverage range and include them into the recommendation quantity.
B: The demand coverage time range now starts AFTER the extended demand period of the planned day, so demands after the planned day in the extended demand period are not counted twice.
5.1.6.2 Material requirements query
RFR-016586 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem:
1. Message PRD-00485 displays in some situations incomplete informations: missing arguments. Messages PRD-00485, PRD-01078 and PRD-01099 in planning logs displays vague and unhelpful details.
2. Checkbox “Log untransferred line items” controls only displaying of messag PRD-01078.
Correction result:
1. Old messages was replaced by new enhanced messages which provide pricese details about real problems: * PRD-00485 replaced by APS-00125
* PRD-01078 replaced by APS-00123
* PRD-01099 replaced by APS-00124
2. Checkbox “Log untransferred line items” can now be used to determine if messages APS-00125 and APS-00123 are displayed in planning log file.
5.1.6.3 Planning conflicts query
RFR-016586 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.7 Production
RFR-016586 Correction
Framework: Production
Application: Reorganize production orders
View: n.a.
Action: n.a.
Category: Exception
Problem: A production order is reorganized even if there exists a parent or child production order referencing it, that would not be reorganized because of voucher chain dependencies.
This can lead to all sorts of other problems, like Exceptions when such a referenced order is edited.
Correction result: When checking whether a tree of production orders can be reorganized, it is also checked if certain voucher chain references prevent reorganization of the po.
5.1.7.1 Product configuration
RFR-016586 Correction
Framework: Production
Application: Product configuration rules
View: all views
Action: switch view
Category: Unexpected behavior
Problem: When user wanted to switch to a different view after data in the header was changed, a dialog was opened, where the user had to confirm the switch in order to not have the changes lost, when in fact, no header data is deleted by switching the view.
Correction result: No dialog is displayed when switching views after changing the header data. It will still appear when details are changed, as intended.
5.1.7.2 Production – General
RFR-016586 Correction
Framework: Production
Application: Order maintenance
View: Detail editor
Action: New detail
Category: Exception
Problem: If a production order is marked for deletion it is still possible to create new detail line items of all possible detail types. If such a action is executed a exeception occusrs.
Correction result: If a prduction order is marked for deletion all relevant production specific actions are disabled. No action at detil level can be performed.
5.1.7.3 Production issues
RFR-016586 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: Save, Validate
Category: Exception
Problem:
1. Before loading any production order entering proper production order type and number and performing action save caused exception.
2. Before loading any production order performing validation for empty order type and number fields caused exception. Additionally perfoming validation with proper type and number of order entered, but before loading it caused the load of production order, but with missing detail loading.
Correction result:
1. Action “Save” is now disabled if order is not loaded.
2. Action “Validate” is now disable if order is not loaded. Action load now properly displays errors about missing number and type of an order.
5.1.7.4 Production orders
RFR-016586 Correction
Framework: Sales, Production
Application: Sales order maintenance
View: n.a.
Action: Generate production orders…
Category: Unexpected behavior
Problem: When from a sales order production orders are generated following production order quantities must be set: a) If sales order (detail) quantity is of 1.st item unit, quantity of production order must be the same as of sales order
b) If sales order (detail) quantity is of a inventory managed packagin unit, quantity of production order must be the same as of sales order (that is of inventory managed packaging unit)
c) If sales order (detail) quantity is of a packging unit which is not inventory managed (“Conversion only”), quantity of production order must be of 1st item unit, converted from sales order from packaging unit
Variant c) does not work anymore since some time.
Correction result: Variant c) does work now as expected.
RFR-016586 Correction
Framework: Production
Application: Production order
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Opening any production order which was dispatched with empty “Dispatching date” automatically enters edit mode, trying to set proper value to this field even if order was already completed.
Correction result: New data update has been created to update empty “Dispatching date” in all already dispatched orders to avoid entering edit mode in “Production orders”.
Technical information: The possibility to keep that “Dispatching date” empty was fixed in one of the previous fix. This date is now set automatically during dispatching or manual adding of an detail. It means the problem occur only for production orders that was created/completed before mentioned previous fix.
Data update: UPDSUP122635
Sets “Dispatching date” for all dispatched production orders to proper value based on earliest begin, latest end and scheduling category of an order header.
5.1.8 Purchasing
5.1.8.1 Bonus agreements
RFR-016586 Correction
Framework: Purchasing, sales
Application: Purchasing bonus agreements, Sales bonus agreements
View: n.a.
Action: content change and save
Category: Unexpected behavior
Problem: If the “content language” in the user settings is set to “en”, any changes made to the “Description” field in Purchasing/Sales bonus agreements will not be saved.
Correction result: The problem has been fixed. We can now change and save any changes to the “Description” field if the language in the user settings is set to “en”.
5.1.8.2 Purchase orders
RFR-016586 Correction
Framework: Purchasing
Application: Purchase orders
Action: Apply defaults, “Delivery dun” creation
Category: Unexpected behavior
Problem:
1.) Before this change the “Delivery dun output settings” of a purchase order were determined by the “delivery partner” (“delivery supplier”); also the purchase order line item “delivery partner” was checked versus tbe current “delivery dun output settings”.
2.) The “Delivery dun” generation uses the main supplier of the purchase order (also for some checks and also as “archive partner”).
==> If the “main supplier” and the “delivery partner” are different and the “main supplier” does not support the determined output settings the delivery dun creation fails.
Correction result: Because the responsible business partner of a purchase order is the “main supplier” up from now the following rules will be used:
1.) The “Delivery dun output settings” of a purchase order will be determined now by the “main supplier”.
2.) The purchase order line item validation (“delivery partner” versus “delivery dun output settings”) was removed.
3.) “Output settings” table: If the current value is not defined (valid) it will be added now to the visible values – before this correction an empty value was displayed in this case.
Hints:
1.) Please note that with respect to this change the old “delivery dun output settings” value of a purchase order might not be valid any more and needs to be corrected manually.
2.) Within an extra development order the online help will be changed – also here the “delivery partner” is defined as relevant – this needs to be changed.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016586 Correction
Framework: Sales
Application: Customer invoices query
Action: Display
Category: Unexpected behavior / Ergonomics
Problem: If the invoice contains mor than one tax code instead of the text “Sum” the wrong value “com.cisag.app.sales.invoice.ui. CustomerInvoiceInquiry:TaxViewSum” is displayed.
Correction result: Now the text “Sum” will be displayed as expected.
RFR-016586 Correction
Framework: Sales
Application: Customer invoices
Action: Create
Category: Invalid data / Unexpected behavior
Problem: A utility class that was used for the customer invoice generation has had an error before this correction. As result the attribute “CustomerInvoiceOrderInfos#detailDiscountValues” contains in some cases a wrong value.
Correction result: Now the utility class has been corrected so that the customer invoice attribute contains now the expected data.
RFR-016586 Correction
Framework: Sales
Applications: Sales orders, Distribution orders, Customer invoices
Action: Cancel customer invoices
Category: Invalid data / Unexpected behavior
Problem: A sales order line item is present with the following data: – the sales order line item has a zero total quantity
– the sales order line item has some order value discounts (at least one)
The invoice generation creates correct data.
But the invoice cancelation does not report the correct (negated) value of the “order value discounts” – as result the next invoice generation does not consider the correct discount values.
Correction result: Now the invoice cancelation reports also in this case the correct discount values.
Hint: In analogy also the status update logic for distribution orders has been changed but here normally no zero total quantity can be used.
Data update:
If needed wrong existing data have to be changed manually. The recommended way is the following: – Cancel all invoices of the relevant order line items.
– if “com.cisag.app.sales. obj.SalesOrderDetailValueDiscount” is present for the relevant sales order line items: set “com.cisag. app.sales.obj.SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[0]” until “com.cisag.app.sales.obj. SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[3]” by OQL for the entry with the relevant order detail guid to zero.
– create again the invoices
5.1.9.2 Sales – General
RFR-016586 Correction
Framework: Sales
Applications: Customer proposals, Sales orders, Sales confirmations
Functionality: Detail group support
Category: Invalid data / Unexpected behavior
Problem: By mistake instances of the business object SalesDetailGroupDocumentData were created with empty values for the internal attributes “_organization”, “_conversionDate” and “_currencyCombo”.
Correction result: Now these attributes will be maintained as expected.
Data update:
Please execute the data update application UPDSUP122696 to correct the existing data.
5.1.9.3 Sales fast entry vouchers
RFR-016586 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Calculate tax
Category: Exception
Problem: In case of “retail calculation” an exception occurs during the step “Calculate tax” if the same application instance is used for multiple sales organizations.
Correction result: Now the exception does not occur any more.
5.1.9.4 Sales orders
RFR-016586 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Reserve inventory amount…
Category: Unexpected behavior
Problem: The sales order type reservation setting “Automatically with reservation term” avoided the manual reservation by the reservation dialog.
Correction result: The reservation dialog is using manual reservation settings and will ignore the automatic reservation settings now as expected.
5.1.10 Solutions Edition
5.1.10.1 Auftragsbezogene Beschaffung
RFR-016586 Correction
Framework: Sales
Application: Sales orders
Action: Save (sub step “Refresh purchase order line items”)
Category: Unexpected behavior
Problems:
1. )
Since “CEE640PB-Fix08 KW14/2025” the “Purchase order line item preferred date” will be changed by some rules with respect to a changed “delivery date”.
But if the “Transition time goods receipt” is used (only in case of “Delivery to issues warehouse”) an unchanged “Purchase order line item preferred date” will not be changed always in analogy to a changed “Purchase order line item delivery date”.
2. )
“Delivery to issues warehouse”: In some cases the “Purchase order line item availability date” is after the “Sales order shipping date”.
Correction results:
1.)
Changed behavior for “Purchase order line item preferred date”:
Precondition: The “Purchase order line item delivery date” changes.
Further conditions: – The “Purchase order line item preferred date” (old preferred date) is the same as the “Old delivery date converted into the preferred date” ==> assert not manually changed.
OR
– The “New purchase order delivery date” is before the “Purchase order line item preferred date” (old preferred date) ==> ensure that the new “Purchase order line item preferred date” is at least the “New purchase order delivery date”
Hint: But if if the “Purchase order line item preferred date” (old preferred date) is before the “New purchase order delivery date” it will stay unchanged.
2.)
Now it will be ensured that the “New purchase order delivery date” plus “Transition time goods receipt” (==>”Purchase order line item availability date”) is not after the “Sales order shipping date” (same date or before this date).
To ensure that the “New purchase order delivery date” will be moved in a loop one working day backwards until this rule is fulfilled.
5.2 Infrastructure
5.2.1 Softwareaktualisierungen installieren
RFR-016586 Correction
Framework: Data Update
Application: com.cisag.app. update.log.UPDADV107259
View: n.a.
Action: Execution of data update
Category: Exception
Technical information: The use of CisTransaction#commitIfSizeLimitExceeded() when updating data, to close and reopen database transactions only when necessary, caused problems with memory requirements, so that fixed block sizes had to be reintroduced in order to better control the memory requirements of this data update.
5.3 System development
RFR-016584 Extension
Framework: all
Application: Caching Mechanism
View: n.a.
Action: the change addresses a system-wide performance issue.
Category: Unexpected behavior
Problem:
All Business Objects (BOs) that contain a BLOB did not have a cache strategy. The framework intentionally prevents caching for such objects by default to avoid high memory consumption. However, for specific BOs with small BLOBs that are accessed frequently, this restriction led to significant performance problems, as they were reloaded from the database on every access.
Correction result:
A new override mechanism has been implemented. For a predefined list of BOs, the default restriction is now bypassed, and a cache strategy of **LRU (Least Recently Used)** is applied. This resolves the performance issues by allowing these frequently used objects to be cached effectively.
RFR-016585 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-016584 Correction
Class: CisObject
Method: copyTo, getTransientCopy
Description: in CisObject there is a content language field. This field only has effect when the user changes the “content language” settings field in the user settings application.
Setting a content language deviating from standard can cause issues when copying the data because the content language information was not transferred from the source to the target object.
When copying the content of an CisObject into another instance the content language is now copied as well. Only in the case that the target object is not transient (i.e. intended to be put by the object manager),
then the language is not set.
Copying CisObject with differnent content language is discouraged but technical possible.
RFR-016584 Correction
Framework: System Management
Application: System cockpit
View: Module
Action: n.a.
Category: Ergonomics
Problem: System groups were not sorted on General tab
Correction result: System groups are now sorted in alphabetical order
RFR-016584 Correction
Optimization of com.cisag.pgm.util.CisHashMap
RFR-016584 Correction
Framework: System management
Application: Individual indexes
View: n.a.
Action: Generate indexes
Category: Unexpected behavior
Problem: If errors occur during the creation of individual indexes, the application does not display them.
Correction result: The application displays a message indicating that errors occurred during creation. Furthermore, messages are written to the message log.
RFR-016584 Correction
intern.
RFR-016584 Correction
Framework: software development
Application: development objects
Action: validate for new objects
Category: Unexpected behavior
Problem: If a development object has a connected text data object and you just validate data, then any error message is shown because the name of the text data object is not yet set.
Similar problem with the file names for a java class object
Correction result: Before validating the names are now set.
Technical information: Directly saving works because in this case the names were set beforehand.
5.3.1 Kernel
RFR-016584 Correction
Framework: System
Application: Core System / Parser Infrastructure
View: n.a.
Action: n.a.
Category: Performance Improvement
Description: This change significantly improves the performance of internal parsing operations within the system. By optimizing the handling of frequently occurring internal `Error` instances, the system will process parsing tasks faster and consume less memory. This leads to a more responsive and efficient overall system.
Technical information: JavaCC parsers often utilize internal `Error` subclasses, such as `LookaheadSuccess`, as a control flow mechanism. These `Error` objects can be instantiated very frequently during parsing. Normally, the creation of an `Error` object involves the costly operation of filling the stack trace. By overriding the `fillInStackTrace()` method within the `private static final class LookaheadSuccess extends Error` to simply return `this`, the overhead associated with generating these stack traces is entirely eliminated. This optimization substantially reduces CPU cycles and memory consumption, thereby enhancing the performance of parsing operations and lessening the load on the Java Garbage Collector. This is particularly effective in scenarios where this internal `Error` is frequently created but its stack trace is not crucial for error handling or debugging purposes.
5.3.1.1 Locking / Caching
RFR-016584 Correction
Process: Lock request
Category: Exception
Problem: A lock request might cause a deadlock. If any involved requested lock is a job lock (as opposed to an application lock), an ArrayIndexOutOfBoundsException (“arraycopy: last source index 32 out of bounds for byte[16]” at com.cisag.sys.kernel.locking.CisLockTable$DeadlockResponder. handleEntry) occurs.
After 10 subsequent deadlocks, an “IllegalStateException: Queue full” (at CisLockTable.createDeadlockResponse) is thrown.
Correction result: No exceptions
5.3.2 ODBC
RFR-016585 Correction
Process: Initialization of virtual functions in ODBC
Category: Exception
Problem: If the Method getTablePath() in an implementation of pgm.base. CisODBCVirtualFunction returns an invalid LDT path (invalid namespace, LDT does not exist), a NullPointerException (at com.cisag.sys.dictionary.log.LogicalDatatypeLogic.load) will occur the first time all implementations are initialized. (This will be performed during various actions, e.g. installation of language refreshes.)
Correction result: The invalid implementation is skipped with a message SYS-6612 in the system log.
RFR-016584 Correction
Process: Initialization of virtual functions in ODBC
Category: Exception
Problem: If the Method getTablePath() in an implementation of pgm.base. CisODBCVirtualFunction returns an invalid LDT path (invalid namespace, LDT does not exist), a NullPointerException (at com.cisag.sys.dictionary.log.LogicalDatatypeLogic.load) will occur the first time all implementations are initialized. (This will be performed during various actions, e.g. installation of language refreshes.)
Correction result: The invalid implementation is skipped with a message SYS-6612 in the system log.
5.3.3 Searches
RFR-016584 Correction
Framework: n.a.
Application: All cockpits
View: n.a.
Action: n.a.
Adding an attribute of a releation based detailsearch.
Category: Exception
Problem: If the user adds an attribute of a releation based detailsearch to the cockpit, and an update deletes this attribut an exception occurs when the user starts the cockpit.
Correction result: The exception do not occur.
5.3.4 Software update
5.3.4.1 Import/install software updates
RFR-016584 Correction
Framework: Software Development
Process: Development task activation
Category: Ergonomics
Problem: Gitlab synchronization was not disabled on production servers
Correction result: Gitlab synchronization has been disabled on production servers
5.3.5 System – General
RFR-016584 Extension
Framework: SoftwareDevelopment
Application: Cockpit REST exports
View: n.a.
Action: Setting maximum number of exported rows
Field/Column: Max number of rows
Category: New field
Description: This new field allows users to set the maximum number of exported rows in the REST export dialog. What is more, there is a validation if the user has administrative capabilities to increase the initial number of exported rows.
RFR-016585 Correction
Process: Start of application server
Category: Exception
Problem: Booting an application server might yield an “OutOfMemoryException: Metaspace” due to insufficient metaspace memory, which is by CEE default limited to 256 MB by the JVM parameter -XX:MaxMetaspaceSize. This parameter is also included in the eclipse launch configuration files generated by the tool crtdvf.
Correction result: The parameter is omitted from the default JVM parameters during boot and from the launch files.
Data update: existing eclipse templates must be re-created
RFR-016585 Extension
Framework: SoftwareDevelopment
Application: Cockpit REST exports
View: n.a.
Action: Setting maximum number of exported rows
Field/Column: Max number of rows
Category: New field
Description: This new field allows users to set the maximum number of exported rows in the REST export dialog. What is more, there is a validation if the user has administrative capabilities to increase the initial number of exported rows.
RFR-016584 Correction
Process: Start of application server
Category: Exception
Problem: Booting an application server might yield an “OutOfMemoryException: Metaspace” due to insufficient metaspace memory, which is by CEE default limited to 256 MB by the JVM parameter -XX:MaxMetaspaceSize. This parameter is also included in the eclipse launch configuration files generated by the tool crtdvf.
Correction result: The parameter is omitted from the default JVM parameters during boot and from the launch files.
Data update: existing eclipse templates must be re-created
5.3.6 Workflow
5.3.6.1 Process editor
RFR-016584 Correction
Framework: Workflow
Application: ProcessDefinitions
View: Default
Action: n.a.
Category: Exception
Problem: When three nodes are hovered on top of each other, a NullPointerException occurs.
Correction result: Finitely many nodes can be hovered on top of each other.