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

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 CEE630PB

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

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

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

• Contained changes and extensions

5.1        Application development

RFR-016393 Correction

Framework: all
Application: all with classification fields for selection of data
Category: Exception

Problem: If the selection text consists of comma separated spaces, a StringIndexOutOfBoundsException occurred.

Correction result: Comma separated spaces are ignored.

RFR-016393 Correction

Framework: n.a.
Application: Cockpits with other fields
View: n.a.
Action: n.a.
Using other fields of type value set as filter field.
Category: Ergonomics

Problem: The entries of another field of the type Valueset can be sorted by the user as desired. If such a field is used as a filter field in a cockpit, the sorting of the entries has not been taken into account.

Correction result: The filter field takes into account the sorting of the entries.

5.1.1    Base

5.1.1.1      Classifications

RFR-016393 Correction

Framework: Base
Application: Classifications
Action: Import
Category: Exception Unexpected behavior

Problem: If an EntityExtensionHierarchy import file contains a wrong datatype an exception occurs during the try to open the application in the correction mode.

Correction result: Now the exception does not occur anymore. Please note that wrong “datatype” values need to be correct directly within the source file.

5.1.1.2      Contracts/RFQs/Quotations/Orders

RFR-016393 Correction

New entry in com.cisag.app.general.OrderType: Name of entry: SEM_MCS_SALES_DOCUMENTS
Description (de): MCS Vertriebsdokumente
Description (en): MCS sales documents
Description (pl): Dokumenty sprzedazowe MCS

5.1.1.3      Item characteristics

RFR-016393 Correction

Framework: Purchasing, Sales
Action: Find and add items
Category: Exception

Problem: The “Find and add items” dialog throws an exception if the view “Item characteristics” was tried to be selected.

Correction result: Now the exception does not occur anymore.

5.1.1.4      Items

RFR-016393 Correction

Framework: Base
Application: Import data
Filter: SupplierPurchaseItem, PurchaseItem
Action: n.a.
Category: Exception

Problem: An IllegalStateException occurred when trying to import units of measure for purchasing which are neither defined as base unit of measure nor as a packaging unit of measure.

Correction result: From now an error message will be displayed in that case.

5.1.1.5      Partners

RFR-016393 Correction

Framework: Base
Application: Customizing
View: Partner
Action: n.a.
Category: Ergonomics

Problem: Opening the dialog of the field “Field selection” more than one time displayed more than one overlaying “attribute” tree. Only the top tree is scrollable and could be used for selections.

Correction result: From now only one tree will be displayed opening the dialog of the field “Field selection”.

RFR-016393 Correction

Framework: Base
Application: Partners
View: n.a.
Action: n.a.
Category: Ergonomics

Problem: The message CMP-51 contains a wrong placeholder for the financial organization. Therefore “{3}” is displayed instead of the financial organizations name.

Correction result: From now the name of the financial organization will be displayed as expected.

5.1.2    Compliance management

5.1.2.1      Declarations

RFR-016393 Extension

Framework: Compliance Management
Application: Declarations
Category: New functionality

Description: The following functionality has been provided:
– In the existing “Cockpit: Declarations” application, sorting by “Declaration” has been defined (previously without sorting); in addition, the “Marked for deletion” attribute is now present in the selection area and in the display area of the “Standard” layout; the column positions and widths have also been changed somewhat.
– New administrative capability “com.cisag.app.compliance. ConsentFormReorganization” (“Declarations reorganization”). This is needed for setting and removing the deletion flag and also for the actual reorganization.
– In the existing “Declarations” and “Cockpit: Declarations” applications, the “Marked for deletion” indicator can be set for declarations with the status “Released” (new capability and UPDATE authorization are required).
– In the existing “Declarations” and “Cockpit: Declarations” applications, the “Marked for deletion” indicator can be removed again for declarations with a deletion indicator (new capability and UPDATE authorization are required).
– With the new background application “Reorganize Declarations” all declarations with a deletion indicator can be reorganized (new capability and UPDATE and DELETE authorization are required).

Technical information: Also a new hook interface “com.cisag.app.compliance.hook.log. ConsentFormReorganizationValidateHook” has been provided for the existing hook contract “com.cisag.app. compliance.hook.log.ConsentForm”, so that validations can be added via hook implementation if needed, which can prevent the reorganization if necessary.

RFR-016393 Extension

Framework: Compliance Management
Application: Declarations
Action: Validation
Category: New functionality

Description: Before this change, the partner needed to be a person. Now also pseudo partners are supported. So declarations can be used also for cases like “order as guest”. For example the “Note” attribute can be used for further data (e.g. partner name and address etc.).

5.1.3    Inventory management

5.1.3.1      Calculate inventory values

RFR-016393 Correction

Framework: Inventory Management
Application: Calculate inventory values
Action: Execute “Calculate inventory values”

Description: The “Calculate inventory values” has been changed, so that now the used result sets are not open anymore a long time. This is needed for the case, that the system engine “watch dog” functionality uses an “idle time out” value that is to low on a concrete system for this functionality (the system property “com.cisag.sys.kernel.sql. CisResultSetGeneric.IdleTimeOut” specifies the number of minutes after that a result set will be closed automatically).

5.1.3.2      Picking orders

RFR-016393 Correction

Framework: Inventory
Application: Cockpit: delivery orders
View: n.a.
Action: Generate and output picking orders…
Category: Exception

Problem: An exception occurred executing this action if a delivery order felt into the selection that is from type “External delivery”.

Correction result: From now delivery orders from type “External delivery” will be filtered executing this action.

5.1.4    Purchasing

5.1.4.1      Purchase price query

RFR-016393 Correction

Frameworks: Purchasing, Sales
Applications: “Cockpit: Purchase prices”, “Purchase price lists”, “Cockpit: Sales prices”, “Sales price lists”
1. Corrections:
– Application “Purchase price lists”: Correction for a start with a specified price definition.
– Application “Sales price lists”: Correction for a start with a specified price definition.
– Application “Cockpit: Purchase prices”: Correction of the display at the field “Price list level”.
2. Extensions:
– Application “Cockpit: Purchase prices”: Link functionality at the field “Price list level” ==> “Sales price lists” with relevant view and data.
– Application “Cockpit: Sales prices”: Link functionality at the field “Price list level” ==> “Sales price lists” with relevant view and data.

5.1.4.2      Purchasing RFQs

RFR-016393 Correction

Framework: Purchasing
Applications: “Purchasing RFQs” and “Cockpit: Purchasing RFQs/line items”
Actions: Print and display data
Category: Invalid data / Unexpected behavior

Problem: Up from the release 5.3, the “Purchasing RFQs line item” has been extended with a price dimension attribute. But the standard “Purchasing RFQs” document report and the line items cockpit display field “Target cost value (primary currency)” do not consider this price dimension.

Correction result: Now the price dimension is considered also at these two places as expected. In addition to that the value “Target cost value (primary currency)” is now rounded with respect to the used currencies.

5.1.5    Sales

5.1.5.1      Customer invoices

RFR-016393 Correction

Framework: Sales
Application: Customer invoices
Category: Unexpected behavior / Ergonomics

Problem: The valueset “com.cisag.app. general.OutputMedium” contains the entries “Printer”, “E-Mail”, “Fax”, “EDI” and “File”. The entries “EDI” and “File” were never used and so they are normally hidden by the data description that belongs to the logical datatype “com.cisag.app.sales.SalesOutputSettingsMedium”. But if the attribute “com.cisag.app. sales.obj.CustomerInvoice:outputMethod.medium” is added manually to the customer invoice cockpit, all entries are visible to be used as filter values.

Correction result: Now the relevant column data description is used to hide the unused entries also for customer invoices. So also the customer invoice cockpit shows only the used values.

5.1.5.2      Sales – General

RFR-016393 Correction

Framework: Sales
Applications: Order confirmations query, Pro forma invoices query, Customer invoices query
Action: Print
Category: Invalid data / Unexpected behavior

Problem:
1. The standard reports for order confirmations and customer invoices were not correct for an ordered item with the item type “Alias item”.
2. The standard report for pro-forma invoices was not correct for an ordered item with the item type “Pseudo item”.

Correction result: Now the three standard reports are correct also for these cases.

5.1.6    Storage Location Control

5.1.6.1      Inventory requisitions

RFR-016393 Correction

Framework: Inventory management
Application: Inventory requisitions
View: Manual inventory movement
Action: Update after a change of the total quantity
Category: Exception

Problem: If a reporting has already been made to the inventory requisition in a unit that is different from the unit of the total quantity, an error has occurred if the total quantity has been changed.

Correction result: Even after a report has been made, the total quantity can be changed as usual.

5.2        System development

5.2.1    Application server

5.2.1.1      Batch

RFR-016391 Correction

Framework: System Management
Application: System cockpit
View: User
Action: Delete a user, deactivate a user, or create a partner for a user
Category: Exception

Problem: When deleting a user, deactivating a user or creating a partner for a user, an exception message “java.lang.NullPointerException … at com.cisag.sys.services. batch.log.CisJobWorker.executeJobInternal” could be displayed.

Correction result: The problem is resolved.

5.2.2    Customizable cockpits

RFR-016392 Correction

Framework: All
Application: Customizable cockpits
Action: Start of batch jobs
Category: New dialog

Description: If a batch job is started from a customizable Cockpit, without selecting any object in the result list, a new confirmation dialog will be shown, prompting the user to confirm, that he really wants the query to be executed again (with the actual filter criteria) and that all objects found in that query should be processed within the batch job.

Technical information: The property “com.cisag.pgm.services.batch.BatchJobSearch. suppressConfirmationDialog=true” can be used to suppress the new confirmation dialog.

5.2.3    GUI

RFR-016391 Correction

Framework: System management
Application: Main application frame
View: n.a.
Action: Log off
Category: Unexpected behavior

Problem: If the new “Tabs” navigation mode is selected in the user settings, the “Log off” menu item is not available, if there are no organization units available/allowed for the user.
Such a situation can happen, for example, if “multi-site” is not used or if the user is not yet assigned to an OLTP database.

Correction result: The “Log off” menu item, is now also available in the scenarios described above.

RFR-016391 Correction

Framework: All
Application: Applications with lists
View: n.a.
Action: n.a.
Category: Ergonomics

Problem: Text in column headers is always left aligned.

Correction result: The text alignment of the column headers is now back under the control of the application (as in CEE 6.1 and below).

5.2.4    ODBC

RFR-016391 Correction

Framework: System management
Application: ODBC data sources
View: n.a.
Action: Creating an odbc data source
Category: Unexpected behavior

Problem: If the user clicks on the link for creating the data source, an error occurs.

Correction result: The error does not occur.

5.2.5    Web server

RFR-016391 Correction

Framework: System management
Application: Webserver
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: Some downloads (e.g. DSN files for ODBC access) may report a 404 error.

Correction result: Fixed.

5.2.6    Workflow

RFR-016391 Correction

Framework: Workflow Managment
Application: Customizing
View: Custom Hook Implementation
Action: Open application
Category: Exception

Problem: When the table is empty and no data is selected and you click on “open application,” an exception occurs.

Correction result: When the table is empty and no data is selected and you click on “open application,” no exception occurs.