Installation Services in all common environments
Troubleshooting and support (2nd and 3rd level support)
Then go back to the Permissions tab to generate the current profile of the permission objects. Once you have completed these steps and secured the role, it has the necessary Fiori permissions to launch the OData service-related application.
I recommend that you schedule the background job PFCG_TIME_DEPENDENCY with the report RHAUTUPD_NEW. Scheduling the RHAUTUPD_NEW report with two variants has proven to be a best practice: Once a day before users log on for the first time (e.g. midnight or very early in the morning). This way the users are synchronized once a day. Once a month (or even once a week) with the option "Perform cleanup", so that obsolete profiles and user mappings are regularly cleaned up. Also handy: If the naming conventions of your roles allow it, you can also align the report according to different time zones. For example, I have a customer who runs the user synchronization for his users in the USA and Asia at different times, so that the daily business of the respective users is not disturbed.
Transaction Code Description
Within SAP R/3 Enterprise, the SAP Basis Plug-In is a prerequisite for you to use the SAP R/3 Plug-In. SAP Basis Plug-In and SAP R/3 Plug-In must always have the same release level, for example PI 2004.1 and PI Basis 2004.1. If you plan to upgrade SAP R/3 Plug-In within SAP R/3 Enterprise, you must also upgrade SAP Basis Plug-In. As of SAP Basis Plug-In 2005.1, the release levels of the two plug-ins no longer need to correspond. However, the SAP R/3 Plug-In Support Package for PI 2004.1, which contains new interfaces, still requires a specific SAP Basis Plug-In. For example, SAP R/3 Plug-In Support Package 10 for SAP Plug-In 2004.1 requires SAP Basis Plug-In 2005.1.
The support packages were successfully fed into a system (test or development system). You performed the modification synchronisation. Procedure Load the support packages into the next system (quality or production system). You must distinguish between the following cases: Their systems have a common transport directory: Release Level 3.x: If the *.ATT files are not present, run RSEPSDOL in the source system and then RSEPSUPL in the target system. If the *.ATT files are present, run only RSEPSUPL in the target system. Release level 4.x: Select SPAM Support Package Upload in the target system. Your systems do not have a common transport directory: Release Level 3.x: Run RSEPSDOL in the source system to create the *.ATT files if they do not already exist. With ftp, transfer all files with the *.PAT extension in binary mode and all files with the *.ATT extension in ASCII mode from the /usr/sap/trans/EPS/in directory (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) of the source system to the target system transport directory. Run RSEPSUPL in the target system. Release level 4.x: With ftp in binary mode, transfer all files with the *.PAT extension from the source system's /usr/sap/trans/EPS/in (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) directory to the target system's transport directory. Select SPAM Support Package Upload in the target system. Play the Support Packages as usual. Import the Modification Balance Transport. Steps of the SPAM The SAP Patch Manager informs you about the step in progress in the status bar. If you want to know what steps are being performed for which scenario, run RSSPAM10.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
After that, these roles should be exported from the system (for example, to an Excel file) and then submitted to the supervisor so that he can decide whether the role assignment is appropriate or not.
On www.sap-corner.de you will also find useful information about SAP basis.
The presentation view is used to visualize the applications and data for the user.