| Release | Comarch ERP Enterprise 6.3 |
| Release date | 17.03.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-016430 – RFR-016432
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-Fix05”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE630PB-Fix05
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix04 will be upgraded to CEE630PB-Fix05.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between 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
No batch data updates have to be carried out.
5.1 Application development
RFR-016432 Documentation
German UI texts have been corrected.
RFR-016432 Documentation
German user interface texts have been corrected.
RFR-016432 Correction
Framework: Storage Location Control
Application: Data export
View: n.a.
Export storage locations
Category: Exception
Problem: The storage location export filter caused an exception.
Correction result: The storage location export filter can be used as before.
RFR-016432 Correction
Framework: Base
Application: Items
View: Base Item
Action: Update (update and deleting packaging definitions)
Category: Unexpected behavior, invalid data
Problem: An inventory managed packaging definition couldn’t set as deleted. The error message GEN-09024 was displayed, if more than one version of the item existed. After changing usage of the the packaging definition to ”Conversion only’, the packaging definition could set to deleted and was deleted updating the item.
Correction result: The following points are changed:
1. the error message GEN-09024 when deleting inventory-managed packaging definitions has been removed. There is now only the usage check for the existence of an instance of the BO ItemUomStructureAssignment for a deletion marked packaging definition left.
2. when deleting an inventory-managed packaging definition, from now it will be deleted in all previous versions of the item, if this packaging definition is also inventory-managed in this version.
3. when updating or creating a new inventory-managed packaging definition, this is also automatically copied to all future versions of the item and to all previous versions of the item, provided that it exists in this version and is inventory-managed.
4. when changing the usage of an inventory-managed packaging definition to “conversion only”, if the change is allowed, this change is automatically copied to all previous versions of the item, if this packaging definition exists in that version.
RFR-016432 Documentation
German user interface texts have been corrected.
RFR-016432 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Output delivery slip copies…
Category: Exception
Problem: An exception occurred after changing the delivery orders number without forcing a reload und then clicking the action ‘Output &delivery slip copies…’
Correction result: From now as expected the error message SAL-105 will be displayed.
RFR-016432 Correction
Framework: n.a.
Application: n.a.
View: .n.a.
Action: Document output
Category: Exception
Problem: java.lang.NullPointerException will be thrown, if the programmer has not set OutputDocument properly.
Correction result: java.lang.NullPointerException will not be thrown and document will be outputted properly.
Technical information: java.lang.NullPointerException will be thrown, if the programmer has not set OutputDocument using DocumentOutputData.setOutputDocument(object instance).
So if OutputDocument is null, java.lang. NullPointerException will be thrown. Now the programmer must not set OutputDocument and java.lang. NullPointerException will not be thrown anymore.
RFR-016432 Correction
Framework: Inventory management
Application: Inventory count
View: n.a.
Action: Generate item-dependent inventory count lists for an item that is managed in identifiers.
Category: Unexpected behavior
Problem: Several inventory count lists could be generated for one identifier item, even if one of the inventory count lists contained a summary line item. This resulted that the inventory count lists could not be opened.
Correction result: A summary line item is only generated if there is not yet a line item with an identifier for this item or a line item with an identifier is only generated if there is no summary line item for this item.
RFR-016432 Correction
New hook contract definitions:
– com.cisag.app.shipping.unitload.hook.ui.UnitLoadCockpit
– com.cisag.app.shipping.unitload.hook.ui. UnitLoadMaintenance
Hook: com.cisag.pgm.appserver.hook.BatchActionHook
Description: Refer to the hook contract definition (development object category “Hook contract”).
RFR-016432 Documentation
The help document “Hook-Contract-Definitionen für Belege” has been updated: hook contract definition com.cisag.app.sales.invoice.hook.ui.CustomerInvoiceInquiry has been added.
RFR-016432 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-016432 Documentation
Help document “Hook-Contract-Definition: Kommunikationsmedium” has been provided.
RFR-016432 Correction
Framework: Document management
Application: Documents, Cockpit: Documents, Document types
View: Document files dockable view, Create notes dialog
Action: n.a.
Category: Unexpected behavior, Ergonomics
Problem:
1. Lack of translation for Other fields on Create note dialog.
2. Drop area too big and have no label.
3. New tab in Document types has no translation.
4. Dockable view for documents had no titlebar.
5. Last modified column in dockable view displayed date in wrong format.
6. Search fields for Status and Kind in Cockpit: Documents have not needed other value.
Correction result:
1. Missing translation has been added. Other fields are now expandable.
2. Drop area is now one column-size.
3. Missing translation has been added.
4. Dockable view for documents has now titlebar.
5. Displaying dates has been improved.
6. Status and Kind have no more other value.
RFR-016432 Correction
Framework: Inventory
Application: Inventory Postings
Action: Save
Category: Unexpected behaviour.
Problem: A conversion error led to an exception during creation/validation of EquipmentItemInstances, e.g. via Inventory Postings.
Correction result: The conversion error was fixed, so no exception occurs anymore.
RFR-016432 Documentation
German UI text has been corrected.
RFR-016432 Correction
Class:
com.cisag.app.bi.obj. InventoryCharacteristicsBi
com.cisag.app.bi.obj.LoadingUnitBi
com.cisag.app.bi.obj. StorageAreaBi
com.cisag.app.inventory.obj.TransportOrderTransaction
com.cisag.app.sales.obj. PickingOrderTransaction
com.cisag.app.inventory.delivery.obj.DeliveryTransaction
com.cisag.app. inventory.delivery.obj.DeliveryDetailTransaction
com.cisag.app.inventory.physical.obj. PhysicalInventoryReporting
Method: n.a.
Description:
Parts implements interface com.cisag.pgm.datatype.NonPersistentPart. Because they will never be used for BusinessObjects and they should never be used for BusinessObjects. Non persistent parts are allowed to be extended.
RFR-016432 Documentation
The help document “Customizing: Lagerlogistik” has been updated regarding several additional parameter and new layout.
5.1.1 Base
5.1.1.1 Base – General
RFR-016432 Correction
The following invalid logical datatypes have been deleted:
– com.cisag.app.general.order.ui.OrderDeliveryInfo_BO
– com.cisag.app.purchasing. SupplierInvoicingData
5.1.1.2 Cockpits
RFR-016432 Extension
Help document “Hook-Contract-Definitionen für Cockpits” (German language version) has been provided.
5.1.1.3 Contracts/RFQs/Quotations/Orders
RFR-016432 Correction
Class: com.cisag.app.sales.order.log. SalesKitLogic
Method: private void refreshComponents(boolean retailCalculation, SalesKitLogicMainDetailData kitMainDetailData, CurrencyConverter cc, boolean truncateCompValues)
Description: By mistake the method uses “DatatypeUtility#equals” instead of “Values#equals”.
RFR-016432 Documentation
Help document “Hook-Contract-Definition: Belegkette” has been updated regarding the interfaces OrderReferenceRegistrationHook and ReorganizationValidateHook. Help document “Hook-Contract-Definitionen für Belege” has been updated in the section on validations before voucher reorganization.
RFR-016432 Correction
Classes: Default…Source classes
Method: public void clear()
Description: Up from 6.3 there was a mistake related to the variables “sourceViewAdapter” and “hookTargetSourceImpl” in the Default…Source classes. Both variables need to be created again within the method “clear()”. Otherwise the supplements will be cleared but no DataAccessInitializerHook call was performed.
==> Exception e.g. during import of such a supplement.
RFR-016432 Extension
Class: com.cisag.app.general.order.hook.log.TargetSource
Description: The following new method has been added for the case that a source hook state implementation class implements further HookState interfaces:
Returns the hook state instance that belongs to this and the specified hook state implementation class.
You can use this method for the case that the specified hook state implementation class implements more than one hook state interface.
@param hookStateImplClass The hook state implementation class to be used.
@param stateRetrieverReturnType The “state retriever method” return type class to be used (mandatory).
This will be used to detect the relevant data view “state retriever” method.
This is typically the relevant source state class (e.g. “HeaderSourceState.class”).
@return The hook state implementation instance or null if not available.
@Stable
public S getHookState(Class hookStateImplClass, Class stateRetrieverReturnType);
So a client can force the determination of the specified hook state (e.g. HeaderSourceState or DetailSourceState).
RFR-016432 Correction
Frameworks: Purchasing, Sales
Applications: Supplier quotations, Purchase orders, Sales fast entry vouchers, Sales quotations, Sales orders, Distribution orders
Action: Change invoicing terms
Category: Unexpected behavior / Ergonomics
Problem: If some errors or unconfirmed warnings are present for a touched line item the line item will be but into the line item editor (OK) but the errors and warnings are not shown for the first line item (cleared by mistake within the step “free dialog data”). They will be shown only if the validate/post action is performed later.
Correction result: Now the errors/warnings will be shown directly as expected.
5.1.1.4 Item templates
RFR-016432 Correction
Framework: Base
Application: Import data
Filter: Items, Item templates
Action: Import
Category: Exception
Problem: An exception occurred importing item- or item template data that contained data of entity extension fields.
Correction result: From now importing item- or item template data that contained data of entity extension fields will work as expected.
5.1.1.5 Partners
RFR-016432 Correction
Framework: Base
Application: Partners
View: Partner relations
Action: Update
Category: Exception / Invalid data
Problem: Defining a partner relation with more than one period could cause an exception. Furthermore in specials cases the automatic update/create of incoming partner relations was incorrect.
Correction result: From now defining partner relations will work as expected.
5.1.2 Financials
RFR-016432 Extension
Framework: Financials
Application: Levy office assignments
Description: The hidden application “Levy office assignments” and the relevant business object “com.cisag.app.financials.obj.PointOfTaxationAssignment” is not needed any more.
So all that belongs to this application is now marked as “Deprecated” and will be deleted in a future release.
5.1.3 Inventory management
RFR-016432 Documentation
The help document “Cockpit: Ausprägungen” has been updated.
5.1.3.1 Availability query
RFR-016432 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Calculate availability…
Category: Unexpected behavior
Problem: If a set is not available the calculation of the next availability date could be not correct because the wrong number of components were used.
Correction result: The calculation of the next availability date will use the correct number of needed components as expected.
5.1.3.2 Identifiers
RFR-016432 Correction
Framework: Inventory Management
Application: Compile identifier where-used list
View: n.a.
Action: Execute…
Category: Exception
Problem: Inventory postings for packing and unpacking were considered and that caused an exception.
Correction result: Inventory postings for packing and unpacking will not be considered during the rebuild process.
RFR-016432 Correction
Framework: Inventory
Application: Identifiers
Action: Open application
Category: Exception / Unexpected behavior
Problem: If the measurements are not activated in the Customizing for identifiers an exception occurs durch the try to open the “Identifiers” application.
Correction result: Now the exception does not occur any more and the “Measurements” data is not displayed as expected.
RFR-016432 Extension
Framework: Inventory Management
Application: Cockpit: Identifiers
Support serial numbers without inventory management in general
Field/Column: Identifier category
Category: New function
Description: Cockpit: Identifiers should also support serial numbers without inventory management.
5.1.3.3 Inventory cockpit
RFR-016432 Correction
Framework: Inventory Management
Application: Loading units – correction mode
View: n.a.
Action: Save
Category: Exception
Problem: If a loading unit report was changed to “not found” during it was corrected within the “loading unit correction mode” a timeout exception could caused at saving the correction.
Correction result: If a loading unit report is changed to “not found” during it is corrected within the “loading unit correction mode” an error message will be displayed at saving the correction.
5.1.3.4 Inventory count
RFR-016432 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Report of unit loads stored in different slots of the same storage location
Category: Unexpected behavior
Problem: Report of different unit loads stored in different slots of the same storage location was denied by an error message.
Correction result: Report of different unit loads stored in different slots of the same storage location can be done as expected.
RFR-016432 Documentation
The help document “Inventurzählliste erzeugen” has been created.
The following help documents have been updated regarding new action “Inventurzählliste erzeugen”: * Cockpit: Bestände
– Cockpit: Aktuelle Bestandswerte
– Cockpit: Bewegungsdaten
– Cockpit: Inventurzähllisten/Positionen
– Cockpit: Lager-Artikel
– Cockpit: Lagerplätze
5.1.3.5 Inventory management – General
RFR-016432 Correction
Framework: Inventory
Application: Cockpit: Items/Inventory Management
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The application didn’t support REST-Service. Data couldn’t be exported in CSV format.
Correction result: From now the application will support REST-Service. From now data could be exported in CSV format.
5.1.3.6 Inventory postings
RFR-016432 Correction
Framework: Inventory management
Application: Delivery orders
View: n.a.
Action: Generate and output delivery slips with multiple inventory owners.
Category: Unexpected behavior
Problem: The revaluation posting could not be posted because the reference storage area was set.
Correction result: The material posting check was corrected to the effect that a reference storage area is also permissible in the case of a revaluation.
5.1.3.7 Loading units
RFR-016432 Correction
Framework: Inventory
Application: Picking orders, Delivery Orders
Dialog: Generate loading units…
Action: Assign. Load
Category: Ergonomics
Problem: As a result of the actions “Assign” and “Load” the message SHP-0003 was displayed.
Correction result: From now as a result of the actions “Assign” and “Load” the message SHP-0003 won’t be displayed.
5.1.3.8 Picking orders
RFR-016432 Correction
Framework: Inventory
Application: Picking orders
View:
Action: Generate loading units…
Category: Unexpected behavior / Ergonomics
Problem: In the dialog the user was able to load the data of delivery orders (and pack them) that weren’t be part of the loaded picking order. Moreover the search of the field “Auftragsnummer” was not initialized correctly if the dialog was opened again after loading a new picking order.
Correction Result: From now the dialog will work as expected.
RFR-016432 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Generate, assign and display loading units…
Category: Ergonomics
Problem: The action ‘Generate, assign and display loa&ding units…’ is enabled although no valid picking order is already loaded.
Correction result: From now the action ‘Generate, assign and display loa&ding units…’ will be enabled only if a valid picking order is loaded.
5.1.3.9 Receipts of goods
RFR-016432 Correction
Framework: Inventory
Application: Receipts of goods
Action: Order assignment
Category: Unexpected behavior / Ergonomics
Problem: In some cases the found order data is displayed with empty fields within the order assignment result list.
Correction result: Now the found order data will be displayed as expected with the normal field content.
RFR-016432 Correction
Classes:
– com.cisag.app.inventory.receipt.ui. TransactionTypeEditorFactory
– com.cisag.app.inventory.receipt.ui. SalesOrderTypeEditorFactory
Description: Within the JavaDoc both classes are using by mistake a reference to the class SalesOrderTypeField. Now both classes have been corrected.
5.1.3.10 Reservations
RFR-016432 Correction
Framework: Inventory Management
Application: Cleanup of reservation data (Not displayed)
View: n.a.
Action: Start data correction
Category: Exception
Problem: The application is closed with an exception.
Correction result: The data update can be executed as expected.
5.1.3.11 Warehouses
RFR-016432 Correction
Framework: Inventory management
Application: Import data
Action: Data import in the background for an existing warehouse without site specification
Category: Exception
Problem: The missing site information led to an exception.
Correction result: The missing site information is determined with the existing warehouse.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016432 Extension
Frameworks: Purchasing, Sales, Inventory
Applications: Distribution order types, Distribution orders, Delivery orders, Receipt of goods, Pro-forma invoices, Customer invoices, Supplier invoices
Action: Return of goods
Category: New functionality
Description: The distribution order supports now the functionality “Return of goods” by an own type value within the distribution order type data.
A return distribution order can base either on a delivery distribution order (prices are always used from the original delivery order) or can be without an original delivery order (own prices are supported). Return distribution orders are creating credit note invoices by negative quantities; also pro-forma invoices are using negative quantities in case of return distribution orders.
In addition to that the owner change storage area can be specified now so that the transfer storage area stock can belong now optionally already to the target owner (in case of delivery). The same for the return.
Further some optimizations have been added for the inventory stock valuation – especially for the valuation of the freight costs.
Technical information: Please note that some incompatible code changes were needed to perform this new functionality.
For the valuation the following new classes have been added that support also the debug functionality:
– com. cisag.app.inventory.log.InventoryTransactionValuationLogic
– com.cisag.app.multiorg.order.log. DistributionOrderValuationLogic
5.1.4.2 Inter-company billing
RFR-016432 Correction
Framework: Base
Application: Inter-company billing
Action: Generate inter-company billing
Category: Invalid data / Unexpected behavior
Problem: If the invoice summary functionality “Per period” is used the wrong invoice voucher date is determined. It should be the last day of the relevant period but it is the first day of the next period.
Please note that if the determined invoice voucher date is in the future today will be used instead (unchanged behavior).
Correction result: Now the correct invoice voucher date will be determined.
5.1.5 Planning
RFR-016432 Extension
Framework: Planning
Application: Artikel-Dispositionsdaten-Zuordnungen, Material requirements planning, Calculate purchase recommendations, Calculate distribution recommendations
View: n.a.
Action: n.a.
Category: New application
Description: The new application Artikel-Dispositionsdaten-Zuordnungen does manage alternative master data which is used in
Material requirements planning, Calculate purchase recommendations and Calculate distribution recommendations according to RFE-004879 Phase 1.
Import and export of com.cisag.app.aps.obj.PlanningThresholdAssignment is also implemented.
Other logics do not consider this new master data yet, until Phase 3 of RFE-004879 is finished.
The new Item planning data classification can be specified in the assignments, but will be included to ItemPlanningData later in Phase 2.
Technical information: The hash-code business object com.cisag.app.aps.obj. PlanningThresholdConfiguration should be reorganized periodically by the standard reorganization application.
RFR-016432 Extension
Framework: Production
Application: Artikel-Dispositionsdaten-Zuordnungen
Action: Export data/ import data
Category: New action
Description: Added import/export functionality for new application “Artikel-Dispositionsdaten-Zuordnungen”
5.1.5.1 Material requirements planning
RFR-016432 Correction
Framework: Planning
Application: Material requirements planning
View: Save locations
Action: Save backup file
Category: Exception
Problem: Invalid entry in backup file generates IO exception when calling save backup file
Correction result: Invalid entry in backup file generates an error message when calling save backup file
5.1.6 Production
RFR-016432 Extension
Framework: Production
Application: Equipment, Bills of material
Action: Create a new equipment item; add equipment item to bill of material
Category: New action
Description: Validation was added to Quantity and UOM of equipment items (EI). This takes place first during initial creation of EI, then while adding an EI to a bill of material and finally whenever the user tries to change the UOM of an EI already in use by a bill of material.
5.1.6.1 Operations
RFR-016432 Correction
Framework: Production
Application: Import data
Action: Import data
Category: Unexpected behavior
Problem: When a routing contained an operation that was generated by an operation template as a ProductionPlanDetail, importing parameter values to this detail failed to change the actual value.
Correction result: Importing changes to the parameters of ProductionPlanDetails generated in the aforementioned way now actually changes the parameter values as intended.
5.1.7 Purchasing
5.1.7.1 Supplier invoices
RFR-016432 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Book value correction
Category: Invalid data / Unexpected behavior
Problem: Since “CIS620PB-Fix11 KW20/2022” a value correction supplier invoice (based on a value correction distribution order) that belongs to a distribution order delivery refreshes directly the valuation data of the original (delivery) distribution order line item – before this change value correction distribution order line items have own valuation data. This change is OK but by mistake the wrong net price, net value and calculated costs are used (the data of the original order line item have to be used and not the data of the correction order line item). In some cases the value correction distribution order line item contains a quantity different from zero – even if such data is present the quantity must not be used – only the value needs to be considered.
Correction result: Now this error was corrected as expected.
RFR-016432 Documentation
The help document “Customizing: Beschaffung” has been corrected and updated regarding the field “Kontoherkunft für Zusatzkostenrechnungen”.
RFR-016432 Extension
Framework: Purchasing
Application: Supplier invoices
1.)
Action: Check supplier invoice
Category: New validation
Description: The “Check supplier invoice” validation checks now if a valid posting period exists for the supplier invoice “Date of receipt”.
2.)
Action: Change exchange rate or supplier invoice date
Category: New field/functionality
Description: In case of an open external supplier invoice the tax date can be changed now by the “Change exchange rate or supplier invoice date” functionality.
RFR-016432 Correction
Class: UPDSUP104367
Description: The coding of the data update application UPDSUP104367 has been changed to increase the performance.
RFR-016432 Correction
Frameworks: Inventory, Purchasing
Applications: “Receipt of goods”, “Cockpit: Receipts of goods”, “Supplier invoices”
Action: Create supplier invoice
Category: Invalid data / Unexpected behavior
Problem: If parallel processing is used in some cases more than one supplier invoice will be created for a receipt of goods.
Correction result: Now only one supplier invoice will be created as expected.
RFR-016432 Extension
1.)
Framework: Inventory
Applications: “Receipts of goods” and “Cockpit: Receipts of goods”
Action: “Generate supplier invoice”
2.)
Framework: Purchasing
Applications: “Purchase orders” and “Cockpit: Purchase orders”
Action: “Generate supplier invoices for third-party orders”
3.)
Framework: Purchasing
Application: “Supplier invoices”
Action: “Generate correction supplier invoice”
Category: New fields
Description: All of these actions have now some new fields that can be used to specifiy the values of the attributes “External voucher date” and “Date of receipt” of the newly generated supplier invoice.
Please note that in case of the action “Generate correction supplier invoice” you can only specify the value of the attribute “Date of receipt”.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016432 Correction
Frameworks: Financials, Inventory, Sales
Applications: Delivery orders, Sales orders, Customer invoices, Debtor credits
Action: Create/Cancel customer invoice
Category: Invalid data / Unexpected behavior
Problem: During the customer invoice creation and cancelation there might be the need to update also some debtor credit instances. If such a debtor credit instance is currently locked by any user the invoice generation will be performed but the step “update debtor credit” will be skipped without any changes (only error messages occur that the instance is locked). So the debtor credit data does not contain as expected the customer invoice data.
Correction result: Now the relevant debtor credits will be tried to lock by the customer invoice generation/cancelation. If the lock failed the creation will skip the relevant shipping orders/sales orders (without any message). In case of customer invoice cancellation the customer invoice will not be canceled in this case.
RFR-016432 Correction
Framework: Sales
Applications: Sales orders, Customer invoices
Action: Create invoice
Category: Invalid data / Unexpected behavior
Problem: In some cases an exception (“java.lang.RuntimeException: Get of object not possible: transaction not found”) occurs (classes: “com.cisag.app.sales.invoice.log.SalesOrderIterator$OrderComparator” and “… $OrderDetailComparator”). As result the invoice generation stops and the customer invoice is invalid.
Correction result: Now the exception does not occur any more. To complete the invalid invoices you have to use the customer invoice cockpit functionality “Finish and output invalid invoice”.
RFR-016432 Correction
Framework: Sales
Application: Customer invoices
Action: Create invoice (based on sales orders)
Category: Invalid data / Unexpected behavior
Problem: A released quantity to be invoiced was cleared to early (within an other transaction). So if the second transaction that considers this quantity as a new invoice line item failed a situation occurs that a cleared invoice quantity is not considered by any invoice. This is especially a problem in the case of credit note line items that belong to a customer return.
Correction result: Now clearing a released invoice quantity will be performed in the same step as the invoice line item creation (same transaction) – so this problem will not occur any more.
5.1.9 Storage Location Control
5.1.9.1 Inventory orders
RFR-016432 Correction
Framework: Storage Location Control
Application: Receipt of goods/Inventory requisitions
Generate inventory orders to put a loading unit
Category: Exception
Problem: If the loading unit could be put into a storage location that had open processes but it had empty slots the automatic put logic caused an exception.
Correction result: The loading unit can be put as expected.
5.1.9.2 Lademittel
RFR-016432 Correction
Framework: Sales
Application: Cockpit: Empties account
Action: Generate balances
Category: Invalid data / Unexpected behavior
Problem: In some cases the calculated balance is not correct.
Correction result: Now the calculated balance is as expected.
5.2 System development
RFR-016431 Documentation
The help documents “Performance Monitors” and “Log and Analyze Performance Information” have been updated regarding deprecated file performance monitors.
RFR-016431 Extension
Framework: Software development
Application: Development objects
View: Parts/Business objects.
Action: using parts in business objects.
Problem: Changing a part used in a business object might lead to a severe problem if for this part a part extension exists.
Therefore standard part must not be changed.
Nevertheless, if a part is not used in business objects there is no technical problem.
Correction result: Th new interface “com.cisag.pgm.datatype.NonPersistentPart” allows to mark a part as “non-persistent”. A part marked as non-persistent may be changed but in turn must not be used in business object.
A part can only be marked as “non-persistent” if it is not already used in a business object.
Technical information: Because usage of part can not be checked on follow up system, a warning is send if a business object uses a non-persistent part.
RFR-016431 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-016431 Documentation
German user interface texts have been corrected.
RFR-016431 Ergonomics
Files of the online help file system have been updated.
RFR-016431 Correction
Help document “Systemcockpit: Typ “Arbeitsbereich”” has been updated regarding the “Storage medium” field and the “Test workspace” action.
RFR-016431 Documentation
The help document “Einführung: Workflow-Management” has been updated. Among other things, the new chapter “Abwesenheiten” has been added.
RFR-016431 Documentation
The help document “Berichtsausgabeaufträge” has been provided (description of and procedure for ReportOutputMaintenance application).
RFR-016430 Correction
Framework: System
Application: System
View: N.a.
Action: n.a.
Optimizing CisConnectionPool
Category: Unexpected behavior
Problem: If the database load is extremely high, or if too few database connections are configured, it could happen that the connection pool does not release any database connection, although there are still free ones.
Correction result: The connection pool can issue a connection in this case.
RFR-016430 Correction
Framework: Software development
Application: Development tasks
View: n.a.
Action: Importing objects in batch
Category: Unexpected behavior
Problem: Due to a possible race condition sometimes the import of development objects does not work.
The message says that the task is not open while in fact it is open.
Correction result: The import now works.
RFR-016430 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Exception
Problem: Function dboString cannot be used in the transition condition.
Correction result: Function dboString can be used in the transition condition.
5.2.1 Application server
5.2.1.1 Batch
RFR-016430 Correction
Framework: System Management
Executing series batch jobs
Category: Unexpected behavior
Problem: A distributed batch series job could change to “Completed” status after execution, instead of executing again at the next planned times.
Correction result: The sereis batch job executes as specified for the series.
Technical information: The problem is limited to distributed batch jobs. The problem occurs if the batch application specifies to wait for sub jobs, but does not specify sub jobs to wait for. One affected batch application is com.sem.ext.app.mcs.item.assortment.log.ItemTransferBatch.
5.2.1.2 JobControl
RFR-016430 Correction
Framework: System Mnaagement
Customizations in system context menus
Category: Unexpected behavior
Problem: Certain customizations in the system context menu of a business entity may be lost after an update of the CEE system. The problem occurs if the standard menu entry, or a field-specific standard menu entry were changed, but no other changes were done for menu entries. User-specific context menus in tab “Context menu” are not affected.
Correction result: The problem is resolved.
5.2.2 Data exchange
RFR-016430 Correction
Framework: System Management
Application: Export data, Import data
Action: Export WSDL
Category: Unexpected behavior
Problem: In the generated WSDL files, the web service URL in the wsdlsoap:address element is missing a slash character (/). In some use cases the WSDL file might be unusable because of this. Requesting WSDL files through a “?wsdl” URL is also affected.
Correction result: THe problem is resolved.
5.2.3 Knowledge Store
RFR-016430 Correction
Framework:SystemManagement
Application: KnowledgeStore
View: n.a.
Action: n.a.
Category: Possible deadlock
Problem: If two parallel processes change documents within the same folder both processes try to update the “last changed” timestamp of the folder.
This can lead to a deadlock.
Correction result: Locking has been change and updating the timestamp of the folder now occurs within a seperate transaction.
That prevents the deadlock.
Technical information: Problem only occurs on database driven knowledge store. On filesystem knowledge store implementation the problem did not occur.
5.2.4 Repository
5.2.5 System – General
RFR-016431 Correction
Framework: all
Application: all Cockpits
View: n.a.
Action: Load, Count
Category: Exception
Problem: A huge number of parameters could lead to an exception, as the parser is not able to create the appropriate OQL-statement.
Correction result: An error message is sent.
Technical information: The parser is limited by the number of possible recursions. Each parameter in one field leads to one extra recursion. Therefore the number of possible parameters in a field is limited. The limit is somewhere below 2500.
5.2.6 Workflow
RFR-016431 Correction
Framework: Workflow Management
Category: Extension
Application: Activity definitions
Problem:
It was not possible to set the value of other fields and for managed supplement workflow attributes in a script.
Correction result:
The following new script functions have been implemented for managed supplement:
– HashMap getSupplement(CisObject object, String supplement)
– HashMap getSupplement(CisObject object, String supplement, Boolean writeMode)
– HashMap getOrCreateSupplement(CisObject object, String supplement)
– HashMap getOrCreateSupplement(CisObject object, String supplement, Boolean writeMode)
Boolean validateSupplement(HashMap supplement)
Boolean putSupplement(HashMap supplement)
The following new script functions have been implemented for setting other fields:
– String dboText(String schemaName, CisObject object, String attributeName)
Number dboTextContentType(String schemaName, CisObject object, String attributeName)
– String dboValueSetName(String schemaName, CisObject object, String attributeName)
– String[] dboListValueSetName(String schemaName, CisObject object, String attributeName)
– String dboValueSetDescription(String schemaName, CisObject object, String attributeName)
– String[] dboListValueSetDescription(String schemaName, CisObject object, – String attributeName)
The following new setter functions for other fields have been implemented:
– Boolean setDboCisDate(String schemaName, CisObject object, String attributeName, CisDate date)
– Boolean setDboCisObject(String schemaName, CisObject object, String attributeName, CisObject object)
– Boolean setDboDomesticAmount(String schemaName, CisObject object, String attributeName, Number amount)
– Boolean setDboDomesticAmount(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app. general.obj.DomesticAmount) domesticAmount)
– Boolean setDboForeignAmount(String schemaName, CisObject object, String attributeName, Number amount, Guid currency)
– Boolean setDboForeignAmount(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app.general.obj.ForeignAmount) foreignAmount)
– Boolean setDboGuid(String schemaName, CisObject object, String attributeName, String path)
– Boolean setDboNumber(String schemaName, CisObject object, String attributeName, Number decimal)
– Boolean setDboQuantity(String schemaName, CisObject object, String attributeName, Number amount, Guid uom)
– Boolean setDboQuantity(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app.general.obj.Quantity) quantity)
– Boolean setDboString(String schemaName, CisObject object, String attributeName, String text)
– Boolean setDboTimestamp(Timestamp schemaName, CisObject object, Timestamp attributeName, Timestamp timestamp)
– Boolean setDboValueSet(ValueSet schemaName, CisObject object, ValueSet attributeName, Number id)
– Boolean setDboValueSetName(String schemaName, CisObject object, String attributeName, String constant)
– Boolean setDboText(String schemaName, CisObject object, String attributeName, String text, Number contentType)
– Boolean setDboText(String schemaName, CisObject object, String attributeName, String text, Number contentType, String language)
– Boolean setDboListCisDate(String schemaName, CisObject object, String attributeName, CisDate[] dateList)
– Boolean setDboListCisObject(String schemaName, CisObject object, String attributeName, CisObject[] objectList)
– Boolean setDboListDomesticAmount(String schemaName, CisObject object, String attributeName, Number[] amountList)
– Boolean setDboListDomesticAmount(String schemaName, CisObject object, String attributeName, CisObject[](com.cisag.app.general.obj.DomesticAmount) domesticAmountList)
– Boolean setDboListForeignAmount(String schemaName, CisObject object, String attributeName, Number[] amountList, Guid[] currencyList)
– Boolean setDboListForeignAmount(String schemaName, CisObject object, String attributeName, CisObject[](com.cisag.app.general.obj.ForeignAmount) foreignAmountList)
– Boolean setDboListGuid(String schemaName, CisObject object, String attributeName, String[] pathList)
– Boolean setDboListNumber(String schemaName, CisObject object, String attributeName, Number[] decimalList)
– Boolean setDboListQuantity(String schemaName, CisObject object, String attributeName, Number[] amountList, Guid[] uomList)
– Boolean setDboListQuantity(String schemaName, CisObject object, String attributeName, CisObject[](com.cisag.app.general.obj.Quantity) quantityList)
– Boolean setDboListString(String schemaName, CisObject object, String attributeName, String[] textList)
– Boolean setDboListTimestamp(Timestamp schemaName, CisObject object, Timestamp attributeName, Timestamp[] timestampList)
– Boolean setDboListValueSet(ValueSet schemaName, CisObject object, ValueSet attributeName, Number[] idList)
– Boolean setDboListValueSetName(String schemaName, CisObject object, String attributeName, String[] constantList)
The following new validate functions for other fields have been implemented:
– Boolean validateDboCisDate(String schemaName, CisObject object, String attributeName, CisDate date)
– Boolean validateDboCisObject(String schemaName, CisObject object, String attributeName, CisObject object)
– Boolean validateDboDomesticAmount(String schemaName, CisObject object, String attributeName, Number amount)
– Boolean validateDboDomesticAmount(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app.general.obj.DomesticAmount) domesticAmount)
– Boolean validateDboForeignAmount(String schemaName, CisObject object, String attributeName, Number amount, Guid currency)
– Boolean validateDboForeignAmount(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app.general.obj.ForeignAmount) foreignAmount)
– Boolean validateDboGuid(String schemaName, CisObject object, String attributeName, String path)
– Boolean validateDboNumber(String schemaName, CisObject object, String attributeName, Number decimal)
– Boolean validateDboQuantity(String schemaName, CisObject object, String attributeName, Number amount, Guid uom)
– Boolean validateDboQuantity(String schemaName, CisObject object, String attributeName, CisObject(com.cisag.app.general.obj.Quantity) quantity)
– Boolean validateDboString(String schemaName, CisObject object, String attributeName, String text)
– Boolean validateDboTimestamp(Timestamp schemaName, CisObject object, Timestamp attributeName, Timestamp timestamp)
– Boolean validateDboValueSet(ValueSet schemaName, CisObject object, ValueSet attributeName, Number id)
– Boolean validateDboValueSetName(String schemaName, CisObject object, String attributeName, String constant)
The following new reset function for other fields have been implemented:
– resetDbo(String schemaName, CisObject object, String attributeName)
The following fixes to exsiting functions have been implemented:
– union(), intersection(), minus() – now returns values in order which they were passed in arguments
– existing getters for other fields with prefix “dboList” now return values in order
– dboCisDate now returns null value instead of UNDEFINED_DATA
– dboListCisDate now returns list(null) values instead of list(UNDEFINED_DATA)
RFR-016431 Correction
Framework: Workflow managment
Application: n.a.
View: n.a.
Action: Forward task
Category: New field
Description: Additional option to forward workflow tasks to specific workflow role.
RFR-016431 Correction
Framework: Workflow Management
Application: Activities, Processes
View: n. a.
Action: load, all actions on tasks (without close unprocessed), action on activities
Category: Exception
Problem: After upgrading a system core, there are sometimes problems with deserializing the environment on the activities and process and load ended with an exception.
Correction result: When an activity or process has a problem with deserializing of environment can load an activity or process and can close unprocessed tasks and activities.
RFR-016431 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a
Category: Unexpected behavior
Problem: Forward user attribute has filled on target forward task.
Correction result: Forward user attribute has filled on source forward task.
RFR-016430 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: Forward task
Field: User
Category: New action
Description: New algorithm is prompting a default forward user.
RFR-016430 Correction
Framework: Workflow Managment
Application: Search for tasks
View: n.a.
Action: open
Category: Unexpected behavior
Problem:
1. When task is delegeted, then open option is disabled.
2. When option “Accept task automatically” is set as “Only automatically assigned task” task is accepted on open action.
Correction result:
1. When task is delegeted, then open option is enabled.
2. When option “Accept task automatically” is set as “Only automatically assigned task” task is not accepted.
RFR-016430 Correction
Framework: all
Application: all
View: n.a.
Action: n.a
Category: Exception
Problem: an unexpected InterruptedException is thrown.
Correction result: The exception is not thrown
Technical information: In rare cases a race condition in class com.cisag.sys.workflow.log.WorkflowDatabase leads to an unexpected InterruptedException. The exception must not necessary occur in the workflow.
RFR-016430 Correction
Framework: Workflow Management
Application: Activity
View: n.a.
Action: n.a.
Category: Exception
Problem: After completing activity from workflow coolbar, activity remains in progress.
Correction result: Activity status changes accordingly to taken actions.
5.2.6.1 Absences
RFR-016431 Correction
Framework: Workflow Managment
Application: Absences
View: n.a.
Action: save, load, valid
Category: Exception
Problem: Possibility to create a absence to non existing user. Load non existing user
Correction result: Added a new save validation to block adding non existing users.
RFR-016430 Correction
Framework: Workflow Management
Application: Search for tasks
View: n.a.
Action: start search
Category: Unexpected behavior
Problem:
1. When change an absence person to not absence, absences from delegate tasks in other user disappear after relogin a system.
2. When absence change status to “not absent” a date of begin/end time has filled.
Correction result:
1. When change an absence person to not absence, absences from delegate tasks in other user disappear after refresh a list.
2. When absence change status to “not absent” a date of begin/end time has cleared.
Technical information: Absences has cached in the system – needed to better performance work. Now new search in “Search for tasks” can refresh this cache.
5.2.6.2 Activities
RFR-016430 Correction
Framework: Workflow management
Application: activities
View: n.a.
Action: complete unprocessed
Category: Unexpected behavior
Problem: When complete unprocessed a task in activity, validate method get a status parameter as done.
Correction result: When complete unprocessed a task in activity, validate method get a status parameter as canceled.
RFR-016430 Correction
Framework: Workflow Management
Application: Activities
View: n.a
Action: Open
Category: Unexpected behavior
Problem: User creates Activity definition with initialized result parameters and attribute “Confirmation of completion” from “Processing” tab set to “Open”. When user opens that activity it is completed without allowing the user to enter results.
Correction result: User is allowed to enter results while opening activity described in “Problem” section.
5.2.6.3 Activity definitions
RFR-016430 Correction
Framework: Workflow Management
Application: Activity
View: n.a
Action: complete
Category: Ergonomics
Problem: Too small activity result dialog when complete a task.
Correction result: Activity result dialog has a normal size.
5.2.6.4 Batch jobs
RFR-016430 Correction
Framework: Workflow management
Application: Service client
View: n.a.
Action: n.a.
Category: Exception
Problem: Use authentication mode as none calls exception when use https protocol.
Correction result: Use authentication mode as none works correctly when use https protocol.
5.2.6.5 Declarations and scripting
RFR-016430 Correction
Framework: Workflow Management
Category: Extension
Application: Activity definitions
Problem: When it gets another field value CisDate in script language for new initialized value have an exception.
Correction result: When it gets another field value CisDate in script language for new initialized value have not assigned value (NULL).
5.2.6.6 Process definitions
RFR-016430 Correction
Framework: Workflow management
Application: impwfl
View: n.a.
Action: import
Category: Unexpected behavior
Problem: After created a Process Definition with a webservice node, then export it using expwfl and then import it using impwfl then the webservice node becomes a service node in the target system.
Correction result: Webservice node has imported correctly.
5.2.6.7 Workflow Engine
RFR-016430 Correction
Framework: Workflow Management
Category: Extension
Application: n.a.
Problem: When system closes some workflow threads is not break.
Correction result: Add more breakpoints in workflow threads.
5.2.6.8 Workflow templates (transport)
RFR-016430 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: Process definitions cannot be saved as template again
Correction result: Fixed template saving.