| Release | Comarch ERP Enterprise 6.3 |
| Release date | 20.06.2025 |
| 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-016553– RFR-016555
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-Fix23”.
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-Fix23
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix22 will be upgraded to CEE630PB-Fix23.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”.
3.2 Cumulative installation of support deliveries
Code status CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
With the “Query data updates” application, you must schedule the following data updates, for any point in time.
UPDBUG029697
Vertriebsauftragspositionen: Korrigiert falsche „Provisionsfähig“-Werte
Die Anwendung „Vertriebsaufträge“ schränkte die Werte des Positionsattributs „Provisionsfähig“ nicht auf die unterstützten Werte „Nein“ und „Ja, mit Provisionsprozent“ ein; darüber hinaus waren versehentlich auch leere Werte möglich. Diese Update-Anwendung korrigiert die falschen Daten auf den Standardwert „Ja, mit Provisionsprozent“.
5 Contained changes and extensions
5.1 Application development
RFR-016555 Correction
Classes:
– com.cisag.app.inventory.delivery.order.log. OrderDetailValidation
– com.cisag.app.inventory.delivery.order.log.OrderHeaderValidation
– com. cisag.app.inventory.location.log.PickingOrderDetailSource
– com.cisag.app.inventory.location.log. PickingOrderSourcePreloader
– com.cisag.app.inventory.picking.order.log.OrderDetailValidation
– com. cisag.app.inventory.picking.order.log.OrderHeaderValidation
Method: Constructor
Description: The visibility of the constructor is changed from private to protected
5.1.1 Base
RFR-016555 Correction
Framework: Base
Applications: “Cancellation reasons” and “Cancellation Reason Assignment”
View: n.a.
Action: n.a.
Category: Wrong coding
Problem: The default constructor of the class “com.cisag.app.general.log. CancellationReason(Assignment)Entity” does not have a registered validation; only the copy constructor registers the “CancellationReason(Assignment)Validation”.
So in some cases the entity does not have a validation.
Correction result: Now the coding has been changed in analogy to the template coding of the class “com.cisag.app.general.log.LanguageEntity”.
5.1.1.1 Base – General
RFR-016555 Ergonomics
Framework: Base
Application: Countries
Category: Ergonomics
Problem: The popup dialog that belongs to the format definition field does not have a shadow.
Correction result: Now the shadow is used as expected.
RFR-016555 Correction
Frameworks: Purchasing and Sales
Applications: Applications with discount fields
Category: Unexpected behavior / Ergonomics
Problem: If the discount unit (percent, currency or “quantity unit”) contains an invalid value this invalid value will be discarded and changed to a percent without any errror message (e.g. if a new sales order line item was added to an order).
Correction result: Now an error message will be send as expected.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016555 Ergonomics
Frameworks: Purchasing, Sales
Applications: Supplier proposals, Purchase orders, Customer proposals, Sales orders, Distribution orders
Action: Apply defaults
Category: Unexpected behavior / Ergonomics
Problem: If the header currency is invalid an error message will be send in some cases directly after a change of some line item data (e.g. item changed). This message will be send without any context.
Correction result: Now in this case no message will be send. Instead such messages will be send as expected by the relevant validations.
5.1.1.3 Item characteristics
RFR-016555 Correction
Framework: Base
Applications: “Item characteristics” applications
Category: Invalid data / Unexpected behavior
Problem: By mistake more than the assigned “Item characteristics” were conisdered for a “Item characteristic classification” (e.g. also the assignments for the classification “10” if the current classification is “100-100”).
Correction result: Now the expected assignments will be considered.
Data update: To remove the not relevant columns and values you have to execute the “Generate item characteristic” batch application.
5.1.1.4 Items
RFR-016555 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Delete
Category: Exception
Problem: An exception occurred deleting a delivery order that contains detail lines of items of kind SNOB. That is the case if the serial number has already been defined in the sales order.
Correction result: From now deleting a delivery order will work as expected.
RFR-016555 Correction
Framework: General
Application: Items
View: Financials
Action: New version
Category: Exception / Unexpected behavior
Problem: An infinite loop and an exception occurred when the user wanted a (third) item financials data version being created.
Correction result: From now creating new item financials data versions will work as expected.
RFR-016555 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: In the item field of the editor the logic, that calculates the (base) item number from a given customer item number, sometimes failed and delivers more than one number. That could happen if the same (customer) item number was used twice for different items and some of these items were marked as deleted already. The marked items were not filtered then and were part of the result.
Correction result: From now items resp. item data, that is marked as deleted will be filtered of the logic as expected and won’t be part of the result.
5.1.1.5 Number ranges
RFR-016555 Correction
Framework: Sales
Application: Customer invoice types
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: Missing indicator (gray corner) in mandatory field “Number range”
Correction result: “Number range” field now has an indicator.
5.1.2 Calculation
5.1.2.1 Calculation – General
RFR-016555 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: validate position
Category: Exception
Problem: In case the user adds a position to the sales order and the position contains a configurable production item, a price calculation must be performed.
For this a new product cost calculation is created with a new number from a number range.
In case the number range cannot yield a new number, because it overflowed, an exception with a PRD-message was thrown.
Correction result: A COS-message is shown in the case described above, possibly only visible in the configuration dialog.
The application does not stop because of exception anymore.
RFR-016555 Correction
Framework: Calculation
Application: Cockpit: Purchase items, Cockpit: Sales items
View: n.a.
Action: Generate calculations..
Category: Unexpected behavior
Problem: Context: The calculation rule used by performing “Generate calculations…” for a purchasing item has no supplier specified and field “Supplier origin” of this rule is set to “No supplier”. But in dialog of “Generate calculations…” user specifies a supplier. This data is transfered to the calculation process but the value of “Supplier origin” has still value “No supplier” within context of calculation process.
Result: This subsequently may lead to an error (price could not be found) if specified price listing contains no price without specified supplier.
The same behaviour can be found when performing “Generate calculations…” for a sales item.
Correction result: Value of “Supplier origin” in calculation process is changed to “Manually defined supplier” when in dialog of “Gernerate calculations…” a supplier is specified.
A trade cost calculation is properly generated and calculation works as expected bot for purchaing items and sales items.
5.1.2.2 Calculation schemas
RFR-016555 Correction
Framework: Calculation
Application: Trade cost calculation
View: Identification view
Action: Save
Category: Unexpected behavior
Problem: First item unit is not set in Items -> Sales view as a allowed sales item unit (field: “Units”). Then creation of a trade cost calculation for this (sales) item fails, if calculation quantity is set in first item unit. Unit is refused due to error message “SAL 1037”.
Correction result: In above described context first item unit is not refused. It is accepted as expected.
5.1.3 Compliance management
5.1.3.1 Verarbeitungszwecke
RFR-016555 Correction
Framework: Compliance Management
Application: Query processing purpose assignments
Action: Search and record data
Category: Unexpected behavior / Ergonomics
Problems:
1.) Filtering by the field “Reference” does not work as expected.
2.) The record (history) functionality does not work.
Correction result: Now the behavior is as expected.
5.1.4 Inventory management
5.1.4.1 Availability query
RFR-016555 Correction
Framework: Inventory Management
Application: Reorganize availability and demand data
View: n.a.
Action: Execute batach application “Reorganize availability and demand data”
Category: Unexpected behavior
Problem: If a shipping order was already deleted the reorganization of its availability details caused error messages (shipping order not found) in the job log. The reorganization was already successful but the messages should not be created.
Correction result: The availability details of a deleted shipping order will be marked as deleted in future and they can be reorganized as expected.
5.1.4.2 Delivery orders
RFR-016555 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Cancel
Category: Exception
Problem: An exception occurred canceling a delivery order of a distribution order, if a source distribution order detail line is completed manually.
Correction result: Canceling a delivery order of a distribution order will work as expected.
RFR-016555 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: CRUD in tabbed pane “External voucher numbers”
Category: Unexpected behavior
Problem: CRUD actions for external reference numbers didn’t work correctly if more than one number is changed in the table of the tabbed pane “External voucher numbers”
Correction result: From now the CRUD actions for external reference numbers will work as expected.
5.1.4.3 Inventory management – General
RFR-016555 Correction
Framework: Inventory
Application: Reorganize delivery orders
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The direct help text of the application was wrong.
Correction result: From now the direct help text of the application will be correct.
RFR-016555 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.
5.1.4.4 Loading units
RFR-016555 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Create
Category: Unexpected behavior / Ergonomics
Problem: Applying defaults didn’t work as expected. In special cases creating a loading unit with an addded loading unit didn’t take over the abc-classification of the added loading unit.
Correction result: From now applying defaults will work as expected: The abc-classification will be taken over from an new added loading unit if it’s not set already.
5.1.4.5 Picking orders
RFR-016555 Correction
Framework: Sales / Inventory
Application: Sales orders
View: n.a.
Action: Generate picking order
Category: Exception
Problem: An exception occurred creating a picking order for a sales order. This happens if the sales organization of the sales order is not an inventory organization and empties line items will be created in the delivery process.
Correction result: From now creating a picking order for a sales order will work as expected.
RFR-016555 Correction
Framework: Production
Application: Order mainenance
View: n.a.
Action: Complete, Reschedule
Category: Unexpected behavior
Problem: A production order uses a order type with overpicking allowd. This production order is dispatched multiple level and some sub orders are generated. A sub-order is completed (without any reporting or with reporting partially).
After rescheduling (without change of order quantity) is performed, picking status of material may change from “Picking order unnecessary” to “No picking in progress”. Also quantity to be picked may change to a value greater zero.
As a result of this status change subsequent rescheduling actions (without change of order quantity) fail due to error PRD-1107.
Correction result: Picking status of a completed sub-order as described above remains unchanged after rescheduling of main order without change of order quantity. Also related value of quantity to pick remains zero. Rescheduling can be repeated and works as expected.
5.1.4.6 Receipts of goods
RFR-016555 Correction
Framework: Inventory
Application: Goods receipts
View: Distribution
Action: Post receipt of goods…
Category: Unexpected behavior
Problem: A goods receipt was not be able to get posted if a detail line is delivered in multiple seperated inventory identifiers and a cost objective is needed for posting.
Correction result: From now posting a goods receipt will work as expected in that case.
RFR-016555 Correction
Framework: Inventory
Application: Delivery orders, goods receipts
View: n.a.
Action: Post receipt of goods …
Category: Unexpected behavior, Invalid data
Problem: Posting a goods receipt for distribution was not possible because INV-09251 was displayed. That was the case if more than one receipt detail line for one delivery detail line was needed, because the delivery was executed with in more than one inventory unit of measure.
Correction result: From now goods receipt will be able to get posted as expected.
Data correction: The (not postable) goods receipt has to be deleted and, moreover, the delivery order has to be canceled and the delivery has to be created again.
5.1.4.7 Reservations
RFR-016555 Correction
Framework: Inventory Management
Application: Reservations
View: n.a.
Execution of actions that based upon data that was changed in the meantime
Category: Exception
Problem: If a demand (origin or coverage) was selected to be updated for a reservation action an exception could be caused if the database object was deleted by an other process or user.
Correction result: The actions were extended to be safer against concurrent changes. Often there will be a message that informs the user about changed data as expected.
5.1.5 Multi-site capability
5.1.5.1 Inter-company billing
RFR-016555 Correction
Framework: Base
Application: Inter-company billing
Action: Create summary invoice
Category: Invalid data / Unexpected behavior
Problem: If a “Inter-company billing” is created as “summary invoice” the customer invooice line item “cost of goods” value was not determined as expected (with the wrong quantity).
Correction result: Now the “cost of goods” value will be determined as expected.
Data update: If needed you can cancel the wrong Inter-company billing invoices and recreate them with the corrected coding.
RFR-016555 Correction
Framework: Base
Application: Inter-company billing
Action: Create “Inter-company billing”
Category: Exception Unexpected behavior
Problem: By the customer invoice type the functionality “Clear billing line item internally” can be activated. If so the “Inter-company billing” generation tries to refresh the status of the original sales order detail (with quantitiy zero) because within the internal billing data as “order” the original sales order detail is used. If this detail is canceled an exception occurs; if it is not canceled it works as expected randomly. For the sales order detail such an “Inter-company billing” is not relevant for the internal billing status – so the “Inter-company billing” generation must not refresh the sales order detail status (also if not canceled).
Correction result: Now the “Inter-company billing” generation does not refresh the sales order detail if the original sales order detail has the total quantity zero.
In analogy also no status update will be performed if the original order detail is a purchase order detail with the total quantity zero.
Hint: Can currently not occur because in purchasing the invoice header will be used as “order” within the internal billing data.
5.1.6 Planning
RFR-016555 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Update planning data and execute planning
Category: Unexpected behavior
Problem: The planned item needs to have forecasts and planning time fence bigger than 0 . In “Material requirements planning” option “Forecasts in time fence” needs to be disabled. Then full transfer and planning needs to be done via action “Transfer planning data and execute planning”.
After changing value of time fence and then performing action “Update planning data and execute planning” the forecast distribution was not changed and therefore the demand from them was also not changed leading to wrong recommendations.
Correction result: Now forecast distribution is properly updated via action “Update planning data and execute planning” if value of planning time fence has been changed for any of the planned item.
5.1.6.1 Generate purchasing recommendations
RFR-016555 Correction
Framework: Planning
Application: Generate purchasing recommendations / Generate distribution recommendations / Generate production recommendations
View: n. a.
Action: Generate purchasing recommendations / Generate distribution recommendations / Generate production recommendations
Category: Unexpected behavior
Problem: When generating multiple recommendations via batch job, with start: scheduled, it was possible that multiple recommendations for the same items where generated, when the batch jobs where activated at the same time in Cockpit: batch jobs.
Correction result: Only one recommendation will be created, even if multiple batch jobs for the same planning/item are activated at the same time.
5.1.7 Production
RFR-016555 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Changing quantity of line item to negative value changed detail’s status to “completely reported” and display an error that says negative quantities are forbidden. This led to make quantity field not editable and thus make it impossible to correct this error without refreshing entire production order.
Changing quantity of line item to zero then validating without saving and changing this quantity again to the same or less value than the original one caused the field to become non-editable and the status of this line item to be incorrectly set to “completely reported”.
Correction result: Changing quantity of line item to negative value doesn’t made the field non-editable and displayed error can be correct without refreshing entire production order.
Changing quantity of line item to zero then validating without saving and changing this quantity again to the same or less value than the original one, sets the correct detail’s status and editability of this field.
RFR-016555 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: New material provided to vendor, Dispatch sub order of an cross-site operation
Category: Exception
Problem: Both problems happened when distribution order related to cross-site operation is deleted.
1. When trying to add new material provided to vendor to that cross-site operation, an exception occured.
2. When trying to dispatch sub order of that cross-site operation and at least one material provided to vendor of that operation is not present in dispatched bill of material then an exception occured.
Correction result:
1. Adding new material provided to vendor is now not possible for cross-site operations which distribution order was already deleted.
2. An exception do not occur anymore in described situation.
RFR-016555 Correction
Framework: Production
Application: Cockpit: Equipment history, Cockpit: Equipment, Cockpit: Initialize equipment, Cockpit: Equipment-related requirements, Cockpit: Equipment reservations, Cockpit: Equipment utilization, Equipment, Service bills of material, Reorganize service bills of material
View: n.a.
Action: n.a.
Visibility of aforementioned applications
Category: Unexpected behaviour
Problem: The concerned apps where displayed for users that had the functions “Equipment” or “Service bill of material” (apps “Service bills of material” and “Reorganize service bills of material”) turned off in customizing.
Correction result: The applications are not displayed anymore if their function is turned off in customizing.
RFR-016555 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch, Recalculate due date and quantity
Category: Unexpected behavior
Problem: When operation with multiple resources without any dependencies between them is scheduled or rescheduled the logic tries to set each resource to start at the same time. When those resources uses different week models and there is no common begin for them possible then some of them are scheduled/reschudeled wrongly (for forward scheduling too far into the future, for backward scheduling too far into the past).
Correction result: Now if resources has not any common begin possible during scheduling/rescheduling they are scheduled properly based on scheduling type so final dates of resources are now not too far into the future/past.
RFR-016555 Correction
Framework: Production
Application: Import data / operation postings
View: n.a.
Action: import
Category: Unexpected behaviour
Problem: When importing a operation posting of type BEGIN, using “normalized form” as time format, an exception occurred, causing the import to fail (even though the time was formatted correctly in the XML source).
Correction result: The import of the operation posting works now with using the “normalized form” time format, as intended.
Technical information: Technically, changing the create() method in com. cisag.app.production.log.OperationPostingDataCollectionLogic counts as an incompatible change. Because the method wasn’t called from anywhere, this doesn’t pose a problem.
5.1.7.1 Product configuration
RFR-016555 Correction
Framework: Sales, Production, Calculation
Application: Sales Orders
View: all
Action: Validate or Accept position in position editor
Category: Ergonomics
Problem: Validating or accepting a sales order position whose production item has an attached product configuration that includes a Product cost calculation, produces an error message, if the total quantity of the sales order position cannot be converted to the base unit of the item without loss.
This error message is very difficult to interpret for the user since it is very generic and is displayed in the product configuration dialog without any connection to the position quantity or the product calculation.
Correction result: Additional error messages are added that explain what the problem exactly is and where it is caused.
5.1.7.2 Production – General
RFR-016555 Correction
Framework: Production
Application: Order maintenance
View: n.a.
Action: Dispatch…
Category: Unexpected behavior
Context: ———-
Master data versioning is active. A product P uses a bill of resource (BOR). BOR is released. A new version of bill of material (BOM) which is used by BOR is created and released. The new version of BOM contains a new material. BOR remains untouched. That means: BOR keeps a reference to the now expired version of BOM.
Problem: ———-
— Dispatching —: Now a production order with product P is created and dispatched.
Result: Each material of old version of BOM is created twice during dispatching process.
This behaviour also occurs for sub orders when dispatching multiple level and a semi-finished product SP uses a BOR/BOM combination as described above.
— Application “Process maintenance” —:
1. The bill of resource BOR as described above is displayed via application „Bill of resources“.
If toggle button „Non-assigned material“ is clicked all materials of referenced bill of material are displayed as not assigned. This is not correct.
2. If a new version of BOR is created and released via application „Bill of resources“ the versions of the referenced BOM and routing unfortunately are not updated to the now new released versions of BOM/routing.
The values of the versions are the same as on original creation of BOR. This is not correct.
3. After new version is created clicking toggle button „Non-assigned material“ still shows all material of referenced bill of material. If button „Assign material“ is clicked all material of referenced bill of material can be assigned. This is not correct.
Correction result: ——————–
— Dispatching —: In the course of dispatching it is proved, if used BOR references a bill of material with an expired version. If this is the case a warning is output like: “Bill of resource BOR uses a bill of material BOM. This is expired or status is invalid.” Due to this warning dispatching is stopped.
If user confirms this warning dispatching will be performed using the expired bill of material as referenced in bill of resource BOR! Material due to BOM is not doubled.
Nevertheless as a consequence of creating a new version of a bill of material is that each bill of resource using this bill of material must be changed. That is: a new version of this bill of resource must be created and changes of bill of material must be regarded adequately before releasing.
In order to support the same behaviour for bill of material and routing the correction is also extended for routings. That is: In the course of dispatching it is proved, if used BOR references a routing with an expired version. If this is the case a warning is output like: “Bill of resource BOR uses a routing AP. This is expired or status is invalid.” Due to this warning dispatching is stopped.
If user confirms this warning dispatching will be performed using the expired routing as referenced in bill of resource BOR!
It is also a consequence of creating a new version of a routing that each bill of resource using this routing must be changed. That is: a new version of this bill of resource must be created and changes of routing must be regarded adequately before releasing.
— Application “Process maintenance” —:
1. Bill of resource BOR is displayed with correct versions of referenced bill of material and routing. This reference versions may be expired! This is a possible and correct situation as released BOR cannot be changed anymore. If toggle button „Non-assigned material“ is clicked only material of referenced bill of
material and version which is not yet assigned is displayed as not assigned.
Warnings are displayed on loading a bill of resource with status released, in process or in approval if it uses a expired bill of material or routing.
2. If a new version of BOR is created bill of material and routing are referenced with their released versions and the new version of BOR is updated with this versions correctly.
3. If toggle button „Non-assigned material“ is clicked at new version of BOR only material of referenced bill of material which is not yet assigned is displayed as not assigned. And this not yet assigned material may only result from new material of new version of bill of material. If button “Assign material” is clicked only this material shows up in assignment dialog.
Additional of 2: If at time of creation of new version of BOR no released version of bill of material is available (possibly blocked) then creation of new version fails with an proper error message.
This goes also for routing if no released one can be found.
5.1.7.3 Production orders
RFR-016555 Correction
Framework: Production
Application: Production orders / Import data
View: n.a.
Action: Import data
Category: Unexpected behaviour
Problem: When a production order with production order details (any kind of operation or resource reservation) that had added parameters was imported, those parameters were lost during the import.
Correction result: Parameters are now imported correctly according to the documentation: they can be edited and imported, but it is still not allowed to add new parameters to a production order detail in a production order.
5.1.7.4 Production plans
RFR-016555 Correction
Framework: Production
Application: Bills of resources
View: Bill of resources
Action: Non-assigned material
Category: Exception
Problem: Load any existing Bill of resources. Change “Bill of material” field to invalid one and validate. In result you should got an error about wrong bill of material. Press list button “Non-assigned material” to activate it. Exception occured and application crashed.
Correction result: In the described situation the exception does not longer occur. Instead the message about wrong Bill of material is displayed(the same one which was displayed after validation).
Additionally now all list actions perform validation when pressed and if validation failed the action is not performed.
5.1.8 Purchasing
5.1.8.1 Bonus agreements
RFR-016555 Correction
Framework: Purchasing, sales
Application: Purchasing bonus agreements, sales bonus agreements
View: n.a.
Action: display of fields and tables
Category: Unexpected behavior
Problem: After changing the bonus agreement status become the related visual elements such as fields and tables invalid and that is incorrect, they should become read-only.
Correction result: The problem is fixed, now all the affected visual elements such as fields and tables are correctly displayes(read-only).
5.1.8.2 Puchasing – General
RFR-016555 Correction
Framework: Purchasing
Applications: “Assign supplier invoices” and “Assign receipts of goods”
Action: Sort order
Category: Unexpected behavior / Ergonomics
Problem: The sort order as stored within the “Standard” layout of these applications was not well defined.
Correction result: Now the sort order is defined so:
1.) “Assign supplier invoices”: Receipt date (descending); all further attributes ascending: receipt line item (type code, header number, main and sub line item number), purchasse order line item (type code, header number, main and sub line item number)
2.) “Assign receipts of goods”: Invoice date (descending); all further attributes ascending: invoice line item (type code, header number, main and sub line item number), purchasse order line item (type code, header number, main and sub line item number)
5.1.8.3 Purchase order confirmations
RFR-016555 Correction
Framework: Purchasing
Applications: “Cockpit: Purchase order confirmations” and “Cockpit: Purchase order confirmations/line items”
Category: Unexpected behavior / Ergonomics
Problem: The field “Confirmation number” does not have a value assistant.
Correction result: Now the field has the expected value assistant.
5.1.8.4 Purchase orders
RFR-016555 Correction
Frameworks: Production, Purchasing
Applications: Production orders, Purchase orders
Action: Complete production order
Category: Exception
Problem: If a production order has a purchase order reference (“External manufacturing”) and the purchase order is marked for reorganization the “Complete production order” fails with an UnsupportedOperationException.
Correction result: Now the exception does not occur any more.
5.1.8.5 Supplier invoices
RFR-016555 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Change view
Category: Unexpected behavior / Ergonomics
Problem: If the view is changed manually by the line item data will not be cleared (in contrast for example to the receipt maintenance).
Correction result: Now the data will be cleared as expected.
RFR-016555 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Generate correction supplier invoice
Category: Exception
Problem: If the purchasing organization of a supplier invoice and the purchasing organization of an assigned purchase order are different and have different domestic amount combinations an exception occurs during the try to perform the “Generate correction supplier invoice” logic.
Correction result: Now the exception does not occur any more.
5.1.9 Sales
5.1.9.1 Customer returns
RFR-016555 Correction
Framework: Inventory
Application: Customer return
View: n.a.
Action: Generate pickup orders…
Category: Exception
Problem: There was a problem if ‘Payment partner’ is selected as partner usage in the ‘Prices’ function in customising application and no payment partner is entered in the customer. An exception was thrown when a pickup order was generated.
Correction result: From now generating pickup orders will work as expected.
5.1.9.2 Sales – General
RFR-016555 Correction
Framework: Sales
Applications: “Order confirmations query” and “Pro forma invoices query”
Action: Generate
Category: Invalid data / Unexpected behavior
Problem: In the “Net” price display, the header discount values of the line items are by mistake the double of the correct value.
Correction result: Now the header discount values have the expected values.
Hint: Please note that in contrast to the “Net” price display of customer invoices the discount values are not cleared (as before).
5.1.9.3 Sales orders
RFR-016555 Correction
Frameworks: Sales, Purchasing
Applications: Sales orders, Purchase orders
Action: Validate, Complete delivery manually, Remove manual completion of delivery
Category: Exception / Unexpected behavior
Problem: If a purchase order was created by a sales order the purchsae order might be reorganized in some cases. Up from this point the sales order line item can not be changed any more because of error messages or exceptions. Also the actions “Complete delivery manually” and “Remove manual completion of delivery” were not possible – so there might exist cases were such sales order line items can not be completed manually any more.
Correction result:
1.) The sales order line item data that is relevant for the update of a purchase order line item can not be changed any more if the purchase order line item is reorganized. Instead of an exeption now an erorr message will be send now by the sales order line item validation.
2.) The sales order line item actions “Complete delivery manually” and “Remove manual completion of delivery” can now be performed also if a referenced purchase order line item is not present any more.
RFR-016555 Correction
Framework: Sales
Application: Sales orders
Action: Validate, Save
Category: Exception / Invalid data / Unexpected behavior / Ergonomics
Problem: The application “Sales orders” did not restrict the values of the line items attribute “Commissionable” to the supported values “No” and “Yes, with commission percent”; in addition to that also empty values were displayed by the field. If a line item contains the value “Yes, with commission percent” an exception occurs during the try to duplicate such a line item.
Correction result: Now only the supported values can be used/saved. Also the field is now marked as required so that the empty value will not be displayed any more by the field.
Data update:
Please execute the data update application UPDBUG029697 to correct the wrong data. It will set wrong values to the default value “Yes, with commission percent”.
RFR-016555 Correction
Framework: Sales
Applications: “Customer proposals” and “Sales orders”
Action: Recalculate
Category: Exception
Problem: If a customer proposal or sales order calculates tax data and uses freight costs or empties an exception can occur during the try to recalculate the order.
Correction result: Now the exception does not occur any more.
Hint: In addition to that a wrong condition for “relevant header change” have been correct within the “document freight cost logic”.
5.1.10 Storage Location Control
5.1.10.1 Inventory management server
RFR-016555 Correction
Class: com.cisag.app.inventory.location.cache.data. SlotOnhand
Method: com.cisag.app.inventory.location.cache.data.SlotOnhand. registerDetailOnhand(DetailOnhand)
Description: The registration or deregistration of a DetailOnhand key must be unique. Because of that the internal key list is changed to an internal key set.
5.1.10.2 Inventory order types
RFR-016555 Correction
Framework: General
Application: Items
View: Item base
Action: Update
Category: Invalid data
Problem: It was possible to manipulate the item packaging units of measure of an item in a kind, that existing picking orders and delivery orders would get invalid.
Correction result: From now the item validation will prohibit these changes of the item packaging units of measure.
5.1.10.3 Storage locations
RFR-016555 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Import of new picking location and item definitions
Category: Unexpected behavior
Problem: If a new picking location or item definition was imported the validations would not be sufficient.
Correction result: The storage location validations will be done during the import as expected.
5.2 System development
RFR-016553 Correction
Framework: All
Action: copying NLS Data
Category:Unexpected behavior
Problem: If a two transient instance of business object both containing supplement are copied into each other and the supplement has an NLS attribute,
then it can happen that a previously set value for a secondary language is lost on copy.
Correction result: the copy process now works as expected for NLSData of a supplement.
Technical information: NLSData are only loaded if needed. In order to know what to load a key is copied.
RFR-016553 Correction
Framework: All
Application: Info dialog
Category: Ergonomics
Problem: The info dialog does not correctly display whether an App is active or not.
Correction result: Now the display is correct.
RFR-016553 Correction
Framework: Document management
Application: Documents
View: n.a.
Action: Mail merge
Category: Unexpected behavior
Problem: The value for template “Document number” is empty.
Correction result: Fixed.
RFR-016553 Correction
Framework: System Management
Application: Software updates cockpit
View: Imported Software updates
Action: Install.
Category: Unexpected behavior
Problem: If an installation was started within the software update cockpit and only language refreshes are installed,
then the end trigger for the installation was not reached.
This kept the installation open. This lead to problems for the next regular installation.
Correction result: When using the ‘Install’ action the installation is now correctly marked as finished in the end.
RFR-016553 Correction
Framework: com.cisag.pgm.SystemManagement
Application: com.cisag.sys.tools.bi.ui.ExportMaintenance/com.cisag.sys.tools.bi.ui.ImportMaintenance
View: n.a.
Action: creating the object info
Category: Unexpected behavior
Problem: In class DefaultObjectInfo, method makeDependent there was a fault concerning the source attributes.
When building a new AssociationDescriptor the targetAttributes were set into the source attributes.
This could lead to a problem if the names are validated and the attribute names of source and target in a relationship are different.
Correction result: Now the source attributes are set correctly.
Technical information: In most cases the names of the attributes are not used. Only if there is an explicit validition built.
5.2.1 GUI
RFR-016553 Extension
Framework: All
Application: All
View: n.a.
Action: User menu
Field/Column: n.a.
Category: New dockable view
Description: If navigation mode “Tabs” is enabled in user settings, the “User menus” are available as a new dockable view.
RFR-016553 Correction
Framework: All
Application: All
View:All
Action: n.a.
Category: Unexpected behavior
Problem: Changing the “Density” in the user settings was sometimes not completely applied in the browser (due to the browser cache).
Correction result: Fixed
RFR-016553 Extension
Framework: All
Application: All
View: n.a.
Action: Save window layout
Field/Column: n.a.
Category: UX
Description: The (collapsed/expanded) state of the left navigation bar (CDS theme with navigation mode “Tabs”) is now saved in the window layout.
RFR-016553 Correction
Framework: All
Application: All
View: n.a.
Action: n.a.
Field/Column: n.a.
Category: UX
Description: Navigation mode “Tabs” (CDS theme) now provides “Back” and “Next” buttons.
RFR-016554 Extension
Framework: All
Application: All
View: n.a.
Action: User menu
Field/Column: n.a.
Category: New dockable view
Description: If navigation mode “Tabs” is enabled in user settings, the “User menus” are available as a new dockable view.
5.2.1.1 Client (browser)
RFR-016553 Correction
Die Erkennung der Touch-Fähihkeit des Klients wurde verbessert. Jetzt wird die nicht aufgrund User-Agent, sondern aufgrund der Erkennung des Touch Event Handlers gemacht.
5.2.2 Kernel
5.2.2.1 Locking / Caching
RFR-016553 Correction
Process: Locking
Category: Exception
Problem: A NullPointerException (at com.cisag.sys.kernel.locking.CisLockTable.removeLockEntryByRequester) might occur randomly, if two or more requesters are waiting to acquire the same lock and a timeout occurs.
Correction result: Fixed.
5.2.3 Repository
5.2.3.1 Tools
RFR-016553 Correction
Framework: Software Development
Tool shell command crtdv
Category: Unexpected behavior
Problem: The Access java class generated for a data view contains a syntax error, if JavaDoc for a mutable relation is specified in the data view development object.
Correction result: The problem is resolved, the generated class can be compiled.
5.2.4 System – General
RFR-016553 Correction
Framework: All
Application: All
View: n.a.
Action: Jump list
Field/Column: n.a.
Category: UX
Description: The number of entries have been increased from five to ten (as documented). Also scrolling is enabled, if the available height is not sufficient.
5.2.5 Workflow
RFR-016553 Correction
Framework: Workflow
Application: Cockpit: Prozesse/OLTP-Datenbank
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Cockpit lists processes with duplicated rows. It happens when a start activity has multiple attachments.
Correction result: one process – one row.
RFR-016553 Correction
Framework: Workflow
Application: ServiceClient
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: If the encoding is not specified in the xml file, the current implementation of the ServiceClient will produce xml in ISO-8859-1 string format.
The xml parser does not understand this format.
Correction result: The ServiceClient produces a string in the default format, regardless of whether the encoding format is written or not.
RFR-016554 Correction
Framework: Workflow
Application: Cockpit: Prozesse/OLTP-Datenbank
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Cockpit lists processes with duplicated rows. It happens when a start activity has multiple attachments.
Correction result: one process – one row.