Title
Data Cleansing Using a Business Information Provider: Data Import

Purpose
This report allows you to use the data cleansing services of a businessinformation provider (BIP) (for example Dun & Bradstreet, Buergel,Schober, Hoppenstedt, Creditreform) in an integrated data cleansingscenario for the SAP Business Partner.
In the context of this BIP integration, a business process was definedthat identifies and eliminates duplicates in the SAP Business Partnermaster data. This process is calleddata cleansing and consistsof four phases:

• Business partner data (business partner number and address data) is
exported to the BIP in XML file format, via floppy disc, the Internet orFTP.

• The BIP compares this exported data with the data in its own database.
If there is a match, then the data record in question will be enrichedwith a unique BIP identification number (e.g. DUNS number).

• The BIP sends the enriched data file back to the SAP System. An import
program then writes the BIP identification numbers to the correspondingbusiness partner master records. Business partner records for which noBIP identification number exists are stored as 'no hit' records in thedatabase. If required, data records with the same identification numberare identified as duplicates, and cleansing cases are created.

• If cleansing cases exist, they can be processed using a standard SAP BP
transaction. In this way it is possible to compare and, if necessary,merge the duplicate records.

Prerequisites
This report should run as a background job, since it typically exportsseveral thousand business partner data records from the SAP System.Thus it is important that the export file is stored on an applicationserver of the SAP system.

Selection
The user has the possibility to specify the type of import file to becreated, i.e. whether it should be a data enrichment file or a cleansingfile. In the latter case, the user chooses to create cleansing casesfor identified duplicates in the SAP System. Data cleansing cases canbe created for duplicates that have been identified in one of thefollowing three ways:


• Two or more data records in the import file have been assigned the same
BIP identification number.

• A comparison is made between the BIP identification numbers in the
export file and those in the SAP System.

• A search is carried out for duplicates in the existing business partner
master records in the SAP System.
In addition, the user has the possibility to specify whether the importfile for data cleansing should be a local file or an application serverfile, the name of the import file and whether a detailed log isrequired. The user can specify the name of an error file in order to beable to restart more quickly in the case of a termination. The errorfile contains all the business partner records that could not beimported. After the errors have been removed, this file can be usedagain as an import file.

Output
If the user specifies that detailed logging is required, then eachimported data record is displayed in an ALV list with its businesspartner number, the BIP identification number and some address data.
The import program writes these identification numbers to thecorresponding business partner master records. If errors occur duringthis process, the data record is stored in the error file specified onthe selection screen of the import program.
In some cases, the business information provider will not find anidentification number for every business partner record that was sent toit. Business partner records for which no BIP identification numberexists are called 'no hit' records. Due to the fact, that these 'nohit' records might be of interest to customers, they are stored in thedatabase and can be displayed using the transactionshow no hit entries.
If the import file has identified duplicates, the resulting cleansingcases can be processed using the standard SAP BP transaction for datacleansing: BUPA_CLEAR





A4C
000
us02d2
620
WEBERMA
2002-08-22
16:06:16
CET
BUPA_BIP_FILE_EXPORT
E
CRM001
External System Identifier
76987698/123/2002 SCHOBER
Please sent back to muster.mann@sap.com<(>
<<)>/BIP_COMMENT>




0000000130
2
80-473-5132 <(>
<<)>/IDENTIFICATIONNUMBER>

Smith, Brian A



X
NORTH CONWAY
03860
Milky Way 17
US
US
NH
EST



US
US
X
905 555-4472
+19055554472
9055554472
X
001


US
US
X
36 70 91 29
+136709129
36709129
X
001



0000000131
2
21-456-7885 <(>
<<)>/IDENTIFICATIONNUMBER>

JPMUNIT
JPMOBILE ORGANIZATIONAL UNIT



X
Koto-ku
1350064
Aomi Frontier Bldg
JP
JP
13
JAPAN



JP
JP
X
03-5531-6900
+81355316900
0355316900
X
001


JP
JP
X
03-5531-6900
+81355316900
0355316900
X
001





######################################################