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

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

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

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.

UPDSUP113635

Goods receipts for distribution – return of goods type

In all goods receipts for distribution orders of type ‘return of goods’ the data of the attribute com.cisag.app.purchasing.obj.ReceiptOfGoods:supplierData will be moved to the attribute com.cisag.app.purchasing.obj.ReceiptOfGoods:customerData. That will be done by copying the partner GUID, name and address from OrderSupplierDataInfo to a new instance of the part OrderCustomerDataInfo and storing the GUID via hash code logic to com.cisag.app.purchasing.obj.ReceiptOfGoods:customerData. The attribute com.cisag.app.purchasing.obj.ReceiptOfGoods:supplierData will be set to null. Furthermore the attribute com.cisag.app.purchasing.obj.ReceiptOfGoods:invoicingOrganization will be updated with the value com.cisag.app.sales.obj.ShippingOrder:invoicingParty of the corresponding delivery order.

5              Contained changes and extensions

5.1        Application development

RFR-016466 Correction

Framework: Inventory management
Application: All applications that can save incoming postings. In our case it was the receipt of goods for production order.
View: Production
Action: Post receipt of goods…
Category: Unexpected behavior

Problem: If the incoming posting was reserved against a demand origin and the conversion factor was unfavorable, the reservation may have had an unallowed number of decimal places.

Correction result: Reservations against receipts are now also rounded correctly.

RFR-016466 Correction

Several texts have been updated regarding company name.

RFR-016466 Documentation

Text corrections (German only).

RFR-016466 Ergonomics

Glossary texts have been updated regarding the company name.

RFR-016466 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.

5.1.1    Base

5.1.1.1      Classifications

RFR-016466 Correction

Framework: Base
Application: Reorganize classifications
View: n.a.
Action: Execute reorganize classifications
Category: Unexpected behavior

Problem: When executing reorganize classifications, the operation will be interrupted if the objects to be reorganized are more than 128.

Correction result: The Problem is fixed.

Technical information: The Method “com.cisag.app.general.log.HierarchyReorganization.TypeMetaData. getEntity(byte[])” checks also whether top level transaction has been changed or not.

5.1.1.2      Contracts/RFQs/Quotations/Orders

RFR-016466 Correction

Class: com.cisag.app.general.order.log. EntityUtility
Method: prepareChange

Problem: If the specified entity instance contains already an acquired lock that belongs to the specified header guid the method “prepareChange” releases by mistake also its own logical lock so that the performed functionality will be executed without a logcal lock.

Correction result: Now the “prepareChange” method works also as expected in this case.

RFR-016466 Documentation

Following help documents have been created (German language versions):
– Voucher Reorganization Settings/Historical Data
– Cockpit: Historical Sales Orders
– Import Historical Sales Orders
– Reorganize Historical Sales Orders
Following help documents have been updated to include historical sales orders (German language versions):
– Retention Categories Associations/Orders
– Action: Find and Add Line Items
– Voucher References Chain
– Reorganize Sales Orders

5.1.1.3      Customizing

RFR-016466 Correction

Framework: System Management
Application: Customizing production
View: Documents
Action: n.a.
Category: Unexpected behavior

Problem: New location: When activating the checkbox “Use OLTP client data” an error message appears (PRD-2202), although the templates are available and saving would be possible.

Correction result: New location: When activating the checkbox “Use OLTP client data” and the templates are available saving is possible.

5.1.1.4      Item characteristics

RFR-016466 Extension

Class: com.cisag.app.general.item.log. ItemPropertyEntity
Method: update

Description: In addition to the existing method “public boolean update()” the new signature “public boolean update(boolean topLevelTxn)” has been added.
By the new signature you can specify if a top level or a sub level transaction will be used.

RFR-016466 Correction

Framework: Base
Applications: “Item characteristics” and “Item-characteristics assignments”
Action: Validate
Category: Unexpected behavior

Problem: If an “Item characteristic” with the type “Quantity” is present and has a zero value (without “unit of measure”) the entity extension attribute “com.cisag.app.general.extension.obj.Datatype. isDefaultValueDefined()” is present with the value “true” – so such an “Item characteristic” cannot be defined as “variant item usage”.

Correction result: Now such a quantity value will be accepted by the “Item-characteristics assignments” application as “no default value present”.
Also now a change to a real “not empty” default value will be determined by the “Item characteristics” application.
In addition to that, the size of the “reference item” data table has been changed to 5 visible rows (even if the current data is not a reference item).

5.1.2    Inventory management

5.1.2.1      Delivery orders

RFR-016466 Correction

Framework: Inventory
Application: Delivery orders, goods receipts
View: n.a.
Action: Complete delivery order and output delivery slip … (and create goods receipt for the target organization)
Category: Exception

Problem: An exception occurred creating the delivery slip for a return of goods of a distribution order. That happens because the process wanted to access ‘distribution’ customizing data of the target organization of the distribution process. Maybe these are not defined. Moreover, the goods receipt for the return process wanted to access supplier data of the target organization of the distribution process. Maybe that is not defined too.

Correction result: From now creating the delivery slip for a return delivery of a distribution order will work as expected. The delivery process for a return delivery of a distribution will access ‘distribution’ customizing data of the source organization of the original distribution process. Moreover, the goods receipt for the return process will access customer data of the target organization of the original distribution process.

Technical information: From now a goods receipt for a return of goods from a distribution process will reference customer data instead of supplier data. The field ReceiptOfGoods:supplierData will be NULL, the field ReceiptOfGoods:customerData will take the customer information.

Data update: UPDSUP113635

RFR-016466 Correction

Framework: Inventory,
Application: Delivery orders
View: n.a.
Action: “Complete delivery and print delivery slip …”
Category: Exception

Problem: An exception occurred completing the delivery of delivery slip details, that contains an item of the type ‘Serial number without inventory management’ in a distribution process. The exception occurred if the option ‘Assign non-inventoried serial numbers’ is deactivated in the distribution order type of the distribution order that is delivered.

Correction result: From now the delivery of delivery slip details, that contains an item of the type ‘Serial number without inventory management’ in a distribution process, will work as expected.

5.1.2.2      Inventory management – General

RFR-016466 Correction

Class: com.cisag.app.shipping.unitload.log.VersionUtility
Method: com.cisag.app.shipping.unitload.log.VersionUtility.archive(UnitLoadDetail, byte[], byte[], byte[], byte[])

Description: The flag com.cisag.app.shipping.obj. UnitLoadDetail:correctionExisting was copied when a new Version is created. That is not a correct behavior because the new version will not contain any corrections. They will not be copied to the new version. The flag must be always false in the new version.

5.1.2.3      Inventory posting query

RFR-016466 Correction

Framework: Inventory Management
Application: Cockpit: Inventory postings
View: Standard
Display of inventory count inventory postings
Category: Ergonomics

Problem: For inventory postings which were created by an inventory count the inventory count itself was not displayed anywhere.

Correction result: The cockpit search gets a new inventory count detailed info search that offers additional information about inventory counts.

5.1.2.4      Reservations

RFR-016466 Correction

Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Save and report
Category: Unexpected behavior

Problem: If the proposed identifier was changed and the new identifier was tentatively reserved in some cases the new identifier could not be reserved. The reason was an obligated inventory packaging within another order demand (e.g. sales order line item) but without a specified identifier.

Correction result: The possibility to redistribute tentatively reserved inventory packaging has been extended.

5.1.3    Planning

5.1.3.1      Material requirements planning

RFR-016466 Correction

Framework: Planning
Application: Material requirements planning
View: n.a.
Action: …execute planning
Category: Unexpected behavior

Problem: If at begin of planning there is a surplus of quantity and receipts are in pre period, this receipts may get conflict “Order/recommendation not required”.
This conflict is assigned to those receipts which still do not turn surplus into an under run of quantity when surplus is diminished by quantity of receipt.
Basis of this proof is the onhand quantity at start of planning. This quantity is not calculated correctly so that the conflict may not be assigned to receipts of pre period properly.

Correction result: Onhand quantity at start of planning is calculated correctly and conflict “Order/recommendation not required” is assigned properly to receipts of pre period if necessary.

5.1.3.2      Planning – General

RFR-016466 Correction

Framework: Planning
Application: Cockpit: Planing results material
View: table
Action: n.a.

Category: Ergonomics

Problem: A technical field “APS result, material line items” could be selected as a column. This is not intended.

Correction result: Field “APS result, material line items” cannot be selected as column anymore.
Further changes:
– column width of table columns adjusted.
– as cockpit mainly is intended to display results of a planning simulation value assistant for choosing a material requirements planning is now a dialog where simulations can be selected
– main sorting is now column “Due date”, descending.

5.1.4    Production

5.1.4.1      Production – General

RFR-016466 Correction

Framework: Production
Application: Purchasing recommendations
View: n.a.
Action: Generate purchase orders
Category: Unexpected behavior

Problem: Due to a lack of LOCK control, purchasing recommendations can be processed multiple times.

Correction result: A LOCK control now in place prevents purchasing recommendations from being processed more than once.

RFR-016466 Correction

Framework: Production
Application: Order maintenance, Rejects Postings
View: Order maintenance: Header view(General), Rejects posting: working area
Action: na.
Category: Unexpected behavior

Problem: A production order’s quantity can be specified in base unit of measure item (product) or of any specified inventory packaging unit of item (product).
1. Value assistant of field “Target quantity” of a Production order only shows base unit of measure of product.
2. Value assistant of field “Scrap quantity” of application “Rejects Posting” only shows base unit of measure of product.

Correction result: In context 1 and 2 beneath base unit of measure of product value assistant also shows allowed inventory packaging units of the product.

5.1.4.2      Production order types

RFR-016466 Correction

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

Problem: The field reservation time point is displayed as not relevant (all grey) as soon as an order has been saved for the type. Since the setting is relevant in the case of “automatic reservation” according to the field reservation category, it should be displayed with black font.

Correction result: The field reservation time point is generally displayed as relevant (with black font), if “automatic reservation” is set in the field reservation category.

5.1.4.3      Production orders

RFR-016466 Correction

Framework: Production
Application: Order maintenace. Cockpit: Production orders
View: n.a.
Action: Calculate availability…
Category: Unexpected behavior

Problem: Overdelivery of picking is active. A production order has one of more picking orders in process (that means: not yet completed of canceled).
If now “Calculate availability…” with “Determine available production warehouse quantity” or “Release excess production warehouse quantity” is executed, availability details are created with respect to the production order details for which picking orders are in process.
This is due to a wrong picking status of production order details for which picking orders are in process. The wrong status is set in the course of execution or “Calculate availability…” with above mentioned modes.

Correction result: In above described context “Calculate availability..” works as expected for both mentioned modes. Picking status of production order details is not changed to a wrong value in the course of calculating availability.

RFR-016466 Correction

Framework: Production
Application: Order maintenance
View: Material list view, material detail
Action: Save
Category: Unexpected behavior

Problem:
Context: Production order with picking context and over delivery of picking. There is surplus quantity at production warehouse.
A. Issue warehouse of a material is changed to production warehouse.
Result: Quantity “Available at production warehouse” in list view of application Order maintenance is not initialized to zero.
B. Issue warehouse (which is now production warehouse) is changed back to former issue warehouse or another issue warehouse.
Result: Change of warehouse saved but availability does not change accordingly (Availability of production warehouse is missing).
Please note: B can also be achieved if issue warehouse is production warehouse at creation time and is changed to another issue warehouse after saving.
C. A material line item is added to PO with identifier defined. Surplus quantity at production warehouse for this identifier exists. Surplus quantity is assigned correctly.
Specified identifier is removed, PO saved. Surplus quantity is assigned correctly without identifier.
Specified identifier is specified a new, PO saved. Surplus quantity is not anymore assigned. Demand is now set for issue warehouse.
D. A material line item is added to PO with identifier defined. No surplus quantity at production warehouse for this identifier exists. Reservation/availability is done correctly at issue warehouse.
D1. Change identifier at line item. New identifier has no surplus at production warehouse but availability at issue warehouse. Exception occurs on save.

Correction result: In above described context change of issue warehouse works as expected.
A. Quantity “Available at production warehouse” is initialized to zero
B. Availability is changed accordingly to new warehouse of material.
C Surplus quantity at production warehouse is assigned properly (reservation and/r availability) to production order detail when identifier is set anew.
D1. Identifier can be added. No exception occurs. Availability/Reservation is set properly at issue warehouse.

5.1.4.4      Where-used list

RFR-016466 Correction

Class: com.cisag.app.general.partner.ui.DeliveryDataComponent
Method: createGroupBox()

Description: A correction of the data view path of the field ‘deliveryTerms’ was needed.

5.1.5    Purchasing

5.1.5.1      Purchase orders

RFR-016466 Correction

Framework: Purchasing
Application: Purchase orders
Action: Save
Category: Unexpected behavior

Problem: Because of a “Reservation API” change the purchase order application creates “Outgoing availability/reservation data” also if not needed.

Correction result: Now the data will be created only if needed.

Hint: Please note that – as before – existing data, that is not needed any more, will not be deleted.
In addition to that the class “com.cisag.app.inventory.reservation.log.OriginWrapper” has been changed to avoid a problem with “com.cisag.app.inventory.reservation.obj.DemandOrigin:firstSubKey”.

5.1.6    Sales

5.1.6.1      Sales – General

RFR-016466 Correction

Framework: Sales
Applications: Customer proposals, Sales orders
Action: “Select delivery customer address”
Category: Invalid data / Unexpected behavior

Problem: The functionality “Select delivery customer address” was available also for kit components. But the data needs no be changed only by the kit main detail.

Correction result: Now the functionality “Select delivery customer address” is not available any more for kit components.

RFR-016466 Correction

Framework: Sales
Applications: “Sales rapid documents”, “Sales requests”, “Customer proposals” and “Sales orders”
Action: Search sales representative
Category: Unexpected behavior / Ergonomics

Problem: The “Sales representative” value help does not consider the “Sales representative origin” as specified by the relevant type instance.

Correction result: Now “Sales representative origin” will be considered as expected.

5.1.6.2      Sales orders

RFR-016466 Correction

Framework: Sales
Applications: Customer proposals, Sales orders
Action: Apply defaults
Category: Exception

Problem: If a header or line item uses as “Purchasing link” the value “External third-party order” and the “Purchasing organization” field contains a value that is not a purchasing organization and the sales organization is not also a purchasing organization an exception occurs.
The same problem occurs if the “Purchasing link” has the value “Return to supplier”.

Correction result: Now the exception does not occur any more.

RFR-016466 Correction

Framework: Sales
Applications: Customer returns, Sales orders
Action: Change generated orders by “Customer return” application
Category: Unexpected behavior
Problems: If an order line item is present that was generated by a customer return and needs to be canceled an error message (“GEN”, 5937“) occurs if the present order line item price has more decimal places than defined for amounts in the relevant currency.

Correction result: Now this error message does not occur any more in this case.

5.1.7    Storage Location Control

5.1.7.1      Inventory orders

RFR-016466 Correction

Framework: Storage Location Control
Application: Picking orders
View: Picking
Action: Generate inventory orders…
Category: Exception

Problem: If the quantity to be transported had a parallel unit that cannot be calculated based on an inventory packaging without rounding the inventory order could not be created correctly.

Correction result: The parallel item unit will be rounded too and the inventory order can be created as expected.

5.1.7.2      Inventory requisitions

RFR-016466 Correction

Class: com.cisag.app.inventory.log. LoadingUnitLogic
Method: readLoadingUnit(InventoryCharacteristicsView, byte[])

Description: If the InventoryCharacteristicsView guid-Attribute is not set (e.g. only a copy) the loading unit is tried to be read using the other functional attributes from the InventoryCharacteristicsView.

5.1.7.3      Storage location reservations

RFR-016466 Correction

Framework: Inventory management
Application (Hidden): Correct voucher data and reservations
View: n.a.
Action: &Correct incorrect data…
Category: Invalid data

Problem: If there was an open shipping order cancelation the correction application would try to create incoming movement data although this process never used stock movement data.

Correction result: The correction application will not try to create incoming movement data for an open shipping order cancelation.

5.1.7.4      Withdrawal restrictions

RFR-016466 Correction

Framework: Storage Location Control
Application: Withdrawal restrictions, Put-away restrictions
View: n.a.
Action: Enter
Category: Unexpected behavior

Problem: The “Enter” action (press Enter button) was not similar to the “Load” action.

Correction result: To load a new warehouse restriction (put-away or withdrawal) either the “Enter” button or the “Load” action can now be used as expected.

5.2        System development

RFR-016464 Correction

Several texts have been updated regarding company name.

RFR-016464 Correction

Framework: Software development
Application: ODBC driver 32 bit
View: n.a.
Action: n.a.
A memory access error occurs while using the driver.
Category: Unexpected behavior

Problem: A memory access error occurs while using the driver.

Correction result: The error does not occur anymore.

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

Copyright file has been updated regarding company name.

RFR-016464 Documentation

Text corrections.

5.2.1    Application server

5.2.1.1      User settings

RFR-016463 Correction

Framework: System management
Application: Customizing
View: User settings for the System / Keyboard shortcuts
Action: Find and add action(s), Save and more
Category: Exception

Problem: When trying to change the keyboard shortcut settings for the system in the Customizing application, an exception may occur.

Correction result: Fixed.

Technical information: The cause was due to incomplete data stored in the customizing.