| Release | Comarch ERP Enterprise 6.4 |
| Release date | 19.09.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.4.
This fix comprises the following support deliveries: RFR-016572 – RFR-016574
Information about the features of Comarch ERP Enterprise 6.4 (release news): · INF-002734 Release-News: Betriebswirtschaftliche Lösungen · INF-002735 Release-News: Technische Lösungen System requirements: · INF-002736 Systemvoraussetzungen Comarch ERP Enterprise 6.4
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.
2 Installation of software updates
Follow the instructions given in the documentation “Introduction: Software Logistics” to install the software updates that are contained in the support deliveries. If there are deviating instructions to be followed, they are provided in chapter “Information about CEE640PB-Fix12”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE640PB-Fix12
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix11 will be upgraded to CEE640PB-Fix12.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4 Rework after installation
4.1 Data updates
Mithilfe der Anwendung „Datenaktualisierungen abfragen“ müssen Sie alle in diesem Abschnitt aufgeführten Datenaktualisierungen ausführen.
UPDSUP122037
Initialisierung Cust. Sachbuchungen: Kontoherkunft ERs ohne Belegbeziehungen
Diese Datenaktualisierung initialisiert das Feld “Kontoherkunft Eingangsrechnungen ohne Belegbezug” im Customizing, Rechnungswesen, Sachbuchungen mit dem Wert “Verwendungszweck Wareneingang/Eingangsrechnung (Bestandskonten-Klassifikation)” (bisheriges Verhalten).
4.2 Batch data updates
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016574 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-016574 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-016574 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-016574 Correction
Framework: Base
Application: Voucher document templates
View: n.a.
Action: save, validate
Category: Unexpected behavior
Problem: Disabled fields (irrelevant data) will be validated. So there is sometimes error message from unabled fields.
Correction result: Disabled fields (irrelevant data) will not be validated.
RFR-016574 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-016574 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 Base – General
RFR-016574 Correction
Frameworks: Purchasing, Sales
Applications: Purchasing bonus settlement, Sales bonus settlement
Action: Execute
Category: Exception
Problem: If the customizing does not contain a valid “supplier invoice type” (purchasing) or “sales order type” (sales) an exception occurs during the try to execute the bonus settlement.
Correction result: Now the exception does not occur any more.
5.1.1.2 Classifications
RFR-016574 Correction
Framework: Base
Application: Classifications
Action: Change organization
Category: Exception / Unexpected behavior / Ergonomics
Problem: A change of the organization does not refresh the complete user interface (in contrast to the load/refresh action).
In addition to that – as following problem – in case of an organisation without relevant data (e.g. without sales data) an “IllegalStateException: Not initialized!” occurs during the try to create a new node.
Correction result: Now the refreshment will be performed as expected.
Please note also the following further changes:
– If the current classification has no data dependent on organizations, any changed data is no longer simply discarded; instead, only the organization is changed.
– If the previous and the new organization have the same maintaining organization, any changed data is no longer simply discarded; instead, only the organization is changed and the title of the application will be refreshed.
– If the old and new organizations have different maintaining organizations or the new organization cannot be used and data has been changed, the usual question as to whether you want to discard your changes or not is now asked before switching. While the confirmation dialog is open, the old organization is used as usual. If you confirm that you want to discard the changes, the data will be refreshed with the new organization – an error message may then appear if the new organization cannot be used for the type of the current classification.
– “Open empty” works now as expected
5.1.1.3 Contracts/RFQs/Quotations/Orders
RFR-016574 Correction
Frameworks: Purchasing/Sales
Applications: Purchase orders, Sales orders
Action: “rescheduling” actions
Category: Unexpected behavior / Ergonomics
Problem: The sales order and purchase order “rescheduling dialog” were using by mistake for the “delivery date” title (“label”) the same field guid (“0260A78B193E1E10A6798464963A0000”).
Correction result: Now the purchase order “rescheduling dialog” uses a new guid (“01A05A3B5C0F331092A20B861BEE0000”) for the “delivery date” title – so both guids are now different.
5.1.1.4 Item characteristics
RFR-016574 Correction
Framework: System Management
Application: Import data
Action: Import “Item-characteristics assignments”
Category: Performance
Problem: The import of “Item-characteristics assignments” should be done ordered by classification (not by item). But if even if the source data is ordered in that kind the data for a classification will be saved and reloaded after 16 imported source instances (hard coded value). Because “reload” performs a load of all persistent item assignments (ItemPropertyCollection instances) the import performance might be to low in some cases.
Correction result: If you have enough memory you can use for example now “set com. cisag.app.general.item.log.ItemPropertyBIController.BlockSize=1000” to increase the value.
Hints:
– If no value or an invalid value (<=0) is specified the default value 16 will be used as before.
– If the classification changes the data will be saved and reloaded even if the “block size” is not reached.
5.1.1.5 Items
RFR-016574 Correction
Framework: General
Application: Partners
View: Partner Relations
Action: CRUD- Actions
Category: Performance optimization
Problem: In special situations the partner relations logic executed database selects for data, that couldn’t exits in the database.
Correction result: From now these situtions will be filtered and skipped.
5.1.1.6 Partner relationship categories
RFR-016574 Extension
Class: com.cisag.app.general.partner.log. PartnerRelationTypeCache
Method: n.a.
Description: newly built cache class for the business object com.cisag.app.general.obj.PartnerRelationType. Refer to the Javadoc.
5.1.1.7 Partner templates
RFR-016574 Correction
Framework: General
Application: Partners
View: n.a.
Action: Create from template
Category: Unexpected behavior
Problem: A newly created partner couldn’t get stored, although no errors are displayed.
Correction result: From now storing a newly created partner will work as expected.
5.1.1.8 Partners
RFR-016574 Correction
Class: com.cisag.app.general.partner.log. SupplierDataObject
Method: com.cisag.app.general.partner.log.SupplierDataObject. retrievePartner()
Error description: The supplier data object used the wrong constructor (without entity context) for the returned partner data object. So retrieving the address data from the partner data object returned null if the supplier data object is a new, not persistent instance.
Correction result: From now the supplier data object will use the contructur including entity context for the returned partner data object. So retrieving the address data from the partner data object will work as expected.
RFR-016574 Correction
Framework: General
Application: Partners
View: Base view
Action: n.a.
Category: Exception
Problem: It was possible to move the field “Date of birth” from the tab “person data” to other components of the application. Doing that, the field would be editable and enabled for partners, which aren’t a person resp. which could not have a date of birth. In that case an exception occurred when the user wanted to open the calendar dialog of this field.
Correction result: From now the visual component “person data” won’t be customizable any more.
5.1.2 Calculation
RFR-016574 Correction
Framework: Calculation
Application: Product cost calculation
View: n.a.
Action: Update sales price
Category: Unexpected behavior
Problem: When line for Sales price is not specified, error leads to wrong field ‘Price1’ instead of ‘Sales price’ field.
Correction result: When line for Sales price is not specified, error leads to correct ‘Sales price’ field.
5.1.2.1 Calculation – General
RFR-016574 Correction
Framework: Calculation
Application: Cockpit: Sales items
View: n.a.
Action: “Generate calculations…”
Category: Unexpected behavior
Problem: In dialog “Generate calculations…” user specifies a sales price listing which has field “End consumer prices” activated.
Result: Generation of calculations is not possible due error message prohibiting a sales price listing based on end consumer prices.
Correction result: In above described context the validation of specified sales price listing concerning end consumer prices is removed.
Please note: Creating a trade cost calculation manually specifying a sales price listing with end consumer prices does not prohibit this usage.
5.1.3 Inventory management
RFR-016574 Correction
Framework: Inventory Management
Application: Availability inquiries
View: n.a.
Organization change
Category: Exception
Problem: If the organization was changed before anything was loaded an exception could be caused.
Correction result: The organization can be changed as expected.
5.1.3.1 Availability query
RFR-016574 Correction
Framework: Inventory Management
Application: Reorganize availability and demand data
View: n.a.
Action: Execute the reorganization not only for invalid data
Category: Unexpected behavior
Problem: If there was an availability data to be deleted and its demand type was not correct the reorganization could create an error message that a shipping order is missing.
Correction result: If the availability data to be deleted belongs to a shipping order that is already deleted it will be rerorganized without any error messages as expected.
5.1.3.2 Identifier where-used list
RFR-016574 Correction
Framework: Inventory Management
Application: Identifier where-used list
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: If the selected level is not “Single” the loading of the displayed list will take a lot of time.
Correction result: The creation of the list was improved it will now be faster. But the most time is still used by the data detection.
Technical information: If there are really big amount of data records for the identifier tracking it could help to create an own individual index for the BO com.cisag. app.inventory.obj.IdentifierTracking (e.g. non unique index for the single attribute identifier).
5.1.3.3 Inventory count
RFR-016574 Extension
Framework: Base
Application: Number ranges
View: n.a.
Action: Validate
Field/Column: Number length
Category: New action
Description: The allowed number length for inventory counts was increased to ten.
5.1.3.4 Inventory postings
RFR-016574 Correction
Framework: Inventory management
Application: Import data
View: n.a.
Action: Import inventory transactions
Category: Exception
Problem: A loading unit posted via goods receipt cannot be corrected if the correction is made by importing material postings and there are several material postings in the import file that are intended to correct this loading unit.
Correction result: A loading unit posted to goods receipt can now be corrected simultaneously using multiple material postings.
5.1.3.5 Loading units
RFR-016574 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Create
Category: Exception
Problem: An exception occurred if the user wanted to save a newly created loading unit with a number of a loading unit, that already exists.
Correction result: From now an error message will be displayed in that case.
RFR-016574 Correction
Framework: Inventory Management
Application: Shipping orders
View: n.a.
Action: Post unit load changes
Category: Exception
Problem: If a loading unit should be packed and before the inventory posting can be processed the loading unit was already unpacked (but not already posted) the later processing would cause an exception.
Correction result: The inventory posting saves the loading unit pack data at its creation point of time. Because of that it is not important when the inventory posting will be processed. This offers more flexibility to create such inventory posting chains in general but also within delivery process. For a better analyze it is now possible to add a detail search to the inventory postings cockpits to display these loading unit pack info data.
Technical information:
– A new data model was created to save the loading unit pack data at the inventory posting creation point of time.
– No data update necessary because the new logic is possible to handle the new data model and inventory postings without these data as well (“CurrentUnitOnhandDetail” data is used instead of the empty loading unit).
RFR-016574 Correction
Framework: Inventory
Application: Import data, Export data
Filter: com.cisag.app.shipping.obj.UnitLoad, com.cisag.app.purchasing.obj.ReceiptOfGoods, com. cisag.app.sales.obj.ShippingOrder
Action: Import data, Export data
Category: Performance
Problem: The filter definitions of the BO’s com.cisag.app.purchasing.obj. ReceiptOfGoods and com.cisag.app.sales.obj.ShippingOrder were to big and needed to much time to load.
Correction result: From now the filters will not contain the associations “UnitLoad->Details->UnitLoadReferences” any more. Moreover the Integer-Systemproperties
– com.cisag. app.shipping.unitload.log.UnitLoadExportControllerPackagingDepth
– com.cisag.app.shipping.unitload.log. UnitLoadImportControllerPackagingDepth
are added. With these properties it’s additionally possible to reduce the supported packaging depth of loading units to a value less than 5 (which is the default value). This will reduce the filter size massively.
RFR-016574 Correction
Framework: Inventory Managment
Application: Receipt of goods
View: n.a.
Posting of a receipt of goods that contains loading units with more than one content
Category: Exception
Problem: If a receipt of goods is posted that contains loading units with more than one content an exception could be caused at processing the packing inventory postings.
Correction result: Loading units with different content can be posted by the receipt of goods as expected.
RFR-016574 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Delete, Create
Category: Exception
Problem: If a loading unit was used by an inventory process and was deleted after it, a creation of a new loading unit with the same number caused an exception.
Correction result: From now deleting a loading unit and creating a new one with the same number will work as expected.
RFR-016574 Correction
Framework: Inventory
Application: Delivery orders / picking orders / loading units
View: n.a.
Action: Create picking slip (from delivery slip)
Category: Unexpected behavior
Problem: Updating the usage status of all loading units connected to the picked delivery orders didn’t work as expected.
Correction result: From now the updating will work as expected.
5.1.3.6 Loads
RFR-016574 Correction
Application: com.cisag.app.shipping.shippingload.log. ShippingLoadReorganization
Method: n.a.
Description: From now ‘shipped’ shipping loads could be marked for deletion in the application ‘Shipping loads’ and the application ‘Cockpit: shipping loads’. A new backround application was created to reorganize marked shipping loads.
RFR-016574 Correction
Framework: Inventory
Application: Shipping loads
View: Deliveries
Action: Post detail from editor (without validate)
Category: Exception
Problem: An exception occurred when posting a detail line from the editor to the list if the validation is deactivated and the data of the posted detail line is not valid.
Correction result: From now, as expected, the invalid detail line will be added to the list in that case.
5.1.3.7 Receipts of goods
RFR-016574 Correction
Framework: Inventory Management
Application: Receipt of goods
View: n.a.
Action: Post receipt of goods…
Category: Exception
Problem: If the warehouse and the inventory unit of measure of the receipt of goods line item differ to the referenced order line item (e.g. purchase order) an exception could be cause during the posting process.
Correction result: A valid receipt of goods line item can be posted as expected.
5.1.3.8 Reservations
RFR-016574 Correction
Framework: Inventory Management
Application: n.a.
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: The performance of reservation logic could be improved.
Correction result: The performance of reservation logic is improved now.
5.1.4 Planning
RFR-016574 Extension
Framework: Purchasing
Application: Distribution Recommendations
View: n.a.
Action: Generate Distribution Orders…
Category: Performance
Description: Runtime performance of this batch action was improved by disabling the reservation of the generated positions while they are still unsaved (even when Customizing enables reservation of temporary positions).
Runtime performance of this batch action was improved by disabling the expensive availability validation. The availability validation will not generate warning messages any more.
RFR-016574 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning, Re-execute planning
Category: Unexpected behavior
Problem: Material requirements planning took a long time, especially when a lot of secondary demands were generated during planning of multiple sites at once and especially when forecasts were enabled.
Correction result: Material requirements planning is faster, especially planning multiple sites together and planning with forecasts.
RFR-016574 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning, Re-execute planning
Category: Unexpected behavior
Problem: Material requirements planning took a long time, especially for transferring item data and for transferring production-related data like variables.
Correction result: Material requirements planning is faster. Especially planning many items and sites is faster. Especially running MRP when items do not have a production view is faster.
5.1.4.1 Material requirements planning
RFR-016574 Correction
Framework: Production
Application: Check production planning structures
View: n.a.
Action: execute batch application
Category: Unexpected behavior
Problem: Despite running and ending correctly, the batch job would output an error message that the job was canceled (KRN-45).
Correction result: Error message KRN-45 is not displayed anymore, if the batch job ran correctly.
5.1.4.2 Material requirements query
RFR-016574 Correction
Framework: Planning
Application: Material requirements query
View: n.a.
Action: Refresh
Category: Exception
Problem: Under very special cirumstances, querying an item with packaged UOMs could lead to a null pointer exception.
Correction result: The possibility for a null pointer exception has been remedied.
5.1.4.3 Planning – General
RFR-016574 Correction
Class: com.cisag.app.general.item.log. AbstractItemRoleDataObject
Method: com.cisag.app.general.item.log.AbstractItemRoleDataObject. isPersistent()
Description: The method must not return getRoleEntity().isPersistent(). This could result in an infinite loop if ‘isPersistent()’ is called in ApplyDefaultsHook. From now it will always return super.isPersistent().
5.1.5 Production
RFR-016574 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: In multi-level dispatched production orders there can be multiple sub-orders following each other immediately.
In case the 2nd sub-order has a first operation with a buffer time formula,
the system automatically creates a dependency to the previous sub-order.
This ensures that multi level dispatching in multiple orders and multi level dispatching in single orders
both use the buffer time via automatically created constraint.
If the user wants to have the sub-orders scheduled in parallel, no constraints must exist between the sub-orders.
The change also applies to the case of buffer time after at the last operation.
Correction result: A new system property allows to turn off the automatic constraint creation for operations with buffer time as first operation in sub-orders.
Technical information: set com.cisag.app.production.order.log. NoBufferTimeBetweenSubOrdersOnDispatch=true
5.1.5.1 Production – General
RFR-016574 Correction
Framework: Production
Application: Reorganize production orders
View: n.a.
Action: n.a.
Category: Exception
Problem: A production order is reorganized even if there exists a parent production order referencing it, that would not be reorganized.
This can lead to all sorts of other problems, like Exceptions when such a referenced order is edited.
Correction result: A production order can only be reorganized if its parent production order, can also be reorganized. This means, the whole tree of production orders has to be reorganizable.
This applies for parent production orders by multi-level-scheduling process as well as parent production orders by cross-site process.
The reorganization of a production order now stops immediately, after the first error is encountered.
Technical information: Reorganizing a po finds its reachable root and checks recursively whether all sub-POs of this root are reorganizable. Only if they are, the po can be reorganized.
5.1.5.2 Production orders
RFR-016574 Correction
Framework: Production
Application: Order maintenance
View: Detail -> Tab “Transport”
Action: Dispatch
Category: Unexpected behavior
Problem: A routing has a cross site operation. In application “Routing”, detail view –> tab “Transport” field “Item(s) for return transport” is changed.
Result: In case a production order uses this routing for dispatching, the value of field “Item(s) for return transport” in the production order detail is not the one defined in routing, but instead the one defined in cross site operation.
This problem may occur with every value which can be set in application “Routing”, detail view –> tab “Transport”.
Correction result: In above described context dispatching uses the values of cross site operation as set in application “Routing”, detail view –> tab “Transport”.
RFR-016574 Correction
Framework: Production
Application: Order maintenance
View: Dialog: Split or replace operation
Action: Split or replace operation…
Category: Exception
Problem:
1) A external operation of a production order has material provided. The external operation is replaced or split. In the course of reducing quantities of original external operation a exception occurs.
2) A external operation of a production order is completely replaced (no delivery, no reporting). Processing time and/or setup time of master data have unit of measures other than hour. After splitting a subsequent save fails because of an error as unit of measure of target processing time and/or target setup time have been changed to “hour” (which is not allowed anymore).
Correction result:
1) Replacing or splitting an external operation with assigned material provided works as expected. No exception occurs. Quantities of original external operation and material provided are reduced properly. For material provided this is done only if “Transfer material” is active.
2) After replacing external operation completely unit of measures of target processing time and target setup time do not change. Saving production order after replacing works as expected.
5.1.6 Purchasing
5.1.6.1 Supplier invoices
RFR-016574 Correction
Frameworks: System Management, Purchasing
Applications: Customizing, Supplier invoices
Action: “Supplier invoice: apply lime item defaults”
Category: Invalid data / Unexpected behavior
Problem: In case of a “Supplier invoice without voucher reference”, activated “General ledger entries” and the line item account origin type “From account assignment” the “Receipt of goods / supplier invoice” clearing account will be used.
But normally (standard process) this is the wrong account because such an invoice does not use voucher references – it should be the “expense account”. But there might exist some installations where the determined account is OK nevertheless.
Correction result:
1.) The customizing has been extended (function “Financials”, “General ledger entries”) by the new field “Kontoherkunft Eingangsrechnungen ohne Belegbezug” with the entries “Aufwandskonto (Aufwandskonten-Klassifikation)” (default value; recommended value) and “Verwendungszweck Wareneingang/Eingangsrechnung (Bestandskonten-Klassifikation)” (migration value; old behavior) (German label and entries).
2.) The “Supplier invoice: apply lime item defaults” considers the current value of the new Customizing field (only for new line items and in case of a relevant change).
Data update:
Please execute the data update application UPDSUP122037 to initialize all active “Financials, General ledger entries” Customizing functions with the value “Verwendungszweck Wareneingang/Eingangsrechnung (Bestandskonten-Klassifikation)”.
5.1.7 Relationship Management
5.1.7.1 Customizable cockpits
RFR-016574 Correction
Framework: Relationship Management
Application: Cockpit: Suppliers, Cockpit: Customers
View: n.a.
Action: Refresh
Category: Unexpected behavior
Problem: Loading data into the cockpits takes long time in case when user have many organizations assigned,
Correction result: Performance of the cockpits has been improved.
5.1.8 Sales
RFR-016574 Extension
Framework: Sales
Application: ChatERP
View: n.a.
Action: QueryMostSoldItems, QuerySalesOrdersTotalNetAmount
Category: Exception
Problem: If organisation dependent permissions are used, the generated OQL query may fail due to a syntax error.
Correction result: Fixed
5.1.8.1 Sales – General
RFR-016574 Correction
Framework: Sales
Application: Customer proposals, Distribution orders
Action: Apply defaults
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the sales orders “apply line item default” logic the logic for customer proposals and distribution orders does not refresh the “cost of goods” value by a “old total quantity ==> new total quantity factor” if only the total quantity is changed from a non zero value to an other non zero value. Instead the “cost of goods” value was refreshed always by the “item valuation price logic” (even if the item, identifier and storage area are the same).
So especially in cases were the “cost of goods” was changed or defined manually a total quantity change does not change as expected the “cost of goods” value.
Correction result: Now the logic of the customer proposals and distribution orders has been corrected so that all of these three documents have the same refreshment behavior.
Hints:
– Please note that a change of the item, identifier (if present) or (source) storage area triggers always – as before – a new “Cost of goods” determination by the “item valuation price logic”.
– If the “cost of goods” and the “total quantity” are changed together (in the same “round trip”) the “cost of goods” value will – as before – not refreshed, so that the user defined value will not be changed.
5.1.8.2 Sales quotations
RFR-016574 Correction
Framework: Sales
Application: Customer proposals
Action: Select and accept items from draft
Category: Exception
Problem: If a variant can be changed manually and a manually added line item is present within the variant an exception occurs durung the tty to execute the action “Select and accept items from draft”.
Correction result: Now the exception does not occur any more.
RFR-016574 Correction
Framework: Sales
Application: Customer proposals
Action: Create variant/version based on a draft
Category: Exception
Problem: If a line item of a customer proposal draft is using an item configuration the created variant or version line item does not contain a copy of the item configuration. As result a change of the item configuration within any of such details changes also the other line items. Further this error has the effect that a change within a proposal variant from one line item to an other alternative line item discards the item configuration of the draft line item by mistake.
Correction result: Now the created variant/version line items have – as expected – an own copy of the item configuration data – so these errors do not occur any more.
5.1.9 Storage Location Control
5.1.9.1 Empty storage units
RFR-016574 Correction
Framework: Sales
Application: Cockpit: Empties account
View: n.a.
Action: Generate balances
Category: Exception
Problem: An exception occurred if the selected organization is not a financials organization.
Correction result: From now the action will be executed as expected even if the selected organization is not a financials organization.
5.1.9.2 Inventory management server
RFR-016574 Correction
Class: com.cisag.app.inventory.location.cache.log. WarehouseCommandLog
Method: throwException(String, int, String…), throwException(String, int, int, String…)
Description: Although the logging is not active the methods both will bind the message text to the CommandException to be created.
5.1.9.3 Inventory requisitions
RFR-016574 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: Manually complete transport process
Category: Invalid data
Problem: If an inventory requisition line item was completed manually its availability and demand data were not completed.
Correction result: If an inventory requisition line item is completed manually its availability and demand data will also be completed as expected.
5.1.9.4 Storage locations
RFR-016574 Correction
Class: com.cisag.app.inventory.location.cockpit.gui. StorageLocationsAllocationRendererFactory
Method: n.a.
Description: The not allowed org.testng.util. Strings.isNullOrEmpty(String) usage is changed to CisStringUtility#isEmpty(String).
5.2 System development
RFR-016573 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-016572 Correction
Framework: Software development
Application: Job maintainance
Action: activating task plus parallel development
Category: Ergonomics
Problem: If a brand new object is part of a task, the logic searched for a previous version and sends a message.
This could lead to confusion. The transfer works nevertheless.
Correction result: If a object has no previous version then there is now a check in advance whether there should exist a previous version.
RFR-016573 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-016573 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-016572 Correction
Optimisation of the synchronisation of the shared cache. Acceleration of read processes when several threads access the cache simultaneously.
RFR-016572 Correction
Framework: Workflow
check for authorization
Category: Exception
Problem: It might happen for users without admin authorization that there is an exception when a check for authorization is performed while they work in workflow context.
Due to technical reason a transaction has to be created and committed. A session with Workflow context must not commit a transaction. This lead to an exception.
Correction result: checks for authorization are now possible in the context of workflow.
RFR-016572 Correction
Database management
Category: Ergonomics
Problem: On a Postgresql database it can happen that the prepared statement has to be asked for its parameter meta data.
Especially if there are a lot of parameters, this can be time consuming.
Correction result: The handling of the meta data is now optimized.
5.2.1 Application server
5.2.1.1 Autorizations
RFR-016573 Correction
Framework: System management
Tool: wrksec
Category: Unexpected behavior
Problem: After copying a system, an authorization role can contain security definitions for knowledge store objects (documents or folders) using to a workspace which doesn’t belong to the current system or whose database isn’t valid. These are shown as incomplete entries in application Authorization Roles.
Correction result: “wrksec -deleteInvalid” deletes these security definitions.
RFR-016572 Correction
Framework: System management
Tool: wrksec
Category: Unexpected behavior
Problem: After copying a system, an authorization role can contain security definitions for knowledge store objects (documents or folders) using to a workspace which doesn’t belong to the current system or whose database isn’t valid. These are shown as incomplete entries in application Authorization Roles.
Correction result: “wrksec -deleteInvalid” deletes these security definitions.
5.2.1.2 Chat
RFR-016573 Extension
Framework: System
Application: ChatERP
View: n.a.
Action: n.a.
Category: New field
Description: A footer with the following text have been added to the chat window: “Comarch ChatERP may make mistakes, so its responses should be verified.”
RFR-016572 Extension
Framework: System
Application: ChatERP
View: n.a.
Action: n.a.
Category: New field
Description: A footer with the following text have been added to the chat window: “Comarch ChatERP may make mistakes, so its responses should be verified.”
5.2.2 Configuration
5.2.2.1 System cockpit
RFR-016572 Correction
Framework: System Management
Application: System cockpit
View: n.a.
Action: Open the application
Category: Exception
Problem: If a user has no business entity authorizations for “Application server”, the System cockpit cannot be opened, and an exception message is shown.
Correction result: The problem is resolved.
5.2.3 Repository
RFR-016572 Correction
Framework: system managment
Application: n.a.
View: n.a.
Category Unexpected behavior
Problem: The incorrect cache strategy for com.cisag.sys. repository.obj.XmlRegistryBase is causing performance issues. Since we cannot modify this class in version 6.4, we are implementing a workaround by overriding the cache strategy for this business object within the cache configuration.
Correction result: less database accesses for this BO
5.2.4 Workflow
5.2.4.1 Activity definitions
RFR-016572 Correction
Framework: Workflow
Application: Activity definition
View: n.a.
Action: Mark of delete on results list
Category: Unexpected behavior
Problem: Mark of delete on results list wrong setting state of combobox entry row and makes it impossible delete a row.
Correction result: Mark of delete is setting correctly on all rows.