The report RSUSR_CUA_LANDSCAPE_CHECK enables you to analyze the RFC connections of an existing CUA landscape. It can only be executed in the CUA central system.
Based on the current definition in the CUA, all RFC connections between the central system and the connected child systems are checked in both directions. Therefore, the report does not have a selection screen.
The first result list shows the results of the check from the perspective of the central system. If you navigate forward to a child system in the first column, you get a new result list from the perspective of the selected child system, in the direction of its central system (known locally).
Results List for CUA Landscape
The header part of the results list contains the following information about the central system of the CUA:
- SID
- Client
- Logical system name
- Which user performed this evaluation and when?
- Instance numbers of the application servers of the system
- Host names of all active application servers
- IP addresses of the application servers of the system
The model name of the CUA is mentioned in the heading of the ALV list.
The ALV list has a line for each CUA child system containing the following information:
- Child System
- If the child system already supports this new function, you can double-click this field to get to the results list for the RFC return connection from this CUA child system to the CUA central system.
- The information displayed there is described in more detail below.
- Status
- For any status other than “green”, you can double-click this field to get a BAL (Business Application Log) dialog window with the corresponding error messages.
- If a child system does not yet support this new function, this is displayed as a warning.
- Model
- This column shows the CUA model name.
- LogSys(CeS)
- This is the logical system name of the child system configured in the CUA central system. If you double-click this field, the corresponding RFC destination (transaction SM59) is displayed.
- LogS(ChS)
- This is the logical system name of the child system as defined in the CUA child system itself (transaction SCC4). In rare cases (for example, after a system copy), the logical system name defined in the child system may not be identical to the name in the CUA definition in the CUA central system.
- You can easily identify this inconsistency by comparing this column with the “LogS(CeS)” column.
- Host Name of Child System
- If the RFC destination for this child system is set to exactly one server without load balancing (transaction SM59, “Target System Settings” box, value: “No”), the “Host Name” or “IP Address” setting in the same box determines which of the two values is shown in this field. If the RFC destination is defined with load balancing (transaction SM59, “Target System Settings” box, value: “Yes”), the field contains the SID, the logon group, and the message server.
- Inst. No.
- If the RFC destination for this child system is set without load balancing, the instance number is displayed in this field. If the RFC destination is working with load balancing, this field is empty.
- Cl. in ChS
- This field contains the number of the client in this child system.
- User in ChS
- This field displays the user name used in the RFC destination for the CUA child system. If the RFC connection to this child system is configured accordingly (the user has the necessary rights and is a dialog-enabled user), you can double-click to go to the display of this user in the child system.
- Rec. Type
- A traffic light shows whether the RFC user used in the child system has a user type recommended by SAP. If it has the type ‘Communication’ or ‘System’ the traffic light is green, otherwise it is red.
- Users with the type ‘Communication’ or ‘System’ are not dialog-enabled and therefore cannot be used for an interactive logon using SAP GUI.
- SAP_BASIS SP
- This displays the SAP_BASIS support package used in this child system.
- Conn. Test
- A traffic light shows whether the RFC connection test to the CUA child system was successful or not.
- If it is red, the test was not successful and the status column in the results lists shows an error.
- Logon Test
- A traffic light shows whether the attempt to log on to the CUA child system was successful or not.
- If it is red, the attempt was not successful and the status column in the results lists shows an error.
- Errors
- A traffic light shows whether RFC calls with errors exist in the CUA child system. Using forward navigation, you can display them in transaction SM58.
- You can also get this information on the initial screen of transaction SCUL, by choosing “Check tRFC with Errors” (CTRL + F1).
- ATCR
- A traffic light shows whether the child system supports automatic text comparison for roles. (See SAP Note 1642106)
- BP
- This column contains an information icon as soon as the child system supports business partner assignments to users. No changes can be made in user administration to the address data of users that a business partner is assigned to. This has to be done via the business partner.
- These users normally do not have a business partner assignment yet in the CUA central system and thus do not have the usual address data of a user. Address data changes in the CUA central system are always sent to the child systems. In the child system however, these are ignored during IDoc inbound processing in the case of users with a business partner assigned.
Results List for Child Systems
The results list of the selected child system contains exactly one line. This is the RFC connection from the CUA child system back to its central system. If this return connection to the CUA central system does not work, this could be the cause of problems in the areas mentioned below:
- The status confirmations of IDoc inbound processing to the CUA central system. You can view this in transaction SCUL. If an IDoc has a “gray” traffic light, this means that the confirmation of inbound processing from the child system is missing in the central system.
- The text comparison of role and profile names, as well as license data, from the CUA child system to the CUA central system. If this fails, new roles, profiles, and price list data in the CUA central system cannot be used for assignments to users.
- The synchronization of user attributes set to “Redistribution” does not take place (see transaction SCUM).
- The different, application-related user administrations in a CUA child system (for example, CRM-ISA or SAP E-Recruiting) cannot create the new users they create locally in the CUA central system at the same time, or perform global role assignments there.
The results list of the child system consists of the following columns:
- Child System
- Status
- For any status other than “green”, you can double-click this field to get a BAL (Business Application Log) dialog window with the corresponding error messages. The quick info for this field provides some error information.
- Model
- The model name known locally in the child system.
- The child system “affiliates” itself with this model.
- LogSys(CeS)
- This is the logical system name of the CUA central system that is known in this CUA child system. This is the system to which the child system uses a direct RFC call to send the status information from IDoc inbound processing, for example.
- LogS(ChS)
- This is the logical system name of the child system as defined in this CUA child system (transaction SCC4).
- Host Name of Central System
- If the RFC destination for this CUA central system is set to exactly one server without load balancing (transaction SM59, “Target System Settings” box, value: “No”), the “Host Name” or “IP Address” setting in the same box determines which of the two values is shown in this field.
- If the RFC destination is defined with load balancing (transaction SM59, “Target System Settings” box, value: “Yes”), the field contains the SID, the logon group, and the message server.
- Inst. No.
- If the RFC destination for the CUA central system is set without load balancing, the instance number is displayed in this field. If the RFC destination is working with load balancing, this field is empty.
- Cl. in CeS
- This field contains the number of the client in the CUA central system.
- User in CS
- This field displays the user name used in the RFC destination for the CUA central system. You can double-click to go to the display of this user in the CUA central system.
- Rec. Type
- A traffic light shows whether the RFC user used in the central system has a user type recommended by SAP. If it has the type ‘Communication’ or ‘System’ the traffic light is green, otherwise it is red.
- Users with the type ‘Communication’ or ‘System’ are not dialog-enabled and therefore cannot be used for an interactive logon using SAP GUI.
- Conn. Test
- A traffic light shows whether the connection test to the CUA central system was successful or not.
- If it is red, the test was not successful and the status column in the results lists shows an error.
- Logon Test
- A traffic light shows whether the attempt to log on to the CUA central system (with the user defined in the RFC connection) was successful. If it is red, the attempt was not successful and the status column in the results lists shows an error.
- Errors
- A traffic light shows whether RFC calls with errors exist in the CUA central system.
- In this view, you cannot branch to transaction SM58 to display it, since there is no remote-enabled function for this transaction.
- Alternatively, you can log on to this child system, and start transaction SM58 there with the following parameters:
- Select the period you want to display.
- Instead of your own user name, which is set as the default, choose *.
- In the TRFC Function field, replace the default * value with the function module name SUSR_USER_RESPONSE.
- In the TRFC Destination field, replace the default * value with the logical system name of the CUA central system.
- In the TRFC Status field, delete the default * value and use multiple selection to enter the values RECORDED, SYSFAIL, and CPICERR.
Purpose
Due to the complexity of the system and CUA landscapes, some CUA child systems may be temporarily unavailable or may not be correctly configured. The report supports troubleshooting in the distribution process within the CUA landscape.
Requirements
Note that for each CUA child system you have to perform a check for each direction: to and from the CUA central system. These checks may take some time, depending on the availability and response times of the systems. Therefore, the display of the CUA landscape in transaction SCUA gives you the option to select particular child systems to check.
