cFiN landscape generally consist of one or more source systems, one SLT system and a target
cFiN system. Upgrade in any one of the three systems will need additional steps to be done in the SLT system.
Before starting the upgrade of source, SLT or target system, make sure to check the compatibility of DMIS versions in the new landscape.
Process
One of the below scenarios are possible:
- Target cFiN system is upgraded –> e.g., from S/4 HANA 1909 to 2021
Below steps need to be done in order:
a. Pause the replication before the upgrade starts by deactivating the respective
configuration in SLT. Use steps 1-3 from the section “Safe Deactivation Procedure”
mentioned in the note 2154420 for pausing the replication before the cFiN upgrade
starts.
b. After the target cFiN upgrade is finished, you will need to update the latest
replication content for the new cFiN version (2021) in SLT. This is because the
replication content is different for different S/4 HANA versions of the target cFiN
system. See section “Replication Content Update” mentioned in the note 2154420.
c. To avoid errors after resuming the replication in SLT, make sure to re-generate
migration objects for all tables of the MTID by following the steps mentioned in the
note 2776058 .
d. Resume replication after the upgrade by re-activating the respective configuration in
SLT. Use the steps 5-6 from the section “Safe Deactivation Procedure” mentioned in
the note 2154420 for resuming the replication after the cFiN upgrade finishes.
2. Source ECC system is upgraded –> e.g., from ECC 6.0 to ECC 6.07
Below steps need to be done in order:
a. Delete the existing triggers before the upgrade as the upgrade tool (SUM) may
stop with errors due to existing triggers. Follow steps from the note 2775350.
Note: If the source is a non-SAP database connection, the triggers have to be removed from
the database manually. Consult with your DBA for the proper steps or check SAP
Note 1620618 for additional information.
b. Pause replication before the upgrade by deactivating the respective configuration
in SLT. Use steps 1-3 from the section “Safe Deactivation Procedure” mentioned
in the note 2154420 for pausing the replication before the source upgrade starts.
c. After the upgrade is finished, run the report “CNV_NOTE_ANALYZER_SLT” in SLT
system as per the procedure described in the note 3016862. Make sure to
implement all the new notes in SLT and source systems.
d. To avoid errors after resuming the replication in SLT, make sure to re-generate
migration objects for all the tables of the MTID by following the steps mentioned
in the note 2776058 .
e. Resume the replication after the upgrade by re-activating the respective
configuration in SLT. Use the steps 5-6 from the section “Safe Deactivation
Procedure” mentioned in the note 2154420 for resuming the replication after the
source system upgrade finishes.
3. SLT system is upgraded –> e.g., from SLT 3.0 SP02 to SP05.
Below steps need to be done in order:
a. Pause replication before the upgrade by deactivating the ALL the configurations
(MTIDs) in SLT. Use steps 1-3 from the section “Safe Deactivation Procedure”
mentioned in the note 2154420 for pausing the replication before the SLT upgrade
starts.
b. After upgrade is finished, run the report “CNV_NOTE_ANALYZER_SLT” in SLT system
as per the procedure described in the note 3016862. Make sure to implement all the
new notes in SLT and source systems.
c. Also, make sure that all the notes for new DMIS version (SLT 3.0 SP05) are applied
from the respective release note. e.g., If the new DMIS version is 2018 SP05 make
sure all the notes are implemented in source and SLT systems as per the note
2955790.
d. To avoid errors after resuming the replication in SLT, make sure to re-generate
migration objects for all the tables of the MTID by following the steps mentioned in
the note 2776058 .
e. Resume the replication after the upgrade by re-activating the respective
configuration in SLT. Use the steps 5-6 from the section “Safe Deactivation
Procedure” mentioned in the note 2154420 for resuming the replication after the
SLT upgrade finishes.
Conclusion
Keeping the above points in mind will save you from surprises during and after the upgrades to cFiN landscape.
Feel free to reach out to me on Abhishek Singh | LinkedIn.
Supporting documentation and information
2776058 – How to regenerate the migration object for a table? – SLT
2775350 – How to delete existing database triggers using IUUC_REMOTE – SLT
2955790 – Release Information SLT – DMIS 2018 SP05
I hope this blog post will help you to conduct upgrades to in your cFiN landscape smoothly. Thank you for spending time reading it. Please do provide your valuable feedbacks and if you have any questions, please contact me.
Please follow me on the forum for more SLT-cFIN related contents: Abhishek Singh
Follow this space for related contents: SAP Landscape Transformation replication server | SAP | SAP Blogs
