| Release | Comarch ERP Enterprise 6.3 |
| Release date | 25.04.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.
This fix comprises the following support deliveries: RFR-016543 – RFR-016545
Information about the features of Comarch ERP Enterprise 6.3 (release news): · INF- 002654 Release-News: Betriebswirtschaftliche Lösungen · INF-002656 Release News: Business Solutions · INF- 002655 Release-News: Technische Lösungen · INF-002661 Release-News: Technical Solutions
System requirements: · INF-002659 Systemvoraussetzungen Comarch ERP Enterprise 6.3 · INF-002660 System Requirements Comarch ERP Enterprise 6.3
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 “Support deliveries query” 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 update 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 Support delivery query 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.
Note:
You need appropriate authorizations to download files. Please refer to the application documentation of “Support delivery query“. If the relevant authorization is missing, please contact your Comarch support partner.
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 CEE630PB-Fix22.”
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 to the message server or to 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 CEE630PB-Fix22
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix21 will be upgraded to CEE630PB-Fix22.
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 CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
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 CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation is 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-016545 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The text of the message SAL-00087 was not as it has to be.
Correction result: From now the text of the message SAL-00087 will be as expected.
5.1.1 Base
5.1.1.1 Base – General
RFR-016545 Correction
Frameworks: Purchasing/Sales
Application: “Cockpit: Purchase prices” and “Cockpit: Sales prices”
Action: Display
Category: Invalid data / Unexpected behavior
Problem: The field for the column “Price list level” does not use always the expected value.
Correction result: Now the value is determined as expected.
5.1.1.2 Cockpits
RFR-016545 Correction
Frameworks: Purchasing, Sales
Applications: “Cockpit: Purchase prices” and “Cockpit: Sales prices”
Action: Change layout
Category: Exception Unexpected behavior / Ergonomics
Problem: If some data is present an exception occurs during the try to add the attribute “discountable” (de: “Rabattfähig”) to the current layout.
Correction result: Now the exception does not occur any more.
5.1.1.3 Contracts/RFQs/Quotations/Orders
RFR-016545 Correction
Frameworks: Purchasing/Sales
Applications: “Cockpit: Distribution orders/line items” and “Cockpit: Purchase orders/line items”
Action: Complete delivery (distribution order: source or target)
Category: Invalid data / Unexpected behavior
Problem: In contrast to the “Complete delivery” functionality of the relevant application and the logic used by the sales order line item cockpit the logic used by the purchase and distribution order line item cockpits does not filter the unsupported details.
As result some invalid data will be present that makes problems e.g. in distribution orders that are based of distribution orders.
Correction result: Now also the logic used by the purchase and distribution order line item cockpits filters all unsupported details.
Data update: If needed, you can repair existing wrong distribution order data manually by the help of the normal functionality (example for source delivery completion):
– Cancel manual completion of source delivery for distribution order
– Create picking order for delivery order
– Cancel (delete) picking order
– Delete delivery order
– Manually complete the distribution order source delivery
RFR-016545 Correction
Applications: Order line item cockpit applications with a “move data” action
Action: “Move date” actions
Category: Invalid data / Unexpected behavior / Ergonomics
Problems:
1. The “move data” actions parameter editor uses always the time zone of the company and not – as expected – the time zone of the organization that is currently selected by the user.
2. The specified date was normalized only with respect to the relevant document time zone by the relevant logic (hours etc. were set to zero).
As result in some cases an unexpected date will be used for the change (next or previous day) because the changed document might use another organization with a different time zone.
Correction result:
1. Now the currently selected organization will be used.
2. Now the specified date value is used as “symbolic date value”; so the relevant logic normalizes the value and shifts it before consideration with respect to the document time zone.
So now the behavior is as expected.
RFR-016545 Extension
Class: com.cisag.app.general.order.log. OrderReferenceComparator
Description: Before this change, the class OrderReferenceComparator called very often the methods “public short getPreviousOrderType()” and “public short getOrderType()” of the hook interface “com.cisag.app.general.order.hook.log.OrderReferenceComparatorHook”.
So, also the “push” and “pop” methods of the internally used “MessageQueueStack” were called very often.
==>With the help of the new class “com.cisag.app.general.order.log.OrderReferenceComparatorUtility” the usage of the hook methods have been reduced up from now.
5.1.1.4 Items
RFR-016545 Correction
Framework: Inventory
Application: Items
View: Inventory
Action: Validate
Category: Ergonomics
Problem: Red edges in case of incorrect user inputs were placed to the wrong input fields.
Correction result: From now the red edges will be placed as expected.
RFR-016545 Correction
Framework: com.cisag.app.general.General
Application: Items
View: Inventory
Action: Modifying the GUI in design mode
Category: Unexpected behavior
Problem: The view ‘Inventory’ contained several GUI components that have duplicate element identification GUIDs. Therefore they were marked with yellow warning triangles and couldn’t be handled correctly by the design manager.
Correction result: From now these GUI components will have either different element identification GUIDs or will be marked as ‘not customizable’. Therefore they will be able to handle correctly by the design manager.
RFR-016545 Correction
Framework: General
Application: Items
View: n.a.
Action: Mark for delete
Category: Exception
Problem: Marking an item as deleted caused a NPE when the item has inventory data and an organization is selected, that is a pure sales organization.
Correction result: From now marking an item as deleted will work as expected.
5.1.2 Calculation
RFR-016545 Correction
Framework: Calculation
Application: Product cost calculation
View: n.a.
Action: Change direct costs / simulate with changed costs
Category: Unexpected behavior
Problem: For a calculation that has multiple times the same resource, but different time UOMs, when changing the simulation costs for one of the resources, the cost of other resources was changed, but it was set to the same value for all resources, even if their time uom differed. When simulation with changed costs took place, the time uom was used and the results were wrong.
Correction result: The cost for the other resources should change according to their time unit (e.g. if 3600 are put in for a resource with time UOM “”hour””, the value should be changed to 60 for “”minute”” and 1 for “”second””). When you calculate, the value should be quantity of time * simulated costs for each entry.”
5.1.2.1 Calculations
RFR-016545 Correction
Framework: Calculation
Application: Product cost calculations, Cockpit: Production items
View: Product cost calculations -> Shelf -> group box “Update sales price using the line” –> Price dimension
Action: Product cost calculations: New, Cockpit: Production items: Generate calculations…
Category: Unexpected behavior
Problem: On creation of a product cost calculation the value of sales price dimension in group box “Update sales price using the line” is missing (unit of measure is set).
Correction result: On creation of a product cost calculation the value of sales price dimension in group box “Update sales price using the line” is set.
The price dimension (value + unit of measure) is retrieved from Item –> Customer view if a customer is specified in group box “Update sales price using the line” else from Item –> Sales view.
Sales price dimension is not set if unit of measure of price dimension differs from unit of measure of calculated quantity. Sales price dimension may change if customer changes.
Please note: a change of sales price dimension is relevant change concerning calculation result and using this result for sales price update. Therefore, the status of product cost calculation is changed to “Created/Incomplete” if sales price dimension has been changed (and calculation already has been performed).
5.1.2.2 Cost centers
RFR-016545 Correction
Framework: Financials
Application: Reorganize cost centers
View: n.a.
Action: Reorganize delete marked cost centers
Category: Unexpected behavior
Problem: When reorganizing delete marked cost centers, an error message is displayed that relevant CostCentreCostRateHistory instances still exist.
Correction result: No more error message is displayed when reorganizing delete marked cost centers
5.1.3 Inventory management
RFR-016545 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Generate by means of loading units from distribution order delivery…
Category: Exception
Problem: An exception occurred when the action “Generate by means of loading units from distribution order delivery…” was executed again after a detail line could not get taken over to the goods receipt.
Correction result: From now the action “Generate by means of loading units from distribution order delivery…” will be deactivated as long as a detail line, that could not get taken over to the goods receipt, is placed in the editor.
5.1.3.1 Identifiers
RFR-016545 Correction
Framework: Inventory Management
Application: Merge/split identifiers
View: Split
Action: Post
Category: Unexpected behavior
Problem: Although the selection “Use source identifier data” was selected the new identifier did not overtake the texts from the “Other fields”.
Correction result: The source identifier data will be used as expected.
5.1.3.2 Inventory count
RFR-016545 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Delete inventory count lists by selection or during the deletion of the inventory count
Category: Unexpected behavior
Problem: The deletion of inventory count lists within the application inventory count was not similar and did not always use the validate hook.
The single object standard hook implementations were not correctly called by the inventory count (wrong context class within the hook contract).
Correction result: Both actions use the same delete validations as expected and the inventory count list hook implementations will also be called now.
The hook implementations of the hook contract (PhysicalInventory) will now be called as expected
Technical information: The hook contract uses the correct context class (com.cisag.app.inventory.physical.log. PhysicalInventorySingleObjectEntity) now.
5.1.3.3 Picking orders
RFR-016545 Correction
Framework: Inventory
Application: Import data
Filter: Picking transactions
Action: Import
Category: Unexpected behavior
Problem: The import controller logic always looped over all detail lines when updating the picking order for a single picking transaction.
Correction result: From now, when updating the picking order, the import controller logic will handle only detail lines which had a picking transaction imported.
RFR-016545 Correction
Framework: Inventory
Application: Picking orders
View: Delivery
Action: Split delivery order
Category: Exception
Problem: An exception occurred trying to split a delivery order that contains ‘additional detail’ lines.
Correction result: From now splitting a delivery order that contains ‘additional detail’ lines will work as expected.
RFR-016545 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Cancel
Category: Exception
Problem: An exception sometimes occurred, if a loaded picking order is canceled (deleted) by background application.
Correction result: From now an error message will be displayed if a loaded picking order is canceled (deleted) by background application.
5.1.3.4 Receipts of goods
RFR-016545 Correction
Framework: Inventory
Application: Goods receipts
View: Distribution
Action: Create goods receipt from loading units
Category: Unexpected behavior
Problem: Identifier numbers were not mapped to the created goods receipt if the “Use supplier item identifiers” checkbox of the application “Customizing” in the view “Identifiers – Base” is selected.
Correction result: From now the setting in the “Use supplier item identifier” checkbox of the application “Customizing” will not be used for goods receipts of distribution type. It’s for purchasing goods receipt type only.
5.1.3.5 Reservations
RFR-016545 Correction
Framework: Inventory Management
Application: Inventory postings
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: If the fixed reservation customizing setting “Inventory that is available again” is active it would be tried to reserve updated stock but also for outgoing inventory postings. This is not necessary and could create not necessary locks that could influence the inventory posting processing.
Correction result: For outgoing inventory postings it will not be tried to reserve the updated warehouse stock automatically as expected. Because it will never be “inventory that is available again”.
5.1.3.6 Warehouses
RFR-016545 Correction
Framework: Inventory Management
Application: Warehouses
View: n.a.
Action: Load
Category: Exception
Problem: If the general tab was set to not visible within an own design view the application view could not be loaded.
Correction result: Application views can be loaded as expected.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016545 Correction
Framework: Sales
Application: Distribution orders
Action: Validate (line item editor)
Category: Exception
Problem: An exception occurs by the “line item editor validation” for a reference item if the sales organization is empty.
Correction result: Now the exception does not occur any more.
Technical information: For analogy reasons also the coding of the sales proposals and orders have been changed but here the error cannot occur because the sales organization is always present for valid data.
5.1.5 Planning
RFR-016545 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer/update planning data and execute planning
Category: Unexpected behavior
Problem: Process structure of a product has multiple levels. Planning a (semi-finished) product creates secondary demands by simulation a dispatching one level. These secondary demands are shifted to previous working day.
Shifting is necessary if secondary demand is an external/internal purchased material. Shifting is superfluous if secondary demand is a semi-finished product.
Example: Preliminary: For simplicity of explanation it is assumed that product and semi-finished products can be manufactured within 1 hour using proper routings.
A demand of product EP00 at period T must be covered by a planning recommendation (at T 00:00:00).
Simulation of dispatching of EP00 results in a secondary demand of semi-finished product SF00 at period T-1 (dispatching is done with latest end: T-1 24:00:00). The demand of SF00 is shifted to T-2!
If semi-finished product SF00 is planned the demand at period T-2 may result in a recommendation at T-2. A simulation of dispatching of SF00 is done with latest end at period T-3 24:00:00.
This procedure is continued for each level of product EP00 and results for each level in a double shift of working days and an earlier availability than needed.
If recommendation of SF00 at T-2 is turned into a production order (latest end date T-3 24:00.00) this will result in a availability of SF00 at T-3 although a latest possible availability could be at T-2.
Correction result: Shifting a secondary demand of a semi-finished product to a previous working day is not performed anymore.
In above used example result now is: Secondary demand without shift is period T-1.
Planning SF00 may result in a recommendation for T-1. A simulation of dispatching of SF00 is done with latest end at period T-2 24:00:00. If SF00also uses a semi-finished product SF01 then secondary demand of SF01 is T-2.
If recommendation of SF00 at T-1 is turned into a production order (latest end date T-2 24:00.00) this will result in a availability of SF00 at T-2 (instead of T-3).
Please note: Old behavior of shifting secondary demand of a semi-finished product can still be enabled by setting server property “com.cisag.app.aps.log.v04. APSPlanningLogic04_dateShiftOfDemand” = true.
RFR-016545 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: New feature
Description: The planning log file tracks messages in the order they occur during the planning run.
In case identical messages occur, they have been written multiple times to the file. Now duplicate messages are recognized and not written into the planning log a 2nd time as long as they are found within the last 10000 messages written.
RFR-016545 Correction
Framework: Production
Application: Cockpit: Production orders/material line items
View: Cockpit: Production orders/material line items
Action: Refresh
Category: Unexpected behavior
Problem: In design mode there is a possibility to specify available columns. After adding attributes for alias ITEM_PLANNING_DATA the planning data of production item of production order was displayed instead of material planning data.
Correction result: Now material planning data are displayed.
RFR-016545 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations, Calculate distribution recommendations
View: n.a.
Action: Calculate purchasing recommendations, Calculate distribution recommendations
Category: Unexpected behavior
Problem: The projected inventory level underrun is detected for days of certain future time range. This time range starts with the “per-date”. The problem was it ends at day equal “per-date” plus “Replenishment lead time”(from planning data of an item) if no delivery calendar was used.
It could lead to situation when checked time range is too small and some recommendations are not created for certain days although they should be created for that days.
Correction result: Now this end of the time range is always increase by one and by “Transition time goods receipt” from item planning data regardless if delivery calendar is used or not.
RFR-016545 Correction
Framework: Production
Application: Delivery calendar assignment
View: n.a.
Action: Mark for deletion
Category: Unexpected behavior
Problem: Action “mark for deletion” was enabled, but is not needed. It’s always possible to directly delete, because there are no dependencies and there’s no big data structures that need more time for deletion.
Correction result: Action “mark for deletion” is disabled.
5.1.5.1 Material requirements planning
RFR-016545 Correction
Framework: Planning
Application: Material requirement planning
View: n.a.
Action: Transfer planning data and execute planning
Category: Unexpected behavior
Problem: Planning item has more than one version of planning and production and uses different bill of materials for each version which has other production item in it.
If one of the bill of materials will be blocked for not last version then each bill of material for the next versions will be not considered during determining order of planning which can lead to wrong recommendations or even to lack of recommendations for secondary demands.
Correction result: All versions of items are now considered properly during determining order of planning, which means that second demands are considered properly now in this case.
RFR-016545 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Exception
Problem: The planned item needs to have weekly or monthly forecast. If there are no working days in a week (for weekly forecast) or in a month (for monthly forecast) when planning starts, then the exception occurred.
Correction result: Now exception does not occur anymore if there are no working days in a week or month.
RFR-016545 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Various Planning actions
Category: Unexpected behavior
Problem: When a planned item with internal demand coverage has its source site set to the same as the site that is currently planned, wrong error messages were shown about why the item cannot be planned.
Correction result: The error messages have correct text now hinting at the correct source of the problem.
5.1.5.2 Planning – General
RFR-016545 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem:
1. If message PRD-02056 was triggered for Item which has “Demand coverage” in view “Planning” set to “Internal purchase” then wrong organization or id number was displayed instead of proper internal purchasing organization in this message.
2. Purchase status of an item is set “blocked” at a wrong (and not relevant) organization. Purchase status is “released” at correct purchasing organization level. Nevertheless this context leads to output of message PRD 2056 and no recommendations are created when items “Demand coverage” is set to “Purchasing” or “Internal purchasing”. The wrong status “blocked” may be set by a wrong import of items.
Correction result:
1. In message PRD-02056 proper organization is now displayed based on configuration in planning data of an item.
2. A purchase status “blocked” at a wrong (and not relevant) organization has no impact on creation of necessary recommendations. Only status of relevant purchasing organization has impact.
5.1.6 Production
RFR-016545 Correction
Framework: Production
Application: Receipt of goods, Operation postings
View: n.a.
Action: Post
Category: Unexpected behavior
Problem: A material of a production order has a setup quantity. Quantity (target + setup) is reported automatically.
Note: in application “production orders” setup quantity is not displayed only sum of target and setup. A receipt of goods is done which only covers part of target quantity of production order.
Result: material is reported automatically. Reported quantity is the prorated value of target + setup.
Correction result: Automatic reporting of material with setup quantity must be done as follows.
First (partial) receipt of goods must trigger a report of material with complete setup quantity + prorated value of genuine target quantity.
Following (partial) receipt of goods must trigger a report of material with prorated value of genuine target quantity only.
Example: Target quantity production order: 1000, target quantity material: 1000, setup quantity material: 100
First receipt of goods: 300 –> reported quantity of material is 100 + 300 = 400
Second receipt of goods: 700 –> reported quantity of material: 700
Cancellations of receipt of goods: Only if the (last) receipt of goods sets back reported quantity to zero the complete setup quantity + prorated value of genuine target quantity of material is canceled.
Example from above continued: Receipt of goods of 300 canceled –> reported quantity of material is -300.
Receipt of goods of 700 canceled –> reported quantity of material is -100 + -700 = -800!
Please note: New automatic reporting behavior with specified fixed quantity works also when automatic report is triggered by operation posting.
Additional: System property com.cisag. app.production.ui.MaterialIssuePostingList_displayFixedQuantity=true enables displaying column “of which setup quantity” right of column “Total quantity” of application “Production issues”. Column displays the part of “Total quantity” which counts for setup quantity.
RFR-016545 Correction
Framework: Production, Costing
Application: Cockpit: Material planning results, Cockpit: Production items
View: n.a.
Action: Open
Category: Unexpected behavior
Problem: Opening Cockpit: Production items(for production framework) or Cockpit: Material planning results, sends warning into logs about missing hook contract for context class.
Correction result: Now hook contract is founded properly so in result no warning is sent into logs.
RFR-016545 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: Post production issues
Category: Unexpected behavior
Problem: When posting a production issue, an error message is triggered rarely, seemingly under random conditions. The error message is “Data have been changed by user ‘yourself'”, and the production issue posting fails.
The production order is not correctly locked as well. The same problem appears when adding identifier lines, saving and then posting a production issue.
Correction result: No error message occurs, production issue can correctly be posted, production order is correctly locked.
RFR-016545 Correction
Framework: Production
Application: Production Orders
View: Planning Data
Action: n.a.
Category: Unexpected behavior
Problem: The view does not show the number and description of an item position, if the item is of type equipment.
Correction result: The view does show the number and description of an item position, if the item is of type equipment.
RFR-016545 Correction
Framework: Costing
Application: Product cost calculations
View: Pre-calculation with quotation reference, Preliminary calculation with service item
Action: Open
Category: Exception
Problem:
1. Trying to open product cost calculation of destination category “Pre-calculation with quotation reference” when customizing function “Production: Configuration” is disabled caused exception.
2. Trying to open product cost calculation of destination category “Preliminary calculation with service item” when customizing function “External manufacturing” customizing function or/and “Internal external manufacturing” option is disabled caused exception.
Correction result: Now in both cases an error is displayed instead informing user why he cannot open chosen product cost calculation.
RFR-016545 Correction
Framework: Production
Application: Order maintenance
View: Table view
Action: Split or replace operation…
Category: Unexpected behavior
Problem: A operation of a production order can be split by specifying a split quantity and a new operation (no replacing of operation). After splitting is performed the result is shown in order maintenance for possible check. Original operation and assigned resources as well as new operation and assigned resources are displayed as changed line items.
Result: Quantity of original operation and assigned resources are reduced according to split quantity but variable times are not reduced. Variable times do not change if production order is saved after splitting.
Correction result: After splitting is performed original operation and assigned resources show reduced variable time due to reduction of quantity.
RFR-016545 Correction
Framework: Production
Application: Import data
View: n.a.
Action: Import data
Category: Exception
Problem: Importing the BO com.cisag.app.general. obj.DemandForecast triggers an Exception and prevents import when two rows have the same business key attributes with only the keyExtension attribute differing.
Correction result: Importing the BO com. cisag.app.general.obj.DemandForecast works correctly.
Technical information: It is recommended to remove as much old data as possible from the table before installing this support delivery to speed up the index recreation process.
To delete all forecast data before the example year 2025, use the following OQL: DELETE FROM com.cisag.app.general.obj.DemandForecast DF
WHERE DF:year < 2025
RFR-016545 Correction
Framework: Production
Application: Resource allocation
View: Diagram
Action: n.a.
Category: Unexpected behavior
Problem: Transport time is displayed after operation.
Correction result: The transport time is always before the operation and is now also displayed as such.
RFR-016545 Correction
Framework: Production
Application: Product configuration rules
View: Conditions and actions
Action: n.a.
Category: Unexpected behavior
Problem: Every odd sequence of actions was colored in the same way as the condition above it in CDS-design, making it difficult to differentiate.
Correction result: Condition is always white, actions below each condition always a different color (light grey in standard CDS).
RFR-016545 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Recalculate due date and quantity
Category: Unexpected behavior
Problem: Operation in production order needs to have at least two resources that starts at the same time. It could be achieved via proper dependency or in case there is no any dependency between each resource.
Rescheduling that production order with finite capacity checkbox will use already existed reservations for rescheduled resources and in result calculated dates will be too far into the future(for forward scheduling) or too far into the past(for backward scheduling).
Correction result: Now rescheduling with finite capacity does not taking into account old reservations of rescheduled resources and in result calculated dates are now correct.
RFR-016545 Correction
Framework: Production
Application: Bills of material, Bills or resources
View: Bills of material, Bills or resources
Action: Refresh with Line item filter via Item
Category: Unexpected behavior
Problem: When in “Line item filter” tab an “Item” field was not empty then the filter did not filter out following details: bills of material line items in “Bills of material” application and operations line items in “Bill of resources” application.
Correction result: Now when “Item” field in “Line item filter” is not empty all bills of material line items (In “Bill of material” application) and operations (In “Bill of resources” application) are now filtered out.
5.1.6.1 Product configuration
RFR-016545 Correction
Framework: Production
Application: Product configuration rules
View: Steps, Configuration characteristics, Condition lists, Conditions and actions
Action: Validate, Refresh, Change view
Category: Unexpected behavior
Problem:
1. Double click any detail on the list. Perform action “Accept entries” in detail editor without changing anything. Then after pressing validate, refresh or changing view the application goes into edit mode although nothing has been changed.
2. On views: “Steps” and “Condition lists” create new detail and perform action “Accept entries” in detail editor. Do not save entire “Product configuration rule”. Change view to any different than active one and confirm warning about losing all changes. Then after validation application goes into edit mode although all changes have been lost.
Correction result:
1. In described case when nothing has been changed, application does not go into edit mode anymore.
2. After confirming losing all changes and switching view, edit mode is not activated after pressing validation if nothing has been changed.
RFR-016545 Correction
Framework: Production
Application: Product configuration rules
View: a) “Configuration characteristics” and b) “Conditions and actions”
Action: a) right click on field “Step” and choose “Properties”, b) right click on field “Condifiton list”/”Start condition list” and choose “Properties”
Category: Exception
Problem: Performing actions described above in views 1. “Configuration characteristics” or 2. “Conditions and actions” causes an exception.
Correction result: Performing actions described above in views 1. “Configuration characteristics” or 2. “Conditions and actions” work as expected. No exceptions occur.
5.1.6.2 Production orders
RFR-016545 Correction
Framework: Production
Application: Cockpit: Production orders
View: Cockpit: Production orders
Action: Refresh
Category: Unexpected behavior
Problem: Problem occurs only if master data versioning is enabled. When there is multiple versions of bill of material, routing or bill of resources and at least one of them is used in any production order then in Cockpit: Production orders this production order will be displayed multiple times instead of just one.
Correction result: Now production order that uses versioned bill of material, routing or bill of resource is displayed only once in Cockpit: Production orders.
RFR-016545 Correction
Framework: Production
Application: Cockpit: Production orders
View: n.a.
Action: Change due date and quantity…
Category: Unexpected behavior
Problem: If more than one order selected in Cockpit: Production orders are rescheduled, this action may fail for all or some orders.
Rescheduling fails for those orders which have a target quantity of inventory managed packaging unit. An error message is output which states that unit of measure of rescheduling quantity does not match unit of measure of target quantity of production order (PRD-02453)
Correction result: Rescheduling of more than one production order selected in Cockpit: Production orders is performed as expected. No error messages are output.
5.1.6.3 Resources
RFR-016545 Correction
Framework: Production
Application: Resource utilization
View: n.a.
Action: Refresh with Reservations enabled
Category: Exception
Problem:
1. Setting time period with begin or end date set to infinite (by entering “beginDate -” or “- endData”) or to date over minimum/maximum date sometimes does not changed wrong period to correct one although the logic used correct date
2. If end date of period was set to maximum date for chosen organization and “Reservations” was enabled then during loading reservation a fatal exception occurred and application has been closed.
Correction result:
1. Now the period is changed properly and displaying same period that is used by logic
2. Now if loading reservations failed for given time range an error message will be displayed.
Technical information: New system property has been added “com.cisag.app.production.SchedulingMinimalYear” to determine minimum year to be used for scheduling.
5.1.6.4 Where-used list
RFR-016545 Correction
Framework: Production
Application: Where-used list
View: Item
Action: Refresh
Category: Exception
Problem: Problem occurs only when “Master data versioning” is enabled in customizing. In application “Where-used list” when trying to load Production item on level bigger than 1, an exception occurred when Bill of resources specified in this production item is blocked.
Correction result: Exception does not occur anymore and loading finish successfully.
5.1.7 Purchasing
5.1.7.1 Purchase orders
RFR-016545 Correction
Framework: Purchasing
Applications: Supplier proposals, Purchase Orders
Category: Unexpected behavior / Ergonomics
Problem: By mistake the line item field “Cash discount assessment basis” (attribut “totalValues:cashDiscountBase”) was editable within the user interface but all changes were discarded by the line item calculation.
Correction result: Now the field of this attribute is “Read only” as expected.
RFR-016545 Correction
Framework: Purchasing
Application: Purchase orders
Action: Status update
Category: Exception
Problem: If the current user is not authorized a purchase order an exception occurs during the try to update the status by the supplier invoice.
Correction result: Now the exception does not occur any more.
5.1.7.2 Supplier invoices
RFR-016545 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Cancel
Category: Unexpected behavior
Problem: By mistake the “Cancel supplier invoice” functionality saves single main line items and did not use the normal block size.
Correction result: Now the functionality works as expected.
RFR-016545 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Generate correction supplier invoice
Category: Exception
Problem: If the generation of a new “correction supplier invoice” fails (e.g. because of missing create authorization) an exception occurs.
Correction result: Now the exception does not occur any more.
RFR-016545 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Change detection
Category: Unexpected behavior / Ergonomics
Problem: If a changeable supplier invoice is present and the application mode is “display” and some data is changed by the line item editor (but not applied) these changes were not detected (e.g. if the application is closed).
Correction result: Now such changes will be detected as expected.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016545 Correction
Framework: Sales
Application: Customer invoices
Action: Generate customer invoice
Category: Exception / Invalid data / Unexpected behavior
Problems: Multiple problems in case of retail calculation and the kind of pricing value “Gross” in the case that discounts with own accounts are used.
1. Because of the correction delivered by “CEE630PB-Fix19 KW45/2024” a new NullPointerException can occur within the method “com.cisag.app.sales. invoice.log.DefaultUpdate.calculateValuesWithoutTax”.
2. A “java.lang.IllegalArgumentException: details must not be empty!” can occur within the method “com.cisag.app.sales.invoice.log.InvoicingEntity. dispatchRoundingDifferences”.
Correction result: Now both problems have been corrected.
RFR-016545 Correction
Framework: Sales
Application: Customer invoices
Action: Validate cancel
Category: Unexpected behavior
Problem: Before the “Cancel invoice” action will be executed, some validations will be performed. To avoid problems within the accounting system a standard validation is present that checks if the payment status is “None” – if not the error message “SAL-08760” will be send.
Normally, this validation is OK but in case of a “zero invoice” this validation might be a problem because such invoices will be typically set by the “transfer to accounting system” step as paid.
As a result, such an invoice cannot be canceled.
Correction result: Now the “payment status” will not be checked any more for a “zero invoice” (gross amount of the customer invoice is zero) so that the error message “SAL-08760” will not occur any more for such invoices.
5.1.8.2 Sales orders
RFR-016545 Correction
Framework: Sales
Application: Sales orders
Action: Save (sub step “Refresh purchase order line items”)
Category: Unexpected behavior
Problem: In case of new purchase order line items the “Purchase order line item request date” will be set to the “Purchase order line item delivery date”. But in contrast to the “Purchase order line item delivery date” the “Purchase order line item request date” will not be refreshed with respect to the relevant sales order line item data.
Correction result:
1. Unchanged behavior for “Purchase order line item delivery date:
The relevant sales order line item date dependents on the “Purchasing reference” value. In case of “Sales delivery” the relevant date is the “Shipping date” otherwise (direct delivery) the “Delivery date”.
The “Purchase order line item delivery date” will be set to the “New relevant sales order line item date” in the following cases:
– The “Purchase order line item delivery date” is the same as the “Old relevant sales order line item date”.
OR
– The “New relevant sales order line item date” is before the “Purchase order line item availability date”
Hint: Please note the in case of “Direct delivery” the “Purchase order line item availability date” is always the same as the “Purchase order line item delivery date”.
2. Changed behavior for “Purchase order line item preferred date”:
The “Purchase order line item preferred date” will be set to the “New relevant sales order line item date” in the following cases: Precondition: The “Purchase order line item delivery date” changes with respect to 1.
Further conditions: – The “Purchase order line item preferred date” is the same as the “Old relevant sales order line item date”.
OR
– The “New relevant sales order line item date” is before the “Purchase order line item preferred date”
5.1.9 Storage Location Control
5.1.9.1 Storage location reservations
RFR-016545 Correction
Framework: Storage Location Control
Application: Picking orders/Correct voucher data and reservations
View: n.a.
Genrate inventory orders and reported warehouse stock
Category: Unexpected behavior
Problem: If the inventory order propose several identifiers in packaging in some cases the warehouse unit of the item is proposed although the packaging would be available.
After reporting the inventory order the correction “Correct voucher data and reservations” application could consider identifiers with packaging in one line item several times.
Correction result: The proposed identifier and their packaging will be proposed as expected.
The correction application “Correct voucher data and reservations” will consider the identifiers only once as expected.
5.2 System development
RFR-016543 Correction
Framework: System management
Application: system cockpit
View: database
Action: n.a.
Category: Unexpected behavior
Problem: If schema and database name differ, then no collation was found on postgreSQL databases.
Correction result: The collation is now found.
RFR-016543 Correction
Framework: Software development
Application: development objects
View: business objects
Action: opening NLS dialog for NLS BO
Category: Exception
Problem: NLS Business objects do not necessarily have an associated text object.
The NLS dialog for field ‘description’ did not took this in account leading to an exception.
Correction result: No exception anymore. Should there be no associated text object, then an empty list is shown.
RFR-016543 Correction
Process: Start of application server / acquire lock
Category: Exception
Problem:
1. Upon starting, “IllegalStateException: instance is not created” might occur, with reference to “system session executing com.cisag.sys.kernel.locking. CisLockTable$DeadlockResponder”.
2. “ArrayIndexOutOfBoundsException: arraycopy: last destination index XX out of bounds” might (rarely) occur if a lock request cannot be granted
Correction result: No exceptions.
RFR-016543 Correction
Framework: System management
Application: Data exchange log entries
View: n.a.
Action: Display messages, Display import errors
Category: Exception
Problem: Very long import/export error messages are not stored completely in the data exchange log. Trying to display them yields “IllegalArgumentException: Parameter messageClassName must not be null”.
Correction result: New long messages are stored after cropping contained display strings like exception text, stack trace or parameter values if necessary.
Old long messages are displayed using wrapper error message BIS-922.
RFR-016543 Extension
Unnecessary DB accesses removed.
RFR-016543 Correction
Framework: Software development
Application: development objects
View: Extension
Action: Delete
Category: Unexpected behavior
Problem: Trying to delete an extension results in an error message indicating the data have be changed. This message was wrong.
When deleting an object, those objects depending on the object to be deleted will be added to the task as well.
If they are already in the job nothing but changing the update timestamp happen.
A circular dependency between objects lead to a timestamp update for the extension leading to the message.
Correction result: The circular dependency is detected and deleting is now possible.
RFR-016543 Correction
Process: Boot application server as service
Category: Unexpected behavior
Problem: For reasons yet unknown, the application server is sometimes booted without JVM parameters.
Correction result: The boot terminates if no JVM parameter are given in the environment variable SEMIRAMIS_JVM. As this seems to coincide with a missing configuration file semiramis.conf, the boot also terminates if this file could not be written.
RFR-016544 Correction
Framework: System management
Application: Data exchange log entries
View: n.a.
Action: Display messages, Display import errors
Category: Exception
Problem: Very long import/export error messages are not stored completely in the data exchange log. Trying to display them yields “IllegalArgumentException: Parameter messageClassName must not be null”.
Correction result: New long messages are stored after cropping contained display strings like exception text, stack trace or parameter values if necessary.
Old long messages are displayed using wrapper error message BIS-922.
RFR-016544 Correction
Process: Boot application server as service
Category: Unexpected behavior
Problem: For reasons yet unknown, the application server is sometimes booted without JVM parameters.
Correction result: The boot terminates if no JVM parameter are given in the environment variable SEMIRAMIS_JVM. As this seems to coincide with a missing configuration file semiramis.conf, the boot also terminates if this file couldn’t be written.
RFR-016544 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
5.2.1 Application server
RFR-016543 Correction
Process: Activating Voucher references chain dockable view
Category: Unexpected behavior
Problem: The dockable views “Voucher references chain” of an application, e.g. supplier invoices, and the view “Messages” are not pinned. After the application produces errors or warnings, the message view is displayed. Clicking on the “Voucher references chain” view icon does not display the chain view, but focusses the message view again. This occurs if the chain view was not opened before. A second click works as expected.
Correction result: The first click activates the chain view.
5.2.1.1 Batch
RFR-016543 Correction
Framework: System Management
Executing batch jobs with start mode “At restart of application server”
Category: Unexpected behavior
Problem: After starting an application server, batch jobs with start mode “At restart of application server” may remain in state “Released” and are not executed. This issue can appear only if the processing queue is distributed and uses workers that are shared between multiple processing queues.
Correction result: The problem is resolved.
Technical information: If a batch job with start mode “At restart of application server” ends itself, or its session is closed by a user, the job also switches into “Released” state. This behavior is correct, and is not caused by the described problem.
5.2.2 Data exchange
RFR-016543 Correction
Framework: System Management
Web service calls (incoming)
Category: Unexpected behavior
Problem: Multiple web service calls that re-use the CEE session, and use URL query strings “contentLanguage” or “displayLanguage” with different languages specified for the query strings among subsequent calls, may fail with a HTTP 500 status code.
Correction result: The problem is resolved.
Technical information: The problem occurs in the third call with a different language specified for one of the query strings, and the calls are actually executed in the same session.
RFR-016543 Correction
Framework: System Management
Application: Import data
View: n.a.
Action: Import data
Category: Unexpected behavior
Problem: Sometimes import json file with wrong data, will end with success notification.
Correction result: Import json file with wrong data, will end with error notification.
5.2.3 GUI
RFR-016543 Correction
Framework: Base
Application: Dashboard
View: n.a.
Action: “Edit…” (context menu of dashboard canvas)
Category: Unexpected behavior
Problem: The layout of the widgets inside a dashboard is based on a grid with a default of 12 (rows) x 12 (columns). The “Edit…” dialog should allow to change these settings, as long the dashboard is still empty. But the fields “Number of rows/columns” were read-only.
Correction result: Fixed. As long the dashboard is empty, the fields “Number of rows/columns” are now editable.
5.2.4 Kernel
RFR-016544 Correction
Framework: System management
Application: Change journal query
View: Business entity
Action: Update
Category: Exception
Problem: The modification journal data might be inconsistent, e.g. if they were copied from another system with a different repository database. The referenced table descriptions might not exist in the current repository. This results in exception “IllegalArgumentException: Parameter o1 must not be null.”
Correction result: Error message KRN-1391 is updated to cover undefined table descriptions.
RFR-016543 Correction
Framework: System management
Application: Change journal query
View: Business entity
Action: Update
Category: Exception
Problem: The modification journal data might be inconsistent, e.g. if they were copied from another system with a different repository database. The referenced table descriptions might not exist in the current repository. This results in exception “IllegalArgumentException: Parameter o1 must not be null.”
Correction result: Error message KRN-1391 is updated to cover undefined table descriptions.
5.2.5 Workflow
5.2.5.1 Absences
RFR-016543 Correction
Framework: Workflow
Application: Absences
View: n.a.
Action: Duplicate
Category: Exception
Problem: Upon duplication an error occurs, stating that the current absence already exists. According to the plan, only one absence per user is allowed, in order to avoid potential problems w/ HR compliance.
Correction result: Now, duplication is impossible.
5.2.5.2 Workflow templates (transport)
RFR-016543 Correction
Framework: Workflow
Application: Process Definitions
View: n.a.
Action: Safe a template…
Category: Unexpected behavior
Problem: By generating a template version of any process definition which has a “Responsible workflow role” created from a template workflow role, we get a process definition template without a corresponding template linked to that workflow role.
Correction result: We get a process definition template with a linked “Responsible workflow role” template.