What's New in SAP Accelerators by Syniti 7.4.5

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 ISA and Mass Maintenance (formerly dspCompose) must update security roles when upgrading to 7.4.5. Refer to the SAP Accelerators Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.5 and later. Consult this manual BEFORE updating to 7.4.5, as an analysis of current security assignments must be completed before the SAP Accelerators can be updated.
Refer to the Product Certification Matrix for the versions of third-party products that this release has been certified against.

NOTE IF YOU ARE UPGRADING TO 7.4.2 OR HIGHER: Please be aware that any JavaScript content added is stripped away and any remaining, safe HTML is displayed to users. In Stewardship Tier versions 7.4.1 and earlier, users were permitted to enter HTML and have it rendered in the UI or included in file downloads from the UI. There were no restrictions in place on what HTML/JavaScript text was permitted, leading to potentially dangerous cross-site scripting attacks. Refer to the Unsafe HTML/JavaScript removed in Stewardship Tier 7.4.2 Knowledge base article for more information.

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.

NOTE: A new, critical, step has been added to the Post Upgrade section of the Installation process. After an upgrade to Stewardship Tier 7.4.5, users must re-create their BAPI templates. Failing to do so will cause the posting of a BAPI template to fail. Refer to Re-create BAPI Templates in the Install Manual for more information.

NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to 7.4.5. The collation technology is included in the product in 7.4.5 and later. To uninstall psaCollate refer to the Knowledge Base article Uninstalling psaCollate Prior to Upgrade.

New Features

Advanced Data Migration (ADM)

ADM is now delivered with a new Collation Aware Migration feature, which simplifies the handling of case-sensitive data through the end-to-end migration process.

The Stewardship Tier runs on MS SQL Server using databases that have a case-insensitive collation (SQL_Latin1_General_CP1_CI_AS). To avoid collation conflicts, Syniti historically required that all project-specific databases use the same case-insensitive collation and for consultants to handle case-sensitive data on a case-by-case basis. This new feature is now delivered with ADM so users can decide at the wave level whether the wave’s data is case-insensitive or case-sensitive, which makes for a much simpler process.

To aid users through collation decisions, there are several new validation messages where new data sources can be introduced to a wave, such as:

  • Adding a new data object on the Process Area: Object page in Console

  • Adding a new process area on the Wave: Process Areas page in Console

  • Changing a data object’s Data Source ID or Report Cache Data Source ID on the Process Area: Object page in Console

  • Changing a process area’s Target System Data Source ID, Data Source ID or Construction WebApp ID on the Wave: Process Areas page in Console

  • Changing a wave’s Target System on the Waves page in Console

  • Adding a new source data to a target table on the Target Sources page in Collect

  • Changing the Collation Type on the Targets page in Collect if the data source has a Collation Type in the Data Source Registry that is different from the one assigned to the target.

IMPORTANT UPGRADE NOTE

When upgrading to Stewardship Tier 7.4.5, data sources are automatically assigned with the Collation Type of General Latin Case-insensitive. This ensures that the ADM AutoGen continues to create SQL tables whose text columns have a case-insensitive collation.

Console

To support the Collation Aware Migration feature, the following new fields are available on the Waves page to change the collation for a wave:

  • Wave Data Sources—Click to open the Wave Data Source Collation page to view any collation mismatches between the wave and the assigned data sources.

  • Collation Type—Displays the intended collation of data used in the wave. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

  • Collation Issue—An indicator that displays if there is one or more conflicts between the wave’s Collation Type and the Collation Type of the assigned data source. Navigate to the Wave Data Source Collation page to use the generated report to fix the issues.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Wave for more information.

Stewardship Tier (formerly Data Stewardship Platform (DSP®)

Common

To support the Collation Aware Migration feature, the following two new fields have been added to the Data Source Registry page:

  • Collation Type—Displays the anticipated collation of text columns of tables in the associated database. It also controls the collation of table text columns that are created by the ADM AutoGen functionality. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

    This field is available for the following data source types:

    • Migration Object Database (dsw%)

    • Target System Database (dg%)

    • Migration Source Database (sdb%)

    NOTE: The default value is General Latin Case-insensitive, which means the collation uses Latin characters and is case-insensitive. Case-sensitive collation is only supported for Advanced Data Migration.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

    NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Data Source for more information.

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

Refer to the Import SAP Transports section of the Installation and Upgrade Manual for information about these transports, and this Knowledge Base article for more information.

Integrate the Knowledge Tier and the Stewardship Tier

NOTE: This feature is only available for SAP Accelerators by Syniti Solutions, cloud edition.

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 terms, rules, systems and data sets to the Knowledge Tier

  • Change existing terms and rules, and change fields on existing data sets in the Knowledge Tier

  • Use API stored procedures to post assets

For detailed information, refer to Integrate the Stewardship Tier with the Knowledge Tier. In this release, it is not possible to add or change category values on new or existing rules and terms. If you need to do this, please contact Syniti Support who will advise how this can be done.

Promote Data in a Multi-tier Landscape

Stewardship Tier 7.4.4 introduces Promote - a new platform module that enables Stewardship Tier solutions to be promoted through a multi-tier landscape. Promote works by comparing the data held within Stewardship Tier application tables and SQL objects created by users between host and destination Stewardship Tier instances and informs users of the differences. Users are then able to selectively transport the changes they require. Promote directly replaces the psaTransport tool and will eventually replace the embedded CTS functionality. Refer to the article Top Benefits of using Promote Over CTS for more information.

Promote is delivered with configurations to support the Transport of Advanced Data Migration solutions. Refer to the Advanced Data Migration Code Promotion standard operating procedure for more information. Configurations for other solutions will be added in upcoming releases.

NOTE: To use Promote, a new Stewardship Tier license must be installed. Request a new license by contacting SAP Support using component XX-PART-SYN.

The Compare event now considers the case sensitivity of data when code is compared across two environments.

We have added video tutorials for the following Promote topics:

Data Migration Dashboards

NOTE: This feature is only available for SAP Accelerators by Syniti Solutions, cloud edition.

Project Managers can gain insight into migration project statuses using the Data Migration Cloud Dashboards accessible in the Knowledge Tier. Configuring and using the dashboards:

  • Allows Design / Mapping and Build Status to be tracked against plan by Wave / Process Area, Object or Target Table
  • Allows for project milestones related to design, mapping and build activities to be set and tracked against using near real-time status information.
  • Provides improved metric reporting and dashboarding, giving project stakeholders better visibility of project status using fact based information.

The dashboards provide the following:

  • An Executive Summary of the migration project, including:
    • Development Status to Plan
    • Target Design Percent Complete
    • Field Mapping Percent Complete
    • Field Mapping & Rule Backlog
    • Field Mapping % Populated
    • Rule Build % Complete
    • Complete Mapping Rule Build % Complete
  • Milestone Reporting including:
    • Project Milestones
    • Target Design % Complete
    • Field Mapping % Complete
    • Rule Build % Complete
    • Number of Objects
  • Object Status
    • Data Object Development Status to Plan
    • Target Design % Complete
    • Field Mapping % Complete
    • Field Mapping Backlog
    • Field Mapping % Populated
    • Rule Build % Complete
    • Complete Mapping Rule Build % Complete

Additionally, there are a series of reports that allow project managers and consultants to drill into status information at Object / Target and Target Source level.

This Data Migration dashboarding capability is supported by the following new DSP features:

  • Planning Groups
  • Milestones
  • Load Cycles
  • Object Planning Data

Refer to Configure Data Migration Cloud Dashboards for more information.

Enhancements

Advanced Data Migration

Console

  • The Copy Wave process now also copies the wave’s Collation Type.

  • A status indicator has been added to the Vertical View of the Process Area: Object page to track the Unit Test status of objects. This indicator will be used in a future release of the Migration dashboards. Refer to Track Report and Load Program Status for more information.

  • A Load Cycle can now have an associated instance assigned to it to tie data in Migration and Data Quality dashboards in the Knowledge Tier to the correct instance in the Stewardship Tier for multi-tier implementations. Refer to Manage Load Cycles for more information.

  • The following items associated with Load Cycle Execution Reporting can now be used by the CTS process:

    • Console—Execution Group

    • Console—Wave Execution Group Values

    • Transform—Execution Plan Template

  • Migration Execution Levels have been added to allow users to define, by object, at what level they want to perform execution-related tasks. For example, for some objects, all target tables are processed and loaded together. For other objects individual target tables may be processed and loaded one by one. Refer to Migration Execution Levels and View Migration Execution Levels for more information.
  • Migration Execution Groups have been added to allow users to specify how execution tasks need to be tracked and recorded to provide the required management insight. For example, a project may want load statistics to be captured by country or business unit. Refer to Add Migration Execution Groups for more information.
  • The Wave Execution Groups and Wave Execution Values pages have been added to manage execution data for an object.

  • The Load Cycle Execution Plan page was added to view Load Cycle Execution Plan load statistics and significant dates for an object’s Migration Execution Groups within an instance’s Load Cycle.

  • Object owners can manually track status for an object’s Relevancy, PreLoad, PostLoad and Program Type. These statuses will be used as input to Migration dashboards in the Knowledge Tier in a future release. Refer to Track Report and Load Program Status for more information.

Target Design

  • In previous versions, when Utility fields were appended to tables, they were only identified by their column name, and did not include the corresponding, user-friendly Description field. Users can now add the Utility field’s description on the Append Utility Columns page. When the Append Utility columns are added to the target table, the description is added to the column Display Name. Refer to Append Utility Columns to All Tables for more information

  • The processing time when importing fields related to Lookup tables has been improved with the addition of a WHERE clause specifying wave, process area and object.

  • The Visibility field on the Target Fields page defaulted to “Both - Mapping for Source and Target” for Natural fields, which meant that every active target field required two mappings: one for the source rule and one for the target rule. This default value caused a duplication maintenance effort because a field typically has either a source or a target rule; not both. To alleviate this duplication, the default value has been changed from “Both - Mapping for Source and Target” to “Source - Source only mapping.”

Map

  • It is now possible to update empty legacy Description fields to include the description to assist while value mapping. Refer to Include Legacy Value Descriptions for more information.

  • 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.

Construct

If a wave and its associated dsw* have a case-sensitive collation type, Data Construction table text columns and columns in list boxes are also case-sensitive.

Construct Source Relevancy Pages

Source Relevancy pages are installed as part of new installations of the Stewardship Tier. These pages, available in Construct, support a common approach to implement data relevancy within an Advanced Data Migration project. Essentially, the pages allow consultants to document the criteria used in their relevancy rules and to then drive the transformation rules they create from this data. For further information about the Source Relevancy pages, including how upgrading customers can obtain these pages refer to the article Advanced Data Migration Source Relevancy in the Knowledge Base.

Transform

SQL AutoGen

In previous versions, if the user clicked the Create All Objects or Create All Rules icons on the Automation page’s Page toolbar, mappings with an Action of Manual Rule or Manual Construction were built and their rule status was set to Complete. Mappings for source rules with these Actions must be manually built by developers. When a rule with these Actions is saved in Map, the Generate Rule check box on the Field Mappings page’s Vertical View is unchecked by default, and the rules are no longer built by SQL AutoGen.

Enhanced Migration Reporting

  • These features have been added to improve Opportunity Views. Users can:

    • View an Opportunity View’s SQL definition

    • View an Opportunity View’s assigned Error reports, providing insight into Data Quality percent calculations

    • Add a Description to an Opportunity View

      Refer to View an Opportunity View’s Definition and Error Reports for more information.

  • A Documentation tab with an External Reference field was added to the Vertical View of the following pages:

    • Objects

    • Groups

    • Your Objects

    • Your Groups

    The External Reference field displays hyperlinks and supporting commentary that demonstrate the connection from data-related assets in the Stewardship Tier to external references in other platforms and applications. Syniti recommends a report be linked to a term, rule or data set in the Knowledge Tier.

  • The WHERE CLAUSE MANUAL field on the User (Reports) page was limited to 2000 characters, which often was not enough characters and led to the generated WHERE clause to be truncated. To accommodate larger WHERE clauses, two changes were made:

    • The WHERE CLAUSE MANUAL field was extended from NVARCHAR(2000) to NVARCHAR(MAX).

    • The associated stored procedures that construct the WHERE clause were updated to ensure the resultant where clause supported NVARCHAR(MAX).

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.3 and above.

ADM Process Areas and Objects

From Stewardship Tier 7.4.3 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.3 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.3 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 Management

  • FM0700: Grant Management

  • 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®))

Updates to the web.config File

A change has been made in version 7.4.3 and later to improve performance. In previous versions, the compilation debug setting in the web.config file on the Stewardship Tier Installation directory (Program files (x86)\BOA\DSP\Web) was set to true. In some situations, this setting resulted in noticeable degradation of Stewardship Tier performance. It also allowed foreground events to potentially run for extended periods of time. In previous versions, foreground events would not time out unless the user session expired.

For 7.4.3 and later, the compilation debug setting is set to false. The executionTimeout property has been set to 300 seconds in the web.config file. These updates will cause all foreground events to timeout after 300 seconds.

NOTE: A message displays in the Quick Panel on the right of the Stewardship Tier if a foreground event times out.

For more information about this setting, refer to the Knowledge Base article Foreground Events Time Out After 300 Seconds.

NOTE: In large Stewardship Tier installations, there is a possibility that foreground events that previously took more than 1 minute 30 seconds will now terminate before they complete.

To prevent this from happening, update the executionTimeout setting in the web.config file. To override the default 300 seconds timeout, users can provide their own value. In the case of a custom application, users could also choose to change specific foreground events to run in the background.

Another update to the web.config file was added to help ensure the proper permissions are applied. The new tempDirectory setting is located after the compilation debug setting in the web.config file. In previous versions the temp directory was in the OS .NET folder structure and not guaranteed to have the correct permissions for the web site to operate. By defining the temp directory, the user can ensure the appropriate Stewardship Tier site permissions are applied. By default, this setting is set to the installation directory, but can be updated.

Additional SST Enhancements

  • The Stewardship Tier now supports Windows Server 2016 and Windows Server 2019; Windows Server 2012 is no longer supported. Refer to Requirements for more information.

  • The Stewardship Tier no longer supports 32-bit mode services. Clients running the Stewardship Tier in 32-bit mode are recommended to switch to 64-bit mode prior to upgrading to version 7.4.5 to allow sufficient testing before upgrading. If issues occur during the switch to 64-bit mode, it is easier to roll back the architecture switch than the entire upgrade. As a result of this change, any clients that need to extract from systems using 32-bit drivers need to contact SAP Support using component XX-PART-SYN to obtain a 32-bit version of Syniti Data Replication. This tool enables continued extraction from systems that rely on 32-bit drivers. Refer to Setting the Site and Service Platform Type to 64-bit and the 32-Bit Support Dropped for Stewardship Tier 7.3 knowledge base article for more information.

  • The Stewardship Tier is now certified to run the Microsoft Edge (Chromium) browser while certification against IE 11 has been discontinued. Due to browser technology constraints, functionality to create BDC Script Integrate templates directly from the Stewardship Tier (Integrate and Mass Maintenance) has been deprecated; however, BDC recordings can still be recorded in SAP and imported into the Stewardship Tier to use this functionality. Additionally, support for the creation of new SAP GUI Integrate templates has been deprecated. Existing GUI Script Integrate templates will continue to work. Refer to the Integrate and Mass Maintenance release notes for more information.

  • The following improvements were made to security auditing:

    • Security events, which can be viewed on the System Logs page, were updated:
      • The target entity name now displays when adding or removing Security Definition key values to roles and users.
      • The role name now displays for role deletion events.
    • Updates made to security (as in, insertions, deletions, and updates to the RoleWebAppGroup table) as a result of updates in Add-Ons are now logged in the security logs and can be viewed on the System Logs page.

Common

  • With the new addition of category values to Syniti’s REST API, category values can now be:

    • downloaded from data sets, goals, initiatives, missions, policies, rules, systems, terms and visions.

    • uploaded to new rules, terms, systems and data sets.

    • changed on existing rules and terms.

      Refer to Integrate the Stewardship Tier with the Knowledge Tier for more information.

  • SAP Application Server data sources allow available RFC Enabled Functions to be extracted. This extract process ran a foreground process that had the potential to timeout. To prevent this, the extract process has been updated to run in the background.

  • Support for SAP Gateway connections has been added to SAP Application Server data sources. Refer to Connect via a Direct Connection or a Gateway Connection for more information.

  • SAP Application Data Sources can now connect the SST to SAP applications using Secure Network Communications (SNC). Refer to the section Connect SAP and SST via SNC for SAP Application Data Source Connections in the Installation manual for more information.

Online Help

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

The following new topics are available:

The following new topics are available for Common:

The following new field descriptions topics are available in Common:

Collect

  • The structure of the dgTargetSouceTable has changed. The key fields for this table were previously Target, Source and Table. Starting with version 7.4.3, the table uses a key field that has a unique ID and the table now has a unique constraint for Target, Source, Table and TableRename. All child tables that have foreign key relationships to the dgTargetSourceTable have been updated to use the new unique id.

    Using Table Rename functionality, users can register multiple tables with large data sets (for example, BSEG) but with different Table Renames (for example Company Code). This allows users to extract data from target sources on a more granular level, pulling the correct data into tables named, for example, for BSEG_Company One, BSEG_Company Two, and so on.

NOTE: These changes to table structure will cause CTS packages, DBVT packages or any scripts used to populate the target source tables built on previous versions to fail. To fix the CTS issue, upgrade, then rebuild the package. Scripts and DBVT packages will need to be modified to use the updated key fields and table structures.

  • When packages with package types BOA RFC or SAP RFC are extracted, the Stewardship Tier now removes all trailing empty spaces in columns by default. The Remove Trailing Spaces option has been added to the Vertical View of the Tables page in Collect to allow users to select the desired behavior. When upgrading, extracts using BOA RFC or SAP RFC package types will have Remove Trailing Spaces set to false. This will ensure that extracts continue to function as before the upgrade.

  • On the Target Source Table Index Columns page, the page is now sorted by the Index ID.

  • On the Data Source Table Columns page, the page is now sorted by the Column Order

  • On the Copy Targets page, the “Target To” list box excludes the target in the “Target From” list box, as this scenario is not valid .

  • On the Table Errors page, added a link to the TABLE column to the Table page.

  • The following changes have been made to the Collect Tables page:

    • The Table Rename column was added to the Horizontal View.

    • The page order was changed to the updated key field, Target-Source-Table-Table Rename.

    • The Package Type field and the Table Rename field were moved from the Advanced Settings tab to the General tab on the Vertical View

    • The Build and Refresh and “Build Package” buttons will now be disabled if the selected table is marked as inactive

  • A new source connection type called ODBCPostGreSQL is available to help set up a PostgreSQL connection for data extraction.

  • If the WHERE clause for an SAP RFC or a BOA RFC is greater than 72 characters, the WHERE clause is now broken down into several lines based on the last white space character before the 72-character limit on each line. If there are no white spaces, a new WHERE clause line after the 72 characters is created. In addition, a validation error has been added to the Tables page to warn the user if they have a WHERE clause with 72 adjacent characters and no spaces. To troubleshoot, enable debug logging for Collect to see how the WHERE clause was split into several lines.

  • In order to better support the extraction of large data sets, changes have been made to the Stewardship Tier platform to ensure that data sets in excess of 2.1 billion records can be handled correctly. Notable changes to the product to support this change include the use of BIGINT (instead of INT) data types for fields containing record counts and the use of COUNT_BIG (instead of COUNT) to get table record counts.

  • To clean up unused columns and to resolve duplicate columns between the Data Source Tables and the Tables pages, the Data Source Tables page was removed. The Columns and SQL Commands icons from the Data Source Tables page were added to the Tables page under the General tab.

  • Removed the Target User Access page as it has been deprecated.
  • To simplify page design and make changing the schema of target source tables easier, the following changes have been made:
    • Navigation from the Target Source Group page to the Tables page is now direct, and no longer via the Target Source Tables page.
    • The Target Source Tables page has been removed.
    • The Vertical View has been removed from the Table Errors page, and the Package Built check box, and Indices and Rules icons have been removed from the Horizontal View.

    Integrate

  • Recording a BDC script to use as the basis for an Integrate template has been removed from the Stewardship Tier. This functionality depended on Internet Explorer 11, which is no longer supported. To create a BDC script to use as the basis for BDC Script template in Stewardship Tier 7.4.4, users can:

    • Create a BDC script using the SHDB transaction in SAP and import the script into Integrate. Refer to Import a BDC Script from a File for more information.

    • Copy an existing BDC script. Refer to Copy a Template for more information.

    • Use a BDC script created in a previous version.

  • Recording a GUI script to use as the basis for an Integrate template has also been removed from the Stewardship Tier, as this functionality also depended on Internet Explorer 11 support. New templates based on GUI recordings cannot be created in version 7.3 and later, but GUI templates created in previous versions of the Stewardship Tier can be used, as well as copies of GUI templates. Refer to Copy a Template for more information.

Information Steward Accelerator (ISA)

To allow users to have better control over the synchronization of failed data table changes between IS and ISA, a new feature called ‘Column Change Mode’ is available to be set at the Project Distribution Rule Binding level. This new feature allows users to select one of the following:

  • Inherit—Inherit the column activation status and priority from the associated IS failed data table

  • Inherit Ins/Del Only—Allow users to update the priority and activation status in ISA and only inherit new columns from IS or have columns deleted in IS removed in ISA

Refer to Modify the Format of Reports Available from the Report Data Viewer and View Rule Binding Inconsistencies for more information.

Syniti Data Replication

The 7.4.5 version of the Stewardship Tier is compatible with Syniti Data Replication 9.7.3.3.

Mass Maintenance

  • External Data processing can now use the IMAP email protocol to connect to the account used for both External Request Scenarios and for External Data Processing with an External Data role. By default, the email protocol is POP3. The setting is configured in the new PROTOCOL field on the External Data Email Accounts page.

  • Mass Maintenance templates can no longer be created from a BDC Script or GUI Script recording. Custom templates can be created, as well as templates based on Integrate templates. Refer to Create Templates for more information.

Resolved Issues

Advanced Data Migration

Console

  • Corrected an issue on the Load Cycle Execution Plan page that allowed users to enter a higher number in the DEFECT COUNT field (the number of records that failed to load) than in the OPPORTUNITY COUNT field (the total number of records). With the fix, a validation has been added to prevent users from saving this invalid record. [DSP70-1293]

  • Wave Load Cycles and Milestones are copied as part of the Wave Copy process. However; the copied Milestone used the wave / load cycle GUID from the original wave instead of the new wave. This issue has been fixed; the copied Milestone now uses the GUID from the new wave. [DSP70-1074]
  • Corrected an issue when processing multiple records on the Load Cycle Execution Plan page that had Warning messages. Accepting the Warning message only updated the status of the record on which the warning was accepted. The other records had an unknown status. In this fix, the associated validations have been changed to Messages ensuring that all records have the correct status. [DSP70-1086]

  • The behavior of the View Notice Indicator on the Load Cycle Execution Plan page has been updated to improve the user experience. Previously, the indicator displayed after the user clicked the Run Count Views icon, and only under certain situations. In this version, the icon displays with the tool tip "Opportunity and Defect Views Not Configured" after the user clicks the Update From Template icon. The user then clicks the Run Count Views icon, and the indicator displays tool tips if the views fail to run or if there are missing or changed configurations. [DSP70-1087]

Construct

Corrected an issue that occurred when adding a Full Construction source to a target. The resulting data construction pages and tables included zLegacy<KEY> columns that were added as keys on the construction page and could not be edited. Users were prevented from creating records on these pages. With the fix, the zLegacy<Key> fields are not included in the pages and tables when adding a Full Construction source to a target. As is standard, full construction expects records to be populated with data in values that relate to the target system. If data is being constructed for a record that has not had a target number generated yet, i.e., not loaded, a legacy record number can be used. During the migration process, this value can subsequently be translated to a target value using cross reference tables. [DSP70-949]

Target Source SQL Automation

Fixed an issue that caused an error to display when a user clicked the Map Source icon on the Automation SQL Target Source page. With the fix, when the user clicks the Map Source icon, Map’s Target Sources page displays with details about the source selected on the Automation SQL Target Source page. [DSP70-1290]

Map

  • Corrected an issue that caused the generated SQL for the Xref mapping to use an incorrect value for the join when using a look up table with multiple keys. With the fix, the SQL generated for validation reports related to multi value key lookup tables includes the correct table join criteria. [DSP70-1092]

  • An error occurred when syncing from Target Design to Map if the user followed this particular navigation path:

  1. Click Design in the context bar.

  2. Click the Sources icon for a target.

  3. Click the Mapping icon for a source.

  4. Click the Sync from Target Design icon in the Page toolbar.

    The issue has been corrected and the sync process runs as expected when the user follows this navigation path. [DSP70-1101]

  • An issue occurred in Map and a validation warning was thrown when:

  1. Target Design had been completed for a table and a source was added to the table in Target Design.

  2. The target was then synced to Map.

  3. In Map, the user selected a source table from the assigned source to assign to the target on the Target Sources page.

NOTE: The selected sources table had at least 1 primary key and was not currently in the source System Type.

  1. The user saved the record.

NOTE: The validation warning “No key was found for this Source Database Object” displayed.

With the fix, the record saves successfully in this scenario. [DSP70-1177]

AutoGen

  • The AutoGen.dbo.boaGetCranPortSelectColumnList scalar function did not work with sources that had spaces in the key field names. The function has been modified and now works as expected. [DSP70-1096]

  • The Rebuild – Alter Table and Drop & Rebuild Views And Stored Procedures option for the AutoGen Level on the Automation page has been updated (and renamed) to no longer drop and alter the source table and target tables. Only views and stored procedures are dropped and rebuilt. [DSP70-1218]

Transform

  • Fixed the hardcoded timeout that caused issues when rules with large amounts of data ran in Transform. The hardcoded value of 9999 has been removed. The stored procedures use the value in the Command Timeout field on the Vertical View of the Data Sources page in System Administration. [DSP70-1461]

    NOTE: After upgrading to 7.4.5 and later, clients may need to increase their data source timeouts if there are timeout issues when executing rules in Transform.

  • Fixed an issue that caused a timeout when a view was registered as a target source and it took longer than 30 seconds to execute. With the fix, the timeout does not occur and the execution completes as expected. [DSP70-1039]

  • 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]

Enhanced Migration Reporting

  • When a report was added to a group on the Your Groups page, in order for the user filter to be applied to the report, the report had to be executed and then either the user filter had to be validated or a new user filter had to be created. This issue has been fixed and user filters for a new report added to a group now function as expected: as long as the user filter has been set up, the filter is applied during the first execution of the report. [DSP70-1001]

  • Previously, if there were duplicate records on the Data Quality Score Thresholds page, then duplicate records appeared on the Target Table Threshold and the Target Table Column Threshold pages. This duplication was caused by incorrect join conditions on the webDQSThrewsholdList view. To fix this issue, the view now has joins on the “Name” field. [DSP70-923]

  • The Process and Process For All Users icons on the Your Groups page were always inactive because the Monitor Group Security Definition Events (webSecurity_GroupUserAdd), which inserts records into the ddGroupUser table, did not have the boaStatus field populated. To fix this issue, the webSecurity_GroupUserAdd stored procedure was updated to default an initial value of 0 (New or Dirty) for boaStatus. [DSP70-925]

  • A report can appear multiple times on the Your Object Reports page because it could be assigned to multiple groups, have different filters applied, and be executed independently. To communicate the duplication to users, a Report Warning icon has been added to the Your Object Reports page with the following options:

    • No warnings
    • Report appears multiple times because it has different User filters in different Groups [DSP70-930]

  • The Columns button on the Report Target Tables page displayed an incorrect count. The count was the number of target table columns for all reports. The count now displays the correct value: the number of target table columns assigned to the target table for that specific report, i.e., the number of records on the Report Target Table Columns page. [DSP70-1009

Information Steward Accelerator

Resolved issues that erroneously reset the Priority for columns on the Activate Columns page which reset changes made in ISA. Previously, the Priority value and Active status were reset when the Activate Columns page loaded, when a user clicked the Sync All button on the Project Summary page, or when the Sync All Projects service page ran. In each case, all active columns were deleted and then fetched again and reinserted into the tables using the order from ISFailedData's information schema. With the fix, users are able to decide whether they want to automatically inherit IS column changes to whether to only inherit new column additions or column deletes. [DSP70-1257]

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

  • Fixed issues that caused slow Excel Import performance when inserting and updating records on a page with a large number of records already added to the page. For example, before the fix, an Excel import to update 10k records over a table with 20k records took 2 mins 28 secs. With the fixes, this import process now takes 23 secs. [DSP70-1281]

  • Fixed an issue that occurred when adding a translation to a page in a custom WebApp that had no custom catalogs registered to it. The issue occurred for a user who was not using a Design license. Previously, when the user clicked the Edit Page Help icon for a column on the Pages page, a record could not be added, as the Stewardship Tier required the user to select a catalog from the Catalog ID list box. Because the custom WebApp did not have any catalogs registered to it, the list box was empty. With the fix, users can add a translation to a column property on a page in a custom WebApp by clicking the Edit Page Help icon on the Pages page. [DSP70-365]

  • Excel Integration functionality in conjunction with field controls has been updated so that the appearance and behavior of the Excel spreadsheet columns are aligned with the page columns on which they are based. Additionally, when using Excel templates that were not created by the Stewardship Tier, under some circumstances, users were able to add or change data in error.

  • The key changes that have been made are:

    • Fields hidden by Page Control Views were previously available in Excel Integration templates and could, in certain circumstances, permit data to be updated when a template was imported into the Stewardship Tier. With this update, hidden fields that are not primary keys are excluded from the Excel Template.
    • Under certain circumstances, fields disabled by Page Control Views could update data when a template was imported into the Stewardship Tier. With this update, disabled fields no longer allow update or addition when a template is imported.
    • When using Excel integration, in cases where a Horizontal view included fields that did not belong to the underlying table, the fields were not included in the spreadsheet. With this change, these fields are now included in the Excel template but cannot be edited. The import process also excludes these fields.

  • NOTE: Pages developed in custom WebApp Mass Maintenance (previously dspCompose) that use Excel Integration may now function slightly differently. Therefore, when upgrading to this release or above, all such pages should be thoroughly tested and adjusted accordingly. Refer to Exclude Columns from Excel Integration for more information. [DSP70-1068]

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:

  1. 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

  1. 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]

  • When a report is executed in Transform with the Publish option enabled, .xlsx files are generated in the Transform directory and in the C:\Windows\Temp folder on the application server. Previously, these files were not deleted, which caused the system to run out of space quickly. Now, these temporary .xlsx files are deleted from the C:\Windows\Temp folder after the report is generated. [DSP70-1229]

Assemble

Corrected an issue when using multi-threading on a source refresh that caused the processing to hang. If the number of records in the CranPort package was large (6 million records) and the package was segmented, sometimes, the segmented table's job never left the job queue. Even though the table's extract completed, the refresh job remained "spinning" in Collect. The cause was Assemble writing logs out of order. With the fix, when Assemble writes logs, it waits until the rest of the log entries, run by background threads for that task, have finished before writing the next log entry. [DSP70-1330]

Common

  • Fixed an issue that caused the Status icon on the System Types page to remain in Processing status after a System Type import, even after the import had completed successfully. Now, the correct status displays when the import is complete. [DSP70-1102]

  • 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]

Collect

  • Corrected an issue introduced in 7.4.4 that caused the DURATION field on the Download Metrics page to always display 0 after a table refresh. The value in this field should be identical to the value in the DURATION field on the Tables page. With the fix, the DURATION field displays the correct amount of time it took to complete the table refresh. [DSP70-1473]

  • Fixed an issue in Collect when adding new tables (on the Tables page) to a Target Source that was configured to use the SAPAPPSERVER Source Connection type. If the default Collect Package Type was set to BOA RFC, newly added tables were being incorrectly created with the "SAP Data Services using RFC" package type. With the fix, the correct "default" package type is used when adding new tables to SAPAPPSERVER Target Sources. [DSP70-1188]

  • Fixed an issue when using SAP RFC or BOA RFC package types to download tables. Even though the Refresh was marked as successful in Collect and in the Job Queue, the process ended with errors that were not displayed. The value in the Record Count field on the General Information tab on the Vertical View of the Tables page and the number of records in the Table in SQL did not match the record count that should have been extracted when the Refresh process successfully completed. With this fix, if there is a failure during the extraction, the extract will terminate and the reason for error will be available. [DSP70-1226]

  • The table rename option did not work for DBMoto and Data Services package types; the issue has been resolved and table rename now works as expected. In addition, the Table Rename field was removed from the Tables page for Syniti Connect, Excel Import and SAP Text packages because the field was not applicable to those package types. [DSP70-1054]

Integrate

Fixed an issue that caused a posting to fail and a Timeout error to display when posting large data sets. The error occurred if:

  • The process post’s underlying view contained a number of records that took longer than 30 seconds to process, and

  • The process post’s WHERE clause did not limit the maximum posting time to 30 seconds

With the fix, the Timeout error does not display in this situation and large data sets can be posted. [DSP70-1278]

Mass Maintenance

Previously, users received an error message when trying to save an electronic signature record if the Comment exceeded 200 characters. The record was saved when the error was disregarded, but the Comment itself was not saved. Now, a validation message displays when the record is saved if the comment exceeds 200 characters. Users must reduce the Comment to fewer than 200 characters in order to save the record. [DSP70-1189]

Known Issue

In Collect, on the Tables page, the Package Type of Syniti Connect displays as IG Universal Connect in the Package Type list box. This option will be updated in a future release.

Enhancement Requests From Users

  • Updated the Collect topic Encrypt CranSoft® DataSource Password with a link to the System Administration topic Encrypt Password for CranSoft® DataSource.
  • Clarified the Page Design Guidelines topic with this note: "A custom page built in the Stewardship Tier will not operate correctly when the framework can’t determine the page’s primary key(s). The framework can determine the key(s) automatically when the page is built based on a table with a primary key defined. The platform cannot determine the key(s) automatically when the page is built on a view or on a table with no primary key. In this case, a key must be assigned to the page."

  • The Maximum Retry Interval description throughout Automate was updated to be clearer with a concise example.

  • Updated Data Control Views to clarify how to control a key column with a control view.
  • The Recompile Objects field description on the Data Source Instances page was updated to include a note that says CLR functions are not supported.
  • Added a reference to the Developer Toolkit Guide to Register Plugins to Import and Export Files.
  • Added boaLockType to list of reserved columns in Create Tables in SQL.

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.

Previous Versions of Help

Help Build Date:April 06, 2022 03:10:14 PM