| Release | Comarch ERP Enterprise 6.4 |
| Release date | 27.02.2026 |
| 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-016604 – RFR-016605
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-Fix16”.
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-Fix16
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix15 will be upgraded to CEE640PB-Fix16.
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
With the “Query data updates” application, you must schedule the following batch data updates, for any point in time.
UPDBUG030255
Items – update inherritance
This application will update organization depending item data. It will remove inherited purchase, sales, inventory and production data, that must not exist because the corresponding functions are not released in the application “Customizing”. Moreover, it checks for production- and planning data if inventory data exists for an item / organization combination. If not, production- and planning data will be also removed.
UPDSUP123733
Updating the usage status of delivered loading units
This update application will correct the usage status of delivered loading units to “Not bound to a process”.
UPDBUG030606
Item data: Correction of inheritance
This update application will search item data of the views inventory, production, planning, sales and purchasing, that is inherited from a faulty parent organization and will correct this data.
5 Contained changes and extensions
5.1 Application development
RFR-016605 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 CIS640PB-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 owerwritten in a customer project.
RFR-016605 Correction
Framework: General
Application: Items
View: Inventory, Production, Planning, Sales, Purchasing
Action: Accept data processing for the selected organization
Category: Invalid data / Unexpected behavior
Problem 1: In special cases the action “Accept data processing for the selected organization” didn’t update the maintaining organization of inherited item data, that should inherit from now the item data from the selected organization.
Correction result 1: From now the action “Accept data processing for the selected organization” will always update the maintaining organization of inherited item data as expected.
Data update: UPDBUG030606
Problem 2: Using the action “Accept data for the selected organizations and for their subordinate organizations” it was possible to inherit item data to organizations, that are not contained in the users organization context, … which means that he is not authorized to do it.
Correction result 2:
As expected from now the action “Accept data for the selected organizations and for their subordinate organizations” will skip inheriting data for organizations, that are not contained in the user’s organization context.
5.1.1 Base
5.1.1.1 Base – General
RFR-016605 Correction
Frameworks: Purchasing and Sales
Applications: “Simulate purchase prices” and “Simulate sales prices”
Action: Apply defaults
Category: Invalid data / Unexpected behavior / Ergonomics
Problem: If the customer (sales) or supplier (purchasing) changes and the price listing is the same as before the price listing should be cleared/refreshed so that the next inquiry will set the default value.
By mistake this does not work every time as expected.
Correction result: Now the behavior is as expected.
Hint: In addition to that the EAN functionality of the sales application for the item field is now also available within the purchasing application.
RFR-016605 Correction
Application: Document applications with “partner name”
Action: Maintain “partner name” data
Category: Invalid data / Unexpected behavior / Ergonomics
Problem: Because of some system engine errors blanks at the end of a “multi line text” value will not be removed if the default “multi line text” field is used within a customizable UI.
Especially for the “partner name” of the document applications this is a problem because such a name is a part of a so called “hash code business object” – here a different content results in a different hash code.
So some documents (e.g. “Shipping order” based on sales order line items) will split up the data because of the different content.
Correction result: Because the system engine cannot be corrected (compatibility reasons) the following changes were performed as workaround: 1. new class “com. cisag.app.general.gui.factories.PartnerNameEditorFactory” which is used for the data description of the logical datatype “com.cisag.app.general.PartnerName”.
2. com.cisag.app.general.order.gui. PartnerAddressDataNameField: new call of “rtrim” within the method “getValue”
5.1.1.2 Cockpits
RFR-016605 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.3 Contracts/RFQs/Quotations/Orders
RFR-016605 Correction
Application: Document applications
Action: Validate
Category: Unexpected behavior
Problem: Given a document item that uses a packaging unit whose type is not commercial. The relevant (most suitable) item unit is also not commercial. Previously, only quantities for the document line item whose packaging unit could be converted into the relevant item unit without rounding errors were permitted; this approach was suitable for commercial units, but not if both units were physical. Furthermore, the documents were not checked uniformly and some conversions were not as expected.
Correction result:
1.
Change to central check (QuantityValidation), which checks the leading (entered) quantity in relation to the most suitable item unit – currently used, for example, in quotations/orders: This check now only takes place if one of the two units is a commercial unit; in addition, the entered quantity must exactly be a packaging unit.
Hint:
– For compatibility reasons a known gap will not be closed: If the entered uom is not directly a packaging unit but a physical packaging unit with the same type exists the check will also not be performed (as before).
– There might be also some gaps if one document uses a commercial unit and the other document uses only physical units.
==> If needed you must restrict within a concrete project for a concrete document the units/amounts that are allowed to be used for a known item.
2.
Supplier invoices: The previous special check when posting a supplier invoice has been changed to QuantityValidation (see above 1.), so that the same conditions now apply here as in quotations and orders.
3.
Receipt of goods:
– Now also here the QuantityValidation (see above 1.) will be used at booking time, so that the same conditions now apply here as in quotations and orders.
– The order assignment dialog has been changed – now the order line item total quantity will be used if the best matching item quantity is equals to the calculated assignment quantity.
4.
Self billing: If the quantities in the item units of a supplier invoice order assignment are the same as the quantities of the receipt of goods order assignment, the leading quantity of the receipt of goods order assignment is also used for the supplier invoice order assignment.
Hint: This should be the normal case – however, in the “Self billing” logic exists an upper limit per order line item, which may take into account. If so, as before, the leading quantity (according to the total quantity of the order line item) is determined based on the most suitable item unit.
5.
Supplier invoice: Receipt assignment dialog: A similar problem as 4. occurs by the usage of the receipt assignment dialogs – now the behavior is as expected.
RFR-016605 Correction
Frameworks: Purchasing and Sales
Applications: “Purchase orders” and “Sales orders”
Action: Duplicate line item
Category: Unexpected behavior / Ergonomics
Problem: Since “CEE630PB-Fix19 KW45/2024” / “CEE640PB-Fix04 KW42/2024” a correction was delivered that prevents new kit components if the main detail is completed manually (“Canceled”, “Delivery manual completed” or “invoice manual completed”).
By mistake this change affects also main line items and sub line items with that are not a kit component (e.g. “Rebate in kind” sub line items).
Correction result: Now the “Duplicate veto” rule that belongs to “manually completed” will be considered – as needed – only for kit components.
RFR-016605 Correction
Framework: Sales
Applications: “Order confirmations query”, “Pro forma invoices query”, “Customer invoices query”
Actions: “Display” and “Print”
Category: Unexpected behavior
Problem: If some header discounts are present, they will be displayed and printed (in case of gross calculation) always even if no detail is using them.
Correction result: Now the header discount data will be displayed and printed only if at least one detail is using them.
In addition to that the applications “Order confirmations query” and “Pro forma invoices query” display now the type also for header discount rows (as already the “Customer invoices query” application).
5.1.1.4 Items
RFR-016605 Correction
Framework: Update
Application: UPDBUG030255
View: n. a.
Action: n.a.
Category: Invalid data / Unexpected behavior
Problem: The data update application removes the inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations. Unfortunately, it is perfectly acceptable to have item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.
Correction result: From now the data update application will not remove an existing inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.
Data update: Restoring inheritance after the data update would only be possible manually.
5.1.2 Inventory management
5.1.2.1 Delivery orders
RFR-016605 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Using checkbox “Blocked for invoicing”
Category: Ergonomics
Problem: Clicking the checkbox “Blocked for invoicing” did not update the status icon of the concerning detail lines in the list.
Correction result: From now, clicking the checkbox “Blocked for invoicing” will update the status icon of the concerning detail lines in the list.
RFR-016605 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: The complete action may display the error message GEN-6044 and the freight cost calculation may calculate no or wrong freight costs if the delivery order uses the base unit of measures instead of the system unit of measures for weights and volumes.
Correction result: From now, the complete action will always work as expected.
RFR-016605 Correction
Framework: Sales / Inventory
Application: Sales orders
View: n.a.
Action: Generate delivery orders with order reference and output delivery slips…
Category: Exception
Problem: An exception occurred creating a delivery slip from a sales order directly if a detail line with an identifier item was overdelivered by setting the dispo quantity higher than the open quantity.
Correction result: From now creating a delivery slip from a sales order directly will always work as expected.
RFR-016605 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: Completing the delivery is prohibited because the error message SHP-00201 is displayed. The reason is that delivery order is packed and contains detail lines with a pseudo item.
Correction result: From now the error message won’t be displayed any more, even if the delivery order is packed and contains detail lines with a pseudo item.
RFR-016605 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: n.a.
Category: Invalid data / Ergonomics
Problem: After picking is completed a delivery order that contains a detail line with an item of type “Serial number without inventory management” went always in “Changed”-Mode if the serial number was already assigned in the sales order. Furthermore, the detail line could not get packed in the packing dialog.
Correction result: From now the problem is fixed. Delivery orders that contain a detail line with an item of type “Serial number without inventory management” will always work as expected.
Data update: To correct the problem a delivery order, that is in “changed”-Mode, could simply be saved.
5.1.2.2 Inventory count
RFR-016605 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Import of new line items to be reported
Category: Exception / Unexpected behavior
Problem: If more than one hundred line-items were imported only the first block (100) of line items could be created and reported successfully.
Correction result: Independent of the number of line items the import of line item reportings can be imported as expected.
5.1.2.3 Inventory management – General
RFR-016605 Correction
Framework: Inventory
Application: Goods receipts
View: Packing dialog
Action: Pack
Category: Performance
Problem: The validation code for packing the goods receipt detail lines was called to often. So, it takes to much time packing large loading units with many receipt detail lines.
Correction result: From now the validation code is optimized and a goods receipt detail line will be validated only on time in a packing action.
RFR-016605 Correction
Framework: Inventory
Application: Goods receipts
View: Distribution
Action: Post goods receipt
Category: Exception
Problem: An exception occurred handling a scrap detail line in a goods receipt of a distribution return.
Correction result: From now posting a goods receipt of a distribution return will work as expected.
RFR-016605 Correction
Framework: Inventory Management
Application: Edit logisctic 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.
5.1.2.4 Inventory postings
RFR-016605 Correction
Framework: Inventory Management
Application: Recompile shadow inventories
View: n.a.
Action: Execute
Category: Invalid data
Problem: If there were not processed outgoing inventory postings their quantities could be wrong considered (addition instead of subtraction).
Correction result: Not processed inventory postings will be considered as expected.
RFR-016605 Correction
Framework: Inventory Management
Application: Loading units
View: n.a.
Action: Pack…
Category: Invalid data / Unexpected behavior
Problem: A loading unit could be packed within a storage location that does not supports storage units. To solve this erroneous situation the loading unit can be unpacked.
Correction result: The try to pack a loading unit within a storage location that does not supports storage units will be denied as expected.
RFR-016605 Correction
Framework: Inventory Management
Application: Edit inventory posting error automatically
View: n.a.
Action: Execute
Category: Exception
Problem: The context lock for reservation could be not successful if there are complete and not completely reserved inventory posting errors for the same context (item, warehouse).
Correction result: If it is possible to process inventory posting errors now it will be possible to save them to be processed as expected.
5.1.2.5 Loading units
RFR-016605 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Save and report a line item with automatic unpacking of a loading unit unpack proposal
Category: Unexpected behavior
Problem: Although the automatic unpack of a loading unit unpack proposal was selected the loading unit was not unpacked and because of that the report was not successful.
Correction result: If the automatic unpack of a loading unit unpack proposal is selected the loading unit will be unpacked as expected.
RFR-016605 Correction
Framework: General
Application: Import Data
Filter: com.cisag.app.shipping.obj.UnitLoad
Action: Import
Category: Unexpected behavior
Problem: The import process for creating loading units consumed a new number from the number range manager even if a number is already defined in the XML source file.
2. Moreover, after changing the organization in the organization selector the application “Loading units” may use the wrong number range for creating a new number.
Correction result: From now the import process for creating loading units will consume a number from the number range manager only then if no number is defined in the XML source file.
Framework: Inventory
Application: Loading units
View: n.a.
Action: Create
Category: Unexpected behavior
Problem: After changing the organization with the organization selector the application “Loading units” may use the wrong number range definition for getting a new number.
Correction result: From now the expected number range definition always will be used, even if the organization is changed.
RFR-016605 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Pack …
Category: Unexpected behavior
Problem: The action did not support the packing on storage location slots.
Correction result: From now, packing on storage location slots will be supported.
RFR-016605 Correction
Framework: Inventory Management
Application: Inventory requisition
View: Manual Stock Movement
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If the warehouse stock could be reserved but the inventory order could not be created (e.g. loading was locked or is in an inventory count at the moment) the generation of the inventory order would never be successful again.
Correction result: If the reason that avoids an inventory order generation is vanished, the inventory order can be generated as expected.
5.1.2.6 Loads
RFR-016605 Correction
Framework: Inventory
Application: Shipping loads
View: n.a.
Action: Send…
Category: Exception
Problem: The action could cause an exception if the data of the contained delivery orders has changed since the last display of the data in the application.
Correction result: From now the application will work as expected.
RFR-016605 Correction
Framework: Inventory
Application: Shipping loads
View: n.a.
Action: Delete / Delete detail line
Category: Invalid data
Problem: In delete processes the application updates the usage status of containing loading units to the invalid status “Issue of goods”. This status is invalid if the assigned delivery order is delivered already.
Correction result: From now, in delete processes the application will update the usage status of containing loading units to the status “Issue of goods” only if the status of the assigned delivery order is “Not delivered”. Otherwise, the usage status of the containing loading units will be set to “Not bound to a process”.
Data update: UPDSUP123733
5.1.2.7 Receipts of goods
RFR-016605 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Reuse loading unit …
Category: Unexpected behavior
Problem: The action is available when the usage status of the loading unit is ‘Receipt of goods’.
Correction result: From now the action will be available if the usage status is ‘Not bound to a process’ or ‘Distribution’ only.
5.1.3 Multi-site capability
5.1.3.1 Distribution orders
RFR-016605 Correction
Framework: Sales
Application: Distribution orders
Action: Reduce line-item editor size using split pane
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the “Sales orders” application the line-item editor height cannot be changed by the “split pane” functionality.
Correction result: Now the behavior is as expected.
5.1.4 Purchasing
5.1.4.1 Purchase order confirmations
RFR-016605 Correction
Framework: Purchasing
Applications: Purchase orders, Supplier confirmations
Action: Validate line item
Category: Unexpected behavior
Problem: A purchase order and purchase order correspondence were created. After that the item replacement status was changed (e.g. to the value “Expired if availability = 0”).
Up from that a supplier confirmation cannot be created that belongs to such a purchase order correspondence (e.g. error message “PUR, 1395”).
Correction result:
1. Purchase orders: – For new line items the “Item replacement status” will be checked now only if the line item is not canceled and the correspondence status is “Not ordered” and confirmation status is “Not confirmed”.
– For persistent line items that are changed from “Canceled” to “Not canceled” the “Item replacement status” will be checked now but only if the correspondence status is “Not ordered” and confirmation status is “Not confirmed”.
2. Supplier confirmations: The “Item replacement status” will be checked now only if the line item is not canceled and the item is different from the relevant purchase order correspondence line item.
5.1.4.2 Purchase orders
RFR-016605 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.5 Sales
5.1.5.1 Freight costs
RFR-016605 Correction
Framework: Sales
Application: Simulate freight costs
Action: Determine freight costs
Category: Unexpected behavior
Problem: In contrast to the document applications the “Simulate freight costs” application does not use the absolute data to determine the freight costs.
Correction result: Now the behavior is the same as within the document applications.
5.1.5.2 Sales fast entry vouchers
RFR-016605 Correction
Framework: Sales
Application: Sales fast entry vouchers transfer
Action: Execute
Category: Unexpected behavior
Problem: Within the “Sales fast entry voucher” base data you can specify if warnings should be confirmed automatically. The automatic transfer by the background application “Sales fast entry vouchers transfer” considers this property but has a mistake: If for any “Sales fast entry voucher” the functionality “Confirm warnings automatically” is activated also for all further Sales fast entry voucher” instances the warnings will be confirmed automatically – even if they have not activated this functionality.
Correction result: Now for every “Sales fast entry voucher” instance the specified “Confirm warnings automatically” value will be used.
In addition to that now a message log entry will be send for a “Sales fast entry voucher” instance if the status changes to the value “Error in automatic transfer”.
5.1.5.3 Sales orders
RFR-016605 Correction
Framework: Sales
Applications: Distribution orders, Sales orders
Category: Exception / Invalid data / Unexpected behavior
Problem: If an order line item contains a specified serial number (with or without inventory management) the total quantity can be only “one base unit”.
But it was possible to specify a “Allocated quantity” (“delivery order/picking order”, “delivery slip” or “cash invoice”) different from one.
As result an exception occurs during the delivery process.
Correction result: Now the “Allocated quantity” (“delivery order/picking order”, “delivery slip” and “cash invoice”) will be checked as expected.
Please note that you have to correct wrong data manually.
5.1.6 Storage Location Control
5.1.6.1 Inventory orders
RFR-016605 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: Generate inventory order…
Category: Unexpected behavior
Problem: If at least one line item is completely not reserved (outgoing process; fix reservation) the whole inventory order generation process would be aborted.
Correction result: The inventory order can be generated as expected. If fix reservation is active and there is a not reserved line item only this line item will be ignored.
5.1.6.2 Inventory requisitions
RFR-016605 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Import
Category: Unexpected behavior
Problem: The responsible employee could not be imported. The current user was already used.
Correction result: If a valid responsible employee is specified it will be imported as expected.
5.2 System development
5.2.1 GUI
RFR-016604 Correction
Framework: System management
Application: User Settings
View: “Diaplay” (Autostart)
Action: Drag & Drop
Field/Column: n.a.
Category: Ergonomics
Description: Drag & Drop support added for CDS design.
RFR-016604 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.