| Release | Comarch ERP Enterprise 6.4 |
| Release date | 18.10.2024 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.4.
This fix comprises the following support deliveries: RFR-016515 – RFR-016517
Information about the features of Comarch ERP Enterprise 6.4 (release news): · INF-002734 Release-News: Betriebswirtschaftliche Lösungen · INF-002735 Release-News: Technische Lösungen System requirements: · INF-002736 Systemvoraussetzungen Comarch ERP Enterprise 6.4
To install the support deliveries, please use the following documentation: · “Introduction: Software Logistics” (German language version) · „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.
The cumulative installation of support deliveries is described in INF-000228.
In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”. |
1 Information about support deliveries
The “Query support deliveries” application in the support system allows you to download directly from Comarch ERP Enterprise the support deliveries with their corresponding delivery documentation as well as further information.
The following types of support deliveries are relevant for you:
- RFR
This type of support delivery comprises a software upate or a file delivery as well as the corresponding delivery documentation.
- INF
This type of support delivery is used to provide FAQ-like information in a document.
- LNG
This type of support delivery is used to deliver language updates that can be installed in addition to German (de).
- 900
This type of support delivery comprises adaptors for the communication with third-party systems. - APP
This type of support delivery comprises installable Apps as well as the corresponding delivery documentation.
The available support deliveries are displayed in the “Query support deliveries” application according to the selected release, delivery, or delivery date. You can search for support deliveries and download their content. You can also find out whether new support deliveries are available. The application keeps a log on who has displayed which information or downloaded which software update, and when.
2 Installation of software updates
Follow the instructions given in the documentation “Introduction: Software Logistics” to install the software updates that are contained in the support deliveries. If there are deviating instructions to be followed, they are provided in chapter “Information about CEE640PB-Fix04”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE640PB-Fix04
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix03 will be upgraded to CEE640PB-Fix04.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
With the “Query data updates” application, you must schedule the following data updates, for any point in time.
UPDBUG029064
Deletion of virtual/dynamic attributes for partners doubles check
This update application removes virtual/dynamic attributes, that was chosen for partners doubles check in customizing. Virtual/dynamic attributes would cause an exception in partners doubles check logic.
UPDBUG028863
Deletes control data for sales quotations and sales orders that no longer exist
The value of the quantity to be picked of a production order item is corrected if (1) The line item is of the type material and has not yet been completed (2) The line item has been picked but not completely (3) The line item has the value 0 as the quantity still to be picked (4) No picking is in progress for the line item (5) The order type involved does not allow overpicking The picking status is set to “partially picked” in the corrected cases. The counters for partial picking and complete picking of the associated production order are updated. The data update can be called up several times.
5.1 Application development
RFR-016517 Correction
Framework: Inventory
Application: Inventory count lists
View: n.a.
Action: Complete inventory count list
Category: Invalid data / Unexpected behavior
Problem: In special cases changes of loading units were not been activated when completing an inventory count list.
Correction result: From now, as expected, changes of loading units always will be activated when completing an inventory count list.
RFR-016517 Correction
Framework: Inventory
Application: Import data
Filter: com.cisag.app.shipping.obj.UnitLoad
Action: Import data
Category: Invalid data / Unexpected behavior
Problem: In special cases the imported value of the attribute UnitLoad:actualGrossWeight has been overwritten unintentionally with a value calculated by the import controller.
Correction result: From now an imported value of the attribute UnitLoad:actualGrossWeight will be stored by the import controller as expected.
RFR-016517 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-016517 Correction
New entry in com.cisag.app.general.OrderType:
Name of entry: SEM_MCS_CUSTOMER_PROPOSAL
ID: 2039
Description (de): Vertriebskanal-Verkaufsangebot
Description (en): Sales channel sales quotation
Description (pl): Oferta sprzedazy kanalu sprzedazy
RFR-016517 Correction
Framework: Inventory
Application: Generation of delivery order
View: n.a.
Action: n.a.
Category: Unexpected behavior / Invalid data
Problem: The generation of delivery order mapped a route definition from the source order header to the created shipping order, that may be not valid. Actually, that was implemented as a fall back when no route is defined on a source order detail.
Correction result: From now the fall back will be deactivated and a route definition will only be mapped to the created shipping order if the route was defined in the source order detail.
5.1.1 Base
5.1.1.1 Classifications
RFR-016517 Correction
Framework: Base
Application: Classifications
View: n. a.
Action: Save nodes
Category: Unexpected behavior/Serious error.
Problem: A serious error in the application Classifications. This is due to the incompatible determination of the length of the attribute code.
Correction result: The error has been corrected.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016517 Extension
Framework: Purchasing, Sales
Application: Purchase orders, Sales orders
Action: Complete billing line items
Description: The logic of the “Complete billing line items” has been changed so that it uses now the entity logic. Especially some validation hooks can be implemented now to prevent the completion in some cases (in analogy to the cancel functionality).
Hint: Please note that the “Complete delivery” logic does not use – as before – the entity logic because it might be used by the receipt or delivery logic status update and here no veto is supported by some validation hook implementations.
Technical information: The completeInvoice methods of the OrderStatusLogic have been removed because a compatible change was not possible.
If needed you have to use the OrderBatchLogic functionality – here the public API is as before and internally the entity is used now.
RFR-016517 Correction
- New entries in com.cisag.app.general.OrderType:
a.
Name of entry: SEM_FIN_PRE_POSTING_FIN
ID: 2037
Description (de): Vorerfasster Beleg Finanzbuchhaltung
Description (en): Pre recorded voucher, Financial Accounting
b.
Name of entry: SEM_FIN_POSTED_POSTING_FIN
ID: 2038
Description (de): Buchungsbeleg Finanzbuchhaltung
Description (en): Posting voucher, Financial Accounting
2. Change of com.cisag. app.general.OrderType value description:
Name of entry: SEM_FIN_POSTING_FIN
ID: 2006
Description (de): “Buchungsbeleg Finanzbuchhaltung” ==> “Erfasster Beleg Finanzbuchhaltung”
Description (en): “Posting voucher, Financial Accounting” ==> “Recorded voucher, Financial Accounting”
RFR-016517 Correction
Application: All applications that are using the “OrderDisplayField” functionality
Category: Unexpected behavior / Ergonomics
Problem: The standard field that is used für displaying the order or order line item identification was configured with the maximum length of 30 characters. But this is too short – needed are 36 characters. As result in some cases a field error message occurs.
Correction result: Now the length is defined with 36 characters so that the field does not show any more such an error message.
RFR-016517 Correction
Frameworks: Purchasing, Sales
Applications: Proposals, Orders
Action: Duplicate sub line item; Create new sub line item
Category: Exception / Invalid data / Unexpected behavior
Problems:
1.
If the main proposal line item is a variable kit line item and this line item was completed manually new kit component sub line items have a status that is not completed.
2.
If the main order line item is a variable kit line item and this line item was completed (completed delivery in case of “not zero total quantity” or completed invoice in case of “zero total quantity”) new kit component sub line items have a status that is not completed. In some cases, also an exception occurs.
Correction result:
1. Now in this case new kit components are also completed manually.
2. Now in this case adding new kit components is not supported any more (as in case of canceled kit main line items).
5.1.1.3 Items
RFR-016517 Correction
Framework: General
Application: Items
View: n.a.
Action: Create, Create from Template
Category: Unexpected behavior / Perfomance
Problem:
1. The application tried to load “warning” instances even if they could not exist.
2. The hook method com. cisag.app.general.item.hook.log.ItemDependentHook.load(V) was called if no data could not be loaded, because the item was not persistent.
3. The validation for the attribute “Bestandsgeführte Verpackungseinheiten planen” in item planning data used a query, that could not use any index.
Correction result:
1. From now the application will try to load “warning” instances only if they could really exist.
2. From now the hook method com.cisag.app.general.item.hook.log.ItemDependentHook.load(V) will be called only if dependent data really could be found. The item must be persistent for that. Otherwise, no dependent data could exist.
3. The query used by the validation for the attribute “Bestandsgeführte Verpackungseinheiten planen” in item planning data is modified. From now an existing index will be usable.
RFR-016517 Correction
Class: com.cisag.app.general.item.log. ItemAccountingEntity
Method: retrieveItemAccountingData(byte[])
Description: From now this method will call the method com.cisag.app.general.item.log.ItemAccountingEntity. rebuildItemAccountingData(ItemAccountingData, List) with a list of mutable of ItemAccountingData instances.
5.1.1.4 Partners
RFR-016517 Correction
Framework: General
Application: Customizing
Function: com.cisag.app.general.Partners
Rubric: Duplicates validation
Category: Unexpected behavior
Problem: Virtual/dynamic attributes, that was chosen for partners doubles validation in customizing would cause an exception in partners doubles check logic because partners doubles validation bases on database tables only.
Correction result: From now virtual/dynamic attributes will be filtered in the partners doubles validation rubric of the customizing application, so the user won’t be able to select them.
Data update: com.cisag.app.update.log.UPDBUG029064
RFR-016517 Correction
Framework: Base
Application: Partners
View: Base
Action: n.a.
Category: Unexpected behavior
Problem:
1. The tab ‘General’ was not enabled if a pseudo partner was created or loaded.
2. The validation required a name for a pseudo partner.
Correction result:
1. From now the tab ‘General’ will be enabled even if a pseudo partner was created or loaded.
2. From now the validation will not require a name for a pseudo partner.
5.1.2 Financials
5.1.2.1 Account assignments
RFR-016517 Extension
Framework: Financials
Application: Account assignments
Category: New field
Description: The account assignments have been extended with the new field “Offset price component account”. This field is visible only if the financials organization uses levies instead of tax codes. Also this field is used only if the account use has the value “Revenue account”.
In addition to that the warnings „FIN-00659“ and „FIN-00660“ will be send up from now only if the account use has the value “Inventory account”.
5.1.3 Inventory management
RFR-016517 Extension
It is now possible to display the values for weights and dimensions in the items, identifiers and vouchers applications with weights and volumes in other units using the tooltip. The display depends on the current organization in the organization selector.
For this purpose, a leading unit of a different unit system can be assigned for each unit category in Customizing at organization level, in contrast to the system unit. For example, the system unit “kg” (SI) is used for the unit category mass (weight), and the leading unit “lb” (pound – customary unit) can be assigned for an organization (USA).
In addition, the option can be activated via the delivery order type so that the reweighed or remeasured values (weight and volume) are proposed in the deviating leading unit in delivery orders and commissions. However, values that have already been entered or imported are not overwritten.
RFR-016517 Correction
Framework: Update
Application: UPDADV103530A
View: n. a.
Execution of the data update
Category: Ergonomics
Problem: If existing warehouse stock was changed although this data update was not executed successfully an exception was caused. It is not allowed to go on working without the successful execution of all data updates.
Correction result: The data got a new error message that is displayed when existing warehouse stock was changed before this data update is executed successfully.
5.1.3.1 Delivery orders
RFR-016517 Correction
Framework: Inventory
Application: Shipping orders
View: n.a.
Action: Print container labels
Category: Ergonomics
Problem: The action is enabled in the application although the delivery slip was not yet created. The user was able to click it although no document is printed.
Correction result: From now the action will be enabled only then, when the delivery slip is created.
RFR-016517 Correction
Framework: Inventory
Application: Delivery orders, goods receipts
View: Distribution
Action: Complete delivery order and create delivery slip
Category: Exception
Problem: An exception occurred when creating a goods receipt in the delivery process for distribution. This happened when a delivery order line item is packed into a loading unit with a multilayer packing structure.
Correction result: From now creating a goods receipt in the delivery process for distribution will work as expected.
5.1.3.2 Identifiers
RFR-016517 Correction
Framework: Inventory management
Application: Identifiers
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The bottom fold-out area of the ‘Weights and dimensions for 1st item unit’ section was visible in every tab.
Correction result: The bottom fold-out area of the ‘Weights and dimensions for 1st item unit’ section is now only visible in the ‘General’ tab.
5.1.3.3 Inventory count
RFR-016517 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Close inventory count list…
Category: Exception
Problem: When an inventory difference was reported but the storage location and its inventory owns someone else the created inventory postings could not be processed.
Correction result: If such a case is detected a warning will be sent. At closing the line item an erroneous inventory posting will be created. So, it is possible to check the problems after closing the line item.
RFR-016517 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Duplicate
Category: Unexpected behavior
Problem: A changed organization was not considered during the duplication process.
Correction result: If the selected organization is different to the organization of the duplicated inventory count the selected organization will be used for the new inventory count as expected.
RFR-016517 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Close…
Category: Unexpected behavior
Problem: When a loading unit had to be unpacked and packed the corresponding inventory postings only got a reference to the count list but not to the concrete line item. But that could be important to find those postings e.g. for erroneous closing processes.
Correction result: The inventory posting to pack or unpack a loading unit will get a reference to the concrete count list line item as expected.
5.1.3.4 Inventory query
RFR-016517 Correction
Framework: Inventory Management
Application: Cockpit: Inventories
View: n.a.
Display loading unit content
Category: Ergonomics
Problem: The detail search of the Cockpit: Inventories was not sorted by item and identifier.
Correction result: The detail search of the Cockpit: Inventories will be sorted by item and identifier as expected.
5.1.3.5 Loading units
RFR-016517 Correction
Framework: Inventory management
Application: Loading units
View: n.a.
Action: Change load unit contents or delete load unit
Category: Unexpected behavior or Exception
Problem: Although there were still not processed inventory postings for the packing of load units, the content of the load unit could be changed or the load unit could be deleted.
Correction result: If there are inventory postings for packing that have not yet been processed for a load unit, the contents of the load unit cannot be changed and it is also not possible to delete the load unit.
RFR-016517 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Pack, unpack, lock, unlock and reuse
Category: Exception/Ergonomics
Problem: In special cases the validations were not executed for these actions. As a result of this an exception could occur executing these actions.
Correction result: From now these actions will be validated correctly as expected or the clicked action will be set to disabled.
RFR-016517 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Actions: Pack…, Unpack…, Lock…, Unlock, Reuse…
Category: Unexpected behavior / Ergonomics
Problem: The error messages of the validations of the actions “Pack…”, “Unpack…”, “Lock…”, “Unlock, Reuse…” were sent to message log only, even if the actions were executed immediately. The messages were not displayed in the application.
Correction result: From now the error messages of the validations of the actions “Pack…”, “Unpack…”, “Lock…”, “Unlock, Reuse…” will be displayed in the application if they are executed immediately.
5.1.3.6 Picking orders
RFR-016517 Correction
Framework: Inventory
Application: Reorganize picking orders
View: n.a.
Action: Reorganize
Category: Exception
Problem: An exception occurred in special cases using PickingOrderDataObject instances
Correction result: From now using PickingOrderDataObject instances will work as expected.
RFR-016517 Correction
Class: com.cisag.app.inventory.picking.order.log.OrderBatchLogic
Method: com.cisag.app.inventory.picking.order.log.OrderBatchLogic.close(PickingOrder, boolean)
Description: From now an #entity.releaseLock is called at the end of the method. That was forgotten in a former version of this method.
RFR-016517 Correction
Framework: Production
Application: Order maintenance, Cockpit: production orders
View: n.a.
Action: Generate picking orders and output picking slips…
Category: Invalid data
Problem: Preliminaries: Production order uses production order type with “Overdelivery of picking allowed” = false; material line items must be picked.
For a production order a picking order is generated. Picking order is completed with less quantities than is suggested to report.
Result: Open picking quantity is set to zero (which is wrong) and picking status is set to “completed” (also wrong).
Correction result: After completion of picking order in above described manner
– “Open picking quantity” of associated production order detail is set to quantity still to be picked (order maintenance, table view -> planning data)
– “Picking status” of associated production order detail is set to “partially picked”
Data update: A data update UPDBUG028863 must be performed. Data update corrects “open picking quantity” (order maintenance, table view -> planning data) and “picking status” of material line items
5.1.3.7 Receipts of goods
RFR-016517 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Post receipt of goods…
Category: Unexpected behavior
Problem: The system acknowledges the posting with the error message INV-09221.
Correction result: From now the error message INV-09221 will not be displayed any more.
RFR-016517 Correction
Framework: Inventory
Application: Goods receipts
View: Distribution
Action: Post receipt of goods…
Category: Exception
Problem: An exception occurred posting the goods receipt. That happens in special cases when the goods receipt has more than 16 detail lines.
Correction result: From now posting the goods receipt will work as expected.
5.1.3.8 Reservations
RFR-016517 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Change of the QC status from NOT “Released”.
Category: Exception
Problem: If the customizing function “reservations” is not active but it was active and the concerned warehouse delegated the reservation time value to the customizing an exception would be caused.
Correction result: The change of the storage location QC status can be processed as expected.
RFR-016517 Correction
Framework: Inventory Management
Application: Automatic reservations (Batch)
View: n.a.
Automatic start of the automatic reservations for new warehouse stock
Category: Unexpected behavior
Problem: If the reservation scope was only set to “Inventory” (customizing setting) new warehouse stock would not be reserved automatically although it should be (customizing setting: “New Inventory”)
Correction result: If the customizing setting: “New Inventory” is activated new warehouse stock will be reserved automatically as expected.
RFR-016517 Correction
Class: com.cisag.app.inventory.reservation.log.FixedReservationLogic
Method: reserve(ReservationRequestCollection), report(ReservationRequestCollection), transfer(ReservationRequestCollection)
Description: New possibility to collect reservation requests and executes them as a bulk operation. Internal sorting will reduce the possibilities of dead lock situations within reservation processes.
RFR-016517 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Create picking orders…
Category: Exception
Problem: If a concrete identifier was specified within a line item the picking order creation would cause an exception.
Correction result: Picking order can be created as expected.
RFR-016517 Correction
Framework: Inventory Management
Application: Inventory requisition
View: Manual stock movement
Change the warehouse of a reserved line item
Category: Exception
Problem: When an inventory order is deleted and the warehouse was changed after that the creation of a new inventory order will cause an exception. But only if the item has no identifier, it does not support inventory packagings and the line is a withdrawal.
Correction result: The inventory order for the changed warehouse can be generated as expected.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016517 Correction
Framework: Sales
Application: Distribution orders
View: Return of goods
Return the goods from and to structured warehouses
Category: Invalid data
Problem: The inventory postings created by the receipt of goods and the delivery slip set incorrect origins and these inventory postings got wrong storage zones.
Correction result: Those inventory postings will get correct origins and correct storage zones as expected.
RFR-016517 Correction
Frameworks: Purchasing, Sales
Applications: “Distribution recommendations” and “Distribution orders”
Actions: “Distribution order line item – apply defaults”, “Distribution recommendations: default logic and UI”, “generation: Distribution recommendations ==> Distribution orders”
Category: Unexpected behavior / Ergonomics
Problem:
1. Distribution order: The “Target availability date” was determined by the wrong calendar (was calendar of “sales organization”; should by calendar of “delivery customer”).
2. Distribution recommendations: The order of the date fields within the user interface and the date value refreshments were not as expected.
3. Distribution recommendations ==> Distribution orders: The date values were not always set as defined into the distribution order line item.
Correction result:
1. Distribution order: The “Target availability date” is determined now by the calendar of the “delivery customer”. Hint: Refreshment triggered as before by a change of “delivery date” or “Transition time goods receipt”.
2. Distribution recommendations: The “Planned shipping date” is now in the first row (row of “Issuing organization”) and “Delivery date” is now in the second row. Also, the field refreshment has been changed so that manual changes of maintained date fields will not be overridden by the refreshment logic.
3. Distribution recommendations ==> Distribution orders: The date values are set now into the distribution order line item as defined by the relevant distribution recommendation.
5.1.5 Planning
RFR-016517 Correction
Framework: Purchasing
Application: Calculate distribution recommendations
View: n.a.
Action: Calculate distribution recommendations
Category: Unexpected behavior
Problem: Field “Purchasing scheduler” was ignored during calculation of distribution recommendation.
Correction result: Now this field is used properly and it is not ignored anymore if the user filled it.
RFR-016517 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning
Category: Unexpected behavior
Problem:
1. During transfer data to planning, some data could not be loaded properly. If it occurred for entire one type of data (e.g. for transfer items) an error was displayed in logs of type ERROR, that transfer of that type was not successful. However, the transfer of the remaining data continues, as does the planning is executed. Because of that results from planning could be wrongly calculated (some data are missing).
2. Some errors mentioned in previous point was not even displayed in logs.
Correction result:
1. Now this kind of errors are set to fatal in log file, so when user sees at least one fatal error in logs, he should does not believe in planning results.
2. All errors about transferring failed for entire one type of data are now visible in logs.
5.1.5.1 Material requirements planning
RFR-016517 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning execution actions
Category: Exception
Problem: During material planning, when the scheduling is trying to reserve a resource for a large time range (e.g. , when the resource is reserved very long because of a large number of POs), or small time range and lots of shifts, a NegativeArraySizeException is thrown. The planning then skips this secondary demand analysis. A similar problem could occur for 24/7 resources being reserved for multiple years.
Correction result: The resource scheduling and reservation logic now correctly handles longer time ranges.
Technical information: Incompatible change: The constructors of com.cisag.app.production.scheduling.log.ResourceAvailability were changed. They only require a guid and serialized data respectively state array now. Other values are read directly from the deserialized states / states array. RA.persistent is always false unless the data comes from serialized states. RA.persistent is handled by the class itself, see RA.setPersistent() to override.
Incompatible change: The protected field ResourceAvailability.states is now private and must be accessed via getStates() or setStates()
Incompatible change: The protected field ResourceAvailability.stateCount was removed and replaced by the method getStateCount(). Every function concerned with state-array-length now uses ints instead of shorts.
Incompatible change: The protected fields ResourceAvailability.from and until were removed and replaced by the methods getFrom() and getUntil() or getFromDate() and getUntilDate(). The values are directly computed from the underlying states array.
Furthermore, a new version to serialize states into the DB was introduced. It uses ints instead of shorts for state-array-length (and state.reservations.length).
All old versions can still be read from database.
The default of the SystemProperty “com.cisag.app.production. scheduling.log.ResourceLogicImpl_SchedulingTimeHorizon” was changed to 20.
5.1.6 Production
RFR-016517 Correction
Framework: Production
Application: Product configuration rules, Items, Sales orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When the user selects a step in the step column in the “Steps” list in the product configuration rule dialog, and this causes a focus command to another step, the steps list was not correctly updated with the newly focused step.
This caused certain interactions, like switching tabs, to show the initially selected step, not the newly focused step.
Another interaction was: with a message-queue open, the next click on a step in the “steps” list would select the step that was focused after the last click, not the step that was clicked right now.
Correction result: Selecting steps and focus instructions correctly work together.
RFR-016517 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: “Post production issues”
Category: Unexpected behavior
Problem: The application “production issues” crashes with an IllegalArgumentException, if a second user session has deleted the underlying production order, just shortly before the post of the production issue is being executed.
Correction result: The application does not crash any more. Before the post update, it is checked if the production order is still available. If not, the message GEN-5574 (Voucher type/header XY or at least one of the voucher line items no longer exists.) will be shown.
RFR-016517 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Recalculate due date and quantity
Category: Unexpected behavior
Problem: When production order has cross-site operation as one of its line item, the subOrder is created after dispatching. Additionally, for both of those orders a distribution order is created. After finishing those distribution orders and deleting both of them, performing action “Recalculate due date and quantity” on main production order causes a second, new distribution order for return transport (for sub order) to be created.
Correction result: The second distribution order is no longer created, when an existing one is already deleted.
RFR-016517 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations (via workflow)
View: n.a.
Action: Start process
Category: Exception
Problem: The batch application “Purchasing/distribution recommendation generation” calculates purchasing recommendation when called by application “Calculate purchasing recommendations”. It calculates distribution recommendations if called by application “Calculate distribution recommendations”.
This batch application should also calculate recommendations (purchasing or distribution) when called within a workflow.
Most of the selection fields shown by “Calculate purchasing recommendations” or “Calculate distribution recommendations” are not properly transferred to batch application by workflow. Hence workflow process failed.
Correction result: Selection fields are properly transferred to batch application “Purchasing/distribution recommendation generation” by a proper activity definition. A workflow process can calculate recommendation depending on the selections.
Technical Information: The “Load” parameters of application “com.cisag.app.purchasing.log.ReorderCalculationNew” (development object) have been adapted to better fit workflow requirements.
RFR-016517 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: New operation reservation
Category: Unexpected behavior
Problem:
1. When manually adding an operation to a production order, the units of the target processing times of all resources are changed to the unit of the target processing time of the primary resource, but the amounts are kept unchanged. This converts 5 minutes into 5 hours.
2. When manually adding an operation to a production order, a target processing time of zero of a resource was replaced by the target processing time of the primary resource.
3. Changing the target processing time of an operation position changes the target processing time of resources proportionally. This is done by converting the target processing time of resources into the unit of the target processing time of the operation first.
Correction result:
1. Units specified in “Operations” application are kept in described case (so there is no conversion happening, neither amount nor unit is changed). This behavior is consistent with the creation of operation positions through “Dispatch” action.
2. Keep target processing time of zero. This behavior is consistent with the creation of operation positions through “Dispatch” action.
3. Target processing time units of resources are not converted to target processing time units of operation when changing operation processing time. Their amounts are still recalculated proportionally.
RFR-016517 Extension
Framework: Production
Application: Cockpit: Production order booking imports
View: Cockpit: Production order booking imports
Action: n.a.
Category: New application
Description: New cockpit displays information about imported production order bookings with information of status of each one. Additionally user can start import application from this cockpit to start process of updating Production orders times based on imported data.
RFR-016517 Correction
Framework: Production
Application: Resources
View: n. a.
Action: Validate, Save
Category: Unexpected behavior
Problem: After switching field “Valuation of gaps as interruption” to value “Reservable with time interruption”, the field “Interruption-free reservation duration” is set to read-only, but after performing actions “Validate” or “Save” the field became editable again.
Correction result: Now after validating or saving the field stay read-only, so below sentence is always true now: When field “Valuation of gaps as interruption” is set to “Reservable with time interruption”, the field “Interruption-free reservation duration” is read-only.
RFR-016517 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Dispatch, Dispatch and release, Recalculate due date and quantity, Midpoint rescheduling
Category: Unexpected behavior
Problem: When a resource has a constraint to another resource, this constraint was ignored during scheduling and rescheduling.
Option “Predecessor exists” was ignored for resources also.
Correction result: Constraints of resources to other resources are not ignored during scheduling and rescheduling.
Option “Predecessor exists” is not ignored for resources.
RFR-016517 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: “Post production issues”
Category: Unexpected behavior
Problem: The application “production issues” crashes with an IllegalArgumentException, if a second user session has deleted the underlying production order, just shortly before the post of the production issue is being executed.
Correction result: The application does not crash any more. Before the post update, it is checked if the production order is still available. If not, the message GEN-5574 (Voucher type/header XY or at least one of the voucher line items no longer exists.) will be shown.
RFR-016517 Correction
Framework: Production
Application: Product configuration rules
View: Steps, Configuration characteristics, Condition lists, Conditions and actions
Action: Duplicate
Category: Exception
Problem: Perform action duplicate “Product configuration rule” on any existing rule. Without saving, change to a different view. After pressing save in new open view an exception occurred.
Correction result: Exception is not occurring anymore in described situation.
RFR-016517 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Replacing a resource as a line item
Category: Exception
Problem: Trying to change the resource via line item editor with a non-existing resource code leads to a null pointer exception.
Correction result: Instead of exception, error PRD-00066, “Specified resource does not exist” appears.
RFR-016517 Extension
Framework: Production
Application: Reorganize production order scheduling import data
View: n.a.
Action: n.a.
Category: New application
Description: Reorganize application which deletes all ProductionOrderBookingImport data with all dependent references which has status successfully processed.
RFR-016517 Correction
Framework: Production
Application: Import data, Production orders
View: n.a.
Action: Import data
Category: Exception
Problem: When importing new production order with operations with guids for details, new production order is created, but operations and resources are empty. Then performing any action on that imported production order caused exception.
Correction result: Now if production order with detail’s guids is imported successfully operations and resources are not empty and performing actions on such a production order does not cause an exception anymore.
5.1.6.1 Bills of material
RFR-016517 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release
Category: Unexpected behavior
Problem: Bill of material with two details for the same item. On of them has field “Resolve item” set to “Resolve”, another one to “Do not resolve”.
After multiple level dispatching this bill of material in “Production orders” both were resolved.
Correction result: Now details set to “Do not resolve” in described situation are not resolved.
5.1.6.2 Product configuration
RFR-016517 Correction
Framework: Production
Application: Product configuration rules, Items, Production Orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When a formula would show an image from a non-default workspace (e.g. FILE1 instead of), an error is shown, even if the image exists.
Correction result: The image is correctly displayed even when it comes from a non-default workspace.
RFR-016517 Correction
Framework: Production
Application: Product configuration rules, Items, Sales orders
View: n.a.
Action: n.a.
Showing the product configuration rule dialog in various places.
Category: Unexpected behavior
Problem: When a product configuration rule contains a configuration characteristic of type “long text”, this configuration characteristic cannot be set to the result of a formula when executing the configuration rule.
Correction result: The configuration characteristic can be set correctly to the result of the formula. This will set the plain text only and only set the text in the default language.
5.1.6.3 Production – General
RFR-016517 Correction
Framework: Production
Application: Order maintenance
View: Table view -> Column “External operation status”
Action: Reschedule …
Category: Unexpected behavior
Problem: An external operation in a production order is already completed. Now rescheduling is performed for this production order with increase of quantity. Result: Status of external operation is not adjusted. Status should be “Partial …”. See table column “External operation status” of production order.
Also if external operation status is “Partial…” and a rescheduling decreases quantity so that this status should change into “Completed…” this is not the case.
Correction result: “External operation status” is adjusted, when rescheduling with increasing/decreasing, to “Partial…”/”Completed…” properly.
RFR-016517 Correction
Framework: Production, Calculation
Application: Cockpit: Production Items
View: Cockpit: Production Items
Action: n.a.
Category: Unexpected behavior
Problem: When Production Methods are disabled in Customizing then in applications Cockpit: Production Items (Production and Calculation framework) context menu for column Item cannot be opened. Jumping by CTRL+click to Item application was also impossible for that column.
Correction result: Context menu can be opened and jumping by CTRL+click is also possible now.
5.1.6.4 Production cockpit
RFR-016517 Correction
Framework: Production
Application: Cockpit: Production orders
View: Standard
Action: Open application
Category: Unexpected behavior
Problem: Preselection for field “Status” was (All).
Correction result: Preselection for field “Status” is now (Multiple selection), with status “Completed” and “Reorganization started” de-selected.
RFR-016517 Extension
Framework: Production
Application: Cockpit: Production orders
View: Cockpit: Production orders
Action: n.a.
Field/Column: Bill of resources, Bill of material, Routing
Category: New fields
Description: Production order header attributes Bill of material, Routing and Bill of resources can now be used as search parameters in Cockpit: Production orders.
5.1.6.5 Production orders
RFR-016517 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Dispatch and release, Entering line item manually
Category: Unexpected behavior
Problem: Scheduling Base Date (field Dispatching date in tab Dispatching) was set incorrectly and it was filled automatic every time it was empty, even when no line items were added to production order.
Correction result: Field is now automatically filled when it is empty and at least one line has been added using dispatching action or detail editor.
Automatic filling sets scheduling base date to its basic date depends on Scheduling category.
If Scheduling category is set to type “Back”, basic date is Latest end (in case this date is not set to finite the current date is used instead).
If the type of this field is “Forward”, basic date is Earliest begin date.
When the user sets a date that exceeds the basic date, it will be automatically changed forward (for “Forward” scheduling category) or backward (for “Back” scheduling category).
RFR-016517 Correction
Framework: Production
Application: Cockpit: Production orders
View: Selection fields –> “Level”
Action: New, Load
Category: Invalid data
Problem: Selection field “Level” has a value which is not “(All)”. Button “New” is clicked. Result: Selection field “Level” keeps original value instead of changing to “(All)”
A search filter “X1” is pinned to context menu with a specified value for field “Level” (not “(All)”). Another search filter “XAll” is pined to context menu with value “(All)” for field “Level”.
Filter “X1” is active and displayed. Now Filter “XAll” is activated. Result: Value of field “Level” does not switch to value “(All)” as is expected. Value is the same as before activation filter “XAll”.
Correction result: The value of field “Level” always changes to predefined values as expected after action “New” or switching from one filter to another.
RFR-016517 Correction
Framework: Production
Application: Order maintenance
View: Operation Detail
Action: Save
Category: Unexpected behavior
Problem: An operation is manually added to a production order. The default value of due date is changed.
Result: assigned resource line items do not have changed due date but still default value of due date.
Correction result: In above descried action all resources assigned to newly added operation have the same due date as new operation has.
5.1.6.6 Routings
RFR-016517 Correction
Framework: Production
Application: Bills of material, Routings, Operations, Resource lists
View: Bill of material, Routing, Operation
Action: Validate
Category: Exception
Problem:
1. Entering into the field “Inventory management organization” organization that is not Inventory Logistics organization caused exception and crashed the application.
2. In “Routings” application entering not existing organization into field “Inventory management organization” caused exception and crashed the application.
Correction result:
1. An error is displayed informing that only Inventory Logistics organizations can be used.
2. An error is displayed about entering non-existing organization
5.1.7 Purchasing
5.1.7.1 Purchase order confirmations
RFR-016517 Extension
Framework: Purchasing
Application: Supplier confirmations
Action: Import
Category: Extension
Description: The import filter for the business object “com.cisag.app.purchasing.obj.SupplierConfirmation” has been extended so that the attribute “orderChange” is now supported for the header and the main line items.
5.1.7.2 Purchase orders
RFR-016517 Correction
Framework: Purchasing
Application: Purchase orders
Action: Complete billing line items
Category: Exception
Problem: An exception occurs during the try to complete the invoice of some kit line items.
Correction result: Now the exception does not occur any more.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016517 Correction
Framework: Sales
Application: Customer invoices
Action: Generate
Category: Invalid data / Unexpected behavior
Problem: If a sales order was generated by a customer return the invoice generation considers sometimes the same sales order line item multiple times.
Correction result: Now the error does not occur any more.
Hint: In case of error you have to cancel the additional invoices manually.
RFR-016517 Correction
Framework: Sales
Application: Customer invoice
Action: Generate
Category: Invalid data / Unexpected behavior
Problem: In case of retail calculation and the kid of pricing value “Gross” the detail discounts values with own accounts are booked by mistake with taxes.
Correction result: Now, this error does not occur anymore.
5.1.8.2 Sales – General
RFR-016517 Correction
Framework: Sales
Application: Pro-forma invoices query, Customer invoices query
Action: Delete/Reorganize and refresh/display within the application
Category: Exception
Problem: If a “Pro-forma invoice” or “Customer invoice” is displayed in one session and the same instance is deleted or reorganized by another session or user an exception occurs during the try to determine the current “retail calculation” value within the line item list.
Correction result: Now the exception does not occur any more. In addition to that the data is disabled now if the application was opened with empty data, no data was found by load or after a successful delete.
5.1.8.3 Sales orders
RFR-016517 Correction
Framework: Sales
Application: Sales orders, Customer invoices
Action: Generate cash invoice
Category: Exception Unexpected behavior
Problem: In case of zero total quantity sales order line items the process “Cash invoice” does not work as expected if the sales order line item is configured as “direct delivery”; also an UnsupportedOperationException can occur.
Correction result: Now also this case works as expected.
5.1.9 Storage Location Control
5.1.9.1 Inventory management server
RFR-016517 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Reporting of an inventory order for a receipt of goods
Category: Exception
Problem: When stock with open receipt of goods process data within the receiving zone was removed by an inventory count process the put-away inventory postings of another receipt of goods could not be processed correctly.
Correction result: The inventory postings will be processed now and the inventory orders of other receipt of goods can be discarded as expected.
5.1.9.2 Inventory requisitions
RFR-016517 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders
Category: Exception
Problem: If an item quantity should be transferred but the specified unit of measure is not an inventory unit for the item an exception could be caused during the regeneration of the “Target”- inventory order.
Correction result: The quantity calculation is corrected now and the target inventory order can be regenerated as expected.
5.1.9.3 Storage locations
RFR-016517 Correction
Framework: Storage Location Control
Application: Inventory postings
View: Inventory postings
Unpack of loading units stored within a storage location
Category: Unexpected behavior
Problem: The calculation of the loading unit weight and volume was done although the loading unit would be unpacked.
Correction result: The calculation of the loading unit weight and volume will be done for the loading unit content but not for the loading unit to be unpacked.
5.2 Comarch Financials Enterprise
RFR-016517 Correction
Framework: General
Application: Partners
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: The configuration process of an “empty” OLTP needs to assign the user to the first partner. After doing it, logging off and logging in, the partner application displayed the error message CMP-52.
Correction result: From now the partner application will work as expected in that case.
5.3 System development
RFR-016516 Extension
Framework: Software development
Application: Development objects
View: n.a.
Action: n.a.
Category: New language supported
Description: It is now possible to support Portuguese as language.
RFR-016516 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-016515 Correction
Framework: Software development
Application: Job maintenance
View: n.a.
Action: Checkin
Category: Ergonomics
Problem: On checking a copyright string with an outdated address is set into java classes.
Correction result: The correct address is now set into the java class.
RFR-016515 Correction
Framework: System Management
Application: Simplified Data Export, Simplified Data Import
View: n.a.
Action: Validate
Category: Ergonomics
Problem: If you load a simplified export controller into the application and then decide to explicitly validate it, then an error message occurs even though everything is okay.
Correction result: Explicit validation now works normally.
RFR-016515 Correction
Framework: Software development
Application: Editorial cockpit
View: import texts
Action: n.a.
Category: Unexpected behavior
Problem: Since release 6.4 Terminus object are no longer maintained by an external system. Therefore, it should also be possible to import texts for Terminus objects.
Correction result: In editorial cockpit import of texts for terminus objects is now possible.
RFR-016515 Correction
Framework: All
Application: All cockpits
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: In cockpits the function of com.cisag.pgm.datatype.DataDescriptionFilter does not work.
Correction result: The interface com.cisag.pgm.datatype.DataDescriptionFilter works as expected.
RFR-016515 Correction
Framework: System Management
Application: System cockpit
View: User
Action: Refresh
Category: Exception
Problem: An Exception will be thrown, if the user does not have permission to load data.
Correction result: There is no exception anymore.
5.3.1 Configuration
5.3.1.1 System cockpit
RFR-016515 Correction
Process: system configuration
Category: Exception
Problem: A higher number of connected OLTP databases or database languages might cause “RuntimeException: timeout while acquiring a connection for database XX” upon application server start.
Correction result: Default value of database connections raised from 5 to 10 (if not set by system property com.cisag.sys.kernel.ConfigurationConnectionTransactionalConnections)
5.3.1.2 Tools
RFR-016515 Correction
Framework: System Management
Application: Tool: addsysusr
Category: Unexpected behavior
Problem: When specifying non-existing user in option -user, no error message is displayed, and an invalid user assignment is saved with the system. This could lead to further problems also in application System cockpit.
Correction result: The problem is resolved.
5.3.2 Data exchange
RFR-016515 Correction
Framework: System management
Application: Export data
View: n.a.
Action: Export data
Category: Exception
Problem: Export of the modification journal fails with “IllegalArgumentException: Object not defined! com.cisag.sys.tools.modificationjournal.log.ModificationJournalExportController$Entity”
Correction result: Successful export.
RFR-016515 Correction
Framework: System Management
Application: Import data
Importing business entity data with supplement business objects.
Category: Unexpected behavior
Problem: Checks in BIS imports implemented by interface com.cisag.pgm.bi.Verifier were not performed for supplement business objects. Affected were string length checks, and invalid value set entry checks, among others.
Correction result: Mentioned checks are performed for supplement business objects.
5.3.3 Kernel
5.3.3.1 Locking / Caching
RFR-016516 Extension
Process: Lock requests
Category: Performance
Problem: A lock request that cannot be granted due to a cyclic deadlock (one or more other requesters are waiting for a lock owned by the current requester, but have been granted the requests lock) will be canceled only after the set timeout has elapsed.
Correction result: The request is canceled immediately. The additional information provided can help to identify all involved requesters and locks.
Technical information: Instead of sys.kernel.locking.CisLockException the new Exceptions CisLockException, CisLockTimeoutException or CisLockDeadlockException (all in pgm.appserver) are thrown and can be caught.
RFR-016515 Correction
Process: Lock requests
Category: Invalid data
Problem: After a lock request using CisApplicationManagerWrapper.acquireLock(..) fails with a timeout, CisApplicationManagerWrapper.getLockInformation(String) does not provide user information on the current lock holder.
Correction result: Valid user information.
5.3.4 Repository
RFR-016516 Extension
Framework: Software development
Application: Development tasks, Batch for mass code synchronization with GitLab
View: n.a.
Action: activate task
Category: New application
Description: Add possibility to export repository code to gitlab class and export every task code when activated.
5.3.5 Software update
RFR-016516 Correction
Framework: System management
Application: Export apps
View: n.a.
Action: Generate add-on versions
Category: Exception
Problem: Generate fails with NullpointerException if there is a dependent friendly app declared for the current app, but does not exist in the current system (i.e. there is no development object for the dependent app).
Correction result: Exception replaced by error message (REP-03823).
5.3.6 System – General
RFR-016515 Correction
Framework: System Management
Tool: ExportSystem/ImportSystem
Category: Exception
Problem: If there are no views to be exported but the option to zip at the end is used, then it can happen that the empty Views directory is ignored.
This lead to an exception when using such an exported file as the source for tool “ImportSystem”.
Furthermore, on creating connections on a sql server some misleading outputs were created, because a default value was changed.
Correction result: If there is no views directory, a simple message is shown.
The parameter for the sql server connection is properly set.
5.3.7 Web server
RFR-016515 Extension
Framework: System-Management
Application: Webserver
View: n.a.
Action: n.a.
Category: New feature
Description: The internal (Jetty based) web server of CEE now supports the PROXY prototol, used by several load balancers, e.g. HAProxy.
Technical information: To enable the PROXY protocol support in CEE, use the following property: com. cisag.sys.kernel.webserver.acceptProxy=true
5.3.8 Workflow
5.3.8.1 Workflow roles
RFR-016515 Correction
Framework: Workflow
Application: WorkflowRoles
View: n.a.
Action: any action (in CoolBar or on exit) on “Workflow Roles” fresh run.
Category: unexpected behavior.
Problem: The application “Workflow Roles” enters edit/new mode and returns warning after any action in application.
Correction result: Behaves as it should.
Technical information: Changes are applied to load() and setMode() methods.