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

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

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

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.

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
batch data updates, for any point in time.

UPDBUG030255

Items – update inherritance

This application will update organization depending item data. It will remove inherited purchase, sales, inventory and production data, that must not exist because the corresponding functions are not released in the application “Customizing.” Moreover, it checks for production- and planning data if inventory data exists for an item / organization combination. If not, production- and planning data will be also removed.

UPDBUG030606

Item data: Correction of Inherritance

This update application will search item data of the views inventory, production, planning, sales and purchasing, that is inherrited from a faulty parent organization and will correct this data.

5              Contained changes and extensions

5.1        Application development

RFR-016608 Correction

Framework: Software Development
Application: Supportrequest
View: n.a.
Action: Adding an upload to a text.
Category: Exception

Problem: In rare cases, exceptions may occur during the upload process.

Correction result: The exception no longer occurs.

RFR-016608 Correction

Framework: General
Application: Items
View: Inventory, Production, Planning, Sales, Purchasing
Action: Accept data processing for the selected organization
Category: Invalid data / Unexpected behavior

Problem 1: In special cases the action “Accept data processing for the selected organization” didn’t update the maintaining organization of inherrited item data, that should inherrit from now the item data from the selected organization.

Correction result 1: From now the action “Accept data processing for the selected organization” will always update the maintaining organization of inherrited item data as expected.
Data update: UPDBUG030606

Problem 2: Using the action “Accept data for the selected organizations and for their subordinate organizations” it was possible to inherrit item data to organizations, that are not contained in the users organization context, … which means that he is not authorized to do it.

Correction result 2:
As expected from now the action “Accept data for the selected organizations and for their subordinate organizations” will skip inherriting data for organizations, that are not contained in the user’s organization context.

RFR-016608 Correction

Framework: n.a.
Application: Other fields in applications
View: n.a.
Action: n.a.
Using other fields of type valueset
Category: Unexpected behavior

Problem: If the display language deviates from the standard, the correct entries are not displayed in the value set.

Correction result: The valueset shows the correct translated entries.

5.1.1    Base

5.1.1.1      Classifications

RFR-016608 Correction

Framework: Base
Class: com.cisag.app.general.log. ClassificationAdapter.ClassificationAdapter
Category: Performance improvement

Problem:
When determining buildByPathKey or whether the classification is organization-dependent or not, the constructor first attempts to retrieve buildByPathKey without organization, and if a NoSuchMethodException is thrown, buildByPathKey is retrieved with organization (and also set/getOrganizationalUnit).
Instead, all public methods of the class should be retrieved. If one of the methods is called “buildByPathKey” and has only one parameter of type String, then this is the buildByPathKey method we are looking for and the classification is not organization-dependent. Otherwise, buildByPathKey should be retrieved with organization as before.

Correction Result: The Problem is fixed und this results in better performance and more code readability.

5.1.1.2      Fiscal years

RFR-016608 Correction

Framework: Base
Application: Fiscal years
Actions: “Previous/Next status” (periods)
Category: Unexpected behavior / Ergonomics

Problem:
1. Manuall changes of the period lines were discarded by executing the period change actions.
2. In case of period status changes that were performed “Online” the changed lines will be refreshed with respect to the new value but these lines changes also to the “edit” mode. So further status changes can not be performed directly.

Correction result:
1. Before a period, status change can be performed it will be checked now if any changes of the period lines of the current tab are available. If so, a new error message will be sent for the relevant periods and the status change can not be performed.
Hint: New check for status changes of some periods and change for the whole year.
2. After executing the status change the new value will be set into the relevant period lines (as before) and also the line will be set to “not changed”.
So – if needed – further status changes can be performed directly.
Hint: Please note that this correction changes only the behaviour for the case that the status change will be performed directly (“Online”) – in case of executiong the change by a background application the data needs to be refreshed manually before performing further changes.

5.1.1.3      Items

RFR-016608 Correction

Framework: Update
Application: UPDBUG030255
View: n. a.
Action: n.a.
Category: Invalid data / Unexpected behavior

Problem: The data update application removes the inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations. Unfortunately, it is perfectly acceptable to have item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.

Correction result: From now the data update application will not remove an existing inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.
Data update: Restoring inheritance after the data update would only be possible manually.

5.1.2    Calculation

RFR-016608 Correction

Framework: Costing
Application: Product cost calculations / Trade cost calculations
View: n.a.
Action: Calculate

Category: Ergonomics

Problem: Locking mechanisms in product/trade cost calculation where were not optimally implemented.

Correction result: Locking mechanisms are now more performant.

5.1.3    Document Management

5.1.3.1      Document cockpit

RFR-016608 Correction

Framework: Document Management
Application: Cockpit: Documents
View: n.a.
Action: Load
Category: Ergonomics

Problem: Loading data to Cockpit: Documents takes very long time in case there are lots of documents.

Correction result: Performance of the cockpit has been improved.

5.1.4    Inventory management

5.1.4.1      Reservations

RFR-016608 Correction

Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate delivery orders with order reference and output delivery slips…
Category: Exception

Problem: Exception (this.warehouse2SiteMap is null) was caused during the reservation process.

Correction result: The action can be executed as expected.

5.1.5    Multi-site capability

5.1.5.1      Distribution orders

RFR-016608 Correction

Framework: Sales
Application: Distribution orders
Action: Reduce line item editor size using split pane
Category: Unexpected behavior / Ergonomics

Problem: In contrast to the “Sales orders” application the line-item editor height can not be changed by the “split pane” functionality.

Correction result: Now the behavior is as expected.

5.1.6    Planning

RFR-016608 Correction

Framework: Production
Application: Production recommendations / Distribution recommendations
View: n.a.
Action: Generate production orders / generate distribution orders
Category: Unexpected behavior

Problem: In application “Distribution recommendations”, it was possible to enter 0 quantity for recommendations in the list. When using acting “Generate distribution order” this led to an error.
In application “Producton recommendations”, it was possible to enter a negative priority.

Correction result: It is not possible anymore to enter a quantity of 0 in “Distribution recommendations” nor a negative priority in “Production recommendations” as validation for both cases has been added.

RFR-016608 Correction

Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Enter organizations in field “Sites” & update
Category: Unexpected behaviour

Problem: Entering more than 255 characters in field “Sites” led to a fatal error during planning.

Correction result: Field “Sites” now validates the input length, more than 255 characters are denied.

5.1.6.1      Generate purchasing recommendations

RFR-016608 Correction

Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: Save, Process, Release, Block
Category: Exception

Problem:
1. It was possible to set the same delivery and availability date for a single recommendation when a calendar year for those dates did not exist; the save operation completed successfully without any errors.
2. Setting different availability and delivery dates for a purchasing recommendation, when the calendar does not exist for at least one of the date years, caused an exception during saving or when changing the recommendation status. Despite the exception occurring, the status change actions also saved incorrect dates.
3. Recommendations with dates for which the corresponding calendar year does not exist were hidden, and a warning about the missing calendar year was always displayed. However, the user could not see the incorrect data and therefore could not correct it.

Correction result:
1. Validation now checks if a calendar year exists for the provided dates; if not, an error message is displayed.
2. Attempting to save a date for which the calendar does not exist will result in the same error as in case 1, and the recommendation is not saved or updated after a status change due to the validation error.
3. Recommendations with invalid dates are now also visible, and the validation displays messages for the wrong dates so the user can identify and correct them.

5.1.7    Production

RFR-016608 Correction

Framework: Production
Application: Material requirements query
View: n.a.
Action: Open tab “demands”
Category: Unexpected behaviour

Problem: Translations for fields “Unit of measure” “Total” and “Previous period” are not adapted to user-language if it has been changed.

Correction result: Translations for fields “Unit of measure” “Total” and “Previous period” are adapted to user-language if it has been changed.

RFR-016608 Correction

Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Recalculate due date and quantity…
Category: Unexpected behavior

Problem: A production order uses a cross-site operation. The cross-site operation has some formulas defined for variable and setup time using allowed variables.
Dispatching calculates proper variable and setup time for cross site operation, but rescheduling production order results in wrong calculated variable and setup time.

Correction result: In above-described context variable time and setup time of a cross-site operation are calculated properly on rescheduling production order.

RFR-016608 Correction

Framework: Production
Application: Bills of material
View: Bill of material
Action: Validate, Save
Category: Unexpected behavior

Problem: When bill of material contains line item which is replaced and action Save or Validate will be performed this details is not validated at all, which allows to save invalid data e.g. quantity with decimal number.

Correction result: Now replaced detail is also validated which makes saving invalid data impossible.

RFR-016608 Correction

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

Problem: When dispatching a production order for a production item that has only bill of material as production method set in item view “Production” and a lead time set in item view “Disposition”, the schedulingBaseDate was not calculated as expected.

Correction result: The scheduling base date is now calculated as expected, i.e. earliest begin time + lead time.

RFR-016608 Correction

Framework: Production
Application: Data updates
View: n.a.
Action: Run application
Category: Unexpected behaviour

Problem: Calling the data update multiple times resulted in “Canceled with error”.

Correction result: Calling the data update multiple time succeeds.

5.1.7.1      External manufacturing operation postings

RFR-016608 Correction

Framework: Production
Application: External manufacturing operation postings
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: Fields “purchase order type” and “purchase order” were marked as mandatory (grey corner), even though they are not.

Correction result: Fields are not marked as mandatory anymore.

5.1.7.2      Production – General

RFR-016608 Correction

Framework: Production
Application: Scrap postings
View: n.a.
Action: Post
Category: Unexpected behaviour

Problem: Implementation of validation was faulty.

Correction result: Validation is now correct in any case.

RFR-016608 Extension

Framework: Production
Application: Bill of materials, Routings, Operations, Product configuration rules, Order maintenance
View: Dialog “Edit conditions with substitue and formulas”, “Product configuration rules” -> view “Conditions and actions”
Action: n. a.
Category: New action

Description: For above mentioned applications, formulas and conditions are extended. Expressions can be defined using a wide range of operations on character strings.
Operations are: „substring“, „contains“, „starts_with“, „ends_with“, „last_index_of“, „index_of“, „length“, „replace“
Detailed information will be provided in the help document.

RFR-016608 Correction

Framework: Calculation
Application: Product cost calculations, Trade cost calculations
View: n.a.
Action: Exit
Category: Unexpected behavior

Problem: Changes have been made in applications Product cost calculations and Trade cost calculations. On exiting these applications without saving no notification about changed data appears via “Close application” dialog.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is not locked. Another user thus can load, change and save the same product/trade cost calculation.

Correction result: Applications Product cost calculations and Trade cost calculations display “Close applications” dialog if data have been changed. Thus, user can decide to stop closing application or to close application without saving.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is locked. Another user can load, change but not saving due to a proper information about locked data.

RFR-016608 Correction

Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior

Problem:
1. The PRD-00485 message still appears in logs for blocked structures, but it displays vague and unhelpful details. It is also displayed regardless of the “Log untransferred line items” checkbox setting.
2. The APS-00125 message displays the type of the problematic detail, but it also shows the entire path from the header, which results in a misleading production plan header type.

Correction result:
1. All remaining PRD-00485 messages have been replaced with the APS-00125 message, which means there are now controlled by the “Log untransferred line items” checkbox.
2. The APS-00125 message has been improved to display both the production plan header type and the production plan detail type to improve readability.

5.1.7.3      Production orders

RFR-016608 Correction

Framework: Production
Application: Operations, Order maintenance
View: Operations -> Dialog: Edit conditions with substitute and formulas
Action: Dialog: Edit conditions with substitute and formulas -> Accept, Accept current line item; Order maintenance -> Dispatch
Category: Unexpected behavior

Problem:
1. It is possible to define formulas for an external operation / cross site operation like: Processing time = Order.PRODQTY*Resource. VARTIME*Resource.SCRAP. This leads to an error on dispatching as variable Resource.VARTIME as well as Resource.SCRAP is not defined within scheduling context, that is: there are no values assigned to parameters Resource.VARTIME and Resource.SCRAP. Error message PRD-1094 is displayed.
This has two different reasons: (a) Resource.VARTIME: A proper value can be retrieved on scheduling but it is not supported right now
(b) Resource.SCRAP: A proper value cannot be retrieved as external operations / cross site operations do not support such a value
add (a)
The following parameter values are supported within context external operations / cross site operations, but retrieving is no supported up to now: Processing time: Resource.VARTIME,
Setup time: Resource.FIXTIME
add (b)
The following parameter values are not supported within context external operations / cross site operations: Performance grade: “RESOURCE.PERF”
Rejects: “RESOURCE.SCRAP”
Resource group: “RESOURCE.GROUP”,
Number of resources: “RESOURCE.NUMBER_OF_RESOURCES”

2.
It is possible to define for a resource detail of a normal operation e.g. Resource.VARTIME*Resource.SCRAP. But parameter Resource.SCRAP (-> “Rejects”) is not supported for resources, only Resource.PERF(-> “Performance grade”).
A formula using Resource.SCRAP will provide a value of 0 as value of this parameter is always 0.

3.
If a formula/condition/substitution/alternative is added or is changed in dialog application “Operations” does not show “Edited” sign when dialog is closed with action “Accept”. “Edited” is shown after action “Validate” or if application “Operations” is closed without saving.

4.
If to a production order manually an external operation is added with assigned formula for setup time and/or processing time the result of this formulas do not affect setup time / processing time of production order detail for this external operation.

5.
Production order with external operation using formula/condition based on Resource.VARTIME and/or Resource.FIXTIME is rescheduled. Error message PRD-1094 is displayed as both values are not provided in a rescheduling context.
6. Issues 1, 3, 4, and 5 go also for cross site operations.

Correction result:
1a. Values of parameters Resource.FIXTIME and Resource. VARTIME are retrieved properly for external operations or cross site operations. Formulas using this parameters and other valid parameters within context external operation or cross site operation are calculated as expected.
1b. If parameters listed in “add 1b” are used in dialog “Edit conditions with substitute and formulas” in context “external operation” or “cross site operation” usage will be rejected due to an error message (PRD-00437).

2.
If parameter Resource.SCRAP is used in dialog “Edit conditions with substitute and formulas” in context “resource” usage will be rejected due to an error message (PRD-00437).

3.
If a formula/condition/substitution/alternative is added or is changed in dialog application “Operations” does show “Edited” sign.

4.
If to a production order manually an external operation is added with assigned formula for setup time and/or processing time the result of this formulas does affect setup time / processing time of production order detail for this external operation due to proper calculation.
This is also valid for manually adding cross site operations.
5.
Production order with external operation using formula/condition based on Resource.VARTIME and/or Resource.FIXTIME is rescheduled. The values are provided and lead to calculations as expected.

6.
Issues 1, 3, 4 and 5 go also for cross site operations.

5.1.7.4      Production plans

RFR-016608 Correction

Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer/Update planning data and execute planning
Category: Unexpected behavior

Problem: A product P uses a bill of resource BOR_Z which itself uses a bill of material BOM_Z. A line item of bill of material BOM_Z is another (phantom) bill of material BOM_X. If product p is planned ending up with some recommendation the calculated secondary demands of material belonging to phantom bill of material BOM_X are wrong. Reasons is that the ratio between reference factor of BOM_Z and quantity of line item BOM_X is not regarded properly in calculation of secondary demands.

Correction result: In above-described context ratio between reference factor of BOM_Z and quantity of line item BOM_X is regarded properly and calculation of secondary demands works well.

5.1.8    Relationship Management

5.1.8.1      Customizable cockpits

RFR-016608 Correction

Framework: Relationship Management
Application: Cockpit: Marketing partners, Cockpit: Partners, Cockpit: Customers, Cockpit: Suppliers
Category: Unexpected behavior

Problem: There are 10 identical icons loaded to each row.

Correction result: Icons are now load and layered correctly.

5.1.8.2      Opportunities

RFR-016608 Correction

Framework: Relationship Management, System management
Application: Import data (com.cisag.app.crm.obj.Opportunity)
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: It was impossible to import opportunities with classifications using only path attributes of the classifications.

Correction result: Now it is possible to import opportunities with classification using only path attributes of the classifications.

5.2        System development

RFR-016607 Ergonomics

Framework: Softwaredevelopment
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics

Problem: There was no parallel development for tasks created using the editorial cockpit.

Correction result: Parallel development is now active for tasks created within the context of editorial cockpits.
Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.

RFR-016606 Correction

Framework: All
Application: All cockpits
View: n.a.
Action: Searching
Category: Exception

Problem: An exception may occur if a search is performed in a customizable cockpit with detailed search enabled, and then a search is performed without detailed search enabled.

Correction result: The exception no longer occurs.

RFR-016606 Ergonomics

Framework: Softwaredevelopment
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics

Problem: There was no parallel development for tasks created using the editorial cockpit.

Correction result: Parallel development is now active for tasks created within the context of editorial cockpits.
Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.

RFR-016606 Correction

Framework: Software development
Application: Cockpit: Production level development objects
View: n.a.
Process: Transfer objects
Category: Exception

Problem: If the cross reference is wrong a null pointer exception occurs when trying to check an object from cross reference.

Correction result: An extra check now prevents this null pointer exception.

RFR-016606 Correction

Framework: System Management
Application: Export data
View: n.a.
Action: n.a.
Category: Exception

Problem: NullPointerException will be thrown on the search restriction, if a search field is dependend on an organization.

Correction result: Search restriction works properly.

5.2.1    GUI

RFR-016606 Correction

Framework: All
Application: All
View: Messages (Text Pane)
Action: n.a.
Category: Unexpected behavior

Problem: The “TextPane” UI element which is mainly used for displaying messages, but also in some applications as well, had several issues regarding the display of “styled” text, the interpretion of “plain” vs. HTML text, and the correct determination of size requirements for its contents.

Correction result: Significantly improved.

RFR-016606 Correction

Framework: All
Application: Applications with customizable table
View: n.a.
Action: n.a.
Category: Exception

Problem: Changing the value of one column of a main row (using a value help, like “calculator”) and then changing the fokus to a datail view of another main row (using the mouse), an exception can occur.

Correction result: Fixed.

RFR-016606 Correction

Framework: All
Application: All UI applications
View:n.a.
Action: Open value help
Category: Unexpected behavior

Problem: Since Chrome/Edge version 144, the open value help (fly-over) icon no longer works reliable.
Firefox is not affected.

Correction result: Fixed.

5.2.2    Knowledge Store

RFR-016606 Correction

Framework: Document Management
Application: Documents
View: n.a.
Action: Generate document file from template
Category: Unexpected behavior

Problem: Paragraphs in table cells that contain only empty merge fields were not autonatically removed.

Correction result: Fixed.