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.

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

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

With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix02 will be upgraded to CEE640PB-Fix03.

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

4              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.

UPDADV112146

Initialises the “assignmentType” attribute of the levy assignments.

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.

UPDBUG028980

Update of the last inventory count list

Updates {@link PhysicalInventoryItemStorageData#setLastInventoryCountList(byte[])} and {@link StorageLocationOnhand#setLastInventoryCountList(byte[])} when they did not 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.

• Contained changes and extensions

5.1        Application development

RFR-016511 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 any more.

RFR-016511 Correction

Framework: Inventory
Application: Picking Orders
View: n.a.
Action: Update
Category: Unexpected behavior

Problem: Changing the warehouse for an identifier assignment line was not possible, if the warehouse value of the detail line of that assignment has not a valid QS-status. The message INV-01233 was displayed.

Correction result: As expected, from now changing the warehouse for an identifier assignment line will not depend on the QS-status of the detail line.

RFR-016511 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-016511 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: Error has been corrected.

RFR-016511 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.

5.1.1    Base

5.1.1.1      Base – General

RFR-016511 Correction

Framework: System Management
Application: System cockpit
View: User
Action: Generate partner for user
Field: Assign all organizations
Category: New field

Description: In the dialog for the system cockpit action “Generate partner for user” a new checkbox field “Assign all organizations” was introduced.
If this field is active, all internal organizations are transferred to “Assigned organization” during partner creation.

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

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

Problem: There was 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-016511 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      Partners

RFR-016511 Correction

Framework: Base
Application: Partners
View: General
Action: n.a.
Category: Unexpected behavior

Problem: The customization of the UI failed, because, as a placeholder, a label without a valid key was contained in the programmed UI code.

Correction result: From now all UI elements will have a valid key and the customization will work as expected.

5.1.1.6      Voucher document templates

RFR-016511 Correction

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

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

5.1.2    Financials

RFR-016511 Extension

Framework: Financials
Application: Levy assignments
Category: Invalid data / Unexpected behavior

Problem: The “type” attribute was maintained with the wrong sort order (wrong value set definition). So the data within the user interface and the levy determination did not work as expected before this correction.

Correction result: The “type” attribute has been replaced by the “assignmentType” attribute (plus a new value set). The new attribute uses the correct sort order; all places have been changed from “type” to “assignmentType”.

Technical information: The old value set and attribute have been deleted.

Data update: Please execute the data update application UPDADV112146 to initialize the new attribute.

5.1.3    Inventory management

5.1.3.1      Delivery orders

RFR-016511 Correction

Framework: Inventory
Application: Delivery slips
View: n.a.
Action: n.a.
Category: Invalid data

Problem: The outputted documents “delivery slip” and “dispatch advice” did not show the correct values for gross weight, net weight, gross volume and net volume from the database.

Correction result: From now the documents will show the correct values.

5.1.3.2      Inventory count

RFR-016511 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.3.3      Loading units

RFR-016511 Correction

Framework: Inventory management
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.3.4      Picking orders

RFR-016511 Correction

Framework: Inventory management
Application: Picking orders
View: n.a.
Action: n.a.
Category: Ergonomics

Problem: The field searches of the quantity fields offered all units of measures for selection without filtering the subset, that is allowed for a detail line item.

Correction result: From now the field searches of the quantity fields will offered the units of measures for selection filtering the allowed for a detail line item only.

5.1.4    Sales

5.1.4.1      Customer invoices

RFR-016511 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-016511 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-016511 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.2        Infrastructure

5.2.1    Consulting

RFR-016511 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-016509 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.

RFR-016509 Correction

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

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

Correction result: The behavior described above no longer takes place. Focus switches on workflow pane only if there is a change in work item list.

5.3.1    Application server

5.3.1.1      Authorizations

RFR-016509 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-016510 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    Configuration

5.3.2.1      System cockpit

RFR-016509 Correction

Framework: System Management
Application: System cockpit
View: System/Performance information
Action: Display persistent performance information query
Field: n.a.
Category: Display and table export extension

Description: The display and table export of the performance information cockpit in the system cockpit have been extended. The table will now show duration fields with leading zeros for readability. Furthermore, the table export output to Excel has been expanded. The exported table will include an additional column for all durations in long number format. This enhancement will assist with sorting durations in Excel. Additionally, the column labeled “statement” from the sub-search view “Statement” will now also display the hex-guid of the database statement. This feature will help relate the statements from Excel to the table application.

5.3.3    ERP system output manager

RFR-016509 Correction

Framework: System Management
Exporting and importing system reports using BIS
Category: Exception

Problem: Exporting and importing system reports with BIS (Business Entity com.cisag.sys.repository.obj.Report) each fails with an exception message ”
java.lang.UnsupportedOperationException: Unable to find the accessor:engine (short)”.

Correction result: The problem is solved.

5.3.4    GUI

RFR-016509 Correction

Framework: All
Application: Applications with HTMLEditor
View: n.a.
Action: Paste images from clipboard
Category: Unexpected behavior

Problem: If an image was pasted from clipboard into the HTML editor, the image is lost after “save” or after switching to “text only” mode and back.

Correction result: Fixed.

Technical information: Browsers are embedding pasted images using “data:” URLs, but the fitter rules of the HTML editor were blocking “data” URLs in general. Now, data URLs for some image format (PNG, JPG, GIF) are accepted by the filter.

5.3.5    Workflow

5.3.5.1      Declarations and scripting

RFR-016509 Correction

“replace” now returns a value.