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

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

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

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.

UPDADV116308

Purpose: Activates the management of resource reservations via BO ResourceBooking instead of BO ResourceAvailability.
Preconditions: No users must be using the system during this migration! Technical details: Deletes all data from target BO com.cisag.app.production.resourcescheduling.obj.ResourceBooking. Loads all data from the source BO com.cisag.app.production.obj.ResourceAvailability, converts and saves it to target BO. Deletes all data in the source BO. Activates the com.cisag.app.production.ResourceBookings function in Customizing. The server should be restarted after the migration. Result: The activation of this the Customizing-Function prevents this update from being executed again. Once this function is activated, resource reservations of the framework “Production” are managed via BO ResourceBooking instead of ResourceAvailability.

• Contained changes and extensions

5.1        Application development

RFR-016529 Correction

Framework: General
Application: Customizing, Items
View: n.a.
Action: Load, Validate
Category: Exception

Problem: In conjunction with the conversion of physical units of measure defined in the customizing function ‘com.cisag.app.general.WeightsAndDimensions’ several exceptions occurred.

Correction result: From now the conversion of physical units of measure defined in the customizing function ‘com.cisag.app.general.WeightsAndDimensions’ will work as expected.

RFR-016529 Correction

Text changes for cockpit actions from “Vertriebspreise Löschkennzeichen setzen” and “Beschaffungspreise Löschkennzeichen setzen” to “Vertriebspreise löschen” and “Beschaffungspreise löschen” in cockpit applications “Cockpit: Vertriebspreise” and “Cockpit: Beschaffungspreise”.

RFR-016529 Ergonomics

Update of the FR language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.

RFR-016529 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-016529 Ergonomics

Update of the EN user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.

5.1.1    Base

RFR-016529 Correction

Class: com.cisag.app.general.otherwarnings.log.OtherWarningsEntity, com.cisag.app.general.otherwarnings.log.OtherWarningsStructureCache

Description: The caching logic is extended to improve the performance. Furthermore, from now the other warnings entity will call that new extended logic.

RFR-016529 Correction

Framework: Base
Application: Series pattern
View: n. a.
Action: n.a.
Category: New application

Description: This application allows to create, edit, display (and import) series patterns for price list extensions. It should be possible to use prices within their validity period, e.g. only on certain days or in a season.
The series patterns should be available in both Purchasing and sales, including rental.

5.1.1.1      Base – General

RFR-016529 Extension

1. Class: com.cisag.app.general.gui. StrategyField
   New Method: public boolean setVisibleValues(CisCollection guids, boolean originalSorting)Description: In analogy to the method “com.cisag.pgm.gui.ValueSetField. setVisibleValues(short[] constantValues, boolean originalSorting)” the class “com.cisag.app.general.gui.StrategyField” also supports the parameter “originalSorting” now.

   Hint: The existing method public boolean setVisibleValues(CisCollection guids) calls the new method now with the value “true” for the parameter “originalSorting” (same behavior as before).
   2. New class:
   “com.cisag.app.general.gui. factories.StrategyEditor” that is based on the class “com.cisag.app.general.gui.StrategyField”.
   3. New class:
   “com.cisag.app.general.gui.factories.StrategyEditorFactory” that is based on the class “com.cisag.app.general.gui.factories.StrategyEditor”.

5.1.1.2      Contracts/RFQs/Quotations/Orders

RFR-016529 Correction

New entries in com.cisag.app.general.OrderType:

1. Name of entry: SEM_RENTAL_ORDER
ID: 2040
Description (de): Mietvertrag
Description (en): Rental order

2. Name of entry: SEM_RENTAL_ORDER_CONFIRMATION
ID: 2041
Description (de): Mietvertragsbestätigung
Description (en): Rental order confirmation

RFR-016529 Correction

New entry in com.cisag.app.general.OrderType: Name of entry: SEM_ERP4PL_SAD_DOCUMENT
ID: 2042
Description (de): SAD-Dokument
Description (en): SAD document
Description (pl): Dokument SAD

5.1.1.3      Echange rates

RFR-016529 Extension

Framework: Base
Application: Exchange rates
View: n. a.
Action:n.a.
Category: Required changes

Description: The following changes have been made:
1. Some columns must also be right-aligned.
2. In the tooltip, the quote that is not entered but calculated by reciprocal value formation should be displayed with 15 decimal places and use the round sign ˜ (or ‘\u2248’) instead of the equal sign.
3. the prices in the table that are displayed in a different notation from the one entered or saved, i.e. those that cannot be edited, should be displayed with 15 decimal places and in italics.

5.1.2    Inventory management

5.1.2.1      Delivery orders

RFR-016529 Correction

Framework: Inventory management
Application: Delivery orders, Picking Orders
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: The Hook-Interface “com.cisag.app.general.order.hook.log.HeaderApplyDefaultsHook” was not called although it’s contained in the hook-contract

Correction result: From now the Hook-Interface “com.cisag.app.general.order.hook.log.HeaderApplyDefaultsHook” will be called as expected.

5.1.2.2      Inventory count

RFR-016529 Correction

Framework: Inventory Management
Application: Inventory count
View: n.a.
Inventory posting key fields
Category: Ergonomics

Problem: Some inventory posting key fields was marked as required although no inventory postings should be created (only count methods: External inventory count, Inventory reconciliation).

Correction result: The required mark depends on the setting whether inventory postings should be created.

5.1.2.3      Inventory postings

RFR-016529 Correction

Framework: Inventory management.
Application: Inventory postings
View: Inventory posting
Action: Save
Category: Exception

Problem: If the storage location control is disabled and you carry out a transfer posting, an exception was thrown when saving.

Correction result: If the storage location control is disabled, no exception is thrown even if a transfer posting is made.

5.1.2.4      Picking orders

RFR-016529 Correction

Framework: Inventory management
Application: Picking orders / Inventory orders
View: n.a.
Change the previous suggested inventory identifier
Category: Unexpected behavior

Problem: If the whole stock is reserved but only for the item level the change of the suggested inventory identifier could be denied although it is possible to reserve it.

Correction result: If the released warehouse stock of the changed identifier is not fix reserved the identifier can be changed within the picking order as expected.

5.1.2.5      Reservations

RFR-016529 Correction

Framework: Inventory Management
Application: Picking orders
View: n.a.
Reporting
Category: Exception

Problem: If the picking order was created without reservation support and the reservation was activated before the reporting process, the reporting of an item quantity could cause an exception.

Correction result: The picking order can be reported as expected although the reservation setting was changed.

5.1.2.6      Warehouses

RFR-016529 Extension

Framework: Inventory management
Application: Warehouses
View: n.a.
Action: n.a.
Field: Abgaben-Erhebungsebenen-Klassifikation
Category: New field

Description: A levy collection level classification can now be assigned to a warehouse.

5.1.3    Multi-site capability

5.1.3.1      Inter-company billing

RFR-016529 Correction

Framework: Base
Application: Inter-company billing
Action: Generate inter-company billing
Category: Invalid data/Unexpected behavior

Problem: If some base discounts are present but not used by all line items the currency of these discounts is not set. So in case of “Gross calculation” some base discounts are visible but without a currency.

Correction result: Now the values of all used base discounts will be initialized with the invoice currency so that this error does not occur any more.

Hint: There is no data update application available to correct the wrong data; if needed, you have to cancel and recreate such invoices.

5.1.4    Production

RFR-016529 Correction

Framework: Production
Application: Import production order dates
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: In case an operation begin/end time was given and a sibling resource begin/end time range was bigger than the operation time range the operation time range was extended but not the time range for other sibling resources that were not mentioned in the import data.

Correction result: The extended operation begin/end times are now first computed from all child resourced and these times are applied to all child resources without begin/end times mentioned in import.
This only applies in case the resources without begin/end times would be updated from the operation times anyway.
When no operation begin/end times are given, the resources without begin/end times stay unmodified.

RFR-016529 Extension

Framework: Production
Application: All applications that are concerned with resource reservations.
Category: Refactoring

Description: Resource reservations can now optionally be stored differently in the DB (after a manual data update).
This will allow import of reservation data from external systems and better performance when working with reservations in general.

Technical information: To activate this new feature, the data update UPDADV116308 has to be carried out. This feature is required, when resource reservation data is to be imported via “Cockpit: Production order scheduling import data”.

Data update: This reads all data from BO com.cisag.app.production.obj.ResourceAvailability, converts it and writes to com.cisag.app.production.resourcescheduling.obj.ResourceBooking.
Also activates customizing function com.cisag.app.production.ResourceBookings to enable new features.
Data migration cannot be undone.
For more information, see documentation document UPDADV116308.

5.1.4.1      Production orders

RFR-016529 Correction

Framework: Production
Application: Production orders, Routings, Operations
View: n.a.
Action: Dispatch, Dispatch and release, New dependency
Category: Exception

Problem: Creating new dependency between details with column “Overlap time” set to non-time unit of measure and trying to dispatch that constraint caused exception.
Value assistant for that column suggested each unit of measure, not only time-specific units.
Error about wrong unit of measure triggers only in some cases, although setting in wrongly for each case caused exception then.

Correction result: Now setting unit different than second, minute or hour displays error message in every case. Now value assistant shows only allowed unit of measure. Dispatching constraints with wrong unit of measure (created before that fix) will set “Overlap time” to zero with same unit as “Target processing time”.

RFR-016529 Correction

Framework: Production
Application: Cockpit: Production orders/Material line items, Cockpit: Production orders, Production orders
View: n.a.
Action: Calculate availability…
Category: Unexpected behavior

Problem:
1. Some production orders have material line items with material which is not accounted onhand. On creation this material gets the availability status “No availability check”. If in “Cockpit: Production orders/Material line items” this material is selected for performing action “Calculate availability…” result of this action is that material not accounted onhand gets availability status “Not available”. This is not correct.
2. A production order is scheduled back or forward multiple levels and some sub orders are generated. Due to production order type no availability check is on generation. This is done by user subsequently performing action “Calculate availability…” (-> “Dertermine only availability status”) either by application “Production orders” or “Cockpit: Production orders”.
Result: only for main order calculation of availability is done, not for sub orders.
Please note: If availability check has to be done on generation of production order/sub orders (due to setting of production order type), this calculation is done for main order as well as for sub orders.

Correction result:
1. Performing action “Calculate availability…” via “Cockpit: Production orders/Material line items” availability status remains in status “No availability check” for material which is not accounted onhand.
2. Performing action “Calculate availability…” (-> “Dertermine only availability status”) either by application “Production orders” or “Cockpit: Production orders” calculates and sets availability status for main order as well as for sub orders.

RFR-016529 Correction

Framework: Production
Application: Production orders
View: Tab “Dispatching”
Action: Dispatch…/Dispatch and release …
Category: Unexpected behavior

Problem: In the course of dispatching the resolved product structures are set in not editable fields “Bill of resource”, “Bill of material”, “Routing” (and “Production method”).
If product structure results in sub orders field “Bill of material” may have a wrong entry. This is the case if bill of material of semi-finished product (“BOM-SF”) has as first line item a bill of material (“BOM-XY”) instead of a regular material. Instead of correct bill of material “BOM-SF” the bill of material “BOM-XY” is set in tab “Dispatching”. Things work correct if “BOM-SF” has one or more regular material as first line items followed by a bill of material (“BOM-XY”).

Correction result: In above-described context file “Bill of material” in tab “Dispatching” is set correct (in example: “BOM-SF”).

RFR-016529 Correction

Framework: Production
Application: Production orders
View: n.a.
Action: New operation reservation, Recalculate due date and quantity
Category: Exception

Problem: If operation has a specified resource list with at least two resources and next it has been added manually to production order then after performing rescheduling with recalculation quantities, an exception occurred.

Correction result: In described situation exception does not occur anymore and rescheduling works properly for that case.

5.1.5    Purchasing

5.1.5.1      Supplier invoices

RFR-016529 Correction

Framework: Purchasing
Application: Supplier invoice
Action: Apply defaults and logics about the “account” attributes
Category: Invalid data / Unexpected behavior

Problem: Since some time the usage of the purchasing customizing property “Account origin for additional cost invoices” was restricted to additional cost invoices (purchasing or distribution) only.
But this was not enough for cases where “General ledger entries” is activated for the relevant financials organization.

Correction result: The “Account origin for additional cost invoices” is used also for “normal” invoices now and will be copied also into their correction invoices, but it has an effect only of additional invoice line items.
To avoid some further problems, the customizing value “Use “from order”” will be used now only for invoices with activated “General ledger entries”.
Also some further problems have been corrected especially for line items for that an expense account is relevant.

Hint: Please note that the needed documentation changes will be performed by an extra correction order.

RFR-016529 Correction

Framework: Purchasing
Application: Supplier invoices
Action: “Manually assign purchase order line item to selected line item” / “Manually assign receipt of goods line item to selected line item”
Category: Invalid data / Unexpected behavior / Ergonomics

Problem: If the purchase order has specified costing data (“cost center” “cost objective”) either as one value or as split values, the supplier invoice did not use the specified data in all cases. The data will be used only if the “cost center / cost objective” combination is not already present.

Correction result: Now in the case that a “cost center / cost objective” combination is already present the quantities add values will be increased with respect to the added data.

5.1.6    Sales

5.1.6.1      Customer invoices

RFR-016529 Correction

Framework: Sales
Application: Customer invoices
Action: create/generate customer invoice
Category: Unexpected behavior

Problem: If the iso code of output language (from the invoice customer) has more than two signs (e.g. “en-us”) a specified item description in this language will not be determined because within the system engine the language code has not separator (for example here “enus”).

Correction result: Now the separator will be removed before reading the item data by the system engine. Please note that in case of an empty item description in the output language the database default language will be used as before.
Hint: In addition to that, some customer invoice coding has been corrected that did not consider the output language for the “price uom” code.

RFR-016529 Correction

Category: Exception

Problem: The generated classes that belong to the data views “com.cisag.app.financials.model.CustomerInvoicePrepayment” and “com.cisag.app.sales.invoice.model.CustomerInvoicePrepayment” did not match to the relevant XML definition data – as result an exception (“relation PrepaymentAssignment missing method”) occurs during the try to use the data view.

Correction result: Now the classes were generated again so that the exception does not occur any more.

RFR-016529 Correction

Framework: Sales
Action: Customer invoice generation
Category: Exception

Problem: If a shipping order has an additional line item that is not based on a sales/distribution order line item an exception occurs.

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

5.1.6.2      Sales quotations

RFR-016529 Correction

Framework: Sales
Application: Customer proposals
Action: Print
Category: Invalid data / Unexpected behavior

Problem: If a customer proposal uses the “net kind of pricing” and has some freight costs the standard report contains an unexpected value for the printed “total value”; also, the “end value” is missing in some cases.

Correction result: The standard report has been corrected.

5.1.7    Storage Location Control

5.1.7.1      Storage locations

RFR-016529 Correction

Framework: Inventory Management
Application: Warehouses
View: n.a.
Import of simple zones
Category: Unexpected behavior

Problem: When a simple zone has been tried to be imported an error message prevented the import.

Correction result: Simple zones can be imported as expected.

RFR-016529 Correction

Framework: Inventory management
Application: Storage locations
View: n.a.
Action: Create a new storage location
Category: Unexpected behavior

Problem: If the type was not yet specified, the fields for replenishment were not displayed in the item definition.

Correction result: If the type is not specified, all fields are displayed in the item definition, including those for replenishment.

5.2        Internal applications

5.2.1    Support requests

RFR-016529 Correction

Framework: Software development
Application: Support requests
View: n.a.
Action: n.a.
Field search shows the same values multiple times
Category: Unexpected behavior

Problem: The field searches for partners have no search context.

Correction result: The field searches work as expected.

5.3        System development

RFR-016528 Ergonomics

Update of the EN user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.

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

5.3.1    Application server

5.3.1.1      Chat

RFR-016528 Extension

Framework: System management
Application: ChatERP
View: n.a.
Action: n.a.
Category: Various

Description: The internal API for communication with the ChatERP service has been changed. The new API allows the following new features:
– more secure authentication
– streaming of answers (faster response)
– support for user feedback and suggestions

5.3.2    Data exchange

RFR-016528 Correction

Framework: System Management
BIS SOAP Export web service
Category: Exception

Problem: A BIS SOAP Export web service call or WSDL request may fail with an exception “java.lang.IllegalStateException: Error looking for parameter names in bytecode: unexpected bytes in file”. In case of a web service call, the exception is contained in the web service response.

Correction result: The problem is resolved.