Default Date Fields For Telephone Numbers

[kevin_hines]

Hello. We are using the function modules BAPI_BUPA_CENTRAL_CHANGE and BAPI_BUPA_ADDRESS_CHANGE to add and expire phone numbers on the business partner. The "Valid From" and "Valid To" dates get updated just fine but the "Default From" and "Default To" dates do not update for phone number that we are expiring and dates do not get inserted for numbers that we add. We have discovered that this is causing an issue when our CSRs attempt to do a Move-In (which creates a parked document). In the ADTEL structure, there are no fields for "Default From" and "Default To" but if you go to the actual BP and enter a number, the fields are populated automatically. Is there a way to populate/change the "Default From/To" fields using the function modules? Thanks.

[oliviawalsh · Accepted solution]

Hello,

For your requirement, you should try to update the original default tel's BAPIADTEL-STD_NO to X, as well as inserting a new entry with BAPIADTEL-STD_NO = BLANK.

Example:

When the telephone number for example 010101 was added to the business partner, the system made the telephone as standard for the period 01.01.2010 to 31.12.9999. But when you add another telephone, there should not be a change in the standard telephone. 010101 was already present as standard for the period 01.01.2010 to 31.12.9999. So the newly added telephone should not be replacing the old telephone. There should not multiple standard telephone numbers for any particular time. This is the reason, the default dates are not filled for both the telephone nos, also the old standard telephone is not replaced by new one.

Hope this helps.

Regards

Olivia

Edited by: Olivia Walsh on Sep 22, 2010 11:21 PM

[kevin_hines]

Thanks for the explanation. Here is how we are using phone numbers.

Most of our customers will have two telephone numbers listed initially. We will differentiate them using the COMMENTS section (in this field, we would specify either HOME or OUTAGE). The "Valid From" date will be the date the number is added. The "Valid To" date will be 12/31/9999". I've noticed the default dates for the first entry matches the "Valid From/To" dates and the default dates for the second entry are blank.

The CSR uses a custom screen to change phone numbers (that calls the bapi BAPI_BUPA_ADDRESS_CHANGE). If they change both numbers, the two existing numbers will have the "Valid To" dates changed to today's date (to show that those numbers have been expired) and two more entries are created to show the new numbers (the "Valid From" date is the day the number was added and the "Valid To" date is 12/31/9999). The original numbers are not deleted since we would like an audit trail of what numbers were active/valid during a given period of time. The problem is that the "Default From/To" fields are never populated for any number but the first (and for the first entry, even though the "Valid To" date changed, the "Default To" date stays as 12/31/9999).

I tried the change you suggested and it did not have any effect. I appears that, when a Move-In is done via CRM, it looks at the "Default From/To" dates (instead of the "Valid From/To Dates") and throws an error since the "Valid To" and "Default To" dates are not the same (this was told to me by another developer).

From your explanation, should the Default Dates never been populated? It seems if you add the number manually via transactions BP or FPP2, it autopopulates those fields when you add a number.

[kevin_hines]

Hello. Just wondering if anyone else have any other possible solutions. Thanks.