| Release | Comarch ERP Enterprise 6.4 |
| Release date | 24.04.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-016612 – RFR-016614
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-Fix17”.
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-Fix17
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix16 will be upgraded to CEE640PB-Fix17.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016614 Documentation
What’s this help for the “Applicable voucher” (“Verwendender Beleg”) field has been added.
RFR-016614 Correction
Framework: Inventory
Application: Inventory allocation
View: n.a.
Action: n.a.
Category: New parameters
Description: From now the parameters are declared in the repository development object for this application.
Framework: Inventory
Application: Generation of delivery order
View: n.a.
Action: n.a.
Category: New parameters
Description: From now the parameters are declared in the repository development object for this application.
Framework: Purchasing
Application: Purchase order generation
View: n.a.
Action: n.a.
Category: New parameters
Description: From now the parameters are declared in the repository development object for this application.
5.1.1 Base
5.1.1.1 Base – General
RFR-016614 Correction
Class: com.cisag.app.general.log. MutableArrayDependentData
Method: copy constructor
Category: Invalid data / Unexpected behavior
Problem: By mistake the “copy constructor” did not work in all cases as expected. So, it could occur that the newly created instance contains empty data instead a copy of the specified data.
Correction result: Now the “copy constructor” works as expected.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016614 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 perform (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 have to 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.
5.1.1.3 Fiscal years
RFR-016614 Correction
Framework: Inventory
Application: Goods receipts
View: Customer return
Action: Generate sales order from goods return and post receipt of goods
Category: Invalid data
Problem: It was possible to complete a goods receipt (i.e. with the action ‘Generate sales order from goods return and post receipt of goods’) allthough no open fiscal period could be found for the receipts document date. That could happen if the goods receipt contains no detail line that requires an inventory transaction (i.e. empties receipt detail lines only).
Correction result: From now it will be checked if an open fiscal period can be found for the receipts document date. If not, the goods receipt won’t be allowed to get completed.
5.1.2 Calculation
RFR-016614 Correction
Framework: Calculation
Application: Cockpit: Production items
View: n.a.
Action: “Generate calculations…”
Category: Exception
Problem:
1. In an environment where Customizing -> Production -> Method is not active Cockpit: Production items is opened, items are selected and action “Generate calculation…” is performed.
Result: an exception occurs.
2. Same preliminaries as in a). Cockpit: Production items can be opened from menu “Calculations” as well as from menu “Production”.
Opening from menu “Calculation” action “Generate calculation” should be supported, opening from menu “Production” this action should not be not supported. This is not the case. It is vice versa.
Correction result:
1. In an environment where Customizing -> Production -> Method is not active Cockpit: Production items is opened, items are selected and action “Generate calculation..” is performed.
Result: no exception occurs, calculation is generated as expected.
2. Opening from menu “Calculation” action “Generate calculation” is supported, opening from menu “Production” this action is not supported.
RFR-016614 Correction
Framework: Calculation
Application: Trade cost calculations
View: n.a.
Action: New
Category: Unexpected behavior
Problem: When a user loads a ‘Trade cost calculation purchasing items’, changes its type to ‘Trade cost calculation sales items’, and then clicks the ‘New’ button, the application incorrectly displays a confirmation window about losing unsaved changes, even though no modifications were made.
Correction result: Now after performing the same actions, a new empty object is opened without the unnecessary confirmation window.
RFR-016614 Correction
Framework: Costing
Application: Product cost calculations / Trade cost calculations
View: n.a.
Action: Calculate
Category: Ergonomics
Problem: Locking mechanisms in product/trade cost calculation where were not optimally implemented.
Correction result: Locking mechanisms are now more performant.
RFR-016614 Correction
Framework: Costing
Application: Export data
View: n. a.
Action: Export instances of time-dependent BO ValuationPriceHistory.
Category: Unexpected behavior
Problem: Exporting instances of ValuationPriceHistory didn’t yield data of different versions (e.g. prices). Instead, only data of the currently active version was exported multiple times.
Correction result: All versions are exported.
5.1.2.1 Calculation types
RFR-016614 Correction
Framework: Calculation
Application: Product cost calculations, Calculation types
View: Product cost calculations: Selection of a product cost calculation category; Calculation types: Field Product cost calculation category
Action: n.a.
Category: Ergonomics
Problem: Dealing with allowed product cost calculation category in the context of applications Product cost calculations and Calculation types technically is implemented in two different ways which possibly is a source of deviating behavior of usage of product cost calculation category.
Correction result: Technical implementation has been unified. Current behavior was not changed, no additional functionality has been added.
Right now there is only one value of product cost calculation category which depends on context: Preliminary calculation with service item
Application Calculation types: Preliminary calculation with service item is available to be selected if at least for one site multi-site production is activated (Customizing -> production -> external Production -> checkbox “multi-site production)
Application Product cost calculations: Preliminary calculation with service item is available to be selected if the specified organization allows multi-site production.
5.1.3 Document Management
5.1.3.1 Document cockpit
RFR-016614 Correction
Framework: Document Management
Application: Cockpit: Documents
View: n.a.
Action: Load
Category: Ergonomics
Problem: Loading data to Cockpit: Documents takes very long time in case there are lots of documents.
Correction result: Performance of the cockpit has been improved.
5.1.4 Inventory management
5.1.4.1 Availability query
RFR-016614 Correction
Framework: Inventory Management
Application: Availability queries
View: Origin
Availability calculation using “Remaining shelf life” (Customizing, Sales Item)
Category: Unexpected behavior
Problem: Batches: If the remaining shelf time is set within the customizing or sales item it should be considered and calculated based on the first expired point of time but it was calculated using the last available date before it is expired (MHD = German description/meaning) .
Correction result: The “Remaining shelf life” is considered as expected. The changed calculation should be checked and if it is needed, please increase the “Remaining shelf life” time by one day within the customizing or sales item settings.
5.1.4.2 Delivery orders
RFR-016614 Correction
Framework: Inventory
Application: Delivery orders
Test case: Delivery order for distribution
Action: Cancel
Category: Exception
Problem: An exception occurred cancelling a delivery order for distribution if the assigned goods receipt is reorganized already.
Correction result: From now an error message will be displayed in this case. The cancelling will be prohibited.
RFR-016614 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Exception
Problem: An exception occurred completing a delivery order, former reported by a transport order proposing the concrete stock, … and without using a picking order.
Correction result: From now completing a delivery order will work as expected in that case.
5.1.4.3 Identifiers
RFR-016614 Correction
Framework: Inventory Management
Application: Receipt of goods
View: Purchasing
Generate identifiers automatically
Category: Exception
Problem: If a number range is specified that uses production data as parameter and the receipt is for a purchasing process the identifier generation would be aborted with a NullPointerException within the system infrastructure.
Correction result: For this erroneous case a message (= message exception) is thrown and the identifier generation will be aborted as expected.
5.1.4.4 Inventory count
RFR-016614 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Create item-based inventory count lists…
Category: Exception
Problem: The field “Inventory check setting” could be empty although the field “Include inventory” was not set to “Empty count list”. This error is only caused by changing the value in the field “Inventory check setting”.
Correction result: If the value of the field “Inventory check setting” is mandatory it will be set as expected.
RFR-016614 Correction
Framework: Inventory management
Application: Inventory count
View: n.a.
Action: Create item dependent count lists…
Category: Unexpected behavior
Problem: if an item classification was selected and the stock consideration field was changed, the generated selection string would be added every time the consideration field was changed.
Correction result: The selected classification values stay in the classification fields until they are changed.
RFR-016614 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Import of inventory count reports
Category: Unexpected behavior
Problem: Performance: At import process the inventory count list data were loaded too often.
Correction result: The inventory count list data will be loaded once per import process and again after the update of every imported block (100) of reportd as expected.
5.1.4.5 Inventory postings
RFR-016614 Correction
Framework: Inventory Management
Application: Inventory postings
View: Posting error log
Action: Post
Category: Exception
Problem: If the posting error log was opened but the inventory error postings were already processed by the background application an exception could be caused.
Correction result: The application is able to consider already processed inventory posting errors as expected.
5.1.4.6 Loading unit templates
RFR-016614 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Validate / update
Category: Invalid data / Unexpected behavior
Problem: It was possible to store an amount not equals to zero as a parallel unit of measure for a loading unit detail line of an item, that has no parallel units of measure defined.
Correction result: From now it will not be possible to do that.
5.1.4.7 Loading units
RFR-016614 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Generate unit load dependent count lists for equipment
Category: Unexpected behavior
Problem: Some processes support loading units that contain equipment and tools but not all. Especially the inventory count could not count those loading units.
Correction result: – loading units with equipment are now permitted, and all processes shall be supported in accordance with existing loading unit functionalities (Inventory requisition, Inventory orders, Storage location/transport reservations, Receipt of goods, Physical Inventory, etc.).
– Storage locations now also support loading units that include equipment.
– Restriction: Storage locations remain restricted by material type (regardless of the loading units). This means that loading units containing mixed material types are currently only supported in simple storage zones with the material type setting “All” or in simple warehouses.
5.1.4.8 Picking orders
RFR-016614 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Import of inventory order reports with loading units
Category: Unexpected behavior
Problem: If the order line item contained an unpacking proposal (=>unpack of a loading unit at the source side) the unpack automatically marker would not be correctly used. Because of that the loading unit was not unpacked automatically.
Correction result: The import of loading unit reports supports the automatic unpack and unloading processes at source and target side of an inventory order as expected.
RFR-016614 Correction
Framework: Inventory
Application: Delivery orders, Cockpit: Delivery orders
View: n.a.
Action: Generate and output picking orders…
Category: Exception
Problem: An exception occurred creating a picking order for delivery orders being packed in more than one layer, which means a delivery order that is packed in a loading unit that itself is packed in another loading unit.
Correction result: From now creating a picking order for delivery orders being packed in more than one layer will work as expected.
5.1.4.9 Receipts of goods
RFR-016614 Correction
Framework: Inventory
Application: Goods receipts, delivery orders
View: n.a.
Action: Generate, assign and display loading units…
Category: Exception
Problem: An exception occurred if the packing was executed with an invalid storage unit.
Correction result: From now the validation process will work as expected.
5.1.5 Multi-site capability
5.1.5.1 Distribution orders
RFR-016614 Correction
Framework: Sales
Application: Distribution orders
Action: Reorganize
Category: Exception / Invalid data / Unexpected behavior
Problem: Before this correction it was possible to reorganize a completed “Distribution order” although an open (not booked) supplier invoice exists.
After the “Distribution order” reorganization such a supplier invoice cannot be booked any more.
Correction result: Now an error message will be send that prevents from the “Distribution order” reorganization in this case.
5.1.5.2 Inter-company billing
RFR-016614 Correction
Frameworks: Purchasing / Sales
Action: Internal billing
Category: Invalid data / Unexpected behavior
Problem: If a supplier invoice line item is based on a return distribution order line item the “Destination cost center” and the “Destination cost units” of the relevant original order line item are not used for the supplier invoice line item.
Correction result: Now the data is used as expected.
5.1.6 Planning
RFR-016614 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Enter organizations in field “Sites” & update
Category: Unexpected behavior
Problem: Entering more than 255 characters in field “Sites” led to a fatal error during planning.
Correction result: Field “Sites” now validates the input length, more than 255 characters are denied.
RFR-016614 Correction
Framework: Purchasing
Application: Calculate distribution recommendations
View: n.a.
Action: Calculate recommendations
Category: Unexpected behavior
Problem: When planning with delivery calendars, the “Delivery calendar classification” configured in the item’s planning view at section “Purchasing (external)” was used for distribution recommendations.
Correction result: When planning with delivery calendars, the “Delivery calendar classification” configured in the item’s planning view at section “Purchasing (internal)” is used for distribution recommendations.
RFR-016614 Correction
Framework: Planning
Application: Material requirements planning, Cockpit: Planning conflicts
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem: When an item’s “Lot size method” is set to “Exact lot size”, the planning run may generate a “Quantity of order/recommendation too small” conflict for an order that falls before the planning start date. In this case, the suggested correction quantity is incorrectly too large. For the same order placed within the planning horizon, the planning server generates the same conflict but with a correct, smaller correction quantity.
Correction result: The correction quantity calculated for orders before the planning start date is now aligned with the correction quantity calculated for orders within the planning horizon, and the suggested value is now correct.
RFR-016614 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all actions that execute planning
Category: New feature
Description: Add system property com.cisag.app.aps.SuppressMessage to suppress specific messages from being written to logs during planning.
RFR-016614 Correction
Framework: Production
Application: Production recommendations / Distribution recommendations
View: n.a.
Action: Generate production orders / generate distribution orders
Category: Unexpected behavior
Problem: In application “Distribution recommendations”, it was possible to enter 0 quantity for recommendations in the list. When using acting “Generate distribution order” this led to an error.
In application “Production recommendations”, it was possible to enter a negative priority.
Correction result: It is not possible anymore to enter a quantity of 0 in “Distribution recommendations” nor a negative priority in “Production recommendations” as validation for both cases has been added.
5.1.7 Production
RFR-016614 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-016614 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release
Category: Exception
Problem: Multi-level dispatching for a production order fails when its production item’s bill of material contains an equipment item with the “Item resolution in multi-level dispatching” setting enabled in item production view. The process throws an exception because the system incorrectly attempts to create a sub-order for the equipment detail.
Correction result: Sub-orders are no longer generated for equipment details. This ensures that the dispatch process finishes successfully under the same conditions.
RFR-016614 Correction
Framework: Production
Application: Bills of material
View: Bill of material
Action: Validate, Save
Category: Unexpected behavior
Problem: When bill of material contains line item which is replaced and action Save or Validate will be performed this details is not validated at all, which allows to save invalid data e.g. quantity with decimal number.
Correction result: Now replaced detail is also validated which makes saving invalid data impossible.
RFR-016614 Extension
Framework: Production
Application: Production order types, Production order
View: n.a.
Action: Generate service distribution order or update price
Field/Column: Calculation type
Category: Extension of field
Description: Field “calculation type” in production order type configurated for Multi-site production is not mandatory anymore.
In case that field is empty, then during performing action “Generate service distribution order or update price” price for service item is calculated/loaded from price list instead. If price cannot be determined via price list too then 0 is set as default price.
RFR-016614 Correction
Framework: Production
Application: Material requirements query
View: n.a.
Action: Open tab “demands”
Category: Unexpected behaviour
Problem: Translations for fields “Unit of measure” “Total” and “Previous period” are not adapted to user-language if it has been changed.
Correction result: Translations for fields “Unit of measure” “Total” and “Previous period” are adapted to user-language of it has been changed.
RFR-016614 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: Prerequisite: A production item has set production method “Bill of material and routing”, and this bill of material only contains a sub-bill of material, which in turn contains some material line items, and the routing contains an external operation.
When a Production order with this production item was scheduled, the material of the sub-bill of material was then converted to “material provided”, which was unexpected.
Correction result: After scheduling a production order with the prerequisite above, the material of the sub-bill of material is not automatically turned into “material provided”.
RFR-016614 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: When dispatching a production order for a production item that has only bill of material as production method set in item view “Production” and a lead time set in item view “Disposition”, the schedulingBaseDate was not calculated as expected.
Correction result: The scheduling base date is now calculated as expected, i.e. earliest begin time + lead time.
RFR-016614 Extension
Framework: Production
Application: Bills of material, Routing, Bills of resources
View: n.a.
Action: Validate
Field: Site, Inventory management organization
Category: New validation
Description:
1. When changing the site of a Bill of Material (BOM), Routing, or Bill of Resources, a new validation checks if the linked production plan is used in a production item belonging to a non-matching organization. If a mismatch is found, a warning is displayed.
2. Changing a BOM’s site automatically updates the sites of all its parent BOMs. A new validation has been added to prevent data corruption by checking if this site change is valid for the parent BOMs. If the site change is valid, the system also performs the production item usage validation (described in point 1) on the updated parent BOMs.
RFR-016614 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Recalculate due date and quantity…
Category: Unexpected behavior
Problem: A production order uses a cross-site operation. The cross-site operation has some formulas defined for variable and setup time using allowed variables.
Dispatching calculates proper variable and setup time for cross site operation, but rescheduling production order results in wrong calculated variable and setup time.
Correction result: In above-described context variable time and setup time of a cross-site operation are calculated properly on rescheduling production order.
RFR-016614 Extension
Framework: Base
Application: Items
View: Production
Action: Validate
Field/Column: Bill of material, Routing, Bill of resources, Alternate methods
Category: New validation
Description: Routings and Bills of Resources are site-specific production plans. A Bill of Material can be either site-neutral or site-specific, which is determined by whether a warehouse is specified for any of its line items. Previously, there was no validation to ensure that a production plan with the correct site was set in the “Production method” tab and the “Alternate method” table of the Production Item view. This led to situations where users would not receive any error messages during the configuration of a production item. However, the configured item could not be dispatched in a production order or be properly planned by the Material Requirements Planning application.
A new validation has been introduced to address this. It checks whether the site entered for the production plan is the same as the production item’s site, or one of its child organizations. In case of a mismatch, a warning is displayed, informing the user about the incorrect configuration.
Additionally, if a Bill of Material becomes site-specific and is already in use by a production item with a non-matching organization, a new warning will now be displayed.
RFR-016614 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-016614 Correction
Framework: Production
Application: External manufacturing operation postings
View: n.a.
Action: Ship to external manufacturer…
Category: Unexpected behavior
Problem: In the course of generating a shipping order for an external operation the warning PRD-2619 occurs if “Order shipping quantity” exceeds quantity “Ready for shipping”. This warning is output after dialog “Shipping to external manufacturer” has been confirmed. The warning cannot be confirmed and thus process “Shipping to external manufacturer” is not performed.
Correction result: If “Order shipping quantity” exceeds quantity “Ready for shipping” the warning is output before dialog “Shipping to external manufacturer” is shown. If the warning is confirmed and action “Shipping to external manufacturer” is executed once more a shipping order is properly generated.
5.1.7.1 External manufacturing operation postings
RFR-016614 Correction
Framework: Production
Application: External manufacturing operation postings
View: n.a.
Action: n.a.
5.1.7.2 Production – General
RFR-016614 Correction
Framework: Production
Application: Cockpit: Production orders
View: Availability with material line items
Action: Specify available columns -> Material…
Category: Unexpected behavior
Problem: When adding the “replenishmentLeadTime” field (“reorderTime” from BO “Item planning data”) to the Material search via design mode, the system incorrectly displayed the planning data of the main production item for the entire production order, rather than the data for the specific material. Additionally, if the organization maintaining the planning for the production item differed from the organization for the material item, the field remained empty.
Correction result: The field now correctly shows the material’s planning data. It is also not affected by production item maintaining planning organization anymore.
RFR-016614 Extension
Framework: Production
Application: Cockpit: Plant data collection postings, Reorganize plant data collection postings
View: n.a.
Action: Delete, Reorganize
Category: New action, New application
Description: Add the delete action to the cool bar of Cockpit: Plant data collection postings. This enables users to delete Plant data collection posting entries. Additionally, add new reorganization application Reorganize plant data collection postings. This allows the automatic deletion of completed postings above a certain age.
RFR-016614 Extension
Framework: Production
Application: Bill of materials, Routings, Operations, Product configuration rules, Order maintenance
View: Dialog “Edit conditions with substitute and formulas”, “Product configuration rules” -> view “Conditions and actions”
Action: n. a.
Category: New action
Description: For above mentioned applications formulas and conditions are extended. Expressions can be defined using a wide range of operations on character strings.
Operations are: „substring“, „contains“, „starts_with“, „ends_with“, „last_index_of“, „index_of“, „length“, „replace“
Detailed information the help document will provide.
RFR-016614 Correction
Framework: Calculation
Application: Product cost calculations, Trade cost calculations
View: n.a.
Action: Exit
Category: Unexpected behavior
Problem: Changes have been made in applications Product cost calculations and Trade cost calculations. On exiting these applications without saving no notification about changed data appears via “Close application” dialog.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is not locked. Another user thus can load, change and save the same product/trade cost calculation.
Correction result: Applications Product cost calculations and Trade cost calculations display “Close applications” dialog if data have been changed. Thus user can decide to stop closing application or to close application without saving.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is locked. Another user can load, change but not saving due to a proper information about locked data.
RFR-016614 Correction
Framework: Production
Application: Scrap postings
View: n.a.
Action: Post
Category: Unexpected behavior
Problem: Implementation of validation was faulty.
Correction result: Validation is now correct in any case.
5.1.7.3 Production orders
RFR-016614 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Edit condition with substitute or formula of selected line item
Category: Exception
Problem:
1. When cross-site operation has formula of type “Buffer time before” or “Buffer time afterward” in production order, opening that formula via button in detail list caused exception.
2. The operation type details within a production order incorrectly displayed formula types as “Processing time” and “Setup time.” These formulas actually affected the operation’s quantity, not its duration as their names suggested.
Correction result:
1. The “Buffer time before” and “Buffer time afterward” formulas now open correctly from the production order details for cross-site operations and can be properly modified, regardless of how they were created or which button is used.
2. The formula type descriptions have been corrected. The production order’s operation details now accurately display quantity-based formula types, clarifying their true impact.
RFR-016614 Correction
Framework: Production
Application: Operations, Order maintenance
View: Operations -> Dialog: Edit conditions with substitute and formulas
Action: Dialog: Edit conditions with substitute and formulas -> Accept, Accept current line-item; Order maintenance -> Dispatch
Category: Unexpected behavior
Problem:
1.
It is possible to define formulas for an external operation / cross site operation like: Processing time = Order.PRODQTY*Resource. VARTIME*Resource.SCRAP. This leads to an error on dispatching as variable Resource.VARTIME as well as Resource.SCRAP is not defined within scheduling context, that is: there are no values assigned to parameters Resource.VARTIME and Resource.SCRAP. Error message PRD-1094 is displayed.
This has two different reasons: (a) Resource.VARTIME: A proper value can be retrieved on scheduling but it is not supported right now
(b) Resource.SCRAP: A proper value cannot be retrieved as external operations / cross site operations do not support such a value
add a)
The following parameter values are supported within context external operations / cross site operations, but retrieving is no supported up to now: Processing time: Resource.VARTIME,
Setup time: Resource.FIXTIME
add b)
The following parameter values are not supported within context external operations / cross site operations: Performance grade: “RESOURCE.PERF”
Rejects: “RESOURCE.SCRAP”
Resource group: “RESOURCE.GROUP”,
Number of resources: “RESOURCE.NUMBER_OF_RESOURCES”
2.
It is possible to define for a resource detail of a normal operation e.g. Resource.VARTIME*Resource.SCRAP. But parameter Resource.SCRAP (-> “Rejects”) is not supported for resources, only Resource.PERF(-> “Performance grade”).
A formula using Resource.SCRAP will provide a value of 0 as value of this parameter is always 0.
3.
If a formula/condition/substitution/alternative is added or is changed in dialog application “Operations” does not show “Edited” sign when dialog is closed witch action “Accept”. “Edited” is shown after action “Validate” or if application “Operations” is closed without saving.
4.
If to a production order manually a external operation is added with assigned formula for setup time and/or processing time the result of this formulas do not affect setup time / processing time of production order detail for this external operation.
5.
Production order with external operation using formula/condition based on Resource.VARTIME and/or Resource.FIXTIME is rescheduled. Error message PRD-1094 is displayed as both values are are not provided in a rescheduling context.
6.
Issues (1), (3), (4) and (5) go also for cross site operations.
Correction result:
1.a) Values of parameters Resource.FIXTIME and Resource. VARTIME are retrieved properly for external operations or cross site operations. Formulas using this parameters and other valid parameters within context external operation or cross site operation are calculated as expected.
1.b) If parameters listed in “add 1b” are used in dialog “Edit conditions with substitute and formulas” in context “external operation” or “cross site operation” usage will be rejected due to an error message (PRD-00437).
2.
If parameter Resource.SCRAP is used in dialog “Edit conditions with substitute and formulas” in context “resource” usage will be rejected due to an error message (PRD-00437).
3.
If a formula/condition/substitution/alternative is added or is changed in dialog application “Operations” does show “Edited” sign.
4.
If to a production order manually a external operation is added with assigned formula for setup time and/or processing time the result of this formulas does affect setup time / processing time of production order detail for this external operation due to proper calculation.
This is also valid for manually adding cross site operations.
5.
Production order with external operation using formula/condition based on Resource.VARTIME and/or Resource.FIXTIME is rescheduled. The values are provided and lead to calculations as expected.
6.
Issues (1), (3), (4) and (5) go also for cross site operations.
RFR-016614 Correction
Framework: Production
Application: Cockpit: Production orders/material line items
View: n.a.
Action: Export objects according to search criteria
Category: Exception
Problem: When trying to export object from “Cockpit: Production orders/material line items” in batch, the exception occurred.
Correction result: There is no exception during export anymore resulting with successful export in batch.
5.1.7.4 Production plans
RFR-016614 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer/Update planning data and execute planning
Category: Unexpected behavior
Problem: A product P uses a bill of resource BOR_Z which itself uses a bill of material BOM_Z. A line item of bill of material BOM_Z is another (phantom) bill of material BOM_X. If product p is planned ending up with some recommendation the calculated secondary demands of material belonging to phantom bill of material BOM_X are wrong. Reasons is that the ratio between reference factor of BOM_Z and quantity of line item BOM_X is not regarded properly in calculation of secondary demands.
Correction result: In above described context ratio between reference factor of BOM_Z and quantity of line item BOM_X is regarded properly and calculation of secondary demands works well.
5.1.8 Purchasing
5.1.8.1 Purchase orders
RFR-016614 Correction
Framework: Purchasing
Application: Purchase order
Action: Delivery, Cancel delivery
Category: Exception / Invalid data / Unexpected behavior
Problem: The purchase orders support a delivery and return of kit components. The kit main detail will be refreshed with respect to the kit component delivery changes.
By mistake it could occur (e.g. in case of “delivery return cancelation”) that the delivered quantities and the delivery status if a kit main detail were not refreshed as expected.
After that the order contains invalid data.
Correction result: Now the data of kit main details will be refreshed as expected.
Hint: This correction does not contain a data update application. If needed you have to check and correct the following attributes manually: – PurchaseOrderDetail: deliveredQuantity, deliveredQuantities[0..3], deliveryStatus, invoiceStatus, internalBillingStatus, status
– PurchaseOrder: deliverNoneCount, deliverCompleteCount, invoiceNoneCount, invoiceCompleteCount, internalBillingNoneCount, internalBillingCompleteCount, deliveryStatus, invoiceStatus, internalBillingStatus, status
RFR-016614 Correction
Framework: Purchasing
Applications: Purchase orders, Supplier confirmations
Action: Complete confirmation
Category: Unexpected behavior
Problem: A supplier confirmation cannot be completed if the relevant purchase order is invalid with the reason “Document discounts”.
This is a problem if the change by the completion results in such state.
Correction result: Now the problem does not occur anymore.
RFR-016614 Correction
Framework: Inventory
Application: Transport orders
View: n.a.
Action: Save and report
Category: Exception
Problem: An exception occurred saving and reporting a transport order detail line containing a loading unit with a withdrawal proposal.
Correction result: From now saving and reporting transport order detail lines will work as expected.
Technical information: The exception occurred updating the loading unit history.
5.1.8.2 Supplier invoices
RFR-016614 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Save correction invoice
Category: Invalid data / Unexpected behavior
Problem: Please note first that within a correction invoice a “price correction” of an order assignment is defined so: – The current invoice is not a “Cancel invoice”: The quantity sign is greater than zero.
– The current invoice is a “Cancel invoice”: The quantity sign is less than zero.
If an order assignment of a correction invoice is not a “price correction” it is a “quantity correction”.
The order assignment quantities of a correction invoice are not relevant if this order assignment is a “price correction” – so such quantities must neither be considered at save time and also not at booking time (==> purchase order status update).
In contrast to that the quantities of a “quantity correction” have to be considered as within normal invoices.
By mistake quantity corrections were considered only at booking time (==> purchase order status update) but not at save time.
As result in further invoices the quantities of the dialog that belongs to the “Automatically insert line items and assign to order line items” action were not as expected.
Even if the default value within this dialog is not as expected you can use and book further invoices with the correct quantities/values.
Correction result: Now the quantities of “quantity correction” order assignments will be considered as expected.
Please note that existing data (ReceiptInvoiceOrderAssignment#supplierInvoiceQuantities; key: purchase order detail) will not be corrected.
RFR-016614 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Line item booking validation
Category: Invalid data / Unexpected behavior
Problem: The fix “CEE640PB-Fix16” contains some changed quantity validations. By mistakte the supplier invoice does not perform any more all necessary quantity validations at booking time for the “Total quantity” of external supplier invoice line items that are not marked as “additional cost”.
Correction result: Now the booking quantity validations will be performed as expected.
RFR-016614 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Create/Book correction invoice
Category: Unexpected behavior
Problem:
1. If a kit component line item is to be corrected and the determined kit component line item net value is zero the correction invoice cannot be generated/booked (error message “PUR, 1784”).
2. If the supplier invoice to be corrected contains for an order assignment a zero quantity and a positive net value the correction invoice order assignment contains also this positive net value and the correction invoice cannot be generated/booked (error message “PUR, 1784”).
3. A new header number of a correction invoice will be determined by the number range even if no correction is needed and also if the correction invoice cannot be saved.
4. There exists some problems if the base invoice contains only zero quantities and zero net values.
5. The expected amount (“Target amount”) of correction invoice order assignments does contains always the amounts of the base invoice order assignments.
Correction result:
1. Now invoice corrections support also zero net values for kit component line items (same rule as for rebate in kind line items).
2. Now in this case the correction invoice will use the negated values of the original supplier invoice order assignment.
3. Now the correction invoice will be created with a fix temporary header number (“XXXXXXXXXX”). Only if any corrections were determined and the data can be saved with respect to the normal validations a number will be determined and considered from the number range at save time for a new correction invoice.
4.
a.) If a quantity correction exists but the quantity and net value of the base invoice are both zero now the partial value of the relevant purchase order line item is used as base.
Hint: For compatibility reasons other cases use the same logic as before.
b.) If a correction invoice line item has a zero net value it will not be added. Hint: Because of technical restrictions currently in case of kit main details a line item number gap might be present.
5. Now the determined amount of the order assignments will be used also as “Target amount”.
RFR-016614 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate delete
Category: Invalid data / Unexpected behavior
Problem: Internal supplier invoices must not be deleted. The “Delete action” is disabled for such invoices but before this correction it was possible to perform the “delete” functionality directly on the logic level if the invoice is not already booked.
Hint: This might be the case if the creation status “Released” is used in case of invoices that are based on distribution orders.
Correction result: Now the delete validation prevents by a new error message the deletion.
RFR-016614 Correction
Framework: Purchasing
Application: Supplier invoices
Action: “Automatically insert line items and assign to order line items”
Category: Exception
Problem: By mistake the fix “CEE640PB-Fix16 KW09/2026” contains a change for the class “com.cisag.app.purchasing.invoice.ui.OrderAssignmentList” so that this class throws in some cases a “Source measure must not be null!”-Exception.
Correction result: Now the exception does not occur anymore.
5.1.9 Relationship Management
5.1.9.1 Opportunities
RFR-016614 Correction
Framework: Relationship Management
Application: Opportunities
View: n.a.
Action: Validation
Category: Ergonomics
Problem: Individual validation messages are not displayed correctly in Classification fields in Opportunities application.
Correction result: Individual validation messages are displayed correctly in Opportunities application.
RFR-016614 Correction
Framework: Relationship Management, System management
Application: Import data (com.cisag.app.crm.obj.Opportunity)
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: It was impossible to import opportunities with classifications using only path attributes of the classifications.
Correction result: Now it is possible to import opportunities with classification using only path attributes of the classifications.
5.1.10 Sales
5.1.10.1 Assortments
RFR-016614 Correction
Framework: Sales
Application: Assortment lists
View: n.a.
Action: Validate
Category: Invalid data
Problem: It was possible to add time overlapping assortment list detail lines with the same item or classification and a different consideration type. That should not be possible.
Correction result: From now it will not be possible to add time overlapping assortment list detail lines with the same item or classification and a different consideration type.
5.1.10.2 Customer invoices
RFR-016614 Correction
Framework: Sales
Application: Customer invoices
Action: Generate invoice
Category: Invalid data / Unexpected behavior
Problem: By mistake the following CustomerInvoice attributes were not filled correctly in all cases with the data of the relevant partner:
1. invoicingPartyCommercialRegisterNumber, invoicingPartyLocalTaxIdentificationNumber, invoicingPartyTaxIdentificationNumber
2. customerCommercialRegisterNumber, customerLocalTaxIdentificationNumber, customerTaxIdentificationNumber
Correction result: Now in all cases the relevant partner is used. The relevant partner is:
1. The financials organization of the sales organization.
2. The invoice customer (invoice recipient).
Hints: – Please note that the attribute “invoicingParty” contains – as before – in contrast to the relevant partner of 1.) the “sales organization”.
– Please note that the attributes “invoicingPartyCommercialRegisterNumber” and “customerCommercialRegisterNumber” are used only if the “Country-specifics” with the value “Czech Republic” are used for the relevant organization.
– Please note that the business object “com.cisag.app.sales.obj.CustomerInvoiceTaxData” contains the attribute “deliveryCustomerTaxIdentificationNumber”. This attribute is based on the “delivery recipient” of the source line items, and the generated customer invoices are separated according to the value of this attribute.
RFR-016614 Ergonomics
Framework: Sales
Application: Customer invoices query
Action: Show/hide identification pane
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the applications “Order confirmations query” and “Pro forma invoices query” the tabbed pane of the “Customer invoices query” application was not located within the identification area.
As result the special system engine feature for “Show/hide identification pane” action that hides only the tabbed pane and not the identification data.
Correction result: Now the tabbed pane is located within the identification area so that the system engine feature works as expected also for this application.
RFR-016614 Correction
Framework: Sales
Application: Customer invoices
Action: Generate customer invoice
Category: Unexpected behavior
Problem: If a customer invoice is based on a distribution order with the type “Value correction” the customer invoice line item uses always the total quantity of the distribution order line item.
If the total quantity of the distribution order line item is changed after the invoice generation the distribution order line can be invoiced again and after the invoice generation the invoiced quantity decreases by every call and the open invoice quantity increases. As result such a distribution order line item can be completed only if all invoices but the last were canceled.
Correction result: Now the invoice generation uses in this case always the open invoice quantity.
RFR-016614 Correction
Framework: Sales
Application: Customer invoice
Action: Display/Print
Category: Invalid data / Unexpected behavior
Problem: Up from the fix “CEE640PB-Fix 16” the customer invoice unused base discounts were not displayed/printed.
By mistake up from this change invoices based on “internal invoicing data” did not display/print used base discounts any more.
Correction result: Now also in this case used base discounts are printed/displayed as expected.
RFR-016614 Correction
Framework: Sales
Application: Customer invoice
Action: Activate/Print
Category: Unexpected behavior
Problem: By mistake internal customer invoices were not printed after the “activate” step.
Correction result: Now internal customer invoices were printed again after the “activate” step.
RFR-016614 Correction
Framework: Purchasing, Sales
Application: Supplier invoices, Customer invoices
Action: Internal billing
Category: Invalid data / Unexpected behavior
Problem: Before this correction it could occur that a customer invoice is valid but the corresponding supplier invoice is invalid.
As result it was not possible to book the supplier invoice (wrong gross amount and status).
Correction result: Now – in case of internal billing – a customer invoice will be changed to a valid state in the same transaction as the supplier invoice.
Further a customer invoice can be canceled now only if the corresponding supplier invoice is valid.
Data update: If needed such invalid supplier invoices have to be corrected manually.
RFR-016614 Correction
Framework: Sales
Application: Customer invoices
Action: Generate invoice
Category: Invalid data / Unexpected behavior
Problem: Error up from “CEE640PB-Fix04 KW42/2024”: By mistake in some cases a “rebate in kind line item” is not a sub line item of the relevant main line item.
Correction result: Now the “rebate in kind line item” is generated as expected.
5.1.10.3 Kits
RFR-016614 Correction
Framework: Inventory
Application: Transport orders (for picking a delivery order)
View: n.a.
Action: Save and report
Category: Exception
Problem: An exception occurred reporting a transport order containing a transport for a component detail line, that belongs to a kit, that is deleted already.
Correction result: From now reporting a transport order containing a transport for a component detail line, that belongs to a kit, will work as expected, even if the kit is deleted already.
Technical information: It is allowed to change or delete a kits master data at any time.
5.1.10.4 Sales – General
RFR-016614 Correction
Framework: Sales
Applications: Customer proposals, Sales orders
Action: Validate
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the online help the “gross margin” validation will be performed only if the “gross margin” of the header/line items is changed with respect to the persistent state.
Correction result: Now the “gross margin” validation will be performed for the header and all relevant line items by the “validate” action of the header also if the “gross margin” stays unchanged.
Hints: – Please note that there exist some further (unchanged) preconditions (e.g. “not deleted/canceled” line item, “active proposal line item”, “no rebate in kind line item” etc.).
– If you do not want to confirm always the warning “SAL, 319” that belongs to this validation you can use the application “Automatically confirm warnings”.
RFR-016614 Correction
Framework: Sales
Application: Customer proposals, Confirmations, Pro-forma invoices, Customer invoices
Action: Print
Category: Invalid data / Unexpected behavior
Problems:
1. If the kit components are price relevant and have some line-item discounts but are configured so that they will not be printed the printed values of a “gross calculation” document were not OK before this correction because of the missing kit component line-item discounts.
2. The “pro-forma invoices”, “confirmations” and “customer invoices” print document discounts at the end but it was hard to identify which data belongs to line items and which to the document discounts.
3.
a.) The applications for “pro-forma invoices”, “confirmations” and “customer invoices” display document discounts with a confusing background color.
b.) Also the order line items and order info (if ordered by delivery orders) and the delivery info (if ordered by order) have some unexpected colors.
Correction result:
1.) The report has been corrected. Alos now a new warning will be sent within the kits application if the kit components are price relevant but are configured as “Do not print”.
2.) Now a new separator line will be printed before every block of document discounts. Hint: Also, for “Customer proposals”
3.) The usages of the levels (colors) have been improved. Also – if needed – a new “Document discounts” line has been added as separator from the line items data.
In addition to that the sub line-item number will be displayed now within the “Customer invoices” application for shipping order line items (ordered by order; show delivery slip data).
5.1.10.5 Sales orders
RFR-016614 Correction
Framework: Sales
Application: Sales orders
Action: Duplicate line item, Import line item
Category: Invalid data / Unexpected behavior
Problem: If the sales order line item contains a “purchase order header” reference the “Warehouse” of a source (import or duplicated line item) will not be set into the current (target) line item.
Correction result: Up from this correction an existing “purchase order header” reference is not relevant any more. As result the behavior is now as expected.
Hint: As before the “Warehouse” from source will not be considered if the sales order line item uses for “Purchasing link” the value “External third-party order”.
5.1.11 Storage Location Control
5.1.11.1 Inventory orders
RFR-016614 Correction
Framework: Storage Location Control
Application: Inventory orders (Inventory requisitions)
View: n.a.
Transport processes with automatic withdrawal and unpacking of loading units
Category: Unexpected behavior
Problem: The automatic withdrawal and unpacking of loading units were not supported in all cases. This functionality could be needed if a partial amount of a loading unit is requested by a reference order.
Correction result: The automatic withdrawal and unpacking of loading units will be supported for all transport scenarios as expected.
RFR-016614 Correction
Framework: Storage Location Control
Application: Cockpit: Inventory orders
View: n.a.
Action: Complete and report…
Category: Unexpected behavior
Problem: If there were any warning message they could not be confirmed.
Correction result: The background dialog and the parameter of the background action offer the possibility to confirm warnings now as expected.
RFR-016614 Correction
Framework: Storage Location Control / Inventory Management
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Unexpected behavior
Problem: If there was one single prescribed serial number to put it into stock and the target is a simple warehouse an error message would be displayed.
Correction result: A serial number can be put into a simple warehouse stock as expected.
5.1.11.2 Inventory requisitions
RFR-016614 Correction
Framework: Inventory Management
Application: Cockpit: Inventories
View: n.a.
Action: Create inventory requisitions…
Category: Unexpected behavior
Problem: If more than one loading unit was selected the created requisition line item would contain only one loading unit and the total quantity would be erroneous.
Correction result: For each selected loading unit a separate line item will be created as expected.
RFR-016614 Correction
Framework: Inventory management
Application: Inventory requisitions
View: Manual stock movement
Action: Save
Category: Exception
Problem: If the line item was created for a serial number with serial number assignment and the item was changed the save try would cause an exception.
Correction result: If the item of a line item is changed the not matching serial number assignments must be removed before the save step otherwise an error message is sent as expected.
5.2 System development
RFR-016612 Correction
Reduction of exceptions during dialog operation.
RFR-016612 Correction
Framework: System Management
Application: Export data
Solve problem with Dynamic objects on OQL export controller.
5.2.1 Data exchange
RFR-016612 Correction
Framework: n.a.
Application: REST Web Service
View: n.a.
Action: n.a.
Category: Extend REST web service
Description: Extend REST Web service for BIS OQL Export.
RFR-016612 Correction
Framework: All
Application: Cockpit applications
Action: Export according to search criteria
Category: Exception
Problem: In certain cockpits, when data is exported using action “Export objects according to search criteria”, and the batch dialog is accepted by button “In background”, the batch job may be canceled with an exception message like “java.lang.NullPointerException (…) at com.cisag.sys.gui.lnf.Theme.isTouchUI (…)”.
Correction result: The problem is resolved.
Technical information: The problem occurs in specific cockpits, when specific columns are shown.
5.2.2 Kernel
RFR-016612 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Description: Internal performance optimization regarding individual validations.
Technical information: Optimization in com.cisag.sys.tools. validation.log.AbstractCustomizableAdapter.call(Method, Object…): The parser was previously created before checking if a script exists. To improve performance and avoid unnecessary object creation, the parser is now instantiated only after the check confirms that a script exists.
RFR-016612 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Problem: If a lock on application level was granted, an exception was stored internally. This exception was never used.
Correction result: The creation and storage of these unused exceptions have been removed to optimize resources.
Technical information: Optimization in lock management: When an application lock is granted, no exception is instantiated anymore.
RFR-016612 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.
5.2.3 System – General
RFR-016612 Correction
— Correction
Framework: System Management
Application: Batch Jobs
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The processing queue fails to assign batch jobs to workers. This is caused by deadlocks on the Job Business Object, which occur because the sorting order when fetching jobs is not unambiguous. Additionally, if an exception is thrown in the DeadlockResponder thread, the thread terminates silently without leaving any feedback in the logs.
Correction result: The sorting order when fetching batch jobs has been made unambiguous to prevent these deadlocks. Furthermore, the DeadlockResponder thread has been secured against exceptions so that it no longer terminates silently and properly logs errors.
Technical information: Fixed ambiguous sorting on Job BO queries that led to deadlocks. Added proper exception handling and logging to the DeadlockResponder thread to ensure its continuous operation.
RFR-016612 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Problem: The internal exception handling for date and time parsing created unnecessary stacktraces, impacting performance.
Correction result: The creation of stacktraces has been optimized and is now disabled by default.
Technical information: Optimization in com.cisag.sys.kernel.time.CisDateAndTimeParserException: This exception is a CisMessageException. Often the stacktrace is not important, but the message is. The creation of the stacktrace is now disabled by default, but it can be enabled with a debug switch (level: 3).
5.2.4 Web server
RFR-016612 Correction
Framework: System Management
Application: BIS export web services
View: n.a.
Action: n.a
Category: Unexpected behavior
Problem: Web service export to much attributes, even if those attributes are not checked on their export filter.
Correction result: Web service export only checked attributes on their export filter.