WDA: DateNavigator returns incorrect values

[] [] [] []

Symptom
The DateNavigator user interface (UI) element returns incorrect data. Year, month, and day are swapped.
Reason and Prerequisites
This problem is caused by a programming error.
This occurs in Release 7.01, Support Package 5.
Solution
Implement the attached correction instructions or import the relevant Support Package.

Incorrect R3 user and Default receiver for pager.

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Symptom
Pager data not being updated correctly in certain Data Exchange scenarios.
Other terms
BAS_COMMUNICATION, PAGER, TELEPHONE, SMS ENABLED, ADR2, ADR13, ADDR_COMM_MAINTAIN, ADDR_COMM_MAINTAIN_INTERNAL, COMMSYNC_SYNCHRONIZE_SMS_PAGER, LSZA0F65, LSZA0F76
Reason and Prerequisites
When an user enters a pager, without it being associated to a telephone
number, for a particular address, a select query is done on the
telephone data that is being created. This results [...]

Job refers to incorrect spool request

[] [] [] []

Symptom
You want to display the spool request for a job step in transaction SM37. However, the system displays a spool request that does not seem to correspond to the relevant job.
Reason and Prerequisites
The spool request that originally corresponded to this job was deleted in the meantime. The number was then used again [...]

Where-used list incorrect for includes

[] [] [] [] [] [] [] []

Symptom
The where-used list for includes does not find all usage locations.
Other terms
WBCROSSI, SE38, where-used list
Reason and Prerequisites
This problem is caused by a program error.
Solution
Implement the advance correction or import the specified Support Package.
To generate the where-used list index, you must rerun the SAPRSEUB report after you implement the advance correction. Schedule the report in [...]