| Release | Comarch ERP Enterprise 6.3 |
| Release date | 10.05.2023 |
| 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-016489 – RFR-016491
Information about the features of Comarch ERP Enterprise 6.3 (release news): · INF- 002654 Release-News: Betriebswirtschaftliche Lösungen · INF-002656 Release News: Business Solutions · INF- 002655 Release-News: Technische Lösungen · INF-002661 Release-News: Technical Solutions
System requirements: · INF-002659 Systemvoraussetzungen Comarch ERP Enterprise 6.3 · INF-002660 System Requirements Comarch ERP Enterprise 6.3
To install the support deliveries, please use the following documentation: · “Introduction: Software Logistics” (German language version) · „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.
The cumulative installation of support deliveries is described in INF-000228.
In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”. |
1 Information about support deliveries
The “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.
Note:
You need 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-Fix15.”
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-Fix15
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix14 will be upgraded to CEE630PB-Fix15.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation is provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016491 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Code design
Problem: For developers it was not possible to inherit from APSObjectManager and let the inherited class replace the standard class because the CisFactory method was called with a private constructor.
Correction result: The private constructor of APSObjectManager is now removed.
RFR-016491 Correction
Framework: com.cisag.app.general.General
Application: com.cisag.app.general.extension.ui.DatatypeMaintenance
View: n.a.
Action: Start -> fill in any Field Type and Category. A Defaults-field should appear. Now press New, and then No to discarding changes (also works with yes) -> two Default-fields
Category: Unexpected behavior
Problem: See action.
Correction result: At most one default-field is visible at any one time.
Technical information: Removed a field=null assignment. The field then gets removed from the view and created anew by existing logic
5.1.1 Base
5.1.1.1 Base – General
RFR-016491 Correction
Frameworks: Purchasing, Sales
Applications: “Purchase price lists” and “Sales price lists”
Action: Validate
Category: Unexpected behavior
Problem: In contrast to the orders applications not all expected price uoms are allowed to be used by the price definition applications.
Correction result: Now all uoms can be used as price uom for price definitions that are convertible to the item base uom.
Hint: In “Purchase price lists” also with respect to the supplier (in definitions with supplier only).
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016491 Correction
Frameworks: Purchasing, Sales
Applications: Purchase orders, Sales orders
Action: Generate purchase orders
Category: Unexpected behavior
Problem: Within “CIS620PB-Fix17 KW04/2023” an extension has been added, so that in case of “automatic contract selection” (purchasing) the generated purchase order will be saved more times with the goal to consider by the “automatic contract selection” also the added purchase order line items. By mistake also kit main details and kit components were saved before this correction directly (without kit components) so that the error message “PUR-01306” occurs (kit needs at least one kit component).
Correction result: Now a generated kit will be saved only if all kit components were considered.
Hints:
– Please note that for purchase order kit components the “automatic contract selection” is never active.
– Rebate in kind sub details (from sales order) will be converted into normal purchase order main line items
– in contrast to a purchase order kit main detail a sales order kit main detail does not support rebate in kind sub line items
RFR-016491 Correction
Class: com.cisag.app.general.order.ui. AbstractChangeDetailsDialog.DialogImpl.
Method: performAction
Problem:
At the end for the switch-cases “TAKE_SINGLE”, “TAKE_ALL” and “ButtonBar.OK” the following lines were present before this correction: …
maintenance.getDetailEditor().enterBatchMode(changedDetailsIterator, singleMode);
setVisible(false);
break;
…
If the “enterBatchMode” triggers e.g. by the line item editor a further modal dialog an exception will occur (“Can not open dialog ‘…’ if one of ancestors has the visible modal dialog ‘…’.”).
Correction result: Now the order of the code lines have been changed so that the AbstractChangeDetailsDialog will be closed before considering the changes by “enterBatchMode”: …
setVisible(false);
maintenance.getDetailEditor(). enterBatchMode(changedDetailsIterator, singleMode);
break;
…
5.1.1.3 Item characteristics
RFR-016491 Correction
Framework: Base
Application: Item characteristic classifications
Action: Save
Category: Unexpected behavior / Ergonomics
Problem: If the editor contains some assignments with multiple data the “save” action has the effect, that unused empty table rows are visible. The problem is that the user interface will be rebuild by some actions like “save” and the old editor were not removed by this step.
Correction result: Now the old editor will be removed by the “rebuild UI step” so that also these unexpected rows are not present any more.
RFR-016491 Correction
Framework: Base
Applications: Item characteristic classifications, Item-characteristics assignments
Action: Generate table schema
Category: Unexpected behavior
Problem: Even in case of a small schema extension the sub step “initIpcValues” of the action “Generate table schema” takes a lot of time.
Correction results:
1. The SELECT that was used for the sub step “initIpcValues” considers before this correction to many entries. Now the select was changed so that only the needed data will be used for the initialization.
2. In addition to that a validation of the “Item-characteristics assignments” data was changed so that it validates now only rows with required data that are either newly assigned or where the EntityExtension data was changed since the last save of the ItemPropertyCollection data.
Hints:
1. If needed you can enable the debug infos: dbgcls -class:com.cisag.app.general.log.ItemPropertyGenerationBatch
2. Please note that the “Item-characteristics assignments” maintenance uses a cache, so that EntityExtension data (item propoerty definition) changes might be considered only after a new application start.
5.1.2 Calculation
RFR-016491 Correction
Framework: Calculation
Application: Trade cost calculation
View: .n.a.
Action: Calculate…
Category: Exception
Problem: Context:
A customer has no financial accounting data. If this customer is used in a trade cost calculation an exception occurs when payment terms are retrieved from customer.
Correction result: If a customer has no financial accounting data, payment terms/ discount percent are regarded as 0%.
5.1.2.1 Calculation – General
RFR-016491 Correction
Framework: Calculation
Application: Product Cost Calculations
View: n.a.
Action: Calculate
Category: Exception
Problem: Performing “Calculate” action for “Calculation type” that has not specified purchasing organization caused exception.
Correction result: Now in described case an error will occur about missing purchasing organization for chosen “Calculation type”.
It is not possible anymore to create new “Calculation type” in application “Calculation types” without specifying purchasing organization.
Technical information: Changing field “Purchasing organization” in application “Calculation types” to mandatory field.
5.1.2.2 Calculations
RFR-016491 Correction
Framework: Calculation
Application: Product cost calculation
View: n.a.
Action: Simulate with changed costs
Category: Unexpected behavior
Problem: In application “Product cost calculation” in tab “Calculation tabs” in case there is a Product cost calculation which has two identical semifinished products in different lines, entering simulation costs for one line manually will also set the field “Simulation costs” to same value in the other line. This is correct so far.
In the next step when the action “Simulate with changed costs” is performed, the result for the 2nd line is calculated from the original value that was previously changed in step one.
As a result, the displayed input and output values for the second line are inconsistent because the output was not calculated from the changed input.
Correction result: “Simulated value” is now calculated correctly in described case which means this value is the same for line with same quantities and same semifinished products item.
5.1.3 Financials
5.1.3.1 Tax exemption
RFR-016491 Correction
Framework: Financials
Application: Tax exemptions
Action: Refresh / Validate
Category: Invalid data / Unexpected behavior
Problem: If the type “Date and amount” is used the additional domestic amounts will not be rounded any more so that in some cases the error message “GEN-05937” occurs.
Correction result: Now the additional domestic amounts will be rounded as expected.
5.1.4 Inventory management
5.1.4.1 Availability query
RFR-016491 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Calculate availability for variable set
Category: Exception
Problem: An exception caused when a variable set contains an item twice.
Correction result: Although a variable set contains an item twice the availability calculation can be done.
RFR-016491 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Check availability…
Category: Unexpected behavior
Problem: If the requested set amount was not available and one of the components had only stock but no availability data the calculation of the next available date would fail.
Correction result: The next availability date calculation for sets will consider warehouse stock as expected.
5.1.4.2 Delivery orders
RFR-016491 Correction
Framework: Inventory Management
Application: Delivery orders
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The report header of the report shipping order is sometimes printed and sometimes not.
Correction result: The problem is fixed.
5.1.4.3 Inventory count
RFR-016491 Correction
Framework: Inventory management
Application: Inventory Count
View: n.a.
Action: Creation of a permanent inventory according to inventory check cycle
Category: Unexpected behavior
Problem: The inventory cycle was always delayed by one day, so that a one-day cycle could not be specified.
Correction result: The inventory cycle is no longer delayed by one day, so that a one-day cycle can be specified.
RFR-016491 Correction
Framework: Inventory management
Application: Inventory postings
View: Posting error log
Action: Save an inventory posting with fixed reservations.
Category: Unexpected behavior
Problem: Even if nothing was changed, the inventory posting error log was mistakenly regarded as changed, so that unnecessary reservation actions were carried out, which may have led to problems.
Correction result: Change determination for inventory posting error log has been corrected so that unnecessary follow-up actions are no longer carried out when processing an inventory posting error log.
5.1.4.4 Receipts of goods
RFR-016491 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Post canceled goods receipt
Category: Invalid data / Unexpected behavior
Problem: A canceled goods receipt could not be posted after reporting all loading units for withdrawing in a transport order. The message PUR-1137 was displayed. This could happen if a receipt detail line was packed in more than one loading unit with different quantities.
Correction result: From now the canceled goods receipt will be able to be posted in that special case as expected.
Data correction: Due to the confirmation of the transport order for the canceled goods receipt, incorrect data was written to the canceled goods receipt. For this reason, the canceled GR cannot be posted even though all loading units have been confirmed to the GR zone. This correction ensures that this does not happen in future, but does not correct invalid data of already canceled goods receipt invalidated before this correction. These must be straightened manually in order to be able to post it:
– ReceiptOfGoods:putStatus must be set to “not stored”,
– ReceiptOfGoods:putNoneCount must be increased by 1,
– ReceiptOfGoodsDetail:putStatus must be set to “not stored” and
– ReceiptOfGoodsDetail:putQuantity[0] must be updated to 0 Pkg.
Then the cancel goods receipt can be posted.
5.1.4.5 Reservations
RFR-016491 Correction
Class: com.cisag.app.inventory.reservation.log. FixedReservationLogic
Method: reserveDemandCoverage(DemandData, CisQuantity[])
Description: The method does not support obligated packaging units correctly. Now they will be converted in item units for the following reservation processes.
5.1.5 Multi-site capability
5.1.5.1 Distribution orders
RFR-016491 Documentation
The following help documents (German language versions) have been updated regarding returns:
– Verteilauftragsarten
– Verteilaufträge
– Verteilaufträge: Aktionen
– Customizing: Vertrieb
5.1.6 Planning
RFR-016491 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem: In a test case where the pre-period forecast compensation mode is set to “issues only” and forecast in pre-period is lower than the demand the cropping of forecasts happened at a date later than the base date, when the forecasts exceeded the demands for the first time.
Correction result: The cropping of forecasts to not exceed the demands now only occurs at the planning base date.
RFR-016491 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem:
1. Running a planning with update mode did not update some internal cached values (quantity and date of demands) for items planned with forecasts.
2. Unnecessary new internal mappings for order positions and delivered quantities had been created during planning data updates.
The planning results had not been affected.
Correction result:
1. During planning in update mode, the internally cached values for quantity and date of demands are refreshed also for items planned with forecasts.
2. Existing internal mappings are kept and found across update runs.
The planning results are identical to the situation before the change.
RFR-016491 Correction
Framework: Planning
Application: Material requirements planning, Material requirements query
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem: A demand that was covered by an earlier forecast in the same forecast period was not reduced by the amount already covered by the forecast, leading to higher predicted resulting demands.
Correction result: Demands, forecasts, delivered quantities and resulting demands are accumulated within each forecast period day-by-day.
For each day the accumulated delivered quantities are subtracted from the accumulated forecasts and then compared to the accumulated demands.
The higher value of both is then compared to the resulting demands of the previous day.
The delta between current day and previous day is the resulting demand, which is added to the accumulated resulting demands in case it is positive.
5.1.6.1 Generate purchasing recommendations
RFR-016491 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations
View: n.a.
Action: Calculate purchasing recommendations
Category: Unexpected behavior
Problem: When calculating purchasing recommendations for an item with “Coverage time” greater than 0 for a test example in which the target date of the recommendation has a demand, the recommendation based on dynamic reorder level was too high because the demand was counted twice: First to lower the projected onhand on the target date and second to increase the dynamic reorder level for the same date. This was correct according to the examples in documentation but obviously logically wrong.
Correction result: In contradiction to documentation the dynamic reorder level demand accumulation will start one day AFTER the date it is calculated for.
That means the time covered by the dynamic reoder level will also be shifted one working day into the future.
The documentation will be updated to reflect the logically correct time ranges for dynamic reoder level calculation.
5.1.6.2 Material requirements planning
RFR-016491 Extension
Framework: Production
Application: Product configuration rules
View: Configuration characteristics
Action: Edit Field
Field/Column: Diamond Icon Long text
Category: New action
Description: Configuration characteristics of type “long text” now open a text editor by using the diamond icon in the configuration rules.
5.1.6.3 Material requirements query
RFR-016491 Correction
Framework: Planning
Application: Material requirements planning, Material requirements query
View: n.a.
Action: n.a.
Category: Exception
Problem: Importing demand forecasts of same units as packaging unit that is set to “Conversion only” in item base view and performing action “Transfer planning data and execute planning” in application “Material requirements planning” set to plan this item and forecasts, caused exception when trying to see forecast data in application “Material requirements query” for that item.
Adding additional item that has forecasts imported in unit that is set to “Conversion only to the item that has also forecast imported, caused the same exception when trying to see forecast data for additional item in application “Material requirements query”.
Additional item’s forecasts was incorrectly calculated and in result forecasts for that items was lower than expected or even negative.
Correction result: Exception does not occur anymore and demand forecasts are displayed correctly only in item units or packaging units that are set to “Inventory”. Calculated forecasts for additional item are now correct.
Technical information: Performing planning in application “Material requirement planning” does not keep packaging units that are set to “Conversion only” anymore, but only their converted quantities during planning of demand forecasts.
5.1.7 Production
RFR-016491 Correction
Framework: Production
Application: Where-used list
View: Operation
Action: n.a.
Category: Exception
Problem: When entering operation of type cross-site into field “Operation” and press enter or perform action “Refresh” an exception occurred.
Correction result: Entering a cross-site operation into field “Operation” shows list of usage of this operation now.
RFR-016491 Correction
Framework: Production
Application: Bills of material
View: Bill of material
Action: Duplicate
Category: Exception
Problem: Trying to duplicate bill of material and leave field “Description” empty caused exception.
Correction result: Duplicating bill of material and leave field “Description” empty causes error which informs that description must be specified.
RFR-016491 Correction
Framework: Production
Application: Where-used list
View: Item, External manufacturing item
Action: n.a.
Category: Exception
Problem: When entering external manufacturing item in view “Item” or “External manufacturing item” and refresh an exception occurred.
Same problem occurred when action “Replace detail line items” was performed and in displayed window “External item” will be entered for search.
Correction result: An exception does not occur anymore and entering external item for any of these two views correctly displays a list of external operations where it is used.
Same result for window displayed after performing action “Replace detail line items”.
RFR-016491 Extension
Class: com.cisag.app.production.order.log. ProductionOrderBookingImportController
Description: Logic for standard import for new BOs
Class: com.cisag.app.production.order.log. ProductionOrderBookingExportController
Description: Logic for standard export for new Bos.
5.1.7.1 Production orders
RFR-016491 Correction
Framework: Production
Application: Order maintenance
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: Context: With picking, over delivery of picking is allowed.
Add a material to a production order of an item of type identifier. Specify also an identifier. This identifier must not be not completely available at production warehouse, but must be available at issue warehouse.
After saving production order, change identifier of this material detail. Choose an identifier which is completely available at production warehouse so that no quantity has to be picked at issue warehouse.
Result after saving:
1. Reservation / availability is set at production warehouse -> OK
2. Reservation / availability at issue warehouse with original set identifier is not removed -> Error
Correction result: If in above described scenario, identifier is changed so that reservation / availability is complete at production warehouse and no quantity has to be picked at issue warehouse then
result after saving is as follows:
1. Reservation / availability is set at production warehouse -> OK
2. Reservation / availability at issue warehouse with original set identifier is removed, no reservations /availability at issue warehouse – > OK
RFR-016491 Correction
Framework: Production
Application: n.a.
View: n.a.
Action: n.a.
Unexpected behavior
Correction result: A reported possible error relates technical to a not used function. This function has been deprecated and will be removed.
Technical information: Related function: public void refreshDetailCountStatus(ProductionOrder po, ProductionOrderDetail pod, boolean add) in class com.cisag.app.production.order.log.OrderStatusLogic.
5.1.8 Purchasing
5.1.8.1 Purchase order confirmations
RFR-016491 Correction
Framework: Purchasing
Application: Purchase order confirmations
Action: Duplicate detail
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the release 6.2 the functionality “duplicate/split confirmation line item” does not consider the highest purchase order line number. So, an error message occurs if the purchase order line number is already present.
Correction result: Now the behavior is again as in the release 6.2.
RFR-016491 Correction
Framework: Purchasing
Applications: Purchase orders, Supplier confirmations
Action: Complete confirmation
Category: Unexpected behavior
Problem: If a purchase order line item belongs to a sales order line item the field “Reference” is maintained by the sales order line item. If a supplier confirmation line item contains a different “Reference” value the supplier confirmation cannot be completed if the functionality “Change order line item” is used (e.g. needed for other changes).
Correction result: Purchase orders: If a purchase order line item belongs to a sales order line item the value of the “Reference” attribute will be ignored now if it is specified as source value (here from confirmation).
Please note that within the supplier confirmation line items the “Reference” value stays also in this case relevant for the “change present ?” logic.
This is needed because the comparison result is saved within the attribute “com.cisag.app.purchasing. obj.SupplierConfirmationDetail:dataChanged”.
5.1.8.2 Supplier invoices
RFR-016491 Correction
Framework: Purchasing
Application: Supplier invoices
Actions: “Automatically insert line items and assign to receipt / order line items” and “Create self billing invoice”
Category: Invalid data / Unexpected behavior
Problem:
1. If a kit component of an order sub line item has an item with parallel units (e.g. “kg” and “m”) and these units are different from the kit line item base quantity (e.g. “Stk”) and the order sub line item uses for the kit component not the base uom (e.g. the second item unit “m” – e.g. “2 m”) the invoice sib line item (kit component) quantity will be set to “0 kg” instead of “2 m”. Because of the correct booking validations such an invoice can not be booked.
2. The “Create self billing invoice” logic as optional sub step of the “receipt of goods” booking action uses as invoice line item quantity always the base quantity.
Correction result:
1. Now also in this case the invoice sub line item (ki component) quantity will be set to the expected value.
Please note that now for normal details and kit components (but not for “rebate in kind” details) the quantity within the receipt/order line item “total quantity” uom will be used; before this correction always the item base uom was used. If the relevant open invoice quantity uom differs from the receipt/order line item “total quantity” uom – the uom of the open quantity will be used.
2. Now the “Create self billing invoice” logic uses the quantity of the order assignment for the invoice line item quantity.
RFR-016491 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Line item validation
Category: Unexpected behavior
Problem: In case of kit items the kit structure of the invoice line items and the assigned order line items needs to be the same. For the comparison the invoice order assignments of the sub line items (kit components) will be sorted by the relevant order line items. By mistake this sorting will be performed by the full order line item String and not by the order line item level data (“type code”, “header number”, “main detail number” and “sub detail number”). So, for example the full sub line item number “TTT-HHHH-5-5” will be sorted after “TTT-HHHH-5-10”. As result the error message “PUR-08721” will be send.
Correction result: Now the sorting will be performed as expected. So, for correct structures the error message “PUR-08721” will not be send any more.
RFR-016491 Correction
Framework: Purchasing
Application: Supplier invoices
Actions: Order assignment validation, Self billing
Category: Invalid data / Unexpected behavior
Problem: A supplier invoice and all assigned purchase orders need the same currency. Before this correction this was considered only by the order assignment dialog. But wrong data could be created in the following two cases: 1. In case of import supplier invoices can be created and booked with a different currency ==> error.
2. The “self billing generator” does not consider orders with different currencies – so assigned orders with different currencies were used for the same invoice; as further problem the currency as specified by the partner master data was used and not the currency of the assigned order(s).
Correction result:
1. Now a new validation has been added so that also an import with a different currency is not possible.
2. The “self billing generator” uses now the purchase order currencies and uses different currencies also as “Splitting criterion”.
Hint: If needed you can cancel wrong supplier invoices and recreate them.
5.1.9 Sales
5.1.9.1 Assortments
RFR-016491 Correction
Framework: Sales
Application: Import data
Filter: com.cisag.app.sales.obj.AssortmentListing
Action: Import
Category: Exception
Problem: Running the import application in the background throwed an exception.
Correction result: From now running the import application in the background will work as expected.
5.1.10 Storage Location Control
5.1.10.1 “Assign storage locations” dialog
RFR-016491 Correction
Framework: Inventory management
Application: Receipt of goods
View: n.a.
Action: Assign storage locations
Category: Unexpected behavior
Problem: The storage location type item purity restrictions were not checked.
Correction result: The storage location type item purity restrictions will be checked as expected and if necessary, warnings will be sent.
5.1.10.2 Inventory management server
RFR-016491 Correction
Framework: Storage Location Control
Application: Inventory requisition
View: Manual Stock Movement
Action: Generate inventory orders…
Category: Exception
Problem: If an inventory order type is used that support cross docking and that will not assign serial numbers an exception could be caused.
Correction result: Independent of the setting “Assign serial numbers” the cross-docking strategies can be used as expected.
5.1.10.3 Inventory orders
RFR-016491 Correction
Framework: Inventory management
Application: Inventory orders
Action: Complete without reporting
Category: Unexpected behavior
Problem: If an inventory order was completed without reporting and the return transfer inventory order was blocked, the original order was also blocked and could no longer be released.
Correction result: The original order is no longer blocked if the inventory order could not be completed without reporting.
RFR-016491 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Generate inventory order to put a loading unit
Category: Exception
Problem: If a storage location was selected that does not support the storage unit of the loading unit and it has open outgoing processes an exception could be caused.
Correction result: Storage locations which do not support the loading unit to be put will be ignored as expected.
5.1.10.4 Inventory requisitions
RFR-016491 Correction
Framework: Inventory Managment
Application: Inventory requisitions
View: Withdrawal for picking order
Action: New
Category: Ergonomics
Problem: The message text of the error message was not clear enough.
Correction result: The error message text is now more precisive.
5.2 System development
RFR-016489 Correction
Framework: All
Application: Application frame
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: In the CDS design, especially when using the tab navigation mode, the context menus on applications (and tabs), have less entries than in the former design. Although, that this change is intended in order to make the context menus more clear and easier to use, there should be an option to reach the less common menu entries if needed.
Correction result: The “Shift” modifier key can be now used to open an extended context menu.
RFR-016489 Correction
Framework: System Management
Action: Accessing NLS data while in uncommitted transaction
Category: Unexpected behavior
Problem: If you change the NLS data of an object, put the object and then re-read the object while the transaction still open, i.e. is not yet committed,
the transaction cache was ignored. The unchanged data was read again.
Correction result: When reading NLS Data for an object while within a transaction, also the eventually changed data from the transaction cache is considered.
RFR-016490 Ergonomics
Update of the PL language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
5.2.1 Application server
RFR-016489 Correction
Framework: System management
Application: Change journal query
View: n.a.
Action: Update
Category: Exception
Problem: Journal references to object instances that are no longer existing can cause a NullpointerException.
Correction result: No exception.
5.2.1.1 Autorizations
RFR-016489 Ergonomics
Process: Login / accessing a knowledge store folder
Category: Ergonomics
Problem:
1. A login can take a long time if the user is assigned to a large number of authorization roles (e.g. 40 seconds for 100 roles).
2. Accessing a knowledge store folder can take a long time or fail with a timeout if it contains a large number of files.
Correction result: Performance improved in both cases.
5.2.1.2 JobControl
RFR-016489 Correction
Process: job control
Category: Exception
Problem: If 3 applications are started in a row and each one terminates with a runtime exception, the diagnostic exception “IllegalStateException: Possible recursion in TaskList detected” is thrown, which is misleading.
Correction result: No exception.
Technical information: Please submit request including logfile if this occurs.
5.2.1.3 Logs
RFR-016489 Correction
Framework: System Management
Logging of messages
Category: Unexpected behavior
Problem: Messages, especially exception messages, may be logged twice in the message logs.
Correction result: Messages that are sent once by an application, are logged at most once. This is independent from message manager logging settings (Tool dbgmsgmgr).
5.2.1.4 Mail
RFR-016489 Correction
Framework: System Management
Application: E-Mail server
View: n.a.
Action: Send test e-mail
Category: Exception
Problem: By clicking the Action “Send test e-mail”, “java.lang.IllegalArgumentException” will be thrown, if Email server has no valid entity.
Correction result: Action “Send test e-mail” is enabled only if Email server has a valid entity.
5.2.2 Data exchange
RFR-016489 Correction
Framework: System Management
Application: Import data
View: “n.a.
Action: Import data
Category: Exception
Problem: Different language setting between Filter and Import file.
Example: Filter with Language Setting “Multilingual”, but import file “Monolongual”.
Correction result: There is error message, if Language setting of filter is different from import file.
5.2.3 GUI
RFR-016489 Extension
Framework: All
Application: UI applications
View: value help (date chooser and calculator)
Action: n.a.
Category: Ergonomics
Problem: The value help popup windows for number and date fields (“Calculator” and “Data chooser”) were not correctly displayed.
Correction result: Size, background and borders have been corrected and also adapted to the CDS design as well as to different densities and font sizes.
5.2.4 Web server
RFR-016489 Correction
Framework: System management
Application: web services
View: n.a.
Action: n.a.
Category: Exception
Problem: Using %HEX encoded strings in path components of web service URIs could result in an exception in the webserver.
Correction result: Fixed.
RFR-016489 Extension
Framework: System management
Application: Web server
View: n.a.
Action: n.a.
Category: Security
Description: The defaults for some HTTP headers have been modified in order to make the default configuration more secure (only allow what is needed in the usual case).
The following headers/features are affected:
– CORS (Access-Control-Allow-Origin): Disabled by default now. Can be re-enabled by a property if needed (see below)
– Session cookie: Now with “SameSite=Strict” as default, can be changed to “Lax” or “None” by property if needed (see below)
– CSP (Content-Security-Policy): Now with frame-ancestors ‘self”. Can be customized by a property (see below)
Technical information: If cross-site access (CORS) is needed, the following property can be used to specify a (comma separated) list of hosts, that should have access (see specification of “Access-Control-Allow-Origin” header)
com.cisag.sys.kernel.webserver.cors. allowedOrigins=
Note: Wildcards (‘*’) are genrally allowed (e.g. for specfying all hosts of a domain), but do not use “*” to “allow all”
In the case, that the “SameSite=Strict” setting for session cookies should be changed to “Lax” or even “None”, the following property cab be used: com.cisag.sys.kernel. webserver..cookie.sameSite=Lax|None
If content of CEE have to be embeded in other site (e.g. via IFRAME), the URIs of these sites have to be added using this property: com.cisag.sys.kernel.webserver. http.headers.csp.frame-ancestors=
See specification of “Content-Security-Policy: frame-ancestors”
Note: Specifying this property with an empty value, the header will be suppressed at all.
5.2.5 Workflow
5.2.5.1 Activity definitions
RFR-016489 Correction
Framework: Workflow management
Application: Cockpit: Activity definitions
View: Default
Action: Refresh (load activity with specified status)
Category: Correction
Problem: After activating/deactivating Activity Definitions, statuses of Activity Definitions with category individual activities were not updated when refreshing data or reopen application. Filtering by statuses was also applied to old state of Activity Definitions.
Correction result: After activating/deactivating Activity Definitions, statuses in cockpit are updated automatically. Filtering by statuses works after refreshing data.