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

With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix01 will be upgraded to CEE640PB-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 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.

UPDADV116175

Initialises the attribute “DistributionOrderDetail#sourceDetailType”.

Initialises the attribute “DistributionOrderDetail#sourceDetailType” as follows:
– Value “Line item” if “orderDetail” is neither null nor ZEROGUID.
– Value “Freight costs” if “orderDetail” is ZEROGUID.
– Value “Cash discount” if “orderDetail” is null and the item corresponds to the item in the payment term.

UPDBUG028844

Updates the combination of the begin value in InventoryOnhandPeriodSummay BO.

Checks the currency combination of the begin value with a zero amount of the inventory onhand period summaries and updates it if it is different to the used currency combination with the used currency combination.

• Contained changes and extensions

5.1        Application development

5.1.1    Base

5.1.1.1      Base – General

RFR-016505 Ergonomics

Applications
Category: Unexpected behavior / Ergonomics

Problem: In some cases “1-n” data will be maintained with the help of the class com.cisag.app. general.gui.factories.OneManyDependentEditor.
If new data and deletion is supported the “set/remove deletion marker” action is not directly active after adding a new row.
The “set/remove deletion marker” action will be activated later by an extra “round trip” or action (e.g. “validate”).

Correction result: Now the “set/remove deletion marker” action will be activated directly after adding a new row.

Technical hints: The new functionality is implemented within the method “protected void addRows(List preparedDependents)”.
If the “toggle deletion marker” action is not supported in some specific cases (implemented in an own “public void setValue(Object value, DataDescriptionModification metadata)” method) you have to override also the “addRows” method and disable here the action with respect to the relevant rules.

5.1.1.2      Items

RFR-016505 Correction

Framework: Base
Application: Items / Partners
View: Base
Action: n.a.
Category: Ergonomics

Problem: The fields in the base views of the applications “Items” and “Partners”, that are used to configure functionalities which are limited by the the licence-Key “com.cisag.app.financials.Levies” were visible, although the license was not activated.

Correction Result: From now the fields in the base views of the applications “Items” and “Partners”, that are used to configure functionalities which are limited by the the license-Key “com.cisag.app. financials.Levies” will be visible if the license is activated only.

5.1.2    Inventory management

5.1.2.1      Inventory count

RFR-016505 Correction

Framework: Inventory management
Application: Inventory counts
View: n.a.
Action: Delete
Category: Unexpected behavior

Problem: The automatic deletion of inventory count lists before the inventory count deletion looks not save.

Correction result: To avoid errors during the deletion of inventory counts an additional validation will be executed now.

5.1.2.2      Loading units

RFR-016505 Correction

Framework: Inventory management
Application: Inventory postings
View: Inventory posting
Action: Save an inventory posting for packing a loading unit on storage location.
Category: Unexpected behavior

Problem: If the item definition in the loading unit was smaller than the stock in the storage location, not all of the stock in the storage location was packed. This is not permitted and may lead to further problems.

Correction result: If the entire stock is not considered when packing a load unit, the packing is rejected with an error message.

5.1.2.3      Routes

RFR-016505 Correction

Framework: Inventory
Application: Routes
View: n.a.
Action: n.a.
Category: Extension of the application

Description: From now the application supports the UI-Designer to customize the user interface for extension attributes. Moreover it supports hooks to implement applying defaults and validations for the extended attributes.

5.1.3    Multi-site capability

5.1.3.1      Distribution orders

RFR-016505 Correction

Framework: Sales
Application: Distribution orders
Action: refresh customer outstanding debt
Category: Exception

Problem: By mistake up from the release 6.1 the “refresh customer outstanding debt” logic creates a “currency converter instance” for the financials organization with the method “createSalesInstance”. If the financials organization is not also a sales organization, an exception will be thrown by “CurrencyConverter#createSalesInstance”.

Correction result: Now – as in 6.3 – the “currency converter instance” will be created by the method “CurrencyConverter#createInstance” – so the exception does not occur anymore.

RFR-016505 Correction

Framework: Inventory
Application: Delivery Orders
View: Distribution
Action: Cancel
Category: Unexpected behavior

Problem: The inventory transactions of a canceled delivery order were transferred into the transaction error log because the onhand on the transfer warehouse is less than needed. That happened if the delivered quantity (or a part of it) was former manually completed at the target warehouse.

Correction result: From now the inventory transaction of a delivery order cancelation can be posted as expected, even if the delivered quantity (or a part of it) was completed manually at the target warehouse.

5.1.4    Planning

RFR-016505 Correction

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

Problem: In case items were planned with reservations and with forecasts and a reservation was earlier in a forecast period than a forecast, this forecast was not reduced by the reserved quantity.

Correction result: Reserved quantities of a demand in a forecast period do reduce forecasts at the same day or later in the same forecast period.

5.1.5    Production

RFR-016505 Extension

Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planing actions
Field: Forecasts in time fence
Category: New field

Description: New field has been added to allow user to keep forecasts in time fence for items that has this time fence specified.
This makes that forecasts from time fence will be cumulated and if needed recommendation will be created for them at the first day after time fence ends.

RFR-016505 Correction

Framework: Production
Application: Bills of resources
View: Bill of resources
Action: n.a.
Category: Exception

Problem: Open Bill of resources with routing that has cross-site operation. Without closing already opened BOR open used routing and delete one of the cross-site operation. After coming back to opened Bill of resources an exception occurred.
Same exception occurred after deleting bill of materials line item (It is bill of materials used as line item in another bill of materials).

Correction result: An exception does not occur anymore. Instead an error is displayed about deleted line item which is the same solution as for deletion of operation or external operation from routing or material from bill of materials.

5.1.6    Sales

5.1.6.1      Sales – General

RFR-016505 Extension

The following new attributes have beed added:
– Confirmation and ProformaInvoice: new attributes “generationStatus” and “levyDeterminationDate”
– ConfirmationDetail and ProformaInvoiceDetail: new attributes “levyDeliveryPartnerData” and “levyValidityDate”
Please note that the “levy…” attributes will be used only if levies are used (currently not available) and the usage of “generationStatus” will be added later within the release 6.4.
In addition to that, ProformaInvoiceDetail has now in analogy to ConfirmationDetail the new attribute “sourceDetailType”. The value of this attribute will be maintained up from this extension by the “Pro-forma invoice” generation and will be initialized for existing data by the data update application UPDADV116175.

5.1.6.2      Sales orders

RFR-016505 Correction

Framework: Sales
Application: Sales orders
Action: refresh customer outstanding debt
Category: Exception

Problem: By mistake up from the release 6.1 the “refresh customer outstanding debt” logic creates a “currency converter instance” for the financials organization with the method “createSalesInstance”. If the financials organization is not also a sales organization an exception will be thrown by “CurrencyConverter#createSalesInstance”.

Correction result: Now – as in 6.3 – the “currency converter instance” will be created by the method “CurrencyConverter#createInstance” – so the exception does not occur anymore.

5.1.7    Storage Location Control

5.1.7.1      Inventory management server

RFR-016505 Correction

Framework: Inventory management
Application: Inventory management server
View: n.a.
Action: Restart Inventory Management server
Category: Exception

Problem: If a financial organization exists for which no financials function in customizing is available, the inventory management server is terminated with an exception.

Correction result: If a financial organization exists for which no financials function in customizing is available, the inventory management server can still start and sends an error message to the message log.

5.1.7.2      Inventory requisitions

RFR-016505 Correction

Framework: Storage Location Cocntrol
Application: Cockpit: Inventories
View: n.a.
Action: Generate inventory requisitions…
Category: Unexpected behavior

Problem: If the target of a transfer is a structured warehouse and the target storage zone or bin is specified, these data would be ignored.

Correction result: If the target of a transfer is specified, these data will be considered as expected.

RFR-016505 Correction

Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: n.a.
Category: Exception

Problem: Technical problems during the class replacement mechanism.

Correction result: The class com.cisag.app.inventory.location.requisition.log.RequisitionDetailValidation
can be replaced now.

Technical information: The static initializing of Path information caused problems during the RequisitionDetailValidation class replacement mechanism. The static variables declaration is removed now.

RFR-016505 Correction

Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Release of serial number transfer between two warehouses (structured warehouse at the source)
Category: Invalid data

Problem: If several serial numbers assignments with storage bin specification were created only the first serial number would get open outgoing process data. (Seldom use case)

Correction result: Open outgoing process data will be created for every exactly specified transfer transports.

Data update: If necessary, erroneous data can be corrected by using the existing application “Correct voucher data and reservations” which should be restricted for the concrete source side.

RFR-016505 Correction

Framework: Inventory Management
Application: Inventory requisitions
View: Manual Stock Movement
Create a line item for a virtual warehouse
Category: Unexpected behavior

Problem: It was not allowed to transport inventory from or to a virtual warehouse although manual inventory postings supported this business case.

Correction result: With the use of inventory requisitions it is now possible to create transports for virtual warehouses.

5.1.7.3      Storage locations

RFR-016505 Correction

Framework: Inventory Management
Application: Receitp of goods
View: n.a.
Search-Action: “Find and add storage locations…” within the dialog “Assign storage locations”
Category: Unexpected behavior

Problem: The performance of the search action is worth for a big amount of partners.

Correction result: The performance of the search action is increased for a big amount of partners.

5.2        System development

RFR-016504 Extension

Update of the library of crystal report.

5.2.1    Application server

5.2.1.1      Autorizations

RFR-016503 Correction

Process: Update of authorization roles
Category: Invalid data

Problem: After any capability of an authorization role is changed on one application server, this exception can occur on other active application servers of the system: “Exception in shared cache object change listener, java.lang.IllegalArgumentException: Parameter guid must not be null”. The capability update is not accounted for in subsequent logins.

Correction result: Updated capability is available on other application servers.

5.2.2    Repository

RFR-016503 Correction

Framework: Software development
Action: Installing language refreshes
Category: Unexpected behavior

Problem: If you install an old language refresh it can happen that effectively older text versions become active.

Correction result: The version of the imported text is now compared to the version of the existing text if present. The newer one will become active.

5.2.3    System – General

RFR-016503 Correction

Framework: n.a.
Application: All of report output application
View: n.a.”
Action: Save, Validate
Category: Exception

Problem: Exception will be thrown on validate or save action, if the user want to create a new report output and the report title field contains more than 50 characters.

Correction result: Error message will be sent if the report title field contains more than 50 characters.

5.2.4    Workflow

5.2.4.1   Process definitions

RFR-016503 Correction

Framework: Workflow
Application: Process Definitions
View: n.a.
Action: Refresh
Category: Exception

Problem: The Method TaskList.recordAction(int action, CisParameterList parms, String description, boolean persistent) handled only null String objects. This led to the error in the further processing in UserHistorySupport.recordAction(…) method.

Correction result: No exception.

Technical information: StringUtilitiy. isEmpty(String) function fixes this issue.

RFR-016503 Correction

Framework: Workflow
Application: Activities
View: n. a
Action: Refresh (in Activities) or upon pressing “Open” on the corresponding node under “Process model” tab in Processes application.
Category: Exception

Problem: In ActivityDefinitions application: If a string, longer than 255 characters, is set as a value of a TextField in “Declarations” tab, then upon opening “Activities” application comes out a DLG-00001 error message.

Correction result: DLG-00001 appears no longer. Now, one can set results of the “TextField” type with long strings. and viewed it fully after the end of an activity.

Technical information: The solution is temporary.