What's New in Syniti Solutions 6.0.3

This topic contains

New Features

Common

  • System type table copy functionality. Refer to Copy a System Type Table.

  • ReadOnly WebApp group.

  • Rule Field field on the System Types – Table Fields page. This field marks a field as Rule Only. Refer to the Common field descriptions.

 Console

  • Auto Set Not Used for Multiple Sources parameter. This field controls whether Map updates the ACTION column to “Not Used” for primary and secondary source mappings where the action has not been set (i.e., the ACTION column is blank). Refer to Set Parameters for Map, Transform and Construct.

  • Move targets from one object to another functionality. Refer to Move a Target to Another Object.

  • ReadOnly WebApp group.

dspCompose™

  • CTS for Org Units, Roles, Teams, and Templates.

  • ReadOnly WebApp group.

Map

  • Auto Update Not Used icon is on the Target Sources page. This field is used to set all blank Actions to “NotUsed” for the Target Source mappings. Refer to the Target Sources field descriptions.

  • Target Field Value Field field on the Cross Reference Check Table page. This field gives the ability to select which Multi-Part key to use for Value Mapping rules. Refer to Cross Reference Check Table field descriptions.

  • New fields used in the Copy Source process:

o   Activate Inactive Fields In Copy To Target

o   Initialize All Mappings In Copy To Target

o Create And Insert Mapping Groups In Copy To Target

  • Synchronize Target icon on the Targets page. This field provides the ability to immediately refresh the target and target field configuration using the new Synchronize Target. Refer to the Targets field descriptions.

  • FieldMapper, ValueMapper, ObjectRuleBuilder and ReadOnly WebApp groups.

  • Lock Field field on the TargetSchema and Target Source Schema pages. This field controls if the field will be reset when the target or Target Source is reset. Refer to the Target Schema and the Target Source Schema field descriptions.

  • Rule Field field on the Target and Target Schema pages. This field marks a field as Rule Only.  Refer to the Targets and the Target Schema field descriptions.

Transform

  • ReadOnly WebApp group.

  • Fields added to the My Worklist process to provide additional information when reviewing new or changed field mappings:

    • Object
    • Target
    • Source

Refer to the My Worklist field descriptions.

Enhancements

  • Various validation rules added and improvements to user experience

Collect

  • Download time reduced for BOA RFC downloads

  • Count on Fields icon on Targets page refactored to include completed mappings for each primary source

Console

  • Records delivered on the List Value Configuration page (i.e., records where DSP Supplied is enabled) cannot be deleted. Refer to Configure List Box Values.

  • Hid the Instance field on the Parameters page because it wasn’t being utilized.

  • Expanded the length of the Language field from 1 to 25 characters to support any ERP Target system requirements. This change impacts the Waves and the Target: Source pages.

Common

  • Updated the Profile feature to be more user friendly by disabling

    • Profile TT Tables Only when there are no tt tables in the data source
    • Activate All Tables when all tables are active
    • Inactivate All Tables when all tables are inactive

Refer to Profile Data Sources.

  • Added ‘TEXT_SAP’ table to the ‘DG Reports SAP Tables’ scope

  • Removed DBMoto Function Setup page and all field references to “DBMoto Function”

dspCompose™

  • GUI Script posting is restricted to background only

  • Updated template and org unit security. Refer to Add the Org Unit Security View to Template Role Validation Rules.

dspMonitor™

  • Information Steward integration files were incorporated into the installation package for dspMonitor™. Refer to SAP Information Steward Integration.

Integrate

  • GUI Script posting is restricted to background only

  • GUI script posting supports SAP GUI 7.30

  • SAP Transport RD2K900SN was replaced with RD2K900T0

  • SAP Transport RD2K900T0 was replaced with RD2K900U1

Map

st tables creation via Map automation improved to adhere to methodology change of key creation on st tables.

Transform

  • Source Table limit has been increased from 50 characters to 128 characters

  • Default value added to the Source Database Object field on the Target Sources page. Refer to Assign Additional Target Sources.

  • SAP Readiness Report Type are now Target Readiness Report Type

  • The performance of the Targets page has been improved so that the page loads faster compared to previous versions.

Online Help

  • Feedback link in the footer

  • Note in footer about limited access based on security

  • Screen shots to instructional steps

  • Various edits and clarification notes

  • New task descriptions :

o   Common

§  Copy a System Type Table

§  Set up Security for Common

o   Console

§  Move a Target to Another Object

o   dspCompose™

§  Add the Org Unit Security View to Template Role Validation Rules

o   dspMigrate™

§  Grant Users Access to dspMigrate™

o   dspMonitor™

§  Getting Started with Running Reports

§  Set up Data Sources for dspMonitor™

o   Integrate

§  Import Legacy Scripts into Integrate

§  Set up Security for Integrate

o   Map

§  Copy Sources

§  Create Custom Workflow Messages

§  Track Changes for Field Mappings, Value Mappings, and Target and Rule Creation

§  Update Unmapped Target Fields to NotUsed

§  Update Unmapped Target Source Fields to NotUsed

        o   System Administration

§ Getting Started with DSP® Security for Delivered Components

§ Getting Started with DSP® Security for Custom Components

§ WebApp Groups

§Assign Users to WebApp Groups

o   Transform

§  Set up Data Sources for Transform

§  View Transform Reports

§  View Summary Dashboard

·         New field descriptions:

o   Collect

§  Workflow Summary User Settings

o   dspCompose™

§  Create Custom Template

o   System Administration

§  Bulk Duplicate Detection

§  Dictionaries

§  Dictionary Words

§ Groups

§ Group Pages

§  Stop Lists

§  Stop List Words

o   Transform

§  All Reports

§  Cutover Plan

§  Source (Errors)

§  Source (Info)

§  Target (Errors)

§  Target (Info)

§  Target Metrics Content

§  Target Metrics Object Development

§  Target Metrics Report

§  Target Rule (Audit)

  • Re-organized layout of System Administration documentation

  • Standardized Overview and Getting Started sections for every component

  • Re-wrote Construct documentation to better capture end user’s goal and purpose

Security

  • Modified security for dspMonitor™ so only users with security can be assigned as a Group Owner.

  • Added new WebApp groups to various components. Refer to WebApp Groups.

  • Re-organized the Security documentation to be clearer and more process-driven

User Interface Enhancements

  • Standardized Date, Application and Version fields on the Parameters page for each component

  • Fixed typos and capitalization errors in various field names

  • Added missing and updated various icons

  • Added entries to catalogs

Resolved Issues

Various bugs were fixed.

Known Issues

Common

1.  An error occurs when adding object for duplicate detection more than once

 

An object can be added for duplicate detection one time (Common > Analyze > Duplicates). If a user attempts to add an object for duplicate detection that was previously added, the following error displays:

 

1.Violation of PRIMARY KEY constraint 'PK_ttDupObject'. Cannot insert duplicate key in object 'dbo.ttDupObject'. The duplicate key value is (JM497_3). The statement has been terminated

 

Workaround: When the error message displays, close the error message, cancel the record and click OK. The unsaved changes will be lost.

 

2. An error occurs when disabling the Key check box on the Object Columns page

When configuring column display for the duplicate detection process on the Object Columns page, disabling the Key check box results in an error. When the user disables the Key check box, this message displays: “One column must be defined as the KEY. Check Key for another record”. When the user clicks OK to confirm the message, the following error message displays.

 

Internal CranSoft Error

The CranSoft website could not finish processing the current request due to an unexpected system error.

 

Summary

The website reports the following:

1.Object reference not set to an instance of an object.

Workaround: Follow these steps.

1. Click x to close the error message.

2. Click the Back button in the browser.

3. Click the Columns icon on the Objects page to return to the Object Columns page.

 4. Click the Failed Status icon for the row with the error to validate the record on the Object Columns page.

 5. Click the Back button in the browser to return to the Objects page.

6. Click the Failed Status icon for the row with the error to validate the record on the Object page. .

 Continue with the object build process.

System Administration

Refresh issue on CTS Items page

This known issue occurs when adding CTS items on the CTS Items page during the CTS process. After all items have been added, the user clicks Cancel on the CTS Items page. The page remains in Add mode and duplicate rows display.

Workaround: Refresh the CTS Items page. The page no longer displays in Add mode, and the data displays correctly.

Previous Versions