| Release | Comarch ERP Enterprise 6.4 |
| Release date | 16.01.2026 |
| 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-016596 – RFR-016598
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-Fix14”.
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-Fix14
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix13 will be upgraded to CEE640PB-Fix14.
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
No data updates have to be carried out.
4.2 Batch data updates
With the “Query data updates” application, you must schedule the following batch data updates, for any point in time.
UPDBUG030255
Items – update inheritance
This application will update organization depending item data. It will remove inherited purchase, sales, inventory, production and planning data, that must not exist because the corresponding functions are not released in the application “Customizing.” Moreover, it checks for production- and planning data if inventory data exists for an item / organization combination. If not, production- and planning data will be also removed.
UPDBUG030483
Delete item id’s of deletion marked business objects
This update application will delete (physically) all item id’s (com.cisag.app.general.obj.ItemId) that belongs to deletion marked business objects of type – com.cisag.app.sales.obj.CustomerSalesItem – com.cisag.app.sales.obj.CustomerClasificationItem. – com.cisag.app.purchasing.obj.SupplierPurchaseItem.
5 Contained changes and extensions
5.1 Application development
RFR-016598 Correction
Framework: General
Application: Items
View: n.a.
Action: Accept data for the selected organizations and for their subordinate organizations
Category: Invalid data / Unexpected behavior
Problem: As an error the action created inherited data for organizations, where these data were not allowed, because the corresponding functions in the application “Customizing” were not released or no corresponding inventory data exist.
Correction result: From now this action will inherit data for organizations only, where these data be allowed.
Data update: com.cisag.app.update.log.UPDBUG030255
RFR-016598 Correction
Framework: n.a.
Application: Other fields in applications
View: n.a.
Action: n.a.
Using other fields of type valueset
Category: Unexpected behavior
Problem: If the display language deviates from the standard, the correct entries are not displayed in the valueset.
Correction result: The valueset shows the correct translated entries.
RFR-016598 Correction
Correction of the German user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016598 Correction
Framework: Software Development
Application: Supportrequest
View: n.a.
Action: Adding an upload to a text.
Category: Exception
Problem: In rare cases, exceptions may occur during the upload process.
Correction result: The exceptions no longer occur.
5.1.1 Base
5.1.1.1 Classifications
RFR-016598 Correction
Framework: Base
Class: com.cisag.app.general.log. ClassificationAdapter.ClassificationAdapter
Category: Performance improvment
Problem: When determining buildByPathKey or whether the classification is organization-dependent or not, the constructor first attempts to retrieve buildByPathKey without organization, and if a NoSuchMethodException is thrown, buildByPathKey is retrieved with organization (and also set/getOrganizationalUnit).
Instead, all public methods of the class should be retrieved. If one of the methods is called “buildByPathKey” and has only one parameter of type String, then this is the buildByPathKey method we are looking for and the classification is not organization-dependent. Otherwise, buildByPathKey should be retrieved with organization as before.
Correction Result: The Problem is fixed und this results in better performance and more code readability.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016598 Correction
Class: com.cisag.app.general.order.log. SourceViewStateUtility
Method: S getHookState(Class hookStateImplClass, Class stateRetrieverReturnType)
Category: Invalid data / Unexpected behavior
Problem: If any SourceState implementation (especially a “com.cisag.app.general.order. hook.log.HeaderSourceState” implementation) implements also the EntityState, sometimes the wrong “data view” method (“getEntityState”) is used instead the correct source state method (e.g. “getHeaderSourceState”).
Hint: Because typically the header DataObject has normally also an EntityState HookState container. So the method does not work as expected (expected “HeaderSourceState” implementation is not used) or wrong data is used.
Correction result: Now all methods that return an EntityState will be skipped so that the method works always as expected.
RFR-016598 Extension
- availability/reservation inventory APIs: Class: com. cisag.app.inventory.reservation.log.FixedReservationAvailabilityMaintenanceLogic
New methods: create(short, short, byte[], byte[], String), load(short, short, byte[], byte[], String) and DataEntry. Builder.detailNumber(int, int)Description: The availability/reservation data contains a “formattedOrderNumber” attribute – before this extension this String was determined automatically at save time by the availability/reservation APIs.
In many cases the client of the availability/reservation data APIs knows already the header and line item identifications that are used as base for the “formattedOrderNumber”.
To improve the performance and to ensure the usage of the correct data the client can now specify the header number and detail numbers (main and sub number).
Further – also to improve the performance – the detail numbers will now not be filled up any more with zero numbers as defined by the relevant number range.
The old API methods have been marked as “@deprecated”.2. availability/reservation order APIs:
a.) Classes: com.cisag.app.general.order.log. EntityReservationLogic and com.cisag.app.general.order.log.ReservationLogic
New methods: create(H headerObj) and load(H headerObj)
b.) Class: com.cisag.app.general.order.log. ReservationChangeData
new method: “change” with “D detailObj”Description: For the “create” and “load” methods you have to specify now the “header object” instead of “order type”, “sub type guid” and “header guid”.
For the ReservationChangeData you have to specify now the “detail object” instead of “detail guid”.Hint: Please note that instead of the old four “change” method signatures only one signature with the full parameter set has been added.
The old API methods have been marked as “@deprecated”.
The new methods are using the new methods as introduced by 1..
3. Clients of 2.: The purchasing requests, customer proposals and orders (distribution, purchasing and sales) have been changed so that they are using now the new methods as introduced by 2. instead of the methods that are now marked as “@deprecated”.
RFR-016598 Extension
Framework: Base
Application: Voucher reorganization settings/historical data
Action: Maintain document types
Category: Unexpected behavior
Problem: By mistake the dialog to maintain the “Document types” contains a “System.out.println” – so a log file line was created when performing the “next page” or “previous page” table action.
Correction result: Now the “System.out.println” has been removed.
RFR-016598 Correction
Frameworks: Purchasing/Sales
Applications: Purchase orders, Sales orders
Action: Cancel line item
Category: Unexpected behavior
Problem: In contrast to the functionality “Delete cancellation” the “Cancel” functionality will not be considered as change from “previous” to “current” by the “DetailApplyDefaultsHook”.
Correction result: Now the “Cancel” functionality works as expected in analogy to the “Delete cancellation” functionality.
5.1.1.3 Currencies
RFR-016598 Correction
Framework: General
Application: Cockpit: Exchange rate history
View: n.a.
Action: Load, Switch between applications
Category: Unexpected behavior / Ergonomics
Problem:
1. The value in the “Valid until” date field increased 1 day every time if the user switched to another application and turned back afterwards.
2. The search result range did not match the value of the “Valid from” field. The search result moreover contained results from 12 hours earlier than the date in “valid from”.
Correction result: From now the application will work as expected.
5.1.1.4 Fiscal years
RFR-016598 Correction
Framework: Base
Application: Fiscal years
Actions: “Previous/Next status” (periods)
Category: Unexpected behavior / Ergonomics
Problem:
1. Manual changes of the period lines were discarded by executing the period change actions.
2. In case of period status changes that were performed “Online” the changed lines will be refreshed with respect to the new value but these lines changes also to the “edit” mode. So further status changes cannot be performed directly.
Correction result:
1. Before a period status change can be performed it will be checked now if any changes of the period lines of the current tab are available. If so, a new error message will be sent for the relevant periods and the status change cannot be performed.
Hint: New check for status changes of some periods and change for the whole year.
2. After executing the status change the new value will be set into the relevant period lines (as before) and also the line will be set to “not changed”.
So – if needed – further status changes can be performed directly.
Hint: Please note that this correction changes only the behavior for the case that the status change will be performed directly (“Online”) – in case of executing the change by a background application, the data needs to be refreshed manually before performing further changes.
5.1.1.5 Items
RFR-016598 Correction
Framework: General
Application: Items, import processes with items
View: n.a.
Action: n.a.
Category: Performance
Technical information: From now several classes regarding to the item import process will be performance-optimized
RFR-016598 Correction
Framework: General
Application: Items
View: n.a.
Action: Validate, …
Category: Exception
Problem: An item is marked as deleted. After loading it in the application “Items” an exception occurred if meanwhile in the background or in another session the reorganization for items was running and deleted the item or dependents of this item.
Correction result: From now some (not all cases) of theses exceptions will not occur any more. The code is corrected, were it’s not incompatible.
Technical information: In the “Items” application and it’s entities it will not be possible to eliminate ALL lines of code, where these exceptions may occur, without doing a complete redesign of the application.
RFR-016598 Correction
Framework: General
Application: Items
View: n.a.
Action: New version
Category: Exception
Problem: An exception occurred creating a new version. This happened if the valid from date, the user inserted, is an increment value, that results in a date that is out of the range for a valid date.
Correction result: From now no exception will occur. A new version with the furthest future “valid from” date of the valid range of dates will be created
5.1.1.6 Partners
RFR-016598 Correction
Framework: General
Application: Import data
Filter: com.cisag.app.general.obj.Partner
Action: Import
Category: Exception
Problem: An exception occurred if a partner of type ‘Person’ is imported using a partner template for a partner of type ‘Organization’.
Correction result: From now an error message will be displayed in that case instead.
5.1.2 Calculation
RFR-016598 Correction
Framework: Calculation
Application: Calculation type
View: Group box “Defaults”, Field “Product cost calculation category”
Action: n.a.
Category: Unexpected behavior
Problem: Value “Pre-calculation with quotation reference” could temporarily only be set in application “Calculation Types” if Customizing -> Production -> Configuration is active.
Correction result: Value “Pre-calculation with quotation reference” is generally available in application “Calculation Types”.
5.1.3 Document Management
5.1.3.1 Document cockpit
RFR-016598 Correction
Framework: Document Management
Application: Cockpit: Documents
View: n.a.
Action: Load
Category: Ergonomics
Problem: Loading data to Cockpit: Documents takes very long time in case there are lots of documents.
Correction result: Performance of the cockpit has been improved.
5.1.4 Inventory management
RFR-016598 Extension
-
Framework: Inventory
Application: Delivery slip types
View: n.a.
Action: n.a.
Field/Column: Ladeeinheiten in den Bestand übernehmen (EN: Accept loading units into inventory)
Category: New fieldDescription: Activate this field if you want to automatically accept loading units that are not put away into the inventory at delivery and when selecting the action “Post loading unit changes”. If this function is deactivated, then loading units that are not put away are not automatically accepted into the inventory. Instead, at delivery and when selecting the action “Post loading unit changes”, loading units that are put away are automatically unpackaged.
2.
Framework: Inventory
Application: Goods receipt types
View: n.a.
Action: n. a.
Field/Column: Ladeeinheiten in den Bestand übernehmen (EN: Accept loading units into inventory)
Category: New fieldDesciption: In this field you select how loading units are posted in the receipt of goods process. The following values are available:
• Always, Select “Always” to accept loading units into the inventory when posting receipts of goods.
• Only at unstructured warehouses, Select “Only at unstructured warehouses” to accept loading units into the inventory when posting receipts of goods only at structured warehouses. At simple warehouses the items and identifiers that are contained within the loading units are accepted unpackaged into the inventory.
5.1.4.1 Availability check
RFR-016598 Correction
Framework: Inventory Management
Application: Reorganize availability and demand data
View: n.a.
Action: Execute
Category: Exception
Problem: An Exception could be thrown if the execution caused some error messages.
Correction result: The reorganization application can be executed as expected.
5.1.4.2 Delivery order types
RFR-016598 Correction
Framework: Inventory
Application: Delivery slip types
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: The application outputs organization info to the log-file because of unremoved code from a local test.
Correction result: The code, that outputs the data, is removed now. From now the application will not output any data to the log-file any more.
5.1.4.3 Delivery orders
RFR-016598 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: In the delivery slip report (pdf) the unit of measures (UOM) of order quantities of delivery slip detail lines weren’t displayed in the right way. That was the case if the displayed UOM has a system unit of measure that is different of it.
Correction result: From now the unit of measures of order quantities of delivery slip detail lines will be displayed as expected.
5.1.4.4 Inventory count
RFR-016598 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Generate item based inventory count lists
Category: Unexpected behavior
Problem: If an item inventory was counted by a perpetual inventory count it would not be filtered although the consideration settings should filter it.
Correction result: If an item is already counted by a perpetual inventory count and the consideration settings should filter it this item inventory will be filtered as expected.
RFR-016598 Correction
Framework: Inventory Management
Application: Inventory count valuation
View: n.a.
Action: Post valuation change and close
Category: Ergonomics
Problem: If the new price was zero a warning would be displayed but without any item information.
Correction result: The displayed warning is extended with item and sometimes warehouse information as expected.
5.1.4.5 Inventory management – General
RFR-016598 Correction
Framework: Inventory
Application: Export data
Filter: com.cisag.app.sales.obj.ShippingOrder, com.cisag.app.purchasing.obj. ReceiptOfGoods
Action: Export
Category: Unexpected behavior
Problem: Since CEE640PB-FIX12 the export does not support the relation “UnitLoads->Details->UnitLoadReferences” any more. Some of our customers need it. So it have to be provided again.
Correction result: From now on demand the relation “UnitLoads->Details->UnitLoadReferences” will be supported again. It could be activated in the BI processes by setting the following system properties of type Boolean to true.
– Export delivery order —> com.cisag.app.inventory.delivery.log. ShippingOrderExportControllerSupportUnitLoadReferences
– Export goods receipt —> com.cisag.app. inventory.receipt.log.ReceiptExportControllerSupportUnitLoadReferences
The default value of these system properties will be false (not set), which means, the relation “UnitLoads->Details->UnitLoadReferences” will not be supported in the listed processes.
RFR-016598 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Update
Category: Invalid data
Problem: Storage assignments for identifier assignments were not deleted automatically after deleting an identifier assignment. This could result in invalid storage location reservations.
Correction result: From now storage assignments for an identifier assignment will be deleted automatically when the identifier assignment will be deleted.
Data update: Old storage assignments of already deleted identifier assignments could be deleted manually in the dialog ‘Assign storage locations…’
RFR-016598 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate inventory allocation…
Category: Unexpected behavior
Problem: If an item supported stock related packaging and there was inventory contained in loading units the inventory allocation calculation would not consider the loading unit content.
Correction result: The loading unit content will be considered as expected.
RFR-016598 Correction
Framework: Inventory Management
Application: Transaction date determination rules
View: n.a.
Action: Determine last transaction date
Category: Exception
Problem: If the rule considered loading unit packaging posting that did not have any item, an exception would be caused.
Correction result: The data will be detected as expected.
5.1.4.6 Inventory postings
RFR-016598 Correction
Framework: Inventory Management
Application: Import data
View: n.a.
Import inventory postings
Category: Exception
Problem: If an inventory posting should be imported that had invalid data length (e.g. reference text), an exception could be caused.
Correction result: The data types will be validated as expected and invalid import data will be denied.
RFR-016598 Correction
Framework: Storage Location Control
Application: Warehouses
View: n.a.
Change of the QA status of a storage zone
Category: Invalid data
Problem: If the QA status of a storage zone was increased (e.g. from on hold to released) and there is an unprocessed inventory posting (but already persistent) for this storage zone the later processing could cause wrong QA status amounts.
Correction result: The inventory posting will be processed as expected and all QA status amounts will be correct.
RFR-016598 Correction
Framework: Inventory Management
Application: Inventory posting
View: Manual
Save an inventory posting for intial loading
Category: Unexpected behavior
Problem: It is not allowed to save inventory posting to store an empty loading unit but it was also not possible to fill up a loading unit that was not stored.
Correction result: The first (initial) loading inventory postings will store the specified empty and currently not stored loading automatically.
Technical information: Those initial loading inventory postings and the first incoming inventory posting of a loading unit will support the inventory posting packing lists now.
Packing inventory postings already supported the inventory posting packing lists.
5.1.4.7 Inventory query
RFR-016598 Correction
Framework: Inventory Management, Storage Location Control
Application: Cockpit: Inventories, Cockpit: Storage location inventories
View: n.a.
Action: n.a.
Field/Column: Verpackt (german description)
New sub detail search Ladeeinheiteninformation-Ladeeinheiteninhalte (german description)
Category: New field / New sub detail search
Description: Cockpit: Inventories:
– New column (icon and tool tip) to display whether a stock is packed partially or completely (not displayed as default),
– New sub detail search to display the loading unit content especially for not pure loading units (not displayed as default). Sub Detail search based upon the parent search “Item loading unit information”.
– Some layout changes for a better overview of loading unit stock data
Cockpit: Storage location inventories:
– New column (icon and tool tip) to display whether a stock is packed partially or completely (displayed as default),
– New sub detail search to display the loading unit content especially for not pure loading units (not displayed as default). Sub Detail search based upon the parent search “Item loading unit information”.
– Some layout changes for a better overview of loading unit stock data,
5.1.4.8 Loading units
RFR-016598 Correction
Framework: Inventory
Application: Cockpit: Loading unit history
View: n.a
Action: n.a.
Category: Unexpected behavior
Problem: Particularly the warehouse was not part of the archived (displayed) data, even if a warehouse is part of the achieved process step.
Correction result: From now the warehouse will be archived and displayed if a warehouse is part of the archived process step.
RFR-016598 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: The field “Warehouse/zone/location” displayed the warehouse, zone and location only with overlay, … only then, if the warehouse management server has executed the posting.
Correction result: From now the field “Warehouse/zone/location” will display the warehouse, zone and location without overlay directly in the moment when the posting action is executed. Moreover, the field will display the slot (if a storage location is divided in slots).
5.1.4.9 Loads
RFR-016598 Correction
Framework: Inventory
Application: Delivery orders, loading units
View: n.a.
Action: Generate, assign and display loading units…
Category: Invalid data / Unexpected behavior
Problem: It was possible to change the packaging of a delivery order that had already been loaded. Under certain circumstances, this meant that the displayed contents of the shipping load in the “Loading units” view no longer matched the actual contents of the shipping load according to the delivery.
Correction result: From now it will not be possible to change the packaging of a delivery order that had already been loaded. First the delivery order has to be removed from the shipping load.
RFR-016598 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual postings
Action: Validate
Category: Exception
Problem: If the loading unit status is delivered an exception could be caused.
Correction result: If the loading unit to be stored is delivered an error message is displayed as expected.
5.1.4.10 Reservations
RFR-016598 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Reserve warehouse stocks…
Category: Unexpected behavior
Problem: The dialog would not be shown if the line item and its demand data were created newly. The reason was an exception that was not displayed.
Correction result: The dialog can be opened now as expected and if an exception is caused it will be thrown as expected too.
RFR-016598 Correction
Framework: Inventory Management
Application: Receipt of goods
View: Customer Return
Post the cancellation voucher
Category: Unexpected behavior
Problem: If fixed reservation were used and the receipt of goods cancellation of a customer return should be posted an error message would be send that the reservation could not be transferred to the inventory posting.
Correction result: The receipt of goods cancellation of a customer return can be posted as expected and as all other receipt of goods cancellations.
RFR-016598 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Reserve (Reserve inventory quantities dialog)
Category: Ergonomics
Problem: If the reservation support was deactivated (e.g. for the warehouse) there was no information that the reserved quantities could only be decreased.
Correction result: A warning will be displayed when the reserved quantities should be changed and the item/warehouse context do not support reservations anymore.
RFR-016598 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Invalid data / Unexpected behavior
Problem: If an inventory requisition was created for direct withdrawal the generated inventory order could cause problems at the report step. There were only problems by using the combination of “picking point” strategies and partial withdrawals from loading units or inventory managed packaging.
Correction result: As before a single inventory order will be generated for the issue of goods. This direct picking inventory order does not used any picking points as expected.
RFR-016598 Correction
Framework: Customizing
Application: Function Reservation
View: n.a.
Reserve “Inventory that is available again”
Category: Unexpected behavior
Problem: The automatic reservation process to reserve “Inventory that is available again” is not applied for reservations with the reservation creation setting “Automatically with reservation term”.
Correction result: If the reservation point of time (reservation term) is already reached those demands will be reserved as expected.
RFR-016598 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate delivery orders with order reference and output delivery slips…
Category: Exception
Problem: Exception (this.warehouse2SiteMap is null) was caused during the reservation process.
Correction result: The action can be executed as expected.
5.1.4.11 Warehouses
RFR-016598 Correction
Framework: Inventory Management, Storage Location Control
Application: Picking orders (Generate inventory orders background application)
View: n.a.
Action: Generate inventory orders#
Category: Unexpected behavior
Problem: If the “Generate inventory orders” dialog is used to create inventory orders the both actions “In background” and “Immediately” differed when error messages were created during the time delayed inventory order creation. The message batch job “Message log: Generate inventory orders” was not created when the “Generate inventory orders” batch job was created for background execution.
Correction result: The message batch job “Message log: Generate inventory orders” is also created for background execution of the batch application “Generate inventory orders” as expected. It will bind the error messages created during the inventor order creation in the inventory management server. The batch job behavior of “Generate inventory orders” stays unchanged and has its own independent states if it is started in background, too.
5.1.5 Multi-site capability
5.1.5.1 Distribution order types
RFR-016598 Correction
Framework: Sales
Application: Distribution request types, Distribution order types
Action: Create/Duplicate
Category: Exception
Problem: During the try to determine a number for the “code” attribute an exception occurs if “MultiSite” is not enabled for the current organization.
Correction result: Now in this case no number will be determined (same behavior as for the case that the “number range” within the Customizing is empty).
5.1.6 Planning
5.1.6.1 Generate purchasing recommendations
RFR-016598 Correction
Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: Save, Process, Release, Block
Category: Exception
Problem:
1. It was possible to set the same delivery and availability date for a single recommendation when a calendar year for those dates did not exist; the save operation completed successfully without any errors.
2. Setting different availability and delivery dates for a purchasing recommendation, when the calendar does not exist for at least one of the date years, caused an exception during saving or when changing the recommendation status. Despite the exception occurring, the status change actions also saved incorrect dates.
3. Recommendations with dates for which the corresponding calendar year does not exist were hidden, and a warning about the missing calendar year was always displayed. However, the user could not see the incorrect data and therefore could not correct it.
Correction result:
1. Validation now checks if a calendar year exists for the provided dates; if not, an error message is displayed.
2. Attempting to save a date for which the calendar does not exist will result in the same error as in case 1, and the recommendation is not saved or updated after a status change due to the validation error.
3. Recommendations with invalid dates are now also visible, and the validation displays messages for the wrong dates so the user can identify and correct them.
5.1.7 Production
RFR-016598 Correction
Framework: Planning
Application: Production recommendations
View: n.a.
Action: Generate and release production orders
Category: Unexpected behavior
Problem: Trying to generate and release production order from production recommendation of quantity 1 and item with identifier did not create and set identifier for production order if production order type has field “Time of determination of identifier” set to “When releasing the production order”.
Correction result: Now identifier is created and properly set in released production order.
RFR-016598 Correction
Framework: Production
Application: Data updates
View: n.a.
Action: Run application
Category: Unexpected behaviour
Problem: Calling the data update multiple times resulted in “Canceled with error”.
Correction result: Calling the data update multiple time succeeds.
5.1.7.1 Production – General
RFR-016598 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem:
1. The PRD-00485 message still appears in logs for blocked structures, but it displays vague and unhelpful details. It is also displayed regardless of the “Log untransferred line items” checkbox setting.
2. The APS-00125 message displays the type of the problematic detail, but it also shows the entire path from the header, which results in a misleading production plan header type.
Correction result:
1. All remaining PRD-00485 messages have been replaced with the APS-00125 message, which means there are now controlled by the “Log untransferred line items” checkbox.
2. The APS-00125 message has been improved to display both the production plan header type and the production plan detail type to improve readability.
5.1.7.2 Production order types
RFR-016598 Correction
Framework: Production
Application: Production order type maintenance
View: Tab “Multi-site production”
Action: n.a.
Category: Exception
Problem: If customizing Production -> External manufacturing -> “Activate internal external manufacturing” is not set application “Production order types” does not display tab “Multi-site production” nor does it display checkbox “Internal external manufacturing”.
As this application is designable it is possible to remove tab “Multi-site production”. If within such a context a production order type is loaded with checkbox “Internal external manufacturing” active an exception occurs.
Correction result: In above-described context no exception occurs. An error message is displayed that multi-site data are missing.
5.1.8 Relationship Management
5.1.8.1 Opportunities
RFR-016598 Correction
Framework: Relationship Management, System management
Application: Import data (com.cisag.app.crm.obj.Opportunity)
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: It was impossible to import opportunities with classifications using only path attributes of the classifications.
Correction result: Now it is possible to import opportunities with classification using only path attributes of the classifications.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016598 Correction
Framework: Sales
Application: Customer invoices
Action: Cancel
Category: Invalid data / Unexpected behavior
Problem: The “Cancel” functionality redetermines the “exchange rate” attribute with respect to the current rate. Instead, the attribute must remain as copied from the “original invoice”.
Correction result: Now the “exchange rate” attribute will not be determined – so a “cancel invoice” contains as expected the copied value from the “original invoice”.
Hint: Please note that the attribute “exchange rate” is marked as deprecated with the following text: @deprecated Exchange rate from invoice currency to corporate currency.
DO NOT use for conversion, for information only!
RFR-016598 Correction
Framework: Sales
Application: Customer invoices
Action: Display, Print
Category: Invalid data / Unexpected behavior
Problems:
1. Standard customer invoice report: The “Carry-forward” of the customer invoice was not correct in case of “Gross calculation” (missing discounts/surcharges).
2. Standard customer invoice report: The “Carry-forward” of the customer invoice was not correct in some cases with “order info” lines.
3. Standard customer invoice report: The document discounts were not correctly displayed in case of summary invoices with “Gross calculation” (also with missing discounts/surcharges).
4. Customer invoice application: The orders of the “Document discounts” block at the end were not correctly sorted by “order type code” and “order header number” in case of summary invoices with “Gross calculation”.
Correction result:
1. The relevant standard report (“com.cisag.app.sales.rpt.CustomerInvoice”) has been corrected (“Carry-forward” and consideration of virtual table change – see 3..
Hints: – Correction of “ÜbertragRabattwert” (without line “and {app_sales_CustomerInvoiceDetail. priceRelevant}”)
– Correction of “AuftragslieferscheinPositionsInfo” (consideration of virtual table change ==> print order header info in some cases instead of order line-item info)
2. Correction of “ÜbertragPositionswert” (relevant only for lines with the type “INVOICE_DETAIL”; usage of “CustomerInvoiceDetailVirtualTable.guid” instead of “CustomerInvoiceDetail.guid”).
3. The relevant virtual table (“com.cisag.app.sales.invoice.log.CustomerInvoiceDetailVirtualTable”) has been corrected.
Hints: – Please note that now the document discounts of the orders were printed now at the end of the report (as already displayed within the application).
– To ensure a correct alignment of the printed lines within the case “Sort by delivery slips” and “Invoice line items without delivery slip” the virtual table uses now as “detail type” the order line item values (SALES_ORDER_DETAIL, DISTRIBUTION_ORDER_DETAIL, PURCHASE_ORDER_DETAIL) but with an empty order detail guid value instead of an “detail type” value that belongs to the order header (SALES_ORDER, DISTRIBUTION_ORDER, PURCHASE_ORDER).
4. Now the orders of the “Document discounts” block are sorted as expected.
5.1.9.2 Pro forma invoices
RFR-016598 Correction
Framework: Sales
Application: Distribution orders
Action: Generate and output pro forma invoice
Category: Exception / Unexpected behavior
Problem: If the current distribution order has the type “Return of goods” and the order line item is based on an original order line item (with prices) the “Pro forma invoice generator” does not use – in contrast to the release 6.3 – the “gross price” as specified by the original order line item. Instead, the empty “gross price” of the return order line item will be used and because of the empty currency an exception occurs.
Correction result: Now – as in 6.3 – the “gross price” of the original order line item will be used so that the exception does not occur any more.
RFR-016598 Correction
Framework: Sales
Application: Pro-forma invoices
Action: Create, determine tax code
Category: Invalid data / Unexpected behavior
Problem: In contrast to sales order confirmations and customer invoices the attribute “deliveryCustomer” of pro-forma invoice is not filled for line items that were mapped from an order detail (sales or distribution) – only the attribute “deliveryCustomerData” is filled.
Hint: For freight cost details the attribute “deliveryCustomer” is filled.
Because the tax code determination uses the “deliveryCustomer” atribute the determined tax code might be wrong/unexpected (depending on the tax code assignments).
Correction result: Now the “deliveryCustomer” is filled as expected also for details that were mapped from an order detail (sales or distribution).
5.1.9.3 Sales fast entry vouchers
RFR-016598 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Apply defaults
Category: Exception / Unexpected behavior
Problem: If the value “Binding” is determined for the attribute “Binding unit” an exception occurs.
Correction result: Now the exception does not occur anymore.
RFR-016598 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Price origin
Category: Unexpected behavior / Ergonomics
Problem: If the price is configured to be determined delayed and is not determined for a line item the try to execute the “Price origin” action sends an error message because of the missing price unit of measure.
Correction result: Now the new error message “SAL, 8998” will be send in this case and the dialog does not open.
This error message informs the user that the price must either be determined or specified manually.
RFR-016598 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Price origin
Category: Invalid data / Unexpected behavior
Problem: In contrast to the sales proposals and orders the dialog that belongs to the “Price origin” action uses also in case of a “retail calculation” document the “Gross price incl. taxes” instead of the “Gross price incl. taxes”.
Correction result: Now the correct value is used as expected.
5.1.9.4 Sales orders
RFR-016598 Correction
Framework: Sales
Applications: Customer proposals, Sales orders
Action: simulate (calculation)
Category: Unexpected behavior / Ergonomics
Problem: Given is a retail document with a kit in which the components are price-relevant. Such a price-relevant component is present in the line-item editor and a value relevant for the price calculation is changed (price, quantity, discount, etc.) – then, within the scope of the calculation simulation, the prices and amounts including taxes are refreshed, but not the prices and amounts excluding taxes. Prior to this correction, the refreshment only took place when the line-item data was applied to the entity data.
Correction result: Now also in this case the prices and amounts excluding taxes will be refreshed as expected.
RFR-016598 Correction
Framework: General
Application: Items
View: Customer Sales Item, Customer Classification Item, Supplier Purchase Item
Action: Mark/Unmark as deleted, Inheritance
Category: Unexpected behavior
Problem: Since CEE640PB-Fix09 KW20/2025 the item number inheritance of customer sales item data, customer classification item data and supplier purchase item data did not work as expected.
Correction result: From now the item number inheritance will work as expected. Furthermore, it will work as expected if customer sales item data, customer classification item data or supplier purchase item data is marked as deleted.
Data update: UPDBUG030483
RFR-016598 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: Detail line items of type ‘service’ weren’t be delivered if no picking order was created (and completed) for the delivery order and the detail line items warehouse attribute is set to a warehouse with location organization.
Correction result: From now, as expected, the open deliver quantity of a detail line item of type ‘service’ will be delivered in that case.
5.1.10 Storage Location Control
5.1.10.1 Inventory management server
RFR-016598 Correction
Framework: Inventory Management
Application: Inventory Management servers (Background application)
View: n.a.
Inventory posting processing
Category: Unexpected behavior
Problem: When the inventory management server released data for other processes because dialog processes are preferred there should be no messages about a critical error in the message log.
Correction result: The inventory management server creates messages that it has released data to prefer other processes and some more describing error messages as expected. But there will not be any message about a critical situation at the inventory posting processing.
RFR-016598 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Add loading unit
Category: Exception / Unexpected behavior / Ergonomics
Problem: If a loading unit was added to an inventory order line item several problems could occur: – The loading unit field emptied its value after using the field value assistant
– Changing a loading unit that should be transported but not reported to the reference order reported incorrect quantities
– Adding a loading unit for report did not create stock movement data
Correction result: A loading unit can be added to an inventory order line item as expected and it will be reported correctly.
RFR-016598 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Add loading unit only for report
Category: Exception / Unexpected behavior
Problem: Item line item has not supported the action “Add loading unit” but it was offered and its usage could cause erroneous behavior.
Correction result: An error message will be displayed as expected when the action is used for a line item that belongs to serial numbers.
5.1.10.2 Inventory orders
RFR-016598 Correction
Framework: Inventory Management
Application: Cockpit: Storage locations
View: n.a.
Action: Generate replenishment inventory order
Category: Unexpected behavior
Problem: The setting “Ignore replenishment zone” to ignore the specified replenishment storage zone was considered erroneous.
Correction result: The setting “Ignore replenishment zone” will be considered as specified and as expected.
5.1.10.3 Put-away
RFR-016598 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Generate inventory orders
Category: Unexpected behavior
Problem: If there is no default storage unit defined within the item storage data the put or pick process would be denied.
Correction result: If there is no default storage unit defined within the item storage data the put or pick process will only consider simple zones and the inventory order can be generated as expected and set.
5.2 External support
5.2.1 Programming
RFR-016598 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: n.a.
Category: Extension of the application
Description: From now the application supports the UI-Designer to customize the user interface (ident pane and editor only) for extension attributes. Moreover, it supports hooks to implement applying defaults and validations for the extension attributes.
5.3 System development
RFR-016597 Ergonomics
Framework: Software development
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics
Problem: There was no parallel development for tasks created using the editorial cockpit.
Correction result: Parallel development is now active for tasks created within the context of editorial cockpits. Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.
RFR-016596 Ergonomics
Framework: Software development
Application: Editorial Cockpit, Development objects
View: n.a
Category: Ergonomics
Problem: There was no parallel development for tasks created using the editorial cockpit.
Correction result: Parallel development is now active for tasks created within the context of editorial cockpits. Furthermore, text conflicts can now be deactivated.
Terminus objects are part of parallel development.
RFR-016596 Correction
— Correction
Framework: Kernel / Persistence
Application: Internal Performance Optimization
View: n.a.
Action: n.a.
Description: The methods com.cisag.sys.kernel.CisSharedCache.beginCommit() and com.cisag.sys.kernel. CisSharedCache.endCommit(), along with their associated fields, have been removed. Consequently, the calls to these methods in com.cisag.sys.kernel.server.CisTransactionManagerImpl.commit(CisTransaction, CisSessionControlBlock) were removed. Additionally, fields within the inner classes of com.cisag.sys. kernel.server.CisTransactionCache were set to final where possible. This adjustment resulted in measurable performance gains in other areas of the CisSharedCache.
RFR-016596 Correction
Framework: Software development
Application: Cockpit : production level development objects
View: n.a.
Process: Transfer objects
Category: Exception
Problem: if the cross reference is wrong a null pointer exception occurs when trying to check an object from cross reference.
Correction result: An extra check now prevents this null pointer exception.
RFR-016596 Correction
Framework: All
Application: All cockpits
View: n.a.
Action: Searching
Category: Exception
Problem: An exception may occur if a search is performed in a customizable cockpit with detailed search enabled, and then a search is performed without detailed search enabled.
Correction result: The exception no longer occurs.
RFR-016596 Correction
Framework: Kernel / Persistence
Application: Internal Performance Optimization
View: n.a.
Action: n.a.
Description: Replacing CisHashMaps with ConcurrentHashMap to reduce synchronized blocks in the kernel.
RFR-016596 Correction
Framework: software development
Application: development objects
View: n.a.
Action: Drag and drop in the naviagator
Category: Exception
Problem: If you try drag and drop on the navigator for development objects and the list is empty an exception occurs.
Correction result: No exception occurs anymore.
RFR-016596 Correction
Minor speed optimizations in the persistence service area.
5.3.1 Application server
5.3.1.1 StartUp
RFR-016596 Correction
Framework: Software development
Application: Update destination system
Category: Unexpected behavior
Problem: The batch application may abort with an exception message “java.lang.NullPointerException (…) at com.cisag.sys.sis.log.RefreshTargetSystem. checkWritingRemote” if the execution begins at start of the application server.
Correction result: The problem is resolved.
5.3.2 Data exchange
RFR-016596 Correction
Framework: System management
Application: Import data
View: n.a.
Action: Import data
Category: Unexpected behavior
Problem: Setting a foreign key to NULL value, could not remove it from its Business entity.
Correction result: Foreign key on a business entity can be removed.
RFR-016596 Correction
Framework: System Management
Application: Import data
View: n.a.
Action: Import data
Category: Exception
Problem: If an XML import file contains an empty XML element for a supplement business object, an import may abort with an exception message “java.lang.RuntimeException: Attribute or association without Target or Source”.
Correction result: The problem is resolved, the exception does not occur.
Technical information: A workaround for this problem is to either remove the XML element from the import file, or to make the XML element non-empty.
RFR-016596 Correction
Framework: System Management
Execution of incoming web services
Category: Unexpected behavior
Problem: Depending on the design of a web service, some parts of the request message could be shown in System cockpit, Sessions tabs, as instance description, during execution of the web service.
Correction result: The described information is no longer shown, as it could be long, or contain sensitive data.
5.3.3 GUI
RFR-016596 Correction
Framework: All
Application: Applications using the “document chooser” dialog
View: “document chooser” dialog
Action: n.a.
Category: Unexpected behavior
Problem: The “document chooser” dialog shows the creation date instead of “last modified” date of a file if the file was updated since creation.
Correction result: Fixed.
RFR-016596 Correction
Framework: All
Application: Customizable cockpits
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Several issues with fixed columns (columns that do not scroll horizontally).
Correction result: Fixed.
5.3.4 Knowledge Store
RFR-016596 Correction
Framework: Document Management
Application: Documents
View: n.a.
Action: Generate document file from template
Category: Unexpected behavior
Problem: Paragraphs in table cells that contain only empty merge fields were not automatically removed.
Correction result: Fixed
5.3.5 Workflow
5.3.5.1 Workflow Engine
RFR-016596 Correction
Framework: Workflow
Application: Activities
View: n. a.
Action: running a batch job
Problem: Batch jobs were not running, when started from the activity.
Correction result: Batch jobs can be successfully run from the activity.