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

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

• 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.

UPDProxyBOs

“Proxy business objects” are on the OLTP database the proxies for business objects from the repository database and the configuration database. With them, information from the repository or configuration database can be offered in a search. For example, this information can be used to tell the user which user created an object or was the last user who changed it.

With this data update, these objects can be updated on the OLTP database. No logic can or should be based on proxy business objects. Their sole purpose is to be displayed in cockpits.

UPDSUP107310

Setting a correct data in empty title in greeting formula.

Greeting formula with empty title has an invalid guid. This Update will change this guid to Zero guid.

• Contained changes and extensions

5.1        Application development

RFR-016408 Correction

Framework: Base
Application: Partners
View: Financials data
Action: n.a.
Category: Ergonomics

Problem: Since release CEE 6.2 the field “IBAN” at the tabbed pane “Bank assignments” is no longer set to the “upper case” mode.

Correction result: From now the field “IBAN” at the tabbed pane “Bank assignments” will be set to the “upper case” mode as expected.

RFR-016408 Documentation

The following help documents have been corrected regarding the technical names and descriptions of the virtual functions: Ursprungsbeleg/Sammellieferung auf Ladeeinheiten-Etikett (was: Sammellieferung bei dem Etikettendruck)
Sammellieferungsinformation auf Warenabgangsschein (was: Sammellieferung)

RFR-016408 Ergonomics

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

RFR-016408 Correction

Framework: Calculation
Application: Trade cost calculations
View: n.a.
Action: Calculate
Category: Exception

Problem: A kit is calculated by Valuation price “Calculation of kit components”. At least one component is an item to be purchased. Item has no sales view. For the purchasing item a trade cost calculation of category “Trade cost calculation purchasing items” is performed automatically (due to specification “Calculation type of purchasing item” of used calculation schema).
After calculation application “Trade cost calculations” is refreshed. While refreshing an exception occurs and application terminates uncontrolled.
Reason is, that column “Calculation category” of tab “Calculation information components” has an improper restriction of allowed values of asigned value set to be displayed. The value “Trade cost calculation purchasing items” is not allowed for the column field. The value of column “Calculation category” has been set wrong if component had a sales view. Then value was set to “Trade cost calculation sales item” despite usage of a calculation of category “Trade cost calculation purchasing items”.

Correction result: In above described context after calculation of kit no exception occurs and trade cost calculation is displayed properly. Especially column “Calculation category” of tab “Calculation information components” has proper value and no more restriction of allowed values.

RFR-016408 Correction

The help document “Lagerorte importieren” has been updated regarding Cross-Docking-functionality and divided put and picking strategies (Einlager- und Auslagerstrategie).

5.1.1    Base

5.1.1.1      Company calendars

RFR-016408 Correction

Framework: Base
Application: Company Calendar
View: n.a.
Action: Duplicate Calendar
Category: Ergonomics

Problem: The NLS-Data was not copied to the calendar copy. Therefore an error message was displayed after duplicating an existing calendar, that the description in language “X” is not defined.

Correction result: From now the NLS-Data will be copied as expected. The error message will not be displayed after duplicating an existing calendar.

5.1.1.2      Fiscal years

RFR-016408 Correction

Framework: Base
Application: Fiscal years
Action: Next period set status
Category: Exception

Problem: If a FiscalPeriodSet has already the status “Closed” (e.g. because of parallel processing) since some time an error message (“GEN, 9217”) occurs during the try to set the next status (before that an exception occurs). But this error message contains a wrong text – it says that the status of the “Fiscal year status” line item” (“ClosingSetDetail”) will be changed but the relevant logic tries to change the FiscalPeriodSet status; also the error message does not contain the relevant usage context of such a FiscalPeriodSet (e.g. “ERP”).

Correction result: Now the error message “GEN, 9217” is marked as deprecated; instead the new error message “GEN, 9232” will be send that contains also the relevant usage.

5.1.1.3      Item characteristics

RFR-016408 Extension

Framework: Base
Application: Cockpit: Item characteristics
Actions: “Suggest &destination data”, “Empty destination data”, “Release destination data”, “Reverse releasement of the target data”
Category: Unexpected behavior / Ergonomics

Problem: The listed actions have a wrong direct help (copy&paste error).

Correction result: Now the wrong direct helps has been removed and will be filled later.

RFR-016408 Correction

Framework: Base
Application: Item/Item characteristic assignments
Category: Unexpected behavior / Ergonomics

Problem: If an “Item characteristic” is configured as “Value list” and the type is “Business object” the relevant field does not have the dialog button to enter multiple values.

Correction result: Now the field works as expected.

5.1.1.4      Items

RFR-016408 Correction

Framework: Base
Application: Items
View: n.a.
Action: n.a.
Category: Exception

Problem: An exception occurred when the user wanted to step from item number field to the application ‘Item characteristics’ per context menu if the item number field was not filled with a number.

Correction result: From now the step to the application ‘Item characteristics’ per context menu will work as expected.

5.1.2    Financials

5.1.2.1      Nominal ledger postings

RFR-016408 Correction

Framework: Inventory management
Application: All applications that creates inventory postings, e.g. inventory postings.
View: n.a.
Action: Save
Category: Unexpected behavior

Problem: The fiscal period was determined using a date that corresponds to the time zone of the site. This may have determined an incorrect fiscal period.

Correction result: The fiscal period is now determined with a date that has the time zone of the associated financial organisation.

5.1.3    Inventory management

5.1.3.1      Calculate inventory values

RFR-016408 Correction

Framework: Inventory Management
Application: Cockpit: Current inventory values
Action: Excel export
Category: Invalid data / Unexpected behavior / Ergonomics

Problem: The cockpit supports some columns that belong always to the first “Primary currency”. But if such data is exported to excel the contained data belongs sometimes to the second or third “Primary currency”.

Correction result: Now the excel data contains the expected data.

5.1.3.2      Delivery orders

RFR-016408 Correction

Framework: Sales, Inventory
Application: Sales orders, delivery orders
View: n.a.
Action: n.a.
Category: Invalid data

Problem: The empties calculation used for sales and delivery orders did not consider the sales item flag ‘Empties’.

Correction result: From now the empties calculation used for sales and delivery orders will consider the sales item flag ‘Empties’ as expected.

5.1.3.3      Picking orders

RFR-016408 Documentation

The help document “Virtuelle Tabelle: Kommission” (German language version) has been provided.

5.1.3.4      Receipts of goods

RFR-016408 Correction

Framework: Inventory
Application: Receipts of goods
View: Customer return of goods
Action: Book
Category: Unexpected behavior

Problem: If a receipt of goods is present that is based on a customer return with an item reference only (without sales order line item reference) the attributes “cost centre” and “cost objective” are not determined as expected to be used by the inventory transaction.
If one of these fields is required with respect to the inventory transaction type, the receipt of goods can not be booked. Also, the empty data might not match in all cases to the used financials system configurations.

Correction result: Now both attributes are determined in analogy to a sales order line item.

Please note the following hints:
– The sales organization and customer are known by the receipt header
– As financials organization the financials organization of the sales organization will be used
– The customer will be used also as “delivery customer” and “invoice customer”
– As “calculation date” the current time stamp will be used
– As “validity date” the receipt of goods date will be used
– As “transaction accounting classification” an empty value will be used
– The item is specified by the receipt detail line item

5.1.4    Production

5.1.4.1      Production – General

RFR-016408 Correction

Framework: Production
Application: Production order
View: n.a.
Action: Delete
Category: Exception

Problem: A configuration rule has one or more characteristics. They are all deleted. Configuration rule is still used for production items. If a production order using such an item is cretated and saved, a subsequent deletion fails because of an exception and application “Production orders” stops with fatal error. Same exeption occurs if an existing production order using this configuration rule is deleted.

Correction result: In above described context, deletion of a production order works as expcted. No exception occurs.

Please note: If a configuration rule is set up without characteristics (that means: none created and hence removed), above described exception does not occur when deleting a production order using this configuration rule.

5.1.5    Purchasing

RFR-016408 Correction

Framework: Purchasing
Applications: Purchasing RFQs, Supplier quotations, Purchase orders
Action: Find and add line items
Category: Invalid data / Unexpected behavior / Ergonomics

Problem: For the “Original voucher” value “Sales quotations” (base or line items) the field “End consumer prices” is visible and used (in contrast to “Sales orders”).

Correction result: Now the field “End consumer prices” is not visible and not used as expected also for “Sales quotations”.

5.1.5.1      Purchasing RFQs

RFR-016408 Correction

Framework: Purchasing
Application: Purchasing RFQs
Action: Find and add line items
Category: Invalid data / Unexpected behavior

Problem: In contrast to the release 6.0 the functionality “Find and add line items” with the target “Purchasing RFQ” and the sources “Customer proposal” and “Sales order” does not create order reference chain entries.

Correction result: Now the order reference chain entries are created as expected.

5.1.6    Sales

5.1.6.1      Customer invoices

RFR-016408 Correction

Framework: Sales
Application: Sales orders, Distribution orders, Customer invoices
Action: Create and cancel customer invoices
Category: Invalid data / Unexpected behavior

Problem: A sales order line item is present with the following configuration:
– The sales order type uses end consumer prices (retail prices).
– The sales order uses the price calculation “Net”.
– The sales order line item contains some “Order line item value discounts” and for such discount an account is defined with respect to the account classification that is specified within the relevant “Sales price component type”.
If such an order line item is invoiced, the invoice generation refreshes the order line item considered “Order line item value discounts” with wrong values. Instead using the “Order line item value discounts with tax” (as specified by the order) the “Order line item value discounts without tax” will be used as considered “Order line item value discounts”.So following invoices are using the wrong considered “Order line item value discounts” data.

Correction result: Instead of the (wrong) attributes “CustomerInvoiceDetail:calculatedDetailDiscountValues[0..3]” now always the attributes “CustomerInvoiceDetail:calculatedDiscounts[0..3]” will be used.

Please note that the relevant logic was changed for all cases and not only for the wrong case. Also the logic of distribution orders have been changed in analogy.

Data update: If needed, wrong existing data have to be changed manually. The recommended way is the following:
– Cancel all invoices of the relevant order line items.
– if “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount” is present for the relevant sales order line items: set “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[0]” until “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[3]” by OQL for the entry with the relevant order detail guid to zero.
– Create the invoices again.

5.1.6.2      Pro forma invoices

RFR-016408 Correction

Framework: Sales
Application: Pro-forma invoices
Action: Print
Category: Invalid data / Unexpected behavior

Problem: The “Pro-forma invoice” standard report does not print classification and order value discounts in case of “gross” kind of pricing.

Correction result: Now these discounts are printed as expected.

5.1.6.3      Sales orders

RFR-016408 Correction

Help document “Einführung: Frachtkosten” (German language version) has been updated regarding third-party orders and distribution orders.

5.1.6.4      Sales prices

RFR-016408 Extension

Framework: Sales / Purchasing
Application: Sales price lists / Purchasing price lists
View: n.a
Action: Search and insert items
Category: New action

Description: The new action ‘Search and insert items’ makes it possible to add a new price definition for more than one item simultaneously.

5.1.7    Workflow Management

RFR-016408 Correction

Framework: General
Application: Greeting formulas
View: n.a.
Action: save, validate, accept
Category: Unexpected behavior

Problem: Field title is mandatory.

Correction result: Field title is not mandatory.

Data update: com.cisag.app.update.log.UPDSUP107310 Greeting formula with empty title has an invalid guid. Update will change this guid to Zero guid.

5.2        System development

RFR-016407 Ergonomics

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

RFR-016407 Correction

Framework: Software development
Application: Cockpit : Production level development objects
View: n.a.
Action: Activate tasks
Category: Action changed

Description: Activating tasks now runs via a restartable batch application. Therefore it is now possible to trigger a background application.

Technical information: Due to technical reasons is it necessary to explicitly specify the server where the background task shall be running.
Either by using a job queue that is dedicated to a server or if using a distributed job queue by specifying the server.

RFR-016406 Correction

Framework: Software development
Application: User defined attributes
View: n.a.
Action: Creating new attributes
Category: Unexpected behavior

Problem: Due to a missing validation it was possible to create attributes starting with a capital letter.
This lead to problems in the dataview using the business object.

Correction result: Now a validation prevents creating attribute with names starting with a capital letter.

RFR-016406 Correction

Framework: System Management
Action: Cache reacting on Supplement
Category: Unexpected behavior

Problem: If there is a registered OLTP cache on a business object and there is a supplement for this business object defined and the supplement is treated directly, then the cache did not react if only the supplement is changed.

Correction result: A registerd cache for a business object now reacts on the change of a connected supplement.

5.2.1    Data exchange

RFR-016406 Correction

Framework: System Management
All BIS import applications
Category: Unexpected behaviour

Problem: In rare cases BIS imports may report an error message BIS-42 “Error while generating the error file”. The data may have been imported correctly despite this message, but the error file may be incomplete.

Correction result: A possible cause for this error was corrected to avoid the message in a certain case. This correction may help identifying other import errors.

5.2.2    GUI

RFR-016407 Correction

Framework: All
Application: Applications with customizable tables
View: n.a.
Action: Hide all detail views
Category: Unexpected behavior

Problem: The text for the action “Hide all detail views” was not taken from the development object (com.cisag.sys.gui.CustomizableTableHideAllDetailViewsAction), but hard coded to “Alle Detailansichten ausblenden”. Additionally, the texts in the development object were not correct. They were refering to “detail searches” instead of “detail views”.

Correction result: Fixed.

RFR-016406 Extension

Framework: All
Application: UI applications with “ident pane”
View: n.a.
Action: n.a.
Category: UX

Description: A dragable divider (“splitter”) between ident and work pane is now provided, to allow to change the heights of these panels on demand.

Technical information:
– Not all UI applications are using the ident pane. The divider will only be added, if the ident pane is used.
– The divider considers the minimum and maximum height of the ident pane and will only be added, if these sizes indicate, that resizing of the ident pane is allowed.

5.2.3    Kernel

5.2.3.1      Data types/data structures

RFR-016406 Correction

Framework: Storage location control
Application: Storage locations
View: n.a.
Action: Validate
Category: Unexpected behavior
Message KRN-00408 is sent, but no string starts with a blank.

Problem: The validaion is wrong.

Correction result: The message is not sent if no string starts with a blank.

5.2.4    Repository

RFR-016406 Correction

Framework: Base
Application: Partners
View: Base
Action: Validate
Category: Exception

Problem: if an incorrect email address, such as “. text@comarch.com”, is checked, an exception occurs.

Correction result: Message KRN-00407 is sent.

5.2.5    System – General

RFR-016406 Correction

Framework: System Management
Application: Output report documents in the batch
Category: Unexpected behavior

Problem: When outputting specific reports in the batch application “Output report documents in the batch”, an error message KRN-41, “Data description :.lt does not exist”, could appear if parameter fields were empty. No document is created. The problem does not appear in dialog application “Output report documents”.

Correction result: The problem is resolved.

5.2.6    Workflow

RFR-016406 Correction

Framework: Workflow Management
Application: Activities
View: n.a
Action: validate
Category: Unexpected behavior

Problem: Validating created activity with attachment and Editor Expression using variables defined in activity was unable to find its definition and evaluate.

Correction result: Validating created activity with attachment and Editor Expression using variables defined in activity is now able to find its definiton and evaluate.

RFR-016406 Correction

Framework: Workflow Management
Application: Search for tasks
View: n.a.
Action: start
Category: Unexpected behavior

Problem: Sort by date columns (Start time, End time) has been ignored.

Correction result: Sort by date columns (Start time, End time) works now.