3 Tips You Should Know about SAP S/4HANA Migration Cockpit

You leverage SAP S/4HANA Migration Cockpit to migrate the custom legacy business data into the new SAP Cloud ERP——SAP S/4HANA. Here I list some scenarios where you would need help on using Migration Cockpit, and some useful tips you should know about Migration Cockpit.

---

Scenario 1: You are using Migration Cockpit for the first time, or you are encountering different questions on different migration objects. You don’t know what channel to check with.
Tip 1: It’s strongly recommended to read the SAP Note 2538700 before having hands-on experience on Migration Cockpit. This is a collective Note which provides you with a list of SAP Notes/Knowledge base articles (KBA) related to the SAP S/4HANA Cloud Migration Cockpit content.
There are questions related to the tool:

There are also questions related to certain migration objects:

Moreover, we are also updating this Note very frequently, to ensure all those latest hot questions are included.

---

Scenario 2: You are preparing the customer legacy data with certain migration object template, SAP just publishes new content for the migration object templates in the new quarterly release. You want to know if there are any changes to the migration object template which you are working on.
Tip 2: Considering the new content will be published every quarter, this is a common scenario which could happen at customer projects. SAP provides the Migration Objects Template Comparison Report, which helps the customer to find out what are the new/changed/unchanged migration objects between releases. It can also help to list out the detailed changes for certain migration object from release to release.
E.g. change overview from 1902 to 1905:

You can also find out the detailed field-level changes for every migration object between releases:

---

Scenario 3: You are filling the data into the migration objects template which you downloaded from Migration Cockpit. You are familiar with SAP R3 ERP, but not with SAP S/4HANA. You are having difficulties to maintain the migration objects template.
Tip 3: In every migration object template, we hide some fields(SAP technical structure name, technical field name, detail description). By unhiding the fields, it can help you to add the data into the template file correctly. Especially if you are an SAP R3 consultant, you will be very familiar with these technical names.



So, these are the tips which I would like to share in this blog. Hope it can help to clarify some of the questions you have on using Migration Cockpit


Source: https://blogs.sap.com/2019/05/21/3-tips-you-should-know-about-sap-s4hana-migration-cockpit/?

S/4HANA Cloud 1905 – What´s new in test automation tool for S/4HANA Cloud

The next release for S/4HANA Cloud is coming. Time to explore exciting improvements, new features, and… time to do regression testing!

Here is some information about
A) new features in test automation tool for SAP S/4HANA Cloud, and
B) changes to standard automated test scripts, delivered by SAP.

If you prefer listening to reading, you might want to check out the “early release webinar” for “SAP Activate deployment – test your solution”. It is available in the list of early release webinars for 1905.

A) New features

If there’s just one thing you take away from this blog, I’d like to highlight this first feature! We enabled the change of role for testing not only for custom process steps, but also for process steps in type “standard”. This allows you to do role-based testing, whilst keeping the respective process step in type “standard”. With that, you can profit from the quarterly updates to automated test scripts that SAP delivers.

“Manage Your Test Processes” app

1.Possibility to change roles in process type “standard”

2. Release change information available at test process level

3.Download list of test processes (filtered/unfiltered list) into an excel spreadsheet

“Test Your Processes” app

1. Release change information at standard automated test process

…is now available on test process level (under test plan). This highlights where a standard process step was changed compared to the previous release.

2.Download list of test plans (filtered/unfiltered list) into spreadsheet

3.Define test data variants that shall be used for execution within “schedule test plans” feature

 

4.Execute test processes with data variants (similar as available feature at test plan and logs level)

B) Changes to automated test scripts

In 1905, the number of pre-delivered automated test scripts increased to 228. The 13 new automated test scripts are in the following areas: Financials (7), Manufacturing (2), Database & data management (1), Sourcing & Procurement (1), and Supply Chain (2). The complete list of available automated test scripts in 1905 is available in the “Automated Test Scripts Index” in the JAM Group for test automation tool (request access via mail to saps4hanacloudtesttool@sap.com)
A detailed change information at test scripts is available in the “What´s new” document within the same JAM Group. SAP updates the pre-delivered automated test scripts (process steps in type “standard”) in every release, to adapt them to release dependent changes of your system. The “what´s new” document will highlight all changes to the pre-delivered automated test scripts on the test process step level. If you created custom process steps, you should check for changes in the original process step from SAP. Most likely you will have to adapt your custom steps in a similar way.


Source: https://blogs.sap.com/2019/05/03/s4hana-cloud-1905-whats-new-in-test-automation-tool-for-s4hana-cloud/?source=social-global-voicestorm-LinkedIn&campaigncode=CRM-YA19-SSO-GETSOC1

S/4 HANA : MSEG or MATDOC Where is my data going?

       

5 Likes 114 Views 1 Comment

In S/4 HANA, there is always a confusion about the tables MSEG and MATDOC. This blog is to explain where exactly your data is going and how to understand the link between MSEG and MATDOC tables.

For example, in the below case when you check the number of entries of MSEG in SE16N, it shows 55 entries.


Where as if you check the same in MATDOC, it shows the same 55 records. So which one is real?



Lets try a different approach. Lets try to check the correct entries through a database query using transaction DBACOCKPIT which directly queries the database. First check in MATDOC as below.

Perfect!. it shows 55 as expected when you run a straight forward select query from MATDOC at database level.
Lets try to run the same thing for MSEG now and I am sure you are expecting 55 here as well. Right?

Oops!. It shows 0. So it is clear that we don’t have any entries in MSEG in HANA database. It just simply points towards MATDOC internally when you run through SE16N. How is it doing & how do we know that?
This is an important screenshot taken from transaction SE11. Go to Extras menu for table MSEG and you will see these details.
SAP has introduced a concept called ‘Replacement Object’ where a CDS view name is mentioned. Earlier, this was called as Proxy object till 1709 version and it looks like SAP has renamed it as ‘Replacement Object’ to avoid any confusion because of the word ‘Proxy’.


For MSEG, NSDM_E_MSEG is shown as replacement object. So when you access MSEG either in SE16N or in your custom program, SAP routes the logic through this CDS view which gets the data from MATDOC. You can see the logic in the below screenshot.
Give CDS View NSDM_E_MSEG in view name in SE11. You will get the below details which gives the DDL definition name and the DDL SQL view name (NSDM_V_MSEG) also.

View NSDM_V_MSEG in SE11 clearly shows that it gets the data from MATDOC.
 
Last part in the DDL definition talks about any custom fields or appended fields and how this is handled in these replacement objects. You need to use Extend view and append the custom fields in Eclipse editor.

Please note that you don’t have the replacement object available for all replaced tables in S/4 HANA. This concept is different for each table and above explained steps are specific to MSEG/MATDOC. Replacement object/Proxy object concept was mainly introduced to avoid confusions/changes in custom programs which deals with MSEG. So if a custom program does a select from MSEG, it will still work similar to what we saw in SE16N screenshot above.
Hope this blog helped to clarify some of the doubts related to MSEG/MATDOC tables.

Source: https://blogs.sap.com/2019/05/09/s4-hana-mseg-or-matdoc-where-is-my-data-going/?