What's New in SAP Accelerators by Syniti 6.7

This topic contains:

WARNING: Any additions or changes users have made to CTS configuration (Admin > CTS >Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

Please contact if you would like assistance with this activity.

Enhancements

CTS Process

  • A user can build a CTS Package by selecting that wave only in the packing list. The package contains all of the items required to successfully promote the entirety of a Migration Wave (and all its dependents) to another environment.
  • The CTS Packing List Summary and the CTS Packing List by Config Item pages have been added to streamline the process of excluding items from the packing list. Refer to Review Packing List to Exclude Specific Items in the System Administration help for more information.
  • A package can contain objects from multiple data sources.
  • The DSP now uses a crawler to set up object dependencies and installation order automatically, based on the configuration on the pages accessed in Admin > CTS > Configuration.

NOTE: CTS configurations for delivered WebApps must not be updated. If CTS’ing a custom WebApp, the baseline configuration must be set on these pages. Refer to Set a Baseline Configuration for Shippable Items in Custom WebApps.

Advanced Data Migration (ADM)

Map

  • Value Mapping values can now be entered outside of the DSP® and imported into Map. The Value Mapping (Legacy to Target) page now has Excel Integration and Bulk Execution enabled by default. This allows a user to download a template spreadsheet for data entry completion outside of the DSP®. The value mapping values can then be imported into Map from the spreadsheet. Refer to Perform Value Mapping, Use Excel Integration and Use Bulk Execution for more information.

SQL AutoGen

  • It was difficult for migration developers to know whether the SQL AutoGen logs they were looking at had just been written or were historical and therefore from an execution prior to changes they had just made. Now, the Added On and Added By dates are displayed on the Horizontal View of the AutoGen SQL Log page to improve clarity.
  • In previous versions, fields with a zLegacy prefix were automatically excluded from the auto-generated CranPort package, which imports data from sdbConstruct to the dsw databases. In some instances, these fields could be required downstream and removing them would not produce a desired effect. With this release, all fields (including fields that start with zLegacy) in the dcs page table are included in the CranPort packages and are imported into both the sdb source table and the dsw source table.

Data Stewardship Platform (DSP®)

  • When the installation license Hardware IDs did not match the currently licensed Hardware ID, it caused users to be denied access to the DSP®. With this release, users can continue to access the DSP® for 14 days while waiting to receive an updated license.
  • Many client sites required the use of an SAP Message Server when communicating with SAP via RFC. On these sites, DSP® was previously unable to extract tables or load data properly. With this release, SAP Message Server Connections in Collect, Common and Integrate are now supported.
  • Users could not easily check to see which job queue a job had run on. So, the Queue Name has been added to the Horizontal Views of the All Jobs and Jobs (Failed) pages under Admin > Resources.
  • On the CTS Items, CTS Item Keys, and CTS Packing List pages, the Description field displays the text description so that users can easily identify those items in the Packing List.
  • Previously on the WebApp Customization page, no count appeared on the Catalogs, Custom Links, or Pages icons. With this release, counts appear for the underlying elements and users can easily identify web applications where customizations have taken place.
  • Added the help topic Add Phrases to Catalogs.
  • The icons on the CTS Configure page now display counts of the number of records on the underlying pages to assist users while navigating and evaluating data.

Online Help

  • Added documentation for the Vertical View of the WebApps page.
  • Added documentation for the Database Types page.
  • Added documentation for CTS Configuration pages.

Resolved Issues

Advanced Data Migration (ADM)

An issue occurred when users copied an object from the Process Area : Object page, and only one target of the copied object was shown in the destination wave in Map. The rest of the targets were inserted in cMap.dbo.ttTarget without a DataSourceID, and on the source wave instead of the destination wave. With this fix, all targets belonging to the copied object appear in the new Wave, across Console, Design, Map and Transform. [DSP-9540]

Map

  • An issue occurred when adding System Type joins that caused target sources with over 500,000 records to take over a minute to save. With this fix, target sources with System Type joins save quickly. [DSP-9807]
  • When users mapped a field as Construction, a Construct page was automatically generated with the key fields disabled by default. As a result, key fields usually required for populating data were excluded from Excel Integration download files. With this fix, key fields are no longer excluded from the Excel Template even if they are not editable. [DSP-9417]

Target Design

  • A stored procedure used in Map that automatically generated validation views for Construct pages assumed there was a single key for the lookup table. This assumption meant that any validation view generated for a multi-key lookup table had to be manually corrected in SSMS before the associated Construct page could be used (without the user receiving a warning). With this fix, only invalid records prompt a warning message when a multi-key lookup table is associated with a Construct page. [DSP-9227]

  • An issue occurred that prevented users from saving records on the Target Lookup Table page. When attempting to add lookup tables with a multipart key, the Multi Value Field Lookup Table Value Column field was required, but the values in that list box did not display until the record was initially saved. In other words, it was not possible to save the record because it was not possible to update the field on the Horizontal View. Instead, an error message displayed and the record that was being added no longer displayed. To correct the issue, the Target Lookup Table page switches to the Vertical View when the user clicks Save. The Multi Value Field Lookup Table Value Column field can then be updated from the Vertical View, and the record can be saved. [DSP-9509]

Transform

  • If there were line feeds in one of the fields in the results of a view, a new row was created when downloaded in Excel format. With this fix, the downloaded Excel file has one row for each record in the view result. [DSP-7311]
  • In Transform, when downloading a report to Excel, if the Report Column Delimiter field was set to Comma and Report Column Qualifier field was set to DoubleQuote in the Report Settings section of the Transform tab on the Parameters page, and the value contained a comma, the value would then be split into two columns. With this fix, if there is a comma contained in a value wrapped in double quotes, and the Report Column Delimiter is set to Comma and Report Text Delimiter is set to DoubleQuote, the comma is not used as a column delimiter. [DSP-7526]
  • An issue occurred where reports with fields that had a double quote (") character in the first column produced a MaxBufferSize data parsing error. With this fix, the reports generate without issues. [DSP-9052]
  • An issue occurred where reports with fields that had a ž character produced a MaxBufferSize data parsing error. With this fix, the reports generate without issues. [DSP-9233]

SQL AutoGen

  • There was an issue where Data Services reports were not registered in Transform with the correct naming convention. They were created in SQL with underscores, and users had to change the registrations of these reports on the table every time they were generated to get them to process properly. With this fix, when AutoGen creates all Data Services report views in SQL, it registers those reports in Transform, and reconciles the names to the SQL view names. [DSP-9421]
  • In AutoGen, the [WaveProcessAreaID] datatype was set to NVARCHAR, which led to lengthier processing times when conducting Transform target execution. By changing the [WaveProcessAreaID] datatype to the appropriate UNIQUEIDENTIFIER (in all the st% tables), users are now able to conduct Transform target execution more efficiently. [DSP-9465]

dspCompose™

Any dspCompose™ Archive Compare tables - rtxxxCompare - that were created prior to 6.6 have ArchiveID defined as an Identity field. In 6.6, the Compare tables do not have the ArchiveID as an Identity field. As a result, when Requests for these templates were posted, the stored procedure that moved data into rtxxxCompare table during the Posting process would error out when attempting to move data into rtxxxCompare tables.

The stored procedure that moves data into rtxxxCompare tables has been modified to detect if the rtxxxCompare table still has ArchiveID defined as an Identity field and accommodates that table definition so data is successfully moved into the rtxxxCompare table and posting completes successfully.

NOTE: A separate, stand-alone stored procedure webTemplate_OneTime_FixComparisonApprovalArchiveTableUpd is provided with 6.7 (but not inside the standard DSP® setup) along with instructions for the stored procedure. This stored procedure may be manually executed for individual templates to correct the schema definition of pre-6.6 Template rtxxxCompare tables.

If the Template was created in 6.5.6, a unique nonclustered index will have been created on the ID field of the rtxxxCompare table. Either drop that unique nonclustered index and create a nonunique nonclustered index, or execute the separate stand-alone stored procedure webTemplate_OneTime_FixComparisonApprovalArchiveTableUpd to correct that issue. [DSP-9336]

Data Stewardship Platform (DSP)®

An issue occurred that caused the DSP® to crash when users tried to build an SSIS package after installing a new version of SQL Client Tools on their application server. With this fix, all currently supported versions of SQL Server work with their associated SQL Client Tools and SSIS packages build without issues. [DSP-9412]

Collect

  • An issue occurred in Collect while using any RFC Connection type with an SAP Message Server where the package would not get built. With this fix, RFC type packages build with or without using a message server. [DSP-6070]
  • An issue occurred in Collect where the SSIS option was not populating in the Package Type list box for Target Source tables. With this fix, SSIS appears in the Package Type list box. [DSP-9497]
  • An issue occurred that caused an error when trying to build SSIS packages using ODBC data source types. With this fix, a dedicated ODBC connection object has been created and users can successfully build SSIS Packages with the DSP®, configured in either 32-bit or 64-bit mode. [DSP-9270]
  • In Collect documentation, the security required for a user to receive a workflow notification when a table failed to download was described incorrectly. A user must be assigned to a security role that has the Collect WebApp group WorkFlowFailureAll or WorkFlowFailureByTargetAccess assigned to receive these emails. [DSP-9717]

Common

  • An issue occurred on the Data Source Registry page when users set up a connection to SAP Message Servers. The connection failed and produced a configuration parameters error. With this fix, users can connect to the SAP Message Server without issues. [DSP-8008]

Integrate

The process template connection for Integrate is now a shippable item and can be CTS'ed independently of process templates. [DSP-10240]

Information Steward Accelerator (ISA)

An issue occurred where when distribution schedules in ISA did not match rule scheduling in IS, reports with old record scores were sent in workflow attachments. With this fix, the report record scores sent with the workflows are current. [DSP-9741]

Enhancement Request from Users

In dspMonitor™, the Implication and Comment fields on the Vertical View of the Repository Reports page have been changed to Text Areas so that users can record all necessary information. [DSP-6078]

Online Help

On the Data Sources page in System Administration, the Server Address field has been revised to inform users to avoid using the IP address of the server as the Server Address property. For the CranSoft data source, the Server Address property must be the host name of the database instance and cannot be the IP address. Although the IP address may test successfully, if the IP address is used for the CranSoft data source, then Collect downloads do not return the Record Count and the rules registered to the Collect table will not execute. [DSP-9586]

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

NOTE: 6.5.4 and 6.5.5 versions of SAP Accelerators by Syniti were not released. The immediately prior release to 6.5.6 was version 6.5.3.

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

Help Build Date:March 08, 2022 12:37:51 PM