Each time D&B provides new data, the master data for the InfoObjects DUNS Number (0DBDUNS_NUM) and Customer number (0CUSTOMER) require updating. If you are using a SAP CRM system, the InfoObject Business Partner (0BPARTNER) also requires updating. The data has also to be loaded into the MarketingCube. For this purpose the following files are sent from D&B:
The first time you get data from D&B, D&B provides these files in addition to the files required for initial upload.
For the InfoObjects 0CUSTOMER, 0BPARTNER and 0DBDUNS_NUM new InfoPackages are required. The D&B Marketing Cube (InfoSource 0DB_MKT_1) needs one new InfoPackage as well.
- For the InfoObject 0DBDUNS_NUM you create four InfoPackages for the different data sources:
- One for the text description (data source 0DBDUNS_NUM_TEXT)
- Three for the master data upload (for each data source 0DBDUNS_NUM_ATTR, 0DBDUNS_NUM2_ATTR, 0DBDUNS_NUM3_ATTR).
- For each of the InfoObjects 0CUSTOMER and 0BPARTNER and for the D&B Marketing Cube (InfoSource 0DB_MKT_1) you create one new InfoPackage.
The parameters of the InfoPackages are described in the following tables. Create the InfoPackages with this information.
InfoPackages 0DBDUNS_NUM_TEXT, 0DBDUNS_NUM_ATTR and 0DBDUNS_NUM3_ATTR
Tab | Field | Value |
Select data | ||
No entries required | ||
External data | ||
Load external data from | Application server | |
File name | A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_ABSTRACT_MU.CSV for InfoPackage 0DBDUNS_NUM_ATTR D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_CONT_MU.csv for InfoPackage 0DBDUNS_NUM3_ATTR D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_TEXT_MU.csv for InfoPackage 0DBDUNS_NUM_TEXT Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server) | |
Control file | No | |
File type | CSV file | |
Data separator | , | |
Escape sign | " | |
External data parameters | ||
Thousand separator | , | |
Character for decimal point |
| |
Number of headers that should be ignored when loading |
| |
Processing | ||
Update data | Only PSA and then in the InfoObject | |
Update parameters | ||
Update mode | Full update |
InfoPackage 0DBDUNS_NUM2_ATTR, 0CUSTOMER and 0BPARTNER
Tab | Field | Value |
Select data | ||
No entries required | ||
External data | ||
Load external data from | Application server | |
File name | A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DB_IMPORTFILE_MU.csv Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server) | |
Control file | No | |
File type | CSV file | |
Data separator | , | |
Escape sign | " | |
External data parameters | ||
Thousand separator | , | |
Character for decimal point |
| |
Number of headers that should be ignored when loading |
| |
Processing | ||
Update data | Only PSA Update Subsequently in Data Targets Ignore Double Data Records | |
Update parameters | ||
Update mode | Full update |
InfoPackage for InfoSource 0DB_MKT_1
Tab | Field | Value |
Select data | ||
No entries required | ||
External data | ||
Load external data from | Application server | |
File name | A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DB_IMPORTFILE_MU.csv Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server) | |
Control file | No | |
File type | CSV file | |
Data separator | , | |
Escape sign | " | |
External data parameters | ||
Thousand separator | , | |
Character for decimal point |
| |
Number of headers that should be ignored when loading |
| |
Processing | ||
Update data | PSA and then in the InfoObject | |
Data targets | ||
Select data targets Under the column Updating the data target, mark the field that refers to the D&B Marketing Cube | ||
Update parameters | ||
Update mode | Full update | |
Error Handling | Valid records update, reporting possible (request green) | |
Error Handling – Termination by no. errors | 9999999999 |
No comments:
Post a Comment