- Print
- DarkLight
About System Views
The System Views page provides setup and building of the Pass Thru Views for a Data Migration Project. Each working database uses Pass Thru Views of the Target system check table data in the process of running rules and reports against migration data.
Notice that the format for these views is Table Name_System Datasource Name. The views stay in sync with the table data in the System Datasource.
Prerequisites for Building System Views
Datasets must be Imported into the Release within Mappings. Refer to section Migrate > Mappings > Import Datasets to Mapping for details of this process.
Target System Data Dictionary tables (DD tables) must be setup in the Target Datasource and must be complete as they are used in building the views. Refer to section Catalog > Datasources for details of this process.
Within Project Setup, a Subject Area is added to a Release and the working database and the working datastore are then created in the database system and ETL tool. These Subject Areas automatically display within System Views page.
Users & Roles in System Views
The Data Migration Project Lead, Deployment IT lead, or the Migration Team Developers are responsible for managing System Views values.
Role | Definition |
---|---|
Admin | The Admin or Project Manager responsible for all Dataset Design initial setup. |
Developer | The user developing the System Views for use in migration of data. |
Working in System Views
View the following page by navigating to Migrate > System Views from the Syniti Migrate Homepage. This page provides a list of Subject Areas and the associated Target Systems that provide views for the Working database listed within the Subject Areas.
This page includes three panels - Subject Areas, Target Systems, and System Views.
Panel | Description |
---|---|
Subject Areas | This panel provides the details for the Subject Area including Project, Release, and working database names.
|
Target Systems | This panel provides every Target system attached to the highlighted Subject Area and details for the Name, Schema, and Client as example.
|
System Views | This panel provides each check table attached to the highlighted Target System. |
Subject Area Panel
The panel for Subject Areas provides a list of all active Subject Areas for the system. This panel is setup with a set of key fields that make up the Subject Area - Project/Release/Subject Area/Working Instance. This list may not be altered within this page, however, the Subject Area is maintained with Catalog > Dataset Design > Create & Maintain Subject Areas.
See below for column definitions for Subject Area:
Column | Definition |
---|---|
Project | The Project name. |
Release | The Release name. |
Subject Area | The Subject Area name. |
Working Instance | The Working Instance associated to this Subject Area in Reporting Environment. |
Start Date | Release Start Date. |
End Date | Release End Date. |
Target Systems Panel
The panel for Target Systems provides connections for all Target Datasources that are associated with the highlighted Subject Area in the left side pane.
Prerequisite to Adding a Target System
This process is intended to provide a list of all of the relevant pass thru views for the Project / Release / Subject Area / Working DB based upon the mapping of fields from source to target. The list of System Views is based upon the Target Datasource and the Check Tables that are provided within a mapping. Every Check Table is included regardless of whether it is setup as a mapping type for cross reference. This way, if later it becomes necessary to change the mapping for cross reference, the system view is in place.
Within Catalog > Dataset Design, the Subject Area is defined and as Datasets are created, they are assigned to a System Datasource that represents the target system. These target systems are identified within System Views to assist in the build of Pass Thru Views.
Add a Target System to the Subject Area
On the System Views multi-panel page, the Target Systems panel is in the upper right of the System Views page. Click Add icon to open the Target System Details window.
Note
The System Views are dependent upon having a Target System identified, so once a Target System is identified, the System Views panel will display the Add icon.
See below for field definitions for adding a Target System:
Field | Definition |
---|---|
Target Snapshot Datasource* | The drop down list of Target systems that are Snapshot. (Required) |
Environment* | Specifies which Environment to build the views. |
Schema | Name of the schema for this database. (Ex: dbo or TGTMM) |
SAP Client | If the target system is SAP, then provide the Client. |
SAP Language | If the target system is SAP, then provide the default language. |
Note
The SAP Language, if filled initiates the System Views to default toggle Language Filter = 1 or Active. This action builds the System Views (Pass Thru Views) that filter for the Language value entered as WHERE SPRAS = N'E' as example. The SAP Client, if filled initiates the System Views to add into each view 'WHERE MANDT = N'client#' - Where the client number is entered. In the case below, the statement 'WHERE MANDT = N'100' is present in each System View generated by this action.
Fill in the fields as shown below.
Note
The Schema field value must match the formatting of the database otherwise the data fails to import.
When finished with edits, click the Save icon to complete.
Upon saving the system produces a message "Views Preloaded Successfully."
System Views Panel
Once the Target System has been saved for a Subject Area, the system produces a list of System Views based upon the Mapping of fields from source to target and the Target Datasource system.
See below for column definitions for the System Views panel:
Column | Definition |
---|---|
Check Table | The check table active in Mappings for this Target Datasource |
Comment | Free text to store table level comments |
Language Filter | Toggle to mark active for filter by language. |
Build View | Toggle to mark active for build. |
At this point, the user may elect to mark certain check tables as Inactive by a click on Build View toggle, and they may add comments to the Check Tables.
Note
If the user pulls in an additional table after the initial Build Views has completed, Do NOT toggle the Build View toggle Inactive as it drops those rows updated and does not create a new view. Always keep the Active Check Tables toggled as Active for Build View.
Build System Views for Target System
The resulting Target System displays with a button to produce the System Views. Click Build button to initiate a Job Queue to build these "Pass Thru Views" in the Database system.
Note
A Prerequisite to Building the System Views is that the Datasets must be Imported into the Release within Mappings. This way the build knows what fields and check tables are required for build. Refer to section Migrate > Mappings> Import Datasets to Mapping for details of this process. Also, If there are no Target Systems in the panel above, then the Add icon does not display for use in the System Views panel. One is dependent upon the other.
The system presents a warning message for the user to acknowledge. Click OK to proceed.
The system responds with a message "Job Initiated to Create Views." Check on the progress of System View Build from within pathway Administer > Job Queues.
Note
The field for Schema provide the tgtXXX table schema for building the Pass Thru Views. Make sure to enter the correct schema to reduce issues and errors during the system view build. For each Check Table Toggled as Build View Active there are two steps, Drop view and Create view.
The resulting job queue displays an executable job for "Build Config Views in wrkXXX for tgtXXX" job name similar to the image below:
The Pass Thru Views should resemble the image below when created in the Database:
The Build Config Views job drops and then creates the view in the Database. Should all of the job steps show as COMPLETE with no Step ERRORS then this process has been successful, and the System Views display in the working database.
Note
In the case of using SAP HANA DB or HANA database system, there is a third step for each view to GRANT SELECT ON - EX: GRANT SELECT ON AUSP TO wrkMM, REPORT. The GRANT SELECT ON step grants access to the view. In SAP HANA DB and HANA databases this is required for the reports to be accessible. SQL Server database does not require these steps for GRANT SELECT ON.
Note
The System Views panel fields allow the user to add comments to a check table as well as filter by Language and mark as Active/Inactive.
Copy Target Datasource Tables to a New Target Datasource
If a Target Datasource with tables already exists for a Subject Area, you can copy those tables into a new Target Datasource, allowing the same pass-through views built from these tables to be added to the new Datasource. Use this feature to quickly populate Target Datasources for different environments, such as Load and Dev.
During the copy, all tables are copied to the new Datasource, and all non-conflicting check tables are appended to the new Datasource.
Note
Conflicting check tables are not copied to the new Datasource.
To copy Target Datasource tables to a new Target Datasource:
Select Migrate > System Views from the Migrate menu.
In the Subject Areas panel, select the Subject Area containing the Target Datasource with the tables to copy.
In the Target Systems panel, click the Edit icon for the Target Datasource with the tables to copy.
In the Target System Edit page, select the Target Datasource to copy the tables to in the Copy System Views to Another Target list box.
Note
This section displays if more than one Target Datasource has been added to the Subject Area.
Click the Copy button.
Click the close X icon.
Note
A confirmation message displays in the lower right corner and the tables and check tables are copied to the new Datasource.
Add a System View
The user may need to add a System View for a check table that is not proposed. In this case, add this new System View manually. From within Migrate > System Views, the user may add a new view based upon an existing table in the database for the target system (regardless of whether the table exists within the actual target system).
Note
The actual table must be created within the Target System before this works successfully.
Click on the Add icon to open the System View dialog box.
This is an opportunity where the user has produced a view to be used as a check table against one or more fields of the table. The view would need to have been built within the Database prior to adding to this panel.
See below for field definitions for adding a new System View:
Field | Definition |
---|---|
Checktable* | The table stored in the Target System to be used as a System view. (Required) |
Comment | The added comments associated with the System View. |
Language Filter | Toggle to mark the Language Filter as Active/Inactve.
|
Build View | Toggle to mark the System View as Active/Inactive for Building the view.
|
When finished with edits, click the Save icon to complete.
Edit a Target System
The Target System may be updated to correct for the fields for Schema, Client and Language. It is not advisable for the user to change the actual Target Snapshot Datasource once the System Views have been built and added. This causes issues.
When finished with edits, click the Save icon to complete.
Delete a Target System
The Target Datasource may be deleted from the list by a click on the Delete icon. A warning message displays to ask "Are you sure you want to Delete?" The user selects OK to proceed or Cancel to disregard and exit.