| Release | Comarch ERP Enterprise 6.3 |
| Release date | 08.11.2024 |
| 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-016518 – RFR-016520
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-000200 “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 the 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 deliveries 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 to have appropriate authorizations to download files. Please refer to the application documentation of “Support deliveries 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-Fix19.”
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-Fix19
With the delivered software updates, the CEE630PB-Fix18 of the Comarch ERP Enterprise system version will be upgraded to CEE630PB-Fix19.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system is in 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 documentation “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.
3.2 Cumulative installation of support deliveries
The 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 installation 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 “Data updates query” application, you must schedule the following data updates, for any point in time.
4.2.1 UPDBUG028863
Deletion of control data for sales quotations and orders that no longer exist
The value of the quantity to be picked for a production order line item is corrected if (1) the order line item is of the material type and has not yet been completed (2) the order line item has been picked, but not completely (3) the order line item, which quantity still to pick is 0 (4) There is no picking in progress for the order line item (5) The order type involved does not allow
overpicking. The picking status is set to “partially picked” in the corrected cases. The counters for partial picking and complete picking of the associated production order are updated. The data update can be called up multiple times.
4.2.2 UPDBUG029064
Deletion of the virtual/dynamic attributes for the partner’s validation
This update application removes the virtual/dynamic attributes, that were chosen for the partner’s validation in Customizing. The virtual/dynamic attributes would cause an exception in the partner’s validation logic.
5 Contained changes and extensions
5.1 Application development
RFR-016520 Ergonomics
The 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-016520 Correction
Framework: Production
Application: Production issue
View: n.a.
Action: Post
Category: Unexpected behavior
Problem: The production order has a material item with identifier (batch) and an identifier is specified. The context is non-picking.
If a production issue is done with a part of target quantity, two availabilities are created — one with the identifier specified, and one without. This is wrong.
Correction result: In the above-described situation the production issue of material with a part of target quantity works as expected. After issuing is done, an availability with the specified identifier and quantity still to be reported does exist.
RFR-016520 Correction
New entry in com.cisag.app.general.OrderType: Name of entry: SEM_MCS_CUSTOMER_PROPOSAL
ID: 2039
Description (de): Vertriebskanal-Verkaufsangebot
Description (en): Sales channel sales quotation
Description (pl): Oferta sprzedaży kanału sprzedaży
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016520 Correction
Application: All applications that are using the “OrderDisplayField” functionality
Category: Unexpected behavior / Ergonomics
Problem: The standard field that is used for displaying the order or order line item identification was configured with the maximum length of 30 characters. However, the length wasn’t enough as the system requires 36 characters. As a result, in some cases, a field error message occurred.
Correction result: Now, the length is defined with 36 characters, so that the field does not show such an error message any more.
RFR-016520 Correction
Frameworks: Purchasing, Sales
Applications: Proposals, Orders
Action: Duplicate sub line item; Create new sub line item
Category: Exception / Invalid data / Unexpected behavior
Problems:
1. If the main proposal line item is a variable kit line item and this line item was completed manually, new kit component sub line items have a status that is not completed.
2. If the main order line item is a variable kit line item and this line item was completed (completed delivery in case of “Not zero total quantity” or completed invoice in case of “Zero total quantity”), new kit component sub line items have a status that is not completed. In some cases, the exception occurs as well.
Correction result:
1. Now, in this case, new kit components are also completed manually.
2. Now, in this case, adding new kit components is not supported any more (same as in case of canceled kit main line items).
5.1.1.2 Items
RFR-016520 Correction
Framework: General
Application: Items
View: n.a.
Action: Create, Create from Template
Category: Unexpected behavior/Performance
Problem:
1. The application tried to load “Warning” instances even if they didn’t exist.
2. The hook method com.cisag.app.general.item.hook.log.ItemDependentHook.load(V) was called if no data wasn’t loaded, because the item was not persistent.
3. The validation for the attribute “Plan inventoried packaging units” in the item planning data used a query, that couldn’t use any index.
Correction result:
1. From now, the application will try to load “Warning” instances only if they really exist.
2. From now the hook method com.cisag.app.general.item.hook.log.ItemDependentHook. load(V) will be called only if dependent data really can be found. The item has to be persistent for that. Otherwise, no dependent data could exist.
3. The query used by the validation for the attribute “Plan inventoried packaging units” in the item planning data is modified. From now, the existing index will be usable.
RFR-016520 Correction
Class: com.cisag.app.general.item.log. ItemAccountingEntity
Method: retrieveItemAccountingData(byte[])
Description: From now this method will call the method com.cisag.app.general.item.log.ItemAccountingEntity. rebuildItemAccountingData(ItemAccountingData, List) with a list of mutable of ItemAccountingData instances.
RFR-016520 Correction
Framework: General
Application: Items
View: n.a.
Action: Create/Create from template
Category: Unexpected behavior, Performance
Problem: The application tried to load the item accounting data from the database, that couldn’t exist on the database because the base item itself wasn’t persistent.
Correction result: From now, the application will try to load data only if the base item already exists.
5.1.1.3 Partners
RFR-016520 Correction
Framework: Base
Application: Partners
View: Base
Action: n.a.
Category: Unexpected behavior
Problem:
1. The tab “General” was not enabled if a pseudo partner was created or loaded.
2. The validation required a name for a pseudo partner.
Correction result:
1. From now, the tab “General” will be enabled even if a pseudo partner was created or loaded.
2. From now, the validation will not require a name for a pseudo partner.
RFR-016520 Correction
Framework: General
Application: Customizing
Function: com.cisag.app.general.Partners
Rubric: Duplicates validation
Category: Unexpected behavior
Problem: The virtual/dynamic attributes, that was chosen for the partner’s double validation in Customizing would cause an exception in partner’s validation logic because the partner’s validation is based on the database tables only.
Correction result: From now, the virtual/dynamic attributes will be filtered in the partner’s validation section of the Customizing application, so the user won’t be able to select them.
Data update: com.cisag.app.update.log.UPDBUG029064
5.1.2 Inventory management
5.1.2.1 Identifiers
RFR-016520 Correction
Framework: Inventory management
Application: Identifiers
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The bottom fold-out area of the “Weights and dimensions for 1st item unit” section was visible in every tab.
Correction result: The bottom fold-out area of the “Weights and dimensions for 1st item unit” section is now only visible in the ‘General’ tab.
5.1.2.2 Picking orders
RFR-016520 Correction
Framework: Inventory
Application: Reorganize picking orders
View: n.a.
Action: Reorganize
Category: Exception
Problem: An exception occurred in special cases using PickingOrderDataObject instances
Correction result: From now, using PickingOrderDataObject instances will work as expected.
RFR-016520 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Generate picking orders and output picking slips
Category: Invalid data
Problem: Preliminaries: The production order uses a production order type with “Overdelivery of picking allowed” = false; the material line items must be picked.
For the production order, a picking order is generated. The picking order is completed with less quantities than is suggested to report.
Result: The open picking quantity is set to zero (which is wrong) and the picking status is set to “completed” (also wrong).
Correction result: After the completion of picking order in the above-described manner
– “Open picking quantity” of the associated production order detail is set to quantity still to be picked (order maintenace, table view -> planning data);
– “Picking status” of the associated production order detail is set to “partially picked”.
Data update: A data update UPDBUG028863 must be performed. Data update corrects “Open picking quantity” (order maintenace, table view -> planning data) and “Picking status” of material line items
5.1.2.3 Reservations
RFR-016520 Correction
Framework: Inventory Management
Application: Automatic reservations (Batch)
View: n.a.
Action: Automatic start of the automatic reservations for new warehouse stock
Category: Unexpected behavior
Problem: If the reservation scope was only set to “Inventory” (Customizing setting), the new warehouse stock would not be reserved automatically even if it should be (Customizing setting: “New Inventory”).
Correction result: If the Customizing setting: “New Inventory” is activated, the new warehouse stock will be reserved automatically as expected.
5.1.3 Multi-site
5.1.3.1 Distribution orders
RFR-016520 Correction
Frameworks: Purchasing, Sales
Applications: Distribution recommendations, Distribution orders
Actions: Distribution order line item – apply defaults, Distribution recommendations: default logic and UI, Generation: Distribution recommendations ==> Distribution orders
Category: Unexpected behavior / Ergonomics
Problem:
1. Distribution order: The “Target availability date” was determined by the wrong calendar (it was a calendar of “Sales organization” instead of “Delivery customer”).
2. Distribution recommendations: The order of the date fields within the user interface and the date value refreshments were not as expected.
3. Distribution recommendations => Distribution orders: The date values were not always set as defined into the distribution order line item.
Correction result:
1. Distribution order: The “Target availability date” is determined now by the calendar of the “Delivery customer”. Hint: Refreshment triggered as before by a change of “Delivery date” or “Transition time goods receipt”.
2. Distribution recommendations: The “Planned shipping date” is now in the first row (row of “Issuing organization”) and “Delivery date” is now in the second row. Also, the refreshment has been changed, so that manual changes of the maintained date fields will not be overridden by the refreshment logic.
3. Distribution recommendations => Distribution orders: The date values are set now into the distribution order line item as defined by the relevant distribution recommendation.
5.1.4 Planning
RFR-016520 Correction
Framework: Purchasing
Application: Calculate distribution recommendations
View: n.a.
Action: Calculate distribution recommendations
Category: Unexpected behavior
Problem:
1. Field “Purchasing scheduler” was ignored during calculation of distribution recommendation.
2. When option “Use execution date” was chosen for field “Setting via date” then the “Offset” field was always ignored and its default value was used (which is 0).
Correction result:
1. Now, this field is used properly and it is not ignored anymore if user filled it.
2. Now, the “Offset” field is properly used and uses value that user entered.
RFR-016520 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning
Category: Unexpected behavior
Problem:
1. During the data transfer to planning, some data could not be loaded properly. If it occurred for the entire type of data (e.g. for transfer items), an error was displayed in logs with the type ERROR, indicating that transfer of that type was not successful. However, the transfer of the remaining data continues and the planning is executed. Due to that, the planning results could be wrongly calculated (some data are missing).
2. Some errors mentioned in the previous point was not even displayed in logs.
Correction result:
1. Now, this kind of errors are set to fatal in log file, so when user sees at least one fatal error in logs, he should not believe in the planning results.
2. All errors regarding the transfer that failed for the entire type of data are now visible in logs.
5.1.4.1 Material requirements planning
RFR-016520 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning execution actions
Category: Exception
Problem: During the material planning, when the scheduling is trying to reserve a resource for a large time range (e.g. when the resource is reserved very long because of a large number of POs), or small time range and lots of shifts, a NegativeArraySizeException is thrown. Then, the planning skips this secondary demand analysis.
A similar problem could occur for the 24/7 resources being reserved for multiple years.
Correction result: Now, the resource scheduling and reservation logic correctly handles longer time ranges.
Technical information: Incompatible change: The constructors of com.cisag.app.production.scheduling. log.ResourceAvailability were changed. They only require a Guid and serialized data respectively state array now. Other values are read directly from the deserialized states/states array. RA.persistent is always false unless the data comes from serialized states. RA.persistent is handled by the class itself, see RA.setPersistent() to override.
Incompatible change: The protected field ResourceAvailability. states is now private and must be accessed via getStates() or setStates()
Incompatible change: The protected field ResourceAvailability.stateCount was removed and replaced by the method getStateCount(). Now every function concerned with state-array-length uses ints instead of shorts.
Incompatible change: The protected fields ResourceAvailability.from and until were removed and replaced by the methods getFrom() and getUntil() or getFromDate() and getUntilDate(). The values are directly computed from the underlying states array.
Furthermore, a new version to serialize states into the DB was introduced. It uses ints instead of shorts for state-array-length (and state.reservations.length).
All old versions can still be read from database.
The default of the SystemProperty “com.cisag.app.production. scheduling.log.ResourceLogicImpl_SchedulingTimeHorizon” was changed to 20.
5.1.5 Production
RFR-016520 Correction
Framework: Production
Application: Import data, Production orders
View: n.a.
Action: Import data
Category: Exception
Problem: While importing a new production order with operations (with Guids for details), a new production order is created, but operations and resources are empty. Then, performing any action on that imported production order caused an exception.
Correction result: Now, if a production order with the details’ Guids is imported successfully, operations and resources are not empty and performing the actions on such a production order doesn’t cause an exception anymore.
RFR-016520 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations (via workflow)
View: n.a.
Action: Start process
Category: Exception
Problem: The batch application “Purchasing/distribution recommendation generation” calculates purchasing recommendation when called by the application “Calculate purchasing recommendations”. It calculates distribution recommendations if called by application “Calculate distribution recommendations”.
This batch application should also calculate recommendations (purchasing or distribution) when called within a workflow management.
Most of the selection fields shown by “Calculate purchasing recommendations” or “Calculate distribution recommendations” are not properly transferred to the batch application by workflow management. Hence, the workflow process failed.
Correction result: Selection fields are properly transfered to the batch application “Purchasing/distribution recommendation generation” by a proper activity definition. The workflow process can calculate recommendation depending on the selections.
Technical Information: The “Load” parameters of application “com.cisag.app.purchasing.log. ReorderCalculationNew” (development object) have been adapted to better fit workflow requirements.
RFR-016520 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Dispatch, Dispatch and release, Recalculate due date and quantity, Midpoint rescheduling
Category: Unexpected behavior
Problem: When a resource has a constraint to another resource, this constraint was ignored during scheduling and rescheduling.
The option “Predecessor exists” was ignored for resources as well.
Correction result: The constraints of resources to other resources are not ignored during scheduling and rescheduling.
The option “Predecessor exists” is not ignored for resources any more.
RFR-016520 Correction
Framework: Production
Application: Product configuration rules, Items, Sales orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When the user selects a step in the step column in the “Steps” list in the product configuration rule dialog, and this causes a focus command to another step, the “Steps” list was not correctly updated with the newly focused step.
This caused certain interactions, like switching tabs to show the initially selected step, not the newly focused step.
Another interaction was with a message-queue open, the next click on a step in the “Steps” list would select the step that was focused after the last click, not the step that was clicked right now.
Correction result: Selecting steps and focus instructions correctly work together.
RFR-016520 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: Post production issues
Category: Unexpected behavior
Problem: The application “Production issues” crashes with an IllegalArgumentException, if a second user session has deleted the underlying production order just shortly before, the post of the production issue is being executed.
Correction result: The application does not crash any more. Before the post update, it is checked if the production order is still available. If not, the message GEN-5574 (Voucher type/header XY or at least one of the voucher line items no longer exists.) will be shown.
RFR-016520 Correction
Framework: Production
Application: Product configuration rules
View: Steps, Configuration characteristics, Condition lists, Conditions and actions
Action: Duplicate
Category: Exception
Problem: The user performs the Duplicate action for “Product configuration rule” on any existing rule. Without saving, the user switches to a different view.
After pressing the Save button in a new open view, the exception occurred.
Correction result: The exception in the above-described situation does not occur anymore.
RFR-016520 Correction
Framework: Production
Application: Resources
View: n. a.
Action: Validate, Save
Category: Unexpected behavior
Problem:
After switching the field “Valuation of gaps as interruption” to the value “Reservable with time interruption”, the field “Interruption-free reservation duration” is set to read-only, but after performing actions “Validate” or “Save” the field became editable again.
Correction result: Now, after validating or saving, the field stay read-only, so the below-described sentence is always true now: When field “Valuation of gaps as interruption” is set to “Reservable with time interruption”, the field “Interruption-free reservation duration” is read-only.
RFR-016520 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: New operation reservation
Category: Unexpected behavior
Problem:
1. While manually adding an operation to a production order, the units of the target processing times of all resources are changed to the unit of the target processing time of the primary resource, but the amounts are kept unchanged. This converts 5 minutes into 5 hours.
2. While manually adding an operation to a production order, a target processing time of zero for a resource was replaced by the target processing time of the primary resource.
3. Changing the target processing time of an operation position changes the target processing time of resources proportionally. This is done by converting the target processing time of resources into the unit of the target processing time of the operation first.
Correction result:
1. Units specified in the “Operations” application are kept in the described case (so there is no conversion happening, neither amount nor unit is changed). This behavior is consistent with the creation of operation positions through the “Dispatch” action.
2. It keeps target processing time of zero. This behavior is consistent with the creation of operation positions through the “Dispatch” action.
3. The target processing time units of resources are not converted to target processing time units of operation when changing operation processing time. Their amounts are still recalculated proportionally.
5.1.5.1 Bills of material
RFR-016520 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release
Category: Unexpected behavior
Problem: The bill of material with two details for the same item. One of them has field “Resolve item” set to “Resolve”, another one to “Do not resolve”.
After multiple level dispatching, this bill of material in “Production orders” both details were resolved.
Correction result: Now, the details set to “Do not resolve” in the above-described situation are not resolved.
5.1.5.2 Product configuration
RFR-016520 Correction
Framework: Production
Application: Product configuration rules, Items, Sales orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When a product configuration rule contains a configuration characteristic of type “long text”, this configuration characteristic cannot be set to the result of a formula when executing the configuration rule.
Correction result: The configuration characteristic can be set correctly to the result of the formula. This will set the plain text only and only set the text in the default language.
RFR-016520 Correction
Framework: Production
Application: Product configuration rules, Items, Production Orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When a formula would show an image from a non-default workspace (e.g. instead of FILE1), an error is shown, even if the image exists.
Correction result: The image is correctly displayed even when it comes from a non-default workspace.
5.1.5.3 Production – General
RFR-016520 Correction
Framework: Production
Application: Order maintenance
View: Table view -> Column “External operation status”
Action: Reschedule …
Category: Unexpected behavior
Problem: An external operation in the production order has been already completed. Now, rescheduling is performed for this production order with the increase of quantity. The result: Status of the external operation is not adjusted. The status should be “Partial …”. See table column “External operation status” of the production order.
Also, if the external operation status is “Partial…” and a rescheduling decreases quantity so that this status should change into “Completed…”, this is not the case.
Correction result: “External operation status” is adjusted when rescheduling with increasing/decreasing properly to “Partial…”/”Completed..”.
RFR-016520 Correction
Framework: Production, Calculation
Application: Cockpit: Production Items
View: Cockpit: Production Items
Action: n.a.
Category: Unexpected behavior
Problem: When the Production Methods are disabled in Customizing, then in applications “Cockpit: Production Items” (both in Production and Calculation frameworks) the context menu for column Item cannot be opened. Jumping by CTRL+click to the Item application was also impossible for that column.
Correction result: The context menu can be opened and jumping by CTRL+click is also possible now.
5.1.5.4 Production cockpit
RFR-016520 Correction
Framework: Production
Application: Cockpit: Production orders
View: Standard
Action: Open application
Category: Unexpected behavior
Problem: The preselection for the “Status” field was (All).
Correction result: The preselection for the “Status” field is now (Multiple selection), with the status “Completed” and “Reorganization started” de-selected.
5.1.5.5 Production orders
RFR-016520 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release, Entering line item manually
Category: Unexpected behavior
Problem: The scheduling base date (field “Dispatching date” in the tab “Dispatching”) was set incorrectly and it was filled automatically every time it was empty, even when no line items were added to the production order.
Correction result: Now, the field is automatically filled when it is empty and at least one line has been added using dispatching action or detail editor.
Automatic filling sets scheduling base date to its basic date depends on the scheduling category.
If the scheduling category is set to type “Back”, a basic date is the latest date (in this case, this date is not set to finite the current date is used instead).
If the type of this field is “Forward”, a basic date is the earliest start date.
When the user sets a date that exceeds the basic date, it will be automatically changed forward (for the “Forward” scheduling category) or backward (for the “Back” scheduling category).
5.1.5.6 Routings
RFR-016520 Correction
Framework: Production
Application: Bills of material, Routings, Operations, Resource lists
View: Bill of material, Routing, Operation
Action: Validate
Category: Exception
Problem:
1. Adding the organization which is not an Inventory Logistics organization to the field “Inventory management organization” caused exception and crashed the application.
2. In the “Routings” application, entering not existing organization into the field “Inventory management organization” caused exception and crashed the application.
Correction result:
1. An error is displayed to inform that only Inventory Logistics organizations can be used.
2. An error is displayed to inform about entering non existing organization
5.1.6 Purchasing
5.1.6.1 Purchase order confirmations
RFR-016520 Extension
Framework: Purchasing
Application: Purchase order confirmations
Action: Import
Category: Extension
Description: The import filter for the business object “com.cisag.app.purchasing.obj.SupplierConfirmation” has been extended so that the attribute “orderChange” is now supported for the header and the main line items.
5.1.6.2 Purchase orders
RFR-016520 Correction
Framework: Purchasing
Application: Purchase orders
Action: Complete billing line items
Category: Exception
Problem: An exception occurs during the attempt to complete the invoice of some kit line items.
Correction result: Now, the exception does not occur any more.
5.1.7 Sales
5.1.7.1 Customer invoices
RFR-016520 Correction
Framework: Sales
Application: Customer invoices
Action: Generate
Category: Invalid data / Unexpected behavior
Problem: If a sales order was generated by a customer return, the invoice generation considers the same sales order line item multiple times sometimes.
Correction result: Now, the error does not occur any more.
Hint: In case of an error, you have to cancel manually the additional invoices.
RFR-016520 Correction
Framework: Sales
Application: Customer invoice
Action: Generate
Category: Invalid data / Unexpected behavior
Problem: In case of retail calculation and the pricing value “Gross”, the detail discounts values with own accounts are booked by mistake with taxes.
Correction result: Now, this error does not occur any more.
5.1.7.2 Sales – General
RFR-016520 Correction
Framework: Sales
Application: Pro-forma invoices query, Customer invoices query
Action: Delete/Reorganize and refresh/display within the application
Category: Exception
Problem: If a “Pro-forma invoice” or “Customer invoice” is displayed in one session and the same instance is deleted or reorganized by another session or the user, an exception occurs during the attempt to determine the current “Retail calculation” value within the line item list.
Correction result: Now, the exception does not occur any more. In addition to that, the data is disabled now if the application was opened with the empty data, no data was found by load or after a successful delete.
5.1.7.3 Sales orders
RFR-016520 Correction
Framework: Sales
Application: Sales orders, Customer invoices
Action: Generate cash invoice
Category: Exception/Unexpected behavior
Problem: In case of zero total quantity of the sales order line items, the process “Cash invoice” does not work as expected if the sales order line item is configured as “Direct delivery”; also an UnsupportedOperationException can occur.
Correction result: Now, this case works as expected.
5.1.8 Storage Location Control
5.1.8.1 Inventory requisitions
RFR-016520 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders
Category: Exception
Problem: If an item quantity should be transferred but the specified unit of measure is not an inventory unit for the item, an exception could be caused during the regeneration of the target inventory order.
Correction result: Now, the quantity calculation is corrected and the target inventory order can be regenerated as expected.
5.1.8.2 Storage strategies
RFR-016520 Correction
Framework: Storage Location Control
Application: n.a.
View: n.a.
Consideration of the “Time limit for bulk additions to existing stock” during the inventory order creation for withdrawal
Category: Unexpected behavior
Problem: During the automatic warehouse stock detection for creation of a withdrawal inventory orders, the lime limit for bulk additions was not always detected correctly.
Correction result: The settings for “Bulk additions to existing stock” will be detected from the current valid strategy as expected.
5.2 System development
RFR-016518 Correction
Framework: System Management
Application: Simplified Data Export, Simplified Data Import
View: n.a.
Action: Validate
Category: Ergonomics
Problem: If you load a simplified export controller into the application and then decide to explicitly validate it, then an error message occurs, even though everything is okay.
Correction result: The explicit validation now works normally.
RFR-016518 Correction
Framework: All
Application: All cockpits
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: In the cockpits, the function of com.cisag.pgm.datatype.DataDescriptionFilter does not work.
Correction result: The interface com.cisag.pgm.datatype.DataDescriptionFilter works as expected.
RFR-016518 Correction
Framework: Software development
Application: Job maintenance
View: n.a.
Action: Checking
Category: Ergonomics
Problem: While checking a copyright string with an outdated address, it is set into Java class.
Correction result: The correct address is now set into the Java class.
RFR-016518 Correction
Framework: Software development
Application: Development objects
View: External object
Action: Resolver for foreign keys
Category: Unexpected behavior
Problem: It is possible to use the same name for the foreign key resolvers. While doing so, the logic lost context and mixed resolvers are leading to errors.
Furthermore, it was not possible to register an external object in a controller if you use more than one level of the foreign key resolvers for the used key.
Correction result: A validation prevents the usage of the same name for the foreign key resolvers. More complex registration is possible now.
RFR-016519 Ergonomics
The update of the Polish language interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016519 Correction
Framework: Software development
Application: Development objects
View: External object
Action: Resolve for foreign keys
Category: Unexpected behavior
Problem: It is possible to use the same name for the foreign key resolvers. While doing so, the logic lost context and mixed resolvers are leading to errors.
Furthermore, it was not possible to register an external object in a controller if you use more than one level of the foreign key resolvers for the used key.
Correction result: A validation prevents the usage of the same name for the foreign key resolvers. More complex registration is now possible.
5.2.1 Configuration
5.2.1.1 System cockpit
RFR-016518 Correction
Process: System configuration
Category: Exception
Problem: A higher number of connected OLTP databases or database languages might cause “RuntimeException: timeout while acquiring a connection for database XX” upon application server start.
Correction result: The default value of database connections raised from 5 to 10 (if not set by system property com.cisag.sys.kernel.ConfigurationConnectionTransactionalConnections)
5.2.2 Customizable cockpits
RFR-016518 Correction
Framework: All
Application: Customizable cockpits
View: n.a.
Action: Select and organize views
Category: Unexpected behavior
Problem: When switching between two views with different sorting criteria, the data was automatically updated (database query). Depending on the type and complexity of the new filter and sorting criteria, usable indices in the database and the amount of data, it could take a very long time to perform the update.
Correction result: There is no longer an automatic update when switching between views. Instead, the results list is automatically deleted if the sort and filter criteria of the new view differ from those last used. In this context, the handling of database timeouts has also been changed. Previously, the timeout detection was deactivated during the automatic update due to a change in the sorting criteria, now the timeout detection is active for every update — even when changing sorting criteria via dialog or clicking on the column headers.
RFR-016518 Correction
Framework: All
Application: Customizable cockpits
View: n.a.
Action: Specify search fields
Category: Unexpected behavior
Problem: If the “Specify search fields” dialog was used to modify the visible search fields, the values of all search fields were removed on “OK”.
Correction result: Fixed.
5.2.3 Data exchange
RFR-016518 Correction
Framework: System management
Application: Export data
View: n.a.
Action: Export data
Category: Exception
Problem: Export of the modification journal fails with “IllegalArgumentException: Object not defined! com.cisag.sys.tools. modificationjournal.log.ModificationJournalExportController$Entity”
Correction result: Successful export.
RFR-016518 Correction
Framework: System Management
Application: Import data
Importing business entity data with supplement business objects.
Category: Unexpected behavior
Problem: Verifications in BIS imports implemented by interface com.cisag.pgm.bi.Verifier were not performed for the supplement business objects. The string length verifications were affected such as e.g. invalid value set entry verification.
Correction result: The above-mentioned verifications are performed for the supplement business objects.
5.2.4 GUI
RFR-016518 Correction
Framework: All
Application: Applications with HTMLEditor
View: n.a.
Action: Paste images from clipboard
Category: Unexpected behavior
Problem: If an image was pasted from clipboard to the HTML editor, the image is lost after saving or after switching to “text only” mode and back.
Correction result: Fixed.
Technical information: Browsers are embedding pasted images using “data:” URLs, but the fitter rules of the HTML editor were blocking “data” URLs in general. Now, data URLs for some image format (PNG, JPG, GIF) are accepted by the filter.
RFR-016518 Extension
Display message in active modal dialog: Dialog message is only displayed if there is at least one recipient for a message in the modal dialog.
5.2.5 Kernel
5.2.5.1 Locking / Caching
RFR-016518 Correction
Process: Lock requests
Category: Invalid data
Problem: After a lock request using CisApplicationManagerWrapper.acquireLock(..) fails with a timeout, CisApplicationManagerWrapper.getLockInformation(String) doesn’t provide user information on the current lock holder.
Correction result: Valid user information.
RFR-016518 Extension
Process: Lock requests
Category: Performance
Problem: A lock request that can’t be granted due to a cyclic deadlock (one or more other requesters are waiting for a lock owned by the current requester, but have been granted the requested lock) will be canceled only after the set timeout has elapsed.
Correction result: The request is canceled immediately. The additional information provided can help to identify all involved requesters and locks.
Technical information: Instead of sys.kernel.locking.CisLockException, the new exceptions CisLockException, CisLockTimeoutException or CisLockDeadlockException (all in pgm.appserver) are thrown and can be caught.
RFR-016519 Extension
Process: Lock requests
Category: Performance
Problem: A lock request that can’t be granted due to a cyclic deadlock (one or more other requesters are waiting for a lock owned by the current requester, but have been granted the requested lock) will be canceled only after the set timeout has elapsed.
Correction result: The request is canceled immediately. The additional information provided can help to identify all involved requesters and locks.
Technical information: Instead of sys.kernel.locking.CisLockException, the new exceptions CisLockException, CisLockTimeoutException or CisLockDeadlockException (all in pgm.appserver) are thrown and can be caught.
5.2.6 Software update
RFR-016518 Correction
Framework: System management
Application: Export apps
View: n.a.
Action: Generate add-on versions
Category: Exception
Problem: Generate fails with NullpointerException if there is a dependent friendly app declared for the current app, but does not exist in the current system (i.e. there is no development object for the dependent app).
Correction result: The exception replaced by error message (REP-03823).
RFR-016519 Correction
Framework: System management
Application: Export apps
View: n.a.
Action: Generate add-on versions
Category: Exception
Problem: Generate fails with NullpointerException if there is a dependent friendly app declared for the current app, but does not exist in the current system (i.e. there is no development object for the dependent app).
Correction result: Exception replaced by error message (REP-03823).
5.2.7 System – General
RFR-016518 Correction
Framework: System Management
Tool: ExportSystem/ImportSystem
Category: Exception
Problem: If there are no views to be exported but the option to zip at the end is used, then it may happen that the empty views directory is ignored.
This leads to an exception when using such an exported file as the source for tool ImportSystem.
Furthermore, while creating connections on an SQL server, some misleading outputs were created, because a default value was changed.
Correction result: If there is no views directory, a simple message is shown.
The parameter for the SQL server connection is properly set.
5.2.8 Web server
RFR-016518 Extension
Framework: System-Management
Application: Webserver
View: n.a.
Action: n.a.
Category: New feature
Description: The internal (Jetyy based) web server of Comarch ERP Enterprise now supports the PROXY prototol, used by several load balancers, e.g. HAProxy.
Technical information: To enable the PROXY protocol support in Comarch ERP Enterprise, use the following property: com.cisag.sys.kernel.webserver.acceptProxy=true
5.2.9 Workflow Management
5.2.9.1 Workflow roles
RFR-016518 Correction
Framework: Workflow Management
Application: Workflow Roles
View: n.a.
Action: any action (in CoolBar or on exit) on “Workflow Roles” fresh run.
Category: unexpected behaviour.
Problem: The application “Workflow Roles” enters edit/new mode and returns warning after any action in application.
Correction result: Behaves as it should.
Technical information: Changes are applied to load() and setMode() methods.