Show TOC

Maintaining Control Parameters for Data TransferLocate this document in the navigation structure

Procedure

Enter the required data in the following fields.

  1. Source system (source system)

    Enter the logical system for your source client and assign a control parameter to it.

    For information about source clients, see the source system under Tools → Administration → Management → Client Management → Client Maintenance.

  2. Maximum size of the data package (max KB)

    When transferring data into BW, the individual data records are sent in packages of variable size. You use this parameter to control the typical size of a data package of this type.

    If you do not make an entry, the data is transferred with the default setting of 10,000 kBytes per data package. However, the required memory depends on both the data package size setting and the width of the transfer structure, the required memory of the affected extractor, and, for large data packages, the number of data records in the package.

    We recommend setting this value to between 20,000 and 50,000.

    The size of the data packages can be calculated using the following formula:

    If the value for the maximum number of rows in a data package is smaller than the value for the maximum size of the data package, the value for the maximum number of rows limits the size of the data package. You can find information about how applications affect the size of the data package and examples of calculating the size of the data package according to the control parameters in SAP Notes 417307 and 409641.

  3. Maximum number of rows in a data package  (Max. Rows)

    For large data packages, the required memory mainly depends on the number of data records that are transferred with the package. You use this parameter to control the maximum number of data records that you want the data package to contain.

    In the default setting, the system transfers a maximum of 100,000 records per data package. We recommend setting this value to between 20,000 and 100,000, depending on the main memory size. This is approximately 2 X 'Max. Rows' X 1000 bytes per data package .

  4. Frequency (Frequency)

    The frequency you enter specifies the number of data IDocs that has to be reached before an info IDoc is sent, or how many data IDocs are described by an info IDoc.

    The default setting for the frequency is 1. This means that an info IDoc follows after each data IDoc. You should choose a frequency between 5 and 10, but no greater than 20.

    The larger the package size of a data IDoc, the lower you should set the frequency. As a result, you get information about the data load status during the data upload at relatively short intervals.

    In the BW extraction monitor, you can use each IDoc to determine whether the load process was successful. If this is the case for all data IDocs described in an info IDoc, the traffic light in the monitor is green. Info IDocs contain information about whether the data IDocs were correctly uploaded.

  5. Maximum number of parallel (dialog) processes for the data transfer (max percent.)

    Enter a value greater than 0. The default setting for the maximum number of parallel processes is 2. We recommend a setting between 1 and 4. The best choice to make here depends on the configuration of the application server that you are using for the data transfer.

    Note

    This control parameter for data transfer is used for requests that transfer data from a source system with a Service API release 7.0 (Plug-In-Basis 2005.1) or higher, or Plug-In 2004.1 SP10 for 4.6C source systems and that do not end in PSA. These are PSA requests for 3.x DataSources that also write to data targets (like requests for 3.x DataSources with InfoPackage processing option PSA and then to Data Target/InfoObject (by Package)) and requests in a data mart scenario (for example for posting a DataStore object to an InfoCube using an export DataSource).

    The control parameter for requests is also used to transfer the data from source systems with a Service API release lower than 7.0 (Plug-In Basis 2005.1) or Plug-In 2004.1 SP10 (for 4.6C source systems).

    Otherwise, the data transfer is controlled by the qRFC outbound queue.

    More information:Data Transfer with qRFC Outbound Queue

  6. Target system of a batch job (target system)

    Enter the name of the application server where you want to process the extraction background job.

    To find the name of the application server, choose Tools → Administration → Monitor → System Monitoring → Server. The Host column displays the name of the application server.

  7. Maximum number of data packages in a delta request (Max. DPs)

    You use this parameter to set the maximum number of data packages in a delta request or a rerun of a delta request (repair).

    Only use this parameter if you are expecting delta requests with a very large volume of data. In this case, allow more than 1000 data packages to be generated in a request, while retaining an appropriate data package size.

    As before, there are no limits for initials values or the value 0. The number of data packages is only limited if you have a value greater than 0. To ensure consistency, however, this number is not always strictly adhered to. Depending on the extent to which the data in the qRFC queue is compressed, the actual limit can deviate by up to 100 from the specified value.