| Release | Comarch ERP Enterprise 6.5 |
| Release date | 20.02.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-016601 – RFR-016603
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-Fix04”.
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-Fix04
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE650PB-Fix03 will be upgraded to CEE650PB-Fix04.
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.
UPDADV122873A
Initialize buffer times for operations and operation templates.
Update undefined buffer times in com.cisag.app.production.obj.ProductionPlan for the following types: * ProductionPlanTypes.OPERATION * ProductionPlanTypes.OPERATION_TEMPLATE The default value assigned is 0 hours.
UPDBUG030483
Delete item ids of deletion marked business objects
This update application will delete (physically) all item id’s (com.cisag.app.general.obj.ItemId) that belongs to deletion marked business objects of type – com.cisag.app.sales.obj.CustomerSalesItem – com.cisag.app.sales.obj.CustomerClasificationItem. – com.cisag.app.purchasing.obj.SupplierPurchaseItem.
UPDADV122873B
Initialize buffer times for operation-type details in Routings
Set buffer times to 0 hours in com.cisag.app.production.obj.ProductionPlanDetail when they are undefined, provided that the header type is ProductionPlanTypes.ROUTING and the detail type is one of the following: * ProductionPlanDetailType.OPERATION * ProductionPlanDetailType.EXTERNAL_OPERATION * ProductionPlanDetailType.CROSS_SITE_OPERATION
UPDADV123657
Activates the production server customizing in case the production customizing is active.
UPDADV122873C
Initialize wait times for production order operation-type details
Update undefined wait times in com.cisag.app.production.obj.ProductionOrderResource for the following types: * ProductionOrderDetailType.OPERATION * ProductionOrderDetailType.EXTERNAL_OPERATION * ProductionOrderDetailType.CROSS_SITE_OPERATION The default value assigned is 0 hours.
UPDADV123026
Initialize reportedCisQuantities parameter of OperationDataCollection BO
Initialize “reportedCisQuantities” parameter of OperationDataCollection BOs, which have only old parameter “quantity” set. Old parameter value stores quantity as amount plus string of unit of measurement, when new parameter stores unit as guid to actual unit in system. Data update converts those old quantities into new ones via same conversion that was used to display reported quantity in Cockpit: Plant data collection postings. That calculated converted value is then stored in new parameter.
5 Contained changes and extensions
5.1 Application development
RFR-016603 Ergonomics
Update of the English user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016603 Correction
Class: com.cisag.app.general.log. SingleObjectEntityController
Method: com.cisag.app.general.log.SingleObjectEntityController.process(Source)
Description: The code is changed back to the version before CEE640PB-Fix10 with one modification: A new protected method “isOrganizationRequired()” is added. It checks if the primary key or the business key of the imported object contains an attribute with name “organizationalUnit”. If this method returns true, the method readOrganization(Source) must return a valid organization GUID. Both methods isOrganizationRequired() and readOrganization(Source) are protected and could be overwritten in a customer project.
5.1.1 Base
5.1.1.1 Cockpits
RFR-016603 Correction
Framework: General
Application: Cockpit: Employees
View: n.a
Action: Start application
Category: Unexpected behavior
Problem: The search pattern setting of the field “Organization responsible” was overwritten by the selected organization when the application is started from the menu with a former saved search pattern.
Correction result: As expected from now the presetting of the field “Organization responsible” will be taken from the search pattern when the application is started from the menu with a former saved search pattern.
Framework: General
Application: Cockpit: Partners
View: n.a
Action: Start application
Category: Unexpected behavior
Problem: The search pattern setting of the field “Organization” was overwritten by the selected organization when the application is started from the menu with a former saved search pattern.
Correction result: As expected from now the presetting of the field “Organization” will be taken from the search pattern when the application is started from the menu with a former saved search pattern.
Framework: Sales
Application: Cockpit: Customers
View: n.a
Action: Start application
Category: Unexpected behavior
Problem: The search pattern setting of the field “Sales organization” was overwritten by the selected organization when the application is started from the menu with a former saved search pattern.
Correction result: As expected from now the presetting of the field “Sales organization” will be taken from the search pattern when the application is started from the menu with a former saved search pattern.
Framework: Purchasing
Application: Cockpit: Suppliers
View: n.a
Action: Start application
Category: Unexpected behavior
Problem: The search pattern setting of the field “Purchasing organization” was overwritten by the selected organization when the application is started from the menu with a former saved search pattern.
Correction result: As expected from now the presetting of the field “Purchasing organization” will be taken from the search pattern when the application is started from the menu with a former saved search pattern.
Framework: Base
Application: Cockpit: Partners / Financials
View: n.a
Action: Start application
Category: Unexpected behavior
Problem: The search pattern setting of the field “Firm” was overwritten by the selected organization when the application is started from the menu with a former saved search pattern.
Correction result: As expected from now the presetting of the field “Firm” will be taken from the search pattern when the application is started from the menu with a former saved search pattern.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016603 Correction
Frameworks: Purchasing/Sales
Applications: Purchase orders, Sales orders
Action: Cancel line item
Category: Unexpected behavior
Problem: In contrast to the functionality “Delete cancellation” the “Cancel” functionality will not be considered as change from “previous” to “current” by the “DetailApplyDefaultsHook”.
Correction result: Now the “Cancel” functionality works as expected in analogy to the “Delete cancellation” functionality.
RFR-016603 Extension
Frameworks: Purchasing, Sales
Applications: Contracts, Sales fast entry vouchers, Proposals, Orders
1. Contracts: The line-item action “Determine price” has been extended by the new field “Net price dimension origin”.
2. Sales fast entry vouchers: The line-item action “Price origin” considers now the properties “Advanced price calculation” and “Net price dimension origin” of the target order document type.
3. Proposals, Orders: The line item action “Price origin” has been changed for kit main details and kit components:
– If the “Price determination” level is “Using kit items” the “Price origin” dialog for the components has been changed and shows now how the current “kit component detail” is calculated as part of the kit main detail.
Hint: For the “kit main detail” the normal “Price origin” dialog will be used.
– If the “Price determination” level is “Using components” the “Price origin” dialog for the kit main detail has been changed and shows now how the “kit main detail” is calculated.
Hint: For the “kit component detail” the normal “Price origin” dialog will be used.
RFR-016603 Extension
- Availability/reservation inventory APIs:
Class: com.cisag.app.inventory.reservation.log. FixedReservationAvailabilityMaintenanceLogic
New Methods: create(short, short, byte[], byte[], String),
load(short, short, byte[], byte[], String) and
DataEntry. Builder.detailNumber(int, int)Description: The availability/reservation data contains a “formattedOrderNumber” attribute – before this extension this String was determined automatically at save time by the availability/reservation APIs.
In many cases the client of the availability/reservation data APIs knows already the header and line item identifications that are used as base for the “formattedOrderNumber”.
To improve the performance and to ensure the usage of the correct data, the client can now specify the header number and detail numbers (main and sub number).
Furthermore – also to improve the performance – the detail numbers will now not be filled up any more with zero numbers as defined by the relevant number range.
The old API methods have been marked as “@deprecated”.2. availability/reservation order APIs:
a. Classes: com.cisag.app.general.order.log.EntityReservationLogic and com.cisag.app.general.order.log.ReservationLogic
new methods: create(H headerObj) and load(H headerObj)b. Class: com.cisag.app.general.order.log. ReservationChangeData
new method: “change” with “D detailObj”Description: For the “create” and “load” methods you have to specify now the “header object” instead of “order type”, “sub type guid” and “header guid”.
For the ReservationChangeData you have to specify now the “detail object” instead of “detail guid”.Hint: Please note that instead of the old four “change” method signatures only one signature with the full parameter set has been added.
The old API methods have been marked as “@deprecated”.
The new methods are using the new methods as introduced by 1..3. Clients of 2.: The purchasing requests, customer proposals and orders (distribution, purchasing and sales) have been changed so that they are using now the new methods as introduced by 2., instead of the methods that are now marked as “@deprecated”.
RFR-016603 Correction
New entry in com.cisag.app.general.OrderType:
Name of entry: SEM_FIN_POSTING_AAC
ID: 2043
Description (de): Buchungsbeleg Anlagenbuchhaltung
Description (en): Asset accounting posting voucher
5.1.1.3 Fiscal years
RFR-016603 Correction
Framework: Base
Application: Fiscal years
Actions: “Previous/Next status” (periods)
Category: Unexpected behavior / Ergonomics
Problem:
1. Manual changes of the period lines were discarded by executing the period change actions.
2. In case of period status changes that were performed “Online” the changed lines will be refreshed with respect to the new value but these lines changes also to the “edit” mode. So further status changes cannot be performed directly.
Correction result:
1. Before a period, status change can be performed it will be checked now if any changes of the period lines of the current tab are available. If so, a new error message will be sent for the relevant periods and the status change cannot be performed.
Hint: New check for status changes of some periods and change for the whole year.
2. After executing the status change the new value will be set into the relevant period lines (as before) and also the line will be set to “not changed”.
So – if needed – further status changes can be performed directly.
Hint: Please note that this correction changes only the behavior for the case that the status change will be performed directly (“Online”) – in case of executing the change by a background application the data needs to be refreshed manually before performing further changes.
5.1.1.4 Items
RFR-016603 Correction
Framework: General
Application: Items
View: n.a.
Action: Validate, …
Category: Exception
Problem: An item is marked as deleted. After loading it in the application “Items” an exception occurred if meanwhile in the background or in another session the reorganization for items was running and deleted the item or dependents of this item.
Correction result: From now some (not all cases) of theses exceptions will not occur any more. The code is corrected, where it is not incompatible.
Technical information: In the “Items” application and its entities it will not be possible to eliminate ALL lines of code, where these exceptions may occur, without doing a complete redesign of the application.
RFR-016603 Correction
Framework: General
Application: Items
View: n.a.
Action: New version
Category: Exception
Problem: An exception occurred creating a new version. This happened if the valid from date, the user inserted, is an increment value, that results in a date that is out of the range for a valid date.
Correction result: From now no exception will occur. A new version with the furthest future “valid from” date of the valid range of dates will be created
5.1.1.5 Partners
RFR-016603 Correction
Framework: General
Application: Import data
Filter: com.cisag.app.general.obj.Partner
Action: Import
Category: Exception
Problem: An exception occurred if a partner of type ‘Person’ is imported using a partner template for a partner of type ‘Organization’.
Correction result: From now, an error message will be displayed in that case instead.
5.1.2 Inventory management
RFR-016603 Extension
1.
Framework: Inventory
Application: Delivery slip types
View: n.a.
Action: n.a.
Field/Column: Ladeeinheiten in den Bestand übernehmen (EN: Accept loading units into inventory)
Category: New field
Description: Activate this field if you want to automatically accept loading units that are not put away into the inventory at delivery and when selecting the action “Post loading unit changes”. If this function is deactivated, then loading units that are not put away are not automatically accepted into the inventory. Instead, at delivery and when selecting the action “Post loading unit changes”, loading units that are put away are automatically unpackaged.
2.
Framework: Inventory
Application: Goods receipt types
View: n.a.
Action: n. a.
Field/Column: Ladeeinheiten in den Bestand übernehmen (EN: Accept loading units into inventory)
Category: New field
Description: In this field you select how loading units are posted in the receipt of goods process. The following values are available:
– Always, select “Always” to accept loading units into the inventory when posting receipts of goods.
– Only at unstructured warehouses, select “Only at unstructured warehouses” to accept loading units into the inventory when posting receipts of goods only at structured warehouses. At simple warehouses the items and identifiers that are contained within the loading units are accepted unpackaged into the inventory.
5.1.2.1 Availability check
RFR-016603 Correction
Framework: Inventory Management
Application: Reorganize availability and demand data
View: n.a.
Action: Execute
Category: Exception
Problem: An Exception could be thrown if the execution caused some error messages.
Correction result: The reorganization application can be executed as expected.
5.1.2.2 Availability query
RFR-016603 Correction
Framework: Customizing
Application: Customizing
View: n.a.
Action: “n.a.”
Field/Column: Verfügbarkeiten und Bedarfsdaten sofort löschen (german description)
Category: New field
Description: Customizing function: Warehouse inventory
There is a new customizing setting that allows users to delete availability and demand data as soon as they are no longer needed, instead of reorganizing them later.
5.1.2.3 Delivery order types
RFR-016603 Correction
Framework: Inventory
Application: Delivery slip types
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: The application outputs organization infos to the log-file because of unremoved code from a local test.
Correction result: The code, that outputs the data, is removed now. From now the application will not output any data to the log-file anymore.
5.1.2.4 Identifiers
RFR-016603 Extension
Framework: Inventory Management
Application: Ausprägungsnachweise reorganisieren (german description)
View: n.a.
Action: n.a.
Field/Column: n. a.
Category: New application
Description: New reorganization application to delete inventory identifier where-used-lists that were selected by the user.
5.1.2.5 Inventory count
RFR-016603 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Generate item based inventory count lists
Category: Unexpected behavior
Problem: If an item inventory was counted by a perpetual inventory count it would not be filtered although the consideration settings should filter it.
Correction result: If an item is already counted by a perpetual inventory count and the consideration settings should filter it this item inventory will be filtered as expected.
RFR-016603 Correction
Framework: Inventory Management
Application: Inventory count valuation
View: n.a.
Action: Post valuation change and close
Category: Ergonomics
Problem: If the new price was zero a warning would be displayed but without any item information.
Correction result: The displayed warning is extended with item and sometimes warehouse information as expected.
5.1.2.6 Inventory management – General
RFR-016603 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate inventory allocation…
Category: Unexpected behavior
Problem: If an item supported stock related packaging and there was inventory contained in loading units the inventory allocation calculation would not consider the loading unit content.
Correction result: The loading unit content will be considered as expected.
RFR-016603 Correction
Framework: Inventory Management
Application: Edit logistic units
View: n.a.
Activate design mode for the application
Category: Exception
Problem: If the design mode was activated, an exception was caused because of a missing method implementation.
Correction result: The design mode can be used now as expected.
RFR-016603 Correction
Framework: Inventory
Application: Export data
Filter: com.cisag.app.sales.obj.ShippingOrder, com.cisag.app.purchasing.obj.ReceiptOfGoods
Action: Export
Category: Unexpected behavior
Problem: Since CEE640PB-FIX12 the export does not support the relation “UnitLoads->Details->UnitLoadReferences” any more. Some of our customers need it. So, it must be provided again.
Correction result: From now on demand the relation
“UnitLoads -> Details -> UnitLoadReferences”
will be supported again. It could be activated in the BI processes by setting the following system properties of type Boolean to true.
– Export delivery order —> com.cisag.app.inventory.delivery.log. ShippingOrderExportControllerSupportUnitLoadReferences
– Export goods receipt —> com.cisag.app.inventory.receipt.log. ReceiptExportControllerSupportUnitLoadReferences
The default value of these system properties will be false (not set), which means, the relation “UnitLoads -> Details-> UnitLoadReferences” will not be supported in the listed processes.
5.1.2.7 Inventory postings
RFR-016603 Correction
Framework: Inventory Management
Application: Inventory posting
View: Manual
Save an inventory posting for initial loading
Category: Unexpected behavior
Problem: It is not allowed to save inventory posting to store an empty loading unit but it was also not possible to fill up a loading unit that was not stored.
Correction result: The first (initial) loading inventory postings will store the specified empty and currently not stored loading automatically.
Technical information: Those initial loading inventory postings and the first incoming inventory posting of a loading unit will support the inventory posting packing lists now.
Packing inventory postings already supported the inventory posting packing lists.
RFR-016603 Correction
Framework: Inventory Management
Application: Import data
View: n.a.
Import inventory postings
Category: Exception
Problem: If an inventory posting should be imported that had invalid data length (e.g. reference text) an exception could be caused.
Correction result: The data types will be validated as expected and invalid import data will be denied.
5.1.2.8 Loading units
RFR-016603 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: The field “Warehouse/zone/location” displayed the warehouse, zone and location only with overlay, … only then, if the warehouse management server has executed the posting.
Correction result: From now the field “Warehouse/zone/location” will display the warehouse, zone and location without overlay directly in the moment when the posting action is executed. Moreover, the field will display the slot (if a storage location is divided in slots).
RFR-016603 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.
RFR-016603 Correction
Framework: Inventory
Application: Cockpit: Loading unit history
View: n.a
Action: n.a.
Category: Unexpected behavior
Problem: Particularly the warehouse was not part of the achieved (displayed) data, even if a warehouse is part of the achieved process step.
Correction result: From now the warehouse will be achieved and displayed if a warehouse is part of the achieved process step.
5.1.2.9 Loads
RFR-016603 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual postings
Action: Validate
Category: Exception
Problem: If the loading unit status is delivered an exception could be caused.
Correction result: If the loading unit to be stored is delivered an error message is displayed as expected.
RFR-016603 Correction
Framework: Inventory
Application: Delivery orders, loading units
View: n.a.
Action: Generate, assign and display loading units…
Category: Invalid data / Unexpected behavior
Problem: It was possible to change the packaging of a delivery order that had already been loaded. Under certain circumstances, this meant that the displayed contents of the shipping load in the “Loading units” view no longer matched the actual contents of the shipping load according to the delivery.
Correction result: From now it will not be possible to change the packaging of a delivery order that had already been loaded. First the delivery order must be removed from the shipping load.
5.1.2.10 Reservations
RFR-016603 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Invalid data / Unexpected behavior
Problem: If an inventory requisition was created for direct withdrawal the generated inventory order could cause problems at the report step. There were only problems by using the combination of “picking point” strategies and partial withdrawals from loading units or inventory managed packaging.
Correction result: As before a single inventory order will be generated for the issue of goods. This direct picking inventory order does not used any picking points as expected.
RFR-016603 Correction
Framework: Customizing
Application: Function Reservation
View: n.a.
Reserve “Inventory that is available again”
Category: Unexpected behavior
Problem: The automatic reservation process to reserve “Inventory that is available again” is not applied for reservations with the reservation creation setting “Automatically with reservation term”.
Correction result: If the reservation point of time (reservation term) is already reached those demands will be reserved as expected.
RFR-016603 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Reserve warehouse stocks…
Category: Unexpected behavior
Problem: The dialog would not be shown if the line item and its demand data were created newly. The reason was an exception that was not displayed.
Correction result: The dialog can be opened now as expected and if an exception is caused it will be thrown as expected too.
RFR-016603 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Reserve (Reserve inventory quantities dialog)
Category: Ergonomics
Problem: If the reservation support was deactivated (e.g. for the warehouse) there was no information that the reserved quantities could only be decreased.
Correction result: A warning will be displayed when the reserved quantities should be changed and the item/warehouse context do not support reservations anymore.
5.1.2.11 Warehouses
RFR-016603 Correction
Framework: Inventory Management, Storage Location Control
Application: Picking orders (Generate inventory orders background application)
View: n.a.
Action: Generate inventory orders
Category: Unexpected behavior
Problem: If the “Generate inventory orders” dialog is used to create inventory orders the both actions “In background” and “Immediately” differed when error messages were created during the time delayed inventory order creation. The message batch job “Message log: Generate inventory orders” was not created when the “Generate inventory orders” batch job was created for background execution.
Correction result: The message batch job “Message log: Generate inventory orders” is also created for background execution of the batch application “Generate inventory orders” as expected. It will bind the error messages created during the inventor order creation in the inventory management server. The batch job behavior of “Generate inventory orders” stays unchanged and has its own independent states if it is started in background, too.
5.1.3 Multi-site capability
5.1.3.1 Distribution order types
RFR-016603 Correction
Framework: Sales
Application: Distribution request types, Distribution order types
Action: Create/Duplicate
Category: Exception
Problem: During the try to determine a number for the “code” attribute an exception occurs if “Multisite” is not enabled for the current organization.
Correction result: Now in this case no number will be determined (same behavior as for the case that the “number range” within the Customizing is empty).
5.1.4 Planning
RFR-016603 Extension
Framework: Planning
Application: Material requirements planning, Material requirements query, Cockpit: Planning conflicts
View: n.a.
Action: All planning actions
Column: Correction quantity
Category: New logic
Description: Correction quantity displayed for conflicts of type “Quantity of order/recommendation too high” and “Quantity of order/recommendation too small” now consider lot sizes.
RFR-016603 Correction
Framework: Purchasing
Application: Cockpit: purchasing recommendations, Edit purchasing recommendation
View: n.a.
Action: Generate purchase orders
Category: Unexpected behavior
Problem: When generating purchase order from purchase recommendations from production and purchase order type is not specified in window and in recommendations itself the error about content based authorization for null was displayed.
Correction result: Content based authorization now checks proper purchase order type for recommendations from production resulting in proper error if failed or generated order if succeed.
5.1.4.1 Generate purchasing recommendations
RFR-016603 Correction
Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: Save, Process, Release, Block
Category: Exception
Problem:
1. It was possible to set the same delivery and availability date for a single recommendation when a calendar year for those dates did not exist; the save operation completed successfully without any errors.
2. Setting different availability and delivery dates for a purchasing recommendation, when the calendar does not exist for at least one of the date years, caused an exception during saving or when changing the recommendation status. Despite the exception occurring, the status change actions also saved incorrect dates.
3. Recommendations with dates for which the corresponding calendar year does not exist were hidden, and a warning about the missing calendar year was always displayed. However, the user could not see the incorrect data and therefore could not correct it.
Correction result:
1. Validation now checks if a calendar year exists for the provided dates; if not, an error message is displayed.
2. Attempting to save a date for which the calendar does not exist will result in the same error as in case 1, and the recommendation is not saved or updated after a status change due to the validation error.
3. Recommendations with invalid dates are now also visible, and the validation displays messages for the wrong dates so the user can identify and correct them.
5.1.4.2 Material requirements query
RFR-016603 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 information: 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 message PRD-01078.
Correction result:
1. Old messages was replaced by new enhanced messages which provide price 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.5 Production
RFR-016603 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The value assistant for transport times and buffer times in the “Operations” and “Routings” applications was displaying seconds, minutes, hours and days as units of measure. In contrast, the value assistant for the same fields within the “Production orders” application only displays seconds, minutes, and hours, lacking the “days” unit.
Correction result: The value assistant for transport times and buffer times in the “Production orders” application has been updated to include “days” as a unit of measure. This change ensures consistency with the options available in the “Operations” and “Routings” applications.
RFR-016603 Extension
Framework: Production
Application: Cockpit: Production orders/work line items
View: Cockpit: Production orders/work line items
Action: n.a.
Field/Column: Quantity deviation line item
Category: New field
Description: A new column, “Quantity deviation line item”, has been added to “Cockpit: Production orders/work line items”. It corresponds to the column with the same name in “Cockpit: Production orders/material line items” and shows, as a percentage, the deviation between the total quantity and the actual quantity.
RFR-016603 Extension
Framework: Production
Application: Bill of materials / production orders / material requirements planning
View: n.a.
Action: Edit formula for line item
Category: New action
Description: Bill of material reserve factor assignments are used when formulas and conditions of line items in bill of materials check for “ProdPlan.Scrap”
RFR-016603 Correction
Framework: Production
Application: Cockpit: Equipment reservation
View: Cockpit: Equipment reservation
Action: Generate inventory requisition for provisioning
Category: Unexpected behavior
Problem: When using the “Generate inventory requisition for provisioning” action for an entry with “Assigned” status, the system incorrectly displays an error about the wrong requisition type usage. This prevents the inventory requisition from being created via this action at all.
Correction result: The generation process now finishes successfully, allowing the inventory requisition to be generation via this action.
RFR-016603 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Execute planning
Field/Column: State / last action
Category: New field
Description: In tab “status”, string tables for fields “status” and “last action” were updated to give information during / after reserve factor assignment transfer (or in case of an error).
5.1.5.1 Production – General
RFR-016603 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem:
1. The PRD-00485 message still appears in logs for blocked structures, but it displays vague and unhelpful details. It is also displayed regardless of the “Log untransferred line items” checkbox setting.
2. The APS-00125 message displays the type of the problematic detail, but it also shows the entire path from the header, which results in a misleading production plan header type.
Correction result:
1. All remaining PRD-00485 messages have been replaced with the APS-00125 message, which means there are now controlled by the “Log untransferred line items” checkbox.
2. The APS-00125 message has been improved to display both the production plan header type and the production plan detail type to improve readability.
5.1.6 Purchasing
5.1.6.1 Purchase orders
RFR-016603 Correction
Class: com.cisag.app.purchasing.pricing.log. Calculation
Method: completeCalculationResult(CalculationParams params, CalculationResult result)
Category: Invalid data
Problem: By mistake the following lines have been removed within a change of “CEE640PB-Fix06 KW02/2025”: …
result. setNetValueDomestic(toDomestic(result.getNetValue()));
result. setBonusRelevantValueDomestic(toDomestic(result.getBonusRelevantValue()));
result. setCashDiscountRelevantValueDomestic(toDomestic(result.getCashDiscountRelevantValue()));
result. setTaxRelevantValueDomestic(toDomestic(result.getTaxRelevantValue()));
…
As result these attributes were not calculated correctly any more.
Correction result: Now these lines have been added again.
Data update:
If needed you must recalculate manually the relevant purchasing proposals and orders.
5.1.6.2 Supplier invoices
RFR-016603 Correction
Framework: System Management
Application: Export data
Action: Export supplier invoices
Category: Exception
Problem: If a supplier invoice without levies is present and the attribute “levyDeliveryRecipientData” or the attribute “levyDeliverySupplierData” of the header or the details (line items) is used an exception occurs.
Hint: Please note that the same problem occurs during the supplier invoice reorganization if the export is used here.
Correction result: Now the exception does not occur any more.
5.1.7 Sales
5.1.7.1 Customer invoices
RFR-016603 Correction
Framework: Sales
Application: Customer invoices
Action: Cancel
Category: Invalid data / Unexpected behavior
Problem: The “Cancel” functionality redetermines the “exchange rate” attribute with respect to the current rate. Instead, the attribute must remain as copied from the “original invoice”.
Correction result: Now the “exchange rate” attribute will not be redetermined – so a “cancel invoice” contains as expected the copied value from the “original invoice”.
Hint: Please note that the attribute “exchange rate” is marked as deprecated with the following text: @deprecated Exchange rate from invoice currency to corporate currency.
DO NOT use for conversion, for information only!
RFR-016603 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 the invoices again
5.1.7.2 Pro forma invoices
RFR-016603 Correction
Framework: Sales
Application: Pro-forma invoices
Action: Create, determine tax code
Category: Invalid data / Unexpected behavior
Problem: In contrast to sales order confirmations and customer invoices the attribute “deliveryCustomer” of pro-forma invoice is not filled for line items that were mapped from an order detail (sales or distribution) – only the attribute “deliveryCustomerData” is filled.
Hint: For freight cost details the attribute “deliveryCustomer” is filled.
Because the tax code determination uses the “deliveryCustomer” attribute the determined tax code might be wrong/unexpected (depending on the tax code assignments).
Correction result: Now the “deliveryCustomer” is filled as expected also for details that were mapped from an order detail (sales or distribution).
RFR-016603 Correction
Framework: Sales
Application: Distribution orders
Action: Generate and output pro forma invoice
Category: Exception / Unexpected behavior
Problem: If the current distribution order has the type “Return of goods” and the order line item is based on an original order line item (with prices) the “Pro forma invoice generator” does not use – in contrast to the release 6.3 – the “gross price” as specified by the original order line item. Instead, the empty “gross price” of the return order line item will be used and because of the empty currency an exception occurs.
Correction result: Now – as in 6.3 – the “gross price” of the original order line item will be used so that the exception does not occur any more.
5.1.7.3 Sales fast entry vouchers
RFR-016603 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Price origin
Category: Unexpected behavior / Ergonomics
Problem: If the price is configured to be determined delayed and is not determined for a line item the try to execute the “Price origin” action sends an error message because of the missing price unit of measure.
Correction result: Now the new error message “SAL, 8998” will be send in this case and the dialog does not open.
This error message informs the user that the price must either be determined or specified manually.
RFR-016603 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Price origin
Category: Invalid data / Unexpected behavior
Problem: In contrast to the sales proposals and orders the dialog that belongs to the “Price origin” action uses also in case of a “retail calculation” document the “Gross price incl. taxes” instead of the “Gross price incl. taxes”.
Correction result: Now the correct value is used as expected.
5.1.7.4 Sales orders
RFR-016603 Correction
Framework: Sales
Applications: Customer proposals, Sales orders
Action: simulate (calculation)
Category: Unexpected behavior / Ergonomics
Problem: Given is a retail document with a kit in which the components are price-relevant. Such a price-relevant component is present in the line-item editor and a value relevant for the price calculation is changed (price, quantity, discount, etc.) – then, within the scope of the calculation simulation, the prices and amounts including taxes are refreshed, but not the prices and amounts excluding taxes. Prior to this correction, the refreshment only took place when the line-item data was applied to the entity data.
Correction result: Now also in this case the prices and amounts excluding taxes will be refreshed as expected.
RFR-016603 Correction
Framework: General
Application: Items
View: Customer Sales Item, Customer Classification Item, Supplier Purchase Item
Action: Mark/Unmark as deleted, Inheritance
Category: Unexpected behavior
Problem: Since CEE650PA KW20/2025 the item number inheritance of customer sales item data, customer classification item data and supplier purchase item data didn’t work as expected.
Correction result: From now the item number inheritance will work as expected. Furthermore, it will work as expected if customer sales item data, customer classification item data or supplier purchase item data is marked as deleted.
Data update: UPDBUG030483
5.1.8 Storage Location Control
5.1.8.1 Inventory management server
RFR-016603 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Add loading unit for withdrawal
Category: Exception
Problem: If a loading unit was added to an inventory order line item that was created for an item with identifier an exception could caused. The exception would only thrown if the inventory order was created for an real outgoing (inventory requisition).
Correction result: A loading unit can be added to an inventory order line item as expected and it will be reported correctly.
RFR-016603 Correction
Framework: Inventory Management
Application: Inventory Management servers (Background application)
View: n.a.
Inventory posting processing
Category: Unexpected behavior
Problem: When the inventory management server released data for other processes because dialog processes are preferred there should be no messages about a critical error in the message log.
Correction result: The inventory management server creates messages that it has released data to prefer other processes and some more describing error messages as expected. But there will not be any message about a critical situation at the inventory posting processing.
RFR-016603 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Add loading unit only for report
Category: Exception / Unexpected behavior
Problem: Item line item has not supported the action “Add loading unit” but it was offered and its usage could cause erroneous behavior.
Correction result: An error message will be displayed as expected when the action is used for a line item that belongs to serial numbers.
5.1.8.2 Inventory orders
RFR-016603 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Unexpected behavior
Problem: If the inventory order was created for a receipt of goods and the remaining quantities should be stored int the receiving zone the reporting would be denied.
Correction result: The receiving zone is also allowed to be used as zone for remaining serial numbers that could not be stored elsewhere. Because of that, they can be reported as expected.
RFR-016603 Correction
Framework: Inventory Management
Application: Cockpit: Storage locations
View: n.a.
Action: Generate replenishment inventory order
Category: Unexpected behavior
Problem: The setting “Ignore replenishment zone” to ignore the specified replenishment storage zone was considered erroneous.
Correction result: The setting “Ignore replenishment zone” will be considered as specified and as expected.
5.1.8.3 Storage location types
RFR-016603 Correction
Framework: Storage Location Control
Application: Storage location types
View: n.a.
Action: Validate
Category: Unexpected behavior
Problem: Picking location without storage unit didn’t validate correctly. The put purity restrictions for the process and the packaging were considered as mandatory.
Correction result: Picking locations without storage units can be validated and saved as expected.
5.2 External support
5.2.1 Programming
RFR-016603 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: n.a.
Category: Extension of the application
Description: From now the application supports the UI-Designer to customize the user interface (ident pane and editor only) for extension attributes. Moreover, it supports hooks to implement applying defaults and validations for the extension attributes.
5.3 System development
5.3.1 GUI
RFR-016601 Correction
Framework: All
Application: Cockpit applications
View: n.a.
Action: Scrolling
Category: Ergonomics
Problem: On scrolling (e.g. with the mouse wheel), sometimes the screen is not update (single scroll actions seem to be lost).
Correction result: Fixed.
RFR-016601 Correction
Framework: All
Application: Applications with customizable table
View: n.a.
Action: n.a.
Category: Exception
Problem: Changing the value of one column of a main row (using a value help, like “calculator”) and then changing the focus to a detail view of another main row (using the mouse), an exception can occur.
Correction result: Fixed.
RFR-016601 Correction
Framework: All
Application: All UI applications
View:n.a.
Action: Open value help
Category: Unexpected behavior
Problem: Since Chrome/Edge version 144, the open value help (fly-over) icon no longer works reliable.
Firefox is not affected.
Correction result: Fixed.
RFR-016601 Correction
Framework: All
Application: All
View: Messages (Text Pane)
Action: n.a.
Category: Unexpected behavior
Problem: The “TextPane” UI element which is mainly used for displaying messages, but also in some applications as well, had several issues regarding the display of “styled” text, the interpretation of “plain” vs. HTML text, and the correct determination of size requirements for its contents.
Correction result: Significantly improved.
RFR-016601 Correction
Framework: All
Application: Cockpit applications
View: n.a.
Action: n.a.
Category: Exception
Problem: An exception may occur if a cockpit uses deeply nested groups with group totals and horizonal scrolling enabled — and the user is clicking on one of the rows with the totals.
Correction result: Fixed.
RFR-016601 Correction
Framework: System management
Application: User Settings
View: “Display” (Autostart)
Action: Drag & Drop
Field/Column: n.a.
Category: Ergonomics
Description: Drag & Drop support added for CDS design
5.3.2 Kernel
RFR-016601 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a
Description: Internal performance optimizations regarding the system script parser.
Technical information:
Optimization in com.cisag.sys.kernel.parser.Parser: The internal exception LookaheadSuccess is used for flow control. Since creating exceptions is expensive (even if no stacktrace is created), a static instance is now used to improve performance.