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-Fix18.”

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-Fix18

With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix17 will be upgraded to CEE630PB-Fix18.

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 Supportauslieferun­gen” which contains information about possible causes and about instructions on how to solve the problem.

• Rework after installation

4.1        Data updates

No data updates have to be carried out.

4.2        Batch data updates

With the “Query data updates” application, you must schedule the following data updates, for any point in time.

4.2.1    UPDBUG028980

Update of the last inventory count list

Updates {@link PhysicalInventoryItemStorageData#setLastInventoryCountList(byte[])} and {@link StorageLocationOnhand#setLastInventoryCountList(byte[])} when they didn`t contain the count list that was used to count them the last time. Erroneous data can only exist for permanent inventory count list details closed after 2022,1,29. The inventory management server will be reinitialized after this data update.

4.2.2    UPDBUG028917

Recalculation of sales orders due to empties/loading equipment order line items

The empties determination logic has been changed so that special handling of storage units no longer exists (design error). This update application corrects the incorrect sales order data.

5              Contained changes and extensions

5.1        Application development

RFR-016514 Correction

Framework: Planning
Application: Cockpit: Planning conflicts
View: Selection view
Action: New
Category: Unexpected behavior

Problem: Cockpit: Planning results has a not intended default value “OBH100” for selection field “Material requirements planning”.

Correction result: Default value is set now to empty value.

RFR-016514 Correction

Framework: Base
Application: com.cisag.app.general. extension.ui.DatatypeMaintenance
View: n.a.
Action: create or edit DataTypes of type BusinessObject
Category: Ergonomics

Problem: Editing of types does not get blocked soon enough.

Correction result: the moment the type is persistent, the “Business Entity” field is no longer editable.

RFR-016514 Correction

Framework :Base
Application: Output text modules
View: n.a.
Action: Report output
Category: Error in report output

Problem: Error in report output in the application Output text modules

Correction result: No error occurs anymore.

RFR-016514 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-016514 Correction

Framework: System Management
Application: Import data
View: n.a.
Action: Importing EntityExtensionSet
Category: Unexpected behavior

Problem: Importing invalid data into EntityExtension for “other fields” can result in faulty database data. For example, generating table schema is not possibly any more.

Correction result: Erroneous data will not be imported anymore.

RFR-016514 Correction

Framework: Inventory
Application: Import data
Filter: com.cisag.app.shipping.obj.UnitLoad
Action: Import data
Category: Invalid data / Unexpected behavior

Problem: In special cases the imported value of the attribute UnitLoad:actualGrossWeight has been overwritten unintentionally with a value calculated by the import controller.

Correction result: From now an imported value of the attribute UnitLoad:actualGrossWeight will be stored by the import controller as expected.

5.1.1    Base

5.1.1.1      Base – General

RFR-016514 Correction

Framework: Extension
Application: Other Fields
View: n.a.
Action: new
Category: Ergonomics

Problem: create new selection-field and fill out the selection list, while the system language is not German. Then try to choose a default value. All alternatives to “no selection” will be blank.

Correction result: now in the default, values are shown, even in the proper system language

Technical information: before the correction, the multi-language-data of the row was used, rather than the multi-language-data of the value within the row.

5.1.1.2      Contracts/RFQs/Quotations/Orders

RFR-016514 Extension

New entry in com.cisag.app.general.OrderType: Name of entry: SEM_QM_INSPECTION_ORDER
ID: 2036

Description (de): Prüfauftrag
Description (en): Inspection order
Description (pl): Zlecenie kontroli

5.1.1.3      Customizing

RFR-016514 Correction

Framework: System Management
Application: Customizing
View: n.a.
Action: Sales prices, purchasing prices
Category: Exception

Problem: There is a problem with starting sales and purchasing apps despite the activation of the modules

Correction result: The problem is fixed.

5.1.1.4      Items

RFR-016514 Correction

Framework: Base
Application: Import data
Filter: i.e. com.cisag.app.general.obj.Item
Action: Import
Category: Exception

Problem: An exception occurred importing texts in the language “en-us” (i.e. for item extension fields).

Correction result: From now importing texts in the language “en-us” will work as expected.

5.1.1.5      Voucher document templates

RFR-016514 Correction

Framework: Base
Application: Voucher document templates
View: n.a.
Action:n.a.
Category: New behaviour

Description: E-Mail template will be used in mail body text, if “E-Mail template mode” is “From template”, not depend on “Text setting mode”.

5.1.2    Inventory management

5.1.2.1      Delivery orders

RFR-016514 Correction

Framework: Inventory
Application: Shipping orders
View: n.a.
Action: Print container labels
Category: Ergonomics

Problem: The action is enabled in the application although the delivery slip was not already created. The user was able to click it although no document is printed.

Correction result: From now the action will be enabled only then, when the delivery slip is created.

5.1.2.2      Inventory count

RFR-016514 Correction

Framework: Inventory management
Application: Inventory count list
View: n.a.
Close inventory count line items for a permanent inventory count
Category: Invalid data

Problem: The error was already corrected but no data update was carried out because the attributes were not use in the logic and after the next inventory count process the data were updated automatically.

Correction result: A data update was implemented to correct the data immediately.

Data update: UPDBUG028980

5.1.2.3      Loading units

RFR-016514 Correction

Framework: Inventory
Application: Import data
Filter: com.cisag.app.shipping.obj.UnitLoad
Action: Import
Category: Unexpected behavior

Problem: The import process of loading units always discards the association to an existing goods receipt, even if extension attributes only should be set.

Correction result: From now the import process of loading units will not discard the association to an existing goods receipt, unless it is explicitly stated in the import file.

5.1.2.4      Picking orders

RFR-016514 Correction

Class: com.cisag.app.inventory.picking.order.log. OrderBatchLogic
Method: com.cisag.app.inventory.picking.order.log.OrderBatchLogic.close(PickingOrder, boolean)

Description: From now an #entity.releaseLock is called at the end of the method. That has been forgotten in a former version of this method.

5.1.2.5      Receipts of goods

RFR-016514 Correction

Framework: Inventory
Application: Goods receipts
View: Distribution
Action: Post receipt of goods…
Category: Exception

Problem: An exception occurred posting the goods receipt. That happens in special cases when the goods receipt has more then 16 detail lines.

Correction result: From now posting the goods receipt will work as expected.

5.1.2.6      Reservations

RFR-016514 Correction

Framework: Inventory Management
Application: Inventory requsition
View: Manual stock movement
Change the warehouse of a reserved line item
Category: Exception

Problem: When an inventory order is deleted and the warehouse was changed after that the creation of a new inventory order will cause an exception. But only if the item has no identifier, it does not support inventory packaging and the line is a withdrawal.

Correction result: The inventory order for the changed warehouse can be generated as expected.

RFR-016514 Correction

Framework: Sales
Application: Sales orders
View: n.a.
Action: Create picking orders…
Category: Exception

Problem: If a concrete identifier was specified within a line item the picking order creation would cause an exception.

Correction result: Picking order can be created as expected.

5.1.3    Multi-site capability

5.1.3.1      Distribution orders

RFR-016514 Correction

Framework: Sales
Application: Distribution orders
View: Return of goods
Return the goods from and to structured warehouses
Category: Invalid data

Problem: The inventory postings created by the receipt of goods and the delivery slip set incorrect origins and these inventory postings got wrong storage zones.

Correction result: Those inventory postings will get correct origins and correct storage zones as expected.

5.1.4    Sales

5.1.4.1      Customer invoices

RFR-016514 Correction

Framework: Sales
Application: Customer invoices
Action: Cancel
Category: Exception

Problem: If a cash invoice has some “empties” line items an exception occurs during the try to cancel such an invoice.

Correction result: Now such an invoice can be canceled as expected.

RFR-016514 Correction

Framework: Sales
Application: Customer invoices
Action: Reorganize
Category: Invalid data / Unexpected behavior

Problem: Instances of the following three business objects were not considered before this correction by the customer invoice reorganization logic:
– com.cisag.app.sales.obj.CustomerInvoiceDebtorCredit
– com.cisag.app. sales.obj.CustomerInvoiceDebtorCreditTaxData
– com.cisag.app.sales.obj. DocumentFreightCost

Correction result: Now also instances of these business object will be deleted that belong to a reorganized customer invoice.

5.1.4.2      Sales – General

RFR-016514 Correction

1.
Framework: Sales
Applications: Sales orders, Sales order confirmations, Shipping orders, Pro-forma-invoices, Customer invoices
Action: Maintain document empties data
Category: Unexpected behavior

Problem: Before this correction there was a special condition present for the case that a normal order line item is a storage unit that is marked as empties. This special condition affects some problems in the following documents (Sales order confirmations, Shipping orders, Pro-forma-invoices, Customer invoices).

Correction result: Because the special condition was an error in the original specification this special condition has been removed up from now. So for example sales orders consider such line items now with the expected behavior.
The shipping orders have been changed so that.

Data update:
The data update application UPDBUG028917 corrects the data of the relevant wrong sales orders. Hints:
– The sales orders need a valid order status. If needed you can recalculate invalid orders after changing them to a valid state.
– Other documents like sales order confirmations, shipping orders, pro-forma-invoices and customer invoices will not be touched by this data update application UPDBUG028917.

2.
Framework: Base
Application: Items
View: Base and Sales
Category: Extension

Description: To support empties data also for storage unit items the following item attributes can be maintained now also for storage unit items: – Item base data: Packaging uoms; “Generate deposits and empties line items”
– Sales item data: “Generate deposits and empties line items”
In addition to that, the shipping order supports now such items to be packed.

5.1.5    Storage Location Control

5.1.5.1      Inventory management server

RFR-016514 Correction

Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Reporting of an inventory order for a receipt of goods
Category: Exception

Problem: When stock with open receipt of goods process data within the receiving zone was removed by an inventory count process the put-away inventory postings of another receipt of goods could not be processed correctly.

Correction result: The inventory postings will be processed now and the inventory orders of other receipt of goods can be discarded as expected.

5.1.6    Workflow Management

RFR-016514 Correction

Framework: Workflow Management
Application: Job titles
View: default
Action: n.a.
Category: Correction

Problem: If user creates at least two job relationships or partner relationships and then changes bot relationship types/partner categories, changing first or last of created rows will cause that both rows to be completed with the same data (immediately or while selecting second of rows).

Correction result: Changing one row does not affect other rows.

5.2        Infrastructure

5.2.1    Consulting

RFR-016514 Correction

Framework: Multiple
Application: Applications with “Other fields” support
View: n.a.
Action: “New” on “Other fields” toolbar
Category: Unexpected behaviour

Problem: When creating a new “Other field” from type “Selection field”, validations will not show the red corner for error message indication for the field “Selection list”

Correction result: The red corner indicating an error message is shown.

5.3        System development

RFR-016512 Correction

Framework: Workflow
Application: WorkflowPane
View: WorkflowPane
Action: n.a.
Category: Ergonomics

Problem: WorkflowPane, which is a side attachable window, “steals” focus, when it is attached.
Examples:
1. upon pressing “ENTER” in an application X, focus jumps to WorkflowPane;
2. open application A,B, etc… , WorkflowPane takes focus.

Correction result: The behavior described above no longer takes place. Focus switches on WorkflowPane only if there is a change in Workitem list.

RFR-016512 Correction

Framework: System management
Application: Export data
View: n.a.
Action: Export data
Category: Exception

Problem: Export of configuration business objects (e.g. User) by a non-administrator completes, but yields a RuntimeException (“Object mapper for class XX and database YY could not be loaded!”), regardless of granted authorizations.

Correction result: No exception occurs anymore.

5.3.1    Application server

5.3.1.1      Autorizations

RFR-016513 Correction

Framework: System management
Application: Authorization roles
View: n.a.
Action: Validate, change selection
Category: Ergonomics

Problem: Messages SYS-7155 and REP-11022 use “Yes”/”No” instead of object type.

Correction result: Messages corrected and expanded.

RFR-016512 Correction

Framework: System management
Application: Authorization roles
View: n.a.
Action: Validate, change selection
Category: Ergonomics

Problem: Messages SYS-7155 and REP-11022 use “Yes”/”No” instead of object type.

Correction result: Messages corrected and expanded.

5.3.2    Workflow

RFR-016512 Correction

Framework: Workflow Management
Application: Activity Definitions
View: Individual activity
Action: Validate
Category: Correction

Problem: When script functions setResultFieldVisible or setResultFieldEditable are used in Declarations, error KRN-00504 (Function does not exist.) occurs.

Correction result: When script functions setResultFieldVisible or setResultFieldEditable are used in Declarations, error does not occur. These functions can be used to show/hide or enable/disable result fields in the application “Activities ” and in the results dialog.

5.3.2.1      Activity definitions

RFR-016512 Correction

Framework: Workflow managment
Application: Activities
View: Standard
Action: Generation of scipt node by process
Category: Correction

Problem: After running process with script nodes activities from script nodes have empty field subject, so these activities cannot be validate with success.

Correction result: Script nodes activities are saving with subject from activity definition (static or set dynamically).

5.3.2.2      Declarations and scripting

RFR-016512 Correction

“replace” now returns a value.

5.3.2.3      Process definitions

RFR-016512 Correction

Framework: Workflow Management
Application: Process definitions, Activity definitions
View: n.a.
Action: Refresh, Save
Category: Exception

Problem: If user tries to use refresh or save action when both fields: Activity definition/Process definition and description are empty, exception will occur.

Correction result: Exception does not occur, error message about not specified activity or process definition is displayed.