rss feed blog search engine
 
Search rss blog search engine
 
SAP Netweaver  
Released:  9/3/2008 10:26:09 PM
RSS Link:  http://allsapnetweavernotes.blogspot.com/feeds/posts/default ..
Last View 11/21/2009 7:00:47 AM
Last Refresh 11/21/2009 5:11:56 AM
Page Views 1293
Comments:  Read user comments (0)
Share



Description:



Cross-Component Programming, Dynamic Programming, Integrating Forms, Integration, Integration of ALV, Interview Questions, List Viewer in Web Dynpro Portal Integration, TCodes, Web Dynpro ABAP


Contents:

Procedure documentation Configuring Size of Data Packets and Frequency

Use

To upload large sized flat files, the setting of the following parameters within the BW Customizing is important:

  • Size of data packets
  • Frequency

For data transfer into BW, the individual data records are sent in packets of variable size. Using the parameters for the size of data packets you can control how large a data packet typically is. If no entry is maintained, the data is transferred with the default setting of 10,000 Kbytes per data packet. Within BW Customizing you can increase this setting to 40,000 Kbytes or higher.

By specifying the frequency, you determine after how many data IDocs an Info IDoc is sent, or how many data IDocs are described by an Info IDoc. Choose a frequency of between 5 and 10, but not greater than 20.

Procedure

  1. Open the customizing tree from the SAP Easy Access menu under the folder Tools
  2. ® Business Engineer.
  3. Double-click on BW Customizing and select SAP Reference IMG.
  4. Expand the tree BW Customizing Implementation Guide
  5. ® Business Information Warehouse ® Links to Other Systems ® Maintain Control Parameters for the data transfer.
  6. Change the parameters as required.



Expanding Table Spaces

Use

SAP recommends that the following table spaces should be expanded:

  • PSAPSTABD
  • PSAPSTABI
  • PSAPFACTD
  • PSAPFACTI
  • PSAPDIMD
  • PSAPDIMI
  • PSAPCLUD
  • PSAPODSI
  • PSAPTEMP

The following table can be used as a guide. It illustrates the table space sizes that are used to upload 1,8 million records based on an Oracle database.

Table space sizes

Table space

Size (kb)

Free

PSAPSTABD

2.048.000

At least 1.6 GB free

PSAPSTABI

2.048.000

At least 1.6 GB free

PSAPFACTD

716.800


PSAPFACTI

965.904


PSAPDIMD

102.400


PSAPDIMI

117.744

At least 40 MB free

PSAPCLUD

51.200


PSAPODSI

2.702.824


PSAPTEMP

5.013.480

At least 5 GB free

Procedure

For detailed information, see SAP note number 184905.




Customizing BW for the Usage of the D&B Marketing Universe

Procedure

  1. In your BW system, select transaction rsmonitor_db.
  2. From the Environment menu, choose D&B Registration.
  3. Create a new scenario using the Create icon.
  4. If you are using a SAP CRM system, choose the logical system name of your CRM system. If you use a 3rd party CRM leave the logical system blank.
  5. In the field CRM Scenarios choose D&B Integration of external Data.
  6. Save your scenario.



Customizing for Business Partner Creation from BW in SAP CRM

Procedure

  1. In your CRM system, register the InfoObject DUNS Number 0DBDUNS_NUM as an identification object for the business partner.

Use transaction sm30 to maintain the table RSCRMEXTERN as follows:

    • Logical System: system name of the CRM system
    • InfoObject: 0DBDUNS_NUM
    • InfoObject: 0BPARTNER
    • ID Category: BUP001 (provided with the customizing of your CRM system)
    • Maximal allowed age of master data (in calendar days): for example 365 for 1 year
  1. Bear in mind that the D&B scenario is a B2B scenario. Therefore only companies and organizations are considered as business partner. To check if the ID category BUP001 is valid for organizations proceed as follows:
    • In your CRM system, use transaction sm30 to display the table v_tab039A.
    • Mark the row with BUP001 and click on the Details icon.

The Identificationtype should be relevant for organizations only.




InfoPackages for Initial Upload

Together with the first D&B data files you also receive some D&B files containing customer-independent information. These files need to be uploaded only once. To prepare the upload process you create the required InfoPackages.

The following table shows the files you get from D&B for the initial upload. For each file you create one InfoPackage. In the right column you see the InfoObjects to which the new InfoPackages belong.

D&B File

Technical name

InfoObject for which you create the InfoPackage

Legal Status Text File

0DBLGLSTAT_TEXT.CSV

0DBLGLSTAT

D&B Rating Net Worth - Text

0DBRATENW_TEXT_MU.CSV

0DBRATENW

D&B Rating Condition – Text

0DBRATECON_TEXT_MU.CSV

0DBRATECON

D&B Score - Text

0DBSCORE_TEXT_MU.CSV

0DBSCORE

D&B Sector Code - Text

0DBSECTCOD_TEXT_MU.CSV

0DBSECTCOD

Country Code Text File

0DBCTRYCOD_TEXT.CSV

0DBCTRYCOD

D&B Region Code - Text

0DBREGCOD_TEXT_MU.CSV

0DBREGCOD

D&B Area Code - Text

0DBAREACOD_TEXT_MU.CSV

0DBAREACOD

D&B District Code - Text

0DBDISTRCOD_TEXT_MU.CSV

0DBDISTRCOD

SIC Text File

0DB87SIC1_TEXT.CSV

0DB87SIC1

SIC Hierarchy File

0DB87SIC1_HIER.CSV

0DB87SIC1

All the InfoPackages have got the same pattern as described in following table. Create the InfoPackages with this information.

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:usrsapQB5D19work/0DBLGLSTAT_TEXT.CSV for InfoPackage 0DBLGLSTAT_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



1

Processing




Update data

PSA and then in the InfoObject

Update parameters




Update mode

Full update




InfoPackages for Repeated Upload

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:


  • D&B Marketing Universe Matched Client File (0DB_IMPORTFILE_MU.csv)

  • D-U-N-S Text File (0DBDUNS_NUM_TEXT_MU.csv)

  • D&B Universe of Abstract Data (0DBDUNS_NUM_ABSTRACT_MU.csv)

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:usrsapQB5D19work/0DBDUNS_NUM_ABSTRACT_MU.CSV for InfoPackage 0DBDUNS_NUM_ATTR

D:usrsapQB5D19work/0DBDUNS_NUM_CONT_MU.csv for InfoPackage 0DBDUNS_NUM3_ATTR


Home  


 



Link to us




RSS Feed of new blogs                                                   Home        Feed Map        Submit Feed      Link to Us       Contact