In this blog, I have detailed the steps taken for SAP BODS application migration from existing on premises to HANA database including the DR Testing Setup.
The Purpose of this blog is to provide a guidance path for migration of the BODS Application to HANA.
Existing Landscape Design:
1. The IPS and DS version remain the same as on premises.
As the SAP Basis administrator, we understand how to set up a trusted RFC connection between ABAP systems. This allows us to connect to the target system using our current user credentials, without needing to input them again, as shown in the screenshot. I hope this blog post finds you in good health. If you have any questions or concerns, please don't hesitate to reach out to me.
But what if we want to use a specific technical user and still want to benefit from trusted RFC? Actually, we can do it with the same method and I will show you how in this blog post.
I would like to share with you a method I wrote in my last S/4HANA 2022 Assetmanagement Project to identify from ABAP side (Userexit, BADI, Enhancement, ...) the UserInterface (UI) Technology ("WinGUI", "htmlbased GUI", "WebDynpro", "Fiori", ...) the user is currently using.
Many time there are custom requirements for which it requires the need of creating Enhancement in standard SAP functionality.
Overview: PO Approvers are maintained in Release Strategy. Once the PO is generated it is set to be approved by PO approvers based on the levels maintained in PPOME structure. Only then the PO will be set to 03 status in EKKO.
Pre-requisite: All the roles and authorization must be given to the approvers to access the PO Approval Tile in SAP Fiori.