SAP Accounting Consulting

Incorrect duplicate check occurs on changing BP name

July 10, 2009 at 3:50 am

[ADDRESS_SEARCH] [BAPI_BUPA_CENTRAL_CHANGE] [BUPA_CENTRAL_CHANGE] [check] [duplicate] [duplicate entry] [incorrect] [login incorrect]

Duplicate Customer Invoice numbering for IndiaSymptom While creating customer invoices for India, the numbering of...
BP DX:Outbound incorrect when ADRU entries are missingSymptom During dataexchange of Business Partners, if the communication data...
0BP_DEF_ADDRESS_ATTR Delta queue updated incorrectlySymptom Whenever changes are made to Address independent communication data...
FS_CHECKMODE: Check for duplicate address guidSymptom 1)Duplicate address guid in but020. 2) Same address guid...
Request Fulfillment Report – Actual End Date incorrectSymptom In the Report ‘Request Fulfillment Report’ in the Work...
SAP BP:Text of Error Message R1 477 and R11 186 is incorrectSymptom Text of Error Message R1 477 is incorrect. Other...
Validity of address independent communication data incorrectSymptom Validity of address independent communication data is inconsistent after...
BYD_HF:Posting date is incorrect in generated DE MT940Symptom After upload of the DE MT940 bank statement file...

Symptom

When the business partner name is changed using Web UI or BAPI_BUPA_CENTRAL_CHANGE or BUPA_CENTRAL_CHANGE, the BP gets identified as a duplicate. However, the results returned are incorrect and do not match the duplicate check criteria.

Other terms

BAPI_BUPA_CENTRAL_CHANGE
BUPA_CENTRAL_CHANGE
ADDRESS_SEARCH
DUPLICATE CHECK

Reason and Prerequisites

The module BUPA_CENTRAL_CHANGE contained structures to accept only central data fields. Hence, on changing a Business partner, the duplicate check was triggered to check only with the name fields. However, the duplicate check should ideally consider a combination of name and address.
Since the duplicate check was called with incomplete data, it was returning wrong results.

Solution

Implement the corrections of this note.
The note contains the following corrections :
1. A new optional importing parameter IS_DUPLICATE_CHECK_ADDRESS has been added to BUPA_CENTRAL_CHANGE. Applications that change the name of the BP using BUPA_CENTRAL_CHANGE can decide which address is to be combined with the name for the purpose of duplicate check and can send the details accordingly.
2.A new optional importing parameter DUPLICATE_CHECK_ADDRESS has been added to BAPI_BUPA_CENTRAL_CHANGE.Applications that change the name of the BP using BAPI_BUPA_CENTRAL_CHANGE can decide which address is to be combined with the name for the purpose of duplicate check and can send the details accordingly.
3. BUPA_CENTRAL_CHANGE contains code corrections to accommodate the address fields also as a part of the duplicate check. In case the application does not pass an address to be included for the duplicate check, BUPA_CENTRAL_CHANGE will use the standard address which is currently valid.

The correction has been released as an advance correction for ABA 700 with changes only in BUPA_CENTRAL_CHANGE. The corrections made to BAPI_BUPA_CENTRAL_CHANGE cannot be applied through a note, but will be integrated through a support pack. The changes for other SAP_ABA releases will also be delivered thorough a support pack.