Scribd
Upload
859 views11 pages

Steps in Syniti ADMM For Development

This document outlines the steps to migrate data from an Excel source to a SAP target using Syniti. It describes importing the Excel file, creating the data model objects, performing mappings between the source and target, executing the ETL jobs, and validating the target data.

Uploaded by

venkay1123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
859 views11 pages

Steps in Syniti ADMM For Development

This document outlines the steps to migrate data from an Excel source to a SAP target using Syniti. It describes importing the Excel file, creating the data model objects, performing mappings between the source and target, executing the ETL jobs, and validating the target data.

Uploaded by

venkay1123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

SYNITI STEPS WITH NAVIGATIONS MARKED

1. Create an excel for each object which u want to develop.

EXAMPLE:-

2. Go to administer--> Import File --> Excel import (excel is source file)


3. Modify the excel according to the data --> so that headers should be visible just above the actual data --
> Give the 'Start row' according to the beginning row of the data (including headers)

4. Since all the data that we import is considered as a source, we give SRCConstruct in the Datasource ID
and give a table name
5. Then navigate to SQL --> DataSources--> SRCConstruct--> Check for our newly created table

6. Check the records in the table and modify the excel file if there any data format issues, always check the
format of the data.
7. Navigate to Catalog--> DataSources--> SRCConstruct--> DataSource tables --> Click on '+' sign and add the
created table
8. After adding the table --> refresh the page --> so that all the columns will be populated in the below pane
(Data Columns)

9. check Key field box for the fields which are mandatory/keys as per the mapping
10. Then navigate to Catalog-->Data Design

In note: Be cautious in deleting the objects as this can be a big trouble later on

11. Navigate to Subject Area--> Add a new object --> Give all the details

 RICEFW : refers to the id of the object (not mandatory and can be updated later on)
o Specify the target data source --> S4H_SBX (in our case)
o Give a migration prefix (Ex: PFC for Profit Centre)
o After creating the Object, now we need to create data elements and tables.
12. Add Dataset table --> name is given in the mapping file (Data Model)

Also check for the fields --> which should be active (Data element active) and enable Key field for the same.

13. Now navigate to Migrate to proceed with mappings.


14. Mappings-->Import Dataset--> Select the dataset and click import --> Refresh the page.

15. click on create Build Table and click on create reports.

16. Now specify the sources by clicking on '+' near sources tab

Give these details: zSource-->Construct; Primary Source table --> Give the table name created in 4th step Mention
the assigned developers for the object and then save

*** If a target has more than 1 source, we can simply add new row for each source ***
17. Now proceed with the mappings --> Select the source --> click on the icon below mappings.

You can either select the mapping action from the ICONS in the parents pane (A from below screenshot),
or from the dependent pane dropdown (shown as B in the screenshot)
 Save the mapping once done with giving the action.
 Once you mark the mapping status as Complete and want to change the mapping action, you can click on
Unlock key 🔒 icon.

Below are the mapping actions and descriptions for better understanding: -

Action Description
1. Copy Allows you to copy a value from a Source field to a Target field.
For example, you could copy the Source LIFNR value (Account Number) to
the ZLEGACYLIFNR field
Use this if you want the value in a field to automatically populate a particular value.
2. Default For example, you could default the BRSCH field (Industry Key) to WHSH if all the
data records apply to that deployment location.
3. Rule Allows you to enter logic for a mapping rule. The Developer uses this logic to
develop the mapping rule. For example, you could add a rule so that NAME1 copies
the first 35 characters from the Source.
4. Xref Allows you to use a cross-reference table to perform value mapping to translate a
Source value to a corresponding value in the Target field. For example, if the LAND1
field (Country Key) should be translated to a new value that adheres to the Target
configuration, you could use the Xref action to do this.
Use this action if a Target field does not need to be populated. For example,
5. Not Used if NAME4 field will never be populated, you can assign the Not Used action to this
field.
18. Once the mapping is done, Go to ETL and execute.

Once Build is done, Execute the jobs, and the check the status in Jobqueue steps

Once the steps are executed, if there is any error debug it accordingly. If the process completes without error, Go
to targets and refresh the reports.
19. Navigate to targets pane as below and select reports icon,

20. Refresh the reports.

21. Filter according to the status of the reports and work accordingly if any report fails or doesn’t work as
expected.
22. Once all the reports are executed without any errors and are validated successfully, you can download the
reports: -
 You have multiple options to View, Refresh, Download the reports as required. Below are the highlighted
options in the screenshot!

******NOTE: - Please add the steps if you feel any step is missed or any step is mentioned wrong.******

You might also like