| Release | Comarch ERP Enterprise 6.3 |
| Release date | 13.06.2023 |
| 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-016442 – RFR-016444
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-Fix07”.
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-Fix07
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix06 will be upgraded to CEE630PB-Fix07.
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.
UPDBUG027822
Update activity tasks counters
Data update checks forwarded and waiting (to be processed) tasks counters and, if they are not consistent with real number of tasks with right status and updates wrong values. Works only with not completed activities.
5.1 Application development
RFR-016444 Correction
Framework: Base
Application: Items
View: n.a.
Action: Update / Accept data processing for the selected organization
Category: Invalid data, unexpexted behaviour
Problem: In special cases the acceptance of the data processing for the selected organization of a reference item was not transferred correctly to the variants.
Correction result: From now the acceptance of the data processing for the selected organization of a reference item will be transferred to the variants correctly.
RFR-016444 Correction
Framework: Base
Application: Company Calendar
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The date field in the editor’s coolbar did not always display the right date of the selected calendar day. This happened for example, if the user context is assigned to an organization with the time zone GMT.
Correction result: From now the date field in the editor’s coolbar will always display the right date of the selected calendar day.
RFR-016444 Ergonomics
Update of the English user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016444 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-016444 Correction
Framework: Inventory
Application: Distribution orders / Delivery orders
View: n.a
Action: n.a.
Category: Exception
Problem: An exception occurred creating a delivery order from a distribution order that contains more than 16 line items.
Correction result: From now creating delivery orders from a distribution order will work as expected.
RFR-016444 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Generate transport order
Category: Ergonomics
Problem: The red corners after displaying an error message were placed at a wrong visual element. So double clicking the message opened the address dialog of the delivery recipient.
Correction result: From now the red corner will be placed correctly at the delivery orders number field.
RFR-016444 Correction
Framework: Base
Application: Import data
Filter: com. cisag.app.general.Partner
Action: Import
Category: Exception
Problem: Importing a partner with “DELETE” flag caused an NPE if the imported partner did not exist on the database
Correction result: From now an error message will occur in that case.
RFR-016444 Correction
Framework: Inventory management
Application: Posting keys
View: n.a.
Action: Load an existing posting key with process package receipt or package issue when the customizing function “Manage inventory in logistic units” is not active.
Category: Exception
Problem: The field for displaying the process in the application posting keys throws an exception because the values package receipt and package issue are no longer valid when the customizing function “Manage inventory in logistic units” is not active.
Correction result: The customizing function can no longer be deactivated if posting keys with the process package receipt or package issue exist.
RFR-016444 Correction
Hook: com.cisag.app.general.item.hook.log. ItemDependentMarkAsDeletedHook
Description: Refer to the hook contract definition (development object category “Hook contract”).
RFR-016444 Correction
Framework: Inventory management.
Application: Picking orders.
View: n.a.
Action: Complete picking order for a production order.
Category: Exception
Problem: If the reservation was allowed against new planned receipts, an exception could occur when the commission was completed.
Correction result: The logic for transferring the reservation to the production order has been corrected so that an exception no longer occurs.
RFR-016444 Documentation
Following help documents have been updated regarding bank data, Italian-specific fields, voucher document templates, and application layout changes: – Partner, Ansicht “Rechnungswesen”
– Vorgehensweisen: Partner, Ansicht “Rechnungswesen”
RFR-016444 Extension
Framework: Purchasing,Sales
Application: Purchase, Sales price lists
Description: In price list maintenance in purchasing and sales, the price definition maintenance should be generated with a factory method, not with new.
RFR-016444 Ergonomics
Update of the French user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
FR-016444 Correction
Framework: Base
Application: Item overview
View: Standard
Action: n.a.
Category: Ergonomics
Problem: The tables in the standard view did not resize automatically when the window changes the size. They had a fixed size.
Correction result: From now the tables in the standard view will resize automatically when the window changes the size.
RFR-016444 Extension
Framework: System Management
Application: Customizing
Action:n.a.
Field/Column: some required fields
Category: New action
Description: Support missing default values at required fields at the main following functions:
– Activation Base
– Activation Financials
– Activation Inventory management
– Activation Purchasing
– Activation Sales
– Activation Compliance-Management
RFR-016444 Correction
Framework: Inventory Management
Application: Delivery orders
Action: Export
Category: Ergonomics
Problem: The Constructor of ShippingOrderExportController is “private” but should be “protected” because CisFactory is used to create it.
Correction result: The problem is fixed.
5.1.1 Base
5.1.1.1 Base – General
RFR-016444 Correction
Framework: Base
Application: Customizing
Function: com.cisag.app.purchasing.ReturnOfGoods
Action: n.a.
Category: Invalid data / Unexpected behavior
Problem: In the customizing part com.cisag.app.customizing.purchasing.obj.ReturnOfGoods, the relationships to the BO’s DeliverySlipType and InventoryTransactionType used are missing. Despite its use in Customizing, a delivery order type or posting key could therefore currently be deleted if it is not used anywhere else.
Correction result: From now neither a delivery order type nor a posting key would be able to be deleted if it is used in the customizing part com.cisag.app.customizing.purchasing. obj.ReturnOfGoods.
5.1.1.2 Cockpits
RFR-016444 Extension
Frameworks: Inventory, Sales
Applications: “Cockpit: Receipts of goods/line items”, “Cockpit: Delivery orders/line items”, “Cockpit: Picking orders/line items”, “Cockpit: Customer invoices/line items”
Action: Display
Category: Unexpected behavior / Ergonomics
Problem: These line item cockpits does not show in all cases the sub line item number. Also the sorting of the data was not as expected. In case of receipt of goods line items the order data was not always shown.
Correction result: Now all of these problems have been corrected.
5.1.1.3 Company calendars
RFR-016444 Correction
Message: GEN-08531
Description: Correction of the message’s text.
5.1.1.4 Contracts/RFQs/Quotations/Orders
RFR-016444 Correction
Applications: Document reorganization applications that are based on the base class “com.cisag.app.general.order.log.AbstractEntityReorganization”
Action: Reorganize
Category: Exception, Unexpected behavior
Problem: If a document has more line items than the block size that is used by the reorganization (default: 32 main line items) an exception occurs during the try to continue a stopped reorganization (e.g. server shut down, table lock etc.).
Correction result: Now the document reorganization continues as expected in such a case.
In addition to that, the “archive data status” will be set now to “Reorganization started” for the case that the archive data reorganization was started – so the deletion marker can not be removed any more up from this state.
RFR-016444 Correction
Frameworks: Purchasing, Sales
Applications: Purchase orders, Sales orders, Distribution orders
Action: Determine open delivery quantity
Category: Exception
Problem: If the used layout contains the “open delivery quantity” field (in case of distribution for source and/or target) and a line item is persistent and contains as total quanity a packaging uom, an exception occurs if the total quantity uom is changed to an invalid entry.
Correction result: Now the exception does not occur any more – as “open delivery quantity” the zero quantity will be used in this case.
RFR-016444 Extension
Framework: Inventory, Sales
Applications: Sales orders, Sales confirmations, Pro-forma invoices, Picking orders, Shipping orders
Actions: “Generate sales confirmation”, “Generate pro-forma invoice”, “Generate picking order”, “Generate shipping order” and “Cancel delivery slip”
Category: Exception / Invalid data / Unexpected behavior
Problem: All documents have a header identification (“type code” and “header number”), this number is needed also after a performed reorganization. Normally such a number can not be used again (validation in the document application at create time). But in some cases a new document can be created with the same number; this works until also such a document is needed to be reorganized – here an exception occurs during the try to insert the needed identification data.
Correction result: Now the following document action will check if the number to be used for the new document is already used in combination with the relevant type instance: “Generate sales confirmation”, “Generate pro-forma invoice”, “Generate picking order”, “Generate shipping order” and “Cancel delivery slip”.
5.1.1.5 Due date types
RFR-016444 Correction
Framework: Base
Application: Partners
View: Suppliers
Action: n.a
Category: Unexpected behavior
Problem: The left part of the compound field “Due date type” was not displayed any more.
Correction result: From now the left part of the compound field “Due date type” will be displayed as expected.
5.1.1.6 Item characteristics
RFR-016444 Correction
Framework: Base
Application: Item characteristics
Category: Unexpected behavior / Ergonomics
Problem: If no classification is selected some unexpected effects occur.
Correction result:
1. The field “Classification” is now marked as required.
2. The “Validate” and “Update” actions of the main cool bar are enabled only if a valid classification is present.
3. The “Creae” of the main cool bar is not avaiable any more – you have to load a valid classification first (by load action, value help or classification tree).
5.1.1.7 Items
RFR-016444 Correction
Framework: Base
Application: Import data
Filter: com. cisag.app.genral.obj.Item
Action: Import
Category: Invalid data
Problem: In special cases it was possible to change the reference item of an already saved variant via import.
Correction result: From now it will never be possible to change the reference item of a variant that is already saved, neither from GUI nor via import. An error message will be displayed.
RFR-016444 Correction
Framework: Base
Application: Items
View: Item planning data
Action: Import (with correction maintenance)
Category: Exception
Problem: In special cases the correction maintenance hast been started allthough the error pool of the import controller was empty. In that case the imported item was already saved and an exception was thrown if the user klicked “next error”
Correction result: From now the import using the correction maintenance will work as expected. Even if the correction maintenance will start without showing an error message, the correction maintenance will be able to save the item without throwing an exception.
RFR-016444 Correction
Framework: Base
Application: Items
View: Base
Action: Validate
Category: Ergonomics
Correction: From now a warning message will be displayed if the user defines a basic unit of measure for an alias item, that will be different from the original item. Moreover a warning will be displayed if the user defines packaging unit of measures for an alis item.
RFR-016444 Correction
Framework: Base
Application: Item overview
View: n.a.
Action: Load
Category: Unexpected behavior / Ergonomics
Problem: Loading items from the navigator search let the application create invalid data in the history of loaded items.
Correction result: From now the application will work as expected. The history of loaded items will be created as expected.
RFR-016444 Correction
Framework: Base
Application: Items
View: n.a.
Action: Duplicate
Category: Exception
Problem: An exception occurred duplicating a displayed item. The reason was, that the item reorganization had deleted the item or parts of the item in the meantime between loading the item and starting the duplicate process.
Correction result: From now the exception will not occur any more. Furthermore, it will be ensured that the copied item will be always actual.
RFR-016444 Correction
Class: com.cisag.app.general.item.log. ImportExport
Method: com.cisag.app.general.item.log.ImportExport.checkVariantMaintainRole(ItemEntity, short)
Description: An exception is thrown if a variant item is imported and the imported item wanted to maintain an item role for an organization that is different from the maintaining organization of that role of the reference item. From now the text of that exception will be contain more information about the reason of this illegal constellation.
5.1.1.8 Partners
RFR-016444 Correction
Framework: Base
Application: Export Data
Filter: com. cisag.app.general.obj.Partner
Action: Export
Category: Exception
Problem: An exception occurred using the searches “Customer” or “Supplier” to select the data to export, when the export was started as a backround job and the selected organization is neither a sales organization nor a purchasing organization.
Correction result: From now the the searches “Customer” or “Supplier” will work in a backround job for all selected organizations as expected.
RFR-016444 Correction
The following help documents have been updated regarding new fields for a person’s date of birth:
– Partner, Ansicht “Basis”
– Partner importieren
– Einführung: Besonderheiten in Italien
RFR-016444 Correction
Class / Application: com.cisag.app.multiorg.log. RecalculationPartnerVisibilities
Method: n.a.
Description: The runtime of the application was improved.
5.1.1.9 Reorganize base
RFR-016444 Correction
Framework: Base
Application: Items
View: Customer sales item
Action: Mark/Unmark for delete
Category: Exception
Problem: An exception occurred unmarking a marked for deletion customer sales item if the reorganization application run between marking and unmarking for deletion and the loaded customer sales item was deleted in the mean time.
Correction result: As expected from now an error message will be displayed in that case.
5.1.2 Calculation
5.1.2.1 Calculation – General
RFR-016444 Correction
Framework: Calculation
Application: calculation schemas
View: value assistant
Action: n.a.
Category: Unexpected behavior
Problem: Value assistant does not display data in “Valuation price” column when the valuation price of schema is ‘Price list’ and ‘Calculation of kit components’
Correction result: Value assistant displays data in “Valuation price” column when the valuation price of schema is ‘Price list’ and ‘Calculation of kit components’.
5.1.3 Document Management
RFR-016444 Correction
Framework: Documents
Application: Documents
View: Reference tab
Action: Load/Refresh
Category: Unexpected behavior
Problem: If an object of type CisObject.T_BUSINESS_OBJECT is included in the reference, the label of the other entries is displayed incorrectly, respectively not updated.
Correction result: References tab displays data properly in case object of type CisObject.T_BUSINESS_OBJECT is included.
5.1.4 Inventory management
RFR-016444 Correction
Message: com.cisag.app.sales.01259
Description: The messages long text has been updated.
5.1.4.1 Delivery orders
RFR-016444 Correction
Framework: Inventory
Application: Picking orders
View: Delivery orders
Action: Update / Validate
Category: Exeption
Problem: An exception occurred changing the delivery recipient of a delivery order.
Correction result: From now changing the delivery recipient of a delivery order will work as expected.
5.1.4.2 Identifiers
RFR-016444 Correction
Framework: Inventory
Application: Identifiers
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the release 6.2, the “Other fields” can not be moved within the design mode.
Correction result: Now the “Other fields” can be moved again as expected.
Please note that the programed layout structure was changed for this correction (programmed tabbed pane added that contains the programed tab “Other fields”) – so the “Standard” layout was created newly; also own layouts needs to be corrected.
RFR-016444 Correction
Framework: Inventory Management
Application: Inventory Identifiers
View: n.a.
Action: Validate or Load
Category: Exception
Problem: If an item was specified that did not exist, an exception would be caused at validation.
Correction result: The validation can be executed as expected.
5.1.4.3 Inventory count
RFR-016444 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Export of an inventory count list
Category: Exception
Problem: If the language setting “multilingual” was selected, the export caused an exception.
Correction result: Although the language setting “multilingual” is selected the inventory count list can be exported as expected.
5.1.4.4 Inventory postings
RFR-016444 Correction
Framework: Inventory management
Application: Inventory postings
View: Inventory posting
Action: Save
Category: Exception
Problem: If a posting key is deleted during its usage within the application inventory postings an exception will be caused.
Correction result: If a posting key is deleted during its usage within the application inventory postings it will behave as expected.
5.1.4.5 Inventory value query
RFR-016444 Correction
Framework: Inventory Management
Application: Cockpit: Periodic inventory values
Action: “Period” field value help
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the result list the period value help shows also entries that do not have the usage “ERP”.
Correction result: Now the period value help shows only instances with the usage “ERP”.
5.1.4.6 Loading units
RFR-016444 Correction
Class: com.cisag.app.shipping.unitload.log. VersionUtility
Method: archive(UnitLoad, byte[], byte[])
Description: Method did not reset the attribute UnitLoad:zone. From now it will do.
5.1.4.7 Picking orders
RFR-016444 Extension
Framework: Inventory Management
Application: Picking orders
View: n.a.
Action: n.a.
Field/Column: n.a.
Category: New function
Description: The behaviour of the reservation is extended. If the stock is tentatively reserved because e.g. the concrete identifier is not specified the report of an identifier should be possible as long as available stock is existing.
RFR-016444 Correction
Framework: Inventory
Application: Picking orders
View: delivery orders
Action: validate (update)
Category: Exception
Problem: An exception occurred after changing the delivery recipient to an invalid value and then pressing validate or update.
Correction result: From now an error message will be displayed that the delivery recipient is not valid in that case.
RFR-016444 Correction
Framework: Inventory Management
Application: Picking orders
View: Picking order
Action: Complete picking order… (for production process)
Category: Exception
Problem: If the picking process starts with reservation support and the reservation settings within the item data were changed an exception could be caused at the picking order completion.
After an update of those reservation settings the update application “Update demand data” should be used. But when the picking order was updated before its execution, an exception could be caused.
Correction result: Although the update application is not executed the picking process can now be completed and its reservation support state will be considered as expected.
RFR-016444 Correction
Framework: Inventory
Application: Picking orders
View: Delivery orders
Action: n.a.
Category: Unexpected behavior
Problem: The fields ‘Delivery customer’, ‘Delivery term’, ‘Shipping term’ and ‘Freight carrier’ were not been editable in a not completed picking order as in former releases until CEE 5.3.
Correction result: From now the fields ‘Delivery customer’, ‘Delivery term’, ‘Shipping term’ and ‘Freight carrier’ will be editable in a picking order, that it’s not completed, exept freight cost calculation is not enabled for the delivery order but it is enabled for all related sales orders.
5.1.4.8 Receipts of goods
RFR-016444 Correction
Framework: Inventory
Application: Receipts of goods
View:
Action: Generate loading units…
Category: Unexpected behavior
Problem: In special cases loading unit references could not be removed from a loading unit via the action ‘Remove assignments’. The error message INV-8871 was displayed.
Correction result: From now the action ‘Remove assignments’ will work as expected.
RFR-016444 Correction
Framework: Inventory
Application: Receipts of goods
View: Purchasing
Action: Cancel partially
Category: Unexpected behavior / Ergonomics
Problem: In special cases error messages displayed in the ‘Cancel partially’-dialog could not be readed because a connected red corner was not dislayed.
Correction result: As expected from now for every error message, displayed in the ‘Cancel partially’-dialog, a connected red corner will be dislayed too.
5.1.4.9 Reservations
RFR-016444 Correction
Framework: Inventory Management
Application: Automatic Reservations
View: n.a.
Execution of automtic reservations for erroneous customer proposals demand data
Category: Exception
Problem: If demand data exists for customer proposals the automatic reservation caused an exception because customer proposals do not support reservations at the moment.
Correction result: If any demand data exist the automatic reservation will consider them without an exception.
5.1.5 Multi-site capability
5.1.5.1 Distribution orders
RFR-016444 Correction
Framework: Sales
Application: Distribution orders
Action: Excel export within some of the line item action dialogs (e.g. “Move date”)
Category: Invalid data / Unexpected behavior
Problem: The “Excel export” does not work as expected within some of the line item action dialogs.
Correction result: Now the excel export works as expected.
RFR-016444 Correction
Framework: Sales
Application: Distribution orders
Action: Validate line item
Category: Unexpected behavior
Problem: If a return distribution order is based on an original distribution order the storage areas (source and target) have to be the same as within the original order line item. In some cases an error message “not the same storage area” (“ORG, 434” / “ORG, 435”) occurs although the storage areas are not different.
Correction result: Now this validation works as expected.
5.1.5.2 Inter-company billing
RFR-016444 Extension
Framework: Base
Application: Inter-company billing
Action: Generate inter-company billing
Category: New functionality
Description: The “Generate inter-company billing” of the “Inter-company billing” application considers now customer invoice header and footer texts that are specified for the sales organization and invoice customer.
5.1.6 Planning
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: Log file
Action: Execute planning
Category: Unexpected behavior
Problem: Error messages contain incorrect data or are not translated correctly.
Correction result: New error messages contain correct data and are translated correctly.
RFR-016444 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data … / Update planning data …
Category: Performance
Problem: The transfer of item planning data took a high fraction of the planning data transfer phase depending on the number of items processed.
Correction result: Item data that was loaded for each item individually and repeatedly can now be loaded in item blocks and is cached to be used multiple times in the different parts of the item tranfer logic, especially the item view inheritance data.
Technical information: The new caches are active as default and can be deactivated in case of problems by a system property: com.cisag.app.aps.UseItemCache=false.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: transfer/update
Category: Ergonomics
Problem: In case a calendar has an undefined year, the message PRD-02303 was created, but it did not contain the code of the calendar type.
Correction result: In case a calendar has an undefined year, the message PRD-02303 will be createdincluding the code of the calendar type.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: Log file
Action: Execute planning
Category: Unexpected behavior
Problem: Items for which there is no disposition data in the planning data in the organisation, are displayed without item names in the error message PRD-02650.
Correction result: Items for which there is no disposition data in the planning data in the organisation, are displayed with item names in the error message PRD-02650.
RFR-016444 Extension
Framework: Planning
Application: Artikel-Dispositionsdaten-Zuordnungen
View: n.a.
Action: n.a.
Field/Column: Datum ab
Category: New field
Description: As described in RFE-004879 Phase 2 there is now versioning available.
Technical information: Like all item views the planning requires the version ranges to be aligned to the version ranges of the item planning view.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem:
Part 1: In the item planning view there is a field “Turnaround time” / “Durchlaufzeit” that defines a default processing time for a planned production order that only has a bill of material and no operations that could yield a real processing time. However, the planning always used the reorder time as planned production processing time and computed a wrong planned production order begin date. This problem happened only in case there was a reorder time configured with a unit of measurement.
Part 2: The planning can create production recommendations and computes the begin date of the production by backward scheduling the operations of a temporary in-memory production order from the demand date. In case the reservation data in this time range was not fully existing in database the computed begin date was too late. Dispatching a production order from the recommendation resulted in an earlier begin date.
Part 3: The reorder time (from all 3 possible sources) was only used with default minimum value of “1” internally in some places.
Part 4: The application “Generate purchasing recommendations” does recalculate the supplier and the order date, but always used the master data versions “now”.
Correction result:
Part 1: The planning now uses the value of the field “Turnaround time” / “Durchlaufzeit” in case a production recommendation is created to compute the planned begin time in case only a bill of material if configured at the production item.
Part 2: In case the planning computes a production recommendation begin date using in-memory scheduling of operations, the begin date will also be correct when the planning has to create possible reservation time ranges on-the-fly from the work time models.
Part 3: The reorder time (from all 3 possible sources) is now used with default minimum value of “1” internally in all places.
Part 4: The application “Generate purchasing recommendations” does recalculate the supplier and the order date, and uses the master data versions at the order date, moving to an earlier order date if necessary.
5.1.6.1 Material requirements planning
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all plan actions
Category: Unexpected behavior
Problem: In case an item has a delivery-calendar assigned and the planning was executed with delivery-calendar feature enabled,
the reorder level was used like a minimum inventory level.
Correction result: In case an item is planned in delivery-calendar mode and has a reorder level higher than zero defined,
all reorder level underruns are tracked at possible delivery dates.
In case a delivery-date is reached and a reorder level underrun is detected and there had been an earlier reorder level underrun detected and the two dates are separated at least by the amount of calendar days defined by the reorder time, a new recommendation is created for the currently examined delivery date.
The common reorder level mechanism rules apply, for example in case there have been other recommendations created between the two dates.
The reorder level optimization feature is disabled for delivery-calendar managed items because it could only create a 2nd recommendation at a non-delivery date.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: .Execute planning
Category: Unexpected behavior
Problem: At the end of planning an item there may be a surplus of quantity. This can be due to planned orders using lotsize quantity but also due to late receipts. If there are late receipts this receipts may be unnecessary. But no proper conflict is assigned to this receipts.
Correction result: In above described context to those receips a conflict “unneccessary order” is assigned which could be omitted and still a surplus exits. Receipts with assigned reserved quantity do not get conflict “unneccessary order”.
A surplus exists if quantity exceeds maximum of minimum inventory level / reorder level.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all, except save/load
Category: Exception
Problem: Starting any of the material requirements planning actions to transfer and plan and then requesting a server shutdown produced a unique key violation on database.
The planning results database cleanup was canceled by the shutdown request but the planning results writing was not.
Correction result: Multiple checks for planning server shutdown requests have been added at long running processing steps.
RFR-016444 Correction
Framework: Planning
Application: Material requirements planning, Generate distribution recommendations
View: n.a.
Action: Generate distribution recommendations, Execute planning
Category: Exception
Problem: An item X is internally purchased. After a proper planning run distribution recommendations are generated.
For item X recommendation(s) are generated which may have missing values for: target warehouse (destination warehouse), source warehouse(issues warehouse), delivery partner (organization source warehouse is assigned to).
This is due to the fact that in Customizing -> Multisite for the planned (selected organization of customizing application) site target warehouse and/or source warehouse are missing. This may be intended as this fields are not mandatory.
When editing distribution recommendations for item X (application “Distribution recommendations”) user is forced to set proper values for the missing data as target and source warehouse are mandatory for this application.
But if missing values are not completed before next planning run transfer of distribution recommendations may lead to exceptions. This happens if planning parameter “Distribution recommendations” specifies that also distribution recommendations of status “Created” must be transferred to planning.
Correction result: In the above described context no exception occurs. Instead, for each not completed distribution recommendation an error message is output in planning protocol.
Example: “PRD-09743 Ein Verteilvorschlag für den Artikel A000006 mit Liefertermin 25.04.2023 enthält unvollständige Daten und wird nicht in die Planung übernommen… “
Distribution recommendations which are not completed concerning mandatory values are not transferred to planning.
5.1.7 Production
RFR-016444 Extension
Framework: Production
Application: Cockpit: Plant data collection postings
View: n.a.
Action: Opening the Plant data collection postings application by double-clicking on the order number
Category: Unexpected behavior
Problem: The double click on order number shows no reaction.
Correction result: The double click on order number opens the plant data collection postings application.
RFR-016444 Extension
Framework: Production
Application: Production orders
View: n.a.
Action: Delete order, Dispatch, Dispatch and release, Delete Line Items, Set Deletion Marker for Line Items
Application: Cockpit: Production orders
View: n.a.
Action: Dispatch orders, Dispatch and release orders, Delete orders, Delete order Line Items
Category: Performance
Problem: Deleting a production order takes a long time, especially when multiple orders are deleted at once.
This also happens, when line items containing sub orders are deleted from a multi-level production order.
Correction result: Deleting a single order takes the same amount of time as before, but each additional order gets deleted in very little time.
Deleting 10 orders at once should be about two to three times faster than before.
Technical information: [ATTENTION INCOMPATIBLE CHANGE] The code in the protected method com.cisag.app.production.order.log. OrderHeaderValidation.configure has been moved to com.cisag.app.production.log. ProductionOrderReferenceLogicBuilder.
When deleting an order, the system checks for uses of it’s guid. This is done in OrderReferenceLogic.
This object is expensive to set up (or rather, the first use is expensive because of a lazily initialized cache).
The old code creates a new OrderReferenceLogic for each production order that has to be deleted.
The new code uses a single thread-local OrderReferenceLogic instance, that is set up and used via ObjectReferenceLogicProvider. getProductionOrderReferenceLogic.
This object is AutoClosable and should be used in a try block. It can be used initially at the top of the call stack, usages further down the call stack will automagically use the same instance.
In the old code, the OrderReferenceLogic was configured in com.cisag.app. production.order.log.OrderHeaderValidation.configure.
This code has been moved to com.cisag.app. production.log.ProductionOrderReferenceLogicBuilder.
RFR-016444 Extension
Framework: Production
Application: Production Orders
View: n.a.
Action: Dispatch, Recalculate due date and quantity
Category: Ergonomics
Problem: System property UseAdministrationTimesForSubOrdersOnScheduling was not loaded by SystemPropertyUtility.
Correction result: System property UseAdministrationTimesForSubOrdersOnScheduling is loaded by SystemPropertyUtility.
RFR-016444 Extension
Framework: Production
Application: Customizing
View: n.a.
Action: Save
Field/Column: Equipment
Category: New function in customizing
Description: Inventory requisition types can be set in customizing.
5.1.7.1 Operations
RFR-016444 Correction
Framework: Production
Application: Order maintenance
View: Order detail
Action: Duplicate
Category: Unexpected behavior
Problem: An operation has parameters at basis level. In a scheduling process this operation is used in a production order. For this production order one/many parameters of the operation are changed. If the operation is duplicated within the production order, parameters are not duplicated from operation (as expected) but retrieved from master data.
Correction result: Duplicating a operation in a production order also duplicates the parameters of basis level of operation within production order.
Please note: Duplicating an operation of a production order also duplicates assigned resources and their parameters as set within production order. This works as long as duplicated operation quantity is not changed while duplication is going on. If quantity of duplicated operation is changed within duplication process (that is: before applying and saving) then assigned resources will be retrieved from master data (and thus also parameters). This is done in the course of a scheduling of the duplicated (new) operation.
Quantity of a persistent operation detail of an production order can be changed without change of resource parameters. A rescheduling of production order is strongly recommended after such a change. This behaviour is untouched by this correction.
5.1.7.2 Production – General
RFR-016444 Correction
Framework: Calculation
Application: Output product cost calculation / Output trade cost calculation
View: n.a.
Action: Right click on the fields calculation type and calculation number
Category: Unexpected behavior
Problem: After right-clicking on the input fields, ‘text modules’ is offered for selection.
Correction result: After right-clicking on the input field calculation type ‘calculation type’ is offered for selection
After right-clicking on the input field calculation number ‘product/trade cost calculations’ is offered for selection.
5.1.7.3 Production orders
RFR-016444 Correction
Framework: Production
Application: Receipt of goods
View: n.a.
Action: Cancel a receipt of goods posting
Category: Unexpected behavior
Problem: Context: An operation only has a setup time defined (variable time is zero). This operation is used in a production order and automatic report is activated for the production order detail. A receipt of goods is performed with a scrap quantity. Automatic reporting works as expected.
Now receipt of goods is cancelled. In the course of cancellation error PRD 1199 occurs stating that two of quantities setup time, variable time and operation quantity have different signs (one negative, one positive). This is not allowed for reporting operations.
As a consequence cancellation of receipt of goods is done but not automatic cancellation of the operation.
Correction result: In above context cancellation of a receipt of goods with specified scrap quantity works as expected. No error occurs. Automatic postings of production order details work as expected.
RFR-016444 Correction
Framework: Inventory Management
Application: Picking orders
View: n.a.
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If the unit of measure is obligated another packaging unit is preferred although unpacked stock is existing in this obligated unit of measure. This caused unnecessary unpack processes.
Correction result: If unpacked stock of an obligated requested unit of measure is existing this stock must be preferred over a stock that has to be unpacked before.
RFR-016444 Correction
Framework: Production
Application: Order maintenance
View: Detail view
Action: n.a.
Category: Unexpected behavior
Problem: Field “Current begin” is not editable for co products.
Correction result: Field “Current begin” is now editable also for co products as long as no quantity has been reported. Field label is now “Due date” (DE: “Termin”)
5.1.7.4 Resource capacities
RFR-016444 Correction
Framework: Production
Application: Ressource capacities
View: list view
Action: Refresh
Category: Ergonomics
Problem: Capacities of selected range are editable. For convenience (better overview at boundaries) last editable day is followed by next day (out of selected range) and therefore is not editable. The same behaviour should work for first day too. But instead of previous day, the selected first day is set as not editable.
This forces user to extend selected range. Especially if only one day is selected capacities for this day are not editable.
Correction result: The selected range is exteded for better overview with previeous day of selected begin and following day of selected end. These days are not editable. If only one day is selected capacities of this day are editable.
5.1.8 Purchasing
5.1.8.1 Purchasing – General
RFR-016444 Correction
Framework: Purchasing
Applications: Supplier proposals, Purchase orders
Action: Usage of
Category: Exception
Problem: Up from “CIS620PB-Fix10 KW14/2022” an extension has been provided that added the “supplierItemNumber” and “supplierItemDescription” to the supplier proposal line item and purchase order detail line item data views.
Within the applications “Supplier proposals” and “Purchase orders” this extension works as expected. But if these attributes are tried to be used by another context (e.g. receipt of goods order assignment) an exception occurs.
Correction result: Now both attributes can be used also for other contexts so that the exception does not occur any more.
5.1.8.2 Purchase order confirmations
RFR-016444 Correction
Framework: Purchasing
Application: Supplier confirmations
Action: Add detail
Category: Invalid data / Unexpected behavior
Problem: If the first added line item is canceled – it will be added to sum although canceled line items are not relevant for the sum.
Correction result: Now the sum will be calculated as expected also in this case.
5.1.8.3 Supplier invoices
RFR-016444 Correction
Framework: Purchasing
Application: Supplier invoices
View: Additional cost invoices
Action: Import
Category: Invalid data / Unexpected behavior
Problem: By mistake since “CIS620PB-Fix07 week 48/2021” the import of additional cost invoices does not work any more as expected.
Correction result: Now the import works as expected again. In addition to that, the “Distribution” attribute is now supported as expected.
Furthermore, the “redistributeAdditionalCosts” is now supported also for additional cost invoices (functionality of the user interface action “Recommend supplementary cost distribution on delivered order line item values”).
RFR-016444 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate book
Category: Unexpected behavior
Problem: In contrast to the release 6.1 the warnings “PUR”, 131″ (different “payment terms”) and “PUR”, 132″ (different “payment method”) will be send also in case of an additional cost invoice (purchase order based). But these warnings should be send in case of an external purchasing invoice with the type “Supplier invoice” only.
Correction result: Now the behavior is again as within the release 6.1.
5.1.9 Relationship Management
5.1.9.1 Opportunities
RFR-016444 Documentation
The help documents “Vertriebsaussichten”, “Vertriebs-Aussichtsarten” and “Vertriebsphasen” have been updated.
5.1.10 Sales
5.1.10.1 Customer invoices
RFR-016444 Correction
Framework: Sales
Application: Customer invoices
Action: Create invoice by delivery slip
Category: Invalid data / Unexpected behavior
Problem: Since „CIS600PB-Fix23 KW12/2020“, an error exists if a sales order contains a charge item that is marked to be invoiced and a delivery slip is invoiced. In this case the created invoice contains the charge item two times.
Correction result: Now the error does not occur any more.
RFR-016444 Correction
Framework: Sales
Applications: Customer invoices
Action: Activate invalid invoices
Category: Invalid data / Unexpected behavior
Problem: If an invalid invoice is present that uses with respect to the invoice type the retail calculation the “Activate invalid invoices” does not consider the “Retail calculation” value – so such an invoice is not calculated as expected.
So after activation such an invoice needs to be canceled and created again.
Correction result: Now also the “Activate invalid invoices” functionality considers the “Retail calculation” value as expected.
5.1.10.2 Customer returns
RFR-016444 Ergonomics
Frameworks: Inventory, Sales
Applications: Receipt of goods, Customer returns
Action: Save
Category: Ergonomics
Description: If a receipt belongs to some customer returns and some line items have some items with multiple unit of measures and some quantities are entered by the receipt detail and the relevant customer return detail receipt assignments have the quantities origin “Automatic” the action “Reduce receipt of goods quantities in customer returns” can be used to refresh the order assignment quantities.
Alternatively, you can use the “refresh” action of the return line item receipt assignment quantites field within the “Customer returns” application.
Up from this extension the “Save receipt of goods” action will trigger a refreshment of all associated customer returns that are using the quantities origin “Automatic” – so the changed data is available now directly after this save action and the receipt of goods can be booked directly in more cases.
5.1.10.3 Delivery allocation
RFR-016444 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate inventory allocation…
Category: Exception
Problem: The inventory allocation process tried to change the reservation of a sales order line item that is assigned to a production order. This caused an exception.
Correction result: The reservation change try will be ignored by the reservation process and the reservation quantities will stay unchanged as expected.
RFR-016444 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate inventory allocation…
Category: Unexpected behavior
Problem: The inventory allocation did not delete the allocation of deliverable detail lines in case of the delivery restriction ‘Deliver order in full’ if any detail line of an order could not be allocated.
Correction result: As expected, from now the inventory allocation will delete the allocation of deliverable detail lines in case of the delivery restriction ‘Deliver order in full’ if any detail line of an order could not be allocated.
5.1.10.4 Freight costs
RFR-016444 Correction
Framework: Sales
Applications: Sales orders, Customer invoices, Internal billing data
Action: Create invoice
Category: Invalid data / Unexpected behavior
Problem: If the sales order calculates freight costs and the delivery order does not calculate freight costs the created invoice does not create an internal billing entry for the freight costs if the source and target financials organizations are different and such an entry is supported with respect to the invoice type. Also the cancel invoice does not create such an entry.
Correction result: Now an internal billing entry will be created also in this case for the invoice and the cancel invoice. Please note the following pre conditions: – The invoice needs to be based on a sales order
– The sales order owner origin (header attribute) needs to be “Delivery partner firm”.
– The firm of the inventory organization needs to be different from the firm of the sales organization.
– The invoice type needs either the value “Yes, with value” or “Yes, without value” for the attribute “Clear billing line item internally”.
Please note the a cancel invoice creates such an entry only if the original invoice has created such an entry.
Technical hint: Please note that up from this correction the CustomerInvoiceDetail:owner attribute is filled now if an invoice detail is based on a sales order freight cost entry.
5.1.10.5 Logon authorizations (customer, supplier, representative)
RFR-016444 Correction
Framework: Base
Application: Partners
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: External customers and suppliers locked in as a collaboration user could not load and update the partner data of their company any more.
Correction result: From now external customers and suppliers locked in as a collaboration user will be allowed to load and update the name and address data of their company in the partner data as in former releases.
5.1.10.6 Sales – General
RFR-016444 Extension
Framework: Sales
Applications: Sales document details
Action: Usage of
Category: Exception
Problem: Up from “CIS620PB-Fix11 KW20/2022” an extension has been provided that added the “basicPriceData” attribute to some sales document detail line item data views.
Within the applications “Customer proposals”, “Sales orders” etc. this extension works as expected. But if these attributes are tried to be used by another context (e.g. receipt of goods order assignment) an exception occurs.
Correction result: Now the attribute can be used also for other contexts so that the exception does not occur any more.
5.1.10.7 Sales orders
RFR-016444 Correction
Framework: Sales
Applications: Customer returns, Sales orders
Action: Generate or change credit note orders
Category: Error message, Unexpected behavior
Problem: If a created return credit note sales order line item contains a specified inventory identifier, a cancellation and a change to a zero quantity of such a line item is not possible because of the normal sales order line item error message “SAL, 821”. So the action “Generate or change credit note orders” fails in such a case.
Correction result: Now the error messages does not occur any more for such a line item.
5.1.10.8 Sales price listings
RFR-016444 Correction
Frameworks: Purchasing, Sales
Applications: Purchase price listings, Sales price listings
Action: Create lsit assignment, Validate
Category: Unexpected behavior / Ergonomics
Problem: If multiple price list assignments are added to a price listing and no further changes are present such a line will not be validated and saved.
Correction result: Now such a line will be validated and some error messages occur as expected (e.g. because of an empty price list).
5.1.10.9 Sales quotation types
RFR-016444 Correction
Framework: Sales
Application: Customer proposal types
Action: Validate
Category: Invalid data / Unexpected behavior
Problem: Customer proposals do not support inventory reservations. This is checked by a customer proposal type validation. But this validation will be performed only if the reservations are activated for the company within the Customizing.
Within the user interface only the value “no reservation” is possible but by a creation/change via the import functionality or directly by a logic a value different from “no reservations” can be saved.
So if the reservations are activated later it is possible to create inventory reservations also for customer proposals.
Correction result: Now the error message will occur always – even if the reservations are not activated for the company; in case of wrong import data you have to correct the source data because the field is not present if the reservations are not active for the company.
5.1.11 Storage Location Control
5.1.11.1 Inventory management server
RFR-016444 Correction
Framework: Inventory Management
Application: Inventory management server
View: n.a.
Action: Delete
Category: Unexpected behavior
Problem: After a successful deletion of an inventory menegement server an error message was send that the deleted server is not existing.
Correction result: After a successful deletion of an inventory menegement server no error message will be send.
5.1.11.2 Inventory orders
RFR-016444 Correction
Framework: Inventory management
Application: Inventory orders
View: n.a.
Action: Save an unit load assignment without report.
Category: Unexpected behavior
Problem: An unit load assignment may only be saved and reported at the same time.
Correction result: Only the saving (without report) of a unit load assignment is prevented by an error message.
RFR-016444 Correction
Framework: Inventory Management
Application: Inventory orders
View: n.a.
Action: Refresh
Category: Exception
Problem: If the inventory order was maked as deleted and it was deleted by the reorganize application an exception could be caused.
Correction result: If an inventory order is deleted externally it becomes invalid as expected.
RFR-016444 Correction
Framework: Inventory management
Application: Inventory orders
View: n.a.
Action: Save and report an inventory order for a withdraw with a return transfer inventory order.
Category: Unexpected behavior
Problem: The withdraw inventory order cannot be reported because this is prevented by a inventory posting validation.
Correction result: The report can be executed, as no more incorrect inventory postings are created.
5.1.11.3 Inventory requisitions
RFR-016444 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If two transfer line items have the same target warehouse but different source warehouses and they are managed by the same inventory management server an abort dialog should be displayed although all was generated correctly.
Correction result: If the inventory order can be generated for every open line item no abort dialog will be displayed as expected.
5.2 System development
RFR-016443 Documentation
The help document “Process definitions” (German version) has been corrected.
RFR-016443 Ergonomics
Update of the English user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016443 Ergonomics
Files of the online help file system have been updated.
RFR-016443 Extension
Framework: Software development
Application: ODBC driver
View: n.a.
Action: n.a.
Field/Column: n.a.
Category: new ODBC driver
Description: The ODBC driver for CEE is now available in a 64 bit version. This is compatible with Crystal Report 2020 (64 bit). Furthermore, the ODBC driver can be used with Microsoft Excel 64 Bit, if the connection is made with Micrososft Query.
RFR-016443 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-016443 Extension
Framework: com.cisag.pgm. SoftwareDevelopment
Application: Editorial Service
View: n.a.
Action: n.a.
Category: New application
Description: webservice for CEE translation process.
RFR-016442 Correction
Process: BIS data export with JSON format
Category: Unexpected behavior
Problem: Error BIS-00021 with parameter “JsonGenerationException: Can not write a string, expecting field name (context: Object)” can occur in this case: The filter definition contains an association with an array as target (e.g. Item.PurchaseItems.Uom), but the exported object instance does not contain values for each array index.
Correction result: BIS Export in JSON Format will work properly.
Technical information: Missing array values are indicated by virtual attribute “#Obj” in the JSON file
RFR-016442 Correction
Framework: Software Development
Application: Text editing cockpit
View: n.a.
Action: Import
Category: Exception
Problem: Newer versions of Microsoft Excel (R) do change the file format when saving the workbook. When the file format has been changed an exception is thrown during the import.
Correction result: Import should work again.
RFR-016442 Correction
Class: com.cisag.pgm.util.LRUMap
Method: V putAndGetRemovedValue(K key, V value) {
Description: The previous implementation of put did not fulfill the contract of java.util.Map:put. The old implementation returned the removed element. Now to get the removed element you must use the Method V putAndGetRemovedValue(K key, V value).
RFR-016442 Correction
Framework: Software development
Application: development objects
View: file delivery
Action:“n.a.”
Category: Ergonomics
Problem: The rows for newly created file entries stayed in “changed” mode even after update.
The target folder was not reset when creating a new file delivery.
The list action stayed disabled after creating a new delivery.
Correction result: The list and the state of the rows are now displayed correctly. The target folder is reset to the default “lib” folder on create.
The list actions become enabled on new. No need to update first anymore.
5.2.1 Application server
5.2.1.1 Batch
RFR-016442 Correction
Framework: System Management
Executing batch applications immediately
Category: Unexpected behavior
Problem: When selecting to exeucte a batch application immediately in a batch dialog, a message dialog with message SYS-162 could be displayed instead, and it is not possible to select to execute the batch application in the message dialog. This problem occurs only in batch dialogs that have no “In batch” button, and the system is configured with system property com.cisag.sys.services.batch.MaximumOnlineBatchThreads=0.
Correction result: The batch application is executed, and the message dialog does not appear.
RFR-016442 Correction
Framework: System Management
Executing batch jobs
Category: Unexpected behavior
Problem: The Workflow script function getBatchResult() may return null instead of the expected result parameters from a batch job which is created and executed in a workflow activity. The problem occurs with distributed batch jobs that do not execute the main job after the last sub jobs. The problem also occurs with some batch jobs creating reports output, typically with voucher output. The workflow activity must wait for the batch job execution for the problem to occur.
Correction result: The Workflow script function getBatchResult() returns the batch job result parameters.
Technical information: Activities that don’t wait for the batch job execution cannot receive the results.
Framework: System Management
Executing batch job as series
Category: Unexpected behavior
Problem: The activity for a batch job started as a series could show one or more of its serial activities as “delayed”, while the batch job itself is executed as planned. The problem occurs with distributed batch jobs that do not execute the main job after the last sub jobs. The problem also occurs with some batch jobs creating reports output, typically with voucher output.
Correction result: The display of the serial activities shows “Completed” status after the batch job was executed.
5.2.2 Searches
RFR-016443 Correction
Framework: All
Action: Performing dialog or locator searches.
Category: Exception
Problem: Certain complex search criteria might lead to an exception when performing the search.
This closes the running application.
Correction result: Exceptions in dialog or locator searches are caught and a message is send instead.
The exception itself is written in the message protocol and the log file.
5.2.3 Workflow
RFR-016442 Correction
Framework: Workflow management
Application: Process definitions
View: n.a.
Action: Generate start application
Category: Unexpected behavior
Problem: When start activity has an event generate start application is available.
Correction result: When start activity has an event generate start application is disabled.
RFR-016442 Extension
Framework: Workflow
Application: Process definition
View: n.a.
Action: n.a.
Category: Extension
Description: New possibility to generate a start application based on the process definition template.
Technical information: This possibility will only be active on the production level system.
5.2.3.1 Activities
RFR-016443 Correction
Framework: Workflow Management
Application: Activities/Activity coolbar
View: Individual Activity
Action: delegate task/accept/complete
Category: Correction
Problem: Problem occurs, when an activity is created with editor type workflow_role, delegate tasks is set to “during absences” and one of workflow_role users is absence and substitute by current user.
When user open delegated task from search for tasks: after accepting task coolbar options are deactivated.
When user accepts the delegated task, the activity is not in status completed, despite all tasks are forwarded or completed. If user tries to complete the activity, an exception occurs.
Correction result: When user opens a delegated task from search for tasks: after accepting task coolbar proper options are active.
When user accepts delegated task, Activity is in status completed. Old activities which did not change status can be manually updated to completed status.
Data update
Data update UPDBUG027822 is needed to update activity tasks counters, so old activities which did not change status could be manually updated to completed status.
RFR-016442 Correction
Framework: Workflow Management
Application: Cockpit: Tasks/OLTP database
View: Standard
Action: Forward…
Category: Exception
Problem: Using “Forward…” action causes NPE.
Correction result: Using “Forward.. .” action does not cause NPE. (proper window is shown).
5.2.3.2 Process definitions
RFR-016442 Correction
Framework: Workflow management
Application: Process definition
View: n.a.
Action: Start application
Category: Exception
Problem: After set parameter User Settings -> Start with last instance to yes, and after delete a process definition and close – open is not possible.
Correction result: Process definition application open with last open and existing object.
RFR-016442 Correction
Framework: Workflow management
Application: Process definitions
View: n.a.
Action: save
Category: Unexpected behavior / Ergonomics
Problem: After generating a template from a process definition, it can not be saved.
Correction result: It is possible to save after generating a template from a process definition.
5.2.3.3 Process editor
RFR-016442 Correction
Framework: Workflow Management
Application: Process definitions
View: n.a.
Action: Duplicate node, save
Category: Unexpected behavior
Problem: After duplicate node and save a process definition, an error message and save completed.
Correction result: Saving is now possible.
5.2.3.4 Workflow templates (transport)
RFR-016442 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: An exception occurred during generation from template or update.
Correction result: Fixed PK violation.
RFR-016442 Correction
Framework: Workflow management
Application: Activity definitions, Workflow role definitions, Process definitions, Development objects
View: n.a.
Action: new, duplicate, save as template, generate from template or update, Template field changed
Category: Unexpected behavior / Ergonomics
Problem: Not a unified way to create templates.
Correction result: Actions New and Duplicate has been disabled for templates.
Action “save as template” is active only when loaded an instance definition and is not a new object.
Action “generate from template or update” is active only when loaded a template definition and is not a new object.
Change a value for template field has not created a template/instance object, after change we can load a new object.
RFR-016442 Correction
Framework: Workflow management
Application: n. a
View: n.a
Action: n.a
Category: Unexpected behavior
Problem: Impossible to save template, when first enter name or description is incorrect.
Correction result: Description and name can be changed.
RFR-016442 Correction
Framework: Workflow management
Application: Activity definitions, Wrokflow role definitions, Process definitions
View: n.a.
Action: Template field changed
Category: Unexpected behavior / Ergonomics
Problem: When change template field to value “yes” delete action had deleted a innstance object. When change template field to value “no” new action had been disabled.
Correction result: When change template field to value “yes” delete action has been disabled. When change template field to value “no” new action has been enabled.
RFR-016442 Correction
Problem: When generating a process definition from a template the Process definition does not open in New mode.
Correction result: When generating a process definition from a template the Process definition opens in New mode.
RFR-016442 Correction
Framework: Workflow Management
Application: Process definitions
View: n.a.
Action: save, save as template
Category: Unexpected behavior
Problem: After generating instance from process definition, save return error.
Correction result: After generating instance from process definition, saving works as expexted.
RFR-016442 Correction
Framework: Workflow management
Application: process definitions, activity definitions, workflow roles
View: n.a.
Action: Generate from template or update, save
Only production and test production environment.
Category: Unexpected behavior
Problem: After saving a generated template – nothing happened.
Correction result: After saving a generated template – it is saved correctly.
RFR-016442 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: An error occurred while saving if there is no standard namespace.
Correction result: Standard namespace is created.