| Release | Comarch ERP Enterprise 6.4 |
| Release date | 28.06.2024 |
| 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-016500 – RFR-016502
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 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 “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-Fix01”.
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-Fix01
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB will be upgraded to CEE640PB-Fix01.
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 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
No batch data updates have to be carried out.
5.1 Application development
RFR-016502 Correction
Framework: Inventory
Application: Cockpit: delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: Some validations weren’t done if the action was excecuted from the
Cockpit: delivery orders.
Correction result: From now, the same validations will be done, as when excecuting this action from maintenance application.
RFR-016502 Correction
Framework: Production
Application: Cockpit: Production orders/material line items,Cockpit: Production orders/work line items
View: Cockpit: Production orders/material line items,Cockpit: Production orders/work line items
Field: Line item output
Category: Unexpected behavior
Problem: Default view of the field “Line item output” shows all 5 possible choices instead of “All” text.
Changing value of this field and then perform action “New” did not resets value of this field to default one.
Correction result: If all choices are set for “Line item output” field it displayes “All” text in every case.
Performing action “New” always changing value of this field to default value of chosen view.
RFR-016502 Correction
Framework: Production
Application: Production issue
View: n.a.
Action: Post
Category: Unexpected behavior
Problem: A production order has a material item of type identifier (batch) and a identifier is specified. Context is non-picking.
If a production issue is done with part of target quantity two availabilities are created, one with identifier specified, one without. This is wrong.
Correction result: In above described situation a production issue of material with part of target quantity works as expected. After issuing is done an availability with specified identifier and quantity still to be reported does exist.
RFR-016502 Correction
Class: com.cisag.app.general.item.log.ItemsImpl
Method: n.a.
Description: Several methods, that consumes GUID-Arrays as input parameters changed the value of the given input parameters unintentionally. From now, that won’t happen anymore.
RFR-016502 Correction
Framework: System Management
Application: System cockpit
View: n.a.
Action: Deactivate User
Category: Unexpected behavior
Problem: When deactivating users in System cockpit with option “Mark Partner for deletion”, it may happen that partners are delete-marked although they could not have been delete-marked in application parters, because they are still in use.
Correction result: Problem is resolved.
RFR-016502 Correction
Framework: Base
Application: Items
View: n.a.
Action: Mark for deletion
Category: Unexpected behavior
Problem: The application went into ‘changed’-mode after marking the item completely as deleted. The removing of the deletion mark was not possible without saving the item first.
Correction result: From now the application will work as expected.
Technical information: All data of the item will get a deletion mark in all views, including the item accounting data, when the item base is marked as deleted. Furthermore, if item accounting data of an organization is marked for deletion, the sales data status, purchasing data status and inventory data status have to be set to ‘on hold’. Unfortunately, that didn’t happen because of a programming error.
Data update: UPDBUG028772
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016502 Correction
Framework: Purchasing
Application: Purchase orders
Action: changes by OrderStatusLogic
Category: Potential problem
Problem: The internal method “com.cisag.app.purchasing.order.log.OrderEntity.statusLogicProcessPerformed(byte[] header, byte[][] details)”
is used by the OrderStatusLogic. This method saves the data by the normal logic (OrderEntity) but does not consider unconfirmed warnings or errors – so wrong data could be the result, if the save functionality fails.
Correction result:
1.) As of now warnings will be confirmed here automatically and in case of errors, an exception will be thrown.
The change will be performed now with the new entity mode value “com.cisag.app.purchasing.order.log.OrderEntity.MODE_STATUS_LOGIC”.
2.) In addition to that the interface new interface “com.cisag.app.general.order.model. EntityModeRetriever” has been added with the method “public int getEntityMode()”
An implementation of this method has been added to the class “com.cisag.app.general.order.log.EntityDataObject”.
The interface EntityModeRetriever is supported now also by the following data view interfaces:
– com.cisag.app.financials.debtorcredit.model.DebtorCreditInterface
– com.cisag.app.general.orderarchive.model. DocumentReorganizationDataInterface
– com.cisag.app.inventory.delivery.model. ShippingOrderInterface
– com.cisag.app.inventory.location.requisition.model. WarehouseOrderInterface
– com.cisag.app.inventory.picking.model.PickingOrderInterface
– com.cisag.app.inventory.recall.model.ProductRecallInterface
– com.cisag.app.inventory.receipt.model. ReceiptOfGoodsInterface
– com.cisag.app.multiorg.order.model.DistributionOrderInterface
– com.cisag.app.multiorg.request.model.DistributionRequestInterface
– com.cisag.app.production.model. ProductionOrderInterface
– com.cisag.app.purchasing.confirmation.model. SupplierConfirmationInterface
– com.cisag.app.purchasing.contract.model.PurchaseContractInterface
– com.cisag.app.purchasing.invoice.model.SupplierInvoiceInterface
– com.cisag.app.purchasing.order.model. PurchaseOrderInterface
– com.cisag.app.purchasing.proposal.model.SupplierProposalInterface
– com. cisag.app.purchasing.request.model.RequestForProposalInterface
– com.cisag.app.sales.contract.model. SalesContractInterface
– com.cisag.app.sales.customerreturn.model.CustomerReturnInterface
– com. cisag.app.sales.order.model.SalesOrderInterface
– com.cisag.app.sales.prepayment.model. PrepaymentRequestInterface
– com.cisag.app.sales.proposal.model.CustomerProposalInterface
– com. cisag.app.sales.rapid.model.SalesRapidDocumentInterface
– com.cisag.app.sales.request.model. RequestForProposalInterface
So now you can consider he “current entity mode” value also within additional validations that belong to these order types.
RFR-016502 Correction
Application: Order applications with an action based on the class “com.cisag.app.general.order.ui.DetailSelectionList”
Category: Invalid data / Unexpected behavior
Problem: If an order application provides an action that is based on the class “com. cisag.app.general.order.ui.DetailSelectionList” (e.g. sales order action “Cancel line items”) and the selection list shows more than 100 line items the selected line items will not be used in every case for the action.
Correction result: Now the selection will be considered as expected.
5.1.1.2 Items
RFR-016502 Correction
Framework: Sales, Purchasing
Application: All applications which call the class “com.cisag.app.general.item.log.ItemsImpl”
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: There was a problem with the use of customer classification-specific article data.
Correction result: Applications that call this method work correctly
Technical information: in the class “com.cisag.app.general.item.log.ItemsImpl” (Version 40.0:6.3.0) an error was found in the method “retrieveCustomerClassificationItems(byte[], byte[][], byte[])”
Within the last loop, the “cache.load” method is passed “customer” as the second parameter, the correct parameter should be “items[i]”.
RFR-016502 Correction
Framework: Base
Application: Items
View: Inventory management
Action: Validate
Category: Unexpected behavior
Problem: For storage area specific data, the application didn’t accept the setting ‘According to the item’ in the field ‘Put-away strategy setting’ and ‘Withdrawal strategy setting’.
Correction result: From now the setting ‘According to the item’ will be valid in the field ‘Put-away strategy setting’ and ‘Withdrawal strategy setting’ for storage area specific data.
5.1.2 Document Management
RFR-016502 Correction
Framework: Document management
Application: All applications with Create document action, Documents
View: n.a.
Action: Create document, Insert reference, Create notes dialog
Category: Unexpected behavior
Problem: Customizing setting “Document reference type for documents” and preferred document reference type from “Document types” application were not used when creation documents with references.
Always Customizing setting “Document reference type for notes” was used.
Correction result: Currently logic takes preferred document reference type from “Document types” application. If there is no preferred reference type logic takes it from Customizing according to document kind (Document / Note).
If the setting “Document reference type for documents” is empty logic would use “Document reference type for notes” for compatibility reasons.
5.1.2.1 Documents
RFR-016502 Correction
Framework: Document management
Application: All applications having Create document action, Documents
View: n.a.
Action: Create document, Create note dialog
Category: Exception
Problem: Exception occurred when calling “Create document” action from context, which does not have Document management customizing function activated.
Correction result: Exception does not occur when action “Create document” is being called from context without activated Document management function.
5.1.3 Inventory management
5.1.3.1 Availability query
RFR-016502 Correction
Framework: Inventory Management
Application: Availability inquiries
View: Identifiers
Action: Change view
Category: Ergonomics
Problem: An error message displayed within the identifier view was overtaken into another view at view change.
Correction result: After a view is changed the displayed error messages will be removed as expected.
5.1.3.2 Delivery orders
RFR-016502 Correction
Framework: Inventory Management
Application: Delivery orders
View: n.a.
Action: Complete delivery order from distribution order
Category: Exception
Problem: In the resulting posting, the price is only determined at a later point in time, so that no price was set at the time the posting was checked, which led to an exception.
Correction result: The posting checks have been made more robust so that a missing price does not lead to an exception.
5.1.3.3 Inventory count
RFR-016502 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Report loading units
Category: Unexpected behavior
Problem: If the same loading unit was reported twice the report would be denied although the report would be allowed. Such a report will be allowed if one time the loading unit is reported as found and the other loading unit line item is reported as not found.
Correction result: The correct reporting of the same loading unit will be accepted as expected.
5.1.3.4 Inventory postings
RFR-016502 Correction
Framework: Inventory management
Application: All applications that can save packing or unpacking postings, e.g. the application “Edit logistic units”.
View: n.a.
Action: Pack/Unpack
Category: Unexpected behavior
Problem: When unpacking or packing, demand coverage data was created for the receipt posting, so that reservations could be made against it, although in reality no new warehouse stock was added. As a result, an over-reservation may have been created when processing the posting.
Correction result: No more demand coverage data is generated for such receipt postings.
5.1.3.5 Inventory query
RFR-016502 Correction
Framework: Inventory Management
Application: Edit logistic units (e.g. from Cockpit: Inventories)
View: n.a.
Action: Edit logistic units
Category: Ergonomics
Problem: In seldom cases the the sorting of the item warehouse logistic unit was not correct.
Correction result: The item warehouse logistic unit is always lowest inventory unit as expected.
5.1.3.6 Loads
RFR-016502 Correction
Framework: Inventory
Application: Delivery orders, picking orders, shipping loads and loading units
View: n.a.
Action: n.a.
Category: Exception
Problem: In the listed applications above it is possible to change the calculated weights and volumes to self measured values. This caused conversion exceptions in later process steps if the user used differing units of measure than the system units of measure for weight and volume.
Correction result: From now it will be no problem to use any unit of measure that is defined for the measure types “weight” and “volume” in the listed applications above. All calculation steps will take care of it and will convert to units of measure that will fit to the actual calculation step.
5.1.3.7 Picking orders
RFR-016502 Correction
Framework: Inventory
Application: Import data
Filter: Picking order transactions
Action: Import
Category: Unexpected behavior
Problem: The assignment only of serial numbers without inventory management was not possible via import without increasing the reported quantity. This increasing resulted in an error message that the detail line will be overdelivered.
Correction result: From now the user is able to set the reported quantity in the import file to 0, so the serial number assignment only will be done.
RFR-016502 Correction
Framework: Inventory Management, Purchasing, Sales.
Application: Purchase orders, delivery orders, picking orders, down payment requests, customer contracts, purchasing RFQs, supplier contracts.
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The report header of the following reports is sometimes printed and sometimes not: Delivery dun, dispatch advice, picking order, pickup, prepayment request, sales contract,
return of goods slip, request for proposal, purchase order correspondence, purchase contract, proforma invoice, shipping order
Correction result: The problem is fixed
RFR-016502 Correction
Framework: Inventory
Application: Cockpit: Sales orders
View: n.a.
Action: Create picking order
Category: Unexpected behavior
Problem: The picking order creation application used the date from the date field of the start dialog as order date, although the user had enabled the option “grouping by shipping date” and the date field was not enabled.
Correction result: From now, the date from the date filed is not used as order date by the picking order creation application if the option “grouping by shipping date” is enabled and the date field is not enabled. The actual date at excecuting time will be used instead as expected.
5.1.3.8 Receipts of goods
RFR-016502 Correction
Framework: Inventory
Application: Cockpit: Goods receipts /detail lines
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: In special cases, an error message is displayed if the field “Open net invoice amount” is contained in the set of table columns.
Correction result: From now, the application will never display any error message if the field “Open net invoice amount” is contained in the set of table columns.
RFR-016502 Correction
Framework: Inventory
Application: Goods Receipt
View: Return of Goods
Action: Cancel
Category: Invalid data / Unexpected behavior
Problem: In special cases a canceled return of goods receipt triggered an internal invoicing allthough the original return of goods receipt didn’t. That was caused by a faulty assignment of the owner in the canceled return of goods receipt.
Correction result: From now the assignment of the owner in the canceled return of goods receipt will work as expected.
5.1.3.9 Reservations
RFR-016502 Correction
Framework: Inventory Management
Application (Batch): Update demand data
View: n.a.
Action: Create and reserve serial number demand data
Category: Unexpected behavior
Problem: If a serial number was specified within an order (e.g. sales order) it would only be tried to reserve when the reservation strength had to be stock bounded (e.g. delivery orders).
Correction result: If a serial number is specified within an order (e.g. sales order) it is tried to be reserved as expected.
RFR-016502 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If an inventory order should transport goods from a simple warehouse to the receiving zone (specified target) of a structured warehouse the inventory order could not be generated.
Correction result: Goods can be transported from a simple warehouse to the receiving zone (specified target) of a structured warehouse as expected.
RFR-016502 Correction
Framework: Inventory Management
Application: Inventory requisition
View: Manual stock movement
Generate inventory order to pick an item with additional item units
Category: Exception
Problem: If an item to pick had several item units and the first unit was not the warehouse unit and the pick was reserved within a simple warehouse en exception could be caused at the ineventory order creating.
Correction result: The inventory order can be created as expected.
5.1.4 Production
RFR-016502 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Reschedule
Category: Unexpected behavior
Problem: If errors occurred while rescheduling production orders message PRD 1995 shows wrong number of successfully rescheduled production orders
Correction result: If errors occurred while rescheduling production orders message PRD 1995 shows correct number of successfully rescheduled production orders
RFR-016502 Correction
Framework: Production
Application: Routing, Bill of Resources
View: Structure view –> Quantity Overview
Action: Toggle button Quantity overview
Category: Exception
Problem: A routing has at least one cross site operation. If switching to “Structure view” and further to “Quantity overview” via Toggle button “Quantity overview”, an exception occurs.
A bill of resource uses a routing which has at least one cross site operation. If switching to “Structure view” and further to “Quantity overview” via Toggle button “Quantity overview” an exception occurs.
This happens because the view “Quantity overview” does not regard detail type “Cross site operation”.
Correction result: In above mentioned scenarios displaying the view “Quantity overview” works as expected. No exception occurs.
RFR-016502 Correction
Framework: Production
Application: Calculate production inventory values
View: n.a.
Action: Calculation of values for inventories that are in the production process
Category: Exception
Problem: When above action was taken for a production order that contains an equipment item as a production order detail, an exception was thrown.
Correction result: When above action is taken for a production order that contains an equipment item as a production order detail, no exception is thrown.
5.1.4.1 Bills of material
RFR-016502 Correction
Framework: Production
Application: ProductionPlan
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Icons for formulas/constraints in ProductionPlanDetails were cropped.
Correction result: The icons are now displayed in full, adjusted to size of column/line.
5.1.4.2 Production – General
RFR-016502 Correction
Framework: Production
Application: Cockpit: Production items
View: n.a.
Action: Open empty
Category: Unexpected behavior
Problem: If Cockpit: Production items is opened empty in selection field “Item” a value “OBH-S101” is defaulted. This value is also defaulted when changing to view “Extended”.
Correction result: If Cockpit: Production items is opened empty, selection field “Item” is empty. It stays empty when changing to view “Extended”.
5.1.4.3 Production orders
RFR-016502 Correction
Framework: Production
Application: Order maintenance
View: n.a.
Action: Recalculate due date and quantity
Category: Unexpected bahavior
Problem: A production order at a target site in a cross site process is rescheduled. If assigned distribution order for transporting back the refined product is missing a error is output. This error has wrong number (PRD 2756 instead of PRD 2757)
Correction result: In above described context the correct error message PRD 2757 is output.
5.1.5 Purchasing
5.1.5.1 Bonus agreements
RFR-016502 Correction
Framework: System Management
Application: Import data
View: n.a.
Action: Import of purchase item bonus classification
Category: Unexpected behavior
Problem: The import of sales item bonus classification, purchase item bonus classification and supplier quotation classification 4 could not detect the organzational unit correctly.
Correction result: The import of sales item bonus classification, purchase item bonus classification and supplier quotation classification 4 will detect the organzational unit as expected.
5.1.5.2 Purchase orders
RFR-016502 Correction
Applications: Order applications with “Find and add line items” dialog.
Action: “Find and add line items”
Category: Exception
Problem: If the search was executed and at least one entry is selected and at least one selection field value was changed to an invalid value before accepting the result, an exception occurs during the “Accept” (all or single) functionality.
Correction result: Now, one or more error message will be send and the dialog stays open without executing the “Accept” functionality, so that the exception does not occur anymore.
RFR-016502 Extension
Framework: Purchasing
Application: Supplier invoices
View: Supplier invoice without voucher reference
Action: Apply line item defaults
Category: New functionality
Description: In analogy to Purchase orders, Supplier invoices with the type “Supplier invoice without voucher reference” determine now the pseudo item description with respect to the current supplier and item.
Hint: Please note that for all other invoice types the functionality was not changed.
5.1.6 Sales
5.1.6.1 Assortments
RFR-016502 Correction
Framework: Sales
Application: Assortment lists
View: n.a.
Action: Update
Category: Exception
Problem: After changing the view of the application, when the user wants to create a new assortment list, an exception occurred because of an invalid key if he didn’t press the ‘Create’-button.
Correction result: From now the excption won’t occure in that case. A new valid primary key will be created automatically as expected.
5.1.6.2 Customer returns
RFR-016502 Correction
Framework: Sales
Application: Customer returns
Actions: “Generate or change credit note orders” and “Generate or change replacement delivery orders”
Category: Invalid data / Unexpected behavior
Problem: Since 6.1 no order references will be created between an original and a created target order (“Return credit note” or “Return replacement order”).
Up from this change in 6.1, by mistake, existing target orders were not found anymore by a further execution of the actions “Generate or change credit note orders” and “Generate or change replacement delivery orders” (e.g. after multiple receipts or after adding some further customer return line items). As a result for the same original order multiple target orders might be present.
Correction result: Now the already present target orders will be considered and used again as expected.
Hints:
– As before, the existing orders will be used only if they match to the current sales order type that belongs to the current action (“Generate or change credit note orders” or “Generate or change replacement delivery orders”).
– As before existing target orders with a deletion (reorganization) marker will be skipped.
– If multiple relevant orders were found (e.g. because of this error), the order with the last creation timestamp will be used as target order.
RFR-016502 Ergonomics
Framework: Sales
Application: Customer returns
Action: Create
Category: Ergonomics
Problem: The “create” validation checks if the customer return type value “Retail calculation” matches to the property “Consumer” of the orderer as defined within the partner accounting data for the financials organisation of the sales organization.
If this check fails, the error message “SAL, 08332” or the error message “SAL, 08333” will be send – but these messages belong to sales order types and not to customer return types.
Correction result: Now the new messages “SAL, 8969” and “SAL, 8970” will be used instead of the messages “SAL, 08332” and “SAL, 08333”.
5.1.6.3 Sales orders
RFR-016502 Correction
Framework: Sales
Application: Sales orders
Category: Unexpected behavior / Ergonomics
Problem: By mistake and in contrast to 6.3, the “Standard” layout does not contain the “delivery terms location” field after “delivery terms” field within the header ui and line item editor.
Correction result: Now, the “Standard” contains the “delivery terms location” again as within the release 6.3.
RFR-016502 Extension
Framework: Purchasing, Sales
Application: Cockpit: Purchase prices, Cockpit: Sales prices
View: n.a.
Action: (German descriptions) Beschaffungspreise Löschkennzeichen setzen…, Vertriebspreise Löschkennzeichen setzen…
Category: New action
Description: The new actions offer the possibility to mark the selected prices as deleted and so far, as no more usable.
5.1.7 Storage Location Control
RFR-016502 Correction
Class: com.cisag.app.inventory.obj. StorageLocationOnhand
Method: getPutDeadline()
Description: Attribute is now marked as deprected because it was not used since long time ago.
In addition to that the method com.cisag.app.inventory. location.cache.data.OnhandContext#getUnitLoad() is replaced by getUnitLoadNumbers() because since CEE 6.4 it is possible to store e.g. several loading units into a simple warehouse zone.
5.1.7.1 Inventory management server
RFR-016502 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual inventory postings
Action: Save
Category: Unexpected behavior
Problem: If the used posting key is without “quantity transaction”, the specified item identifier will not be validated.
Correction result: If an item identifier is specified, it will be checked whether it is existing as expected.
5.1.7.2 Inventory orders
RFR-016502 Correction
Framework: Storage location control
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Invalid data
Problem: If serial numbers without inventories should be reported for a picking order and they are already stored within the shipping zone, an error message will be displayed and the inventory movement data will be incorrect.
Correction result: Serial numbers without inventories can be reported as expected.
Data update: No new data update application is needed. If this seldom constellation does happen, the existing application “Correct voucher data and reservations” can be used to correct the incorrect item data within the shipping zone.
RFR-016502 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: Manual inventory movement
Action: Delete already created inventory order
Category: Exception
Problem: If the conversion values of the item units were changed the deletion of an already created inventory order could cause an exception.
Correction result: The deletion of the inventory order can be done without any exception as expected.
RFR-016502 Correction
Framework: Inventory Management
Application: Inventory orders
View: “n.a.”
Action: Unpack loading unit
Category: Invalid data
Problem: A selected loading unit proposal for a serial number could not be unpacked.
Correction result: A selected loading unit proposal for a serial number can now be unpacked.
5.1.7.3 Lademittel
RFR-016502 Correction
Framework: Storage location control
Application: n.a.
View: n.a.
Action: Calculation of the capacity of a prescribed storage unit and an inventory packaging for validations
Category: Unexpected behavior
Problem: Internal calculation of the capacity e.g. for validations of line items was not correct.
Correction result: The calculation will now be done as expected.
5.1.7.4 Storage locations
RFR-016502 Correction
Framework: Storage location control
Application: Storage locations
View: n.a.
Action: Import storage locations although the inventory management server is running
Category: Unexpected behavior
Problem: At the moment, it is not allowed to import storage location changes when the inventory management server is running.
Correction result: It is still not allowed to delete a storage location when the inventory management server is running. But all other supported updates can be done although the inventory management server is running. As expected, the import process uses now the same validations as the application.
5.2 Infrastructure
5.2.1 Beratung
RFR-016502 Correction
Framework: Various
Application: Various
View: n.a.
Action: n.a.
Category: API extension
Description: The API class “com.cisag.app.general. extension.log.Extensions” for “Other fields” programming support was extended to facilitate long texts.
5.3 System development
RFR-016501 Correction
Framework: System Management
Application: Report output jobs
View: n.a.
Action: Schedule report output job
Category: Unexpected behavior and Exception
Problem:
– An exception will be thrown, if open empty application
– The Pop up submit dialog with the wrong title.
Correction result:
– Schedule the report output job will be disabled if open empty application.
– The Pop up submit dialog with the right title.
RFR-016501 Documentation
The help document “Systemvoraussetzungen” has been updated.
5.3.1 Application server
5.3.1.1 Authorizations
RFR-016500 Correction
Process: Manipulation of authorization roles
Category: Unexpected behavior
Problem: Changes made to any authorization role aren’t effective until the application server is restarted, not even for new logins.
Correction result: Changes take effect without restart.
5.3.1.2 Chat
RFR-016501 Extension
Framework: System Management
Application: AI assistent “ChatERP”
View: n.a.
Action: n.a.
Category: New application (Dockable View)
Description: As of now, you can use the ChatERP virtual assistant to answer your questions about the system you are using.
You can enable ChatERP in the customizing.
Actually it is only available in combination with the CDS theme.
For more information see:
https://help.comarch.com/cee/index.php/article-categories/chaterp/ [EN]
https://hilfe.comarch.de/cee/index.php/ht_kb_category/chaterp/ [DE]
https://pomoc.comarch.pl/cee/index.php/ht_kb_category/chaterp/ [PL]
https://aide.comarch.fr/cee/ht_kb_category/chaterp/ [FR]
5.3.2 Configuration
5.3.2.1 System cockpit
RFR-016500 Correction
Framework: System Management
Application: System cockpit
View: System
Action: “Open empty” in the navigator for the System cockpit
Category: Exception
Problem: If the system cockpit is open, and the tab “Sessions” is displayed for a system, and the user selects “Open empty”, the system cockpit may close with an exception message “java.lang. IllegalStateException: System guid missing in state.”.
Correction result: The System cockpit remains open without an exception.
Framework: System Management
Application: System cockpit
View: User Group
Action: “Update the table’s content based on the search criteria”
Category: Exception
Problem: If the user field for a member is empty because it is being edited, then selecting the action “Update the table’s content based on the search criteria” results in an exception message “java.lang.NullPointerException”.
Correction result: The problem is resolved.
5.3.3 Searches
RFR-016500 Correction
Framework: various
Application: Cockpits
View: Zoom mode
Action: Export objects according to search criteria
Category: Exception
Problem: The export might yield “RuntimeException: Undefined column ” or “IllegalArgumentException: Column does not exist” while the zoom mode is active.
Correction result: The actions “Export objects according to search criteria” and “Copy hyperlink with search criteria” are disabled in zoom mode.
5.3.4 System – General
RFR-016500 Correction
Framework: System Management
Application: Import Data
View: n.a.
Action: Import data
Category: Unexpected behavior
Problem: There is endless loop at the import file Json format, if in the import file, Entity value is different from to imported object (entity)
Example: {
“semiramis”: {
“entity”: “com.cisag.app.general.obj. CommonItemSearch”,
…
“Item”: [{…
…}]
….}
is wrong.
Correct: {
“semiramis”: {
“entity”: “com.cisag.app.general.obj.Item”,
…
“Item”: [{…
…}]
….}
Correction result: Error message will be sent as an information, that import file is not correct.