Ketul,
Buffer range:
The number range buffer is used to increase performance when assigning numbers. Instead of fetching the numbers each time from the database, a single access to the buffer suffices. Only when the buffer is empty, is it refilled from the database (table NRIV).
Use of the buffer has the following benefits:
· Accessing the main memory is a thousand times quicker than accessing the database. Speed is particularly important for applications that assign numbers frequently.
· Database accesses are always subject to the database transaction mechanism. Once an application has assigned a number for one user, a second user cannot assign a number until the first user has executed a commit operation on the database. The application blocks further assignment, and the second user has to wait, until the commit has been executed.
· The number range buffer can also prevent deadlock situations, which may arise from assigning different numbers in a different order.
Check :
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/6eb2aa7aed44ea92ebb969e03081fb/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/6eb2aa7aed44ea92ebb969e03081fb/frameset.htm
RSCUSTV6:
Frequency with which status Idocs are sent
With this frequency you determine according to how many data-IDocs an Info-IDoc is to be sent, or how many data-IDocs are described by one Info-IDoc.
Dependencies
Info-IDocs contain, among other things, information on whether the respective data IDocs have been uploaded correctly.
Using each Info IDoc, you can see in the monitor whether the load process is running free of errors. If this is the case for all data IDocs described in an Info IDoc, then the traffic light in the monitor is green.
Standard settings
Frequency 1 means, for example, that there is an Info IDoc for every data IDoc. In general, you should choose a frequency between 5 and 10 but not greater than 20.
Recommendation
The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data
Number of Data Records per Package
This option refers to the number of data records that are delivered with every upload from a flat file within a packet. The basic setting should be between 5000 and 20000 depending on how many data records you want to load.
Activities
If you want to upload a large quantity of transaction data, change the 'number of data records per packet' from the default value of 1000 to between 10000 (Informix) and 50000 (Oracle, MS SQL Server).
Dependencies
The data packets can be imported in parallel in BW in the background. With an improved use of system resources (uploading is divided up into several work processes), uploading in parallel is the most cost-effective from a performance point of view.
Recommendation
You should not divide up the quantity of data into too large a number of packets since this reduces performance when uploading. The number of data packets should not be more than 100 per loading process.
Size of PSA partition
You can determine here after how many records you want to create a new partition. By default, this value is set to 1,000,000 records.
Hope this helps.
-Doodle
Message was edited by: Doodle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.