| Release | Comarch ERP Enterprise 6.3 |
| Release date | 04.09.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-016454 – RFR-016456
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-Fix09”.
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-Fix09
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix08 will be upgraded to CEE630PB-Fix09.
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.
UPDSUP111620
Set loading weight and volume into onhand data
The parameter values of certain production order line items of the type “operation” are referenced incorrectly. They reference the original parameter values of the operation. The data update duplicates the parameter values of the operation and references the affected production order line items to the duplicated parameter values.
UPDBUG028053
Deletes reorganized order and confirmation line items
The application “Reorganize purch. orders, purch. order documents, and purch. order confirmations” did not delete the purchase order documents, and purchase order confirmations. This update application corrects the incorrect data.
5 Contained changes and extensions
5.1 Application development
RFR-016456 Correction
Framework: Production
Application: Order maintenance
View: dialog “Change due date and/or quantity”
Action: “Recalculate due date and quantity”
Category: Ergonomics
Problem: If a warning/error message is assigned to field “Reference date” (yellow or red triangle in upper right corner of field), this message cannot be inspected by clicking on the triangle if field “Reference date” is not enabled.
Field “Reference date” is not enabled if it is calculated due to value “Forward” or “Backward” of field “Move” together with a proper value of field “Number of work days”.
Correction result: If a warning/error message is assigned to field “Reference date” then assignment of message is shifted to field “Number of work days”, if field “Move” indicates to shift reference date forward/backward by a number of working days.
Otherwise assigned message keeps to be assigned to field “Reference date”.
RFR-016456 Documentation
The following help documents have been updated (German versions):
– “Kampagnen”
– “Vorgehensweisen: Kampagnen”
– “Dokumentarten”
– “Dokumente”
– “Vorgehensweisen: Dokumente”
RFR-016456 Ergonomics
Update of the English language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016456 Documentation
The following help documents have been updated (German only):
– Wareneingänge aus Beschaffung
– Vorgehensweisen und Aktionen: Wareneingänge (previous title “Vorgehensweisen und Aktionen: Allgemein zu Wareneingängen)
– Vorgehensweisen: Wareneingänge aus Beschaffung (no longer available, integrated in “Vorgehensweisen und Aktionen: Wareneingänge”)
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Recalculate due date and quantity / Midpoint rescheduling
Category: Unexpected behavior
Problem: Transitional goods receipt is not taken into account.
Correction result: Transitional goods receipt is taken into account, if the checkbox “Take administration time” is activated.
The documentation for this is adapted accordingly.
RFR-016456 Extension
Framework: System Management
Application: com.cisag.app.system.webservices.service.rest.RESTExampleService
web service and Java class
Category: New operation
Description: Web service operations for streaming data transfer have been added to this example web service. Javadoc documentation has been improved.
RFR-016456 Correction
Framework: Inventory management
Application: Inventory count lists
View: n.a.
Action: Save report
Category: Unexpected behavior
Problem: If the report was given in a unit so that it had to be converted, it could happen that an impermissible number of decimal places results.
Correction result: If the reported unit has to be converted, it is now always rounded after the conversion, so that an unallowable number of decimal places can no longer occur.
RFR-016456 Documentation
The help documents included in the “Partners” folder (under “Base” and there under “Parter Master Data”) have been updated regarding hyperlinks to other help documents, and their structure and layout.
RFR-016456 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Update
Category: Invalid data / Unexpected behavior
Problem: The checkbox to define scrap- or second-quality-quantities for serial number assignments were displayed in the GUI although the option ‘Create 2nd choice/scrap quant. in rec. of goods’ was not been activated in the customizing application.
Correction result: From now, as expected, the checkboxes won’t be displayed in that case.
RFR-016456 Documentation
The following help documents have been updated (German only): – Wareneingänge aus Produktion
– Vorgehensweisen: Wareneingänge aus Produktion (no longer available, integrated in “Vorgehensweisen und Aktionen: Wareneingänge”)
RFR-016456 Correction
Framework: Inventory management
Application: Receipts of goods
View: Purchasing
Action: Assign storage locations
Category: Exception
Problem: If the receipt of goods contained line items with identifiers that were specified in logistic units, the storage locations assignment dialog is closed with an exception.
Correction result: In the storage locations assignment dialog, logistic units are now also handled correctly.
RFR-016456 Documentation
The following help documents have been updated (German only): – Wareneingänge aus Kunden-Rücksendung
– Vorgehensweisen: Wareneingänge aus Kunden-Rücksendung (no longer available, integrated in “Vorgehensweisen und Aktionen: Wareneingänge”)
RFR-016456 Documentation
The help document “Aktion: Ladeeinheiten erzeugen, zuordnen und anzeigen” (former “Ladeeinheiten erzeugen”) has been updated regarding new “Zuordnungen aufheben und Eingangsmengen im Beleg anpassen” action.
RFR-016456 Correction
The help document “Customizing: Lagerlogistik” (German language version) has been updated regarding the “Packaging” field within the “Inventory management” function.
RFR-016456 Documentation
The help documents “Aktivitätsarten”, “Kampagnekennzahlen” and “Partner-Verknüpfungsarten” (German versions) have been updated.
5.1.1 Base
5.1.1.1 Base – General
RFR-016456 Correction
Framework: Production
Application: Create production order change history (batch)
View: n.a.
Action: Activate
Category: Unexpected behavior
Problem: The interface Production actual data from external operations for CFE Controlling makes relevant receipt of goods and invoice data available via the Transferlist Controller. Up to now, (relevant) supplier invoices and invoice details have been evaluated for this purpose, among others.
The Transferlist Controller generates too many invoice and invoice detail entries for this, most of them do not need to be evaluated at all. In addition, the transferlist controller provides invoice data regardless of whether Production / CFE Controlling is active.
Correction result:
1. the TransferList controller is only active for production data as well as invoicing data if both production and CFE controlling are in operation.
2. Condition 1. can be overruled by server properties, e.g. if CFE Controlling is not active.
3. The Transferlist Controller transfers only invoices, no invoice details. The transfer is done only when the invoice is completed or when the invoice is cancelled.
4. For each invoice in transfer list, the interface logic checks whether the invoice has details from external production. Data is provided for these only.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016456 Correction
Class: com.cisag.app.general.order.hook.log. HeaderImportContext
Method: public byte[] getInternalOrganization()
Category: Unexpected behavior
Problem: Because of an error within the class AbstractOrderEntityImportController the method “public byte[] getInternalOrganization()” does not return the correct internal organization in all cases (e.g. not within the “read” step).
Correction result: Now the com.cisag.app.general.order.hook.log. HeaderImportContext implementation returns the correct internal organization as expected also within the “read” step.
Hint: This data will be set correctly now by the method “public boolean processHeader(E entity, Source source)” of the AbstractOrderEntityImportController class.
RFR-016456 Correction
Frameworks: Purchasing, Sales
Applications: Proposals, Orders
Action: Apply defaults
Category: Unexpected behavior / Ergonomics
Problem: There might be some old purchase and sales order data where the discount or price origin type is “PROPOSAL” but at least one of the four discounts has a reference to a price definition (wrong data).
If so such an order is present the application switches to the “Edit” mode without any further trigger.
Correction result: Now the reference will be removed only for new data or in the case that the old discount or price origin type was either “Price list, manual” or “Price list” and the new value is none of them.
Also the references will be removed within the “take discounts/price from proposal” functionality.
Hint: The logic of the purchase/sales proposals and the distribution orders were changed in the same way for analogy reasons.
RFR-016456 Correction
Framework: Purchasing, Sales
Application: Proposals, Orders
Action: Save
Category: Exception
Problem: If a supplement is marked for delete an exception can occur within the save step “end”.
Correction result: Now the exception does not occur any more.
RFR-016456 Correction
Applications: Applications with line items that are based on the abstract class “com.cisag.app.general.order.ui.AbstractOrderEntityMaintenance”
Action: Post line item by “ENTER”
Category: Ergonomics
Problem: In contrast to the past within the order applications that are based on a customizable user interface data that is entered during the post action (triggered by “ENTER”) is not used always for the focused field after the successful post action. So the user has to wait until the post action is finished before entering further data.
Correction result: Based on a system engine change the line item editors of these order applications are configured now so that the entered data will be used now as expected even if the “ENTER” (post) action is still active at typing time.
5.1.1.3 Items
RFR-016456 Correction
Framework: Base
Application: Item reorganization
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The usage of some new business objects was not registered correctly for the item reorganization. Therefore items could not get reorganized.
Correction result: From now the item reorganization will work as expected.
5.1.1.4 Partners
RFR-016456 Correction
Framework: Base
Application: Reorganize partners
View: n.a
Action: Reorganize
Category: Exception
Problem: An exception occurred when deleting objects of type ‘com.cisag.app.general.otherwarnings.obj.OtherWarning’.
Correction result: From now the reorganization of partner will work as expected.
RFR-016456 Correction
Framework: Base
Application: Partners
View: Partner relations
Action: Update
Category: Exception
Problem: An exception occurred updating a partner after adding a new empty partner relation and marking it as deleted immediately after adding.
Correction result: From now, as expected, a new partner relation, that is marked as deleted, will be ignored in the update process.
5.1.2 Calculation
5.1.2.1 Calculations
RFR-016456 Correction
Framework: Calculation
Application: Trade cost calculation
View: n.a.
Action: Create new calculation or duplicate header
Category: Exception
Problem: Exception after saving a new or duplicated trade cost calculation with incorrect data in “Site” field. The organization in the top right corner match the organization of calculation schema.
Correction result: Error message after saving a new or duplicated trade cost calculation with incorrect data in “Site” field.
5.1.3 Document Management
5.1.3.1 Documents
RFR-016456 Correction
Framework: Document management
Application: Cockpit: Documents, Documents
View: n.a.
Action: Delete
Category: Unexpected behavior
Problem: Deletion of documents take very long time in case there are lots of documents and document references in the database.
Correction result: Deletion of documents has been improved.
RFR-016456 Correction
Framework: Document management
Application: Documents
View: n.a.
Action: n.a.
Category: Exception
Problem: NullPointerException occurred in two situations when creating Document via Drag and drop component:
1. Document created with document type with template when document folder did not exist.
2. Document created with document type without template, but for file existing in Kstore, which did not have CEE document.
Correction result: Exception does not occur it such situations, such cases are now handled in validation.
5.1.4 Inventory management
5.1.4.1 Availability query
RFR-016456 Correction
Framework: Inventory Management
Application: Recompilation of availability records
View: n.a.
Rebuild with item restriction
Category: Unexpected behavior
Problem: If the item was specified to limit the rebuild process inventory requisition line items with loading units containing this item would not be rebuild.
Correction result: If the item is specified to limit the rebuild process inventory requisition line items with loading units will be rebuild as expected.
5.1.4.2 Loading units
RFR-016456 Correction
Framework: Inventory
Application: Goods Receipts
View: n.a.
Action: Cancel, Cancel partially
Category: Unexpected behavior
Problem: A goods receipt could not be canceled because it is packed in a loading unit/container, that was used in a former canceled goods receipt.
Correction result: From now, as expected, the validation for canceling will not take those old canceled goods receipts into account.
5.1.4.3 Picking orders
RFR-016456 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Cancel
Category: Exception
Problem: An exception occurred canceling a picking order having detail lines that reported onhand of more than one owner and the option ‘Also cancel external inventory postings’ is enabled in the picking order type.
Correction result: From now canceling a picking order will work as expected in that case.
RFR-016456 Correction
Framework: Inventory
Application: Delivery orders / picking orders
View:
Action: Generate picking order
Category: Invalid data / Unexpected behavior
Problem: Texts of type “purchase order document” (if defined in a purchase order) could get mapped to and inserted as header text in a new picking order when a picking order for a return of goods delivery was created.
Correction result: From now, as expected, no text will be mapped from purchase order to picking orders.
5.1.4.4 Receipts of goods
RFR-016456 Correction
Class: com.cisag.app.inventory.location.cache.log. OnhandService
Method: n.a.
Description: New property (com.cisag.app.inventory.location.cache.log. OnhandService_ReserveWithMaxTimeOut) to increase the wait time (2 minutes => 15 minutes) for onhand reservation server requests. Attention this is only for an exception case. After processing the requests the property should be deactivated as fast as possible.
RFR-016456 Documentation
The following help documents have been updated (German only):
– Einführung: Wareneingänge
– Aktion: Wareneingang teilweise stornieren
– Einheiten im Wareneingang
– Ausprägungen im Wareneingang
5.1.4.5 Reservations
RFR-016456 Correction
Framework: Inventory management
Application: Reservations
View: Receipts and inventory
Action: View reservations of the demand coverage via double-click in the table row.
Category: Exception
Problem: If the demand coverage in the table line has already been deleted, then the display of the reservations was terminated with an exception.
Correction result: If the demand coverage in the table line has already been deleted, the attempt to display the reservations is prevented with an error message.
RFR-016456 Extension
Framework: Sales / Purchasing
Application: Cockpit sales orders/line items, cockpit purchase orders/line items
View: n.a.
Action: n.a.
Field/Column: n.a.
Category: new sub searches
Description:
– Cockpit sales orders/line items: the new sub searches “Reservierte Beschaffungs-Zugänge”, “Reservierte Verteil-Zugänge” und “Reservierte Produktions-Zugänge” are available.
– Cockpit purchase orders/line items: the new sub searches “Reservierte Vertriebs-Abgänge”, “Reservierte Verteil-Abgänge” und “Reservierte Produktions-Abgänge” are available.
5.1.4.6 Warehouses
RFR-016456 Correction
Framework: Inventory Management
Application: Warehouses
View: n.a.
Action: Validate
Category: Exception
Problem: If the reservation is supported within the warehouse although the customizing function reservation is not active for the company an exception could be caused for structured warehouses.
Correction result: Independent of the reservation settings the validation can be executed as expected.
5.1.5 Multi-site capability
5.1.5.1 Inter-company billing
RFR-016456 Correction
Frameworks: Purchasing, sales
Applications: Customer and supplier invoices
Action: Cancel internal invoice
Category: Invalid data / Unexpected behavior
Problem: The “Cancel internal invoice” validation checks before this correction for the “Cancelation date” within the “Cancelation parameters dialog” only if the period of the customer invoice financials organization is open.
But it does not check if the period of the relevant supplier invoice financials organization is open. So the supplier invoice cannot be booked in this case.
Correction result: Now the “Cancel internal invoice” parameters dialog considers also the supplier invoice data – so that the error does not occur any more.
5.1.6 Planning
RFR-016456 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Shut down planning server
Field/Column: Temporary planning data
Category: Delete temporary planning data
Description: Deleting the temporary planning data during shutdown shortens the lead time of the next planning process.
5.1.6.1 Material requirements planning
RFR-016456 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: …execute planning
Category: Unexpected behavior
Problem: If a planned order is created due to a underrun of reorder level this planned order can be removed due to balancing if to late receipt(s) are following.
Removing by balancing may fail if created planned order is the last one created due to under run of reorder level.
Especially if reorder level is under run at beginning because of lack of inventory this leads to a planned order not balanced if only receipts are following by planned order.
Correction result: If reorder level is under run at beginning because of lack of inventory a planned order will be removed/shortened if only receipt(s) are following by planned order and if this receipt(s) cover reorder level.
5.1.6.2 Planning – General
RFR-016456 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: …execute planning
Category: Unexpected behavior
Problem: Conflict “Early order” has as additional information a reference date assigned. This is a suggestion as how to shift delivery date of such a early order. Right now the reference date is in many cases the date of next demand subsequent to early order. Depending on constellations of early orders and demands reference date may also be the date of a later demand.
In both cases this is often not the best possible reference date.
Correction result: In case of a conflict “Early order” the assigned reference date is the date of first under run of minimum inventory or reorder level. Starting point for calculation of this date is availability date of early order considered. Subsequent orders of type receipt are not regarded. Thus calculation may result in an under run of minimum inventory or reorder level and conflict “Early order” with calculated reference date is assigned to considered order.
Please note: In case of completely reserved receipts best possible reference date is date of next following demand.
5.1.7 Production
RFR-016456 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all in “select action”
Category: Ergonomics
Problem: The error number PRD-09743 was not assigned chronologically and so a number too high was selected.
Correction result: The new error number PRD-02695 is now assigned chronologically and replaces PRD-09743.
RFR-016456 Correction
Framework: Production
Application: Order maintenance
View: n.a.
Action: Block, Release
Category: Exception / Unexpected behavior
Problem:
1.
Context: Reservation is active
A production order has a order detail of type co-product. For this co-product a receipt of goods is performed with overdelivery. After this action production order is blocked.
Result: exeception occurs as a negative quantity is tried to reserve for co-product.
2.
Context: Reservation is not active.
A production order has a order detail of type co-product. For this co-product a receipt of goods is performed with overdelivery. After this action production order is blocked.
Result: for co-product of this order detail wrong availability has been generated after production order has been blocked. Availabilities should no be generated at all as order detail is completed.
Correction result:
1. No exception occurs while production order is blocked. No availabilities are generated. Releasing production order again works as expected.
2. No (wrong) availabilities are generated while blocking production order as order detail of type co-product is already completed. Releasing production order again works as expected.
RFR-016456 Extension
Framework: Production
Application: Operation Postings
View: n.a.
Action: Post operations
Category: changed action
Description: Posting operations with non-zero quantity will use up proportional wear capacity of the equipment that is assigned to the operation or resource.
Equipment has to be reserved and located at the resource for this to work. Equipment instances with the least remaining wear capacity are used up first.
RFR-016456 Correction
Framework: Production
Application: Production orders
View: “n.a.
Action: Split or replace operation
Category: Unexpected behavior
Problem: Warning 2377 also appears when one operation should not be replaced by another (if checkbox “Replace original operation” is not active).
Correction result: Warning 2377 only appears when one operation should be replaced by another (if checkbox “Replace original operation” is active).
RFR-016456 Correction
Framework: Production
Application: Customizing –> Production –> Method
View: Production Method View
Action: Update
Category: Unexpected behavior
Problem: It was possible when entering view “Production method” in customizing and subsequently update customizing that this caused change of managed function “ProductionNoMethod”. A consequence of this was that both cockpits “Production items” for activated method and deactivated method where shown in menu.
This might have happened although function “Method” is not editable.
Correction result: Entering view “Production method” in customizing and subsequently update customizing has no effect on appearance of cockpit “Production items” in menu. For each environment proper cockpit is shown.
If there are still double appearances of this cockpit it is possible to run data updates query “UPDADU094321”.
RFR-016456 Extension
Framework: Production
Application: Production Orders
View: n.a.
Action: Midpoint rescheduling
Category: Unexpected behavior
Precondition: set com.cisag.app.production.order.log. UseAdministrationTimesForSubOrdersOnScheduling=true
Problem: When function Midpoint rescheduling is carried out and checkbox “Include administration item” is OFF -> administration time is wrongly used.
Correction result: When function Midpoint rescheduling is carried out and checkbox “Include administration item” is OFF -> administration time is not used.
RFR-016456 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Restart planning server / Shut down planning server
Category: Unexpected behavior
Problem: If a non-existing plan is selected, an error appears, but the actions are carried out for the last successfully loaded plan.
Correction result: If a non-existing plan is selected, an error appears, and no actions are carried out.
RFR-016456 Extension
Framework: Production
Application: Betriebsmittel
View: n.a.
Action: n.a.
Category: New application
Description: The new application “Betriebsmittel” in the production framework configures an additional item view for existing equipment items.
After configuration, these equipment items can be used in bills of material as new position type or manually added to production orders.
When an equipment position added to a production order, it has the normal quantity field and an additional quantity field for the wear capacity.
For each normal quantity there is one equipment requirement position created that is visible in “Cockpit: Betriebsmittelanforderungen”.
To fulfill these requirements, an equipment assignment must be performed.
For this there must be serial number based equipment instances initialized with a wear capacity. This can be done in “Cockpit: Betriebsmittel initialisieren” which shows equipment serial numbers that are physically present in inventory but have not been initialized yet.
After initialization of equipment instances, the assignment of serial numbers to requirements can be performed via action menu in “Cockpit: Betriebsmittelanforderungen”.
The assigned serial numbers are now visible in “Cockpit: Betriebsmittelzuweisungen”.
The next step is to create warehouse requisitions to move the equipment instances to the warehouse location configured at the resource.
This is done via action menu.
From the warehouse requisition, a warehouse order can be generated. After execution of the warehouse order, the equipment arrives at the resource.
Now the operation can be reported, which will automatically report the wear capacity on the provided equipment.
After the operation is completed the equipment can be returned back to its original warehouse via another warehouse requisition created via action menu in “Cockpit: Betriebsmittelzuweisungen”.
The solution additionally provides warehouse requisitions for refurbishment and for disposal via “Cockpit: Betriebsmittelinstanzen”.
RFR-016456 Extension
Framework: Production
Application: Cockpit: Betriebsmittelnutzungsvermögen
View: n.a.
Action: Recalculate
Category: new application
Description: New cockpit to show BO EquipmentWearCapacitySum.
Action “Recalculate” that
1. Inserts all missing EquipmentWearCapacitySum BOs into DB
2. Fixes BO EquipmentWearCapacitySum, depending on selection
3. Fixes associated BOs EquipmentWearCapacityRequirement, depending on selection
RFR-016456 Correction
Framework: Production
Application: ProductionOrders
View: n.a.
Action: Dispatch
Category: Exception
Problem: Exception when processing time in operation is in unit other than time unit, ex. Stk or a nonexistent unit is used.
Correction result: Appropriate validation prevents false input during operations.
RFR-016456 Correction
Framework: Production
Application: Cockpit: Production orders
View: n.a.
Action: Delete / Complete orders
Category: Ergonomics
Problem: In contrast to the production order, the cockpit contains the parameters resources reservation settings, capacity limit and scheduling category,
that are not needed for deleting/completing PO.
Correction result: These parameters have been removed.
RFR-016456 Extension
Framework: Production
Application: Betriebsmittel
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: Minor problems in new equipment features.
Correction result: Fixes in new equipment features.
5.1.7.1 Bills of material
RFR-016456 Correction
Framework: Production
Application: Bill of materials
View: Detail editor
Action: Accept
Category: Exception
Problem: If in detail editor a not valid item is accepted an exception occurs.
Correction result: If in detail editor a not valid item is accepted no exception occurs. Instead a proper error message is shown.
RFR-016456 Correction
Framework: Production
Application: Reports: Bills of material, Routings, Operations, Resource lists
View: Selection view of above mentioned reports
Action: …print
Category: Exception
Problem: Reported: If in field “Bill of material” of report “Output bills of material” as string with more than 1000 characters is specified, application ends with an exception after action “…print..” is executed.
This behavior also applies for reports “Output routings”, “Output operations” and “Output resource lists” when selection of according fields (“Routing”, “Operation”, “Resource list”) exceeds 1000 characters.
For all mentioned reports behavior also applies for the fields “Classification 1” to “Classification 5”.
Correction result: A proper validation proofs number of characters of field “Bill of material” for report “Output bills of material” (and according fields for mentioned reports). If number of characters exceed defined length an error message is output.
The definition of the field which holds the selection data for bills of material (or routing data/operation data, resource list data) is changed to a length of 2000 characters instead of 1000 characters.
Additionally also fields “Classification 1” to “Classification 5” are proofed the same way. The fields which hold selection data of classifications have a length of 1000 characters.
5.1.7.2 Operations
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: New operation line item (no multi-site production operation)
Category: Exception
Problem: When in production order you try to write nonexistent internal or external operation, you specify quantity and press Accept arrow button or Enter key, an exception occurs.
Correction result: When in production order you try to write nonexistent internal or external operation, you specify quantity and press Accept arrow button or Enter key, no exception occurs.
RFR-016456 Correction
Framework: Production
Application: Production orders
View: Order Detail, Operation
Action: Create manually a order detail or type operation or generate such a order detail in the course of scheduling
Category: Invalid data
Problem: If parameters are defined for an operation in the basic view, the parameter values are duplicated when they are used in a production order item of the type “operation”. A reference to the duplicated values is stored in the production order item of type operation (*).
For some time now, when creating a production order item of the type “operation”, the duplicated parameter values are not referenced, but instead the original parameter values of the operation are incorrectly referenced.
Result of wrong reference is: If a parameter is changed in application “Operations”, basic view, production order details using this operation have automatically this new parameter value.
If a parameter is changed in application “Production orders”, detail view, tab “Parameter”, the parameter value of the Master-Data Operation is affected.
Correction result: When a production order detail of type “Operation” is created, the new set of parameters for this detail is now referenced properly by the order detail as described: see (*)
Data update: All production order details having wrong reference to parameter values as described above are corrected.
5.1.7.3 Production – General
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: dispatch with multiple level
Category: Unexpected behavior
Problem: Warnings concerning a shift-specific scheduling method also appear with time-specific method.
Correction result: Warnings concerning a shift-specific scheduling method do not appear with time-specific method.
Hint: This is a warning that indicates an inconsistency in the resource reservation of a resource.
This inconsistency should never occur under normal circumstances and certainly not be displayed during the time-specific scheduling method.
5.1.7.4 Production orders
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Output production documents
Category: Unexpected behavior
Problem: Printing production order with deselection material/processing documents generates the print status “completely issued”. With subsequent position editor, the order goes into edit mode with correction of the status.
Correction result: Printing production order with deselection material/processing documents generates the print status “particularly issued”. With subsequent position editor, the order does not go into edit mode.
RFR-016456 Correction
Framework: Production
Application: Order maintenance
View: Order detail
Action: Save
Category: Unexpected behavior
Problem: Context: with picking, over-delivery of picking allowed, surplus at production warehouse.
A material line item of a production order is created manually or via dispatching. Production order is already in status “Released” before this happens. Surplus quantity of production warehouse is set available to material (and is reserved in case of active reservation). Some quantity to be picked remains.
After this quantity is picked availability for material at production warehouse is wrong. Scope of availability / reservation is now picked quantity.
Note: It is essential that production order is released before creation of material line item. If not production order must be released before picking. After that problem does not occur anymore.
Correction result: In context and procedure described above availability (and reservation) is set properly after picking has been performed. Availability/reservation quantity is sum of picked quantity and already available quantity at production warehouse due to surplus.
RFR-016456 Correction
Framework: Production
Application: production orders
View: n.a.
Action: Resource: set deletion marker
Category: Unexpected behavior
Problem: If a resource is removed from the production order, the set-up time in the operation is not updated with the highest set-up time of the remaining resources.
Correction result: If a resource is removed from the production order, the set-up time in the operation is updated with the highest set-up time of the remaining resources.
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch / Dispatch and release
Category: Ergonomics
Problem: SystemProperty “com.cisag.app.production.bom.log.ProductionPlanDetailLoader_SkipBlockedOperation” = true: The user does not receive an additional message if blocked operations/routings and bills of material have been skipped.
SystemProperty “com.cisag.app.production.bom.log. ProductionPlanDetailLoader_SkipBlockedOperation” = false: Since an error message was issued, the production order could not be dispatched even with unblocked operations/routing/bill of materials.
Correction result: SystemProperty “com.cisag.app.production.bom.log. ProductionPlanDetailLoader_SkipBlockedOperation” = true: no changing
SystemProperty “com.cisag.app. production.bom.log.ProductionPlanDetailLoader_SkipBlockedOperation” = false: A warning appears for each blocked operation/routing/bill of material. By confirming the warnings, the production order can be dispatched with the unblocked
operations/routings/bills of material.
With the setting “false”, both requirements are now covered.
Technical information: Attention: SystemProperty “com.cisag.app. production.bom.log.ProductionPlanDetailLoader_SkipBlockedOperation”: default has changed from true to false.
Changed meaning: If operations/routines/bill of materials are locked in the second level, depending on the setting of the property, the following procedure is followed when the production order is dispatched:
true: the locked operations/routings/bills of material are skipped
and the production order is dispatched with the unblocked operations/routings/bills of material.
No references to skipped operations/routings/bills of material appear.
false: A warning appears for each blocked operation/routing/bill of material. After confirming the warning, the production order is dispatched with the unblocked operations/routings/bills of material.
RFR-016456 Correction
Framework: Production
Application: Order maintenance
View: Detail editor
Action: Apply, Save
Category: Unexpected behavior
Problem: Context: Over delivery of picking is active
A material which has some surplus quantity at production warehouse is added to a production order (dispatching/manually). Quantity at production warehouse is consumed completely/partial (via reservation and/or availability) and quantity still to be picked is reduced accordingly.
Unfortunately at issue warehouse availability is set for complete target quantity (instead of quantity still to be picked). If reservation is active logic tries to get reservation for whole target quantity. This happens for items with/without identifier unless an identifier is specified in material line item of production order.
Correction result: In above described situation, availability at issue warehouse is set according to quantity which still has to be picked. In case nothing has to be picked (as surplus quantity at production warehouse covers target quantity of material) no availability at issue warehouse is set.
If reservation is active then reservation is done according to the availability quantity.
Please note: The error is due a recent correction (see references).
RFR-016456 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Order Maintenance: Recalculate due date and quantity… , Cockpit: Production orders: Recalculate due date and quantity…, Dispatch ord Dispatch and release…
Category: Ergonomics
Problem: On a dispatch process a production order with one/more sub level orders is generated.
Order maintenance: Rescheduling of sub level is allowed but may destroy scheduled dependencies from dispatching process.
Cockpit: Production orders: Dispatching, Dispatching and release, Rescheduling is allowed for (selected) sub level orders. This actions may destroy scheduled dependencies from dispatching process.
Correction result: Order maintenance: If a sub level order is to be rescheduled a warning dialog pops up explaining the risks with options to continue or to cancel the action.
Cockpit: Production orders: For selected sub order levels a warning appears if dispatching, dispatching and release or rescheduling is performed. Process is continued with next selected order.
Dialogs for dispatching or rescheduling allow to set “Confirm warnings”. If this is done above actions will be performed for sub level orders too.
RFR-016456 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Problem A: dispatch
Problem B: recalculate due date and quantity
Category: Unexpected behavior
Problem:
1. After dispatching, the setup time of the operation does not show the maximum setup time for all resource positions, but the setup time of the primary resource.
2. If the processing time of the resource is entered as “0” in the operation, the processing time after recalculating quantity jumps to a value that is calculated proportionally to the quantity change of the operation and the old time at the operation.
Correction result:
1: After dispatching, the setup time of the operation shows the maximum setup time for all resource positions, and not the setup time of the primary resource.
2: If the processing time of the resource is entered as “0” in the operation, the processing time after recalculating quantity remains 0.
RFR-016456 Correction
Framework: Production
Application: Update change history of production orders
View: n.a.
Action: Perform
Exception
Problem: A recent change caused an error in nightly compilation.
Correction result: Nightly compilation works concerning this error.
5.1.7.5 Resources
RFR-016456 Correction
Framework: Production
Application: Resource, Resource group
View: n.a.
Action: Manage resource type
Category: Unexpected behavior
Problem: Combinations of resource groups and resources or combinations of versions within resources cannot be maintained because error messages prevent successive processing.
Correction result: Combinations of resource groups and resources or combinations of versions within resources can now be maintained, as successive processing is possible after confirming warnings.
5.1.8 Purchasing
5.1.8.1 Purchasing – General
RFR-016456 Correction
Framework: Purchasing
Application: Reorganize purchase orders, purchase order documents, and purchase order confirmations
Action: Execute
Category: Invalid data / Unexpected behavior
Problem: Before this correction the application “Reorganize purchase orders, purchase order documents and purchase order confirmations” did not delete the purchase order correspondence and supplier confirmation line items.
This update application corrects the wrong data.
Correction result: Now also these line items will be deleted.
Data update: Please execute the data update application “UPDBUG028053” to correct the wrong data.
5.1.8.2 Purchasing recommendations
RFR-016456 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations / Calculate distribution recommendations
View: n.a.
Action: … calculate…
Category: Exception
Problem: If an items planning view or purchasing view is blocked until 31. 12.9999, an exception occurs if for this item recommendations should be calculated.
Correction result: If an items planning view or purchasing view is blocked until 31.12.9999, no exception occurs. Instead, no recommendations are created.
5.1.8.3 Supplier invoices
RFR-016456 Correction
Class: com.cisag.app.purchasing.invoice.log.InvoiceUtility
Method: public DomesticAmountMutablecalculateGrossAmountDomestic(SupplierInvoice si)
Category: Invalid data / Unexpected behavior
Problem: In contrast to the method “public ForeignAmountMutable calculateGrossAmount(SupplierInvoice si)” the method “public DomesticAmountMutable calculateGrossAmountDomestic(SupplierInvoice si)” contains an error and does not calculate correctly.
Correction result: Now the method works as expected.
Hint: Within the standard, this method is normally not used and a wrong value is corrected normally by “com.cisag.app.purchasing.invoice.log. MutableInvoiceHeaderLogic.Defaults.refreshCalculatedTaxData(InvoiceUtility, InvoiceEntity, SupplierInvoice)”.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016456 Ergonomics
Framework: Sales
Application: Customer invoices
Category: Unexpected behavior / Ergonomics
Problem: The label of the header amount field changes with respect to the current invoice data (depending on “retail calculation” and “kind of pricing”). But the tool tip text belongs always to the case “no retail calculation” and “gross kind of pricing”.
Correction result: Now the tool tip text is always empty.
RFR-016456 Correction
Framework: Sales
Application: Customer invoices
Action: Generate
Category: Exception / Invalid data / Unexpected behavior
Problem: Several errors for 0-quantity kits:
1. When invoicing a sales order with the “Invoice” flag activated for “Invoice” and “Invoice with inventory posting” for a 0-quantity set, an exception occurs in the “InvoicingPrepaymentLogic.calculateTax” method if matching debtor credits exist. The kit components are then present twice (the second time as main line items).
2. When invoicing a delivery slip, where the flag “Invoice” is activated for a 0-quantity set for “Invoice”, an exception also occurs:
a. for a price-relevant kit also in “InvoicingPrepaymentLogic.calculateTax” (see 1. – however, the kit components are only present once here, but incorrectly as main line items).
b. for price relevant kit components the exception occurs in the step “CalculationAdapter.calc ==> … ForeignAmountMutable.roundPrice” for the kit main line item; then the complete kit is not added to the calculation.
Correction result: Now these exceptions do not occur any more.
RFR-016456 Correction
Framework: Sales
Application: Cockpit: Customer invoices
Action: Finish and output invalid invoice
Category: Exception
Problem: If a customer invoice is present that has also a corresponding supplier invoice the “Cancel action” could fail (e.g. exception or server restart before activation). After that the original invoice and the cancelation invoice are marked as invalid. After that you try to activate these invoices by the “Finish and output invalid invoice” action of the “Cockpit: Customer invoices” application. The original invoice will be skipped because already a cancelation invoice exists. But for the cancelation invoice an exception occurs (“The supplier invoice does not exist”).
Correction result: For completing the cancelation the normal cancel action can be executed again. Only this action ensures that all necessary steps will be performed. So cancelation invoices needs to be skipped by the “Finish and output invalid invoice” cockpit action. This will be done for all cancelation invoices and not only for this case (customer invoice with supplier invoice).
Technical information: In addition to that the debug info of the class “com.cisag. app.sales.invoice.log.ActivateInvoiceSource” (enabled by the class “com.cisag.app.sales.invoice.log. Source”) has been corrected (wrong parameter number) and extended.
RFR-016456 Correction
Framework: Sales
Application: Customer invoices
Action: Generate, validate
Category: Exception
Problem: The customer invoice generation and validation sends in some cases a message for the “taxDate” attribute. For that the data description path is needed. Before this correction there were some classes that are using the path of the deleted attribute “CustomerInvoice:taxDate” (moved to “CustomerInvoiceTaxData:taxDate”). As result a NullPointerException occurs within the system engine method “com.cisag.sys.kernel.CisConverterBase. createDateFormat” as sub step of “com.cisag.pgm.datatype.ConverterBase.fromCisDate”.
Correction result: Now these classes are using the correct path “CustomerInvoiceTaxData:taxDate”. So the exception does not occur any more and the messages will be send as expected.
5.1.9.2 Sales – General
RFR-016456 Correction
Framework: Sales
Application: Cockpit: Sales orders/line items
Action: Complete the delivery of the sales order line items manually
Category: Exception / Ergonomics
Problem: If the action “Complete the delivery of the sales order line items manually” is performed for line items for that the “shipping unit status” is not “none”, an exception occurs.
Correction result: Now such line items will be skipped without any message so that the exception does not occur any more.
5.1.9.3 Sales orders
RFR-016456 Correction
Class: com.cisag.app.inventory.availability.log. AvailabilityAdapter
Method: hasNext()
Description: The method is now better protected against concurrently changed data.
5.1.10 Storage Location Control
5.1.10.1 Inventory requisitions
RFR-016456 Extension
Framework: Inventory management
Application: Inventory requisitions
View: Manual inventory movement
Action: Save a released inventory requisition or release an inventory requisition
Category: Unexpected behavior
Problem: If a non-deliverable batch is specified, no reservation was made for the outgoing.
Correction result: Even if a non-deliverable batch is specified, outgoing reservations are made.
RFR-016456 Extension
Class: com.cisag.app.inventory.location.requisition.log. DefaultTransportOrderReporting
Method: com.cisag.app.inventory.location.requisition.log. DefaultTransportOrderReporting.DefaultTransportOrderDetailChangedListener. getReportingTransactionProvider()
Description: The transport reporting interface of inventory requisitions supports the com.cisag.app.inventory.order.log.ReportingTransactionProvider now. Because of that, the entity management is supported now too. Within the release CEE 6.3 the extensions is limited to the usage of “equipment for production” (German: Betriebsmittel für Produktion). But in the next release it will be released for all inventory requisition usages.
5.1.10.2 Storage locations
RFR-016456 Correction
Framework: Storage Location Control
Application: Storage locations
Action: Save or validate a new storage location for a zone with the material category equipment.
Category: Unexpected behavior
Problem: A new storage location for a zone with material category equipment cannot be created because an unexpected error message occurs.
Correction result: The error message that the material category of the storage location cannot be used for the specified zone no longer occurs, as the material category is now set correctly when creating a new storage location.
5.2 Comarch Financials Enterprise
5.2.1 Controlling
5.2.1.1 Controlling – General
RFR-016456 Correction
Framework: Production
Application: Production issues
View: n.a.
Action: Post production issues directly, via operation issues, via plant data collection postings
Category: Unexpected behavior
Problem: Due to an incorrect calculation time, a cost center is drawn that is no longer valid.
Correction result: Thanks to the correct calculation time, the appropriate cost center is now drawn.
5.3 System development
RFR-016455 Correction
Framework: System Management
Application: Output Device maintenance
View: n.a.
Action: n.a.
Category: Exception
Problem: It could happen that the physical output device field is empty. A programmatic selection attempt lead to an exception.
Correction result: no exception anymore.
RFR-016455 Documentation
The change history in the help document “System Requirements” has been updated.
RFR-016455 Correction
Framework: Software development
Application: development objects
View: Business objects
Action: changing primary key
Tool: chkrep
Category: Exception
Problem: The primary key of a business object must not be changed once it is activated.
Technically the time dependency is part of primary key but it was possible to change that.
This lead to an exception on a follow up system if already a supplement was created for this business object.
Correction result: The gap was close. The validation now takes time dependency into account.
In tool “chkrep” an additional option “supplements” was added. This option allows to check the validity of supplements.
RFR-016455 Ergonomics
Files of the online help file system have been updated.
RFR-016455 Correction
XML help objects (text modules) for internal use in help documents have been created.
RFR-016454 Correction
Framework: System Management
Tool: chkrep
Option: objectDirectory
Category: Unexpected behavior
Problem: the option checks all ObjectDirEntry instance.
Should it run into a no longer supported object type the tool stopped.
Correction result: No longer supported object types will be deleted (in connection with option repair) and otherwise ignored. The tool will now run properly.
RFR-016454 Correction
Framework: System Management
Tool: wrkdatupd
View: n. a.
Action: n.a
Category: Ergonomics
Problem: The option csvFileName did not makes it clear that the file path is specified in relation to the server directory.
Furthermore there was no check whether it is possible to write here at all.
Correction result: The option text was improved. If an output file is specified, then a “write” test is performed before starting the update programs.
RFR-016454 Correction
Class: com.cisag.pgm.gui.StrategyField
Method: n.a.
Description: a preselection was not correctly transfered to the combo box
5.3.1 System – General
RFR-016454 Correction
Framework: System Management
Application: Load balancing service for dialog logons
View: n.a.
Action: Execute
Category: Unexpected behavior
Problem: The load balancer service could abort with an exception message because of a temporary database communication error. Connections to the load balancer address were no longer possible unless the application server was restarted.
Correction result: The load balancer will stay executing in certain error situations.
5.3.2 Workflow
RFR-016454 Correction
Framework: Workflow management
Tool: Search for tasks
View: n.a.
Action: n.a.
Category: Correction
Problem: Keyboard shortcuts do not work for task list in the dockable view “Search for tasks”.
Correction result: Keyboard shortcuts work for task list in the dockable view “Search for tasks”.
5.3.2.1 Activities
RFR-016454 Correction
Framework: Workflow management
Application: Absences
View: Default
Action: New
Category: Exception
Problem: If no Delegation rules are defined in Customizing Workflow Management and user tries to add new absence, then an exception is thrown and application is exited.
Correction result: Exception is not thrown anymore.
RFR-016454 Correction
Framework: Workflow management
Application: Cockpit: Activities/OLTP database
View: Default
Action: Complete activity…
Category: Exception
Problem: NPE occurs during workflow reorganization.
Correction result: NPE does not occur.
Technical information: Problem occurred, if there was an activity extension equal to null.
5.3.2.2 Activity definitions
RFR-016454 Correction
Framework: Workflow management
Application: Activity definitions
View: Individual activity, tab Application
Action: validate/save
Category: Exception
Problem: If application name is not same as java class (in development object), exception will occur and application “Activity definitions” will be closed.
Correction result: Exception does not occur, there is possibility to enter application with a name different from the class.
Technical information: Please test validation, saving and running application from activity.
RFR-016454 Correction
Framework: Workflow management
Application: Activity definitions
View: Individual activity, tab Results
Action: save
Category: Exception
Problem: Adding, editing or deleting of results when at least one result existed causes exception when saving.
Correction result: Exception does not occur anymore.
Technical information: Please test for template = yes and templates = no and without any results.
5.3.2.3 Process definitions
RFR-016454 Correction
Framework: Workflow management
Application: Activities
View: Individual activity, tab Results
Action: n.a.
Category: Correction
Problem: If activity produce image as a result, it will be not displayed (text with incorrect image address will be displayed). Image can be displayed during completing activity or in tab Results.
Correction result: Image is displayed correctly.
5.3.2.4 Workflow roles
RFR-016454 Correction
Framework: Workflow management
Application: Workflow roles
View: Default
Action: Add (new holder)
Category: Exception
Problem: The application will be closed because of a fatal error, if user tries to add new Holder without loading any role.
Correction result: The add action will be inactive until user loads some role.