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 datacleansing scenario 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 returns the enriched data file to the SAP System. An import
program then writes the 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 identificationnumber are identified as duplicates, and so-called cleansing cases arecreated.

• 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.

Selection
First the user has to select the type of BIP identification number (e.g.BUP001 for the Dun & Bradstreet number) in accordance with theCustomizing table TB039A. In addition, the user must specify whether afile is a local file or an application server file, the name of the fileand whether a detailed log is required.
A file name consisting of the SAP name and the current date is suggestedto the user. In addition, the user can determine which business partnerdata records are exported, by entering the creation date, the businesspartner number, the maximum number of hits and the archiving flag.Optionally, a data record that has previously been identified as a 'nohit' record can also be exported. The 'no hit' records can be displayedusing the transaction show no hit entries

The export program reads existing identification numbers according tothe chosen identification type. A business partner data record istransferred to the data cleansing export file only if it does notalready have a unique BIP identification number.

Output
If the user specifies that detailed logging is required, then eachexported data record is displayed with its business partner number, theBIP identification number and some address data in an ALV list.
Two files are always produced. The file with the extension XML containsthe current data records that are to be enriched. The file with theextension XSD contains a description of the XML file
The structure of the created export file is XML-based. The customersends this file to the business information provider. The businessinformation provider will usually enrich this file within approximately1-2 weeks.





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
_

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
_

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





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