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

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

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

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

No batch data updates have to be carried out.

• Contained changes and extensions

5.1        Application development

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

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

5.1.1    Base

5.1.1.1      Contracts/RFQs/Quotations/Orders

RFR-016523 Correction

Action: Document reorganization
Category: Unexpected behavior

Problem:
1. In some rare cases a self-order reference exists (source and target order are the same). If such a reference is present it will prevent the reorganization.
2. “Debtor credits” application: The standard action “Reserve automatically” and “Reduce unallocated credit reservations” are enabled also if the current instance is marked for reorganization.

Correction result:
1. Now all order references where source and target order are the same will be ignored.
2. Now both actions are disabled for instances that are marked for reorganization.

RFR-016523 Extension

Framework: Purchasing, Sales
Application: Purchase orders, Sales orders
Action: Complete billing line items

Problem: The fix “CEE640PB-Fix04 KW40/2024” contains a change of the “Complete billing line items” functionality. By mistake up from this change, the general status of the line items were not completed in all relevant cases.

Technical information: Now also the general status will be refreshed as expected.

5.1.1.2      Fiscal years

RFR-016523 Correction

Framework: Base
Application: Fiscal years
Action: Next period status (ERP)
Category: Invalid data / Unexpected behavior

Problem: The period status can be changed to “Temporarily closed” without a warning and to “Closed” without an error message even if an open supplier invoice is present with a “date” value within this period. This is especially a problem for internal supplier invoices that belong to a customer invoice because here the “date” attribute value cannot be changed manually.

Correction result: Now the warning and error messages will be send within the “Fiscal years” application as expected. Please note that difference messages will be used for supplier invoices with the status values “Invalid” and “Released”.

Technical information: The class “com.cisag.app.purchasing.log.FiscalPeriodSetPurchasingStatusHookImpl” has been corrected.
The coding of the class “com.cisag.app.sales.log.FiscalPeriodSetSalesStatusHookImpl” has been changed in analogy (without any functional change).

5.1.1.3      Item characteristics

RFR-016523 Correction

Framework: Base
Application: Item characteristics
Action: Delete
Category: Exception / Unexpected behavior

Problem: If a new item characteristic was not considered by the generation (no table column is present) and has a deletion marker an exception occurs during the try to delete directly such an item characteristic.

Correction result: Now the exception does not occur any more.
Hint: Please note that the “Generate table schema” action/application considers also all item characteristics with a deletion marker.

RFR-016523 Correction

Framework: Base
Application: Item characteristic classifications
Category: Invalid data / Unexpected behavior

Problem: The description (attribute “label”) of the “Item characteristic” is not displayed always within the content language of the current user.

Correction result: Now also the description will be displayed within the content language of the current user.

5.1.1.4      Items

RFR-016523 Correction

Framework: General
Application: Items
View: n.a.
Action: Create/Create from template
Category: Unexpected behavior, Performance

Problem: The application tried to load item accounting data from the database, that could not exist on the database because the base item itself was not persistent.

Correction result: From now the application will try to load data only if the base item is persistent already.

5.1.1.5      Partners

RFR-016523 Correction

Framework: Base
Application: Partners
View: Accounting
Action: Create new bank account
Category: Unexpected behavior

Problem: If an IBAN is given, an account holder without a bank account must be possible.

Correction result: The validation of bank account is removed, an account holder without a bank account is now possible.

5.1.2    Calculation

5.1.2.1      Calculation – General

RFR-016523 Correction

Framework: Calculation
Application: Cockpit: Production orders; Product cost calculation
View: n.a.
Action: Cockpit: Production orders -> Generate calculations…; Product cost calculation -> Calculate…
Category: Unexpected behavior

Problem:
1. In application “Product cost calculations” a calculation of type “Calculation of the production order” is created with a “Valuation price” = “Price from price listing”. Material of the calculated product has well defined purchase prices from specified price listing.
Result: No purchase prices are retrieved. Instead, the substitution valuation price is retrieved. This is wrong. Reason is the setting “Use target quantity” (see shelf) = “Use target quantities and target times”. This setting is correct but leads to a false mode of retrieving quantities for finding prices from price listing.
2. In application “Cockpit: Production orders” for one or more production orders “Generate calculations…” is performed, also with type “Destiny category” = “Calculation of the production order”. The dialog shown for this action has a not editable field “Use target quantity” = “Use actual quantities and actual times” set.
Due to help document this setting is wrong (correct is “Use target quantities and target times” as in context 1). Nevertheless, this setting is forwarded to generated calculation and leads to correct calculation of material prices.

Correction result:
1. For setting “Use target quantity” = “Use target quantities and target times” the quantities for calculating purchase prices are set up correctly and hence purchase prices are calculated correct.
2. The dialog for “Generate calculations…” sets “Use target quantity” = “Use target quantities and target times” when “Destiny category” = “Calculation of the production order” or “Pre-calculation with order reference”. If “final calculation of the production order” is set, field “Use target quantity” is editable with a default value of “Use actual quantities and actual times”. The generated calculation also calculates purchase prices for material correctly with now changed value of “Use target quantity”.

5.1.3    Inventory management

5.1.3.1      Identifiers

RFR-016523 Correction

Framework: Inventory managment
Application: Identifiers
View: n.a.
Action: Load
Category: Ergonomics

Problem: Although the working area contained more elements than the view can display no scrollbar was supported.

Correction result: If the working area contained more elements than the view can display a scrollbar will be offered as expected.

5.1.3.2      Inventory query

RFR-016523 Correction

Framework: Inventory Management, Storage Location Control
Application: Cockpit: Inventories, Cockpit: Inventories/items, Cockpit: Storage location inventories
View: n.a.
New detail search “Artikel-Ladeeinheiteninformationen”
Category: Unexpected behavior

Problem: If the inventory cockpits were used to load item stock the loadunit informations would not be displayed because they have different stock data. It was not simple to recognize packed quantities.

Correction result: The three cockpits are extended now. A new detail search is offered to display all loading unit information that belongs to the same inventory owner, storage structure (warehouse, [zone, bin, slot]), item and identifier. The QC status will be ignored because the loading unit content stock data do not have any QC status. Only the loading unit itself has a stock QC status now.

Technical information: To support the join between the stock data and the loading unit stock (UnitLoadOnhand) the empty zone and bin defaults were changed from Null to ZEROGUID. There is no data update for that, this means when loading units were already used before using this order, the detail search would not display them for simple zones. Every update would also update these attributes. If you need this new detail search you can execute following update statements to enforce the new defaults.
———
UPDATE com.cisag.app.inventory.obj.UnitLoadOnhand ulo
SET ulo:zone=ZEROGUID
WHERE ulo:zone is null
———
UPDATE com.cisag.app.inventory.obj. UnitLoadOnhand ulo
SET ulo:storageLocation=ZEROGUID
WHERE ulo:storageLocation is null

5.1.3.3      Reservations

RFR-016523 Correction

Framework: Inventory Management
Application: Reservations
View: Issues
Action: Reset reservation category
Category: Ergonomics

Problem: The action was not selectable after using the second view “Receipt and Inventory”

Correction result: The action is always selectable within the view “Issues” as expected.

5.1.4    Planning

5.1.4.1      Generate purchasing recommendations

RFR-016523 Correction

Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: New purchase recommendation
Category: Unexpected behavior

Problem: Adding purchase recommendation manually using blocked item or blocked supplier was allowed without any message although on this recommendation actions “Generate purchase orders” and “Generate purchase RFQs” cannot be performed as long as item and/or supplier are blocked.

Correction result: Trying to add manually purchase recommendation with blocked item or/ and supplier will display error now, which means that this kind of recommendation cannot be added anymore. Errors are the same as during action “Generate purchase RFQs”.

5.1.5    Production

RFR-016523 Correction

Framework: Production
Application: External operation transaction postings
View: n.a.
Action: Ship to external manufacturer…
Category: Unexpected behavior

Problem: A production order has an external operation with some assigned material provided. In application “External manufacturing operation postings” for this external operation a quantity is specified and subsequently “Ship to external manufacturer…”.
At least one of the assigned materials provided is not available for shipment.
Result: A delivery order is generated with externally manufacturing item and material provided except the one which is not available. There is no notification of user about the missing material provided.
But it is not possible to ship the material provided later on, when it is available. The only workaround has been to “Complete delivery order and perform output slip” for generated delivery order and perform “External manufacturing operation postings” anew when all material provided is available.
Unfortunately, this workaround does not work anymore due to a problem which skips the problematic material provided again in the course of generating a delivery order although it is available.

Correction result: A new validation is introduced now which checks if all material provided is available for the process “Ship to external manufacturer” and outputs proper messages if not. Thus, the user can quit this process in that case.
If despite these validations a delivery order with material provided missing is generated the workaround described above is working as expected.

RFR-016523 Extension

Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior

Problem: In case a production order was dispatched a 2nd time with a different earliest begin or latest end date or switched scheduling direction,
the scheduling logic still used the scheduling base date of the very first dispatch to start the scheduling forward or backward from this old date.

Correction result: In case a production order is dispatched a 2nd time, the scheduling base date is recomputed from the earliest begin or latest end date depending on the scheduling direction and the scheduling logic will start from this recomputed date.

RFR-016523 Correction

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

Problem:
1. In case an operation position was imported with changed begin/end times and this operation contained an infinite resource position in the production order that was not mentioned in the import data, the infinite resource position stayed at the old begin/end times after the update processing.
2. An infinite resource position that was imported with resource bookings, there was no error message during update processing.

Correction result:
1. In case an operation position is imported with changed begin/end times and this operation contains an infinite resource position in the production order that is not mentioned in the import data, the infinite resource position will take the begin/end times of the parent operation.
2. An infinite resource position that is imported with resource bookings, there is now an error message that explains that this resource position cannot have resource bookings in the import data.
Technical information: Infinite resource does not have resource reservations and no shift reservations.

5.1.5.1      Production – General

RFR-016523 Correction

Framework: Calculation
Application: CalculationTypes
View: Ident view
Action: n.a.
Category: Exception

Problem: It was possible to set field “Product cost calculation type” = “Incomplete” in application “Calculation types”. If such a calculation type is used in application “Product cost calculation maintenance” on action “Create” an exception occurs.
Reason is that value of “Product cost calculation type” triggers the view of application “Product cost calculation maintenance”. A value “Incomplete” in this context is not allowed. “Product cost calculation type” = “Incomplete” is only used for calculations “on the fly” which are not intended to be saved persistently. An example is calculating a price for a configurable item in a sales order.

Correction result: In application “Calculation types” it is not possible any more to set field “Product cost calculation type” = “Incomplete”.
If application “Calculation types” opens a calculation type with this value already set field “Product cost calculation type” is emptied so that user has to select a proper value when saving. If a user creates a new calculation via application “Product cost calculation maintenance” using a calculation type with above mentioned wrong value a calculation of target type “Pre-calculation” as default value is created.
If a user generates new calculations via Cockpit: Product cost calculations using a calculation type with above mentioned wrong value, calculations with target type “Pre-calculation” as default value are created.

5.1.6    Storage Location Control

5.1.6.1      Inventory orders

RFR-016523 Correction

Framework: Inventory Management
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Exception

Problem: If a loading unit that contains a simple item should be reported and transported between two simple warehouses (with reservation support) an exception could be caused.

Correction result: The loading unit can be transported as expected.

5.1.6.2      Inventory requisitions

RFR-016523 Correction

Class: com.cisag.app.inventory.order.log.DemandElementHookWarehouseOrderImpl
Method: n.a.

Description: The method getDemandElementInfo(byte[] header, byte[] detail, byte[] subKey, short availabilityType) now fully supports the specification of a sub key with the value not equal to ZEROGUID.

5.1.6.3      Storage strategies

RFR-016523 Correction

Framework: Storage Location Control
Application: n.a.
View: n.a.
Consideration of the “time limit for bulk additions to existing stock” during the inventory order creation for withdrawal
Category: Unexpected behavior

Problem: During the automatic warehouse stock detection for creation of withdrawal inventory orders, the lime limit for bulk additions was not always detected correctly.

Correction result: The settings for “bulk additions to existing stock” will be detected from the current valid put strategy as expected.

5.2        System development

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

Framework: Software development
Application: Text editing cockpit
View: Import texts/translations
Action: Import Excel file(s)
Category: Exception

Problem: If the to be imported file is corrupt, then the parser cannot read it.

Correction result: If just some rows cannot be parsed, then the exception is caught. A message is written in the log that the row in question will be skipped.

RFR-016521 Correction

Framework: System management
Tool: crtsas, chgsas
Category: Ergonomics

Problem: The parameter svmStart­Parameters has no effect.

Correction result: Parameter is removed.

RFR-016521 Extension

Framework: Software development
Application: development objects
View: file deliveries
Action: n.a.”

Category: Ergonomics

Problem: File deliveries allow to delivered files that might be currently used on the target system, for example files in the lib folder. However, on the creating system those files must be put manually at the desired location.

Correction result: On activation of the job the contained files will be treated like as if they were installed via a file delivery.
On next restart of the system those files will be distributed or exchange accordingly.

5.2.1    Application server

RFR-016521 Correction

Framework: System management
Application: Cockpit: Data exchange log entries
View: n.a.
Action: open with pin
Category: Unexpected behavior

Problem: The filter field “responsible user” is filled with the current user, ignoring the user in the pinned parameters.

Correction result: Field is filled with the user from the pinned parameters.

5.2.1.1      StartUp

RFR-016522 Extension

Updated: some apache-commons libraries, bcel, bouncy castle, poi, postgre jdbc and a “Lib” bundle.

5.2.2    Customizable cockpits

RFR-016521 Correction

Framework: All
Application: Customizable cockpits
View: n.a.
Action: Specify search fields …
Category: Unexpected behavior

Problem: If the “Specify search fields” dialog was used to modify the visible search fields, the values of all search fields were removed on “OK”.

Correction result: Fixed.

RFR-016521 Correction

Framework: All
Application: Customizable cockpits
View: n.a.
Action: Select and organize views
Category: Unexpected behavior

Problem: When switching between two views with different sorting criteria, the data was automatically updated (database query). Depending on the type and complexity of the new filter and sorting criteria, usable indices in the database and the amount of data, it could take a very long time to perform the update.

Correction result: There is no longer an automatic update when switching between views. Instead, the results list is automatically deleted if the sort and filter criteria of the new view differ from those last used. In this context, the handling of database timeouts has also been changed. Previously, the timeout detection was deactivated during the automatic update due to a change in the sorting criteria, now the timeout detection is active for every update — even when changing sorting criteria via dialog or clicking on the column headers.

5.2.3    GUI

RFR-016521 Correction

Display of the message when the modal dialog is active: Message dialog is only displayed if there is at least one recipient for a message in the modal dialog.

5.2.3.1      Grid control

RFR-016521 Correction

Error has been fixed. Now the table will also update correctly after “arrow keys”.

5.2.4    System – General

RFR-016521 Correction

Framework: Software Development
Reading a relationship in a data view
Category: Exception

Problem: When reading a “1..n” relationship of a data view, where the relationship has the PERSISTENT property, an exception “java.lang.IllegalArgumentException: wrong number of arguments” appears. The exception is thrown when program code iterates over the com.cisag. pgm.util.OneMany object which is returned by the relationship’s retrieve…() method.

Correction result: The relationship’s target objects are returned.

Framework: Software Development
Reading a relationship in a data view
Category: Exception

Problem: When reading a “1..n” relationship of a data view, where the relationship is from a data view extension and the data view is of “view” visibility, a ClassCastException exception similar to ” java.lang.ClassCastException: class com.sun. proxy.$Proxy123 cannot be cast to class com.cisag.pgm.base.DataAccess … at com.cisag.pgm.util. OneManyBase.get …” is thrown.

Correction result: The relationship’s target objects are returned.

5.2.5    Workflow

5.2.5.1      Workflow templates (transport)

RFR-016521 Correction

Framework: Workflow
Application: Process Definitions
View: “n.a.”
Action: “n.a.”
Category: Ergonomics

Problem: When the process definition is loaded, no message informs about it.

Correction result: Works as expected, except only the first load is not informed.

RFR-016521 Correction

Framework: Workflow.
Application: Process Definitions, Workflow roles, Activity Definitions.
View: n.a.
Action: loading a business entity
Category: Ergonomics

Problem: No message a.k.a. “#process definition name# is loaded” is shown, when loading a process definition. Choose any Process Definition from search and it will be loaded without above mentioned message. No matter how many times you hit “refresh” button after a load, no message will be delivered.
Activity Definitions and Workflow roles deliver a corresponding message only AFTER the first “refresh” button hit.

Correction result: As soon as you press “Accept” in search window in all three applications, the corresponding message will appear.

Technical information: Had to add a couple of lines to the AbstractWorkflowMaintenance#runConfirmedLoadAction().
Also refactored all methods in ProcessDefinitionMaintenance class, although it was not necessary.