| Release | Comarch ERP Enterprise 6.3 |
| Release date | 04.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-016479 – RFR-016481
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”. |
Table of contents
1 Information about support deliveries 3
2 Installation of software updates 3
3 Information about CEE630PB-Fix13_ 4
3.1 Installing support deliveries 4
3.2 Cumulative installation of support deliveries 4
3.3 Parallel or sequential installation 4
3.4 Problems during the installation 5
4 Rework after installation_ 5
5 Contained changes and extensions 5
5.1.1.1 Contracts/RFQs/Quotations/Orders 6
5.1.1.2 Item characteristics 6
5.1.5.1 Purchase order confirmations 13
5.1.6 Relationship Management 14
5.1.6.1 Customizable cockpits 14
5.1.8 Storage Location Control 15
5.1.8.2 Inventory query at storage locations 16
5.2 Comarch Financials Enterprise 16
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-Fix13.”
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-Fix13
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix12 will be upgraded to CEE630PB-Fix13.
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 Contained changes and extensions
5.1 Application development
RFR-016481 Documentation
The hyperlinks in the help document “Customizing: Rechnungswesen” (German language version) have been updated.
RFR-016481 Documentation
The following help documents have been created:
– Werkskalender importieren
– Aufbewahrungskategorien importieren
– Erklärungen importieren
– Verarbeitungszwecke importieren
– Verfügbarkeitsregeln importieren
The help document “Bewertungspreisänderungen importieren” has been updated regarding new documentation standard.
The help document “Export- und Import-Schnittstellen” has been updated regarding the new import documentations.
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016481 Ergonomics
Frameworks: Inventory, Purchasing and Sales
Applications: Supplier contracts, Supplier quotations, Purchase orders, Purchase order confirmations, Sales quotations, Sales orders, Distribution orders, Customer returns, Receipts of goods
Actions: Create actions with dialog
Category: Ergonomics
Problem: Before this correction the create actions with a dialog did not initialize all fields and did not set the focus to the first field if the dialog was opened again.
Correction result: Now all fields will be set to the same initial state and the first field gets the focus also if the dialog will be used multiple times.
RFR-016481 Correction
Package: com.cisag.app.general.order.hook.log
Classes: HeaderDependentHook, HeaderReorganizationHook, DetailDependentHook and DetailReorganizationHook
Description: The Java documentation of these classes have been corrected and extended.
5.1.1.2 Item characteristics
RFR-016481 Correction
Framework: Base
Application: Item-characteristics assignments
Action: Load
Category: Exception
Problem: In some cases the line data will be changed as sub step of the “load” functionality; if so an event will be send that might cause an exception.
Correction result: Because the load functionality sends at the end a “rebuild all” event no further sib events are needed; so these sub event causes now no exception any more. In addition to that, the method where the exception occurs before this corrections supports now also null parameters.
RFR-016481 Extension
Framework: Base
Application: Item characteristic classifications
Action: Import
Problem: In some cases a child needs to be added to a leaf node. This is not supported if such a leaf node is already in use.
This causes an exception during import.
This exception is OK but it is difficult to detect the relevant classification path without any further information.
Correction result: Now the exception contains the path of the node that cannot be used as parent because it is a used leaf node.
Hint: Please note that you can enable the debug information of the class “com.cisag.app.tools.ObjectReferenceLogic” to determine some data about the instances that are using the relevant classification.
5.1.1.3 Items
RFR-016481 Correction
Framework: Production
Application: Update change history of production orders
View: n.a.
Action: Execute the (batch job) application
Category: Exception
Problem:
1. A production order has not yet been transferred to “Update change history”, but some reporting (product, material, operation) already has been performed. After transfer is done via execution of “Update change history of production orders” manually one/more production order details (material and/or operation) are added to production order.
Result: an exception occurs if unit of measure of added details do not match with base unit of measure of product. The exception also occurs with this context if batch job “Create production orders change history” is running. This batch job – if started – normally runs continuously.
2. A production order has not yet been transferred to “Update change history”. It has an external operation with material provided assigned. A receipt of goods of assigned purchase order has been performed for this external operation. While transferring production order data via execution of “Update change history of production orders,” an exception occurs.
Correction result:
1. Manually added production order details are transferred in a repeated execution of “Update change history of production orders” as expected. No exception occurs.
2. Transferring external operations of production orders via execution of “Update change history of production orders” works as expected. No exception occurs.
5.1.2 Inventory management
RFR-016481 Correction
Framework: Inventory management
Application: Inventory requisitions
View: n.a.
Action: Validate
Category: Ergonomics
Problem: If an item is marked as deleted or it is locked a warning should be displayed to inform the user.
Correction result: If an item is marked as deleted or it is locked currently a warning will be displayed to inform the user.
5.1.2.1 Delivery orders
RFR-016481 Correction
Framework: Sales / Inventory
Application: Sales orders
View:
Action: Generate delivery orders with order reference and output delivery slips…
Category: Exception
Problem: An exception occurred posting a generated delivery order detail line of an item of identifier type ‘Serial number without inventory management’ if the serial number was already defined in the sales order detail.
Correction result: From now these delivery order detail lines will be posted as expected.
5.1.2.2 Inventory count
RFR-016481 Correction
Framework: Inventory Management
Application: Inventory counts
View: n.a.
Action: Delete
Category: Exception
Problem: The Delete Button was enabled although the inventory count was not persistent.
Correction result: If the inventory count is not persistent the Delete button will be deactivated as expected.
RFR-016481 Correction
Framework: Inventory management
Application: Inventory counts
View: n.a.
Action: Delete
Category: Unexpected behavior
Problem: If the inventory count contained inventory count lists the deletion must be executed twice. Because first the count lists were deleted but the deletion of the inventory count failed.
Correction result: The inventory count and its count lists can be deleted as expected.
RFR-016481 Correction
Framework: Inventory management
Application: Inventory count lists
View: n.a.
Action: Close inventory count list with serial numbers or unit loads.
Category: Unexpected behavior
Problem: Line items that were not relevant, such as info line items with a serial number or a loading unit, were incorrectly taken into account when the inventory count list was closed, so that final correction postings were incorrect.
Correction result: Line items that are not relevant are no longer taken into account when the inventory is closed, so that no incorrect postings for serial numbers or loading units are made.
RFR-016481 Correction
Framework: Inventory management
Application: Inventory count lists
View: n.a.
Action: Convert loading unit line item into information line item
Category: Unexpected behavior
Problem: The status of the sub line items of a load unit line item has not been changed.
Correction result: The status of the associated sub line items of a loading unit line item is also changed in line with expectations.
5.1.2.3 Inventory postings
RFR-016481 Correction
Framework: Inventory management
(Batch)-Application: Output inventory posting vouchers
View: n.a.
Firm field value assistant
Category: Unexpected behavior
Problem: The firm field value assistant offered all firms although the current user was not authorized to use them.
Correction result: The firm field value assistant will only offer the firms current user is authorized for.
5.1.2.4 Inventory query
RFR-016481 Correction
Framework: Inventory management
Application: Output inventory
View: n.a.
Action: Output immediately or output in batch
Category: Unexpected behavior
Problem: The separated quantity was not displayed in the report and this quantity was also not included in the total quantity.
Correction result: The separated quantity is now displayed and is included in the total quantity.
5.1.2.5 Picking orders
RFR-016481 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Cancel
Category: Invalid data
Problem: Cancelling and recreating a picking order for a delivery order that contains kit detail lines did not work as expected. In special cases, the kit header detail was skipped when recreating the picking order detail for it.
Correction result: From now cancelling and recreating a picking order for delivery orders will work as expected.
Data update: A picking order with lost kit detail headers will be able to get canceled after installing this software update.
5.1.2.6 Receipts of goods
RFR-016481 Correction
Framework: Inventory management
Application: Receipts of goods
View: Purchasing
Action: Post cancellation voucher.
Category: Exception
Problem: If fixed reservations are not available and there is not enough stock of the identifier to be posted for the cancellation voucher, an exception occurs.
Correction result: The posting of the cancellation voucher now behaves as expected.
5.1.2.7 Reservations
RFR-016481 Correction
Framework: Inventory Management
Application: Picking orders
View: Picking
Overreporting of expired batches
Category: Unexpected behavior
Problem: Although the picking order allows the over reporting of expired batches (confirmed warnings) the reservation did not reserve them.
Correction result: The reservation will now accept over reported expired batches. But the automatic reservation will deny expired batches as before and as expected.
RFR-016481 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Reservation of a production receipt
Category: Unexpected behavior
Problem: If the item supports additional item units and units must be rounded some reserved quantities of the receiving stock would not be rounded.
The main reservation quantity (warehouse unit or inventory packaging unit of the item) was correct during the whole process.
Correction result: The additional item units of the reserved quantities will be rounded as expected.
5.1.3 Planning
RFR-016481 Correction
Framework: Production
Application: Generate distribution recommendations
View: n.a.
Action: Generate distribution recommendations
Category: Unexpected behavior
Problem: During “Generate distribution recommendations” action with option “Setting via date” set to “Use execution date”, the offset is added to date from field “By date,” but it should be added to current day date.
Correction result: Now offset is added to current day date.
RFR-016481 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Execute planning
Category: Unexpected behavior
Problem: A production item references material via Bill of material. In case a material position is a production item itself, this is a secondary demand that should be planned after the requesting item so the secondary demand quantity can be increased from the referencing item.
The structure of the item dependencies is analyzed when planning starts.
This analysis did only use the first version of an item production view to determine the BOM to be analyzed to contain secondary demands.
Additionally: Loop detection during this recursion did not always work properly.
Correction result: The dependency structure analysis of production item now considers all versions of the items’ production view.
Hint: The version time boundaries in planning are always determined by the item planning view. The loop detection has been rewritten. It will now log the exact loop contents as errors into the SAS log file.
5.1.4 Production
RFR-016481 Correction
Framework: Production
Process: Reporting the last transport/inventory order (“Lagerauftrag”) for an inventory requisition (“Lageranforderung”) of an equipment instance
Category: Unexpected behavior
Problem: When an inventory requisition for an equipment instance is generated, it can have more than one associated transport/inventory orders.
In this case, completing the inventory requisition by reporting all transport/inventory orders will leave the equipment instance in the “relocation” status, instead of the correct status after relocation.
Correction result: When completing the inventory requisition, the equipment is in the correct status, even if there are multiple transport/inventory orders.
5.1.5 Purchasing
5.1.5.1 Purchase order confirmations
RFR-016481 Correction
Framework: Purchasing
Application: Purchase orders
Action: “Output confirmation reminder”
Category: Invalid data, Unexpected behavior
Problem: The “Confirmation dun” report does not consider correctly the purchase item data (input parameter item is not mapped) – so for example, the external (supplier) item number is not considered.
Correction result: Now the behavior is as expected.
In addition to that, the assignment of the variables that are used for the decimals formatting (amount, duration, price and quantity) have been corrected.
5.1.5.2 Purchase orders
RFR-016481 Correction
Frameworks: Purchasing, Inventory
Applications: Purchase orders, Shipping orders
Action: Save purchase order, Creation of delivery return order
Category: Exception / Invalid data / Unexpected behavior
Problem: Since another correction, the outgoing availability/reservation data will not be created any more if a purchase order line item has a specified dispo quantity for the process “Generate delivery order for return of goods with &inventory posting and output delivery slip”.
Correction result: Now this data will be created as expected.
5.1.5.3 Supplier invoices
RFR-016481 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Self billing
Category: Unexpected behavior
Problem: In contrast to a manual supplier invoice creation the self-billing triggered by receipt booking fails if the main uom is not the base uom and some costing data is present for such an invoice line item.
Correction result: Now the self-billing works as expected in this case as well.
5.1.6 Relationship Management
5.1.6.1 Customizable cockpits
RFR-016481 Correction
Framework: Inventory Mangament
Application: Cockpit: Inventory postings
View: n.a.
Defaults for the posting
Category: Unexpected behavior
Problem: The default for the posting date is “Today” but this default should not always be set.
Correction result: The default for the posting date should not be set if the values warehouse/zone, item, identifier, inventory posting or a loading unit were used as parameter to be overtaken at start.
5.1.7 Sales
5.1.7.1 Order confirmation
RFR-016481 Correction
Framework: Sales
Applications: Sales orders, Confirmations
Action: Create confirmation
Category: Invalid data / Unexpected behavior
Problem: If a sales order has some canceled line items and some of them were already confirmed, the confirmed quantities of these line items will not be set to zero by the confirmation generator.
Correction result: Now the confirmation generator sets the confirmed quantities of canceled sales order line items to zero (as sub step of the activation step).
Data update: If needed you have to correct wrong sales order line items manually by the following steps:
– Remove the cancelation
– Create a new confirmation
– Cancel the line items
– Create a new confirmation again
5.1.8 Storage Location Control
5.1.8.1 Inventory orders
RFR-016481 Correction
Framework: Inventory Management
Application: Picking orders
View: n.a.
Action: Generate inventor orders…
Category: Unexpected behavior
Problem: If a set and its components should be picked from a structured warehouse the generation could be aborted.
Correction result: If a set and its components should be picked from a structured warehouse the inventory order can be generated for the available number of sets.
5.1.8.2 Inventory query at storage locations
RFR-016481 Correction
Framework: Storage Location Control
Application: Inventory postings
View: Inventory postings
Action: Save
Category: Invalid data
Problem: If an inventory posting for an unstructured zone was created and the inventory owner had no stock within this zone but another inventory owner the new incoming stock would be assigned to the wrong inventory owner. Only the zone stock would be wrong all other stocks (warehouse stock, current stock, current unit onhand and the inventory postings) were correct.
Correction result: The inventory posting for an unstructured zone will be processed as expected.
5.2 Comarch Financials Enterprise
5.2.1 Financial accounting
RFR-016481 Correction
Framework: Base
Application: Partners
View: Partner accounting data
Action: validate
Category: Unexpected behavior
Problem: In a bank assignment the format (defined in the application ‘Countries’) of the account number and IBAN number were not validated, if the user did not input a bank but entered an IBAN instead.
Correction result: From now the format of the account number and IBAN number will be validated if the first 2 characters of the IBAN could determine a valid country.
5.3 System development
RFR-016480 Ergonomics
Files of the online help file system have been updated.
RFR-016480 Documentation
The documents “INF-155” and “INF-228” have been updated regarding 6.3 release.
5.3.1 Application server
RFR-016479 Correction
Process: Session management
Category: Unexpected behavior
Problem: Application server might freeze due to a deadlock caused by session management, e.g. by starting a new session while an old one is being invalidated.
(System cockpit shows two deadlock threads, one locks a CisHashMap, one an Object.)
Correction result: Deadlock prevented.
5.3.1.1 Batch
RFR-016479 Correction
Framework: System Management
Executing batch jobs
Category: Unexpected behavior
Problem: A cause for an issue was identified, where batch jobs waiting for other batch jobs or output jobs, did not complete, although the jobs they were waiting fore were already completed. Among other situations the issue could appear case of database connectivity problems, or an OutOfMemory condition in the message server.
Correction result: Stability of a batch service’s system session in the message server was improved.
Technical information: If the system was still running after occurrence of the issue, it could be observed for the message server that a thread “CisBatchServiceImpl$Observer” was no longer present.
5.3.2 Data exchange
RFR-016479 Correction
Framework: System Management
Application: Data exchange log entries
View: n.a.
Action: Open correction application…
Category: Exception
Problem: Imported incorrected data via SOAP could not be processed using the action: “Open correction application…”
Correction result: Imported incorrected data via SOAP can be processed properly using action: “Open correction application…”
5.3.3 GUI
RFR-016479 Correction
Framework: All
Application: Customizable applications
View: MessageGroupViews
Action: n.a.
Category: Unexpected behavior
Problem: Message indicators are not removed, if the message group has been changed.
Correction result: Fixed.
Technical information: Only such UI elements were affected, where the message group is provided by a data view / data object.
5.3.4 Workflow
RFR-016479 Correction
Framework: Workflow Management
Application: Activities
View: n.a.
Action: n.a.
Category: Correction
Problem: If an activity started batch application and the batch job was running for a short time (less than one second or little more), the activity could not change status to “completed” despite the batch job has finished.
Problem occurs if user initiates the process / activity on the same application server the batch job will run. Activity must be created from activity definition with checked option “Wait for batch job to finish”.
Correction result: The activity will change status to “completed” when the batch job will be finished.