| Release | Comarch ERP Enterprise 6.4 |
| Release date | 21.02.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.4.
This fix comprises the following support deliveries: RFR-016530 – RFR-016532
Information about the features of Comarch ERP Enterprise 6.4 (release news): · INF-002734 Release-News: Betriebswirtschaftliche Lösungen · INF-002735 Release-News: Technische Lösungen System requirements: · INF-002736 Systemvoraussetzungen Comarch ERP Enterprise 6.4
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.
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 CEE640PB-Fix07”.
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 CEE640PB-Fix07
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE640PB-Fix06 will be upgraded to CEE640PB-Fix07.
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 CEE630PB-Fix06 and CEE630PB-Fix13, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE640PB.
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 CEE630PB-Fix06 is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.3 and Comarch ERP Enterprise 6.4 at the same time. Support deliveries for Comarch ERP Enterprise 6.4 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 Rework after installation
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.
UPDBUG029370
Sales orders: delivery state update of set components
By error in the past the delivery state of set components in a sales order was set to ‘delivered’, all though a delivery slip detail line was never ever been created for this component. This application updates the delivered quantity back to zero and the delivery state back to ‘not delivered’.
5.1 Application development
RFR-016532 Correction
Framework: com.cisag.pgm.SoftwareDevelopment
Application: com.cisag.app.internal.support.ui.SupportRequestMaintenance
View: n.a.
Action: Save a REQ that is in the state “Folgeauftrag in Bearbeitung” e.g. ADV62010 REQ-000076
Category:Unexpected behavior
Problem: History tab gets a new entry with every save.
Correction result: Those entries no longer get generated. Every other, legit type of entry still occurs properly. Counter-tested with REQ-000078
RFR-016532 Correction
Frameworks: Sales, Inventory
Application: Sales orders, delivery orders
View: n.a.
Action (application sales orders) :
Generate delivery orders with order reference and output delivery slips…
Category: Invalid data
Problem: Generating a delivery slip for a detail line of type fixed/variable kit result in a wrong delivery status if one of the kit components is not deliverable.
Correction result: From now the delivery status of a detail line of type fixed/variable kit will be as expected after generating a delivery slip: The delivery status of the header and all components will be either “delivered” or the delivery status will be “not delivered” for all, if one of the kit components is not deliverable.
Data update: UPDBUG029370
RFR-016532 Correction
Framework: Warehouse management
Application: Storage location query
View: n.a.
Action: Loading storage locations with wide letters such as ‘W’
Category: Ergonomics
Problem: When loading storage locations that use wide letters, the bins of the storage locations could no longer be displayed in full.
Correction result: The width of the characters used is taken into account when loading, so that even wide letters no longer result in the bins of the storage locations not being displayed in full.
RFR-016532 Ergonomics
Update of the EN user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016532 Ergonomics
Update of the PL user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016532 Correction
Framework: General
Application: Items
View: Base item
Action: Create
Category: Unexpected behavior
Problem: The value of the attribute ‘loading unit change strategy’ was not set in ‘applying defaults’-process. Therefore, an error was displayed if a new storage unit is created in an OLTP, where ‘loading units’ is not activated in the customizing data.
Correction result: From now creating a storage unit will work as expected.
RFR-016532 Correction
Framework: com.cisag.pgm. SoftwareDevelopment
Application: com.cisag.app.internal.ui.SupportRequestMaintenance
View: n.a.
Action: Change as many language settings from DE to EN. Open a Development Request -> Relationships -> try and change a comment -> save
Category: Invalid data / Ergonomics
Problem: Comment cannot be saved. Rather the main language-version never gets changed and immediately replaces the new comment.
Correction result: Comment now saves correctly.
Technical information: Other than expanding the check for changed data, also the foreign language data must be copied
RFR-016532 Correction
Framework: Base
Application: Import data
Filter: com.cisag.app.general.obj.PartnerTemplate
Action: Import
Category: Invalid data / Unexpected behavior
Problem: Upon trying to import several partner templates with different countries in address data, the import controller updates all the partner templates with the country of the first partner template of the file.
Correction result: From now the import of partner templates will work as expected: The import controller will take the individual country definition of each defined template in the file.
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016532 Extension
Class: com.cisag.app.general.order.log.OrderReferenceComparator
Description: Before this change the class OrderReferenceComparator calls very often the methods “public short getPreviousOrderType()” and “public short getOrderType()” of the hook interface “com.cisag.app.general.order.hook.log.OrderReferenceComparatorHook”.
So, the “push” and “pop” methods of the internally used “MessageQueueStack” will also be called very often.
With the help of the new class “com.cisag.app.general.order.log.OrderReferenceComparatorUtility” the usage of the hook methods have been reduced up from now on.
5.1.2 Calculation
RFR-016532 Correction
Framework: Calculation
Application: Product Cost Calculations
View: Pre-calculation
Action: Change simulated costs / Save
Category: Unexpected behavior
Problem: If a warning that needed to be confirmed was displayed, saving was not possible after confirmation of the warning, due to an error in the locking logic.
Correction result: Save after confirmation of warning is now possible.
5.1.2.1 Calculation schemas
RFR-016532 Correction
Framework: Calculation
Application: Calculation schema
View: n.a.
Action: Open empty, Open
Category: Unexpected behavior
Problem: When option “Product cost calculation” was disabled in customizing, then opening application “Calculation schema” always displayed an error about trying to open type that is forbidden by customizing option.
The problem was that disabled type in field “Category” was a default type in that case.
Correction result: Now in field “Category” only allowed types are visible to choose. Opening empty application will now select available type first, instead of “Product cost calculation” type. Old error message only appears when user tries to open “Calculation schema” which is of disabled type.
5.1.3 Financials
5.1.3.1 Down payments
RFR-016532 Correction
Framework: Sales
Application: Cockpit: Down payment requests
Action: Transfer down payment requests
Category: Invalid data / Unexpected behavior
Problem: In contrast to customer invoices the specified “Posting date” is not available at adapter transfer time for prepayment requests – so an adapter implementation cannot use the specified value.
Correction result: Now at “adapter transfer time” the specified “Posting date” is set now also for prepayment requests as simulated value (as for customer invoices).
Please note: As before the persistent data will be changed only if the adapter does not filter (==> confirm) the entry.
5.1.4 Inventory management
5.1.4.1 Delivery orders
RFR-016532 Correction
Framework: Inventory
Application: Delivery orders, Loading units
View: n.a.
Action: Post loading unit changes
Category: Exception
Problem: An exception occurred in correlation with multi layered loading units.
Correction result: From now the action ‘Post loading unit changes’ will work as expected.
RFR-016532 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Complete picking order …
Category: Invalid data
Problem: The demand and availability quantities of all delivery detail lines with identifier assignments went to zero after completing the picking for a delivery order if nothing had be picked to that delivery order.
Correction result: As expected from now the demand and availability quantities of all delivery detail lines with identifier assignments will be the same as before creating the picking order if nothing has be picked to that delivery order. The connection to the picking order will be deleted.
5.1.4.2 Inventory count valuation
RFR-016532 Correction
Framework: Inventory Management
Application: Inventory count valuation
View: n.a.
Action: Load
Category: Unexpected behavior
Problem: If an inventory count valuation from the context menu should be taken over and loaded but with a different financial organization, loading would not be successful.
Correction result: If the user is authorized for the different financial organization the organization context will be changed as expected before loading.
RFR-016532 Correction
Framework: Inventory Management
Application: Inventory count valuation
View: n.a.
Action: Post valuation change and close
Category: Exception
Problem: If the item to be posted has used different item units and the first unit (a.k.a. base unit) could not be converted without a remaining amount the validation would create an exception.
Correction result: The inventory posting of the inventory count valuation will only contain the first unit other units will be ignored for the whole process as expected.
5.1.4.3 Inventory count
RFR-016532 Correction
Framework: Inventory Management
Application: Inventory count lists (data import)
View: n.a.
Import of empty storage location reportings
Category: Unexpected behavior
Problem: If the quantity columns were specified the reporting import would not be successful although the quantities were not specified.
Correction result: The quantities will only be considered as report quantities if they are specified.
RFR-016532 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Print out inventory count lists…
Category: Unexpected behavior
Problem: If either the usage “Check” or “Inventory check” was used the selected inventory count lists were printed out without any sorting.
Correction result: If the usage “Check” or “Inventory check” is used the inventory count lists will now be sorted by their number as expected.
Technical information: See PhysicalInventoryCountSheetDocument. sortCountListForInventoryOrReviewUsage(List, CisList, boolean) to overwrite the default sorting for both usages.
5.1.4.4 Inventory postings
RFR-016532 Extension
Framework: Inventory Management
Application: Reorganize inventory postings
View: n.a.
Action: Start reorganize
Category: Modify action
Description: From now on, inventory postings will be reorganized to period instead of period.
5.1.4.5 Inventory value query
RFR-016532 Correction
Framework: Inventory Management
Application: Cockpit: Current inventory values
View: Warehouse valuation prices
Action: Change to the view warehouse valuation prices
Category: Unexpected behavior
Problem: After changing view to “Warehouse valuation prices” in field Item there is default value KOMA_ARTIKEL.
Correction result: The Problem is fixed, no more default value.
5.1.4.6 Loading units
RFR-016532 Correction
Framework: Inventory
Application: Receipts of goods
View: n.a.
Action: Generate, assign and display loading units
Category: Invalid data, Unexpected behavior
Problem: In the packing dialog, in special cases, it was possible to pack items of receipt detail lines in a loading unit that is already put away in a warehouse.
Correction result: From now it will not be possible to pack items of a receipt detail line in a loading unit that is put away already.
5.1.4.7 Picking orders
RFR-016532 Correction
Framework: Inventory
Application: Picking orders
View: Delivery orders
Action: Add new detail line
Category: Exception
Problem: In special cases, adding a new detail line led to an exception.
Correction result: From now, adding a new detail line will work as expected.
5.1.4.8 Reservations
RFR-016532 Correction
Framework: Inventory management
Application: Update demand data (background application)
View: n.a.
Create/Delete demand data for different orders
Category: Exception / Unexpected behavior
Problem: The execution needed lots of execution time because of concurrent locks. It is normally not possible or only with lots of restrictions to execute the update application parallel.
Correction result: The update background application is changed to be executed not parallel.
Now it is also possible to use the demand data update background application for item mixed loading units.
Technical information: To support the old behavior, a property (com.cisag.app.inventory.reservation.log.UpdateDemandBatch_UseDeprecatedLogic) can be set. But it is not recommended to use the deprecated logic. The property and the deprecated logic will be removed in higher releases.
RFR-016532 Correction
Class: com.cisag.app.inventory.reservation.log. FixedReservationAvailabilityMaintenanceLogic, com.cisag.app.inventory.reservation.log. FixedReservationLogic
Method: com.cisag.app.inventory.reservation.log. FixedReservationAvailabilityMaintenanceLogic.DataEntry.Builder.formattedNumber(String, String), com.cisag. app.inventory.reservation.log.FixedReservationLogic.DemandData.Builder. formattedOrderNumber(String)
Description: Optional possibility to make to specify the formatted order number string directly. This is useful if the order data cannot be detected automatically because they are not put into the transaction at that moment. See Javadoc for more information.
RFR-016532 Correction
Framework: Inventory Management
Application: Picking order
View: Picking
Identifier assignment by inventory order
Category: Unexpected behavior
Problem: If an inventory order assigned an inventory identifier quantity to the referenced picking order it could not be reserved completely. This constellation is seldom and often only if there are other demand origins with a bigger demand and a newer demand date.
Correction result: The consideration of other bigger demands during the redistribution of warehouse stock will be done as expected.
RFR-016532 Correction
Framework: Production
Application: Production orders
View: n.a.
Save a new line item with specified inventory identifier
Category: Unexpected behavior
Problem: Although enough available stock existed it was not possible to reserve a line item with specified identifier.
Correction result: If enough available stock exists the specified stock should be reserved as expected.
5.1.5 Multi-site capability
5.1.5.1 Inter-company billing
RFR-016532 Correction
Framework: Base
Application: Inter-company billing
Category: Unexpected behavior / Ergonomics
Problem: The field “Price origin type” is always not editable if the current value is “Price list” – so a change to this value prevents a change back to the original or any other value.
The original reason was an authorization topic – so the intention was that not every user can define manual prices for the “Inter-company billing”.
Correction result: If the data of the entry can be changed now also this field can be changed independently from the current value – so the behavior is the same as in the proposals/orders applications.
Hint: If not all user are allowed to change the “Price origin type” value you can use the field authorization definitions for these restricted users.
5.1.6 Planning
5.1.6.1 Material requirements planning
RFR-016532 Correction
Framework: Planning
Application: Material requirement planning
View: n.a.
Action: Transfer planning data and execute planning
Category: Unexpected behavior
Problem: Planning item has more than one version of planning and production and uses different bill of materials for each version which has other production item in it.
If one of the bill of materials will be blocked for not last version then each bill of material for the next versions will be not consider during determing order of planning which can lead to wrong recommendations or even to lack of recommendations for secondary demands.
Correction result: All versions of items are now consider properly during determing order of planning, which means that second demands are consider properly now in this case.
RFR-016532 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Category: Exception
Problem: If “Planning horizon’ was bigger than the system property for maximum scheduling period then exception may occurred during planning.
Correction result: These scheduling time range checks in planning are now checking via existence of a calendar at the given date in case of real resources or by the planning time horizon of the planning configuration in case of simulated resources.
5.1.7 Production
RFR-016532 Correction
Framework: Production
Application: Where-used list
View: All
Action: n.a.
Category: Unexpected behavior
Problem: When production item has been displayed in list and it was blocked in production view, the blocked icon did not show.
Correction result: When production item is blocked for production view the blocked icon is now shown the same as for blocked production plans.
RFR-016532 Correction
Framework: Inventory
Application: Inventory requisitions
View: Production equipment
Action: Create new
Category: Unexpected behavior
Problem: It was possible to manually create and save an inventory requisition of mode “Production equipment”, which could not be used in any way.
Correction result: When trying to create an inventory requisition in mode “Production equipment”, saving is not possible and error message INV-08602 appears.
5.1.8 Purchasing
5.1.8.1 Purchase orders
RFR-016532 Correction
Framework: Purchasing
Application: Purchase orders
Actions: “Reschedule delivery date” and “Move preferred date”
Category: Unexpected behavior / Ergonomics
Problem: If a purchase order has some line items that belong to a sales order these line items are not displayed within the dialogs of the actions “Reschedule delivery date” and “Move preferred date”. In addition to that such line items were filtered by the same cockpit functionality. In contrast to this behavior the dates can be changed with respect to some rules (==> warnings or errors) manually (within the line item table or editor).
Correction result: Now such line items will not be filtered anymore by the actions “Reschedule delivery date” and “Move preferred date”. Please note that the same rules as for manual changes will be performed.
So unconfirmed warnings or error messages will be considered and might prevent a change.
5.1.8.2 Purchasing recommendations
RFR-016532 Correction
Framework: Purchasing
Application: Calculate purchasing recommendations, Calculate distribution recommendations
View: n.a.
Action Calculate purchasing recommendations, Calculate distribution recommendations
Category: Unexpected behavior
Problem: Planning data for item has maximum and minimum inventory level set on 0, coverage time set on 0 and reorder level to some positive value. Demand coverage needs to be set to Purchasing or Internal purchase.
Corresponding purchasing data needs to have positive Replenishment lead time. Item has less availability for current day than reorder level value, but between current day and day after ‘Replenishment lead time” there is already some order which solves this problem e.g. purchasing order which raise availability above reorder level.
Next if perform action “Calculate purchasing recommendations”(for demand coverage “Purchasing”) or “calculate distribution recommendations”(for demand coverage “Internal purchase”) for current day then recommendation with negative quantity has been generated.
Correction result: Now, in described situation, no recommendation will been generated.
5.1.8.3 Supplier invoices
RFR-016532 Correction
Framework: Purchasing
Application: Supplier invoices
Action: “Automatically assign purchase order or receipt of goods line items to selected or all line items” and “Automatically link selected or all line items with withdrawal declaration line item”
Category: Invalid data / Unexpected behavior / Ergonomics
Problem: The functionality to assign automatically orders or receipts or withdrawal declaration line items uses sometimes the same assignment data for multiple invoice line items because the used logic asserts that every changed invoice line item and its assignments are saved before considering the next invoice line item.
Correction result: Now every changed invoice line item will be saved before considering the next invoice line item – so multiple assignments will not occur any more.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016532 Correction
Framework: Inventory
Application: Picking orders
View: Shipping orders
Action: Add additional detail
Category: Exception / Invalid data
Problem: In a picking order, that contains more than one delivery order for one sales order, adding an additional detail could lead to invalid data. This occurred, if the shipping order, the detail should be added to, was changed in the field “delivery order” before.
Correction result: From now adding additional details will work as expected.
Technical information: Changing the delivery order in the field “delivery order” in the editor resulted in a delivery detail being added with an incorrect header GUID, namely the header GUID of the previously selected delivery order. As a result, the detail counter and the counter for the unpacked details are incremented in the wrong delivery order (respectively the detail was added to the wrong order). These must be corrected manually.
5.1.9.2 Customer returns
RFR-016532 Correction
Framework: Sales
Application: Customer returns
Actions: “Generate or change credit note orders” and “Generate or change replacement delivery orders”
Category: Invalid data / Unexpected behavior
Problem: If a sales order is generated by a customer return and a line item that is relevant for the save limit (typically the sixteenth line item) is a kit the sales order cannot be created because of the error message “SAL-00768” (kit needs at least one kit component).
The reason is that the customer return tries to save the sales order before adding the relevant kit components.
Correction result: Now it will be ensured by the customer return order generation that all kit components are added before the sales order will be tried to save. So, the problem does not occur anymore.
5.1.9.3 Sales – General
RFR-016532 Correction
Class: com.cisag.app.sales.log.SalesOwnerGroupSupport
Method: public boolean isDefined(byte[] salOrg, short typeOwnerGroupUsage, byte[] item, byte[] storageArea)
Description: The coding of the method “isDefined” has been improved so that “isSalesOwnerGroupAvailable” will be called now only for the specified sales organization and not – as before – for all sales organizations.
In addition to that, the JavaDoc of this class has been corrected.
5.1.9.4 Sales orders
RFR-016532 Correction
Framework: Inventory
Application: Sales orders, distribution orders, production orders
View: n.a.
Action: Generate picking orders and output picking slips…, Generate delivery orders with order reference…
Category: Unexpected behavior
Problem: Since changing the inventory recommendation determination to the proposer algorithm (CEE 6.0), the inventory recommendation determination did not consider identifier demands of concurrent orders when creating delivery orders / picking orders.
Correction result: From now identifier demands of concurrent orders will be considered again.
Technical information: The new behavior can be reset to the status prior to this correction using the ‘com.cisag.app.inventory.picking.log.IgnoreIdentifierDemandWhenProposing’ property
set com.cisag.app.inventory.picking.log.IgnoreIdentifierDemandWhenProposing = true.
5.1.9.5 Simulate sales prices
RFR-016532 Extension
Framework: Sales
Application: Simulate sales prices
Action: Execute
Category: Exception
Problem: Because of an extension within the delivery “CEE640PB-Fix05 KW48/2024” an exception occurs if no taxes were found for the specified parameters.
Correction result: Now the exception does not occur anymore and the tax value is empty in this case.
5.1.10 Storage Location Control
RFR-016532 Correction
Framework: Storage Location Control
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The detection of some storage location based onhand data could not be detected in seldom cases.
Correction result: In all cases the detection of some storage location based onhand data can be done as expected.
Technical information: The method com.cisag.app.inventory.obj.UnitOnhandDetail.buildByInventoryCharacteristicsKey(byte[], byte[], byte[]) was not always correctly used.
5.1.10.1 Inventory management server
RFR-016532 Correction
Framework: Storage Location Control
Application: Warehouses
View: n.a.
Action: Update
Category: Unexpected behavior
Problem: If a zone picking strategy was changed, the inventory management server could not reload this data dynamically.
Correction result: If a warehouse zone is changed, everything cached in the inventory management server will be reloaded as expected.
5.1.10.2 Inventory orders
RFR-016532 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: Manual Stock Movement
Generate inventory orders for simple warehouses
Category: Unexpected behavior
Problem: Although the simple warehouse did not support negative stock inventory orders would always be generated for the total requested stock. But this could only happen if the concrete stock (identifier, obligated unit, etc.) was specified and “reservation” was not supported.
Correction result: If a simple warehouse does not support negative stock, only existing stock will be part of a generated inventory order as expected.
RFR-016532 Correction
Framework: Storage Location Control
Application: Inventory order types
View: n.a.
The fill up restriction was not correct considered
Category: Unexpected behavior
Problem: If the put was for different items, the first open process could not be detected correctly.
Correction result: The open processes will now be detected correctly and the inventory order is created as expected.
RFR-016532 Correction
Framework: Storage Location Control
Application: Inventory orders
View: n.a.
Partial reporting for a bulk storage location
Category: Unexpected behavior
Problem: It was possible to make partial reporting for bulk storage locations the created inventory postings could not be processed.
Correction result: It is not allowed to make partial reporting for bulk storage locations within inventory orders as expected. If such an invalid bulk storage location exists it can be corrected using a manual inventory posting to pick the incorrect whole storage unit.
5.1.10.3 Storage locations
RFR-016532 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Import replenishment data
Category: Unexpected behavior
Problem: The new attribute “logistic unit” cannot be imported using the code attribute of the “LogisticUnit” association (UnitOfMeasure).
Correction result: The logistic unit of a replenishment definition can be imported as expected.
5.2 External support
5.2.1 Programming
RFR-016532 Correction
Framework: Inventory/delivery, multiorg/delivery, purchasing/delivery, sales/delivery, sales/invoice
Application: All applications that generate and sent documents(delivery slip, customer invoice, proforma invoice) via email from ERP system, e.g. Customer invoices query, Pro forma invoices query, delivery orders,….
View: n.a.
Action: send documents via email
Category: Unexpected behavior
Problem: Attachments are not named correctly when sending documents via email. Instead, they are always in German.
Correction result: The problem is fixed.
Technical information: With all OutputHandler-implementations belonging to the above frameworks doing the following in the methode write(): CisLanguageUtility.fromString(receiver. retrieveLanguage().getIsoCode()).
5.3 Internal applications
5.3.1 Support requests
RFR-016532 Correction
Framework: com.cisag.pgm. SoftwareDevelopment
Application: com.cisag.app.internal.support.ui.InstallationMaintenance
View: n. a.
Action: open Installation -> input “SHN-SERESUNIT” in Environment -> enter -> red corner on product -> new -> “SHN-SERESUNIT” stays -> click on Environment -> enter
Category: Exception
Problem: Stacktrace after described actions.
Correction result: No more stacktrace.
Technical information: Just as suspected, adding a isBusinessKeySpecified in validateNotExists fixes it.
5.4 System development
RFR-016531 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016530 Correction
Framework: Software development
Application: development objects
View: business objects
Action: opening NLS dialog for NLS BO
Category: Exception
Problem: NLS Business objects do not necessarily have an associated text object. The NLS dialog for field ‘description’ did not took this in account leading to an exception.
Correction result: No exception anymore. Should there be no associated text object, then an empty list is shown.
RFR-016530 Correction
Framework: Software development
Application: Job Maintenance
View: n.a.
Action: Activating task
Category: Ergonomics
Problem: If there is a successor system to the current development system, object will be locked and the content transferred to the successor system on activating a task.
There is a data type used for displaying application or App versions in the info dialog. It is changed whenever a delivery is made.
The information on the current system is correct but on the successor system wrong.
Correction result: A data type or data description based on the root datatype “com.cisag.pgm.appserver.ExtensionVersion” will not be transferred to the successor system.
RFR-016530 Extension
Remove unnecessary DB accesses.
5.4.1 Configuration
5.4.1.1 System cockpit
RFR-016530 Correction
Framework: System Management
Application: System cockpit
View: System, tab Editor, lower tab “User Assignments”
Action: Update the list based on query fields
Category: Exception
Problem: Refreshing the list of user assignments when the “User” query field contains a text ending with a comma and a space character closes the application with a fatal error. The exception message is “java.lang.StringIndexOutOfBoundsException: String index out of range: 0”.
Correction result: The problem is resolved.
5.4.2 Software update
5.4.2.1 Software updates
RFR-016531 Extension
Framework: System Management
Tool: ExportCodeRefreshDefinition (expcrd) / ReleaseCodeRefreshDefinition (rlscrd)
View: n.a.
Action: Export software update / Release software update
Category: New tool
Description: expcrd tool allows user to export software updates, specify the export prefix and choose if all files should be exported.
rlscrd tool allows user to release software updates.
Technical information: Both tools can accept multiple software updates to work on at once, every option or flag and how to use them is explained.
5.4.3 Workflow
5.4.3.1 Workflow templates (transport)
RFR-016530 Correction
Framework: Workflow
Application: Process Definitions
View: n.a.
Action: Safe a template…
Category: Unexpected behavior
Problem: By generating a template version of any process definition, which has a “Responsible workflow role” created from a template workflow role, we get a process definition template without a corresponding template linked to that workflow role.
Correction result: We get a process definition template with a linked “Responsible workflow role” template.