| Release | Comarch ERP Enterprise 6.3 |
| Release date | 28.02.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.
This fix comprises the following support deliveries: RFR-016533 – RFR-016535
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 “Support deliveries query” 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 update 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 Support delivery query 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 delivery 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-Fix21.”
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 to the message server or to 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-Fix21
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix20 will be upgraded to CEE630PB-Fix21.
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 is 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
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016535 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: Now saves correctly.
Technical information: Other than expanding the check for changed data, also the foreign language data has to be copied.
RFR-016535 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-016535 Extension
Framework: All frameworks that use additional fields
Application: All application that use additional fields
View: n.a.
Action: Loading
Category: Ergonomics
Problem: If an application uses other fields, the metadata of the other fields is loaded during loading. In some cases, database accesses always take place.
Correction result: The number of database accesses required has been reduced.
RFR-016535 Extension
Framework: Software Development
Application: “Development requests” and “Support request service”
View: n.a.
Action: Create successor request
Field: “Follow-up development request suffix indication”, “Follow-up development request release indication”, “Tags”
Category: New functionality and new fields
Description: In application “Development request types” two new fields were introduced, “Follow-up development request suffix indication” and “Follow-up development request release indication”. Both fields influence the description of automatically created successor requests in context of parallel maintenance.
If the field “Follow-up development request suffix indication” is specified, the stored suffix is written to the description in the automatically created follow-up development request.
If the field “Follow-up development request release indication” is active, the release number is written to the description after the suffix in the automatically created follow-up development request.
In application “Development requests” and “Support requests” a new text field “Tags” was introduced. The “Tags” field is used to store additional information. This information is arbitrary and has no special functionality.
RFR-016535 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-016535 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.
RFR-016535 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
RFR-016535 Correction
Class: com.cisag.app.general.otherwarnings.log. OtherWarningsEntity, com.cisag.app.general.otherwarnings.log.OtherWarningsStructureCache
Description: The caching logic is extended to improve the performance. Furthermore, from now the other warnings entity will call that new extended logic.
5.1.1.1 Cockpits
RFR-016535 Correction
Framework: All
Application: Customizable views
View: Views with totals (average)
Action: n.a.
Category: Unexpected behavior
Problem: The computed average value for a foreign amount column is rounded to nearest currency unit and not to the number of decimals as defined for the currency.
Correction result: Fixed.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016535 Correction
New entry in com.cisag.app.general.OrderType: Name of entry: SEM_ERP4PL_SAD_DOCUMENT
ID: 2042
Description (de): SAD-Dokument
Description (en): SAD document
Description (pl): Dokument SAD
5.1.1.3 Partner templates
RFR-016535 Correction
Framework: Base
Application: Partner templates
View: n.a.
Action: Load, Reload via Icons
Category: Unexpected behavior / Ergonomics
Problem: View changing and changing the organization via the icons, contained in the ident pane of the application, did not work.
Correction result: From now changing the view and changing the organization via the icons, contained in the ident pane of the application, will work as expected.
5.1.1.4 Partners
RFR-016535 Correction
Framework: Base
Application: Import data
Importfilter: com.cisag.app.general.obj.Partner
Action: Import
Category: Unexpected behavior
Problem: The import process of a partner using a partner template called the validation method com.cisag.app.general.partner.log.ImportExport.validateTemplatePartnerRoles() twice. That is not necessary.
Correction result: From now the validation method com.cisag.app.general.partner.log. ImportExport.validateTemplatePartnerRoles() will be called only one time as needed and expected.
5.1.2 Calculation
5.1.2.1 Calculation – General
RFR-016535 Correction
Framework: Calculation
Application: Product cost calculations
View: Tab “Calculation details”
Action: “Create simulation costs”, “Calculate with changed costs”
Category: Unexpected behavior
Problem:
1. No creation of simulated costs has been done so far. If toggle button “Total” is clicked total costs are displayed also for simulated costs (column “Simulated values” should be zero amounts).
2. “Create simulation costs” is clicked and after editing some simulated costs “Calculate with changed costs” is performed. Material for which no simulated costs are edited may show different values in columns “Total costs” and “Simulated values”. This is caused by different rounding procedures for both values. It may happen, if value of column “Direct cost” is a already rounded value (e.g. if material price is per 10, per 100…).
Correction result:
1. Column “Simulated values” in view “Total” shows zero values.
2. No difference due to rounding problems between columns “Total costs” and “Simulated values” for material.
5.1.2.2 Calculation schemas
RFR-016535 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 first available type instead of “Product cost calculation” type.
Old error message only appears when user will try to open “Calculation schema” which is of disabled type.
5.1.3 Financials
5.1.3.1 Anzahlungen
RFR-016535 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-016535 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 has been 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 connect to the picking order will be deleted.
5.1.4.2 Inventory count valuation
RFR-016535 Correction
Framework: Inventory Management
Application: Inventoty 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-016535 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-016535 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 value query
RFR-016535 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.5 Reservations
RFR-016535 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 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-016535 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.
RFR-016535 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.
5.1.5 Planning
5.1.5.1 Material requirements planning
RFR-016535 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 an exception may occur 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.6 Production
RFR-016535 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.
5.1.6.1 Production orders
RFR-016535 Correction
Framework: Production
Application: Production orders
View: Tab “Dispatching”
Action: Dispatch…/Dispatch and release …
Category: Unexpected behavior
Problem: In the course of dispatching the resolved product structures are set in not editable fields “Bill of resource”, “Bill of material”, “Routing” (and “Production method”).
If product structure results in sub orders field “Bill of material” may have a wrong entry. This is the case if bill of material of semi-finished product (“BOM-SF”) has as first line item a bill of material (“BOM-XY”) instead of a regular material. Instead of correct bill of material “BOM-SF” the bill of material “BOM-XY” is set in tab “Dispatching”.
Things work correct if “BOM-SF” has one or more regular material as first line items followed by a bill of material (“BOM-XY”).
Correction result: In above described context file “Bill of material” in tab “Dispatching” is set correct (in example: “BOM-SF”).
RFR-016535 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: New operation reservation, Recalculate due date and quantity
Category: Exception
Problem: If operation has specified resource list with at least two resources and next it has been added manually to production order then after performing rescheduling with recalculation quantities, an exception occurred.
Correction result: In described situation exception is not occurring anymore and rescheduling works properly for that case.
5.1.7 Purchasing
5.1.7.1 Purchase orders
RFR-016535 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 any more 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.7.2 Purchase price lists
RFR-016535 Correction
Framework: Purchasing
Applications: Supplier proposals, Purchase orders
Action: Validate
Category: Unexpected behavior / Ergonomics
Problem: If the message “PUR, 540” is send this message will not be shown as expected at the price listing field – instead this message will be shown at the address fields.
Correction result: Now this message will be shown as expected.
5.1.7.3 Purchasing recommendations
RFR-016535 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.7.4 Supplier invoices
RFR-016535 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.8 Sales
5.1.8.1 Customer invoices
RFR-016535 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.8.2 Sales – General
RFR-016535 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 Storage Location Control
5.1.9.1 Inventory management server
RFR-016535 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual
Inventory posting with inter-company billing created in the time zone “GMT”
Category: Exception
Problem: The inventory posting could not be processed because of erroneous date check within the Inter-company billing logic.
Correction result: The inter-company billing validates the GMT time zone as expected.
RFR-016535 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 all cached in the inventory management server will be reloaded as expected.
5.2 External support
5.2.1 Programming
RFR-016535 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 Development requests
RFR-016535 Correction
Framework: Software development
Application: development request
View: n.a.
Action: duplicate
Category: Unexpected behavior
Problem: When a development request is duplicated the registered observer list was not cleared.
Correction result: The observers are now cleared.
5.3.2 Support requests
RFR-016535 Correction
Framework: Software development
Application: Support requests
View: n.a.
Action: n.a.
Field search shows the same values multiple times
Category: Unexpected behavior
Problem: The field searches for partner have no search context.
Correction result: The field searches work as expected.
RFR-016535 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-016534 Extension
Framework: All
Application: All (navigation mode “Tabs”)
View: n.a.
Action: Context menus of applications
Category: Ergonomics
Problem: If the navigation mode “Tabs” is selected in the user settings, the context menus of applications do not contain the entries for the views supported by the application. Some applications, namely “Items” and “Partner” have separate views for each “role”. These views should available as items in the application’s context menu to allow to open the application directly with that view.
Correction result: Fixed.
RFR-016533 Extension
Framework: All
Application: All (navigation mode “Tabs”)
View: n.a.
Action: Context menus of applications
Category: Ergonomics
Problem: If the navigation mode “Tabs” is selected in the user settings, the context menus of applications do not contain the entries for the views supported by the application. Some applications, namely “Items” and “Partner” have separate views for each “role”. These views should available as items in the application’s context menu to allow to open the application directly with that view.
Correction result: Fixed.
5.4.1 Configuration
5.4.1.1 System cockpit
RFR-016533 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 an fatal error. The exception message is “java.lang.StringIndexOutOfBoundsException: String index out of range: 0”.
Correction result: The problem is resolved.
5.4.2 Workflow
RFR-016533 Correction
Framework: Workflow management
Application: Import data
View: n.a.
Action: Import data
Category: Corretion
Problem: Functions in individual validation which are available only for OLTP database and not for Repository database (like dboListValueSet) cause errors during parsing script from individual validation: GEN-09028, KRN-00505, USR-00011. Imported objects are not validated and not saved.
Correction result: Functions like dboListValueSet in Individual validation does not cause parsing errors during Import data. Objects can be properly validated.