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

Preparing the installation

Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.

Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.

3              Information about CEE650PB-Fix01

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

3.1        Installing support deliveries

The following sections describe the special features for installing the support deliveries of this delivery.

If the source system has a state that is between CEE640PB and CEE640PB-Fix12, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE650PB.

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

3.4        Cumulative installation of support deliveries

Code status CEE640PB is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.4 and Comarch ERP Enterprise 6.5 at the same time. Support deliveries for Comarch ERP Enterprise 6.5 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.

4              Rework after installation

4.1        Data updates

Data updates have been carried out automatically in the release upgrade process. You must check the installation protocol for all applied data updates.

4.2        Batch data updates

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

UPDBUG030140

Loading units – Creating loading unit status objects

This update application will create a loading unit status object (com.cisag.app.shipping.obj.UnitLoadStatus) as 1:1 Dependent for all actual loading unit objects (com.cisag.app.shipping.obj.UnitLoad with UnitLoad:version = 0) that don’t have any. It is required, that the data update application com.cisag.app.update.log.UPDADV103530E, that is part of the update from CEE6.3 to CEE6.4, run before.

UPDSUP122696

SalesDetailGroupDocumentData: Initialisiert die fehlenden Hauswährungs-Attribute

Versehentlich wurden Instanzen des BOs „SalesDetailGroupDocumentData“ mit leeren Werten für die internen Attribute „_organization“, „_conversionDate“ und „_currencyCombo“ erstellt. Diese Datenaktualisierungsanwendung füllt leere Attribute mit den Werten des entsprechenden Besitzer-BOs (CustomerProposal, SalesOrder oder Confirmation).

5              Contained changes and extensions

5.1        Application development

RFR-016583 Correction

Label correction for “Complete loading” (com.cisag.app.shipping.shippingload.Complete) from “Verladung abschließen” to “Verladungsstatus prüfen und auf „Verladen“ setzen”, German only.
What’s this help and tooltip have been added.

5.1.1    Base

5.1.1.1      Base – General

RFR-016583 Correction

Framework: v
Application: Export data
Object: com.cisag.app.purchasing.obj.PriceDefinition
Category: Unexpected behavior / Ergonomics

Problem: The label of the “Supplier price hierarchy” field has the wrong text “Customer price hierarchy”.

Correction result: Now the label is as expected.

5.1.1.2      Contracts/RFQs/Quotations/Orders

RFR-016583 Extension

Framework: Base
Application: Voucher reorganization settings/historical data
Action: Maintain document types
Category: Unexpected behavior

Problem: By mistake the dialog to maintain the “Document types” contains a “System.out.println” – so a log file line was created when performing the “next page” or “previous page” table action.

Correction result: Now the “System.out.println” has been removed.

5.1.1.3      Items

RFR-016583 Correction

Framework: General
Application: Items, Import processes with items
View: n.a.
Action: n.a.
Category: Performance

Technical information: From now several classes regarding to the item import process will be performance-optimized

5.1.2    Calculation

RFR-016583 Correction

Framework: Costing, Inventory Management
Application: Cockpit: Item price history
View: n.a.
Action: n.a.
Category: New field

Description: When item prices are calculated and stored using the new level “Item/Site”, the new site attribute is now stored in the item price history and displayed in the related cockpits.

RFR-016583 Extension

Framework: Calculation, Base
Application: Items, Import data
View: Financials
Action: Creating, Saving or Importing an Item with one or many Financial views
Category: Performance

Description: Creating a new Item through Items application or Import takes a lot of time to save the item prices of each Financial view to the history of item prices. This can take around 100ms per Financial view.
Performance is now improved by a factor of 5 to around 20ms per financial view, especially helping batch import of lots of items and lots of financial organizations.

5.1.3    Financials

5.1.3.1      Debitoren-Guthaben

RFR-016583 Correction

Framework: Financials
Application: Debtor credits
Action: Reduce unallocated credit reservations
Category: Unexpected behavior

Problem: The “Reduce unallocated credit reservations” logic considers a “isReducible” functionality that is based on a “DebtorCreditReservationReducibleHook”. This hook is implemented for “sales orders” by “com.cisag.app.sales.debtorcredit.log.SalesOrderDebtorCreditHookImpl”.
By mistake “SalesOrderDebtorCreditHookImpl” returns false also for “debtor credit reservation details” that does not have the order type value “sales order”. As result all other order type value can not be reduced.
By mistake the “com.cisag.app.sales.debtorcredit.log.SalesOrderDebtorCreditHookImpl” returns .

Correction result: Now the “SalesOrderDebtorCreditHookImpl” returns true if the “debtor credit reservation detail” does not have the order type value “sales order”.
So this hook implementation does not prevent any more the reduction of “debtor credit reservation details” that belong to other order types.

5.1.4    Inventory management

5.1.4.1      Delivery orders

RFR-016583 Correction

Framework: Purchasing
Application: Delivery orders
View: n.a.
Action: Complete external delivery…
Category: Exception

Problem: An exception occurred running the action “Complete external delivery…” for an external delivery order.

Correction result: From now running the action “Complete external delivery…” will work as expected.

RFR-016583 Correction

Framework: Inventory, Sales
Application: Cockpit: Delivery orders
View: n.a.
Action: Create picking orders …
Category: Exception

Problem: An exception occurred creating a picking order for more than one selected delivery order.

Correction result: From now creating a picking order for more than one selected delivery order will work as expected.

5.1.4.2      Identifiers

RFR-016583 Correction

Framework: Inventory Management
Application: Identifier Tracking Inquiry
View: Origin
Action: Load identifier tracking data for “ALL” levels
Category: Unexpected behavior

Problem: The creation and sorting of the list took to many time (CPU usage).

Correction result: The identifier tracking data chains will be displayed as expected.

5.1.4.3      Inventory management – General

RFR-016583 Correction

Framework: Inventory
Application: Delivery orders / Packing dialog
View: n.a
Action: Generate, assign and display loadings units …
Category: Exception / Invalid data

Problem: When packing with a loading unit template that contains additional loading unit templates as detail lines, loading units are created without an associated status object. The loading units created are therefore invalid and cannot be loaded.

Correction result: From now packing with a loading unit template that contains additional loading unit templates as detail lines will work as expected.

Data update: UPDBUG030140

5.1.4.4      Loads

RFR-016583 Correction

Framework: Inventory
Application: Cockpit: Shipping loads
View: n.a.
Action: Mark as deleted
Category: Unexpected behavior

Problem: It was possible to mark a shipping load as deleted, that is not shipped already.

Correction result: From now marking a shipping load as deleted, that is not shipped already, will cause an error message.

5.1.4.5      Picking orders

RFR-016583 Correction

Framework: Inventory Management
Application: Picking orders
View: n.a.
Report set item and its kit items
Category: Exception

Problem: If a set item was reported that was supporting fixed reservations save would cause an exception.

Correction result: The set item and its component can be reported as expected.

5.1.5    Planning

RFR-016583 Correction

Framework: Purchasing
Application: Distribution recommendations
View: n.a.
Action: Generate distribution orders
Category: Unexpected behavior

Problem: If an error occured during the generation of orders from distribution recommendations, the entire process was canceled, including for valid recommendations.

Correction result: The error handling now operates differently based on the level at which an error occurs:
– header level error: If an error is found in the order’s header, the entire order and all of its corresponding recommendations are skipped.
– detail level error: If an error occurs in a specific detail line, only the recommendation associated with that detail is skipped. The rest of the order will continue to be processed.
A new validation for detail level errors has been introduced, controlled by new system property that is enabled by default. If this property is disabled, any detail level error is treated as a header-level error, causing the entire order to be skipped.

Technical information: New system property has been added to control detail validation during creation of distribution orders from recommendations: com.cisag.app.purchasing.log.GenerateDistributionOrder.ValidateDetails

5.1.6    Production

5.1.6.1      Production – General

RFR-016583 Correction

Framework: Production
Application: Order maintenance
View: Detail editor
Action: New detail
Category: Exception

Problem: If a production order is marked for deletion it is still possible to create new detail line items of all possible detail types. If such a action is executed a exeception occusrs.

Correction result: If a prduction order is marked for deletion all relevant production specific actions are disabled. No action at detil level can be performed.

5.1.6.2      Production issues

RFR-016583 Correction

Framework: Production
Application: Production issues
View: n.a.
Action: Save, Validate
Category: Exception

Problem:
1. Before loading any production order entering proper production order type and number and performing action save caused exception.
2. Before loading any production order performing validation for empty order type and number fields caused exception. Additionally perfoming validation with proper type and number of order entered, but before loading it caused the load of production order, but with missing detail loading.

Correction result:
1. Action “Save” is now disabled if order is not loaded.
2. Action “Validate” is now disable if order is not loaded. Action load now properly displays errors about missing number and type of an order.

5.1.7    Purchasing

5.1.7.1      Purchase orders

RFR-016583 Correction

Framework: Purchasing
Application: Purchase orders
Action: Apply defaults, “Delivery dun” creation
Category: Unexpected behavior

Problem:
1.) Before this change the “Delivery dun output settings” of a purchase order were determined by the “delivery partner” (“delivery supplier”); also the purchase order line item “delivery partner” was checked versus tbe current “delivery dun output settings”.
2.) The “Delivery dun” generation uses the main supplier of the purchase order (also for some checks and also as “archive partner”).
==> If the “main supplier” and the “delivery partner” are different and the “main supplier” does not support the determined output settings the delivery dun creation fails.

Correction result: Because the responsible business partner of a purchase order is the “main supplier” up from now the following rules will be used:
1.) The “Delivery dun output settings” of a purchase order will be determined now by the “main supplier”.
2.) The purchase order line item validation (“delivery partner” versus “delivery dun output settings”) was removed.
3.) “Output settings” table: If the current value is not defined (valid) it will be added now to the visible values – before this correction an empty value was displayed in this case.
Hints:
1.) Please note that with respect to this change the old “delivery dun output settings” value of a purchase order might not be valid any more and needs to be corrected manually.
2.) Within an extra development order the online help will be changed – also here the “delivery partner” is defined as relevant – this needs to be changed.

5.1.8    Relationship Management

5.1.8.1      Customizable cockpits

RFR-016583 Correction

Framework: Relationship Management
Application: Cockpit: Suppliers, Cockpit: Customers
View: n.a.
Action: Refresh
Category: Unexpected behavior

Problem: Loading data into the cockpits takes long time in case when user have many organizations assigned,

Correction result: Performance of the cockpits has been improved.

5.1.9    Sales

5.1.9.1      Sales – General

RFR-016583 Correction

Framework: Sales
Applications: Customer proposals, Sales orders, Sales confirmations
Functionality: Detail group support
Category: Invalid data / Unexpected behavior

Problem: By mistake instances of the business object SalesDetailGroupDocumentData were created with empty values for the internal attributes “_organization”, “_conversionDate” and “_currencyCombo”.

Correction result: Now these attributes will be maintained as expected.

Data update:
Please execute the data update application UPDSUP122696 to correct the existing data.

5.1.9.2      Sales fast entry vouchers

RFR-016583 Correction

Framework: Sales
Application: Sales fast entry vouchers
Action: Calculate tax
Category: Exception

Problem: In case of “retail calculation” an exception occurs during the step “Calculate tax” if the same application instance is used for multiple sales organizations.

Correction result: Now the exception does not occur any more.

5.1.10       Storage Location Control

5.1.10.1   Inventory management server

RFR-016583 Correction

Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Add loading unit
Category: Exception / Unexpected behavior / Ergonomics

Problem: If a loading unit was added to an inventory order line item several problems could occur: – The loading unit field emptied its value after using the field value assistant
– Changing a loading unit that should be transported but not reported to the reference order reported incorrect quantities
– Adding a loading unit for report did not create stock movement data

Correction result: A loading unit can be added to an inventory order line item as expected and it will be reported correctly.

5.2        Infrastructure

5.2.1    Softwareaktualisierungen installieren

RFR-016583 Correction

Framework: Data Update
Application: com.cisag.app.update.log.UPDADV107259
View: n.a.
Action: Execution of data update
Category: Exception

Technical information: The use of CisTransaction#commitIfSizeLimitExceeded() when updating data, to close and reopen database transactions only when necessary, caused problems with memory requirements, so that fixed block sizes had to be reintroduced in order to better control the memory requirements of this data update.

5.3        System development

RFR-016582 Documentation

The help document “Systemvoraussetzungen” has been updated.

5.3.1    GUI

RFR-016581 Correction

Framework: All
Application: Customizable cockpits
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: Several issues with fixed columns (columns that do not scroll horizontally).

Correction result: Fixed

RFR-016581 Correction

Framework: All
Application: Applications using the “document chooser” dialog
View: “document chooser” dialog
Action: n.a.
Category: Unexpected behavior

Problem: The “document chooser” dialog shows the creation date instead of “last modified” date of a file if the file was updated since creation.

Correction result: Fixed.

5.3.2    Kernel

5.3.2.1      Locking / Caching

RFR-016581 Correction

Process: Lock request
Category: Exception

Problem: A lock request might cause a deadlock. If any involved requested lock is a job lock (as opposed to an application lock), an ArrayIndexOutOfBoundsException (“arraycopy: last source index 32 out of bounds for byte[16]” at com.cisag.sys.kernel.locking.CisLockTable$DeadlockResponder.handleEntry) occurs.
After 10 subsequent deadlocks, an “IllegalStateException: Queue full” (at CisLockTable.createDeadlockResponse) is thrown.

Correction result: No exceptions

5.3.3    Repository

5.3.3.1      Development objects

RFR-016581 Correction

Framework: Software development
Application: user defined attributes
View: n.a.
Category: Ergonomics

Problem: The description fields did not support NLS.

Correction result: The description fields now support NLS.
Furthermore, duplicate action is enabled if an existing managed supplement is loaded.

5.3.4    Searches

RFR-016581 Correction

Framework: n.a.
Application: All cockpits
View: n.a.
Action: n.a.
Adding an attribute of a releation based detailsearch.
Category: Exception

Problem: If the user adds an attribute of a releation based detailsearch to the cockpit, and an update deletes this attribut an exception occurs when the user starts the cockpit.

Correction result: The exception does not occur.