SPDD and SPAU Phases during S/4 HANA Migration

# Purpose of this Article

In this article I would like to share the functional consultant (rather say my understanding) understanding about SPDD and SPAU during S/4 HANA Migration project. It is one of the most critical activities during any migration project as it (SPDD) has direct impact on transaction data. Let’s get started.

Note: I am S/4 HANA (FICO) functional consultant and have drafted it with my limited knowledge about the technical aspects. 

# SPDD Phase

SPDD is a phase during S/4 HANA migration where all data dictionary objects (Structure, Data Element etc.) are compared between S/4 HANA data dictionary object and ECC data dictionary if any changed is found system proposes the same to take necessary actions by ABAP Technical Consultant and Technical consultant take necessary action in consultation with Functional Consultant.

If any data dictionary object is missed or not coming in S/4 HANA, its direct impact would be on your data migration part. Suppose there is one table BSEG field “Discount Reason” in ECC environment and if this field is deleted in S/4 HANA; data related to the field “Discount Reason” would not be migrated at all in S/4 HANA environment and then business will struggle for this information in S/4 HANA system. That’s why it becomes very important to understand the importance of SPDD and do necessary action for each changes SAP proposes in this SPDD phase during S/4 HANA Migration.

All data dictionary elements are presented in three parts 1. with modification assistant, 2. without modification assistant and 3. Deleted objects.

1.     With Modification Assistant: ABAP Technical Consultant has to take appropriate action along with Functional Consultant.

2.     Without Modification Assistant: Here also ABAP Technical Consultant has to take appropriate action along with Functional Consultant. Some manual changes can be done here by technical consultant.

3.     Deleted Objects: This section shows deleted objects and nothing can be done for this section.

What Action is taken in SPDD?

Technical consultant compares the data dictionary objects with new version (S/4 HANA) Vs. latest version in previous system (ECC) and decide whether propose changes need to be accepted or ignored (set original version (ECC version)). Propose changes could of many natures such as, addition of new field in existing table (BSEG) or change in character length of existing field (MATNR) to 40 character in S/4 HANA. So, this sort of action is taken during SPDD.

It is the most critical activity I consider in any migration project (S/4 HANA or otherwise) as it has direct impact on your transactional data. It Should Be Handled with Utmost Care

# When to Perform SPDD During the S/4 HANA Migration Project?

Data Migration Option (DMO) is run by BASIS consultant; once system reaches Pre-processing- Data Dictionary creation (DDIC_UPG) phase, SPDD activities are done. After SPDD activities Pre-Processing- Data Dictionary Activation (ACT_UPG) phase is started. All the SPDD changes are stored in a Transport request in S/4 HANA Mock Migrations. During Production S/4 HANA all SPDD activities are done through saved transport request and only the delta SPDD (if Any) is done manually in production environment.

 # SPAU Phase

SPAU is phase where all reports, programs, screens and functional modules are compared between new system (S/4 HANA) and latest version of the previous system (ECC system) if any changed is found system proposes the same to take necessary actions by ABAP Technical Consultant and Technical consultant take necessary action in consultation with Functional Consultant.

All objects elements are presented in two parts, 1. with modification assistant, 2. without modification assistant.

1.     With Modification Assistant: ABAP Technical Consultant has to take appropriate action along with Functional Consultant.

2.     Without Modification Assistant: Here also ABAP Technical Consultant has to take appropriate action along with Functional Consultant. Some manual changes can be done here by technical consultant.

 # What Action is taken in SPAU?

Technical consultant compares the objects with new version (S/4 HANA) Vs. latest version in previous system (ECC) and decide whether propose changes need to be accepted or ignored (set original version (ECC version)). Any change which is done during SPAU phase, system does not require any access key.

 # When to Perform SPAU During the S/4 HANA Migration Project?

Data Migration Option (DMO) is run by BASIS consultant and once system is technically migrated to S/4 HANA system. Just after DMO and before starting Data migration (Functional) SPAU activities are done in S/4 HANA mock systems and all the changes are stored in Transport request. In production all SPAU activities are done through saved transport request and only the delta SPAU (if Any) is done manually in production environment.

This activity can be done post data migration and handing over to business also. Recommendation would be to complete all the SPAU before handing over the system to business.

Fonte: https://www.linkedin.com/pulse/spdd-spau-phases-during-s4-hana-migration-shakeel-ahmed/