| Release | Comarch ERP Enterprise 6.5 |
| Release date | 02.04.2026 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.5.
This fix comprises the following support deliveries: RFR-016609 – RFR-016611
Information about the features of Comarch ERP Enterprise 6.5 (release news): · INF-002815 Release-News: Betriebswirtschaftliche Lösungen (wird nachgeliefert) · INF-002814 Release-News: Technische Lösungen (wird nachgeliefert) System requirements: · INF-002813 Systemvoraussetzungen Comarch ERP Enterprise 6.5
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 CEE650PB-Fix05”.
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 CEE650PB-Fix05
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE650PB-Fix04 will be upgraded to CEE650PB-Fix05.
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 CEE640PB and CEE640PB-Fix12, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE650PB.
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 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.3 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.
3.4 Cumulative installation of support deliveries
Code status CEE640PB is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.4 and Comarch ERP Enterprise 6.5 at the same time. Support deliveries for Comarch ERP Enterprise 6.5 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
4 Rework after installation
4.1 Data updates
Using the “Query data updates” application, you must perform all the updates listed in this section.
UPDSUP121159
Scaling down the sumQuadDuration value stored in the repository database
The values stored in the sumQuadDuration attribute are scaled down by a factor of 10,000 to prevent overflow.
UPDADV121639
Rebuild indices and initialized new attributes on valuation BO instances
For the following Business Objects (BOs) this data update, rebuild all indices and initialize the site GUID only for records where the warehouse is set: InventoryValuation, InventoryOnhandPeriodSummary, InventoryValuePeriodSummary, InventoryYearLifo, InventoryYearLifoReference, InventoryYearLifoPrices and PhysicalInventoryValuation. The valuationLevel attribute in the PhysicalInventoryValuationParameters BO will be set using the warehouseValuation attribute, following this logic (only for records where the valuationLevel == UNDEFINED_VALUESET_ELEMENT): warehouseValuation == true => ValuationLevel.ITEM_STORAGE_AREA, warehouseValuation == false => ValuationLevel.ITEM.
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 inherritance
This application will update organization depending item data. It will remove inherited purchase, sales, inventory and production 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.
UPDSUP123733
Updating the usage status of delivered loading units
This update application will correct the usage status of delivered loading units to “Not bound to a process”.
UPDADU123241
Activation of the new customizing function ” Inventory management server”
UPDBUG030606
Item data: Correction of Inherritance
This update application will search item data of the views inventory, production, planning, sales and purchasing, that is inherited from a faulty parent organization and will correct this data.
UPDADV123417
Activation of the new customizing function “Planning-Server”.
5 Contained changes and extensions
5.1 Application development
RFR-016611 Correction
Framework: General
Application: Items
View: Inventory, Production, Planning, Sales, Purchasing
Action: Accept data processing for the selected organization
Category: Invalid data / Unexpected behavior
Problem 1: In special cases the action “Accept data processing for the selected organization” didn’t update the maintaining organization of inherited item data, that should inherit from now the item data from the selected organization.
Correction result 1: From now the action “Accept data processing for the selected organization” will always update the maintaining organization of inherited item data as expected.
Data update: UPDBUG030606
Problem 2: Using the action “Accept data for the selected organizations and for their subordinate organizations” it was possible to inherit item data to organizations, that are not contained in the users organization context, … which means that he is not authorized to do it.
Correction result 2:
As expected from now the action “Accept data for the selected organizations and for their subordinate organizations” will skip inheriting data for organizations, that are not contained in the user’s organization context.
RFR-016611 Correction
Framework: General
Application: Fill application server cache
View: n.a.
Action: Excecute
Category: Exception
Problem: An exception occurred when the process started the application ‘Company calendar’.
Correction result: From now starting the application ‘Company calendar’ in this process will work as expected.
5.1.1 Base
5.1.1.1 Base – General
RFR-016611 Correction
Application: Document applications with “partner name”
Action: Maintain “partner name” data
Category: Invalid data / Unexpected behavior / Ergonomics
Problem: Because of some system engine errors blanks at the end of a “multi line text” value will not be removed if the default “multi line text” field is used within a customizable UI.
Especially for the “partner name” of the document applications this is a problem because such a name is a part of a so called “hash code business object” – here a different content results in a different hash code.
So some documents (e.g. “Shipping order” based on sales order line items) will split up the data because of the different content.
Correction result: Because the system engine cannot be corrected (compatibility reasons) the following changes were performed as work around: 1. new class “com. cisag.app.general.gui.factories.PartnerNameEditorFactory” which is used for the data description of the logical datatype “com.cisag.app.general.PartnerName”.
2. com.cisag.app.general.order.gui. PartnerAddressDataNameField: new call of “rtrim” within the method “getValue”
RFR-016611 Correction
Class: com.cisag.app.general.log. MutableArrayDependentData
Method: copy constructor
Category: Invalid data / Unexpected behavior
Problem: By mistake the “copy constructor” did not work in all cases as expected. So, it could occur that the newly created instance contains empty data instead a copy of the specified data.
Correction result: Now the “copy constructor” works as expected
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016611 Correction
Framework: Sales
Applications: “Order confirmations query”, “Pro forma invoices query”, “Customer invoices query”
Actions: “Display” and “Print”
Category: Unexpected behavior
Problem: If some header discounts are present, they will be displayed and printed (in case of gross calculation) always even if no detail is using them.
Correction result: Now the header discount data will be displayed and printed only if at least one detail is using them.
In addition to that the applications “Order confirmations query” and “Pro forma invoices query” display now the type also for header discount rows (as already the “Customer invoices query” application).
Further all three applications display now also for detail discount rows the type.
5.1.1.3 Items
RFR-016611 Correction
Framework: Update
Application: UPDBUG030255
View: n. a.
Action: n.a.
Category: Invalid data / Unexpected behavior
Problem: The data update application removes the inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations. Unfortunately, it is perfectly acceptable to have item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.
Correction result: From now the data update application will not remove an existing inheritance of item planning data for organizations if the “Planning” customizing function is deactivated for those organizations.
Data update: Restoring inheritance after the data update would only be possible manually.
5.1.2 Calculation
RFR-016611 Correction
Framework: Calculation
Application: Cockpit: Production items
View: n.a.
Action: “Generate calculations…”
Category: Exception
Problem:
1. In an environment where Customizing -> Production -> Method is not active Cockpit: Production items is opened, items are selected and action “Generate calculation..” is performed.
Result: an exception occurs.
2. Same preliminaries as in a). Cockpit: Production items can be opened from menu “Calculations” as well as from menu “Production”.
Opening from menu “Calculation” action “Generate calculation” should be supported, opening from menu “Production” this action should not be not supported. This is not the case. It is vice versa.
Correction result:
1. In an environment where Customizing -> Production -> Method is not active Cockpit: Production items is opened, items are selected and action “Generate calculation..” is performed.
Result: no exception occurs, calculation is generated as expected.
2. Opening from menu “Calculation” action “Generate calculation” is supported, opening from menu “Production” this action is not supported.
RFR-016611 Correction
Framework: Calculation
Application: Trade cost calculations
View: n.a.
Action: New
Category: Unexpected behavior
Problem: When a user loads a ‘Trade cost calculation purchasing items’, changes its type to ‘Trade cost calculation sales items’, and then clicks the ‘New’ button, the application incorrectly displays a confirmation window about losing unsaved changes, even though no modifications were made.
Correction result: Now after performing the same actions, a new empty object is opened without the unnecessary confirmation window.
RFR-016611 Correction
Framework: Costing
Application: Product cost calculations / Trade cost calculations
View: n.a.
Action: Calculate
Category: Ergonomics
Problem: Locking mechanisms in product/trade cost calculation where were not optimally implemented.
Correction result: Locking mechanisms are now more performant.
5.1.3 Inventory management
RFR-016611 Correction
Framework: Inventory Management
Application: Warehouses
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The new put strategy setting for the fill-up sequence was editable although the fill-up was not active.
Correction result: The new put strategy setting for the fill-up sequence will be disabled when the fill-up is not active as expected.
RFR-016611 Correction
Framework: Inventory
Application: Goods receipts
View: Production
Action: Insert line items from orders…
Category: Unexpected behavior
Problem: The proposed receiving quantity in the dialog, that opens in this action, did not consider already reported scrap quantities when it should do. This would be the case if the checkbox ‘Consider scrap quantities’ is activated in the production order type of the displayed production order.
Correction result: From now, if the checkbox ‘Consider scrap quantities’ is activated, the already reported scrap quantity will be considered when calculating the proposed receiving quantity.
Technical information: From now the logic com.cisag.app.production.order.log.OrderUtility. getOrderQuantityToReport(ProductionOrder) will be used to calculate the proposed receiving quantity.
5.1.3.1 Availability query
RFR-016611 Correction
Framework: Inventory Management
Application: Availability queries
View: Origin
Availability calculation using “Remaining shelf life” (Customizing, Sales Item)
Category: Unexpected behavior
Problem: Batches: If the remaining shelf time is set within the customizing or sales item it should be considered and calculated based on the first expired point of time but it was calculated using the last available date before it is expired (MHD = German description/meaning) .
Correction result: The “Remaining shelf life” is considered as expected. The changed calculation should be checked and if it is needed, please increase the “Remaining shelf life” time by one day within the customizing or sales item settings.
5.1.3.2 Delivery orders
RFR-016611 Correction
Framework: Sales / Inventory
Application: Sales orders
View: n.a.
Action: Generate delivery orders with order reference and output delivery slips…
Category: Exception
Problem: An exception occurred creating a delivery slip from a sales order directly if a detail line with an identifier item was overdelivered by setting the dispo quantity higher than the open quantity.
Correction result: From now creating a delivery slip from a sales order directly will always work as expected.
RFR-016611 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Using checkbox “Blocked for invoicing”
Category: Ergonomics
Problem: Clicking the checkbox “Blocked for invoicing” didn’t update the status icon of the concerning detail lines in the list.
Correction result: From now clicking the checkbox “Blocked for invoicing” will update the status icon of the concerning detail lines in the list.
RFR-016611 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: The complete action may display the error message GEN-6044 and the freight cost calculation may calculate no or wrong freight costs if the delivery order uses the base unit of measures instead of the system unit of measures for weights and volumes.
Correction result: From now the complete action will always work as expected.
RFR-016611 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: n.a.
Category: Invalid data / Ergonomics
Problem: After picking is completed a delivery order that contains a detail line with an item of type “Serial number without inventory management” went always in “Changed”-Mode if the serial number was already assigned in the sales order. Furthermore, the detail line could not get packed in the packing dialog.
Correction result: From now the problem is fixed. Delivery orders that contain a detail line with an item of type “Serial number without inventory management” will always work as expected.
Data update: To correct the problem a delivery order, that is in “changed”-mode, could simply be saved.
5.1.3.3 Identifiers
RFR-016611 Correction
Framework: Inventory Management
Application: Receipt of goods
View: Purchasing
Generate identifiers automatically
Category: Exception
Problem: If a number range is specified that uses production data as parameter and the receipt is for a purchasing process the identifier generation would be aborted with a NullPointerException within the system infrastructure.
Correction result: For this erroneous case a message (= message exception) is thrown and the identifier generation will be aborted as expected.
5.1.3.4 Inventory count
RFR-016611 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Create item-based inventory count lists…
Category: Exception
Problem: The field “Inventory check setting” could be empty although the field “Include inventory” was not set to “Empty count list”. This error is only caused by changing the value in the field “Inventory check setting”.
Correction result: If the value of the field “Inventory check setting” is mandatory it will be set as expected.
RFR-016611 Correction
Framework: Inventory management
Application: Inventory count
View: n.a.
Action: Create item dependent count lists…
Category: Unexpected behavior
Problem: if an item classification was selected and the stock consideration field was changed the generated section string would be added every time the consideration field was changed.
Correction result: The selected classification values stay in the classification fields until they are changed.
RFR-016611 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Import of new line items to be reported
Category: Exception / Unexpected behavior
Problem: If more than one hundred line-items were imported only the first block (100) of line items could be created and reported successfully.
Correction result: Independent of the number of line items the import of line item reports can be imported as expected.
5.1.3.5 Inventory management – General
RFR-016611 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Update
Category: Invalid data
Problem: Storage assignments for identifier assignments were not be 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…’
5.1.3.6 Inventory postings
RFR-016611 Correction
Framework: Inventory Management
Application: Edit inventory posting error automatically
View: n.a.
Action: Execute
Category: Exception
Problem: The context lock for reservation could be not successful if there are complete and not completely reserved inventory posting errors for the same context (item, warehouse).
Correction result: If it is possible to process inventory posting errors now it will be possible to save them to be processed as expected.
RFR-016611 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-016611 Correction
Framework: Inventory Management
Application: Loading units
View: n.a.
Action: Pack…
Category: Invalid data / Unexpected behavior
Problem: A loading unit could be packed within a storage location that does not supports storage units. To solve this erroneous situation the loading unit can be unpacked.
Correction result: The try to pack a loading unit within a storage location that does not supports storage units will be denied as expected.
5.1.3.7 Inventory value query
RFR-016611 Correction
Framework: Data Update
Application: com.cisag.app. update.log.UPDADV121639
View: n.a.
Action: n.a.
Category: Invalid data
Problem: The “Special usage” setting in application UPDADV121639 has been set to the value “Batch data updates”, allowing this data update to be executed at any time. However, if work continues in the system before the data update has been carried out, it may result in incorrect data in the inventory valuation.
Correction result: The “Special usage” setting in application UPDADV121639 has been set to the value “Data update,” which forces the data update to be executed during the release update to next release version, thereby preventing the creation of incorrect data.
5.1.3.8 Loading units
RFR-016611 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Save and report a line item with automatic unpacking of a loading unit unpack proposal
Category: Unexpected behavior
Problem: Although the automatic unpack of a loading unit unpack proposal was selected the loading unit was not unpacked and because of that the report was not successful.
Correction result: If the automatic unpack of a loading unit unpack proposal is selected the loading unit will be unpacked as expected.
RFR-016611 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Pack …
Category: Unexpected behavior
Problem: The action did not support the packing on storage location slots.
Correction result: From now packing on storage location slots will be supported.
RFR-016611 Correction
Framework: General
Application: Import Data
Filter: com.cisag.app.shipping.obj.UnitLoad
Action: Import
Category: Unexpected behavior
Problem: The import process for creating loading units consumed a new number from the number range manager even if a number is already defined in the XML source file.
2. Moreover, after changing the organization in the organization selector the application “Loading units” may use the wrong number range for creating a new number.
Correction result: From now the import process for creating loading units will consume a number from the number range manager only then if no number is defined in the XML source file.
Framework: Inventory
Application: Loading units
View: n.a.
Action: Create
Category: Unexpected behavior
Problem: After changing the organization with the organization selector the application “Loading units” may use the wrong number range definition for getting a new number.
Correction result: From now the expected number range definition always will be used, even if the organization is changed.
5.1.3.9 Loads
RFR-016611 Correction
Framework: Inventory
Application: Shipping loads
View: n.a.
Action: Delete / Delete detail line
Category: Invalid data
Problem: In delete processes the application updates the usage status of containing loading units to the invalid status “Issue of goods”. This status is invalid if the assigned delivery order is delivered already.
Correction result: From now in delete processes the application will update the usage status of containing loading units to the status “Issue of goods” only if the status of the assigned delivery order is “Not delivered”. Otherwise, the usage status of the containing loading units will be set to “Not bound to a process”.
Data update: UPDSUP123733
RFR-016611 Correction
Framework: Inventory
Application: Shipping loads
View: n.a.
Action: Send…
Category: Exception
Problem: The action could cause an exception if the data of the contained delivery orders has changed since the last display of the data in the application.
Correction result: From now the application will work as expected.
5.1.3.10 Picking orders
RFR-016611 Correction
Framework: Inventory
Application: Delivery orders, Cockpit: Delivery orders
View: n.a.
Action: Generate and output picking orders…
Category: Exception
Problem: An exception occurred creating a picking order for delivery orders being packed in more than one layer, which means a delivery order that is packed in a loading unit that itself is packed in another loading unit.
Correction result: From now creating a picking order for delivery orders being packed in more than one layer will work as expected.
5.1.3.11 Receipts of goods
RFR-016611 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Reuse loading unit …
Category: Unexpected behavior
Problem: The action is available when the usage status of the loading unit is ‘Receipt of goods’.
Correction result: From now the action will be available if the usage status is ‘Not bound to a process’ or ‘Distribution’ only.
5.1.3.12 Reservations
RFR-016611 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-016611 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 Multi-site capability
5.1.4.1 Distribution orders
RFR-016611 Correction
Framework: Sales
Application: Distribution orders
Action: Reduce line-item editor size using split pane
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the “Sales orders” application the line-item editor height cannot be changed by the “split pane” functionality.
Correction result: Now the behavior is as expected.
5.1.5 Planning
RFR-016611 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Enter organizations in field “Sites” & update
Category: Unexpected behaviour
Problem: Entering more than 255 characters in field “Sites” led to a fatal error during planning.
Correction result: Field “Sites” now validates the input length, more than 255 characters are denied.
RFR-016611 Correction
Framework: Planning
Application: Material requirements planning, Cockpit: Planning conflicts
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem: When an item’s “Lot size method” is set to “Exact lot size”, the planning run may generate a “Quantity of order/recommendation too small” conflict for an order that falls before the planning start date. In this case, the suggested correction quantity is incorrectly too large. For the same order placed within the planning horizon, the planning server generates the same conflict but with a correct, smaller correction quantity.
Correction result: The correction quantity calculated for orders before the planning start date is now aligned with the correction quantity calculated for orders within the planning horizon, and the suggested value is now correct.
RFR-016611 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all actions that execute planning
Category: New feature
Description: Add system property com.cisag.app.aps.SuppressMessage to suppress specific messages from being written to logs during planning.
RFR-016611 Correction
Framework: Purchasing
Application: Calculate distribution recommendations
View: n.a.
Action: Calculate recommendations
Category: Unexpected behavior
Problem: When planning with delivery calendars, the “Delivery calendar classification” configured in the item’s planning view at section “Purchasing (external)” was used for distribution recommendations.
Correction result: When planning with delivery calendars, the “Delivery calendar classification” configured in the item’s planning view at section “Purchasing (internal)” is used for distribution recommendations.
RFR-016611 Correction
Framework: Production
Application: Production recommendations / Distribution recommendations
View: n.a.
Action: Generate production orders / generate distribution orders
Category: Unexpected behavior
Problem: In application “Distribution recommendations”, it was possible to enter 0 quantity for recommendations in the list. When using acting “Generate distribution order” this led to an error.
In application “Production recommendations”, it was possible to enter a negative priority.
Correction result: It is not possible anymore to enter a quantity of 0 in “Distribution recommendations” nor a negative priority in “Production recommendations” as validation for both cases has been added.
RFR-016611 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning
Category: Exception
Problem: If the system property com.cisag.app.production.aps.log. APSNewProductionPlanTransferLogic_useOldProcessHeadersOQLs was set to true and a planning run executed, this led to an SQL exception.
Correction result: No SQL exception occurs even when the system property is set to true.
5.1.6 Production
RFR-016611 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: Prerequisite: A production item has set production method “Bill of material and routing”, and this bill of material only contains a sub-bill of material, which in turn contains some material line items, and the routing contains an external operation.
When a Production order with this production item was scheduled, the material of the sub-bill of material was then converted to “material provided”, which was unexpected.
Correction result: After scheduling a production order with the prerequisite above, the material of the sub-bill of material is not automatically turned into “material provided”.
RFR-016611 Extension
Framework: Production
Application: Production orders, Cockpit: production orders
View: n.a.
Action: Recalculate due date and quantity, Change due date and quantity
Field: Lock quantities for completed line items
Category: New field
Description: If new checkbox is enabled all details of production order that have status “Fully reported” will have locked quantities and durations during rescheduling, which means those values will be not changed for those positions.
RFR-016611 Correction
Framework: Production
Application: Material requirements query
View: n.a.
Action: Open tab “demands”
Category: Unexpected behaviour
Problem: Translations for fields “Unit of measure” “Total” and “Previous period” are not adapted to user-language if it has been changed.
Correction result: Translations for fields “Unit of measure” “Total” and “Previous period” are adapted to user-language of it has been changed.
RFR-016611 Correction
Framework: Production
Application: Bills of material
View: Bill of material
Action: Validate, Save
Category: Unexpected behavior
Problem: When bill of material contains line item which is replaced and action Save or Validate will be performed this details is not validated at all, which allows to save invalid data e.g. quantity with decimal number.
Correction result: Now replaced detail is also validated which makes saving invalid data impossible.
RFR-016611 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release
Category: Exception
Problem: Multi-level dispatching for a production order fails when its production item’s bill of material contains an equipment item with the “Item resolution in multi-level dispatching” setting enabled in item production view. The process throws an exception because the system incorrectly attempts to create a sub-order for the equipment detail.
Correction result: Sub-orders are no longer generated for equipment details. This ensures that the dispatch process finishes successfully under the same conditions.
RFR-016611 Extension
Framework: Production
Application: Production order type
View: n.a.
Action: n.a.
Field: Consider scrap quantity for completion
Category: New field
Description: New checkbox “Consider scrap quantity for completion” has been added to “Production order types” application. When it is checked all production orders of that type consider sum of ‘Actual quantity’ and ‘Rejects quantity’ instead of only ‘Actual quantity’ during determining ‘Production receipts’ status of entire order.
In result when that option is enabled ‘Rejects quantity’ of a production order is considered as reported quantity in terms of completion of an order.
5.1.6.1 Bills of material
RFR-016611 Correction
Framework: Production
Application: Import data, Bills of material
View: Bill of material
Action: Import data
Category: Unexpected behavior
Problem: Importing Bill of material with empty attribute “BomScrapClassification” properly saved that BOM, but opening it then in Bills of material application enters edit mode, even though nothing has been changed.
Correction result: Now opening imported Bill of material do not enter edit mode automatically if nothing has been changed.
RFR-016611 Extension
Framework: Production
Application: Production orders
View: n.a.
Action: n.a.
Category: New feature
Description: RFE-006310 Access to production order quantity unit of measurement in formulas.
5.1.6.2 Production – General
RFR-016611 Correction
Framework: Calculation
Application: Product cost calculations, Trade cost calculations
View: n.a.
Action: Exit
Category: Unexpected behavior
Problem: Changes have been made in applications Product cost calculations and Trade cost calculations. On exiting these applications without saving no notification about changed data appears via “Close application” dialog.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is not locked. Another user thus can load, change and save the same product/trade cost calculation.
Correction result: Applications Product cost calculations and Trade cost calculations display “Close applications” dialog if data have been changed. Thus user can decide to stop closing application or to close application without saving.
If changes have been made and saving fails because of wrong data the edited product/trade cost calculation is locked. Another user can load, change but not saving due to a proper information about locked data.
RFR-016611 Correction
Framework: Production
Application: Cockpit: Production orders
View: Availability with material line items
Action: Specify available columns -> Material…
Category: Unexpected behavior
Problem: When adding the “replenishmentLeadTime” field (“reorderTime” from BO “Item planning data”) to the Material search via design mode, the system incorrectly displayed the planning data of the main production item for the entire production order, rather than the data for the specific material. Additionally, if the organization maintaining the planning for the production item differed from the organization for the material item, the field remained empty.
Correction result: The field now correctly shows the material’s planning data. It is also not affected by production item maintaining planning organization anymore.
RFR-016611 Extension
Framework: Production
Application: Bill of materials, Routings, Operations, Product configuration rules, Order maintenance
View: Dialog “Edit conditions with substitue and formulas”, “Product configuration rules” -> view “Conditions and actions”
Action: n. a.
Category: New action
Description: For above mentioned applications formulas and conditions are extended. Expressions can be defined using a wide range of operations on character strings.
Operations are: „substring“, „contains“, „starts_with“, „ends_with“, „last_index_of“, „index_of“, „length“, „replace“
Detailed information the help document will provide.
RFR-016611 Extension
Framework: Production
Application: Cockpit: Plant data collection postings, Reorganize plant data collection postings
View: n.a.
Action: Delete, Reorganize
Category: New action,New application
Description: Add the delete action to the cool bar of Cockpit: Plant data collection postings. This enables users to delete Plant data collection posting entries. Additionally, add new reorganization application Reorganize plant data collection postings. This allows the automatic deletion of completed postings above a certain age.
5.1.6.3 Production orders
RFR-016611 Correction
Framework: Production
Application: Receipt of goods/Production Orders
View: Production
Action: Post receipt of goods
Category: Exception
Problem: Automatic reporting of production orders when booking receipts of good sometimes led to an IllegalStateException.
Correction result: Automatic reporting of production orders works as intended.
RFR-016611 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Edit condition with substitute or formula of selected line item
Category: Exception
Problem:
1. When cross-site operation has formula of type “Buffer time before” or “Buffer time afterward” in production order, opening that formula via button in detail list caused exception.
2. The operation type details within a production order incorrectly displayed formula types as “Processing time” and “Setup time.” These formulas actually affected the operation’s quantity, not its duration as their names suggested.
Correction result:
1. The “Buffer time before” and “Buffer time afterward” formulas now open correctly from the production order details for cross-site operations and can be properly modified, regardless of how they were created or which button is used.
2. The formula type descriptions have been corrected. The production order’s operation details now accurately display quantity-based formula types, clarifying their true impact.
RFR-016611 Correction
Framework: Production
Application: Cockpit: Production orders/material line items
View: n.a.
Action: Export objects according to search criteria
Category: Exception
Problem: When trying to export object from “Cockpit: Production orders/material line items” in batch, the exception occurred.
Correction result: There is no exception during export anymore resulting with successful export in batch.
5.1.6.4 Production plans
RFR-016611 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer/Update planning data and execute planning
Category: Unexpected behavior
Problem: A product P uses a bill of resource BOR_Z which itself uses a bill of material BOM_Z. A line item of bill of material BOM_Z is another (phantom) bill of material BOM_X. If product p is planned ending up with some recommendation the calculated secondary demands of material belonging to phantom bill of material BOM_X are wrong. Reasons is that the ratio between reference factor of BOM_Z and quantity of line item BOM_X is not regarded properly in calculation of secondary demands.
Correction result: In above described context ratio between reference factor of BOM_Z and quantity of line item BOM_X is regarded properly and calculation of secondary demands works well.
5.1.7 Purchasing
5.1.7.1 Purchase order confirmations
RFR-016611 Correction
Framework: Purchasing
Applications: Purchase orders, Supplier confirmations
Action: Validate line item
Category: Unexpected behavior
Problem: A purchase order and purchase order correspondence were created. After that the item replacement status was changed (e.g. to the value “Expired if availability = 0”).
Up from that a supplier confirmation can not be created that belongs to such a purchase order correspondence (e.g. error message “PUR, 1395”).
Correction result:
1. Purchase orders: – For new line items the “Item replacement status” will be checked now only if the line item is not canceled and the correspondence status is “Not ordered” and confirmation status is “Not confirmed”.
– For persistent line items that are changed from “Canceled” to “Not canceled” the “Item replacement status” will be checked now but only if the correspondence status is “Not ordered” and confirmation status is “Not confirmed”.
2. Supplier confirmations: The “Item replacement status” will be checked now only if the line item is not canceled and the item is different from the relevant purchase order correspondence line item.
5.1.7.2 Supplier invoices
RFR-016611 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate delete
Category: Invalid data / Unexpected behavior
Problem: Internal supplier invoices must not be deleted. The “Delete action” is disabled for such invoices but before this correction it was possible to perform the “delete” functionality directly on the logic level if the invoice is not already booked.
Hint: This might be the case if the creation status “Released” is used in case of invoices that are based on distribution orders.
Correction result: Now the delete validation prevents by a new error message the deletion.
5.1.8 Relationship Management
5.1.8.1 Opportunities
RFR-016611 Correction
Framework: Relationship Management
Application: Opportunities
View: n.a.
Action: Validation
Category: Ergonomics
Problem: Individual validation messages are not displayed correctly in Classification fields in Opportunities application.
Correction result: Individual validation messages are displayed correctly in Opportunities application.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016611 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 Sales fast entry vouchers
RFR-016611 Correction
Framework: Sales
Application: Sales fast entry vouchers transfer
Action: Execute
Category: Unexpected behavior
Problem: Within the “Sales fast entry voucher” base data you can specify if warnings should be confirmed automatically. The automatic transfer by the background application “Sales fast entry vouchers transfer” considers this property but has a mistake: If for any “Sales fast entry voucher” the functionality “Confirm warnings automatically” is activated also for all further Sales fast entry voucher” instances the warnings will be confirmed automatically – even if they have not activated this functionality.
Correction result: Now for every “Sales fast entry voucher” instance the specified “Confirm warnings automatically” value will be used.
In addition to that now a message log entry will be send for a “Sales fast entry voucher” instance if the status changes to the value “Error in automatic transfer”.
5.1.9.3 Sales orders
RFR-016611 Correction
Framework: Sales
Applications: Distribution orders, Sales orders
Category: Exception / Invalid data / Unexpected behavior
Problem: If an order line item contains a specified serial number (with or without inventory management) the total quantity can be only “one base unit”.
But it was possible to specify a “Allocated quantity” (“delivery order/picking order”, “delivery slip” or “cash invoice”) different from one.
As result an exception occurs during the delivery process.
Correction result: Now the “Allocated quantity” (“delivery order/picking order”, “delivery slip” and “cash invoice”) will be checked as expected.
Please note that you have to correct wrong data manually.
5.1.10 Storage Location Control
5.1.10.1 Inventory management server
RFR-016611 Extension
Framework: Inventory Management, Customizing
Application: Inventory Management Server, Customizing, Cockpit: Warehouses
View: n.a.
Action: Save
Field/Column: Service user, Responsible employee
Category: New application / New action
Description: The new system based functionality of using service users and the consideration of the new capability to specifiy server service settings was added to the inventory management server.
Therefore the customizing got a new function “Lagerlogistik-Server” (Inventory management server) for inventory management server to specify service settings optionally.
The application inventory management server was extended to support those new functionalities for service users.
There is also a new cockpit application for warehouses with a new action to assign inventory management server to selected warehouses.
Data update: The data update application UPDADU123241 to initialize the new customizing function should be executed.
5.1.10.2 Inventory orders
RFR-016611 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: Generate inventory order…
Category: Unexpected behavior
Problem: If at least one line item is completely not reserved (outgoing process; fix reservation) the whole inventory order generation process would be aborted.
Correction result: The inventory order can be generated as expected. If fix reservation is active and there is a not reserved line item only this line item will be ignored.
5.1.10.3 Inventory requisitions
RFR-016611 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Import
Category: Unexpected behavior
Problem: The responsible employee could not be imported. The current user was already used.
Correction result: If a valid responsible employee is specified it will be imported as expected.
5.1.10.4 Storage locations
RFR-016611 Correction
Framework: Storage Location Control
Application: Cockpit: Storage location inventories
View: Standard
Add a column as search criteria
Category: Unexpected behavior
Problem: The deprecated attribute abc classification from the storage location type was selectable although it has no function since a long time. This was confusing and some clients used this attribute instead of the abc classification from the inventory item.
Correction result: The old and not used attribute abc classification from storage location type was removed from the search and it is no more selectable as expected.
5.2 System development
RFR-016609 Correction
Framework: System Management
Tool: Export System / Import System
Category: Ergonomics
Problem: The combination of auto commit and fetch size was wrong for Postgres leading to unnecessarily high memory usage.
Zipping in ExportSystem and unzipping in ImportSystem is slow.
Correction result: usage of auto commit repaired.
Performance improvement concerning zip respectively unzip.
RFR-016609 Correction
Framework: System Management
Application: Export data
View: n.a.
Action: n.a.
Category: Exception
Problem: NullPointerException will be thrown on the search restriction, if a search field is dependent on an organization.
Correction result: Search restriction works properly.
RFR-016609 Correction
Reduction of exceptions during dialog operation.
RFR-016609 Correction
Framework: Software developement
Tool: actbo, rgzbo
Action: Dropping columns with contraints
Category: Exception
Problem: In 6.5 the possibility to create new columns with data base defaults was invented.
SqlServer is a special case for it creates constraints for these defaults.
Therefore the constraints have to be dropped before dropping the columns is possible.
If you drop more than one column created before 6.5, then a fault in the syntax for dropping these constraints lead to an exception.
Correction result: It is now possible to perform such a drop column operation on a SqlServer.
Technical information: The key word “Drop” has to appear only one time, while “CONSTRAIN IF EXISTS” for every possible constraint.
DROP CONSTRAINT IF EXISTS DF_ABCDV_MYTABLE_MYATTR1,
CONSTRAINT IF EXISTS DF_ABCDV_MYTABLE_MYATTR2;
RFR-016609 Correction
Framework: System Management
Application: Export data
Solve problem with Dynamic objects on OQL export controller.
5.2.1 Data exchange
RFR-016609 Correction
Framework: All
Application: Cockpit applications
Action: Export according to search criteria
Category: Exception
Problem: In certain cockpits, when data is exported using action “Export objects according to search criteria”, and the batch dialog is accepted by button “In background”, the batch job may be canceled with an exception message like “java.lang.NullPointerException (…) at com.cisag.sys.gui.lnf.Theme.isTouchUI (…)”.
Correction result: The problem is resolved.
Technical information: The problem occurs in specific cockpits, when specific columns are shown.
RFR-016609 Correction
Framework: n.a
Application: Rest Web service
View: n.a.”
Action: n.a.
Category: Ergonomics
Problem: Error message is not clear for not existing input parameter.
Correction result: Error message is for not existing input parameter.
5.2.2 Kernel
RFR-016609 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Problem: If a lock on application level was granted, an exception was stored internally. This exception was never used.
Correction result: The creation and storage of these unused exceptions have been removed to optimize resources.
Technical information: Optimization in lock management: When an application lock is granted, no exception is instantiated anymore.
RFR-016609 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Description:
Internal performance optimization regarding individual validations.
Technical information:
Optimization in com.cisag.sys.tools. validation.log.AbstractCustomizableAdapter.call(Method, Object…): The parser was previously created before checking if a script exists. To improve performance and avoid unnecessary object creation, the parser is now instantiated only after the check confirms that a script exists.
5.2.3 System – General
RFR-016609 Correction
Framework: System
Application: System Engine
View: n. a.
Action: n.a.
Category: Unexpected behavior
Problem: The internal exception handling for date and time parsing created unnecessary stacktraces, impacting performance.
Correction result: The creation of stacktraces has been optimized and is now disabled by default.
Technical information: Optimization in com.cisag.sys.kernel.time.CisDateAndTimeParserException: This exception is a CisMessageException. Often the stacktrace is not important, but the message is. The creation of the stacktrace is now disabled by default, but it can be enabled with a debug switch (level: 3).
5.2.4 Web server
RFR-016609 Correction
Framework: System Management
Application: BIS export web services
View: n.a.
Action: n.a
Category: Unexpected behavior
Problem: Web service export to much attributes, even if those attributes are not checked on their export filter.
Correction result: Web service export only checked attributes on their export filter.