| Release | Comarch ERP Enterprise 6.4 |
| Release date | 05.04.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.4.
This fix comprises the following support deliveries: RFR-016537 – RFR-016539
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-Fix08”.
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-Fix08
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix07 will be upgraded to CEE640PB-Fix08.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
With the “Query data updates” application, you must schedule the following data updates, for any point in time.
UPDSUP120219
Updates storage locations without storage location onhand
In this update application new storage location onhands will be created and initialised for all storage locations that do not have them and the relevant active inventory management servers will be reloaded automatically.
UPDADU120324
Correction UnitLoadOnhand storageLocation and zone attributes (null to ZEROGUID)
Correction of the UnitLoadOnhand storageLocation and zone attributes (null to ZEROGUID)
5.1 Application development
RFR-016539 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016539 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.
RFR-016539 Ergonomics
Update of the EN user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016539 Extension
Framework: All frameworks that use additional fields
Application: All application that use additional fields
View: n.a.
Action: Loading
Category: Ergonomics
Problem: If an application uses other fields, the metadata of the other fields is loaded during loading. In some cases, database accesses always take place.
Correction result: The number of database accesses required has been reduced.
RFR-016539 Correction
Framework: Sales
Application: UPDBUG029370
View: n.a.
Action: Update data
Category: Unexpected behavior
Problem: The update application skipped several detail lines by fault.
Correction result: From now the update application will handle and update all needed detail lines.
5.1.1 Base
RFR-016539 Correction
Framework: Base
Application: Time series
View: n.a.
Action:n.a.
Category: Exception, Incorrect positioning of some fields on UI, translator’s mistake
Problem:
– The exception “java.lang.RuntimeException: Transaction info could not be determined as no transaction guid was specified!” is thrown when the application is started and the value help is called for the first time, and this exception will be repeated until new time series is created and saved.
– Incorrect positioning of some fields on UI.
– Some fields have translation although they have no labels. A correction request is registered for this purpose.
Correction result: The problems are fixed.
5.1.1.1 Cockpits
RFR-016539 Correction
Framework: All
Application: Customizable views
View: Views with totals (average)
Action: n.a.
Category: Unexpected behavior
Problem: The computed average value for a foreign amount column is rounded to nearest currency unit and not to the number of decimals as defined for the currency.
Correction result: Fixed.
RFR-016539 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.2 Contracts/RFQs/Quotations/Orders
RFR-016539 Correction
Framework: Sales
Action: Create customer invoices based on sales orders with shipping orders
Category: Exception
Problem: In some cases, an exception “Get of object not possible: transaction not found” occurs during the try to get the header object of an invoiced ShippingOrderDetail.
Correction result: Now the exception does not occur any more.
RFR-016539 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.
5.1.1.3 Items
RFR-016539 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.
RFR-016539 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-016539 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 could not 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 be handled correctly by the design manager.
RFR-016539 Correction
Class:
-com.cisag.app.purchasing.cockpit.ui. SupplierCockpit
-com.cisag.app.sales.cockpit.ui.CustomerCockpit
-com.cisag.app.general.cockpit.ui. PartnerCockpit
-com.cisag.app.financials.cockpit.ui.PartnerAccountingDataCockpit
-com.cisag.app. general.cockpit.ui.EmployeeCockpit
Description: The HookContext for the BatchActionHookManager was specified with ‘this.getClass’. This does not work if someone wants to extend the cockpit and the application class is replaced by an extended, derived class. The HookContext then changes and the implemented hook actions are no longer found.
Correction: The HookContext is now replaced by the final name of the application class.
5.1.1.4 Partner templates
RFR-016539 Correction
Framework: Base
Application: Partner templates
View: n.a.
Action: Load, Reload via Icons
Category: Unexpected behavior / Ergonomics
Problem: View changing and changing the organization via the icons, contained in the ident pane of the application, did not work.
Correction result: From now changing the view and changing the organization via the icons, contained in the ident pane of the application, will work as expected.
5.1.1.5 Partners
RFR-016539 Correction
Framework: Sales
Application: Cockpit: Customers
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: Customers, which belong to a sales organization, that’s not a purchasing organization too, wasn’t be displayed in the cockpit.
Correction result: From now, as expected, all customers which belong to a sales organization, that is assigned to the user will be displayed in the cockpit
Framework: Base
Application: Cockpit: Employees
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: All employees defined was been displayed, even if they belong to an organization the user is not assigned to.
Correction result: From now, as expected, only employees which belong to an organization, that is assigned to the user will be displayed in the cockpit
RFR-016539 Correction
Framework: Base
Application: Import data
Importfilter: com.cisag.app.general.obj.Partner
Action: Import
Category: Unexpected behavior
Problem: The import process of a partner using a partner template called the validation method com.cisag.app.general.partner.log.ImportExport.validateTemplatePartnerRoles() twice. That is not necessary.
Correction result: From now the validation method com.cisag.app.general.partner.log.ImportExport.validateTemplatePartnerRoles() will be called only one time as needed and expected.
5.1.2 Calculation
RFR-016539 Correction
Framework: Calculation
Application: Product Cost Calculations
View: Pre-calculation
Action: Change simulated price in editor
Category: Unexpected behavior
Problem: Changing the simulated price of a resource causes a change for all resources in the calculation to this same price.
Correction result: Changing the simulated price of a resource causes a change for all of the same resources, for all others the price stays as before.
RFR-016539 Correction
Framework: Calculation
Application: Trade cost calculations
View: n.a.
Action: Calculate
Category: Unexpected behavior
Problem: When using action “calculate”, the checkbox “Include special price list” did not affect sales price lists, i.e. the special price list was always used.
Correction result: When using action “calculate”, the checkbox “Include special price list” affects both purchase and sales price lists, i.e. the special price list is used or not used according to the checkbox.
5.1.2.1 Calculation – General
RFR-016539 Correction
Framework: Calculation
Application: Product cost calculations
View: Tab “Calculation details”
Action: “Create simulation costs”, “Calculate with changed costs”
Category: Unexpected behavior
Problem:
1. No creation of simulated costs has been done so far. If toggle button “Total” is clicked total costs are displayed also for simulated costs (should be zero amounts).
2. “Create simulation costs” is clicked and after editing some simulated costs “Calculate with changed costs” is performed. Material for which no simulated costs are edited may show different values in columns “Total costs” and “Simulated values”. This is caused by different rounding procedures for both values. It may happen, if value of column “Direct cost” is an already rounded value (e.g. if material price is per 10, per 100…).
Correction result:
1. Column “Simulated values” in view “Total” shows zero values.
2. No difference due to rounding problems between columns “Total costs” and “Simulated values” for material.
5.1.2.2 Calculations
RFR-016539 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, 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.3 Cost centers
RFR-016539 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 Financials
5.1.3.1 Financials and Human Resources
RFR-016539 Extension
Framework: Financials
Application: Levy determination procedure
Category: New fields
Description: The application has been extended with the new business key field “Process”.
The new field belongs to a new ValueSet attribute with the values “Purchasing” and “Sales”.
The value is optional and an empty value has the meaning that a specified logic can be used for both frameworks.
Also the type combinations have been extended with the process.
Please note that an entry with a specified process has a higher priority than an entry without process.
Technical information:
– The class “LevyInquiryLogicDeterminationHeaderParams” has now a new parameter “LevyContext” and the “LevyInquiryLogic” considers the new “process” attribute with respect to this parameter value.
– The class “LevyInquiry” sets now the “LevyContext” value also into the used “LevyInquiryLogicDeterminationHeaderParams”.
Data update: The existing logic assignments have been migrated by an empty “process” value.
5.1.4 Inventory management
RFR-016539 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.4.1 Average annual LIFO prices
RFR-016539 Correction
Framework: Inventory Management
Application: Average Anual LIFO prices
View: n.a.
Change organization
Category: Exception
Problem: If the organization was changed and the organization valuate inventory on different level this would cause an exception.
Correction result: The organization can be changed as expected.
5.1.4.2 Identifiers
RFR-016539 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.4.3 Inventory count valuation
RFR-016539 Correction
Framework: Inventory Management
Application: Generate inventory count valuation
View: n.a.
Action: Delete and Duplicate
Category: Unexpected behavior
Problem: If an inventory count valuation was deleted and recreated with the same identification the field inventory count valuation would not be refreshed correctly.
Correction result: If the entity object is changed the field inventory count valuation will be refreshed as expected.
5.1.4.4 Inventory count
RFR-016539 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.
RFR-016539 Correction
Framework: Inventory Management
Application: Import inventory count reporting
View: n.a.
If the number of a line item is not specified the auto detection of line items is supported now.
Category: New action
Description: The identification number (Key) fields are no more required but if they are specified, they will be used. But if they are not specified within the import file the inventory count list line item (and sub line item) the report belongs to will be detected or created. The auto detection supports all kinds of line item types and changes but of course this is dependent of the count list type (e.g. item based, loading unit based, etc. ).
The import supports following behaviors:
– If the selected import mode is “create” a new line item will be created as before the extension.
– If the selected import mode is “update” the specified line item will be updated as before the extension. But if the line item identification (number) is not specified the line item and sub line item will be detected by the specified attributes (e.g. loading unit, item, identifier, storage data, etc.). Please note that these attributes must be specified to detect a line item. If a line item is detected it will be updated but a new line item will never be created in this mode (“update”).
– If the selected import mode is not set (=> default mode “update_create”) and the line item is specified it will be used to update it. But if the line item identification (number) is not specified the line item and sub line item will be detected by the specified attributes (e.g. loading unit, item, identifier, storage data, etc.). Please note that these attributes must be specified to detect a line item. If a line item is detected it will be updated. If a line item is not found it will be created as a new line item.
Data update: The data update UPDADU120324 should be executed for loading unit-based inventory count lists.
5.1.4.5 Inventory value query
RFR-016539 Correction
Framework: Inventory Management
Application: Year LIFO inquiry
View: n.a.
Change of the organization
Category: Exception
Problem: If the organization was changed and the new organization did not support the same valuation level exception could be caused using the application.
Correction result: The organization can be changed independent of its used valuation level as expected.
5.1.4.6 Picking orders
RFR-016539 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-016539 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.4.7 Receipts of goods
RFR-016539 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 is for purchasing goods receipt type only.
5.1.4.8 Reservations
RFR-016539 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.4.9 Warehouses
RFR-016539 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.5 Multi-site capability
5.1.5.1 Distribution orders
RFR-016539 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.6 Planning
RFR-016539 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 is displayed.
RFR-016539 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-016539 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 is 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 now disabled.
5.1.6.1 Material requirements planning
RFR-016539 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 not any 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 the exception does not occur anymore if there are no working days in a week or month.
RFR-016539 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.6.2 Planning – General
RFR-016539 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 the status of the relevant purchasing organization has impact.
5.1.7 Production
RFR-016539 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-016539 Correction
Framework: Production
Application: Operations
View: Operation
Action: Save
Category: Exception
Problem: When changing the name of a resource (line item) and trying to save, application was closed and an exception occurred.
Correction result: Entering a non-existing name does not lead to an exception. Once an attempt is made to save the operation itself, validation throws expected errors.
RFR-016539 Correction
Framework: Production
Application: Order maintenance
View: Table view
Action: Split or replace operation…
Category: Unexpected behavior
Problem: An 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-016539 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 found properly, so no warning is sent into logs.
RFR-016539 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.
RFR-016539 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-016539 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-016539 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-016539 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.
5.1.7.1 Product configuration
RFR-016539 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 has been lost.
Correction result:
1. In described case when nothing has been changes, 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.
5.1.7.2 Production orders
RFR-016539 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-016539 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 an 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 an exception.
Correction result: Now in both cases an error is displayed instead informing user why he cannot open chosen product cost calculation.
5.1.7.3 Resources
RFR-016539 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 error 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.7.4 Where-used list
RFR-016539 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 finishes successfully.
5.1.8 Purchasing
5.1.8.1 Puchasing – General
RFR-016539 Correction
Framework: Purchase, Sales
Application: Purchase price lists, Sales price lists
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: If the field supplier (Purchase price lists) or customer (Sales price lists) was mandatory for the current view but was not specified the validation for new lists would not validate it at save. But after save the load validation would send an error message.
Correction result: The whole validations will be done during the save step as expected.
5.1.8.2 Purchase orders
RFR-016539 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.
RFR-016539 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.
5.1.8.3 Purchase price lists
RFR-016539 Correction
Framework: Purchasing
Applications: Supplier proposals, Purchase orders
Action: Validate
Category: Unexpected behavior / Ergonomics
Problem: If the message “PUR, 540” is send this message will not be shown as expected at the price listing field – instead this message will be shown at the address fields.
Correction result: Now this message will be shown as expected.
5.1.8.4 Supplier invoices
RFR-016539 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.
RFR-016539 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-016539 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.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016539 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 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.9.2 Sales orders
RFR-016539 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.10 Storage Location Control
5.1.10.1 Inventory management server
RFR-016539 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual
Inventory posting with inter-company billing created in the time zone “GMT”
Category: Exception
Problem: The inventory posting could not be processed because of erroneous date check within the Inter-company billing logic.
Correction result: The inter-company billing validates the GMT time zone as expected.
5.1.10.2 Inventory requisitions
RFR-016539 Correction
Framework: Update
Application: UPDADV113943
View: n. a.
Execution of data update com.cisag.app.update.log.UPDADV113943
Category: Invalid data
Problem: The data update deactivated the item definitions for all fix locations. Only the picking location item definitions without a replenishment quantity should be activated.
Correction result: The data update is corrected but if it was already executed the data can only be corrected using an update statement to activate all fix location item definitions.
Technical information: If needed following UPDATE Statement can be used to activate the item definition for all fix locations. Please note that the inventory management server have to be reinitialized after correction.
UPDATE com.cisag. app.inventory.obj.PickingLocation pl
SET pl:activation=1
WHERE pl:activation=20 AND EXISTS(
SELECT loc:guid
FROM com.cisag.app.inventory.obj.StorageLocation loc
JOIN com.cisag.app. inventory.obj.StorageLocationType lt ON lt:guid=loc:type
WHERE loc:guid=pl:storageLocation AND lt:kind=5)
RFR-016539 Extension
Framework: Inventory Management, Storage Location Control
Application: Cockpit: Inventory items, cockpit: Identifiers, cockpit: Inventory orders, cockpit: Inventory orders/line items, cockpit: Inventory requisitions, cockpit: Inventory requisitions/line items, cockpit: Storage locations
View: n.a.
Action: n.a.
Category: Support batch action hooks
Description: Provide batch action hook contracts for the following cockpits: com.cisag.app.inventory.cockpit.ui.TransportOrderCockpitBase
com.cisag.app.inventory. location.cockpit.ui.TransportOrderCockpitBase
com.cisag.app.inventory.cockpit.ui. TransportOrderCockpitDetail
com.cisag.app.inventory.location.cockpit.ui. TransportOrderCockpitDetail
com.cisag.app.inventory.cockpit.ui.WarehouseOrderCockpitBase
com.cisag. app.inventory.location.cockpit.ui.WarehouseOrderCockpitBase
com.cisag.app.inventory.cockpit.ui. WarehouseOrderCockpitDetail
com.cisag.app.inventory.location.cockpit.ui. WarehouseOrderCockpitDetail
com.cisag.app.inventory.location.cockpit.ui.StorageLocationsCockpit
From now on our partners can create new batch action hooks based on the offered batch action hook contract.
5.1.10.3 Storage location reservations
RFR-016539 Correction
Framework: Storage Location Control
Application: Picking orders/Correct voucher data and reservations
View: n.a.
Generate 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.1.10.4 Storage locations
RFR-016539 Correction
Framework: Storage Location Control
Application: Cockpit: Storage locations
View: n.a.
Action: ‘Allocation’ selection
Category: Unexpected behavior
Problem: If new storage bins have been created, they cannot be selected correctly using the ‘Allocation’ selection
Correction result: New storage bins can be selected correctly using the ‘Allocation’ selection.
Data update: com.cisag.app.update.log.UPDSUP120219 should be executed.
5.2 System development
RFR-016538 Ergonomics
Update of the Polish user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016538 Correction
Framework: All
Application: All (navigation mode “Tabs”)
View: n.a.
Action: Context menus of applications
Category: Ergonomics
Problem: If the navigation mode “Tabs” is selected in the user settings, the context menus of applications do not contain the entries for the views supported by the application. Some applications, namely “Items” and “Partner” have separate views for each “role”. These views should available as items in the application’s context menu to allow to open the application directly with that view.
Correction result: Fixed.
RFR-016538 Ergonomics
Update of the EN user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016538 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 aren’t 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-016538 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-016538 Extension
Framework: Software development
Tool: wrkfd
View: n. a.
Action: n.a.
Category: New tool
Description: The tool wrkfd (WorkFileDeliveries) allows to upload multiple files into one file delivery development object.
RFR-016537 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-016537 Correction
Process: Start of application server / acquire lock
Category: Exception
Problem:
a) Upon starting, “IllegalStateException: instance isn’t created” might occur, with reference to “system session executing com.cisag.sys.kernel.locking.CisLockTable$DeadlockResponder”.
b) “ArrayIndexOutOfBoundsException: arraycopy: last destination index XX out of bounds” might (rarely) occur if a lock request can’t be granted
Correction result: No exceptions
RFR-016537 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.
5.2.1 Application server
RFR-016537 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 doesn’t 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-016537 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 Configuration
5.2.2.1 System cockpit
RFR-016537 Correction
Framework: System Management
Application: System cockpit
View: Category “Application Server”
Action: New
Category: Exception
Problem: Choosing “New” to create a new application server, and saving it (or validating) may abort the application with an exception message “java.lang.NullPointerException”
Correction result: The problem is resolved.
RFR-016537 Extension
Framework: System Management
Application: System cockpit
View: System/Performance information
Action: n.a.
Field: n.a.
Category: Ergonomics
Description: At most 5000 lines of performance information can be displayed and exported. If a query results in more lines, now a dialog window is shown instead of an informational message.
In Column “Database statement”, the statement text is shown in a tool tip, in addition to the statement ID in the column itself. Column “Statement” for the statement text remains unchanged.
The formatting of times, and some column titles in the export, have been improved.
5.2.3 Data exchange
RFR-016537 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.4 GUI
RFR-016537 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 this 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.5 Repository
5.2.5.1 Development objects
RFR-016538 Correction
Framework: Software Development
Application: Batch for mass code synchronization with GitLab
Category: Unexpected behavior
Problem: Batch job for Gitlab code synchronization did not have an option to synchronize software update.
Synchronized development tasks did not synchronize removed files.
Batch job did not have option to synchronize code to branch other than “main”.
Correction result: Batch has an option to manually synchronize software update.
Batch has an option to synchronize code to different branches.
Synchronized development tasks now correctly synchronize removed files.
RFR-016537 Correction
Framework: Software Development
Application: Batch for mass code synchronization with Gitlab
Category: Exception
Problem: Due to recent changes in gitlab while fetching files from given path, endpoint now would return 404, if path did not exist in repository instead of empty array as before the update. This resulted in exception and abrupt end of the synchronization process.
Correction result: Synchronization engine now correctly handles the new 404 response code for changed endpoint.
5.2.6 Workflow
5.2.6.1 Absences
RFR-016537 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.