| Release | Comarch ERP Enterprise 6.3 |
| Release date | 21.10.2022 |
| 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-016397– RFR-016399
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-Fix01”.
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-Fix01
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB will be upgraded to CEE630PB-Fix01.
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 data updates, for any point in time.
UPDADV096751
Datenumsetzung der Feldinhalte von PickingStatus und ProductionOrderPickingInfo
5.1 Application development
RFR-016399 Documentation
The help documents “Customizing: Rechnungswesen” and “Customizing: Controlling” have been updated regarding the fields for selecting the respective adapters.
RFR-016399 Correction
Framework: Production
Application: Production orders
View: Base view
Action: Save
Category: Unexpected behavior
Problem: Use a production order type with “Time of determination of identifier” = “While generating the production order without abort function”.
Create a production order with this production order type and save.
After a new saving (e.g. after dispatching or manual change of some base view data) error message PRD-936 “Specified serial number cannot have inventory.” occurs and saving fails.
Correction result: Error message must not occur when saving production order unless identifier is changed and new identifier is already allocated to another voucher which is source of a later receipt.
Error message must occur on creation of production order if identifier is manually set and is already allocated to another voucher which is source of a later receipt.
RFR-016399 Documentation
The help document “Vertriebsaufträge” has been updated regarding the description of the “Shipping date” field.
RFR-016399 Documentation
Minor error in help document “Vorgehensweisen: Artikel, Ansicht „Disposition“” has been corrected.
RFR-016399 Extension
Hook contract definition: com.cisag.app.shipping.customs.interfaces.hook.log.CustomsClearance
Hook: “n.a.”
Description: The new hook contract definition is ment to replace CustomsClearanceAdapter implementations with Apps that can be built on com.cisag.app.shipping.customs.interfaces.hook.log.CustomsClearanceHook instead of com.cisag.app.shipping.customs.interfaces.spi.CustomsClearanceAdapter.
RFR-016399 Documentation
The following English help documents have been provided:
– Bills of Material
– Conditions, Formulas, Substitute Functions
– Where-used List
– Parameters for Resource Groups, Resources, and Operations
– Routings
5.1.1 Base
5.1.1.1 Classifications
RFR-016399 Correction
Framework: Base
Application: Classifications
Action: Delete node
Category: Invalid data / Unexpected behavior
Problem: Some business object attributes support the usage of any classification nodes (default: only leaves are allowed to be used). By mistake in some of these cases such an attribute was not registered as “all node usage”. So the classification application allows a deletion of a node, that is not a leaf, although a usage exists.
Correction result: Now all standard business object attributes that support “all node usage” have been registered.
Technical informations: – Some further errors have been corrected in the classes “com.cisag.app.general.log.HierarchyEntity” and “com.cisag.app.general.gui.HierarchyField”.
In addition to that some HierarchyRegistry “all node usage” registrations have been moved to some HierarchyUsageHook implementations.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016399 Correction
Application: Order applications
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the order cockpit applications, within the order applications the set/remove deletion marker (reorganization marker) actions are also enabled if the current user does not have the capability “com.cisag.app.general.order.DocumentReorganization”. Only the logic that tries to set or remove the deletion marker sends an error message.
Correction result: Now the standard order applications have been corrected so that the actions are only enabled if the user has the capability “com.cisag.app.general.order.DocumentReorganization”.
RFR-016399 Extension
Frameworks: Financials, Inventory, Purchasing, Sales
Actions: Display order reference, Field/Application search
Category: Unexpected behavior / Ergonomics
Problem: In some voucher/order applications the partner names and addresses can be changed and will be used also for some following vouchers. But the order reference chain and the field/application search are using the partner master data instead of the potentially changed voucher/order name/address data.
Correction result: Now the following order types/applications are using the relevant partner name and address as stored within the voucher:
– Supplier contracts
– Purchasing RFQs
– Supplier quotations
– Purchase orders
– Purchase order documents query
– Purchase order confirmations
– Receipts of goods
– Supplier invoices
– Prepayment requests
– Debtor credits
– Customer contracts
– Sales RFQs
– Sales quotations
– Sales orders
– Order confirmations query
– Pro forma invoices query
– Customer invoices query
– Invoice corrections
– Consignment withdrawal declarations
– Delivery orders
– Picking orders
– Customer returns
– Distribution requests
– Distribution orders
RFR-016399 Correction
Applications: Applications with order reference chain and order fields
Action: Open application for an archived sales order
Category: Unexpected behavior / Ergonomics
Problem: If the order reference chain or a field displays an archived/reorganized order with some archive data (currently only orders with the type “Sales order”), the order reference chain / field does not open the relevant cockpit application with the relevant instance.
Correction result: Now the relevant application (typically the cockpit for the archived data) will be started and opened with the relevant instance.
Note: Please note that only the header identification will be considered at cockpit start time as filter parameter (“type code” and “header number”).
5.1.1.3 Fiscal years
RFR-016399 Correction
Framework: Base, Financials
Category: Unexpected behavior / Ergonomics
Problem: The “Business periods” search (oql search “com.cisag.app.general. obj.FiscalPeriod”) shows multiple entries if multiple “com.cisag.app.general.obj.FiscalPeriod:use” values are present but the “use” value is not part of the result list.
Correction result: Now the search is marked as “DISTINCT” so that no multiple entries are present any more.
5.1.1.4 Text modules
RFR-016399 Correction
Framework: Base
Application: Import Data
Filter: any filter that allows to import text data (i.e. Item)
Action: Import
Category: Unexpected behavior
Problem: Text data couldn’t get imported if the text data is defined via text code in the import file
Correction result: From now the “text code” tag will be parsed correctly and the text data could get imported as expected.
5.1.2 Calculation
5.1.2.1 Cost types
RFR-016399 Documentation
The help document “Customizing: Rechnungswesen” has been updated regarding the field for determining the maximum cost type length.
5.1.3 Document Management
RFR-016399 Extension
Framework: Document management
Application: Documents
View: New dockable view for Documents
Action: Create note, Create document
Field/Column: Drag and drop area
Category: New view, New field, New action
Description:
1. Drag and drop area has been integrated into Documents application.
2. New documents dockable view has been integrated into Documents application.
3. New dialog for creating Notes has been attached to new dockable view.
5.1.4 Inventory management
5.1.4.1 Delivery orders
RFR-016399 Correction
Framework: Inventory Management
Application: Delivery orders
View: n. a.
Action: Generate and output delivery slips…
Category: Invalid data
Problem: Weights and volumes of kits contained in a delivery slip were counted twice. So the weights and volumes sum of the delivery slip was too high.
Correction result: From now the weights and volumes of kit will be counted correctely.
RFR-016399 Correction
Framework: Inventory Management
Application: Delivery orders
View: n. a.
Action: Output packing list
Category: Unexpected behavior
Problem: When preparing the document output data for the packing list the document receiver is set to the delivery receiver instead of setting it to the delivery document receiver. Therefore the delivery slip was printed in the wrong language if delivery receiver and delivery document receiver are from different countries.
Correction result: From now the packing list will be printed in the language of the delivery document receiver of the delivery slip.
RFR-016399 Documentation
The help document “Delivery orders” (German language version) has been updated regarding action descriptions.
RFR-016399 Correction
Framework: Inventory Management
Application: Delivery orders
View: n. a.
Action:
– Output delivery slip copies
– Output pickup slip
– Output delivery slip for external third-party order
– Output pickup slip copies
– Output third-party order delivery slip copies
Category: Ergonomics
Problem: The dialog for starting the listed output actions above contained a view for the parameters “voucher date” and “voucher date setting”. They were always without any function for theses actions.
Correction result: From now the dialog won’t contain a view for the parameters “voucher date” and “voucher date setting” for the listed actions above any more.
5.1.4.2 Picking orders
RFR-016399 Correction
Framework: Inventory Management
Application: Picking orders
Action: Output
Category: Unexpected behavior / Ergonomics
Problem: If a picking order contains line item texts, then these texts are not used for the output document.
Correction result: Now – as for other documents – defined line item texts will be used for the output document.
5.1.5 Planning
RFR-016399 Correction
Framework: Production
Application: Material requirements planning
Action: Transfer planning data
Category: Unexpected behavior
Problem: Items without planning data were logged as [ERROR] during material requirements planning, although they have no influence on the planning itself. Additional data was missing.
Correction result: Logging of unplanned items is now set to [FINEST] and the corresponding item and its organizational unit are logged as well.
5.1.5.1 Material requirements planning
RFR-016399 Correction
Framework: Planning
Application: Material requirements planning
View: n. a.
Action: …execute planning
Category: Unexpected behavior
Problem: Context: A planned receipts delivery date is previous to a demand A. No underrun of minimum inventory level at date of demand A, that is: no recommendation at this period. But date of demand A is NOT a working day.
A conflict “Early order” is adressed to the receipt with respect to date of demand A (not a working day).
Correction result: Reference date for a conflict “Early order” should be a regular working day. As reference date for conflict “Early order” in above context is not a working day the next previous working day is specified for reference date of conflict “Early order”.
5.1.6 Production
RFR-016399 Extension
Framework: Production
Application: Service bills of material
View: n. a.
Action: deactivate service bom line item
Category: Ergonomics
Problem: somewhat cumbersome procedure when deactivating a service bom line item
Correction result: simplified procedure for deactivating a service bom line item
RFR-016399 Correction
Framework: Purchasing
Application: Calculate purchase recommendations
View: n. a.
Action: Calculate purchase recommendations
Category: Unexpected behavior
Problem: The time horizon to calculate projected inventory quantities was too low when the demand was at the very end of reorder time range after the per-date.
An empty inventory was assumed because the values for this late date was not calculated.
The demand must come from a reorder level underrun.
Correction result: For a reorder level underrun at the end of the examined time range (per-date + reorder time) the inventory receipt date is calculated by adding the reorder time. The order amount must be according to the projected inventory at this date.
So the availablility calculation time horizon is now at least two times the reorder time of the item.
RFR-016399 Extension
Framework: Production
Application: Production orders
View: n. a.
Action: n. a.
Field/Column: Flag to have a dragbar between line item table and editor
Category: New action
Description: It is now possible to move the sizes of the line item table and editor areas using the mouse.
RFR-016399 Correction
Framework: Production
Application: ServiceBillOfMaterial
View: n. a.
Action: n. a.
Field/Column: checkbox: semi-finished good
Category: deleted checkbox
Description: The checkbox semi-finished good is removed from the application Service bill of material because of lack of sense.
5.1.6.1 Production orders
RFR-016399 Correction
Framework: Production
Application: Production orders
View: n. a.
Action: n. a.
Category: Unexpected behavior
Problem: Due to an incorrect initialisation of the field
ProductionOrder.pickingInfoStatus, the production order goes into editing mode after loading.
Correction result: After correcting the data, the production order no longer goes into edit mode after loading.
Technical information: A pre-correction already made with OQL that sets the content of the field pickingInfoStatus from “0” to “5” was not correct because 5 stands for “NOT_APPLICABLE”. This means there is no commission context. This would be wrong for production orders with a commission context.
The correct procedure for correcting the field is described under hints for testing.
Data update: The application UPDADV096751 must be called up in the menu Data updates query
5.1.6.2 Routings
RFR-016399 Correction
Framework: Production
Application: Routings
View: Routing / Tree view
Action: Lock version
Category: Unexpected behavior
Problem: The bar buttons save and validate will be set inactive when routing is blocked and was used in production order (e.g. dispatched)
Correction result: The bar buttons save and validate will be set depending on the setting in the server property com.cisag.app.production.bom.ui. AbstractMaintenance_ChangeReleasedProductionPlanAllowed
when routing is blocked and was used in production order (e.g. dispatched)
RFR-016399 Correction
Framework: Production
Application: Production order maintenance
View: n. a.
Action: Dispatch
Category: Unexpected behavior
Problem: In the course of processing a cross site production order exeptions occur.
(1)If main production order is dispatched a distribution order will be automatically generated. This generation fails due to an exception. This causes also the dispatching fails.
(2)If production order of target (remote) site is dispatched also a distribution order will be automatically generated. This generation fails due to an exception. This causes also the dispatching fails.
(3)If production order of target (remote) site is closed (e.g. in the course of a receipt if all details have been reported). also a distribution order will be automatically generated. This generation fails due to an exception. This causes also the dispatching fails.
Correction result: The described processing steps do not cause exceptions. They work as expected.
5.1.7 Purchasing
5.1.7.1 Purchase order confirmations
RFR-016399 Correction
Framework: Purchasing
Applications: Purchase order documents query, Purchase order confirmations
Action: Delete confirmation
Category: Exception / Invalid data / Unexpected behavior
Problem: If some changes (including deletion markers) are present within a confirmation that affect the correspondene header status and the “Delete confirmation” action was performed some correspondence header data will not be refreshed correctly.
Correction result: Now such changes will be ignored for the correspondence update and so the error does not occur any more.
Data update: No data update application is available. If the correspondence is not confirmed (reportedConfirmationStatus is 1/NONE and reportedConfirmation is null) also the PurchaseOrderCorrespondence attributes “reportedConfirmedCount”, “reportedConfirmedWithChangesCount”, “reportedConfirmedConditionsChangedCount” and “reportedConfirmationRejectedCount” needs to be zero.
5.1.7.2 Purchase orders
RFR-016399 Correction
Framework: Production
Application: Production orders / Purchase orders
View: n.a.
Action: Duplicate, Save
Category: Unexpected behavior
Problem: After duplicating an external operation within a production order, saving and switching to the corresponding purchase order, user actions in this purchase order were not executed and led to error “… purchase order is already edited by user”.
Correction result: User actions in the corresponding purchase order are working without error.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016399 Correction
Framework: Sales
Application: Customer invoices
Action: Cancel invoice
Category: Unexpected behavior
Problem: If an invoice references a debtor credit instance and a prepayment request the debtor credit allocation might be canceled already in some cases so that the customer invoice cancelation can not add a further debtor credit allocation cancelation.
Correction result: Now the “Customer invoice cancelation” logic checks if already a “debtor credit allocation cancelation” entry is present. If so the “add debtor credit allocation cancelation” sub step will be skipped and only the needed invoice debtor credit data will be created.
5.1.8.2 Pro forma invoices
RFR-016399 Correction
Framework: Sales
Application: Cockpit: Pro-forma invoices
Action: Refresh order reference chain
Category: Exception
Problem: If the order reference chain is tried to be refreshed an exception occurs.
Correction result: Now the exception does not occur any more.
5.1.8.3 Sales – General
RFR-016399 Documentation
Following help documents have been updated:
Bericht: Vertriebs-Anfragearten
Bericht: Vertriebs-Angebotsarten
Bericht: Vertriebs-Auftragsarten
Bericht: Verteilauftragsarten
5.1.8.4 Sales prices
RFR-016399 Correction
Framework: Sales
Application: Sales price lists
Category: Unexpected behavior / Ergonomics
Problem: The application displays for the case “End consumer prices” and the type “Standard” the “Basic price” in an own column. Before this correction the “Basic price” table column was also visible for views without an item, but an item is needed to determine the “Basic price”.
Correction result: Now the “Basic price” column is only visible for the views “Item”, “Customer + Item” and “Customer price classification + Item”.
5.1.8.5 Sales quotations
RFR-016399 Extension
Framework: Sales
Application: Sales quotations
Action: Validation
Category: New functionality
Description: Before this extension the new or changed value of the field “Binding period” needs to be in the future. To support some special cases also the current day can be used now.
5.2 Infrastructure
5.2.1 Consulting
RFR-016398 Correction
Framework: System management
Application: Dynamic indicators
View: n.a.
Action: Value assistant
Category: Exception
Problem: The value assistant for field “Activity definitions” yields exception “ValueSetField:try to set a invalid value : 12” upon opening. The value “Process: Function call-up” can’t be selected in search field “Kind”.
Correction result: Value “Process: Function call-up” allowed in search field and set as default. This also allows the search for this value in application “Activity definitions”.
5.3 System development
RFR-016397 Correction
Framework: SystemManagement
Tool: Update user certificates (rfrusrcrt)
View: n. a.
Action: n. a.
Category: Unexpected behavior
Problem: This tool does not work properly. An exception message “java.lang.IllegalArgumentException: key algorithm must be not null or key bits must not be zero” is displayed.
Correction result: The tool works properly. New user certificates are always sent via email. This requires a working certificate email delivery.
RFR-016397 Correction
Process: cache handling for supplements with an open transaction
Category: Exception
Problem: When reading objects in an asynchron manner and said objects have supplements, then it can happen that the cache handling fails with an exception.
Correction result: Cache handling repaired. No more exception.
RFR-016397 Correction
Framework: Software development
Application: Simplified data import
View: n. a.
Action: Importing supplement data
Category: Invalid data
Problem: It is possible to use Supplements as base for an external object. Using such an external object for simplified import did not work.
Correction result: Now it is possible to register an external object based on a supplement and used it for simplified import.
RFR-016397 Correction
Framework: Software development
Application: development object
View: external objecs
Action: foreign key resolving, removing from job
Category: Unexpected behavior
Problem: The dialog for defining how to resolve a foreign key does not always work properly if the same attribute belongs to several relations or target indices.
The possibility to remove an external object from a task was not implemented.
There was an error if the business object the external object is based on was new as well.
Correction result: The dialog now works properly. It is possible to remove an external object from the task.
The application can handle it if the business object is new as well.
RFR-016397 Correction
Framework: n. a.
Application: all report output applications
View: n. a.
Action: save
Category: Unexpected behavior
Problem: New Report output setting (definition) sometime can not be saved, with wrong message.
Correction result: New Report output setting (definition) can be saved properly.
RFR-016398 Documentation
The help document “ERP-Propertys” has been updated regarding the properties com.cisag.app.customizing.financials.CustomizableMaxAccountNumberLength and com.cisag.app.customizing.financials.CustomizableMaxCostTypeCodeLength.
RFR-016398 Extension
The help documents “Individuelle Prüfungen”, “System-Skriptsprache: Allgemeine Funktionen”, “System-Skriptsprache: OLTP-Funktionen” and “System-Skriptsprache: Workflow-Funktionen” have been updated regarding the use context of system script language functions.
RFR-016398 Correction
Framework: Software development
Application: Development objects
View: external objects
Action: foreign key resolving, removing from job
Category: Unexpected behavior
Problem: The dialog for defining how to resolve a foreign key does not always work properly if the same attribute belongs to several relations or target indices.
The possibility to remove an external object from a task was not implemented.
There was an error if the business object the external object is based on was new as well.
Correction result: The dialog now works properly. It is possible to remove an external object from the task.
The application can handle it if the business object is new as well.
5.3.1 Application server
RFR-016397 Correction
Framework: System management
Application: Dynamic indicators
View: n. a.
Action: Change field value
Category: Ergonomics
Problem: If the value in the selection field “database type” is changed, the application mode changes to “New” even if no indicator was loaded previously.
Correction result: Application remains in “Display” mode.
RFR-016397 Extension
Class: com.cisag.pgm.base. CisWebServiceApplication
Method: useWebServiceServerAsClient(), useWebServiceServerAsServer()
Description: Allows simultaneous use of an application server as web service server and client.
5.3.1.1 Autorizations
RFR-016397 Correction
Framework: System management
Application: Authorization roles
View: n. a.
Action: Generate or update according to template
Category: Invalid data
Problem: The newly created role can’t be saved, as its validity dates aren’t set and can’t be edited.
Correction result: Both dates are set to valid values.
5.3.1.2 Batch
RFR-016397 Correction
Framework: System Management
Executing batch jobs
Category: Unexpected behavior
Problem: A batch job in status “Released” and start mode “Add to queue” is not executed when an application server starts with enough free workers in the job queue.
Correction result: The problem is resolved.
5.3.1.3 JobControl
RFR-016397 Correction
Process: Starting an application
Category: Unexpected behavior
Problem: If an application is started or activated and fails to activate due to an exception while executing its method CisUiApplication::taskActivate(), it doesn’t terminate. It also can’t be closed, as this also calls taskActivate(). Especially, the application won’t free its ressources.
Correction result: Application is closed.
RFR-016397 Correction
Process: Job control closes application
Category: Exception
Problem: If an application is automatically closed (either because the maximum number of open applications is reached or memory is low), a RuntimeException “Application control block does not exist” might occur if the application to close is the current one and it tries to access its session’s application block upon exit, e.g. to release held locks.
Correction result: No exception.
Technical information: The application control block is valid throughout the application’s exit()-Method.
RFR-016397 Correction
Framework: Base
Application: Partners
View: Base
Action: Edit contact person
Category: Unexpected behavior
Problem: The pop-up dialog “Contact person” doesn’t display any yellow corners if the application “Partner” was previously opened via a context menu instead of the user menu. Also, there must be an active process definition with non-empty condition relating to the context menu.
Correction result: Yellow corners are displayed.
5.3.2 Kernel
5.3.2.1 Database tools (crtdb/wrkdb)
RFR-016397 Correction
Framework: System management
Tool: crtdbt
Action: n. a.
Category: Exception
Problem: A business object without an active version (usually created and locked in an open development job) yields a nullpointer exception.
Correction result: Objects without active version are ignored.
5.3.3 Web server
RFR-016397 Correction
Update Webserver to Jetty 10.0.12
RFR-016398 Correction
Update Webserver to Jetty 10.0.12