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

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

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

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

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.

UPDSUP122635
Update undefined schedulingBaseDate for dispatched production orders

5              Contained changes and extensions

5.1        Application development

RFR-016589 Correction

Correction of the German 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-016589 Correction

Class: com.cisag.app.general.order.log. SourceViewStateUtility
Method: <S extends HookState> S getHookState(Class<S> hookStateImplClass, Class stateRetrieverReturnType)
Category: Invalid data / Unexpected behavior

Problem: If any SourceState implementation (especially a “com.cisag.app.general.order. hook.log.HeaderSourceState” implementation) implements also the EntityState sometimes the wrong “data view” method (“getEntityState”) is used instead the correct source state method (e.g. “getHeaderSourceState”).

Hint: Because typically the header DataObject has normally also an EntityState HookState container. So, the method does not work as expected (expected “HeaderSourceState” implementation is not used) or wrong data is used.

Correction result: Now all methods that return an EntityState will be skipped so that the method works always as expected.

5.1.2    Calculation

RFR-016589 Correction

Framework: Calculation
Application: Calculation type
View: Group box “Defaults”, Field “Product cost calculation category”
Action: n.a.
Category: Unexpected behavior

Problem: Value “Pre-calculation with quotation reference” could temporarily only be set in application “Calculation Types” if Customizing -> Production -> Configuration is active.

Correction result: Value “Pre-calculation with quotation reference” is generally available in application “Calculation Types”.

5.1.3    Document Management

5.1.3.1      Document cockpit

RFR-016589 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      Delivery orders

RFR-016589 Correction

Framework: Planning
Application: Production recommendations
View: n.a.
Action: All generate/create production orders actions that dispatch order
Category: Unexpected behavior

Problem: Production recommendation of quantity 1 is generated for item with “Identifier category” set to “Serial number with inventory management” and “Creation methods” of “Identifier defaults” set to “Automatic”. Production order type used for generation has field “Time of determination of identifier” set to “When dispatching the production order”. Trying to perform generation of production order with dispatching for that configuration displayed multiple errors about not existing identifier, but production order was generated and dispatched, but without identifier.

Correction result: Identifier is now correctly created and set to newly generated production order without any errors.

5.1.5    Planning

5.1.5.1      Material requirements planning

RFR-016589 Correction

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

Problem: Material requirements planning took a long time when a lot of items were planned, especially when planning multiple sites at once.

Correction result: Material requirements planning is faster, especially with many items and many sites.

RFR-016589 Correction

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

Problem:
1. When an item was planning with delivery calendar and a recommendation was created for a delivery date, only the demands to the next delivery date were included, even in case the item had a demand coverage time range configured that should require to cover also demands after the next possible delivery date.
2. The planning automatically extends the demand period by non-working days that immediately follow the currently planned day. In case a demand coverage time range is also configured, it also started immediately after the currently planned date, also covering the demands of the non-working days following the planning day. Thus, the demands of the extended planning period were counted twice, resulting in too high recommendations. This problem can only appear in case there are demands at non-working days.

Correction result:
1. After the planning decides that a recommendation is necessary considering the demands until the next possible delivery date, it will additionally find demands after the next delivery date until the end of the demand coverage range and include them into the recommendation quantity.
2. The demand coverage time range now starts AFTER the extended demand period of the planned day, so demands after the planned day in the extended demand period are not counted twice.

5.1.6    Production

5.1.6.1      Production order types

RFR-016589 Correction

Framework: Production
Application: Production order type maintenance
View: Tab “Multi-site production”
Action: n.a.
Category: Exception

Problem: If customizing Production -> External manufacturing -> “Activate internal external manufacturing” is not set application “Production order types” does not display tab “Multi-site production” nor does it display checkbox “Internal external manufacturing”.
As this application is designable it is possible to remove tab “Multi-site production”. If within such a context a production order type is loaded with checkbox “Internal external manufacturing” active an exception occurs.

Correction result: In above-described context no exception occurs. An error message is displayed that multi-site data are missing.

5.1.6.2      Production orders

RFR-016589 Correction

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

Problem: Opening any production order which was dispatched with empty “Dispatching date” automatically enters edit mode, trying to set proper value to this field even if order was already completed.

Correction result: New data update has been created to update empty “Dispatching date” in all already dispatched orders to avoid entering edit mode in “Production orders”.

Technical information: The possibility to keep that “Dispatching date” empty was fixed in one of the previous fix. This date is now set automatically during dispatching or manual adding of a detail. It means the problem occur only for production orders that was created/completed before mentioned previous fix.

Data update: UPDSUP122635
Sets “Dispatching date” for all dispatched production orders to proper value based on earliest begin, latest end and scheduling category of an order header.

5.1.7    Relationship Management

5.1.7.1      Opportunities

RFR-016589 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-016588 Ergonomics

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

RFR-016588 Correction

Framework: Software development
App development, usage of “friend” apps.
Category: Invalid data

Problem: An App must function even if a defined friend app is not present.
Java classes can be used to skip certain logic or gui implementations if a friend app is not present. For other development object this possibility does not exist.
This can result in invalid development objects in the target system when installed.

Correction result: The validation was improved. If on a certain development system, a development object references a development object from a friend app then an error message is shown.
A special case are hooks. Here it is possible to set a dependency = false flag. If set the hook implementation is not executed if the hook contract it is based on is not present.
Therefore for hooks the error message is not shown if the flag is set.

RFR-016587 Correction

Framework: Kernel / Persistence
Application: Internal Performance Optimization
View: n.a.
Action: n.a.
Description: Replacing CisHashMaps with ConcurrentHashMap to reduce synchronized blocks in the kernel.

RFR-016587 Correction

Framework: Kernel / Persistence
Application: Internal Performance Optimization
View: n.a.
Action: n.a.

Description: The methods com.cisag.sys.kernel.CisSharedCache.beginCommit() and com.cisag.sys.kernel.CisSharedCache.endCommit(), along with their associated fields, have been removed. Consequently, the calls to these methods in com.cisag.sys.kernel.server.CisTransactionManagerImpl.commit(CisTransaction, CisSessionControlBlock) were removed. Additionally, fields within the inner classes of com.cisag.sys.kernel.server.CisTransactionCache were set to final where possible. This adjustment resulted in measurable performance gains in other areas of the CisSharedCache.

RFR-016587 Correction

Minor speed optimizations in the persistence service area.

RFR-016587 Correction

Framework: software development
Application: development objects
View: n.a.
Action: Drag and drop in the navigator
Category: Exception

Problem: If you try drag and drop on the navigator for development objects and the list is empty an exception occurs.

Correction result: No exception occurs anymore.

5.2.1    Data exchange

RFR-016587 Correction

Framework: System Management
Execution of incoming web services
Category: Unexpected behavior

Problem: Depending on the design of a web service, some parts of the request message could be shown in System cockpit, Sessions tabs, as instance description, during execution of the web service.

Correction result: The described information is no longer shown, as it could be long, or contain sensitive data.