You are using transaction SCU0 to do a comparison of objects from a Transport Request. On the result overview screen, you see differences. When you try to go to the detailed comparison of a selected object, no differences are displayed.
This scenario occurs, when the selected objects (views) are present as a part of a View Cluster which is present in the transport request.
Another symptom is that, the system has been converted to Unicode.

Other terms

Unicode, SCU0, transport requests, comparison, no differences, View cluster, 1110588

Reason and Prerequisites

The comparison was not showing any differences because of Unicode issues. The error has been fixed in code.

Solution

Kindly apply corrections in note, or apply the relevant support packges.
For SAP_BASIS 700 and lower releases, please refer to the note 1110588

A timeout happens in CL_PROXY_WSDL2ABAP.
Other terms

A typical stack trace within the short dump look like: METHOD CL_PROXY_WSDL2ABAP============CP
CL_PROXY_WSDL2ABAP=>ADD_PROBLEM
METHOD CL_PROXY_WSDL2ABAP============CP
CL_PROXY_WSDL2ABAP=>ABAP_GET_NAMES
METHOD CL_PROXY_WSDL2ABAP============CP
CL_PROXY_WSDL2ABAP=>CONVERT_TO_ABAP
METHOD CL_PROXY======================CP
CL_PROXY=>CREATE_FROM_WSDL
METHOD CL_PROXY_RUNTIME_META_DATA====CP
CL_PROXY_RUNTIME_META_DATA=>WSDL_TO_PROXY
Reason and Prerequisites

Error in Coding
Solution

Correction in Coding

In the ALV grid view (ALV GV), the dropdown list boxes and the links at column level are not displayed.
Other terms

ITS, SAP Internet Transaction Server, SAP GUI FOR HTML, WebGUI, combo, combocontrol, ALV, SAP List Viewer
Reason and Prerequisites

You are using ITS 620.
Solution

Apply the patch specified under “SP Patch Level”.
The correction will be delivered in one of the next patches. This
note will be updated automatically once the exact patch number
is known.

Bei der Erzeugung von Konnektoren zu Templates, welche ODPs enthalten, m黶sen weitere Templates ber點ksichtigt werden, welche nicht aufgrund des Datenmodells erfasst werden. Dies ist bisher nicht ber點ksichtigt.

Ursache und Voraussetzungen

Programmfehler.
L鰏ung

Pflegen Sie die beigef黦te Vorabkorrektur ein.

You use the User Information System (transaction SUIM) to search for users, profiles, or authorizations with specific authorization values.
The functions for sorting and setting filters for the fields “User Type”, “Type”, and “Version” do not work.In a central system with Release 7.00 or higher, you start the report RSUSR200. As the target system, you use a child system with Release 6.40 or lower. The functions for sorting and setting filters do not work for the “Date of Last Logon” field.

Other terms

RSUSR002, RSUSR020, RSUSR030, RSUSR200
S_BCE_68001400, S_BCE_68002111, S_BCE_68001409, S_BCE_68001402
CONVERSION_EXIT_AKTPA_INPUT
CONVERSION_EXIT_USTYP_INPUT
CONVERSION_EXIT_XUTYP_INPUT

Reason and Prerequisites

This problem is caused by a program error.

Solution

Implement the correction instructions or import the relevant Support
Package.
Important: To correct the sorting error in the report RSUSR200, you must implement the corrections in the central system of the Central User Administration (CUA) and in all of the related child systems.

Other terms

SDBI_CLUSTER_CHECK, R3check, TSV_TNEW_PAGE_ALLOC_FAILED
Reason and Prerequisites

The program R3check, which must be started at operating system level, is available to check cluster tables for incorrect records (for example, records that cannot be compressed) The program requires a special input file and it is not easy to operate (also see Note 89384).
The ABAP report SDBI_CLUSTER_CHECK facilitates a simplified check of cluster tables.
However, earlier versions of this report contained errors:
An internal table was not reset and this resulted in TSV_TNEW_PAGE_ALLOC_FAILED terminations.The system displayed very old cluster records as defective. Only non-Unicode systems contain these records. The tables DYSO1 and DSYO2 were previously affected by this error.In the “Error report for SAP”, the system issued an incorrect number of errors found if each table contained more than 9 errors.For Oracle databases in particular, the system issues the error messages ERR_ADD and ERR_NOTF for no reason. In the new versions of the check report, ERR_NOTF is no longer used. Before the system issues error message ERR_ADD, it checks whether an error actually occurred.

New attributes include:
Newer versions of the check report recognize errors in the sorting of the logical records of a cluster record.A version ID exists and the system displays this on the initial screen of the report SDBI_CLUSTER_CHECK and makes a note of this in the check log. The report SDBI_CLUSTER_CHECK_ERRREPORT also outputs the version ID.

Solution

The current version of the report has the ID01.2009.
Always use the latest version of the report.
This current report version is available directly in the Support Packages specified in this note. Alternatively, you can use transaction SNOTE to implement the version for Basis Release 6.20 and higher.For Releases 46C and 46D only, use the attached transport (also see Note 13719).

For more information, see Note1309728(operating instructions) and Note1309804(function and error messages).

This note describes various corrections for transaction SAT.
Since SAP NetWeaver Release 7.11, SAT has been used as a follow-on transaction to transaction SE30 (ABAP runtime analysis).
In Release SAP NetWeaver 7.00 Enhancement Package 2, SAT is used as the follow-on transaction for transaction SE30.
1. The system displays a dialog box with the message
“Trace file not yet written. Do you want to wait?”
if a runtime analysis is already complete and the trace file contains incorrect data.2. The system gives the status “Executed” to the measurement that you scheduled using SAT if the time of the user for which the measurement is planned is one or more hours behind the system time.3. Termination:
Runtime Errors CREATE_DATA_ILLEGAL_LENGTH
Exception CX_SY_CREATE_DATA_ERROR4. When you create or change a measurement variant in SAT, the system displays the error message:
Enter the program type (S7 035)
although the table for program parts is empty.5. The function “Evaluate measurement” in the “Evaluate” overview of transaction SAT does not work correctly for non-aggregated measurements. The measurement is not evaluated and is not displayed in the overview.6. The navigation to the ABAP Dictionary does not work in the “Database Tables” view. The system displays the error message “Select one row only”.7. Release 7.11 only: When you try to display an incorrect measurement or a measurement that was canceled, the system displays a dialog box that is almost empty.8. An error occurs when you navigate to the source code for aggregated measurements that were canceled.9. A termination occurs when you display additional fields (for example, package) in the “Call Hierarchy” view.10. A termination occurs when you measure an XML transformation (runtime error DBIF_REPO_INTERNAL_ERROR).11. A termination occurs when you format a scheduled measurement.

Other terms

SAT, runtime analysis, SE30, ATRA, source code
Reason and Prerequisites
1. The status query contains errors: The system does not distinguish between cancelled measurements and active measurements.2. Time-zone conversion is missing: The system does not convert the user time into UTC before calling the kernel methods.3. The check on the header version of a trace file is missing.4. An error occurs during the dynpro field check.5. An error occurs in the function module ATRA_CREATE_CONTAINER.6. An error occurs during the layout handling of the database tables view.7. A text element for the dialog box is missing.8. An error occurs when formatting the measurement.9. An error occurs when determining the package information for enhancement spots.10. The check for XSLT is missing.11. The initialization of the extended passport components is missing.

Solution

The errors are corrected in the following Support Packages:
1. 7.10: SAPKB71007
7.11: SAPKB711012. 7.10: SAPKB71007
7.11: SAPKB711013. 7.10: SAPKB71007
7.11: SAPKB711014. 7.10: SAPKB71008
7.11: SAPKB711025. 7.11: SAPKB71102, Error does not occur in 7.10.6. 7.10: SAPKB71008
7.11: SAPKB711027. 7.11: SAPKB71103, error does not occur in 7.10.8. 7.10: SAPKB71009
7.11: SAPKB711039. 7.02: SAPKB70201, the error does not occur in other releases.10. 7.11: SAPKB71104
7.20: SAPKB72001
11. 7.11: SAPKB71104
7.20: SAPKB72001

Short dump analysis (transaction ST22) shows several run-time errors SYSTEM_SHMCONSTR_LOGON_FAILED (Login for shared objects area constructor abortive) for shared memory area CLUR_NW7_MESSAGE_AREA and user SAPSYS. The error occurs in background and does not influence normal functionality of applications.
The described run-time error occurs when a user opens a WebDynpro application in a browser and inputs an incorrect user/password/client combination, in case when the shared memory area CLUR_NW7_MESSAGE_AREA has not been created in the system yet.

Reason and Prerequisites

Normally, the shared memory area CLUR_NW7_MESSAGE_AREA is created automatically, when a web dynpro application is executed in the system. However, this does not happen when the logon screen is displayed because the user does not have enough rights to make data changes in the system yet. The system recognizes this situation and proceeds normally, but a short dump is nevertheless created in the background.
Solution

You have two options to avoid the mentioned short dumps in the future:
1. Log on to SAP GUI, start any Web Dynpro application, for example WDR_TEST_UI_ELEMENTS, from transaction se80: the missing shared memory area will be created automatically, or2. Implement the attached source code correction.