| Release | Comarch ERP Enterprise 6.3 |
| Release date | 15.12.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.
This fix comprises the following support deliveries: RFR-016590– RFR-016592
Information about the features of Comarch ERP Enterprise 6.3 (release news): · INF- 002654 Release-News: Betriebswirtschaftliche Lösungen · INF-002656 Release News: Business Solutions · INF- 002655 Release-News: Technische Lösungen · INF-002661 Release-News: Technical Solutions
System requirements: · INF-002659 Systemvoraussetzungen Comarch ERP Enterprise 6.3 · INF-002660 System Requirements Comarch ERP Enterprise 6.3
To install the support deliveries, please use the following documentation: · “Introduction: Software Logistics” (German language version) · „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.
The cumulative installation of support deliveries is described in INF-000228.
In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”. |
1 Information about support deliveries
The “Query support deliveries” application in the support system allows you to download directly from Comarch ERP Enterprise the support deliveries with their corresponding delivery documentation as well as further information.
The following types of support deliveries are relevant for you:
- RFR
This type of support delivery comprises a software upate or a file delivery as well as the corresponding delivery documentation.
- INF
This type of support delivery is used to provide FAQ-like information in a document.
- LNG
This type of support delivery is used to deliver language updates that can be installed in addition to German (de).
- 900
This type of support delivery comprises adaptors for the communication with third-party systems. - APP
This type of support delivery comprises installable Apps as well as the corresponding delivery documentation.
The available support deliveries are displayed in the “Query support deliveries” application according to the selected release, delivery, or delivery date. You can search for support deliveries and download their content. You can also find out whether new support deliveries are available. The application keeps a log on who has displayed which information or downloaded which software update, and when.
Note:
You need appropriate authorizations to download files. Please refer to the application documentation of “Support deliveries query”. If the relevant authorization is missing, please contact your Comarch support partner.
2 Installation of software updates
Follow the instructions given in the documentation “Introduction: Software Logistics” to install the software updates that are contained in the support deliveries. If there are deviating instructions to be followed, they are provided in chapter “Information about CEE630PB-Fix26”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE630PB-Fix26
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix25 will be upgraded to CEE630PB-Fix26.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”.
3.2 Cumulative installation of support deliveries
Code status CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
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.
UPDSUP122696
SalesDetailGroupDocumentData: Initializes the missing domestic currency
attributes
Instances of the BO “SalesDetailGroupDocumentData” were accidentally
created with empty values for the internal attributes “_organization,”
“_conversionDate,” and “_currencyCombo.” This data update application fills
empty attributes with the values of the corresponding owner BO
(CustomerProposal, SalesOrder, or Confirmation).
UPDBUG030255
Items – update inherritance
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.
5 Contained changes and extensions
5.1 Application development
RFR-016592 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-016592 Correction
Framework: Base
Application: Items
View: n.a.
Action: Opening field search for item properties
Category: Unexpected behavior
Problem: Long text fields cannot be used in searches because their content is stored in a blob. Nevertheless, the field was displayed in the item properties search. However, input had no effect on the search.
Correction result: The field is displayed as Disabled. A tooltip indicates that the field cannot be used in the search.
RFR-016592 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016592 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.
5.1.1 Base
5.1.1.1 Base – General
RFR-016592 Correction
Framework: v
Application: Export data
Object: com. cisag.app.purchasing.obj.PriceDefinition
Category: Unexpected behavior / Ergonomics
Problem: The label of the “Supplier price hierarchy” field has the wrong text “Customer price hierarchy”.
Correction result: Now the label is as expected.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016592 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 no 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.
RFR-016592 Correction
Class: com.cisag.app.general.order.log. SourceViewStateUtility
Method: <S extends HookState> S getHookState(Class<S> 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-016592 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-016592 Correction
Frameworks: purchasing and sales
Applications: proposals and orders
Action: refresh
Category: Unexpected behavior
Problem:
1. Purchasing and sales: The used “currency converter” and “price calculation” will be refreshed with respect to a changed “price date”.
2. Sales only: The used “price calculation” will be refreshed with respect to a changed “kind of pricing”.
In some cases this refreshment was not performed or performed to late so that in some cases the wrong data was used – especially during the header discount values calculation.
Also the “load” step does not initialize in case of sales the “kind of pricing” of the “price calculation”.
Hint: Normally these errors does not have any negative effect because any relevant detail change will also trigger a refreshment of this data and also of the header discount values.
Correction result: To avoid problems the correct initialization and refreshment will be performed now.
Hint: If needed you can recalculate wrong proposals/orders.
5.1.1.3 Currencies
RFR-016592 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.2 Calculation
RFR-016592 Extension
Framework: Calculation, Base
Application: Items, Import data
View: Financials
Action: Creating, Saving or Importing an Item with one or many Financial views
Category: Performance
Description: Creating a new Item through Items application or Import takes a lot of time to save the item prices of each Financial view to the history of item prices. This can take around 100ms per financial view.
Performance is now improved by a factor of 5 to around 20ms per financial view, especially helping batch import of lots of items and lots of financial organizations.
RFR-016592 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 Financials
5.1.3.1 Debtor credits
RFR-016592 Correction
Framework: Financials
Application: Debtor credits
Action: Reduce unallocated credit reservations
Category: Unexpected behavior
Problem: The “Reduce unallocated credit reservations” logic considers a “isReducible” functionality that is based on a “DebtorCreditReservationReducibleHook”. This hook is implemented for “sales orders” by “com.cisag.app.sales.debtorcredit.log.SalesOrderDebtorCreditHookImpl”.
By mistake “SalesOrderDebtorCreditHookImpl” returns false also for “debtor credit reservation details” that does not have the order type value “sales order”. As result all other order type value can not be reduced.
Correction result: Now the “SalesOrderDebtorCreditHookImpl” returns true if the “debtor credit reservation detail” does not have the order type value “sales order”.
So this hook implementation does not prevent any more the reduction of “debtor credit reservation details” that belong to other order types.
5.1.4 Inventory management
5.1.4.1 Delivery orders
RFR-016592 Correction
Framework: Planning
Application: Production recommendations
View: n.a.
Action: All generate/create production orders actions that dispatch order
Category: Unexpected behavior
Problem: Production recommendation of quantity 1 is generated for item with “Identifier category” set to “Serial number with inventory management” and “Creation methods” of “Identifier defaults” set to “Automatic”. Production order type used for generation has field “Time of determination of identifier” set to “When dispatching the production order”. Trying to perform generation of production order with dispatching for that configuration displayed multiple errors about not existing identifier, but production order was generated and dispatched, but without identifier.
Correction result: Identifier is now correctly created and set to newly generated production order without any errors.
RFR-016592 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Complete delivery order and generate and output delivery slips…
Category: Unexpected behavior
Problem: After clicking this action confirming a warning because of a delivery block for the customer has no effect, … even if the delivery should be allowed because confirming the warning is allowed in the application “Customizing” (Function “Finance).
Correction result: From now after clicking this action confirming a warning works as expected.
5.1.4.2 Inventory management – General
RFR-016592 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 has 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.
5.1.4.3 Inventory postings
RFR-016592 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.
5.1.4.4 Loads
RFR-016592 Correction
Framework: Inventory
Application: Cockpit: Shipping loads
View: n.a.
Action: Mark as deleted
Category: Unexpected behavior
Problem: It was possible to mark a shipping load as deleted, that is not shipped already.
Correction result: From now marking a shipping load as deleted, that is not shipped already, will cause an error message.
5.1.4.5 Picking orders
RFR-016592 Correction
Framework: Inventory Management
Application: Picking orders
View: n.a.
Report set item and its kit items
Category: Exception
Problem: If a set item was reported that was supporting fixed reservations save would cause an exception.
Correction result: The set item and its component can be reported as expected.
5.1.5 Multi-site capability
5.1.5.1 Distribution order types
RFR-016592 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
RFR-016592 Correction
Framework: Purchasing
Application: Distribution recommendations
View: n.a.
Action: Generate distribution orders
Category: Unexpected behavior
Problem: If an error occurred during the generation of orders from distribution recommendations, the entire process was canceled, including for valid recommendations.
Correction result: The error handling now operates differently based on the level at which an error occurs:
– header level error: If an error is found in the order’s header, the entire order and all of its corresponding recommendations are skipped.
– detail level error: If an error occurs in a specific detail line, only the recommendation associated with that detail is skipped. The rest of the order will continue to be processed.
A new validation for detail level errors has been introduced, controlled by new system property that is enabled by default. If this property is disabled, any detail level error is treated as a header-level error, causing the entire order to be skipped.
Technical information: New system property has been added to control detail validation during creation of distribution orders from recommendations: com.cisag.app.purchasing.log.GenerateDistributionOrder_ValidateDetails
RFR-016592 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.
5.1.6.1 Material requirements planning
RFR-016592 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning, Re-execute planning
Category: Unexpected behavior
Problem: Material requirements planning took a long time when a lot of items were planned, especially when planning multiple sites at once.
Correction result: Material requirements planning is faster, especially with many items and many sites.
5.1.6.2 Material requirements query
RFR-016592 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Unexpected behavior
Problem:
1. Message PRD-00485 displays in some situations incomplete informations: missing arguments. Messages PRD-00485, PRD-01078 and PRD-01099 in planning logs displays vague and unhelpful details.
2. Checkbox “Log untransferred line items” controls only displaying of message PRD-01078.
Correction result:
1. Old messages were replaced by new enhanced messages which provide precise details about real problems: * PRD-00485 replaced by APS-00125
* PRD-01078 replaced by APS-00123
* PRD-01099 replaced by APS-00124
2. Checkbox “Log untransferred line items” can now be used to determine if messages APS-00125 and APS-00123 are displayed in planning log file.
5.1.6.3 Planning conflicts query
RFR-016592 Correction
Framework: Planning
Application: Cockpit: Planning conflicts
View: n.a.
Action: Refresh
Category: Exception
Problem: Picking order from delivery order for sales order needs to be generated for item with at least one packaging unit. Unit of total quantity and reported quantity of delivery order needs to be different, but both acceptable for chosen item.
After performing planning which starts after voucher date of delivery order for that item the planning conflict about “Finished/Semi-finished goods demand in previous period” should be generated. Opening “Cockpit: planning conflicts” for that item caused exception due to different unit of measurement for total and reported quantity of a delivery order detail.
Correction result: Now units are properly converted to the total quantity unit and exception does not occur anymore.
5.1.7 Production
RFR-016592 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.
5.1.7.1 Production – General
RFR-016592 Correction
Framework: Production
Application: Order maintenance
View: Detail editor
Action: New detail
Category: Exception
Problem: If a production order is marked for deletion, it is still possible to create new detail line items of all possible detail types. If such an action is executed an exception occusrs.
Correction result: If a prduction order is marked for deletion all relevant production specific actions are disabled. No action at detil level can be performed.
5.1.7.2 Production issues
RFR-016592 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: Save, Validate
Category: Exception
Problem:
1. Before loading any production order entering proper production order type and number and performing action save caused exception.
2. Before loading any production order performing validation for empty order type and number fields caused exception. Additionally, perfoming validation with proper type and number of order entered, but before loading it caused the load of production order, but with missing detail loading.
Correction result:
1. Action “Save” is now disabled if order is not loaded.
2. Action “Validate” is now disable if order is not loaded. Action load now properly displays errors about missing number and type of an order.
5.1.7.3 Production order types
RFR-016592 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.7.4 Production orders
RFR-016592 Correction
Framework: Production
Application: Production order
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Opening any production order which was dispatched with empty “Dispatching date” automatically enters edit mode, trying to set proper value to this field even if order was already completed.
Correction result: New data update has been created to update empty “Dispatching date” in all already dispatched orders to avoid entering edit mode in “Production orders”.
Technical information: The possibility to keep that “Dispatching date” empty was fixed in one of the previous fix. This date is now set automatically during dispatching or manual adding of a detail. It means the problem occur only for production orders that was created/completed before mentioned previous fix.
Data update: UPDSUP122635
Sets “Dispatching date” for all dispatched production orders to proper value based on earliest begin, latest end and scheduling category of an order header.
5.1.8 Purchasing
5.1.8.1 Purchase orders
RFR-016592 Correction
Framework: Purchasing
Application: Purchase orders
Action: Apply defaults, “Delivery dun” creation
Category: Unexpected behavior
Problem:
1. Before this change the “Delivery dun output settings” of a purchase order were determined by the “delivery partner” (“delivery supplier”); also, the purchase order line item “delivery partner” was checked versus tbe current “delivery dun output settings”.
2. The “Delivery dun” generation uses the main supplier of the purchase order (also for some checks and also as “archive partner”).
==> If the “main supplier” and the “delivery partner” are different and the “main supplier” does not support the determined output settings the delivery dun creation fails.
Correction result: Because the responsible business partner of a purchase order is the “main supplier” up from now the following rules will be used:
1.) The “Delivery dun output settings” of a purchase order will be determined now by the “main supplier”.
2. The purchase order line-item validation (“delivery partner” versus “delivery dun output settings”) was removed.
3. “Output settings” table: If the current value is not defined (valid) it will be added now to the visible values – before this correction an empty value was displayed in this case.
Hints:
1. Please note that with respect to this change the old “delivery dun output settings” value of a purchase order might not be valid any more and needs to be corrected manually.
2. Within an extra development order the online help will be changed – also here the “delivery partner” is defined as relevant – this needs to be changed.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016592 Correction
Framework: Sales
Applications: Sales orders, Distribution orders, Customer invoices
Action: Cancel customer invoices
Category: Invalid data / Unexpected behavior
Problem: A sales order line item is present with the following data:
– the sales order line item has a zero total quantity
– the sales order line item has some order value discounts (at least one)
The invoice generation creates correct data.
But the invoice cancelation does not report the correct (negated) value of the “order value discounts” – as result the next invoice generation does not consider the correct discount values.
Correction result: Now the invoice cancelation reports also in this case the correct discount values.
Hint: In analogy also the status update logic for distribution orders has been changed but here normally no zero total quantity can be used.
Data update: If needed wrong existing data have to be changed manually. The recommended way is the following:
– Cancel all invoices of the relevant order line items.
– if “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount” is present for the relevant sales order line items: set “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[0]” until “com.cisag.app.sales.obj.SalesOrderDetailValueDiscount:invoicedAbsoluteDiscount[3]” by OQL for the entry with the relevant order detail guid to zero.
– create again the invoices
RFR-016592 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 redermined – 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 coporate currency.
5.1.9.2 Sales – General
RFR-016592 Correction
Framework: Sales
Applications: Customer proposals, Sales orders, Sales confirmations
Functionality: Detail group support
Category: Invalid data / Unexpected behavior
Problem: By mistake instances of the business object SalesDetailGroupDocumentData were created with empty values for the internal attributes “_organization”, “_conversionDate” and “_currencyCombo”.
Correction result: Now these attributes will be maintained as expected.
Data update: Please execute the data update application UPDSUP122696 to correct the existing data.
5.1.9.3 Sales fast entry vouchers
RFR-016592 Correction
Framework: Sales
Application: Sales fast entry vouchers
Action: Calculate tax
Category: Exception
Problem: In case of “retail calculation” an exception occurs during the step “Calculate tax” if the same application instance is used for multiple sales organizations.
Correction result: Now the exception does not occur any more.
RFR-016592 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.
RFR-016592 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 errror message informs the user that the price must either be determined or specified manually.
RFR-016592 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 any more.
5.1.9.4 Sales orders
RFR-016592 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.
5.1.10 Storage Location Control
5.1.10.1 Put-away
RFR-016592 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 genrated as expected and set.
5.2 Infrastructure
5.2.1 Installing software updates
RFR-016592 Correction
Framework: Data Update
Application: com.cisag.app. update.log.UPDADV107259
View: n.a.
Action: Execution of data update
Category: Exception
Technical information: The use of CisTransaction#commitIfSizeLimitExceeded() when updating data, to close and reopen database transactions only when necessary, caused problems with memory requirements, so that fixed block sizes had to be reintroduced in order to better control the memory requirements of this data update.
5.3 System development
RFR-016590 Correction
Framework: n.a.
Application: n.a.
View: n. a
Action: n.a.
Category: Unexpected behavior
Problem: Sometimes Method “com.cisag.pgm.base.CisApplication.setObjectDescription(String)” will be called with too long parameter string.
Correction result: “com.cisag.pgm.base.CisApplication.setObjectDescription(String)” will reduce the input parameter string to length 1000, if it longer than 1000.
RFR-016590 Correction
Class: CisObject
Method: copyTo, getTransientCopy
Description: in CisObject there is a content language field. This field only has effect when the user changes the “content language” settings field in the user settings application.
Setting a content language deviating from standard can cause issues when copying the data because the content language information was not transferred from the source to the target object.
When copying the content of a CisObject into another instance the content language is now copied as well. Only in the case that the target object is not transient (i.e. intended to be put by the object manager),
then the language is not set.
Copying CisObject with differnent content language is discouraged but technical possible.
RFR-016590 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 more exception
RFR-016590 Extension
Framework: all
Application: Caching Mechanism
View: n.a.
Action: the change addresses a system-wide performance issue.
Category: Unexpected behavior
Problem: All Business Objects (BOs) that contain a BLOB did not have a cache strategy. The framework intentionally prevents caching for such objects by default to avoid high memory consumption. However, for specific BOs with small BLOBs that are accessed frequently, this restriction led to significant performance problems, as they were reloaded from the database on every access.
Correction result: A new override mechanism has been implemented. For a predefined list of BOs, the default restriction is now bypassed, and a cache strategy of LRU (Least Recently Used) is applied. This resolves the performance issues by allowing these frequently used objects to be cached effectively.
RFR-016590 Correction
Framework: software development
Application: development objects
Action: validate for new objects
Category: Unexpected behavior
Problem: If a development object has a connected text data object and you just validate data, then any error message is shown because the name of the text data object is not yet set.
Similar problem with the file names for a java class object
Correction result: Before validating the names are now set.
Technical information: Directly saving works because in this case the names were set beforehand.
5.3.1 Application server
5.3.1.1 StartUp
RFR-016590 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-016590 Correction
Framework: System Management
Execution of incoming web services
Category: Unexpected behavior
Problem: Depending on the desing of a web service, some parts of the request message could be shown in System cockpit, Sessions tabs, as instance description, during exeuction of the web service.
Correction result: The described information is no longer shown, as it could be long, or contain sensitive data.
RFR-016590 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-016590 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 removed it from its Business entity.
Correction result: Foreign key on a business entity can be removed.
5.3.3 GUI
RFR-016590 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.
5.3.4 Kernel
RFR-016590 Correction
Framework: System
Application: Core System / Parser Infrastructure
View: n.a.
Action: n.a.
Category: Performance Improvement
Description: This change significantly improves the performance of internal parsing operations within the system. By optimizing the handling of frequently occurring internal `Error` instances, the system will process parsing tasks faster and consume less memory. This leads to a more responsive and efficient overall system.
Technical information: JavaCC parsers often utilize internal `Error` subclasses, such as `LookaheadSuccess`, as a control flow mechanism. These `Error` objects can be instantiated very frequently during parsing. Normally, the creation of an `Error` object involves the costly operation of filling the stack trace. By overriding the `fillInStackTrace()` method within the `private static final class LookaheadSuccess extends Error` to simply return `this`, the overhead associated with generating these stack traces is entirely eliminated. This optimization substantially reduces CPU cycles and memory consumption, thereby enhancing the performance of parsing operations and lessening the load on the Java Garbage Collector. This is particularly effective in scenarios where this internal `Error` is frequently created but its stack trace is not crucial for error handling or debugging purposes.
5.3.4.1 Locking / Caching
RFR-016590 Correction
Process: Lock request
Category: Exception
Problem: A lock request might cause a deadlock. If any involved requested lock is a job lock (as opposed to an application lock), an ArrayIndexOutOfBoundsException (“arraycopy: last source index 32 out of bounds for byte[16]” at com.cisag.sys.kernel.locking.CisLockTable$DeadlockResponder. handleEntry) occurs.
After 10 subsequent deadlocks, an “IllegalStateException: Queue full” (at CisLockTable.createDeadlockResponse) is thrown.
Correction result: No exceptions.
5.3.5 ODBC
RFR-016591 Correction
Process: Initialization of virtual functions in ODBC
Category: Exception
Problem: If the Method getTablePath() in an implementation of pgm.base. CisODBCVirtualFunction returns an invalid LDT path (invalid namespace, LDT does not exist), a NullPointerException (at com.cisag.sys.dictionary.log.LogicalDatatypeLogic.load) will occur the first time all implementations are initialized. (This will be performed during various actions, e.g. installation of language refreshes.)
Correction result: The invalid implementation is skipped with a message SYS-6612 in the system log.
5.3.6 Searches
RFR-016590 Correction
Framework: n.a.
Application: All cockpits
View: n.a.
Action: n.a.
Adding an attribute of a releation based detailsearch.
Category: Exception
Problem: If the user adds an attribute of a releation based detailsearch to the cockpit, and an update deletes this attribut an exception occurs when the user starts the cockpit.
Correction result: The exception does not occur.