Release	Comarch ERP Enterprise 6.3
Release date	21.07.2023
Reference to other documents	You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.   This fix comprises the following support deliveries: RFR-016448 – RFR-01650   Information about the features of Comarch ERP Enterprise 6.3 (release news): ·         INF- 002654 Release-News: Betriebswirtschaftliche Lösungen ·         INF-002656 Release News: Business Solutions ·         INF- 002655 Release-News: Technische Lösungen ·         INF-002661 Release-News: Technical Solutions   System requirements: ·         INF-002659 Systemvoraussetzungen Comarch ERP Enterprise 6.3 ·         INF-002660 System Requirements Comarch ERP Enterprise 6.3   To install the support deliveries, please use the following documentation: ·         “Introduction: Software Logistics” (German language version) ·         „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.   The cumulative installation of support deliveries is described in INF-000228.   In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”.

 

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

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

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

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.

UPDBUG027886

Convert invalid values in ResourceType field in BO Resource.

UPDADU107777

Update the “Origin” field of the trade cost calculations.

The data update defines the “Origin” field of the trade cost calculations, if this field is not already defined, as follows: “Manually defined supplier” if a supplier is specified in the trade cost calculation and “No supplier” if no supplier is specified in the trade cost calculation.

• Contained changes and extensions

5.1        Application development

RFR-016450 Correction

Framework: Inventory
Application: Loading units
View: n.a.
Action: n.a.
Category: Exception / Unexpected behavior

Problem:
1. The time zone of the date fields in the application were not initialized correctly after starting the application without loading the last loaded instance. An exception occurred if the calendar help of these fields were used.
2. It was possible to delete the value in the field ‘order type’ for a detail line in the editor. An exception occurred if such detail was posted from editor to the detail list.

Correction result: From now these errors are corrected. The application will work as expected.

RFR-016450 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-016450 Ergonomics

German user interface text have been updated.

RFR-016450 Ergonomics

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

RFR-016450 Correction

Class: com.cisag.sys.dictionary.log. ObjectDescriptionLogic
Method: isTimeDependent

Description: A inner class determines whether an object is time dependent or not. In case the object is an extension it did not work properly.
The connected business objects determines time dependency not the extension itself.
This has been corrected.

RFR-016450 Correction

Framework: Inventory management.
Application: Inventory postings.
View: Inventory posting.
Action: Save an inventory posting with a unit load specification.
Category: Unexpected behavior

Problem: The content of the loading unit was not checked, so that items could also be used that had no inventory management data. This led to error messages that did not indicate the cause of the error.

Correction result: The contents of the unit load are now checked so that meaningful messages are issued if they contain items without inventory management data.

RFR-016450 Correction

Framework: Sales / Inventory
Application: Customer Returns / delivery orders
View: n.a.
Action: Generate pickup orders
Category: Exception

Problem: An exception occurred generating a pickup order for a customer return, that contained detail lines of mixed reference types (i.e “Sales order” and “Item”).

Correction result: From now generating a pickup order for a customer return will work as expected.

RFR-016450 Correction

Framework: Inventory
Application: Goods Receipts
View: Distribution
Action: n.a.
Category: Unexpected behavior / Ergonomics

Problem: Editing goods receipts in the distribution process had some little errors and ergonomic malpractice.

Correction result: From now goods receipts in the distribution process will work as expected.

RFR-016450 Documentation

The following help documents have been updated regarding current implementation:
– Wareneingänge aus Verteilung
– Vorgehensweisen: Wareneingänge aus Verteilung (not displayed anymore, integrated in “Vorgehensweisen und Aktionen: Wareneingänge)

5.1.1    Base

5.1.1.1      Contracts/RFQs/Quotations/Orders

RFR-016450 Correction

Frameworks: Purchasing, sales
Applications: Proposals and orders
Action: Apply defaults
Category: Exception

Problem: In some cases the method “hasSameReferenceItem” throws an exception.

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

RFR-016450 Correction

1. Reservation API: Framework: Inventory management, Purchasing, Sales
   Applications: All applications that are using the reservation API

   Problem: If a non persistent line item had been deleted and temporary availability data had been activated, the corresponding active zero availability data would have left.

   Correction result: If a non persistent line item is deleted, no active availability data or demand data will remain.

   Data update: A data update application is not necessary those wrong data will be deleted automatically by “Reorganize Availability and Requirement Data”.

   2. Frameworks: Purchasing, Sales
   Applications: Purchasing requests, Sales proposals, Purchase orders, Sales orders, Distributions orders

   Problem: In some cases new sub line items are created temporary and removed and not reused. These new sub line items will not be inserted but the availability and reservation data will be created by the save step.

   Correction result: Now also such data will be marked as “deleted” by the save step – so the availability and reservation data that belongs to such sub line items will not be created any more.

   Data update: See 1. reservation API correction.

RFR-016450 Correction

Frameworks: Purchasing, Sales
Applications: Contracts, Requests, Proposals, Orders, Sales rapid documents, Supplier confirmations
Action: Apply defaults/refresh
Category: Invalid data / Unexpected behavior / Ergonomics

Problem:
1. The sales order, purchase order and distribution order line item quantities will not be refreshed in all cases after a correction of the item master data – so invalid data was saved for persistent line items. In case of new line items, an error message occurs and the item or total quantity requires to be changed to any value and back to the original/needed value.
2. The other documents does not have this error with invalid data but a save is only possible if the item or total quantity was changed to any value and back to the original/needed value.

Correction result:
1. The invalid data error of persistent order line items does not occur any more. In case of new line items with invalid quantities the quantities will now be refreshed before the validation.
2. The other documents are changed in the same way. So also here a manual refreshment is not needed any more in case of a “not convertible quantity” that was corrected by the item master data.

Data update: A data update application is not available. You have to correct wrong order line items manually (change of total quantity uom or amount and back to the original/needed value).

RFR-016450 Correction

Frameworks: Inventory, Purchasing, Sales
Applications: Contracts, Requests, Proposals, Orders, Receipt of goods, Prepayment requests, Customer returns
Action: Import
Category: Invalid data / Unexpected behavior / Ergonomics

Problem: A correction that belongs to the “Handle finish import” topic (e.g. the consideration of the virtual “autoRelease” tag) contains an error so the whole document was marked as “invalid” if any member can not be imported. As result the import error file contains the whole source file even if some members (e.g. details) are imported already successfully. Normally this is no problem but if the source file does not contain line item numbers the line items (details) will be imported multiple times.

Correction result:
1. Now the error does not occur any more (correction in base class).
2. To support the “Handle finish import” functionality the activated virtual attributes will be stored within the error file as extended “header source mark” String and restored before considering the error data (after restoring this extended data the “mark” String does not contain any more the extension – only the header guid – so that after that the normal logic works as before).

Technical information: Please note that the concrete import controllers that belong to these applications have been corrected. So if your import controller implements the method “public boolean handleFinishedImport(OrderEntity entity, Source source)” of the class AbstractOrderEntityImportController a correction might be needed in analogy to the standard corrections.
Also, other clients of the class “com.cisag.app.general.order.log. ImportAutoReleaseSupport” and similar logics might be needed to be corrected.

RFR-016450 Extension

1. Classes:
   – com.cisag.app.general.order.log. DetailsAccess
   – com.cisag.app.general.order.log.SubDetailsAccess
   – com.cisag.app.general.order.log. AbstractDetailsEntity

   Description:
   – The interface DetailsAccess has been extened by the new method “public byte[] getMainDetailGuid(int number)”.
   – The interface SubDetailsAccess has been extened by the new method “public byte[] getSubDetailGuid(int subNumber)”.
   – The class AbstractDetailsEntity implements these new methods.
   – In addition to that the implementation of the method “protected boolean isNumberAlreadyUsed(int number, int subNumber, CisSet removedSubDetailGuids)” of the class AbstractDetailsEntity has been changed so that the internal “main details”/”sub details” structure data is used now instead of the maintenance cache data that would create some more detail object instances.

   2. Class: com.cisag.app.general.order.log.AbstractOrderEntityImportController

   Description:
   2.1 The order import controller base class (e.g. used by sales orders import) considers now for main line items “number” values that belong to transient line items; before this change only persistent main line items were considered. Hint: For sub line items the “subNumber” values were considered already also for transient line items before this change.
   So if the “number” is member of the import file for main line items a main line item can be used multiple times within the same header data block.
   2.2 The internal methods “private static byte[] readMainDetailGuid(AbstractOrderEntity entity, OrderEntityLogic oel, Source mainDetailBiSource)” and “private static byte[] readMainDetailGuid(AbstractOrderEntity entity, OrderEntityLogic oel, Source mainDetailBiSource)” are using now the new methods “DetailsAccess#getMainDetailGuid” and “SubDetailsAccess#getSubDetailGuid” (see 1. above).

   3.
   3.1 Class: com.cisag.app.purchasing.log. Functions – new method “public static PurchaseDiscountUseMutable[] removeDiscountUseDefinitions(PurchaseDiscountUseMutable[] discounts)”
   3.2 Class: com.cisag.app.sales. log.Functions – new method “public static SalesDiscountUseMutable[] removeDiscountUseDefinitions(SalesDiscountUseMutable[] discounts)”

   Description: The classes have been extended by the new method “removeDiscountUseDefinitions”. This method checks if a “price definition” reference is present. If so this reference will be removed and also the attributes “measure” and “scalable” will be set to the value that would be set by the DiscountUseField in case of manual values.

   4. Frameworks: Purchasing, Sales
   Applications: Proposals, Orders, Sales rapid document, Customer returns (sales order generator – header discounts from original order)

   Description: The header and the line item logic of these applications have been changed so that they are using now the new “removeDiscountUseDefinitions” method as provided by the relevant “Functions” class (see 3. above); as result, a change from the discount or price origin type “Definition” or “Definition, Manual” to another value (e.g “Manual”) removes all special values that are present only in the case that the discount was found by the price determination; so a “discount or price origin type change” by a logic will ensure that the discounts data is the same as for the case that the new value was set by the DiscountUseField.

RFR-016450 Correction

Applications: Applications that are based on the base order entity functionality
Action: Free resources
Category: Unexpected behavior

Problem: The “free resources” functionality (Method “com.cisag.app.general.order.log.AbstractEntity#free()”) does not release an acquired lock if the current entity instance was locked by a client.

Correction result: Now the “Free” method releases also the logical locks in this case.

RFR-016450 Correction

Class: com.cisag.app.sales.detailgroup.log. EmptyDetailGroupDocumentData
Method: public NLSData getDescriptionNLSData()

Problem: The method “getDescriptionNLSData()” of the class “EmptyDetailGroupDocumentData” uses before this correcton a NLSData instance that was initialized by a static context but the NLSData instances need a database context (e.g. different languages used).

Correction result: Now the method “getDescriptionNLSData()” considers the current database so that always the NLSData instance will be returned that belongs to the current database.

5.1.1.2      Customizing

RFR-016450 Documentation

The following help documents have been updated mainly regarding “Erledigungstoleranz” (Completion tolerance), German only:
– Artikel, Ansicht “Beschaffung”
– Artikel, Ansicht “Lieferanten”
– Artikel, Ansicht “Vertrieb”
– Artikel, Ansichten “Kunden-Klassifikation” und “Kunden” (new as combination of “Kunden-Klassifikation” and “Kunden”)
– Vorgehensweisen: Artikel, Ansichten “Kunden-Klassifikation” und “Kunden” (new as combination of “Vorgehensweisen: Kunden-Klassifikation” and “Vorgehensweisen: Kunden”)
– Artikeldaten von Kunden und Lieferanten importieren (no content changes)

5.1.1.3      Item characteristics

RFR-016450 Ergonomics

Framework: Base
Application: Cockpit: Item characteristics
View: Characteristic category
Category: Ergonomics

Problem: The data is grouped by type, group and classification but at the end not by the code of the item characteristics.

Correction result: Now the last sort element is the code of the item characteristics.

RFR-016450 Correction

Frameworks: Base, Production, Sales
Applications: “Item characteristics”, “Product configuration rules”, “Production configuration” dialog
Category: Unexpected behavior / Ergonomics

Problem: Up from the release 6.3 the “CONFPROP” functionality did not work as expected.

Correction result: Now the “CONFPROP” functionality works as expected again.

5.1.1.4      Items

RFR-016450 Correction

Framework: Base
Application: Items
View: Customer, Customer classification, Customer disposition
Action: Duplicate
Category: Exception

Problem: An exception occurred executing the “duplicate” action in the views “Customer”, “Customer classification” and “Customer disposition”.

Correction result: From now the duplicate action will work as expected.

RFR-016450 Correction

Framework: Base
Application: Items
View: Base, Purchasing
Action: n.a.
Category: Ergonomics

Problem: In the table of packaging definitions in the base view (field “EAN”) and in the field “EAN” in the view “Purchasing” blanks and hyphens, that are inserted by the user, are not removed automatically. The error message “GEN, 676” appears instead.

Correction result: From now blanks and hyphens that are inserted by the user will be removed automatically in these fields.

5.1.1.5      Organizations

RFR-016450 Correction

Framework: Base
Application: Organizations
View: n.a.
Action: Duplicate
Category: Invalid data

Problem: Duplicating an organization, that is not a company, could cause invalid DefaultPartnerVisibility-Objects if the duplicated organization is made to a company before saving it. The new organization will not be able to get loaded without throwing an exception.

Correction result: From now duplicating an organization will work as expected.

Technical information: A faulty organization that is caused by this error could only get corrected by oql-statement “delete from com.cisag.app.multiorg.obj.DefaultPartnerVisibility dpv
where dpv:financialsOrganization in (select o:guid from com.cisag.app.multiorg.obj.Organization o where o:code = ‘XXX’)”. After doing that, save the organization again or delete it.

5.1.1.6      Partners

RFR-016450 Correction

Framework: Base
Application: Partners
View: n.a.
Action: Create from template
Category: Unexpected behavior

Problem: The message GEN-07138 was displayed for every financials organization that has data containing in the template, if the partner base data validation results in an error message or a warning message – even if the data context is the company.

Correction result: From now the message GEN-07138 will be displayed only if data in the context of the displayed organization is not correct.

RFR-016450 Correction

Framework: Base
Application: Partners
View: n.a.
Action: Create from template
Category: Unexpected behavior

Problem: The value setting with defaults (i.e. from customizing application) worked not as expected for part attributes.

Correction result: All corrections made in this software update have been reversed. The tests in the QA-process has shown that the offending behavior is correct. So no changing of the code is delivered at all.

5.1.2    Calculation

5.1.2.1      Calculation – General

RFR-016450 Correction

Framework: Calculation
Application: Trade cost calculation
View: n.a.
Action: calculate
Category: Unexpected behavior

Problem: Creation of a calculation: an error message for a non-sales kit component is not always displayed.

Correction result: Creation of a calculation: an error message for a non-sales kit component is always displayed.

RFR-016450 Correction

Framework: Calculation
Application: Product cost calculation
View: Pre-calculation
Action: calculate
Category: Exception

Problem: NPE when using purchasing price listings, if an item of the lower level of a bill of material has no planning data.

Correction result: No NPE but error message, when using purchasing price listings, if an item of the lower level of a bill of material has no planning data.

RFR-016450 Correction

Framework: Calculation
Application: Trade cost calculations
View: Trade cost calculation sales item
Action: Save
Category: Exception

Problem: If you fill other fields without writing an item and save, the application is closed with an exception.

Correction result: If you fill other fields without writing an item and save, no exception occurs but an error message is displayed.

5.1.2.2      Calculations

RFR-016450 Correction

Framework: Calculation
Application: Trade cost calculation
View: Identification view
Action: Calculate…
Field/Column: Supplier origin, Price of components due to valuation price
Category: New field

Description:
1. Function “Supplier origin” of calculation schemas allows to specify a supplier for finding a purchase price for an item.
It is possible to specify
– main supplier or
– alternative supplier
according to planning data of item or
– a supplier which is specified by user within context of product cost calculation
This function is used solely in product cost calculation. Trade cost calculation now benefits from this function too.
2. Calculation of a kit item can be done by calculation its components. This is now extended to also calculate based on valuation prices of components.

Data update: After implementation, a data update query has to be performed. Update application is UPDADU107777. Above mention fields are updated.

RFR-016450 Correction

Framework: Costing
Application: Product cost calculations / calculation schemas
View: pre-calculation / n.a.
Action: Change supplier origin / supplier
Category: Unexpected behavior

Problem: If the attribute origin supplier is set to manual, a supplier must be entered. If the setting is then changed to another origin, the originally entered supplier is not deleted.

Correction result: If the attribute origin supplier is set to manual, a supplier must be entered. If the setting is then changed to a different origin, the supplier is deleted or the correct supplier is displayed.

5.1.3    Inventory management

RFR-016450 Correction

Framework: Storage Location Control
Application: Cockpit: Storage location inventories
View: n.a.
Action: Display tool tips and icons.
Category: Unexpected behavior

Problem: The texts and icons are not all displayed according to the user setting.

Correction result: The problem is fixed.

5.1.3.1      Availability check

RFR-016450 Correction

Framework: Inventory Management
Application: Reorganize Availability and Requirement Data
View: n.a.
Execution for invalid data
Category: Exception

Problem: If the invalid data was corrupt, the reorganization would be aborted.

Correction result: The reorganization will try to ignore those and will proceed with the reorganization. Error messages will be send to inform about the corrupt data.

5.1.3.2      Availability query

RFR-016450 Correction

Framework: Sales
Application: Sales orders
View: n.a.
Action: Check availability…
Category: Unexpected behavior

Problem: If sales order line item contains a concrete inventory identifier specification, the availability check could be not correct.

Correction result: Independent of an inventory identifier specification, the availability check will be done as expected.

5.1.3.3      Inventory count

RFR-016450 Correction

Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Import of an inventory count list reporting for a new line item
Category: Exception

Problem: If the import file contained item identifier data but the item specifications were not correct, an exception could be caused.

Correction result: The validation will avoid invalid data as expected.

5.1.3.4      Inventory postings

RFR-016450 Correction

Framework: Inventory management
Application: Inventory postings or import of inventory postings
View: Inventory posting
Action: Save an inventory posting with a partner specification.
Category: Unexpected behavior

Problem: The partner account classification is not recognized in manual/import inventory postings even if a partner is entered.

Correction result: The partner account classification will be recognized in manual/import inventory postings if a partner is entered.

RFR-016450 Correction

Framework: Inventory Management
Application: Inventory postings
View: Inventory postings
Action: Validate
Category: Unexpected behavior

Problem: If the specified amount for the price or the quantity is enormous the processing of those inventory postings could cause an exception.

Correction result: Manual inventory postings get an “unusal limit” to be checked and if this limit is reached a warning will be send. The warning will be send for the quantity, the price and for the total value of the inventory posting. The current “unusal limit” is 100 Mio.
Technical information: The limit and the relevant inventory transaction creator can be easily overwritten in the class com.cisag.app.inventory.log.InventoryTransactionValidation.
See JavaDoc of the three methods for more informations:
– greaterThanMaximumQuantity(short, QuantityMutable, boolean)
– greaterThanMaximumPrice(short, DomesticAmountMutable, boolean)
– greaterThanMaximumValue(short, DomesticAmountMutable, short, QuantityMutable, boolean)

5.1.3.5      Inventory query

RFR-016450 Correction

Framework: Inventory management
Application: Edit logistic units
View: n.a.
Action: Suggest quantities in all item units
Category: Unexpected behavior

Problem: The suggested quantities were not rounded, so that possibly impermissible decimal places were displayed, which led to an error message.

Correction result: The suggested quantities are now rounded so that there are no more errors in the display of the values.

5.1.3.6      Loads

RFR-016450 Correction

Framework: Inventory
Application: Shipping loads
View: Delivery orders
Action: n.a.
Category: Unexpected behavior

Problem: A wrong quantity is displayed for a delivery detail line if it’s packed in a loading unit that contains further delivery detail lines with the same item.

Correction result: From now the correct quantity will be always displayed as expected.

5.1.3.7      Picking orders

RFR-016450 Correction

Framework: Inventory Management
Application: Picking orders
View: Picking
Action: Validate/Save
Category: Invalid data / Unexpected behavior

Problem: If the relation between the first and the other item unit of measures are not resolvable the item quantities to be reported would not be rounded correctly. Because of that the reporting was denied in seldom cases.

Correction result: The item quantities to be reported will be rounded and the report can be done as expected.

RFR-016450 Correction

Framework: Inventory
Application: Picking orders
View: Delivery orders
Action: Split delivery orders… , Complete delivery orders and output delivery slips…
Category: Exception / Unexpected behavior

Problem: An exception occurred completing and outputting a delivery slip. The reason was, that one delivery detail line of the delivery slip was splitted before and the source order detail had one more open delivery detail line at the same time and the delivery detail line of the delivery slip had set the flag “closed”.

Correction result: From now it will not be allowed to set the “closed” flag in an delivery detail line if more than one open delivery detail line exists for its source order detail. So the exception will not occur any more completing and outputting a delivery slip.

5.1.3.8      Receipts of goods

RFR-016450 Correction

Framework: Inventory
Application: Receipt of goods
Action: Delegte
Category: Invalid data / Unexpected behavior

Problem: If the whole receipt of goods is deleted the order references on the line item level that belong to the order assignments will not be deleted.

Correction result: Now also in case of receipt of goods deletion the line item order references will be deleted.

RFR-016450 Correction

Framework: Inventory
Application: Receipts of Goods
View: n.a.
Action: n.a.
Category: Exception

Problem: In special cases opening the help dialog of the field “Supplier batch” in the editor threw an exception.

Correction result: From now opening the help dialog of the field “Supplier batch” will work as expected.

5.1.3.9      Reservations

RFR-016450 Extension

Framework: Inventory management
Application: Receipt of Goods
View: n.a.
Action: Post receipt of goods…
Category: New behavior

Description: If the QC state of the receiving zone is not released all reservations for released stock will lost their reservations during the post process as before. But if there are other released and fitting inventory elsewhere in the warehouse it will be tried to reserve them.

5.1.4    Planning

RFR-016450 Extension

Framework: Purchasing
Application: Calculate purchasing recommendations
View: n.a.
Action: Calculate recommendations
Category: Performance

Problem: When planning the same item for a high number of warehouses, the Item planning view was loaded repeatedly for the same item.

Correction result: The Item planning view is not loaded repeatedly for the same item.

5.1.4.1      Material requirements query

RFR-016450 Correction

Framework: Planning
Application: Material requirements query
View: Diagram
Action: n.a.
Category: Exception

Problem: Exception, when calling the diagram for an not existing item and then refreshing it or an item without planning data and then changing organization.

Correction result: No exception, when calling the diagram for an not existing item and then refreshing it or an item without planning data and then changing organization.

5.1.5    Production

RFR-016450 Correction

Framework: Production
Application: Production issues
View: n.a.
Action: Post…

Category: Unexpected behavior

Problem: Production issues can be performed in picking context without proper picking before (or using overdelivery of picking).
In this cases demands (and reserved quantity, if reservation active) at original issue warehouse remain unchanged. This is intended but may not be expected by users.
A proper warning is missing.

Correction result: Warehouse of posting transaction is production warehouse: Quantity to report exceeds available quantity for issued item at production warehouse.
“Available quantity” in this context means: picked quantity which has not been reported yet or (in case of overdelivery of picking) the available production warehouse quantity (see list view “Planning data” of application “Production orders”).
If issuing is done, demand at production warehouse is reduced by reported quantity. Demand at issue warehouse due to production order is unchanged. In case of reservation reserved quantity is unchanged at issue warehouse.
That means availability query for issued item and production order detail at issue warehouse remains unchanged, availability at production warehouse is reduced according to reported quantity.
To inform the user about this consequence new warning PRD 2646 is output.

RFR-016450 Correction

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

Problem: Gap-free resources that ignore work-time model gaps yielded an end date too far into the future when scheduled backwards into a time range that contained no resource reservations yet.

Correction result: The gap-free resources are scheduled properly now.

RFR-016450 Extension

Framework: Production
Application: Customizing
View: External manufacturing
Action: n.a.
Category: Ergonomics

Problem: Depending on the status of a property, the block Multi_Site Production appears in Customizing External Production or not.

Correction result: The Multi_Site Production block always appears in Customizing for External Production.

5.1.5.1      Resources

RFR-016450 Correction

Framework: Production
Application: Resources, Resource groups
View: n.a.
Action: n.a.
Category: Invalid data

Problem: Resource type in BO Resource with invalid default value generates an error message.
ResourceGroupType in BO resource groups has invalid default values.

Correction result: Resource type in BO Resource with valid default value does not generate an error message.
ResourceGroupType in BO resource groups has valid default values.

Data update: The application UPDBUG027886 must be called up in the menu Data updates query
Data conversion of the now invalid field-contents as follows: ResourceType/ResourceGroupType
Value 0 (without meaning) -> value 1 (unidentified)

5.1.6    Purchasing

5.1.6.1      Supplier invoices

RFR-016450 Extension

Framework: Purchasing
Application: Supplier invoices
View: Correction invoices
Category: New functionality

Description: Before this change there existed some “edit” restrictions for the supplier invoice line item and order assignment quantity and value fields for the case that a supplier invoice line item belongs to a correction invoice and has a quantity different from zero.
Now this restriction has been removed.

RFR-016450 Correction

Framework: Purchasing
Application: Supplier invoices
Action: Automatically insert line items and assign to receipt of goods line items
Category: Invalid data / Unexpected behavior / Ergonomics

Problem: The dialog of the “Automatically insert line items and assign to receipt of goods line items” action contains a “Net price” column. In contrast to this label and the release 6.1, the result list views do not contain the “Net price” value; instead the “Delivered net value” will be displayed.

Correction result: Now the result lists contain as expected the “Net price” values.

RFR-016450 Correction

Framework: Purchasing
Application: Supplier invoices
Actions: Import, “Recommend supplementary cost distribution on delivered order line item values”, “Recommend supplementary cost distribution on total values of order line items”
Category: Invalid data / Unexpected behavior

Problems:
1. In case of import some order assignment data will not be initialized for an additional cost invoice; as result the action “Recommend supplementary cost distribution on delivered order line item values” does not work as expected (manually or triggered by the virtual import attribute “redistributeAdditionalCosts”).
2. The “Recommend supplementary cost distribution on total values of order line items” does not work as expected for the distribution types “Weight” and “Volume”.

Correction result: Now the functionality works as expected.

5.1.7    Sales

5.1.7.1      Customer invoices

RFR-016450 Correction

Framework: Document management
Application: Applications with Documents query button
View: n.a.
Action: Documents query
Category: Exception

Problem: Exception occurred when pressing Documents query button for some applications if the object maintained was reorganized in the meantime and the application was not refreshed.

Correction result: Exception should not occur in such case anymore. Instead, there should be a validation message.

5.1.7.2      Delivery allocation

RFR-016450 Correction

Framework: Inventory
Application: Inventory allocation
View: n.a.
Action: Accept allocated quantities according to order type / Discard inventory allocation
Category: Invalid data / Unexpected behavior

Problem: After executing the actions “Accept allocated quantities according to order type” or “Discard inventory allocation” for an order, that contains kit detail lines, the distributed value of the order could get negative.

Correction result: From now executing the actions “Accept allocated quantities according to order type” and “Discard inventory allocation” will work as expected.

5.1.7.3      Logon authorizations (customer, supplier, representative)

RFR-016450 Correction

Framework: Base
Application: Partners
View: n.a.
Action: Create from template
Category: Exception

Problem: An exception occurred if a user, locked in as a sales representative, is creating a partner from template that contains marketing data.

Correction result: From now creating a partner from template will work as expected.

RFR-016450 Correction

Framework: Inventory Management
Application: Cockpit: Inventory postings
View: n.a.
Start application via context menu
Category: Unexpected behavior

Problem: If the application was started via context menu the default owner selection could be empty.

Correction result: At start of the application the default inventory owner selection will be set as expected.

5.1.7.4      Sales orders

RFR-016450 Correction

Framework: Sales
Applications: Customer proposals, Sales orders
Action: Apply defaults
Category: Unexpected behavior / Ergonomics

Problem: If a configured item has some sub line items from the configuration the sub line items are sometimes within an unexpected order.

Correction result: The merge of existing lines and new sub line items from the configuration has been changed:
1.) Now the sign of the sub line item is not a criteria any more by the “merge step” – so only the item is used to detect exising lines.
2.) If some sub line items from the configuration are not found within the previous state these sub line items will be added at the end in the order as defined in the item configuration.
Hint: Please note that – as before – sub line item sub number gaps will not be filled by this step.
3.) If some sub line items are present and marked for deletion (remove was not possible by a previous step – e.g. because already delivered) also such a sub line item will be reused now.

5.1.8  Storage Location Control

5.1.8.1      Inventory requisitions

RFR-016450 Correction

Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Create a new transfer line item for a not existing target storage location
Category: Exception

Problem: If the target storage location of a transfer process was invalid, the overtake from editor could cause an exception.

Correction result: The validation will check invalid values as expected.

5.1.8.2      Put-away restrictions

RFR-016450 Documentation

The help documents “Cockpit: Lagerplatzbestände/Artikel” and “Cockpit: Lagerplatzbestände/Ausprägungen” have been updated regarding changed handling of identifiers.

5.1.8.3      Storage locations

RFR-016450 Correction

The help document “Einführung: Lagerplatzsteuerung” has been updated according to bug correction.
The help document “Lagerplätze” has been updated according to two additional attributes.

5.2        GUI

5.2.1    Widgets

5.2.1.1      Fields

RFR-016448 Extension

Class: com.cisag.pgm.gui.CisCalendarField
New Methods:
– setFirstDayOfWeekFieldsEditable(boolean editable). Used to make field “FirstDayOfWeek” editable or not editable on calendar dialog. Default is editable.
– setMinimalDaysInFirstWeekEditable(boolean editable). Used to make field “MinimalDaysInFirstWeek” editable or not editable on calendar dialog. Default is editable.
On the TimeZone dialog:
– combo box of time zone will display more information about the time zone (abbreviaton, code and description).

5.3        Infrastructure

5.3.1    Consulting

RFR-016450 Correction

Framework: Base
Application: Import Data
Filter: com. cisag.app.general.obj.Item
Action: Import
Category: Exception

Problem: An exception occurred if the import file contains a unit of measure as a value for the base quantities, that is not defined in the database.

Correction result: From now an error message will be displayed in that case.

5.4        System development

RFR-016449 Extension

Framework: System Management
Application: Reorganization for automatic data modification entries.
View: n.a.
Action: n.a
Category: New application

Description: Application for reorganizing automatic data modification entries.

RFR-016449 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-016449 Documentation

The help English help documents “CORBA Interface”, “Remote BIS Interfaces”, “Interface for Programmable Web Services” and “Web Services Interface” have been provided.

RFR-016449 Documentation

The help document “System Requirements” (German and English versions) has been updated regarding system IBM i. Accordingly, INF-002659 and INF-002660 have been updated.

RFR-016449 Correction

Framework: Software development
Application: development objects
View: file delivery
Action: value assistant
Category: Ergonomics

Problem: It was not possible to find a file delivery containing a certain file.

Correction result: The value assistant has been improved. Now this kind of reverse search is possible.

RFR-016449 Correction

Framework: System Management
Application: Cockpit: Batch jobs
View: n.a.
Action: Export displayed objects
Category: Exception

Problem: Exporting the displayed data in Excel format closes the cockpit and shows an exception message “java.lang. IllegalArgumentException: Cannot format given Object as a GUID”.

Correction result: The cockpit application is not closed, and the export file is created.

RFR-016449 Correction

Framework: SystemManagement
Application: TransferListReorganization
View: n.a.
Action: n.a.
Category: Unexpected behavior

Problem: System reorganizations should only require the repository database but run if necessary on all connected OLTP Databases.
This was incorrectly implemented.

Correction result: The selection of databases has been corrected.

RFR-016448 Correction

Class: com.cisag.sys.search.filter. DateAndTimeConditionCreator
Method: com.cisag.sys.search.filter.DateAndTimeConditionCreator. getCisDateFormat(FilterExpressionList)

Description: When switching time zones, the date format does not always work properly. Using property “com.cisag.sys.search.filter.DateAndTimeConditionCreator. UseExpressionCalendar” allows you to take the calendar from the filter expression if it is a DateAndTimeFilterExpressionList.

RFR-016448 Correction

Framework: All
Application: Cockpits
View: n.a.
Action: Specify available columns->Add columns
Category: Exception, Ergonomics

Problem:
1. An exception could occur in rare cases when opening a folder.
2. When attributes of a part were included in the definition of a search, these attributes were displayed twice in the dialog, in the main folder and in the associated part folder.

Correction result: The problems no longer occur.

RFR-016448 Correction

Framework: System Management
Application: Editorial Cockpit
View: Import Text
Action: n.a.
Category: Exception

Problem: If a text was imported that contained a text conflict, writing the log file did not work and resulted in an exception.
The import itself worked fine, just the log file was not written.

Correction result: Writing the log file now works.

RFR-016448 Correction

Framework: Software development
Application: Development objects
View: search
Action: validate new object
Category: Exception

Problem: If you create a new object, enter something into the “From” field and press validate an exception occured.

Correction result: The part of the validation causing the problem is skipped if the object is not yet persistent.

Technical information: The part of the validation in question will be performed anyway when the object is made persistent. No problem to skip it here.

5.4.1    Customizable Cockpits

RFR-016448 Correction

Framework: System
Application: All cockpits
View: n. a.
Action: Search
Field/Column: n.a.

Category: improved handling of Valuset parameters

Description: When using other fields of the type selection field as search criteria, all selected values in the where condition were linked individually with or. If the selection field contains a lot of entries and several of these fields are used as search feature, it could happen that the maximum allowed number of search parameters is reached.
Now the values are inserted into the Where condition using the Between expression. This reduces the number of parameters.

5.4.2    Kernel

RFR-016448 Correction

Framework: system
Application: expdbt / impdbt
View:
Action: export / import
Category: Invalid data

Problem: Third domestic amount has been overwritten with first domestic amount.

Correction result: The amounts are properly updated.

Data update: Not possible, since the update cannot decide which values are wrong and which not.

5.4.3    Workflow

5.4.3.1      Activity definitions

RFR-016448 Correction

Framework: Workflow management
Application: Service client
View: n.a.
Action: n.a.
Category: Correction

Problem: There is no possibility to set headers for REST requests. Only headers for SOAP can be set.

Correction result: Headers can be set for all Actions (SOAP, REST-POST, REST-GET). For REST-POST header “Content-Type”: “application/json; charset=UTF-8” is set by default.

Technical information: Encoding can be specified by setting proper header.

5.4.3.2      Processes

RFR-016448 Correction

Framework: Workflow management
Application: Bills of material
View: Bills of material
Action: n.a.
Category: Correction

Problem: After opening the context menu for one item, its instance is shown for process all started for any item.

Correction result: Proper instances are shown for all items.