Correction report for communication data inconsistencies
[ADR2] [ADR3] [AM891] [BAS_COMMUNICATION] [FLG_COMM] [SAPSQL_ARRAY_INSERT_D]
Related:
- Address Communication data: Setting of Time-Dependent flags.Symptom The default communication data is not getting set with...
- Correction report – Address Communication UsagesSymptom Errors in Time dependent Address communication data. Other terms...
- Extension for the Note 436119Symptom The communication data on the database is inconsistent in...
Symptom
The communication data on the database is inconsistent in the address data.
This can have the following effects, for example:
When you change a user through the CUA, the booking in of the IDOC USERCLONE terminates in the target system with the SAPSQL_ARRAY_INSERT_DUPREC
Other terms
ADR2, ADR3, FLG_COMM, AM891, BAS_COMMUNICATION
BAS_COMMUNICATION
SAPSQL_ARRAY_INSERT_DUPREC
COMM_A_IN_MEMORY
MESSAGE_TYPE_X
Reason and Prerequisites
This problem is caused by a data inconsistency.
Version 8 of the correction instructions contains program errors. Use version 10.
Solution
Copy the attached Z_OSSNOTE_436119 report into your system and execute it.
If you start the report with the ALLCLNT = ‘X’ parameter, the check happens not only in the current client, but also in all clients of the system.
There are no changes to the database if you start the report with the TESTRUN = ‘X’ parameter but the entire error log is issued.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}