Address Communication data: Setting of Time-Dependent flags.

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

Related:

  1. Correction report for communication data inconsistenciesSymptom The communication data on the database is inconsistent in...
  2. Correction report – Address Communication UsagesSymptom Errors in Time dependent Address communication data. Other terms...
  3. Extension for the Note 436119Symptom The communication data on the database is inconsistent in...

Symptom
The default communication data is not getting set with respect to time.
Other terms
BAS_COMMUNICATION
ADR2, ADR3, ADR4, ADR5, ADR6, ADR7, ADR8, ADR9, ADR10, ADR11, ADR12, ADR13,
R3_USER, AD_DEFAULT,
Reason and Prerequisites
After 640 release, Time Dependency is introduced in Address communication tables. ADRU table introduced for Time dependency which stores the Default Validities for each communication data. There are some respective flags like flgdefault & r3_user to be set in tables ADR2 to ADR13 based on the time maintained in the ADRU table. Some applications rely on the flags to determine the current default communication data. The flags in these tables should be synchronized with ADRU time validity. If it is not, then application which directly read ADR2 to ADR13 tables will get wrong results.
Prerequistes:
The data in the tables ADR2 to ADR13 and ADRU should be consistent. If there is any inconsistency this report will not update such records. Please refer the note 1158803 for inconsistency in these tables.This report will only set the flags which determines the current default communication data in ADR2 to ADR13.There will no log, no test run and no input parameters required for this report.
Solution
Report is attached in the correction instruction.
Recommedations:
Please run this reprot in Background job.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment