| Release | Comarch ERP Enterprise 6.3 |
| Release date | 21.06.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-016497 – RFR-016499
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-Fix16.”
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-Fix16
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix15 will be upgraded to CEE630PB-Fix16.
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
With the “Query data updates” application, you must schedule the following data updates, for any point in time.
4.2.1 UPDBUG028772
Update items data status after setting a deletion mark to accounting data
When the item base is marked as deleted, all data of the item will get a deletion mark in all views, including item accounting data. Furthermore, if item accounting data of a financial organization is marked for delete, the sales data status, purchasing data status and inventory data status of all organizations, that belongs to the financials organization, has to be set to ‘on hold’. Unfortunately, that didn’t happen sometimes because of a programming error. This application will find the invalid data and will update them.
5 Contained changes and extensions
5.1 Application development
RFR-016499 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016499 Correction
Framework: Base
Application: Items
View: n.a.
Action: Mark for Delete
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 before.
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 item accounting data, when the item base is marked as deleted. Furthermore, if item accounting data of an organization is marked for delete, the sales data status, purchasing data status and inventory data status has to be set to ‘on hold’. Unfortunately, that didn’t happen because of a programming error.
Data update: UPDBUG028772
RFR-016499 Correction
Framework: Calculation
Application: Cockpit: Sales item, Cockpit: purchase items
View: n.a.
Action: Generate calculations…
Category: Unexpected behavior
Problem: Cost calculation types may have calculation schemas assigned.
If for sales items trade cost calculations are generated via cockpit it is mandatory to specify a cost calculation type for this job. If this cost calculation type has a calculation schema assigned some data are taken from this calculation schema. The data are “Supplier” and “Supplier origin”.
If no calculation schema is specified for cost calculation type a calculation schema must be specified for the job to work properly (batch dialog). But in this case data from specified calculation schema are not used for setting supplier and supplier origin.
If a calculation schema is specified for cost calculation type and a different calculation schema for the job(batch dialog), supplier and supplier origin are set from calculation schema of cost calculation type instead of calculation schema of task.
The same behaviour can be experienced when generating trade cost calculations for purchasing items via cockpit.
Correction result: If a calculation schema is specified for the job to be performed (batch dialog) then this schema’s supplier and supplier origin are used as default for generated trade cost calculation.
RFR-016499 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-016499 Documentation
The help document “com.cisag.app.help.instructionsforuse. production.VirtualTableProductionPlanBaseParameters” has been created.
RFR-016499 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 any more.
RFR-016499 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 be done if the action was excecuted from the cockpit: delivery orders.
Correction result: From now, as expected, the same validations will be done which are done excecuting this action from maintenance.
RFR-016499 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Cancel
Category: Exception
Problem: An exception occurred canceling a picking order for a production order if a serial number is already fixed for a material detail line in the production order.
Correction result: From now an exception won’t occur in that case. Everything will work as expected.
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016499 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.)
Now warnings will be confirmed here automatically and in case of errors an exception will be thrown now.
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 you can consider now the “current entity mode” value also within additional validations that belong to these order types.
RFR-016499 Extension
Description:
The following new base classes have been provided to simplify the support of order batch action hook implementations: com.cisag.app.general.order. log.AbstractOrderBatchActionHookApplication
com.cisag.app.general.order.log. AbstractOrderHeadersBatchActionHookApplication
com.cisag.app.general.order.log. BatchActionHookApplicationState
com.cisag.app.general.order.log. DefaultBatchActionHookApplicationState
com.cisag.app.general.order.ui. AbstractOrderCockpitBatchActionHookImpl
com.cisag.app.general.order.ui. DefaultBatchActionHookApplicationParameterEditor
5.1.1.2 Items
RFR-016499 Correction
Framework: Base
Application: Items
View: Inventory
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 Inventory management
5.1.2.1 Availability query
RFR-016499 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Delete
Category: Invalid data
Problem: Deleting a delivery order for external production creates invalid demand origin and availability data (for the assigned purchase order of the order chain).
Correction result: From now invalid demand origin and availability data won’t be created in that case.
Data update: The invalid data have to be corrected with the applications com.cisag.app.inventory.tools.ui.RefreshAvailabilityDetail and com.cisag.app. inventory.tools.ui.CleanBadFixedReservations if needed.
RFR-016499 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.
RFR-016499 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 several times and has warehouse stock for all.
Correction result: Although a variable set contains an item several times the availability caclulation can be done.
5.1.2.2 Delivery orders
RFR-016499 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.2.3 Inventory postings
RFR-016499 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.2.4 Inventory query
RFR-016499 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.2.5 Loads
RFR-016499 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.2.6 Picking orders
RFR-016499 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-016499 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.
RFR-016499 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-016499 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Create transport order
Category: Exception
Problem: An exception occurred creating a transport order for a picking process when a loading unit was assigned for reporting, that contains an item of type “Serial number without inventory management” and serial numbers are defined in the detail lines of the loading unit.
Correction result: From now the creating of the transport order will work with no problems in that case.
5.1.2.7 Receipts of goods
RFR-016499 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-016499 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.2.8 Reservations
RFR-016499 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.3 Multi-site capability
5.1.3.1 Distribution orders
RFR-016499 Correction
Framework: Sales
Application:Distributions orders
Action: Delete line items
Category: Exception
Problem: If a return distribution order is present and a line item is marked for deletion that has also some return identifier data an exception can occur.
Correction result: Now the exception does not occur any more.
5.1.4 Production
RFR-016499 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.
RFR-016499 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Reschedule and Reschedule midpoint
Category: Unexpected behavior
Problem:
1.) In case a constraint did reference a later position, it was ignored during rescheduling because the later positions had not been read from database yet.
2.) In case an operation was manually added, the field “fixedBegin” was automatically filled in the scheduling tab.
Correction result:
1.) Upon rescheduling, the constraints are analyzed AFTER all positions have been read, so later positions are found by the constraints resolving code.
2.) The field “fixedBegin” is not automatically filled, except a midpoint rescheduling is executed, which normally only shows already filled positions or external manufacturing operations.
RFR-016499 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Dispatch, Dispatch and release
Category: Unexpected behavior
Problem:
1.) In case a constraint did reference a later position, it was ignored during dispatching because the later positions had not been read from database yet.
2.) In case a constraint is created for resource and refers to other resource, after dispatching resource refers to operation instead of resource
Correction result:
1.) Upon dispatching, the constraints are analyzed AFTER all positions have been read, so later positions are found by the constraints resolving code.
2.) Constraints created for resources refers to proper resource after dispatching
Technical information: Incompatible change in com.cisag.app.production.order.log.OrderDetailFactory. addResourceDetailFromTask(OrderEntity, MutableOrderDetail, PrimitiveTask, CompoundTask, CompoundTask)
The method now returns the guid of the detail.
RFR-016499 Correction
Framework: Production
Application: Service bills of material
View: n.a.
Action: Deactivate
Category: Unexpected behavior
Problem: Performing action “Deactivate” in application “Service bills of material” clears the message queue.
Correction result: Action “Deactivate” no longer clears the message queue.
RFR-016499 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 view “Quantity overview” does not regard detail type “Cross site operation”.
Correction result: In above mentioned scenarios displaying view “Quantity overview” works as expected. No exception occurs.
5.1.4.1 Bills of material
RFR-016499 Correction
Framework: Production
Application: ProductionPlan
View: n.a.
Action: n.a.
Category: Unexpected behaviour
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.5 Purchasing
5.1.5.1 Purchasing recommendations
RFR-016499 Correction
Framework: Planning
Application: Generate purchasing recommendations
View: n.a.
Action: generate
Category: Unexpected behavior
Problem: The transition time of the planning item view was ignored during re-calcultation of the order date.
Correction result: The transition time of the planning item view is now used during re-calcultation of the order date.
5.1.5.2 Supplier invoices
RFR-016499 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.
RFR-016499 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Book
Category: Exception / Unexpected behavior
Problem: If the booking of a supplier invoice is performed and a warning is present and the warnings will not be confirmed automatically an exception can occur within the “prepare booking” step.
Correction result: Now this excpetion does not occur any more.
5.1.6 Sales
5.1.6.1 Assortments
RFR-016499 Correction
Framework: Sales
Application: Assortment lists
View:
Action: update
Category: Exception
Problem: After changing the view of the application and 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 invoices
RFR-016499 Correction
Framework: Sales
Application: Customer invoices
Action: Generate invoice
Category: Exception / Unexpected behavior
Problem: In case of a retail customer invoice a NullPointerException can occur in the case that now tax code could be determined for the invoice date and the fallback of the sales order detail was used
Correction result: Now the exception does not occur any more.
5.1.6.3 Customer returns
RFR-016499 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 any more 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 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 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-016499 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.4 Sales prices
RFR-016499 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
5.1.7.1 Generate storage locations
RFR-016499 Correction
Framework: Storage Location Control
Application: Cockpit: storage location inventories/item
View: n.a.
Action: Edit logistic units
Category: Exception
Problem: If a row is selected that belongs to the detail search “Item units” an exception will be caused at the execution of the action “Edit logistic units”.
Correction result: Selected rows that belongs to detail searches will be ignored and an error message is displayed at execution of the action “Edit logistic units”.
5.1.7.2 Inventory orders
RFR-016499 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 is happen the existing application “Correct voucher data and reservations” can be used to correct the incorrect item data within the shipping zone.
RFR-016499 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: Manual inventory movement
Delete already created inventory order
Category: Exception
Problem: If the conversion values of the item units were chnaged 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.
5.1.7.3 Lademittel
RFR-016499 Correction
Framework: Storage location control
Application: n.a.
View: n.a.
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-016499 Correction
Framework: Storage location control
Application: Storage locations
View: n.a.
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 System development
RFR-016498 Correction
Framework: System Management
Application: Report output jobs
View: n.a.
Action: Schedule report output job
Category: Unexpected behavior and Exception
Problem:
– Exception will be thrown if open empty application
– Pop up submit dialog with wrong title.
Correction result:
– Schedule report output job will be disabled if open empty application.
– Pop up submit dialog with right title.
RFR-016497 Correction
Class: com.cisag.pgm.appserver. CisTransactionManager
Method: getComparator()
Description: Improved the performance of the returned comparator for the Postgresql database.
RFR-016497 Correction
Framework: System Management
Application: Report output jobs
View: n.a.
Action: Schedule report output job
Category: Unexpected behavior and Exception
Problem:
– Exception will be thrown if open empty application
– Pop up submit dialog with wrong title.
Correction result:
– Schedule report output job will be disabled if open empty application.
– Pop up submit dialog with right title.
RFR-016497 Correction
Framework: Software development
Application: n.a.
View: n.a.
Action: n.a.
Generating reports
Category: Unexpected behavior
Problem: If a user changes a report, the report is located in the work directory. If the report is output via the Java SOM, the report is not taken from the work directory.
Correction result: If the user has locked the report, the java-som takes the report from the common work-directory.
5.2.1 Application server
5.2.1.1 Autorizations
RFR-016497 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.2.2 Searches
RFR-016497 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.2.3 System – General
RFR-016497 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.
5.2.4 Workflow
RFR-016497 Correction
Framework: Workflow Management
Application: Cockpit: Activities/OLTP database
View: Standard
Action: Refresh
Category: Exception
Problem: When user tries to refresh cockpit with active detail search “Links” and one of found activities has reference to non-existent object, exception will occur.
Reference to non-existent object will occur if user deleted object for which activity had been created and then saved this activity.
Correction result: Exception does not occur.