| Release | Comarch ERP Enterprise 6.3 |
| Release date | 09.01.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-016412– RFR-016414
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-Fix03”.
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-Fix03
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix02 will be upgraded to CEE630PB-Fix03.
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 data updates have to be carried out.
5.1 Application development
RFR-016414 Correction
Framework: Inventory
Application: Calculate inventory allocation
View: n.a.
Action: Create inventory allocation
Category: Unexpected behavior
Problem: In special cases the inventory allocation process did not assign a quantity greater than zero for detail lines which are already fixed reserved.
Correction result: From now detail lines which are already fixed reserved will get the fixed reserved quantity assigned as minimum.
RFR-016414 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Load
Category: Exception
Problem: A NullPopinterException occurred reloading a loading unit that was already displayed in the application after deleting an order detail line in an other session that was referenced by the application.
Correction result: From now the exception will not occur in that case. An error message will be displayed instead.
RFR-016414 Correction
Framework: Base
Application: Items
View: Sales
Action: Tab Action “Statistics”
Category: Exception
Problem: An exception occurred pressing the tab action “Statistics” if the function “Data Warehouse and statistics” is disabled in the application “Customizing”.
Correction result: From now the tab action “Statistics” will be disabled too, if the function “Data Warehouse and statistics” is disabled in the application “Customizing”.
RFR-016414 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Entering a new external manufacturing operation or multi-site production operation
Category: Exception
Problem: If a blocked external operation is to be added to the production order, no unit of measure is preassigned. If a quantity is then entered without a unit of measure and the item is validated/accepted, an NPE is created.
Correction result: If a blocked external operation is to be added to the production order, no unit of measure is preassigned. If a quantity is then entered without a unit of measure and the item is validated/accepted, corresponding error messages appear.
RFR-016414 Correction
Framework: Inventory management
Application: Reorganize Availability and Requirement Data
View: n.a.
Action: Execute
Category: Ergonomics
Problem: In the case of an error, no meaningful message was output.
Correction result: Messages have been improved and the logic has been made more robust with regard to erroneous data.
RFR-016414 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: When saving a production order after changing the beginDate of a production order detail of type operation in the editor, the begin and end date of the production order header are changed accordingly. Change of end date must also change the availability of product of poduction order. This does not happen.
Correction result: When saving a production order after changing the beginDate of a production order detail of type operation in the editor, availability of product of production order is changed accordingly.
RFR-016414 Ergonomics
Update of the Polish user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
5.1.1 Base
5.1.1.1 Base – General
RFR-016414 Extension
Classes: “com.cisag.app.general.order.ui. AbstractOrderEntityMaintenance” and “com.cisag.app.general.ui. SingleObjectTableEditorMaintenance”
Description:
1. Both classes have as innerclass the annotation ResizableEditor. This annotation is now marked as deprecated and will be deleted in a future release. The annotation is not used/needed any more because now it will be assumed that this annotation is present – so a “split pane” will be present always (in case of the order application only if a line item table and editor is present).
2. All concrete standard classes have been changed so that they do not contain the ResizableEditor annotation anymore.
RFR-016414 Correction
Class: com.cisag.app.general.ui. SingleObjectTableMaintenance
Category: Unexpected behavior
Problem:
If a concrete sub class uses the annotation “com.cisag.app.general.ui.UseSingleObjectViewAttributes” and an own field is used (e. g. because multiple key member: “SingleObjectTableMaintenance.MainBusinessKeyAttributeEditorFactory. BusinessKeyEditor) the key field was not changed to “read only” in case of persisent instances (in contrast to the case with the “ExtendedEditor”).
Correction result: Now also in this case the field will be changed to “Read only”.
RFR-016414 Extension
Framework: Base
Application: Voucher document templates
View: n.a.
Action: n.a.
Field/Column: Business object
Category: New field
Description: Using this Business object field to define a variable of a business object attribute.
For example:
Business object field: com.cisag.app.sales.obj.Confirmation
Variable: {BO.number} for attribute number.
For document output: this variable will be filled automatically with the attribute number of the instance of com.cisag.app.sales.obj.Confirmation.
RFR-016414 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Replenishement inventory orders suggest pick locations
Category: Unexpected behavior
Problem: If the warehouse structure observation “Cross-warehouse zones” is selected from a storage strategy a replenishment inventory order could suggest picking locations to replenish a picking location.
Correction result: Replenishment inventory orders will never suggest picking locations to be used as replenishment source.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016414 Extension
Classes: Mutable…Detail(Logic)
Method: prepareValidate()
Description: The following Mutable…Detail classes have a “prepareValidate()” method. Before this change the implementation of this method was directly in the Mutable…Detail class. Now the implementation is moved to a new protected method within the relevant Mutable…DetailLogic class: Changed classes:
– com.cisag.app.multiorg.order.log.MutableOrderDetail(Logic)
– com.cisag.app.purchasing.order.log.MutableOrderDetail(Logic)
– com.cisag.app.purchasing.proposal.log. MutableProposalDetail(Logic)
– com.cisag.app.sales.order.log.MutableOrderDetail(Logic)
– com.cisag.app.sales.proposal.log.MutableProposalDetail(Logic)
– com.cisag.app.sales.rapid.log. MutableRapidDocumentDetail(Logic)
RFR-016414 Correction
Frameworks: Production, Purchasing, Sales
Applications: Production orders, Supplier contracts, Purchasing RFQs, Purchase orders, Supplier invoices, Customer contracts, Sales quotations, Sales orders, Customer returns, Distribution requests, Distribution orders, Down payment requests, Debtor credits
Action: Maintain “Output settings”
Category: Unexpected behavior
Problem: If the “Output settings” data is extended by a supplement the coding before this correction did not work as expected.
Correction result: Now the coding has been changed so that now the “Output settings” data can be extended by supplements.
Technical information: Please note that the method “com.cisag.app.general.log.DataViewUtility.createManipulatedDataView(V, Map)” does not work as expected in all cases (like here). So it is set now to “deprecated” and will be deleted in a future release.
In addition to that, the class “com.cisag.app.multiorg.request.gui.factories. DistributionRequestOutputSettingsEditor” is now marked as deprecated and not used anymore. Use “com.cisag.app.multiorg.request.gui.factories.OutputSettingsEditor” instead.
5.1.1.3 Items
RFR-016414 Correction
Framework: Base
Application: Partners
View: Base, Customer, Supplier, Marketing, Employee, Financials Data
Action: Remove future version
Category: Unexpected behavior, (invaid data)
Problem: The application did not delete the entity extension data of a future version of the listed data above if the future version was removed from database.
Correction result: From now the entity extension data will be deleted as expected.
RFR-016414 Correction
Framework: Base
Application: Import data
Filter: com. cisag.app.general.obj.Item
Action: Import
Category: Unexpected behavior
Problem: The item hook com.cisag.app.general.item.hook.log.ApplyReferenceItemHook was not being called when importing item variants. In addition, it was observed that when called, user input in an item extension (supplement) was already overwritten by the reference article.
Correction result: From now the hook com.cisag.app.general.item.hook.log.ApplyReferenceItemHook will be called from the import controller when importing item variants. Moreover extension attributes will not be copied from reference item to variant item before calling this hook.
RFR-016414 Correction
Class: com.cisag.app.general.item.log. ItemEntity
Method: changePoolOrganization(short, byte[])
Description: The method is set to @deprecated and could not longer be supported. It was former used to change the organization context during the import process for items to check purchasing data.
Class: com.cisag.app.general.item.log.ItemPlanningValidation
Method: checkItemRolesForMakeOrBuy(ItemEntity, ItemPlanningData)
Description: The method will not longer check if the item has purchasing data for the defined purchasing organization in the field com.cisag.app.inventory.obj. ItemPlanningData:purchasingOrganization.
RFR-016414 Correction
Framework: Base
Application: Import data (with application “Items” as correction application)
View: n.a.
Action: Import (with correction application)
Category: Exception / Ergonomics
Problem:
1. The correction application (“Items”) did not signalize, that the imported data is changed or not persistent after taking the data from error file. Therefore no warning message was displayed when using the organization selector to perform the load action.
2. When the application “Items” was started as a correction application an exception occurred pressing the validate-button after changing the organization context via the organization selector.
Correction result:
1. From now the correction application (“Items”) will signalize, that the imported data is changed or not persistent after taking the data from error file. A warning dialog will be displayed that data will get lost when using the organization selector.
2. After using the organization selector to change the organization context in the correction mode, the application will exit the import process and switch to the normal mode.
RFR-016414 Correction
Framework: Base
Business Entity: com.cisag.app.general. obj.ItemTemplate
Category: ‘New field’
Description: From now it will be possible to use the business entity ‘com.cisag.app.general.obj.ItemTemplate’ as type creating a new entity extension field.
RFR-016414 Correction
Framework: Base
Application: Import data
Filter: com. cisag.app.general.obj.Item
Action: Import
Category: Unexpected behavior
Problem: The import controller ignored the customizing configuration of the field ‘Utilization status’ of the function ‘Item’ when the controller created variants from a reference item.
Correction result: From now the import controller will work as expected and will set the status of variants as defined.
RFR-016414 Correction
Framework: Base
Application: Items
View: Supplier data
Action: n.a
Category: Exception
Problem: After using the ‘Next’ (F8) – or ‘Back’ (F7) – button after changing the organizational context with the organization selector an exception could occur.
Correction result: From now using the ‘Next’ (F8) – or ‘Back’ (F7) – button will work as expected.
5.1.1.4 Partner templates
RFR-016414 Correction
Framework: Base
Application: Partner-Templates
View: Finance
Action: n.a.
Category: Exception
Problem: In special cases an exception occurred switching from base data view to the financials data view.
Correction result: From now it will work as expected.
5.1.1.5 Partners
RFR-016414 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.
RFR-016414 Correction
Framework: Base
Application: Partners
View: Base
Action: Executing locator search
Category: Exception
Problem: An exception is thrown executing the locator search of the the application “Partners” during the configuration process for a new OLTP. This could happen if the the organization hierarchy was not yet defined and the function “Phonetics” was available.
Correction result: From now the locator search will work as expected.
RFR-016414 Correction
Framework: Base
Application: Partners
View: Base data
Action: n.a.
Field/Column: Country of the place of birth
Category: Changed field
Description: From now the field will neither be displayed in the standard UI layout nor it will be part of the available import/export data.
RFR-016414 Correction
Framework: Base
Application: Partners
View: Base data
Action: Mark as deleted
Category: Invalid data / Unexpected behavior
Problem: It was possible to mark the partners base data as deleted although a partner has employee data, that was used somewhere, i.e. in item planning data.
Correction result: From now it will not be possible to mark the partners base data as deleted in that case.
5.1.1.6 Shipping terms
RFR-016414 Extension
Frameworks: General, Purchasing, Sales
Applications: Shipping terms, Freight costs, Purchasing RFQs, Supplier quotations, Purchase orders, Distribution orders, Sales quotations, Sales orders, Customer return types, Customer returns
Action: “Apply defaults”, validation, “Change delivery data”
Category: New shipping terms attribute and logic
Description:
– The “Shipping terms” has now a new carrier attribute. If a carrier is specified, such a shipping term can be used only in combination with the specified carrier.
Please note that a carrier can be specified only for a “Shipping terms” if both values are used in the listed applications always in the combination to be saved.
– The new attribute will be considered by all of the listed applications (UI and logic).
Hint: For the “Freight costs” application the three views “Carrier”, “Carrier + Customer” and “Carrier + Freight cost classification” are relevant.
– If the application provides the action “Change delivery data” also this action considers the new rules.
Data update: All existing shipping terms will be initialized with an empty carrier.
5.1.1.7 Text modules
RFR-016414 Correction
Framework: Base
Application: Reorganize text
View: n. a.
Action: Reorganize
Category: Exception
Problem: Running the application an exception occurs.
Correction result: From now the application will work as expected.
Technical information: In release CEE 6.2 general text and text codes are splitted into different business objects. In release CEE 6.3 the @deprecated (no more needed) attributes of the business object com.cisag.app.general.obj.Text have been deleted. The occurered exception was the result of a usage of one of the deleted attributes in the reorganization code.
5.1.2 Calculation
5.1.2.1 Cost centers
RFR-016414 Correction
Framework: Financials
Application: Cost unit rates
Action: Editor: “New, “New Version”, “Duplicate” and “Post”
Category: Unexpected behavior / Ergonomics
Problem:
1. The editor “Post” action was registered for the whole application so that “ENTER” within the key field (cost centre) and the “Validity selection” field triggers the editor “Post” action by mistake before this correction.
2. The editor actions “New”, “New version” and “Duplicate” did not set the focus into the editor.
Correction result: Now both problems have benn corrected.
5.1.3 Financials
5.1.3.1 Financials and Human Resources
RFR-016414 Correction
Framework: Financials
Application: Synchronize Financials data
Category: Unexpected behavior
Problem: If the description of an account or currency is subsequently changed by the external financials system, only the content language of the user who triggered the action is updated.
Correction result: If system property “com.cisag.app. financials.interfaces.log.NLSUpdate=true” is set, the other content languages will be updatet too.
5.1.4 Inventory management
RFR-016414 Documentation
The help document “Introduction: Transport Processes” has been updated regarding revaluations.
5.1.4.1 Availability query
RFR-016414 Correction
Framework: Inventory management
Application: Availability query
View: Origin
Action: n.a.
Category: Unexpected behavior
Problem: The display of the print status “output in full” of a production order remains, even if the production order is dispatched again or another line item is added to the production order.
Correction result: The display of the print status of a production order changes to “not output” or “partially output”, if the production order is dispatched again or another line item is added to the production order.
RFR-016414 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Recalculate due date and quantity…
Category: Exception
Problem: A receipt of goods is performed for a co-product of a production order. A subsequent “Recalculate due date and quantity…” is performed. Target quantity for recalculation is set in such a way that new target quantity of co-product is smaller than quantity of receipt. Then recaculation leads to an exception: “Menge (-xx Stk) darf nicht negativ sein”.
Correction result: In above described context action “Recalculate due date and quantity…” is performed without exception and works as expected.
If after receipt of goods of co-product reported status is not “Reported in full” a availability detail exists with quantity = target quantity – reported quantity. After recalculation this availability is removed. Reported status is “Reported in full”.
5.1.4.2 Calculate inventory values
RFR-016414 Correction
Frameworks: Inventory, Purchasing, Sales
Applications: Purchase orders, Distribution orders
Action: Complete delivery manually
Category: Unexpected behavior / Ergonomics
Problem:
1. If the delivery is completed manually some valuation correction postings might be created (distribution: for the target only). But before this correction this will be performed also if nothing was delivered – so the inventory transaction posting logic sends an error message that the quantity must not be null.
2. If some error messages/not confirmed warnings occur within the “complete line items”/”reopen completed line items” actions of the distribution orders application the action was not executed but the relevant messages were not shown in contrast to the sales/purchase orders application.
Correction result:
1. Now the valuation correction postings will not be created if the delivered quanity (distribution: target delivered quantity) is zero.
2. Now messages that require attention will be shown also for these actions of the distribution orders application.
RFR-016414 Correction
Frameworks: Inventory, Purchasing
Applications: Receipt of goods, Supplier invoices
Action: Book receipt/invoice
Category: Invalid data / Unexpected behavior
Problem: Up from the fix “CIS620PB-Fix11 KW20/2022” the “Inventory valuation” logic does not work correctly if the relevant organization has as “domestic amount combination” the value “0”.
Correction result: Now the “Inventory valuation” logic works again as expected also in this case.
5.1.4.3 Delivery orders
RFR-016414 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Delete
Category: Exception / Invalid data
Problem: An exception occurred when deleting a delivery order for a sales order with detail lines permitting multiple inventory owners.
Correction result: From now deleting will work as expected in that case.
Data update: To update the invalid delivery orders availability and demand origin data please save the delivery order once more. Before you must change at least one attribute of the invalid detail line, i.e. a text.
RFR-016414 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Generate and output delivery slips…
Category: Invalid data
Problem: The attribute InventoryTransaction:formattedPostingOrderNumber was not filled during the generation of delivery slips for distribution orders.
Correction result: From now the attribute InventoryTransaction:formattedPostingOrderNumber will be filled as expected.
RFR-016414 Correction
Framework: Storage Location Control
Application: Inventory requisition
View: Manual stock movement
Action: Generate inventory orders for a warehouse internal transport
Category: Exception
Problem: If the target of a warehouse internal transfer is prescribed the generation of inventory orders could cause an exception.
Correction result: Inventory orders with a prescribed target of a warehouse internal transfer can be generated as expected.
RFR-016414 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Cancel and output delivery slips…
Category: Invalid data
Problem: The Cancel process of a delivery order detail line created for the process “Return of goods slips with inventory posting” with an item, that has defined packaging unit of measures of usage type “Inventory”, did not post an inventory transaction.
Correction result: From now inventory transactions will be posted as expected.
RFR-016414 Correction
Framework: Inventory
Application: Shipping loads
View: n.a
Action: Update
Category: Unexpected behavior
Problem: Allthough the delivery partner and the delivery partner address was the same for all included delivery orders, in special cases, the error message SHP-127 was displayed and prevented the update of the loading unit.
Correction result: From now the comparison of delivery partner and delivery partner address of all included delivery orders will work as expected.
Technical information: The reason for displaying the error message SHP-127 was, that the validation for updating shipping loads could not handle duplicates of delivery partner data objects filled with identic data but different primary key.
5.1.4.4 Inventory count
RFR-016414 Documentation
The help document “Inventuren” has been updated regarding new parameter “Ausprägungen gezählter Artikel ausschließen” in action “Artikelbezogene Inventurzähllisten erzeugen” and new action “Inventurdifferenzlisten erzeugen”.
RFR-016414 Correction
Framework: Inventory management
Application: Inventory count lists
View: n.a.
Action: Zähllistenstruktur ändern
Category: Exception
Problem: An error occurred when trying to change a storage location-based inventory count list.
Correction result: Changing a storage location-based inventory count list behaves as expected now.
RFR-016414 Correction
Framework: Inventory Management
Application: Inventory counts
View: n.a.
Generate item based inventory count lists for variant items
Category: Unexpected behavior
Problem: Variant items were ignored at the creation of inventory count lists.
Correction result: Line items with varinat items will be generated as expected.
RFR-016414 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Creation of storage location line item with item data although the same line item exists with a loading unit
Category: Unexpected behavior
Problem: If there was a generated storage location line item for a loading unit it would not be possible to create a new line item for the same storage location/slot with item data.
Correction result:
– Although there is a generated storage location line item for a loading unit it is now possible to create a new line item for the same storage location/slot with item data.
– Although there is a generated storage location line item for item stock it is now possible to create a new line item for the same storage location/slot for a loading unit.
– But it is only allowed to report either the loading as found or the item stock as found for the same storage location/slot.
– This functionality is only supported when the storage location/slot line item is already contained as generated line item (e.g. not manually added).
RFR-016414 Correction
Framework: Inventory management
Application: Inventory count lists
View: n.a.
Action: Import an physical inventory count report Import of a physical inventory count reports into a physical inventory count list with a large number of line items.
Category: Unexpected behavior
Problem: Importing multiple reports into a physical inventory count list with very many line items of the same item, as is the case with serial numbers, for example, the import took an extremely long time.
Correction result: When importing reports, unnecessary duplicate checks were removed, so that the performance could be increased significantly.
RFR-016414 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Generate item-dependent inventory count lists…
Category: Unexpected behavior
Problem: An item with identifier support was contained within an inventory count lists although it was already counted and the generating setting was “Ignored currently”.
Correction result: Although an item is already counted and the generating setting is “Ignored currently” identifier stocks that are not counted will be offered again to be counted. But to completely ignore already counted items the dialog has got the new setting “Ausprägungen gezählter Artikel ausschliessen” (german label).
The default behaviour is as before.
5.1.4.5 Inventory posting query
RFR-016414 Correction
Framework: Inventory management
Application: Cockpit: Inventory postings
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: Some attributes did not have their own data descriptions, so individual naming of attributes was not possible.
Correction result: Data descritions have been added so that individual naming of attributes is now possible.
5.1.4.6 Inventory postings
RFR-016414 Correction
Frameworks: Inventory, Purchasing
Applications: Purchase orders, Delivery orders, Inventory postings
Action: Purchasing return (“Delivery” and “Cancel delivery”)
Category: Invalid data / Unexpected behavior
Problem:
– If a purchase order defines some purchasing costs the receipt of goods books these costs after the increasing the onhand (OK).
– If such a receipt is canceled the costs will be booked (removed) before the onhand is reduced (OK).
– But if a return shipping order is used instead the costs will be booked after the reducement of the onhand (error).
– And f a such return shipping order is canceled the costs will be booked before the increasement of the onhand (also an error).
Correction result: Now the return shipping order and its cancelation will be booked as expected.
RFR-016414 Correction
Framework: Inventory Management
Application: n.a.
View: n.a.
Create inventory postings
Category: Unexpected behavior
Problem: If a storage location was specified although the specified storage zone was simple the inventory posting would not be denied. This problem could only be caused if the inventory posting creator was not the import. The result was a not correct “CurrentUnitOnhand” dat set and because of that the new stock could not be used for any other process.
Correction result: Independent of the creator the correct specification of storage locations, identifiers and number of item units will checked in general.
A data upate is not necessary, there are already tools to update the current unit onhand data.
5.1.4.7 Inventory query
RFR-016414 Correction
Framework: Inventory management
Application: Output inventory
View: n.a.
Action: Output report document.
Category: Exception
Problem: The specification of too long search characteristics led to an exception
Correction result: The length of the search characteristics is now checked so that search characteristics that are too long can no longer be specified.
5.1.4.8 Loading units
RFR-016414 Correction
Framework: Inventory
Application: Delivery orders / Picking orders
View:
Action: Generate, assign and display loading units…
Category: Unexpected behavior
Problem: The values of the storage unit customization attributes ‘Segregated by item’, ‘Segregated by identifier’ and ‘May contain loading units’ loading units were not taken over to a new created loading unit if it was created from loading unit template.
Correction result: As expected from now the values of the storage unit customization attributes ‘Segregated by item’, ‘Segregated by identifier’ and ‘May contain loading units’ loading units will be taken over to a new created loading unit if it was created from loading unit template.
RFR-016414 Correction
Framework: Inventory
Application: Import data
Filter: UnitLoad
Action: Import
Category: Exception
Problem: An exception occured deleting a unit load detail via import.
Correction result: From now deleting a unit load detail via import will work as expected.
RFR-016414 Correction
Framework: Inventory
Application: Loading units
View: n.a.
Action: Validate
Category: Invalid data / Unexpected behavior
Problem: The content of a loading unit was not not validated correctly against the attributes ‘Segregated by item’ and ‘Segregated by identifier’ after changing the storage unit of a loading unit.
Correction result: From now the validation will work as expected.
5.1.4.9 Picking orders
RFR-016414 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Load
Category: Exception
Problem: The “Load”-Action throwed an exception if the “just in that moment” displayed picking slip was already completed and delivered in the backround from other user session. This could happen, if a detail line was reported with zero quantity and therefore is deleted in the backround delivery step.
Correction result: From now the exception will not occur anymore. The application will work as expected.
5.1.4.10 Receipts of goods
RFR-016414 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Cancel
Category: Invalid data
Problem: The cancel process of detail lines with a batch item caused invalid storage location reservations if i.e. the “best before” date was changed before canceling was been excecuted or an other error message prevented the creation of the cancel goods receipt.
Correction result: From now the cancel process will work as expected. no invalid storage location reservations will be created.
Data update: Use the application ‘Correct voucher data and reservations’ to delete the invalid storage location reservations.
5.1.4.11 Reservations
RFR-016414 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: Manual Stock Movements
Action: Generate inventory orders…
Category: Exception
Problem: If there was a serial number demand and the reservations were activated for the item the next reservation try could cause an exception.
Correction result: Although the update application “Update demand data” is not executed after the activation of a reservation function the reservation requests will be processed as expected.
RFR-016414 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Automatic reservation of an planned item incoming
Category: Unexpected behavior
Problem: If the planned incoming was for an item with a concrete idenitifier the sales order line item could not reserve this incoming.
Correction result: If the sales order line item is not created for a specific identifier an incoming for the same item can be reserved as expected.
RFR-016414 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Generate inventory allocation…
Category: Exception
Problem: If the item supports parallel inventory units and inventory packaging units the reservation of an obligated inventory unit could cause an exception. This error could only occur if the item warehouse unit is not the first item unit.
Correction result: The reservation of the inventory packaging units will be done as expected.
5.1.4.12 Warehouses
RFR-016414 Correction
Framework: System Management
Application: Import data
Action: Import data (StorageArea)
Category: Unexpected behavior
Problem: When importing a warehouse, the cost centre and cost objective could only be imported via a GUID.
Correction result: The import controller has been extended so that the cost centre and cost objective can now also be imported via the code.
5.1.5 Production
RFR-016414 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: “Calculate availability…”
Category: Unexpected behavior
Problem: Only affects systems that have the system property com.cisag.app.production.order.log.UseDayTimeBasedAvailability enabled.
When “Calculate availability…” is performed for production order details with identical item and begin time a order is established for which details availability are preferred.
That means: in case the demand quantity sum of all these details exceeds the total availability then the earlier production order material positions still get the status “available”
in case the demand quantity sum of these earlier material positions does not exceed the total availability.
If reservation is active for involved item and production orders following situation may occur (if quantity on stock is completely reserved): Some of the details are reserved completely (which means: availability status is “available).
Some of the details are not reserved (which means: availability status is “not available”). At least one detail may be partially reserved. For this detail calculation of availability results in “available” which is not correct.
Correction result: In above described scenario, calculation of a partially reserved production order detail results in “not available.”
5.1.5.1 Operations
RFR-016414 Correction
Framework: System management
Application: Import data
View: n.a.
Action: import
Category: Exception
Problem: An exception can occur when importing a production plan with additional fields as parameters.
Correction result: The exception does not occur.
5.1.5.2 Routings
RFR-016414 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: Misleading error messages appear when dispatching a production order if all operations/routings are blocked in the second level.
Correction result: The order is not dispatched and a suitable error messages appear.
RFR-016414 Correction
Framework: Production
Application: Production Orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: A blocked operation occurs in routing 1 and routing 2 and routing 2 is included in routing 1. As a result, routing 2 is not scheduled for the production order.
Correction result: All not blocked operations from routing 1 and routing 2 are scheduled for the production order.
5.1.6 Purchasing
5.1.6.1 Purchase orders
RFR-016414 Correction
Framework: Purchasing
Application: Purchase orders (Consignment orders)
Action: Validate
Category: Unexpected behavior
Problem: Since some time, the base discount origin type will be checked. Normally this attribute is mandatory but in case of consignment order this attribute is always empty so that the error message that says that the discount origin type is needed is not correct.
Correction result: Now the error message does not occur anymore in this case.
5.1.6.2 Supplier contracts
5.1.6.3 Supplier invoices
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate
Category: Exception
Problem: If an item is specified but not valid and exception occurs during the try to validate the order assignments.
Correction result: Now the exception does not occur anymore.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Create correction invoice
Category: Unexpected behavior
Problem: The costing data default values (quantities and amounts) are set always to the quantity/amount of the invoice line item. So if the original costing data contains partial quantities/amounts the correction invoice contains unexpected data. In case of multiple costing data entries the correction invoice can not be booked because the sums do not match.
Correction result: Now the relevant partial quantity and partial amount will be used for the correction invoice. Relevant is always the data of the corrected invoice line item.
RFR-016414 Extension
Hook contract definition: com.cisag.app.purchasing.invoice.hook.log.SupplierInvoice
Hook: com.cisag.app.purchasing.invoice.hook.log.HeaderValidateCancelHook
Description: A new hook has been provided so that hook implementations can perform some additional “Cancel supplier invoice” validations. If any hook implementation requires attention the current invoice will not be canceled.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate booking
Category: Exception Unexpected behavior
Problem: An exception occurs for additional line items of a supplier invoice with the types “Supplier invoice” and “Correction supplier invoice” if the line item attribute “Distribution” is empty.
Correction result: Now the exception does not occur anymore. In addition to that, in case of an empty “Distribution” the sum of the assigned amounts will be checked now so that a higher assignment is not possible anymore.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Validate / Validate book
Problem: If with respect to the relevant financials modul an account requires a cost centre or a cost objective or both a supplier invoice line item can not be saved currently (error message “PUR, 1707”). Typically this data will be added automatically together with an order assignment. But if this order assignment will be performed later for any reason a supplier invoice line item can not be saved without any costing data.
Correction result: Because this validation is already a step of the booking validations (with some more detailied rules) there is no need to validate this already at save time. So the validation for the save step was removed by this correction.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Manual/automatic order/receipt assignment
Category: Unexpected behavior
Problem: The order assignment quantity and/or the invoice costing data quantity will not be determined with the expected quantity.
Correction result: Now the quantities will be determined as expected:
1. In case of an order assignment – the order line item total quantity uom will be tried to used (only if without conversion errrors).
2. In case of a costing data – the invoice line item total quantity uom will be tried to used (only if without conversion errrors).
RFR-016414 Correction
Frameworks: System Management, Purchasing
Applications: Customing, Supplier invoices
Actions: Create, Book correction invoice
Category: Exception / Invalid data / Unexpected behavior
Problems:
1. The purchasing customizing field “Account origin for supplier invoices” is defined to be used only for the invoices with the types “Supplementary cost invoice” and “Supplementary cost invoice for distribution” but was set by mistake in all types of invoices.
2. All invoices that are not supplementary invoices ignore the setting that is present in the supplier invoice base. But in case of correction invoices the value of account origin is used that is intended to be used only for supplementary invoices. So some unexpected effects (error messages) occur during the try to book a correction invoice.
Correction result:
1. The purchasing customizing field “Account origin for supplier invoices” has been renamed to “Account origin for additional cost invoices”. In addition to that only new invoices with the types “Supplementary cost invoice” and “Supplementary cost invoice for distribution” are using now this customizing value; all other types are using always the value “According to supplier invoice line item”. As before cancel invoices are using the value of the original invoice.
2. The unexpected effects (error messages) of correction invoices do not occur anymore.
Technical information: The method “com.cisag.app.purchasing.invoice.log.InvoiceBookingEntity. fillCostingDataByRule(InvoiceDetail, InventoryTransaction)” has been set to deprecated and is not needed/used anymore. It will be deleted in a future release.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Import
Category: Exception
Problem: If the import file contains an order detail that does not exist an exception occurs before this correction.
Correction result: Now the exception does not occur anymore.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Cancel/Delete correction invoice
Category: Invalid data / Unexpected behavior
Problem:
1. The “cancel” action of a correction supplier invoice changes by mistake the “com.cisag.app.purchasing.obj. ReceiptInvoiceOrderAssignment#supplierInvoiceQuantities” that belongs to an order line item.
2. The deletion of a correction supplier invoice changes by mistake the “com.cisag.app.purchasing.obj. ReceiptInvoiceOrderAssignment#supplierInvoiceQuantities” that belongs to an order line item.
Correction result: Now this data will not be changed in these cases.
RFR-016414 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Change order assignment data
Category: Invalid data / Unexpected behavior
Problem: Order assignment data changes do not refresh the “Bonus base” and “Cash discount base” data – so as result also the invoice line item data is wrong (if calculated automatically).
Correction result: Now the data will be refreshed as expected.
5.1.7 Relationship Management
5.1.7.1 Campaigns
RFR-016414 Extension
Framework: Relationship Management
Application: Campaigns
View: n.a.
Action: Mark invalid e-mail addresses for deletion
Field/Column: E-mail address
Category: New field, New action
Description: New column E-mail address and action for marking for deletion invalid e-mail addresses has been added to Addresses table in Campaigns application. New field E-mail address has been added to Generate address dialog.
RFR-016414 Extension
Framework: Relationship Management
Application: n.a.
View: n.a.
Action: n.a.
Field/Column: E-mail address
Category: New field
Description: New column E-mail address has been added to EntityAddresses business object.
RFR-016414 Correction
Framework: Relationship Management
Application: Campaigns
View: n.a.
Action: n.a.
Category: Typo and translation correction.
Problem: Incorrect and missing translations on the email validation button, the Addresses tab and the header of the Generate address modal window.
Correction result: Corrected typos. The validation button translation is not added as there is no DE and PL translation in FS.
5.1.8 Sales
RFR-016414 Correction
Framework: Sales / Purchasing
Application: Sales price lists, Purchasing price lists
View: n.a.
Action: post editor dat into table
Category: Unexpected behavior
Problem: The delete flag of a price definition was overwritten by posting a price definition from the editor into the table of the application. That could happen if the “mark as deleted” action was executed after taking over the price definition to the editor.
Correction result: From now the “mark as deleted” action will reset the data of the editor. In the future, it will therefore not be possible to post any data from editor, that will overwrite the delete flag.
5.1.8.1 Customer invoices
RFR-016414 Extension
Hook contract definition: com.cisag.app.sales.invoice.hook.log.CustomerInvoice
Hook: com.cisag.app.sales.invoice.hook.log. HeaderValidateCancelHook
Description: A new hook has been provided so that hook implementations can perform some additional “Cancel customer invoice” validations. If any hook implementation requires attention the current invoice will not be canceled.
RFR-016414 Correction
Framework: Sales
Application: Sales Orders
Action: Generate and output invoice…
Category: Unexpected behavior
Problem: When generating invoices with different line items from different tax periods, it is necessary to call the invoice generation several times until all line items are invoiced.
Correction result: Using a system property the number of invoice generation can be specified.
Technical information: The number of invoice generation can be defined using system property: “com.cisag.app.sales.invoice.log.Invoicing.retries”.
RFR-016414 Extension
Framework: Sales
Application: Customer invoices
Action: Cancel invoice
Category: New warning
Description: Since “CIS620PB-Fix13 KW34/2022” an internal supplier invoice that belongs to a distribution order can be created with the status “Released” instead of the status “Completed”.
If such a supplier invoice is present the customer invoice can be cancelled normally but an error message occurs during the try to cancel also the original supplier invoice (because it is not booked). Such a supplier invoice can be booked and cancelled later.
To avoid such a situation, a new warning will be send now that informs the user before the customer invoice cancellation that the corresponding supplier invoice is not booked – so that the user can decide whether to cancel the customer invoice anyway.
RFR-016414 Correction
Framework: Sales
Application: Customer invoices
Action: Create invoice
Category: Invalid data / Unexpected behavior
Problem: If the customer invoice uses a retail calculation the domestic amounts of “not price relevant line items” (e. g. kit components) were wrong before this correction.
Correction result: Now calculation is as expected.
RFR-016414 Correction
Framework: Sales
Application: Customer invoices query
Action: Display, Reorganization
Category: Exception
Problem: If the customer invoice application or cockpit displays some instances and some of these instances are reorganized an exception occurs during the try to switch back to the application.
Correction result: Now the exceptions do not occur anymore.
5.1.8.2 Customer returns
RFR-016414 Correction
Class: com.cisag.app.sales.customerreturn.log. ReturnUtility
Method: retrieveReturnableQuantity
Description: Before this correction the method throws an exception if the used method “Quantities.bestMatching” returns null.
5.1.8.3 Delivery allocation
RFR-016414 Correction
Class: com.cisag.app.inventory.reservation.log. FixedReservationWorker
Method: FixedReservationWorker.Context.beginSubTxn()
Description: The creation of the internal sub transaction is now ensured against RuntimeExceptions.
5.1.8.4 Pro forma invoices
RFR-016414 Extension
Framework: Sales
Applications: Pro forma invoices query, Cockpit: Pro-forma invoices, Cockpit: Pro-forma invoices/line items
Action: Search, Display
Category: New functionality
Description: The pro-forma incvoice searches have been extended with the “Deletion marker” search and display field. In addition to that the “Standard” layout has been provided for the pro-forma invoice cockpit applications (header and line item) based on the layout that was previously saved on the “search level” – both layouts contain now also the “Deletion marker” search and display field.
5.1.8.5 Sales – General
RFR-016414 Correction
Framework: Sales
Applications: Sales RFQs, Sales quotations, Sales orders
Action: Apply defaults
Category: Unexpected behavior
Problem: If a sales item is configured as “No purchasing reference” the sales line item “Purchasing reference” attribute will be changed normally automatically to the value “None”. But by mistake this will be performed only if the sales line item contains a supplier.
Correction result: Now this functionality has been corrected and works as expected.
5.1.8.6 Sales orders
RFR-016414 Extension
Framework: Purchasing, Sales
Application: Sales orders
Action: Generate purchase orders
Category: Extended logic
Description: If the purchase order type that is used by a sales order is configured so that the “Automatic contract selection” functionality is activated and the same item is used muliple times for the new line items it might occur that a found contract line item open quantity or value does not match to the purchase order line item quantity or value. To support better the consideration of multiple same items the purchase order will be saved now by the purchase order generator after each main line item in this case. If the quantity and value matches after such save actions the generation will be successfully in more cases. If the generation fails it will stop directly at the sales order line item that does not match (e.g. quantity is to high) – so this sales order line item can be splitted up in two line items before the next call of the purchase order generation. Alternatively the “not matching” purchase contract line item can be completed manually so that a following contract line item can be found.
5.1.9 Storage Location Control
RFR-016414 Correction
Class: com.cisag.app.inventory.location.cache.command.log. OnhandCommand
Method:com.cisag.app.inventory.location.cache.command.log.OnhandCommand.preprocess(CommandList)
Description: After using the preprocess method the reference to the opposite command could be lost until the post process method is executed. But if only the preprocess method is used e.g. to copy the command list the opposite command would never be reassigned.
5.1.9.1 Inventory management simulation
RFR-016414 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Slot specification for fix item locations
Category: Unexpected behavior
Problem: Although the item definition had a slot specification they were not completely separeted considered. For example, if there was stock within one slot the other empty slot was no more considered.
Correction result: If the item definitions have different slots they will be considered completely seperated meanwhile the automatic put process.
5.1.9.2 Inventory orders
RFR-016414 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Action: Save and Report
Category: Unexpected behavior
Problem: The put logic suggested a storage location for an equipment loading unit. But it is not allowed to put such a loading unit at the moment.
Correction result: The put logic will not suggest a storage location for an equipment loading unit.
5.1.9.3 Inventory requisitions
RFR-016414 Correction
Framework: Storage Location control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If the source warehouse is simple and it supports fix reservations a failed transport of material to a structured warehouse could not be redone. The problem was only caused when the concrete transport target was not prescribed.
Correction result: If the material could not be put by the automatic put logic the material will be put into the receiving zone of the target warehouse.
Technical information: New API com.cisag.app.inventory.location.cache.log. PutLogic.performForcedPutLogic(PickPutData) and the decision whether the put is prescribed can be overwritten using com.cisag.app.inventory.location.cache.log.PutLogic.isForcedPutProcess(PickPutData).
5.2 Infrastructure
5.2.1 Consulting
RFR-016414 Correction
Framework: Software Development
Application: Support Requests and Development requests
View: n.a
Action: Open Word attachment
Category: Ergonomics
Description: In the ninus applications support requests and deveolpment requests it was possible to attach a word document via the paperclip icon directly to a text object. This option (and the paperclip icon) is removed.
It is still possible to open existing Word attachments via an additional option in the dropdown of the file attachment button.
5.3 System development
RFR-016413 Ergonomics
The logo icons “com.cisag.pgm.gui.coolbar.res2d. semiramis-erp2-255×45”, “com.cisag.pgm.gui.coolbar.res2d.semiramis-yellow-218×33” and “com.cisag.sys.gui. jobcontrol.res2d.semiramis-4-splash-1280×375” have been updated.
RFR-016413 Documentation
The help document “Customizing: Systemfunktionen” has been updated regarding the functions “Workflow-Management” and “Vertretungsregelungen”.
RFR-016413 Correction
The help document “Entwicklungsobjekt: Business Object” has been updated regarding automatic generation of supplements.
The help document “Shared-Cache-Management” has been updated regarding automatic generation of application server partitions and sizes.
RFR-016412 Correction
Correction of BIS import with JSON format.
RFR-016412 Correction
Process: Start of application server
Category: Exception
Problem: An application server fails to start with an InvocationTargetException if its log directory contains a logfile with two index suffixes (e.g. ADV610.ADV610_20221026_5_1.log).
Correction result: No exception.
RFR-016412 Correction
Framework: System Management
Application: Import data
View: n.a
Action: Import data
Category: Unexpected behavior for import with JSON Format
Problem: “mode” in import data was only for main entity and it will be used for entire entity and its dependents.
Correction result: Mode can be overwritten to specific dependent, using “#mode”.
5.3.1 Application server
5.3.1.1 MessageDispatcher
RFR-016412 Ergonomics
Process: Messaging
Category: Ergonomics
Problem: The messaging routines use the system name “” in descriptions of connections to or from other systems. These descriptions are part of the thread names displayed in the system cockpit and are written to the server log file.
Correction result: The system name is used.
5.3.2 GUI
RFR-016412 Correction
Class: com.cisag.pgm.gui.model.DefaultRowModel
Method: public Iterator getAllRows()
Method: public Iterator getChangedRows(boolean reset)
Description: The Iterators returned by the methods “getAllRows()” resp. “getChangedRows()” are no longer throwing a “UnsupportedOperationException” for the “remove” method.
5.3.2.1 Grid control
5.3.2.2 Infrastructure (client/server communication)
RFR-016413 Extension
Framework: Document Management
Application: Documents
View: n.a.
Action: Generate document file from template
Category: Changed behavior
Description: The action “Generate document file from template” no longer depends on Internet Explorer or it’s ActiveX support. The mail merge functionality is now performed at the server side and is therefore independent of the browser.
Limitations: The new server-side implemention for mail merge has the following limitations:
– only the “*.docx” format is supported
– the mail merge template document must not refer to external (or embedded) data sources
– only the “MERGEFIELD” field is supported
– only the switches “\b”, “\f” and “\*” (partly) are supported
– merge fields are only supported within the main document (i.e. not in headers or footers)
– mergefields can not be used in formulas (expressions)
5.3.3 System – General
RFR-016413 Correction
Process: Update of user groups
Category: Ergonomics
Problem: Any updates of user groups suffer from bad performance if the database contains a large number of user groups and user assignments.
Correction result: Improved performance.