Basis Errors and Solutions

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 [...]

Symptom
Erroneous behaviour in the BP screen.
Other terms
BAS_SCREEN, SCREENS, 0200, SAPLSZA6, LSZA6F52, ASSURE_ONE_ENTRY, BP,
ADDRESS DEPENDENT COMMUNICATION, BAS_COMMUNICATION, ADDRESS INDEPENDENT COMMUNICATION.
Reason and Prerequisites
When a particular screen field is called for display, it takes on the attributes of the previous screen field. this is because the attributes of the previous screen field are not cleared. This [...]

Symptom
When you move the communication data from NTD system to TD system, FLGDEFAULT flag is not set properly for the right telephone number.
Other terms
BAS_COMMUNICATION, FLGDEFAULT
Reason and Prerequisites
Due to absense of sorting of the time interval, FLGDEFAULT is not set correctly for the right telephone number.
Solution
Please implement the attached source code instruction.
PLEASE DONOT IMPLEMENT THIS [...]

Symptom
Address communication data cannot be add/modify for the future validity.
Other terms
BAS_communication, AM 892, Internal error,
ADTEL
ADDR_COMM_MAINTAIN
Reason and Prerequisites
When trying to add or modify communication data (telephone, mobile…)
internal error is thrown.
Solution
Program error. Please apply the corrections.

Symptom
When communication type RML is changed from
Address Dependent Comm. type to Address Independent Comm. type and
vice-versa, a dump is thrown.
Other terms
RML
BAS_COMMUNICATION
Reason and Prerequisites
Program error
Solution
Kindly implement the correction instructions.