Ansicht
Dokumentation
RS_UPDATE_TRUST_RELATIONS - Update Trust Relationships to System (SAP Note 1491645)
BAL Application Log Documentation CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Purpose
This report is used to update the trust relationships of all system that trust the current system (in accordance with SAP Note 1498973). This update moves these trust relationshipts to a higher security level.
Integration
SAP Notes 1491645 and 1498973 must be imported into all involved systems before this report can be run.
The report must be started manually in all systems in the landscape to enable existing trust relationships between these systems to be updated. It does not matter in which order the report is started.
The report can be paused and resumed. The report detects trust relationships that are already up-to-date and does not update them again.
Trust relationships not updated by this report can be updated manually by being deleted in in the trusting system and created again (both in transaction SMT1).
Prerequisites
1. SAP Note 1491645 must have been imported in the current system and all systems that trust this system.
2. If the profile parameter "rfc/security_key" is set in the current system, it is negated when the trust relationships are updated using this report. It is advisable to delete this profile parameter after running the report and restarted the affected instances.
3. The user used to run the report requires the following authorizations:
o,,Authorization object S_ADMI_FCD with the field S_ADMI_FCD and the value NADM.
o,,Plus (from SAP Basis Release 7.02): Authorization object: "S_RFC_TT" with the following values:
o,,Field ACTVT with the value "2" (Change)
o,,Field RFC_TT_TYP with the value "2" (calling system)
o,,Field RFC_SYSID with the value <system ID of the current system>
o,,Field RFC_INSTNR with the value <installation number of the current system>, if available.
4. The user used to run the function module in the trusting system requires the following RFC authorization:
o,,Authorization S_RFC:
o,,Field RFC_TYPE with the value FUGR
o,,Field RFC_NAME with the value QRFC
o,,Field ACTVT with the value 16 (Execute)
o,,Comment: From Release 7.02, the RFC user can be given the required authorization based on remote-enabled function modules:
o,,Field RFC_TYPE with the value FUNC
o,,Field RFC_NAME with the value RFC_UPDATE_TRUST_RELATION
o,,Field ACTVT with the value 16 (Execute)
Features
The report is executed in several phases: Prerequisite check, automatic connection, manual connection, and the actual update of the trust relationships.
Phase 1: Prerequisite check.
o,,If the profile parameter "rfc/security_key" is set in the current system, a confirmation dialog box queries whether the user wants to run the report. This profile parameter is negated when the trust relationships are updated. It is advisable to delete this profile parameter (either before of after you run the report).
o,,Authorization checks in the current system (see above).
o,,If the current system has a trust relationship to itself, a check runs (for releases before 7.02) to see whether the database ID of the current system matches the ID derived from the trust relationship. This is necessary for the unique identification of the system; a unique identification by the installation number is only available from Release 7.02.
Phase 2: Automatic connection.
The report attempts to create an RFC connection to the trusting system, using the data stored in the trust relationship. At the same time, it checks whether all prerequisites for the successful update of the trust relationship are met in the trusting system (authorizations, existence of the function module, and so on). If a connection error occurs, the system makes multiple separate connection attempts.
The results of these checks for all systems trusting the current system are displayed in a table. If you select one or more rows in the table and choose "Error Details", detailed information about the check results in question is displayed in a separate window. You can close this window again by choosing "Back to Overview".
The icons in the first column of the check results table have the following meanings:
Red traffic light: No connection was made or the prerequisites for the update are not met. No solution can be provided by the report itself.
Yellow traffic light: A logon error occurred. The user can also log on manually (using a logon window), see phase 3.
Green traffic light: The connection was made and all prerequisites for the update are met.
"Chequered Flag" icon: The trust relationship has been updated.
Phase 3: Manual connection.
For systems where an automatic connection in phase 2 failed due to a logon error, you have the option of performing a manual logon in a logon window. To do this, select the row in question in the table and choose "Manual Logon" on the far right of the toolbar in the table. If the logon fails, or the user closes the logon window, this is indicated in the table. You can then attempt a new manual logon in the same way.
The user can also choose "Connect" for the selected connection to make a new connection attempt. The communication timeout can be entered in a dialog box (between 1 and 300 seconds).
Phase 4: Update (of the trust relationships)
By choosing the "Update" button, the trust relationships are updated in all selected systems where an RFC connection was made (either automatically in phase 2 or manually in phase 3) and indicated accordingly by a green light in the table.
There are two options for non-updated trust relationships:
1) Remove the cause of the error and run the report again.
2) Update the trusted relationship manually from the trusting system using transaction SMT1. Here, the trust relationship must be deleted manually in the trusting system and created again.,,
Output
The display is refreshed each time one of the pushbuttons "Connect", "Manual Logon", or "Update" is chosen.
TXBHW - Original Tax Base Amount in Local Currency General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 6456 Date: 20240520 Time: 114107 sap01-206 ( 108 ms )
