Data & system migrations
SWPC Continue workflows after system crash
In order to ensure the necessary expertise both in the direction of application and application-related IT departments as well as in the direction of infrastructure units, the SAP basis should be divided into an infrastructure-related SAP basis and an application-orientated SAP basis. The infrastructure-based SAP basis acts as a contact level and point of contact for IT departments such as virtualisation, storage management and databases. The application-orientated SAP basis serves as the contact and coordination level for application-related topics. BUILDING OVERARCHING EXPERT TEAMS WITH SAP basis INVOLVEMENT To reduce organisational friction points as well as to optimally handle selected topics, it is recommended to set up expert teams with the participation of the SAP basis. These teams of experts can be virtually organised and therefore of temporary duration and consist of participants from all relevant IT disciplines or business areas. If the topic of the virtual group of experts is the focus of the SAP basis, the SAP basis will take over the management and control of the expert team.
A BW system often plays a very central role in larger companies. Here the data from the various connected source systems are analysed and reported centrally. A previous customer of mine had a BW system, to which a total of over 20 other SAPP production systems were connected. With such a large and mostly living system landscape, it is normal that individual systems are dismantled from time to time. However, especially with large SAP landscapes, there are strict regulations regarding the permissions of technical RFC users. For this reason, the simple "right-click —> delete" of a source system in RSA1 will often not lead to the target, but rather to a failed permission check. With this blog post, I'll show you a workaround on how to clean a source system from a BW system using the RSAR_LOGICAL_SYSTEM_DELETE and RSAP_BIW_DISCONNECT function blocks.
CHANGE TO A NEW ROLE APPROACH
In order for your SAP system landscape to function permanently, it requires error-free installation and regular support. You can rely on these services:
INTRODUCTION A growing number of SAP-based departments are facing major changes and challenges within the SAP product portfolio as well as in their own task environment. These result from influences of digitalisation, digital transformation, new technologies such as cloud computing or big data, but also developments such as customer experience or the Internet of Things. In order to overcome the challenges and to transform the existing SAP basis, recommendations for action are grouped in seven thematic areas. These topics cover the areas of skills and roles (cloud and supplier management, strengthening of the technology architect, focus on project work), marketing and self-understanding (creation of a service catalogue, regular exchange with the CIO, renaming of the SAP basis), new technologies and innovation (test and innovation lab, proactive & regular training), organisation in change (development of the two subject areas close to structure and application-orientated , virtual teams of experts), standardisation and automation (automation of routine tasks, outtasking of rare tasks), "cloudability", outsourcing & outtasking (assessment of usefulness for the cloud, use of appropriate service forms) and IT roadmap (influence of own IT roadmap). By reflecting on the thematic areas, methods and possibilities for implementing the recommendations are presented.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
Select Back to return to the SPAM entry screen.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
They also need to be able to work in a structured manner and find creative solutions and decisions.