What's New in Syniti Solutions 6.5.2

NOTE: DSP® version 6.5 implements a new licensing scheme that ties the license key to a hardware ID specific to the application server on which DSP® is installed. This license key will therefore not work on other machines. In addition, hardware changes to the server, including virtual machine reconfiguration, may cause the license to be invalidated. In the event of a hardware change, server move, or other action that may require a new license to be issued, please open a Support message via SAP Solution Manager using component XX-PART-BOA to request a new license. The request for a new license should be made a minimum of 2 business days before the license is needed to allow time for review and approval.

This topic contains:

The following issues have been resolved in version 6.5.2.

New Features

dspMigrate™

SQL AutoGen

SQL AutoGen creates basic objects used by the migration process (tables, rules and reports) so that users can focus on addressing complex requirements. 

All objects created using SQL AutoGen are written to the data source defined for the object in Console (Process Area > Objects > Vertical View > Data Source ID).

Access SQL AutoGen by clicking the gold Automation tab in the Quick Panel.

Refer to SQL AutoGen for more information.

With SQL AutoGen these tasks can be performed automatically:

 

Fiori

Display and visualize the key activities in a Data Migration given a single pane of glass view into the status of the migration by deploying the Fiori add-on into your SAP HANA Cloud Platform (HCP) account. Using the Fiori user interface, the key metrics of the migration are extracted from the DSP® and displayed using Fiori. These metrics and details can be viewed on a mobile device as well as a workstation and have complete drill-through capabilities directly into dspMigrate™.

Map

A user can profile a source data source on the Vertical View of the Target Sources page or an Update Row source data source on the Vertical View of the Target Sources (Update Row) page. Once the profile has run, the user can view the profile results such as record counts, unique values, or field data types.

Target Design

A new Visibility column has been added for both Natural and Utility fields. Setting the visibility determines whether a field is available to be mapped on the source or target pages. Refer to Set Visibility for Mapping of Target and Source Fields and Set Visibility for Appended Utility Columns for more information.

Transform

Transform provides measurable advantages in the Data Preparation phase of a data migration project. The tool cleans, manipulates and reports on data, and exports the data so that it can be loaded into a target ERP system using a load tool.

Use Transform to register target rules, target remediation rules, and target reports. Transform also creates Target Source rules and Target Source reports. A user can audit updates to target data as a result of rule processing, debug rules and reports, and view dashboards that display a count of active source rules, source reports, target rules and target reports by Wave and Process Area; the number of processes running for reports broken out by report type; and the count of changes to all object types in the Wave and Process Area.

Access to report data can be controlled at the report level by restricting access to reports, or through user filters assigned to a report.

Refer to Transform for more information.

dspCompose™

A user can access the black dspCompose Requests tab on the Quick Panel to navigate among active requests for which the logged in user has access. Refer to View Your Active Requests Details for more information.

Data Stewardship Platform (DSP)®

Common

  • Target system connections and the user credentials for these connections are now set in Common. Refer to Establish a Connection to a Target System for more information.
    NOTE: This feature replaces Back End Authentication that was previously established in Integrate and dspCompose™.
  • An Administrator can import a System Type from any system. The user can add a System Type using that system’s data dictionary to create a System Type Model with the correct SQL. The process imports table descriptions and field descriptions and registers check tables to fields. Refer to Import a Data Source for more information.
    NOTE: The SAP and DE System Types are included with the DSP®.
  • Profiling and duplicate detection have been added.

Profiling

Profiling is a quick and easy method to perform an assessment of data contained within a database. The goal of data profiling is to save hours of research effort by listing all database information in one location. It is important to note that data profiling does not replace viewing and analyzing data, but is considered a value-added activity for reporting to the client and can provide useful information at the beginning of a Data Migration project.

The following elements are available for all profiled databases:

  • A list of all tables in the database
  • A list of all columns within each table with defined Data Type, Length and Table Order
  • A frequency distribution of values for each column
  • A minimum and maximum value for each column
  • A number of blank, null or empty values for each column
  • Indication of unused tables and fields

Duplicate Detection

The duplicate detection feature provides an easy method to identify and resolve duplicate data. After the user creates and register the objects (tables and views) that contain the data to be analyzed for duplication, the process finds potential duplicate data and displays it on a results page. The user can configure this results page as needed. The user reviews the results and identifies duplicate records to decide if the record is a true duplicate, if the record must be reset, or if the record is not a duplicate.

Integrate

  • A user can configure After Post rules that run after the process template executes successfully and before the next process template begins processing (if posting with a multi-template process). After a process template that has an After Post rule registered posts successfully, the data is passed to the next dependent process template as an input parameter. Refer to Register After Post Rules to a Process Template for more information.
  • The SAP Data Services Job  template type has been added to Integrate. It uses a Data Services Job (consisting of a Data Services Repository and a job name) when posting request data to a target system. Refer to Post Data Using an SAP Data Services Job for more information.
  • A user can add a Custom template in Integrate for posting to any application. Refer to Post Data Using a Custom Template for more information.

Enhancements

dspMigrate™

Console

Map

  • In Value Mapping, when refreshing the target values, a warning displays if the language or client fields are entered for the lookup table but the language or client value fields are not populated for the Wave. These fields are maintained on the Waves page's Vertical View in Console.
  • A Migration Developer can designate a system other than the target system for check tables. Refer to Use Check Tables from Different Systems While Value Mapping for more information.
  • The process for establishing relationships has been updated. External sources, Add Row sources (formerly primary sources), and Update Row sources (formerly secondary sources) can now be used when creating relationships. Refer to Work with Sources for more information.
  • The Submit All icon on the Field Mappings page can be used to submit any mappings with a Mapping Status of In Progress and any mappings with a Mapping Status of Complete (if that Mapping Status was set manually by the user but had not yet been submitted).
  • On the Mapping Approval page, a user can click the Complete icon to approve the selected mapping(s) and set the Rule Status to Complete.
  • An Update Row source that is a table can now be added. Rules can be created for this Update Row source table which convert the data before it is processed by the main source rule. The table can also be used as a snapshot of data for results validation. Refer to Add Update Row Sources that are Tables for more information.
  • Mapping Status and Rule Status values and the Mapping Approval process have been updated. During the Mapping Approval process, the Mapper submits a mapping for review. When submitted, the mapping status is set to Complete. The Developer can approve the mapping, which sets the Rule Status to In Progress. The Developer can also select an option to set the Rule Status to Complete when approving a mapping.
    Mapping Status values are:
  • Pending Review – The default value indicates that a mapping has been either:
    • Synced with Target Design but work on the mapping has not begun.
    • Synced with Target Design, has been worked on, but the saved changes did not pass validations.
    • Reset by a Mapper or a Developer. Mappings can be reset on the Field Mappings page or on the Mapping Approval page.
  • Design Required – The mapping has been reviewed by a Developer and rejected on the Mapping Approval page. The Mapper must update the mapping and submit it again.
  • Complete – The mapping has been submitted when the Mapper has finished creating the mapping and clicks the Submit or Submit All icons on the Field Mappings page.

Rule Status values are:

  • Pending Review – The default value indicates that a mapping for the rule:
    • Has not yet been submitted.
    • Has been submitted and is waiting for Developer review.
    • Has been reset by a Mapper or a Developer. Mappings can be reset in AutoGen on the Automation SQL Field Mappings page, in Map on the Field Mappings page, or on the Mapping Approval page accessible from the Quick Panel.
  • Revision Requested – The mapping for this rule has been reviewed by a Developer and rejected on the Mapping Approval page. The Mapper must update the mapping and submit it again.
  • In Progress – The mapping has been approved on the Mapping Approval page.
  • Complete – The mapping development has been completed. A user clicked the Create and Complete icon on the  Automation SQL Field Mappings page or the Create All Rules icon on the Automation page. A Developer clicked Complete on the Mapping Approval page.

Target Design

  • The Derived from Source field has been added to the Target Fields page. It allows the user to include or exclude a field from an insert rule when building the rule in SQL AutoGen.
  • When a lookup table is registered in Target Design, it is registered as a source table with a status of Documentation and a rule priority offset of 50000 so that it is sorted last. Documentation sources are not processed but are a reference item to see all the sources of data.

dspCompose™

  • On the Template (Role Excel Column Control) page, the Include, Exclude, and Exclude If Null options have been moved to the toolbar to allow updates to multiple records.
  • If columns have been previously imported and a new column is added to a template, when the columns are imported again, the new column is added but there are no updates to existing columns.  
  • On the Template (Post Message Tables) page, a user can identify the Integrate template ID specific to the post message tables if a dspCompose™ template is associated with a multi-template process in Integrate.

Data Stewardship Platform (DSP)®

Collect

  • For a Target Source, the data store created in Data Services now has the Target Source name as part of the name when using an SAP Data Services using RFC package type (for example, <DS_SAP_SOURCE1_RFC>) to allow multiple sources to download to a single DS repository.
  • A validation message has been added in Collect, on the Tables page, for Data Services or Data Service using RFC package types to let the user know if a data services repository is not assigned on the Targets page’s Vertical View.
  • The Data Services using RFC package type can only be used by a Target Source with a connection type of SAPAPPSERVER. The Manual Data Services package type is now available for Data Services connections.
  • On the Tables page’s Vertical View Advanced Settings tab, a user can now edit the package name for a Manual Data Services package or accept the default name for the package.
  • When a table is added to a Target Source with SAPAPPSERVER as a source type, the package type now defaults to SAP Data Services using RFC regardless of the package type set in Common on the Parameters – Collect page > Package Info tab.
  • A Do Not Delete check box has been added in Collect on the Target Sources page's Vertical View so that a user can choose whether or not data is automatically deleted from the target table when the target data is built and refreshed. This option has been added to support change data capture with Data Services.
  • In Collect, <source> has been added to the name of SAP RFC connections to allow multiple connections to SAP in a single Data Services Repository.

Excel Integration

  • A user can now update data in the DSP® from an Excel spreadsheet created by the user (based on the current DSP® page) or from a spreadsheet previously downloaded from the DSP®. Refer to Import Data for more information.
  • The default values from the page are now applied for records inserted via Excel Integration. Refer to Import Data for more information.

Integrate

In Integrate, the Delay Between Records field has been added to the Process page's Vertical View. It allows the user to set the amount of time, in milliseconds, that passes after processing of one record is complete and processing of the next record can begin.

Online Help

A glossary has been added.

Resolved Issues

dspConduct™

  • An issue occurred when a user created a request role validation that used the SPRAS field in SAP to filter the validation report by language. The SPRAS field was aliased as the boaSAPLanguage field, which is a reserved field that should not display to the user. boaSAPLanguage did display on the validation report. With the fix, this reserved column no longer displays. [DGE-989]
  • An issue occurred with the Active in Scenario Role setting for a task. When the setting was disabled for a Review or Post type task, requests based on the scenario still included the task. With the fix, only tasks marked as Active in Scenario Role are included in requests. [DGE-992]
  • An issue occurred when a page created in a Content WebApp used multiple tasks within the same role. When a user navigated to the Content WebApp page from the Request Role Task page, the control views underlying the Content WebApp page did not filter as expected and data did not display correctly. The Task ID had not been used as a filter when accessing the Content WebApp page from the Request Role Task page. The Task ID has been added as a filter, and when the user clicks the TASK ID button to access the Content WebApp page, the page data now displays correctly. [DGE-1007)
  • An issue occurred when:
    1. A scenario with dependent roles was configured such that when an Application role (e.g., Role A) was finished, the dependent Application role (e.g., Role B) was also finished.
    2. A request based on that scenario was processed by the Application role (Role A) and the user clicked Finish.
    3. A validation error displayed for the Application role (Role A) and the user corrected the error.
    3. The user clicked Finish again for the Application role (Role A).
    The workflow did not process correctly and the dependent role (Role B) was not finished. With the fix, in this scenario, the dependent role is finished when the user clicks Finish for the Application role after correcting an error. [DGE-1003]
  • An issue occurred regarding the content of workflow emails sent to the Review role. If a user updated multiple records in a table, the changes to only one record displayed in the workflow email. With the fix, all changes associated with the request display in the email sent to the Review role after the Application role is finished. [DGE-991]
  • An issue occurred during audit data collection for a specific page layout. If a task was performed on a Header/Detail page (e.g., pages A and B), and the detail page (e.g., page B) is also a Header/Detail page, changes to requests entered on page B were not tracked. The Review role could not see the list of changes while reviewing the request, as no audit data was collected. With the fix, audit data is collected for child pages that have a Header/Detail layout. [DGE-1004]
  • An issue occurred when viewing the Review Role Audit Details page. Columns that were marked to display on this page (i.e., the INCLUDE IN RECORD KEY check box was enabled for the columns on the Audit Table Column Registration page) did not display data on the Review Role Audit Details page. With the fix, the data for these columns displays and the Review role can now view the changes to the request. [DGE-1006]

Data Stewardship Platform (DSP)®

  • The LinkTag feature allows the page Designer to link to another page and pass an identifying string (stored in the Link Tag field) in order for that page to conditionally choose a Page Control View (PCV) by name. For example, webMyTable#LinkTag#Pcv can become webMyTable#LinkTag1#Pcv or webMyTable#LinkTag2#Pcv. An issue occurred when the wrong PCV was used and the identifying string (the value of the Link Tag) was not maintained throughout the usage of the page. With this fix, the value of the LinkTag is always maintained and the correct PCV view is used. [DCR-595]
  • An issue occurred when the Validation icon was clicked and the pop-up window contained no errors. With this fix, the pop-up window displays with any and all validation errors. [DCR-579]

Collect

Fixed an issue in Collect which affected Oracle replications in DBMoto®. [DSP-6741]

Common

An issue occurred where the import event on the System Type Import page did not check for whether or not a check table entry already existed for a field. It continued to add them resulting in duplicate entries. With this fix, there are no duplicate check table entries. [DSP-7056]

System Administration

The issue of an exception being thrown during an Excel file upload when the drill down criteria contained a column which did not exist on the underlying table for the page has been fixed. [DCR-576]

Transform

  • When Generate Documentation was enabled, an error occurred when the object, target, or Target Source table name was more than 50 characters long. With this fix, the object, target and Target Source table names are allowed to be up to 128 characters. [DSP-7128]
  • An issue occurred where the segmented reports displayed the total record count for the report as if it was not segmented. With this fix, each of the segmented reports displays the record count for the individual report. [DSP-6035]
  • An error occurred when special characters were used in segmented reports. The report would not save, validate or run successfully. With this fix, the report runs successfully. [DSP-6505]
  • An error occurred when attempting to execute the Source Rule in Transform due to the EscapeObjectName function used by the framework. With this fix, the Source Rule executes without error. [DSP-6523]

Enhancement Requests from the User Base

Data Stewardship Platform (DSP®)

 

WARNING: Customizations made to any component of thedelivered 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 VersionsPrevious Versions

NOTE: A 6.4 version of Syniti Solutions was not released. The immediately prior release to 6.5 was version 6.3.1.