Skip to Content
Technical Articles

A Glimpse at Dual-landscape maintenance

While working on Implementation/Roll-out of Dual-landscape scenario, it has comprehensive tasks to be performed and it is completely baffling to maintain in the long run. This blog is intended to shed some light on the holistic view of Dual landscape and prominent, granular insights to ease your task of Support and maintenance

Prologue

  1. What is the use of retrofit functionality?
  2. Architecture of Retrofit
  3. What are the retrofit processes available?
  4. In which conditions Automatic import will work?
  5. In which conditions correction workbench and BC set tool will work?
  6. Which object types are always retrofitted manually?
  7. What is cross-release retrofit?
  8. What checks are performed to ensure that no downgrade occurs?
  9. What cannot be retrofitted?
  10. Can a role be retrofitted?
  11. Where does the CSOL program, checks the dependent objects of a role?
  12. What happens to sequence dependency, when the retrofit is completed?
  13. Where to check the import errors?
  14. What are the Prerequisites for Using the Retrofit Function?
  15. BC Set function is disabled for all system clients in retrofit system. How to manage?
  16. What is standalone retrofit?
  17. Can retrofit be used for all change types?
  18. What are the Retrofit Categories that can be seen?
  19. Why is it significant to set the retrofit to completed successfully?
  20. What are the applicable statuses of Change, that can enable Retrofit Process?
  21. How to know the criticality of a transport request ?
  22. What are the reasons for using manual object import functionality?
  23. What are the limitations of Auto import option?

 

A walk through across Dual landscape Maintenance

 

  1. What is the use of retrofit functionality?

To perform developments in development landscape and corrections/maintenance activities in maintenance landscape at the same time. Synchronizing the changes between two landscapes is called retrofitting

 

2. Architecture of Retrofit

3. What are the retrofit processes available?

-Automatic import

-correction workbench and BC sets as post processing tools

-Manual retrofit

4. In which conditions Automatic import will work?

In retrofit system, if there are no cross-system object lock and if the specific Objects were not changed, then auto import is possible

The system collects all objects that do not have any conflicts in a transport of copies and imports into retrofit system and copies to the target.

5. In which conditions correction workbench and BC set tool will work?

When Workbench objects, customizing objects has cross system object locks and if Objects were changed in the retrofit system, then it is possible to use.

Below is the illustration of all types.

 

6. Which object types are always retrofitted manually.

Retrofit scenario for BW objects and other manual imports In customizing. Blacklist can be defined for the objects that you want to exclude from automatic retrofit.

 

7. What is cross-release retrofit?

You can perform retrofits for systems that are on different support package, enhancement package, or release levels.  Cross-Release Retrofit parameter has to be Activated under “Define System-Specific Retrofit Settings” define those systems which can be allowed.

Ex:  you can retrofit ERP to SAP S/4 HANA, but we recommend you have set up and RFC-enabled an ATC (ABAP Test Cockpit) Central Check System In this case. Refer 2590595

 

8. What checks are performed to ensure that no downgrade occurs?

Below checks are performed by the functionality :

-Check for Customizing objects

-WB objects

-SAP Notes

-conflicts in PFCG roles

 

9. What cannot be retrofitted?

SAP Notes cant be retrofitted.

 

10. Can a role be retrofitted?

Yes, but if there are conflicts for some of the dependent objects of a role, the role and all of the dependent objects of the role are set to “manual retrofit”.

In case of a derived role, both derived role and root role is checked for conflict. If root role has a conflict, then manual retrofit has to be performed.

 

11. Where does the CSOL check the dependent objects of a role?

CSOL checks the table AGR_DEFINE (logical object ACGR, role definition), (table /TMWFLOW/CSOLPER) which represent all dependent objects. If it cannot be released, then all dependent objects have to be imported with a manual retrofit.

 

12. What happens to sequence dependency, when the retrofit is completed?

It is updated or deleted as soon as the retrofit for a transport request is completed.

 

13. Where to check the import errors?

In task list, follow the below

 

14. What are the Prerequisites for Using the Retrofit Function?

-Domain link activation and activate CSOL .

-TMW & TRUSTED RFC of managed system and 000 clients of the TMS landscape domain controller systems.

-Authorization objects S_RFC_ADM, S_TRANSPORT, S_SYS_RWBO to be   maintained  in  both development systems and its 000 clients.

-CCL maintenance for Dev system and retrofit system

-set the client role to “Customizing” to activate the BC Set for retrofit in SCC4 for the logical system

 

15. BC Set function is disabled for all system clients in retrofit system. How to manage?

This happens if a client is assigned to a productive client role. You can avoid this by selecting a non-productive client role in the system. if a client is not assigned to any client role, set the role to “Customizing” to activate the BC Set for retrofit

 

16. What is standalone retrofit?

Retrofitting Without Using the Change Control Management Scenarios is standalone retrofit. For this, activate the STANDALONE parameter. Discrete cycles has to be created to manage them and start retrofit from task list.

If it’s other way, then, retrofit is merged into charm CD itself. Only released transport request will show up in the retrofit queue

 

17. Can retrofit be used for all change types?

Yes. For urgent, standard change and normal change.

 

18. What are the Retrofit Categories that can be seen?

Red – Manual, Yellow- Semi Automatic , Green -Automatic

You can also display the retrofit status in the Transport Management assignment block.

Comparison of the objects in the source and retrofit systems is also possible.

The implementation status field displays an “I” if the retrofit has been implemented.

 

19. Why is it significant to set the retrofit to completed successfully ?

Only then transport requests no longer appear in the transport request overview for the retrofit. If not it remains in overview for the retrofit and shows status Process Retrofit.

 

20. What are the applicable statuses of Change, that can enable Retrofit Process?

Ensure the changes are brought into below statuses, to start  the Retrofitting.

-Authorized for Production (urgent change)

-Successfully tested (normal change and standard change)

 

21. How to know the criticality of a transport request ?

Open the object list for a particular transport either by double-clicking on the transport request number or by choosing Additional Functions Object List of Transport Request.

 

22. What are the reasons for using manual object import functionality?

-Object is locked in the target system

-Transport contains a SAP Note

-Transport contains special content (for example, PFCG)

 

23. What are the limitations of Auto import option?

All object types are supported including workbench and Customizing. Exception is SAP NetWeaver BW, and Java objects.

 

 

These are the high level details to help you navigate across the retrofit functionality and quickly find the right spot for solution when stuck with support issues. Hope this helps.

Cheers!

1 Comment
You must be Logged on to comment or reply to a post.