Table of Contents

NOTE: Syniti’s Professional Service Accelerators (PSA) have been developed and are supported by: a team of senior consultants. The PSAa are designed to supplement the Stewardship Tier delivered features with content and automation that accelerate the progress of the project. If you have any questions or encounter any issues while using a PSA, please submit a support ticket and be sure to select the PSA on the form.

Overview

psaDataFilter is used as a divestiture tool to split data from a current ERP System into table format as a source for a new target system. The tool uses Collect to extract the initial data tables. Organizational Field filters are created in the psaDataFilter application. The Build Filters process creates the views that extract only the data to be sent to the new company.

Key Features:

DataSource auto generate to save days of manual building of the rules
Multiple ESP systems can be processed in a single platform
Ability to auto generate collect packages once target and source have been registered
Ability to build 600 table filters for the SAP template process
Ability to design more templates quickly as the business needs change
Organizational Field data filters are easily defined
Data Retention Rules can be created and added to the download when large amounts of data need to be excluded from the processing
Approval History showing all the data moving from filter format to approved data
Build Process is no destructive allowing new templates to be added while in development
Business Users have easy access to view data in a web page or download an XLSX file
Priority fields have been established to schedule filtering and reviewing of tables

Install psaDataFilter

The application can be installed on Syniti Solutions SST versions 7.0.1 and above

Download the Application License

The psaDataFilter application and/or license are obtained by opening a support ticket at support.syniti.com

To retrieve the necessary information for a license request:

On the SST application server, locate the Hardware Identifier program (called “HardwareIdentifier.exe") included in a zip file along with the SST installation software and documentation previously downloaded from Syniti.
Open the program.
Click Generate.
Copy the automatically generated ID and collect the following additional information. All information below pertains to the application server running SST; no information is needed regarding the database server:
1. Hardware ID (as mentioned above)
2. Windows computer name
3. Number of processor cores (as shown in the Task Manager CPU tab)
4. Usage of the SST instance, as in, DEV, TEST (or QA) or PROD
Syniti Licensing delivers the license file via the support ticket

Install the License

To install the license:

Log in to the SST site as an Administrator.
Select Admin > Configuration > Product Licenses in the Navigation pane.
Click Upload a file icon in the FILE NAME column next to the Upload a New Product License link.
Locate the license file that was provided by Syniti Licensing.
Click Open.
Verify the license is uploaded.

NOTE: If the Navigation pane does not display all the licensed components as expected, use

the browser refresh button or the F5 key to refresh the screen. At this point the full vertical menu appears.

Install the Application

Perform the following steps to install the application:

Right click psaDataFilter.zip and select Properties. Ensure to unblock the file if it is blocked.
Unzip the file.
Navigate to the SST Installation folder (e.g., D:\BOA\DSP or C:\Program Files (x86)\BOA\DSP).
Back up the SST Install\BOA\DSP folder to a compressed zip file.
Back up all Syniti-supplied SQL Server databases or verify that a complete recent backup already exists.

NOTE: Supplied databases: AutoGen, cMap, cMap_Data, cMass, cMass_Data, Console, CranPort,

CranSoft, DataConstructionServer, DataDialysis, DataGarage, DBMoto_Client, DGE, DGE_Data, dgReports, dgSAP, dspAddOn, DSPCommon, dspMonitor_AccPak, dspMonitorConfig, DSW, IGC, Integrate, IntegrateStaging, InterfaceServer, MC, and RADToolkit.
Stop IIS.
NOTE: This process disconnects all active SST users, so it is highly recommended to perform the install when no users are on the system. This process stops IIS on the web server.
1. Open Windows Start Menu.
2. Open the Command Prompt (run as an Administrator).
3. Type: IISReset –stop.
4. Press the Enter key.
5. Leave the Command Prompt window open for later use.
Stop all services that start with “Cransoft Service …”
NOTE: This process stops all SST background jobs, so it is highly recommended to perform the install when no scheduled operations are running on the system.
1. Open Windows Start Menu.
2. Select Administrative Tools.
3. Run Services.
4. Right-click the SST service.
5. Select Stop.
6. Repeat the previous two steps for any additional SST services.
Copy the Web folder from the zip file to your existing SST install\Web folder. If prompted, replace the files in the destination.
Copy the Databases folder from the zip file to your existing SST install\Databases folder. If prompted, replace the files in the destination.
Navigate to SST install\Databases and execute file psaDataFilter_Install.bat (run as an administrator)
Start all services that start with “Cransoft Service …”
1. Open Windows Start Menu.
2. Select Administrative Tools.
3. Run Services.
4. Locate the SST service(s).
5. Right-click the SST service.
6. Select Start.
7. Repeat the previous two steps for any additional SST services.
Start IIS.
1. Open Windows Start Menu.
2. Open the Command Prompt (run as an Administrator).
3. Type: IISReset –start.
4. Press the Enter key.

Configure psaDataFilter

To configure psaDataFilter:

Create a data source connecting to Source System.
1. To create a data source, navigate to Common > Configuration > Data Source Registry and click Add.
2. Specify “External System Connection” as the Application Data Source Type.
3. Add connection specific information.
Create a database named sdbSAP and register a data source.
1. To create a database in SQL, open SQL Server Management Studio (SSMS).
2. Click New Query and type the command - CREATE DATABASE sdbSAP.
3. To create a data source, navigate to Common > Configuration > Data Source Registry and click Add.
4. Specify “Migration Source Database (sdb%)” as the Application Data Source Type.
5. Add connection specific information.
Create a database named sdbSAP_Filtered and register a data source.
1. To create a database in SQL, open SQL Server Management Studio (SSMS).
2. Click New Query and type the command - CREATE DATABASE sdbSAP_Filtered
3. To create a data source, navigate to Common > Configuration > Data Source Registry and click Add.
4. Specify “Migration Source Database (sdb%)” as the Application Data Source Type.
5. Add connection specific information.
Create a Database named sdbSAP_Approved and register a data source.
1. To create a database in SQL, open up SQL Server Management Studio (SSMS).
2. Click New Query and type the command - CREATE DATABASE sdbSAP_Approved.
3. To create a data source, navigate to Common > Configuration > Data Source Registry and click Add.
4. Specify “Migration Source Database (sdb%)” as the Application Data Source Type.
5. Add connection specific information.
In SST, navigate to Collect.
Register sdbSAP as Target and your source as the Target Source.
Verify Target and Source test connection works.
Register sdbSAP_Filter Target and psaDataFilter as a Target Source.
In SST, navigate to psaDataFilter.
Click Datasource page.
Click Add.
1. Set sdbSAP as the Data Source ID.
2. Set sdbSAP as the Source Data Source ID.
3. Set SAP as the System Type.
4. Set sdbSAP_Filtered as the Filter Data Source ID.
5. Set sdbSAP_Approved as the Approved Data Source ID.
Click Build Collect to start the table registration and package build. (Wait a couple of hours for process to be completed.)
Click Build Table Filters to start the table registration and package build. (Wait a couple of hours for process to be completed.)
Click Add Data Retention Filter to add Where Clauses for the connection to remove millions of records from the filter.
1. Configure filter as needed.
2. When finished, navigate to the Data Source page in psaDataFilter.
Click Add Filter to create new Organization Fields. These values process during the Filter cycle. Configure filter as needed.
Review the data looking for retention years, org filters applied and distinct keys used.
Once complete, navigate to Configuration > Admin Table Filters.
Mark the Table as READY FOR REVIEW.
Review the data or download the XLS files.
Approve or Reject the data, and add a comment to explain what is wrong with the filters.
Users can mark a table for automatic approval for future filtering cycles.

If the Navigation pane in SST doesn’t show psaDataFilter, then try these steps:

Log in to the SST site as an Administrator.
Select Admin > Configuration > Product License in the Navigation pane.

NOTE: Ensure that psaDataFilter displays.
Select Admin > Configuration > Site Menu in the Navigation pane.
1. Ensure that psaDataFilter appears here. If not, then:
  1. Click Add.
  2. Enter a priority in the PRIORITY field.
  3. Enter psaDataFilter as the label for the site menu option in the LABEL field.
  4. Select the psaDataFilter : psaDataFilter page from the LINK TO PAGE ID list box.
Select Admin > Configuration > Parameters in the Navigation pane.
1. Click Clear Cache.
2. Reload the browser tab.
If you still can’t reach the psaDataFilter application, then review the Define Security Roles the SST Online Help to ensure the SST user has access to psaDataFilter. The SST Online Help is accessible from the question mark icon in the top-right corner of all SST pages. Also, open a ticket at support.syniti.com for assistance.

User Guide

Data Source

DataSource page displays the configuration being used to split the data from Source System into the filter database and final approved database.

This system can store as many source ERP Systems as needed into Filtered and Approved databases.

The following steps are completed for the user with a click of a button:
- Build Collect—creates the table registrations for Collect and builds the Assembly packages. This process takes a couple of hours for all the packages and tables to be built.
- Build Table Filters—creates the Collect registrations for the filter views. This process uses all Post loading views and rules to create distinct keys. This process takes few minutes to create all the registrations, but a couple of hours to build all the Assembly packages.
- Add Data Retention Filters—used for large tables that need to be filtered on the download.
- Add Filter—adds organizational field filters for the process.
Org Field Summary

Summary of data value assigned to key fields per zSource. The application can filter multiple SAP systems as well as different ERP systems in the same application.

Click FILTER VALUES to add a new value or click on Organizational Fields to add a value for the first time.

Data Divestiture - Organization Field Filters

Enter values for fields on this page.

Table Filters Status

Table Filter Status by zSource and displays the number of tables.

The following is a list of Statuses defined in the application:

Initial Status:

Not In Scope—Tables being excluded from the filtering process
New—Initial table status before any filters have been executed

Working Status:

Filtering in Process—Filtering work has begun on this table. This table may include research on Parent/Child field relationships.
Filter Complete—Collect has processed the filter using the defined Organizational Fields or Distinct keys from the Parent tables.

Business User Status to respond to:

No Data in Full Record Set—No Data in the source system for the table
No Filter Data—No data after the Organizational fields have been applied
Ready For Review—Consultants have run the filters and find the data ready

Business User Response:

Approved—Client Data stewards approve the data
Rejected—Client Data stewards reject the filters
Automatic Approval—Client Data Stewards approval all runs after the initial approval

All Table Filters

Table Filters display all the Tables being filtered by the application. It displays the View Name, Organization Fields, Distinct Keys built from parent tables, as well as Create Distinct Key to be used by child tables. Business users can Approve or Reject the filter results.

There is a comment field for users to identify the issue with the filter if rejected.

On the far right of the screen, there is a button for View Data to see the first 10,000 records. The page displays the full record count, the filter record count and approved record count if previously approved. A download file ICON allows a user to download the data into an XLS file.

The APPROVED toolbar is the only option to get filtered data into the approved database. The Automatic Approval loads the data into the table, if the table has been approved one time by the business user.

Summary Counts by Field

Filter tables can be split into by organization data field for data verification.

On the Admin Table Filter enter the field name in Filter Table Field. When the Filter View executes in Collect, it populates the filter value settings in this table.

The following is an example of entering a Filter Table to be split by Summary Counts.

Approvals

The approvals page displays every filter table with the Approver, Approved On and the matching Approved Audit File. On large projects, this page displays thousands of records after all of the tables have been completed. This page also maintains the approvals for each mock load until the go-live date.

Priority Summary

Priority Summary displays table status showing all tables counts, working status, ready to review status and approved table status.

Admin Table Filters

Admin Table Filters is the page for Administrators to make table adjustments for Priority, System Types, zSource and many other objects. Consultants should do all their work on this page. The Table Filter page is for the Business Users making approvals or rejections.

Tables “NOT IN SCOPE” should be excluded from the Filtering Approval process.

Tables can be marked inactive in collect, but it is not updated after the initial Build.

New tables can be moved to “NOT IN SCOPE” by processing the “X” icon on the page toolbar.

Tables change to “NEW” status are ready to be filter processed.

Tables in “NOT IN SCOPE” can be moved back to “NEW” by clicking the “+” icon on the page toolbar.

Table can be marked “Ready for Review” by clicking the Checkmark icon on the page toolbar. This lets the business know the tables are ready for review.

Distinct Key Summary

Distinct Key Summary shows the keys generated during the filtering processing cycle. These are the parent-child dependencies for the view containing these joins.

The “X” icon on the page toolbar resets all Keys for the next cycle of processing. Distinct Keys is copied to a backup table for audit reviews, but all filters have to be reprocessed to build all the keys again.

Table Retention Rules

Table Retention Rules are used as a WHERE clause on the initial download when millions of records are to be excluded before the filter process. Retention Rules can also run post posting SQL to read several tables and create unique lists like material or customer or vendors reading transactional tables for relevancy.

Click the “Update Collect” button on the page toolbar to update the where clause. The page below will show the retention rule as well as the WHERE clause on the Collect package. It may take 1-2 minutes to process the package as a background build.

SQL Commands processes as an after rule when the database has been downloaded. It is a key process to read or update data across multiple tables. It displays in the download table as an after rule.

The “X” icon on the page toolbar resets all Keys for the next cycle of processing.

Distinct Keys are copied to a backup table for audit reviews but all filters have to be reprocessed to build all the keys again.

Priority Table

Priority Table help track the work progress of all the tables. Define priority on this page for each table. The Admin Table Filter can then be used as an override for the Priority Summary page. Tables marked “NOT IN SCOPE” on the Filter Status should not have a Priority on the Admin Filter Table page. The psaDataFilter is updated as developers process data and marked ready for review.

Table Filter Templates

psaDataFilter has 600 predefined table filter to be published and start the filter process quickly. Filter status by default is “NEW” and the tables are published from the DataSource page. Please review these templates update if needed.

These filters are processed on the DataSource page when the “BUILD TABLE FILTER” is clicked.

Table Org Field Assignments

Organization Fields must be assigned to table for documentation purposes. The template used in the generation must have reference to the correct Org File filter views.

If new Table Organization Fields are added, then create new views like fvDistinctKeyLists_SalesOrder as an example. This view has the Field filter and is then added to the table filter templates.

Schedule Group Priority

Schedule Groups contains the order in which tables should be download in the Filtered Target. Tables in the group run in single thread to maintain Parent-Child relations for the Distinct Key build process.

Clicking the “Refresh” button on the record to download the tables for that group.

The page pulls the latest start and finish time for each group based on the results in Collect.

Generate Log

Generate Logs are built during Build Collect or Build Table Filters from the DataSource page. The SQL commands are non-destructive to existing objects. If an object is not generated, review this log page for error messages. The template can be generated for multiple SAP Systems.

Parameters

Parameters page controls how many records goes into a XLSX file. Filter tables bigger than the limit are generated as CSV files. PreApproved or Approved reports can be turned off by unchecking the flag below. Disabling these settings also deactivates the File Download on the Table Filter page if files are not generated.

The attached document outlines installation, configuration, and usage information for the psaDataFilter application, an accelerator for the Syniti Stewardship Tier (SST, formerly DSP).

Professional Service Accelerators (PSAs) are licensed separately from the SST. For more information, please email NASMT@syniti.com. To download or install a PSA, submit a request to Syniti support.

Updated on Oct 21, 2021

Syniti Solutions psaDataFilter Application Guide.pdf
1 MB Download