Identifier “Mobile Phone” 

Process Model

The address management provides the identifier “mobile phone”. This enables the following process:

·        It is possible to maintain mobile phones independent of the fixed network.

The identifier is registered in the phone table ADR2 and the corresponding dialog structure ADTEL in the field R3_USER.

Data Model

Field ADR2-R3_USER is used to register whether a phone is a mobile phone or not.

The ‘mobile phone’ identifier is considered in the dialog in such a way that the default mobile phone number can be maintained on the main window and that the fixed net numbers and the mobile phone numbers can be maintained on separate details dialog windows.

For both fixed net phones and mobile phones one number must be set as default (called local default from now on). This number can be maintained on the main window.

Various processes require a default number among all phone numbers. This problem was solved as follows: The default among all phone numbers is registered as usual in field ADR2-FLG_DEFAULT.

The field ADR2-R3_USER, which contains the ‘mobile phone’ identifier, is extended to a length of four characters and additionally contains the information which phone number is the respective local default. The individual values are:

Value	Description
SPACE	The phone number is a fixed net number
1	The phone number is the default fixed net number
2	The phone number is a mobile phone number
3	The phone number is the default mobile phone number

The default among all phone numbers is the local default as well.

In old records created before this development, the default fixed net number has the value ADR2-R3_USER = SPACE.

The ‘Default’ field on the details dialog windows for fixed net and mobile phone numbers always identifies the local default.

On both details dialog windows, there is a two-character input field ‘Preferred’ that you use to determine which local default is the default for all phone numbers. The possible values in the dropdown list box are “Fixed Net” and Mobile Phone”.

Maintaining Country Settings

You can customize for each country whether for a new mobile phone number the system should propose the ‘SMS-enabled’ identifier. To customize this, use transactions

·        OY09

·        SM30, view V_T005K_1

·        SPRO, IMG path General Settings → Set Countries → Maintain Mobile Phone Properties

This is only a proposal; the identifier can be changed at will.

To be able to do this, the field MOBILE_SMS was added to table T005K and the new view V_T005K_1 was created.

Identifying Mobile Phone Numbers

To facilitate the identification of mobile phone numbers that were up to now maintained simply as “phone numbers”, the dialog window for fixed net phone number offers a function “Convert to Mobile Phone Number”. On the dialog window for mobile phone numbers, there is the corresponding function “Convert to Fixed Net Number”.

When converting a mobile phone number into a fixed net number, the value for the “SMS-enabled” identifier is kept. When converting a fixed net number into a mobile phone number, the flag T005K-MOBILE_SMS is evaluated and a fixed net number that was not SMS-enabled becomes SMS-enabled if the flag is set.

Processing Blocks

Transactions

The new transaction OY09 allows you to customize for each country whether to propose the identifier ‘SMS-enabled’ in the dialog for creating a new mobile phone number. This is only a proposal; the identifier can be changed at will.

Function Modules

Existing Function Modules

As the structure ADTEL was not changed, all existing function modules work as usual (especially ADDR_COMM_GET, ADDR_COMM_MAINTAIN, etc.); only field ADTEL-R3_USER passes additional information.