What's New in Syniti Solutions 7.4.2

Release Date: 2/25/21

This topic contains:

NOTE IF YOU ARE UPGRADING FROM 7.0.6 OR BELOW: You may need to migrate your security settings to use centralized security. Users of Data Quality (formerly dspMonitor), Master Data Management (formerly dspConduct), and Mass Maintenance (formerly dspCompose) must update security roles when upgrading to 7.4.2. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.2 and later. Consult this manual BEFORE updating to 7.4.2, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

Refer to the Product Certification Matrix for the versions of third-party products that this release has been certified against.

NOTE: The Stewardship Tier is now certified with MS SQL 2019 with Transparent Data Encryption (TDE) activated. Note that enabling TDE has a measurable performance impact. According to Microsoft, TDE has an estimated performance impact of 3-5% (https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/transparent-data-encryption). Syniti testing has confirmed this, and in some cases an even higher impact on performance.

New Features

S/4 HANA Right Sizing Analysis

SAP S/4 HANA is revolutionary. Its in-memory platform, real-time analytics and applications deliver unrivaled speed, efficiency, and scale leading to significant business benefits. Without effective data management, the potential benefits of migrating to S/4 HANA can be reduced or even lost. Right Sizing for SAP S/4 HANA streamlines the data you put into S/4 HANA, to ensure it runs simply, powerfully, and efficiently. In this release, Syniti is delivering analysis software that will help customers to right size their data prior to migration.

Our S/4 HANA Right Sizing Analysis software will help you to:

  • Evaluate all your Business Suite data Identify old or infrequently accessed data for archiving

  • Test ‘what if’ scenarios to confirm what data can be safely delete

  • Accurately specify your S/4 HANA appliance requirements

By streamlining your data:

  • The cost of migrating to S/4 HANA will be reduced

  • Ongoing hardware costs will be significantly lower

Integrate the Knowledge Tier and the Stewardship Tier

With the aid of Synit’s REST API, the Stewardship Tier and the Knowledge Tier can be integrated. Integration between these two tiers could be very useful on a project, such as to:

  • Jump start Data Quality. Download Jump Start Rules into the Stewardship Tier and tie the implementation of the rule in Transform to the Knowledge Tier rule.

  • Migration Harvesting. Upload systems, data sets, terms, rules, etc from a migration initiative run on the Stewardship Tier into the Knowledge Tier to seed data governance initiatives moving forward or moving from a migration project to business-as-usual initiatives.

  • Data Catalog Population. Systems and data sets produced on the Stewardship Tier can be ingested into the Knowledge Tier to seed the catalog for Data Governance-based initiatives.

Common is now delivered with a new set Knowledge Tier Connect pages used to:

  • Configure a connection to a Knowledge Tier tenant

  • View asset mappings that detail how the SwaggerHub endpoint definitions are linked to the object structure

  • Download assets from the Knowledge Tier

  • Create and upload assets to the Knowledge Tier

For detailed information, refer to Integrate the Stewardship Tier with the Knowledge Tier.

Enhancements

Advanced Data Migration

Map

The process for removing unused source values when value mapping has been improved. A user can now access a Remove Values button at the wave, check table and wave / check table / source level to quickly remove all source values that have:

Refer to Remove Unmapped Source Values for more information.

Stewardship Tier Advanced Data Migration Content

To help accelerate migration projects, Syniti is focused on bringing its experience to every project. One of the ways Syniti does this is through the deployment of content via Knowledge Packs.

This content is shipped with Stewardship Tier 7.4.2 and above.

ADM Process Areas and Objects

From Stewardship Tier 7.4.2 and above, Advanced Data Migration (ADM) is delivered with a set of process areas and objects that are most commonly used across the migration projects that Syniti works on. This list of objects is independent of target systems and is based on decades of experience across a wide range of systems.

The specific process areas and objects that are delivered are listed in the following sections.

Process Areas

The following process areas are included in new installations (not upgrades) of the Stewardship Tier version 7.4.2 and above:

  • SAM01CF - Cross Functional

  • SAM01CRM - Customer Relationship Management

  • SAM01EHS - Environmental Health & Safety

  • SAM01FM - Financial Management

  • SAM01GTS - Global Trade System

  • SAM01HCM - Human Capital Management

  • SAM01JVM - Joint Venture Management

  • SAM01MM - Material Management

  • SAM01P2P - Procurement

  • SAM01PLM - Product Lifecycle Management

  • SAM01PM - Plant Maintenance

  • SAM01PP - Production Planning

  • SAM01PRA - Production Revenue Accounting

  • SAM01PROJ - Project Management

  • SAM01QM - Quality Management

  • SAM01RE - Real Estate Management

  • SAM01SD - Sales & Distribution

  • SAM01SM - Service Management

  • SAM01TM - Transportation Management

  • SAM01WM - Warehouse Management

Objects

The following objects are included in new installations (not upgrades) of the Stewardship Tier version 7.4.2 and above:

  • CF0020: Classification

  • CF0030: Business Partners

  • CF0040: Customer Master

  • CF0050: Business Partner Contacts

  • CF0060: Site Master

  • CF0080: Vendor Master

  • CRM0010: Customer Relationship Management

  • EHS0010: Phrase Master

  • EHS0020: Substances

  • EHS0030: Hazardous Substance Master

  • EHS0040: Dangerous Goods Master

  • EHS0050: MSDS

  • EHS0060: Specification Management

  • FM0010: G/L Account

  • FM0020: Cost Elements

  • FM0040: Credit Management (BP)

  • FM0070: Internal Order

  • FM0080: Bank Master

  • FM0120: GL Balances

  • FM0130: GL Open Items

  • FM0140: Open Accounts Payable

  • FM0150: Open Accounts Receivable

  • FM0160: Allocation Cycles

  • FM0300: Asset Management

  • FM0410: Cost Centre

  • FM0420: Profit Centre

  • FM0430: Activity Type

  • FM0450: Cost Centre Group

  • FM0460: Profit Centre Group

  • FM0470: Statistical Key Figures

  • FM0600: Treasury Managment

  • FM0700: Grant Managment

  • GTS0100: ECCN Assignments

  • GTS0200: GTC Assignments

  • GTS0300: HTS Assignments

  • GTS0400: Schedule B Assignments

  • HCM010: Organizational Management

  • HCM020: Personnel Administration

  • HCM030: Recruitment

  • HCM040: Payroll

  • HCM050: Travel Management

  • HCM060: Personnel Management

  • HCM070: Time Management

  • HCM080: Compensation Management

  • HCM090: Training & Event Management

  • HCM100: Wages

  • HCM110: Personnel Development

  • HCM120: Workforce Administration

  • JVM100: Joint Venture Management

  • MM0010: Material Master

  • MM0020: Article Master

  • MM0030: Batch Masters

  • MM0040: Batch Strategy

  • MM0050: Article Brands

  • MM0060: Article Listing

  • MM0070: Article Merchandise Category

  • P2P0030: Purchases Info Record

  • P2P0080: Purchase Order

  • P2P0090: Scheduling Agreements

  • P2P0120: Outline Agreement

  • P2P0130: Purchasing Pricing Agreements

  • P2P0150: Receipts

  • P2P0350: Source Lists

  • P2P0360: Conditions for MM Output Determination

  • P2P0370: Quota Arrangements

  • P2P0380: Purchasing Contracts

  • PLM0010: Material Master

  • PLM0030: DIR

  • PLM0040: Material Classification

  • PLM0050: Equipment Master

  • PLM0070: Interchangeability

  • PM0400: Work Centers

  • PM0410: Functional Locations

  • PM0420: Equipment Master

  • PM0430: Equipment BOMs

  • PM0440: Maintenance Catalog Codes

  • PM0450: Task Lists

  • PM0470: Maintenance Plans

  • PM0480: Open PM Orders

  • PM0490: Measuring Point

  • PP0210: Manufacturing Work Centers

  • PP0220: Bills of Material

  • PP0230: Routing

  • PP0240: Production Versions

  • PP0250: Planned Independent Requirements

  • PP0260: Recipes

  • PP0270: Open Production Orders

  • PRA0010: Production

  • PRA0020: Ownership

  • PRA0030: Contractual Allocations

  • PRA0040: Revenue Accounting

  • PROJ0010: Project Planning

  • PROJ0020: Project Preparation

  • PROJ0030: Project Tracking

  • PROJ0040: Project Reporting

  • PROJ0050: Project Costs

  • PROJ0060: WBS Elements

  • PROJ0070: Project

  • PROJ0080: Project Artists

  • QM0010: Inspection Methods

  • QM0020: Inspection Plans

  • QM0030: Master Inspection Characteristics

  • QM0040: Info Records

  • QM0050: Catalog Codes

  • QM0060: Inspection Setting

  • QM0070: Quality Notifications

  • QM0080: Quality Level

  • RE0010: Real Estate Management

  • SD0010: Customer Contacts

  • SD0020: Billing Output Conditions

  • SD0030: Sales Contract

  • SD0040: Open Sales Orders

  • SD0050: Open Quotations

  • SD0060: Scheduling Agreements

  • SD0070: Customer Material Info Record

  • SD0080: Price Conditions

  • SD0090: Rebate Agreements

  • SD0110: Material Determination

  • SD0120: Listing & Exclusion

  • SD0150: Open Quantity Contract

  • SD0160: Service Plans

  • SD0180: Batch Determination

  • SD0190: Unloading Points

  • SM0010: Repair Orders

  • SM0020: Service Contracts

  • SM0030: Service Notifications

  • SM0040: Service Orders

  • SM0050: Service Quotations

  • SM0060: Warranties

  • TM0020: Freight Order Management

  • TM0030: Freight Settelment

  • TM0040: Org Management

  • TM0050: Planning

  • TM0060: Transportation Network

  • WM0020: Distributed Order Management

  • WM0030: Inbound Management

  • WM0040: International Trade & Customs

  • WM0060: Outbound Management

  • WM0070: Pick to Sequence

  • WM0080: Warehouse Tasking

  • WM0100: MM Ext to EWM

  • WM0110: Storage Bins

  • WM0120: Control Cycles

  • WM0130: Production Supply Areas

  • WM0140: Control Cycles IM

  • WM0150: Packaging Instructions

  • WM0160: Inventory Balances

  • WM0170: Last Bin Count Date

  • WM0190: Supersession

  • WM0200: Reference Product

  • WM0210: Handling Units

  • WM0220: Inbound Deliveries

S/4 HANA Target Design Knowledge Pack

Refer to the section S/4 HANA Target Design Knowledge Pack in the Installation and Upgrade Manual for information about the S/4 HANA Target Design Knowledge Pack.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

The executionTimeout property has been updated to 300 seconds in the web.config file. In 7.4.1, it was set to a 90 second default. This update will cause all foreground events to timeout after 300 seconds. For more information about this setting, refer to the Knowledge Base article Foreground Events Time Out After 300 Seconds.

Promote

  • Syniti has added Promote configuration (Structure Data, Structure Objects and Package Templates) to support the comparing and transporting of Integrate code. With this change, users are now able to easily transport Integrate Categories, Templates and Processes across their Stewardship Tier landscape.

  • There were two SQL field data types that could not be transported due to limitations in Promote: varbinary and image. A new field was added to the Structures - Data Table Columns page, BINARY DATA, which if checked, signifies that binary data exists in the designated column within the source database and Promote applies specific logic to convert these binary columns to an encoded format that is able to be transported to the target. Specifically, this new field fixes an issue in Integrate where some BAPI connection data is stored in an image column.

Syniti Data Replication

The 7.4.2 version of the Stewardship Tier is compatible with Syniti Data Replication 9.7.2.28.

Online Help

The Installation and Upgrade Manual and the Software Requirements and Hardware Sizing Guide been moved online.

The following new use cases are available for Common:

The following new field descriptions topics are available in Common:

Data Quality

Lingering references to “dspMonitor” in workflow messages, SQL statement and stored procedures have been updated to “Data Quality.”

Resolved Issues

Master Data Management

In large Master Data Management implementations, there is a tendency that the processes determining user access to request roles to suffer from performance problems. In this release, Syniti has made several important changes to the process to prevent issues from occurring and to give users a better experience. The most notable change made involves pushing the main SQL stored procedure (webRequest_SecurityIns) that rebuilds request security into a job that runs in the background. This change has been implemented everywhere except in the apiFinalizeRequest procedure. To reduce the frequency that the webRequest_SecurityIns procedure runs, logic has been added to the process that creates the backgrounds so that a job is added only if there is not another job that would result in the same security rebuild waiting in the job queue. Additionally, there has been some optimization of SQL code to ensure better overall performance and significantly reduce the occurrence of deadlocks.

Since the request security update process is now moved to the background, a control parameter Security Job Queue (on the MDM Parameters page) has been added to the Master Data Management application to allow customers to select which job queue and ultimately which Windows services are used to process the jobs that update request security. The default job queue is ‘General’; however, since other jobs run on this queue, Syniti recommends that customers monitor the queue traffic and time taken for security updates to run to ensure the updates are not queued to run for too long. If there are delays, customers can create a dedicated queue with a higher priority than other queues. The number of allowable parallel running request security updates processes can also be set using the Master Data Management parameter (Security Job Threads, also set on the Parameters page). The recommendation is to use the default value of 2, but this can be raised if there is often a backlog of entries that take time to run. Increasing this too far could result in deadlock, so any increases should be monitored.

Summary of Important Changes

  1. Direct calls of procedure webRequest_SecurityIns now result in the creation of background jobs. Previously, this procedure was run as a foreground event. Refer to the Knowledge Base article Stewardship Tier 7.4.2 MDM Request Security Changes for more information.

  1. Adding / removing of Position Category Org Units may result in a background job being created that updates Read Only status of Role Level Org Units.

  2. Two new Parameters have been added to control the processing of MDM background security jobs:

    • Security Job Queue

    • Security Job Threads

  3. Multirow action has been removed from the Assign All Org Units on the Category Org Units for Position page.

IMPORTANT! If any local, core modifications have been made to the way any of the MDM Security related procedures run, it’s recommended that the changes are reviewed BEFORE upgrading. [DSP70-731]

Advanced Data Migration

Transform

Corrected an issue that occurred when the Generate Documentation check box was checked on the Transform tab of the Parameters page in Console and a target with a long table or object name was processed in Transform. An error displayed: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. EndTargetSource: 7d602a5d-2b69-4069-9fbe-12183d17045e failed to execute." The field length was updated, and this error no longer displays. [DSP70-1190]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

System Administration

Corrected an issue with Excel import functionality when importing more than 10k records. Prior to the fix, the Excel Results panel failed to appear at the end of the import. With this change, the import runs to completion, and the Excel Results panel appears and includes the counts of the number of inserted and updated records.

NOTE: For performance reasons, if more than 10k records are inserted and updated, the counts display on the Excel Results panel, but the individual record's changes do not display.

NOTE: Two other scenarios can cause the Excel import to fail:

  • If the Excel import takes longer than the foreground event timeout set in the web.config file, the Excel import will hang. If this happens, the "Thread is aborted" error displays on the Messages page or “The request has been aborted” displays in the Windows Event logs. The foreground event timeout can be changed via these instructions in the Knowledge Base: Foreground Events Time Out After 90 Seconds

  • If the Excel import exceeds the record count configured on the Excel Import Record Limit setting (currently defaulted to 100k) on the Parameters page, under the Page Parameters tab in System Administration, an error displays during the upload. [DSP70-1245]

Common

Previously, fields (used to determine whether records were in sync) that were encrypted on the Data Sources page in System Administration and on the Data Source Registry page in Common would cause the Out of Sync indicator to be populated on the Data Source Registry page. This occurred because the encryption process generates different hashed values even if the unencrypted values are identical on both pages. Since Passwords and Connection Strings are now delivered as encrypted, the Out of Sync indicator is shown after installation. To resolve this issue, Passwords and Connection Strings fields are now excluded when determining whether or not data sources are out of sync. [DSP70-1103]

Enhancement Requests From Users

WARNING: Customizations made to any component of the delivered Syniti Solutions will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

Changes in Previous Versions

Previous Versions of Help

Help Build Date:April 20, 2022 04:03:12 PM