When the fields Phone and Mobile are set as Mandatory it is possible to perform a Save without the actual phone number being maintained if a '.' (full stop) is entered instead.
Reproducing the Issue
Prerequisite: Phone and Mobile fields are set to Mandatory on the Contact.
- Go to the Customers work centre.
- Go to the Contacts view.
- Create a new Contact.
- For the fields Phone and / or Mobile, enter a full stop '.'.
- Click Save.
RESULT: the full stop vanishes, however, the save is executed. Both fields now appear without value.
In the system in the Contact quick create view, the fields Phone and Mobile have been marked as Mandatory using the KUT (key user tools).
In such a case the mandatory check (if a field is empty or not) is performed at client level.
If '.' is entered, the client mandatory check goes through, but in the backend (BO) we have a parser for phone/mobile/fax which removes unnecessary characters (in this case '.') automatically and therefore it's possible to perform the save even if phone/mobile is empty.
This is expected system behaviour.
If a "real" mandatory check is required and you want to guarantee that for every newly created contact in the system phone/mobile is filled we recommend to implement such a check via PDI.
KBA , SRD-FIN-GL , General Ledger , How To