Business Warehouse Performance Tuning at Source System

[Former Member]

BW Performance At source

1) Maintain the control parameter for data transfer in SBIW -> General settings -> Maintain control parameters for data transfer.

Source system table ROIDOCPRMS: It contains the control parameters for data transfer from the source system to BW.

STATFRQU - Number of packets that are transferred before statistical info is sent

MAXPROCS - Maximum number of dialog work processes per upload request used to send the data to the BW system

MAXLINES - Maximum number of records sent in one IDoc packet.

MAXSIZE - Maximum size of an IDoc packet in KB.

Important Points to be considered.

A) Package size = MAXSIZE * 1000 / size of the transfer structure 

Package Size -  Not more than MAXLINES.

Transfer Structure size is determine by using SE11 (ABAP Dictionary) -> Extras -> Table Width -> Length of data division under ABAP.

B) If table ROIDOCPRMS is empty, the systems use default values during run-time. You should not allow these default values to be used.

SAP Note 1597364 - FAQ: BW-BCT: Extraction performance in source system

SAP Note 417307 Extractor package size: Collective note for applications

2) Values for Max Conn and Max Runtime in SMQS (Configure number of IDoc to be processed parallel depending on number dialog  process available in BW)

Cause

tRFC processing is very slow and has "Transaction recorded" status in SM58 or IDOC processing delay or Workflow processing delay

Resolution

1. Call transaction SMQS
2. Choose the destination
3. Click Registration
4. Increase the Max.Conn (Enter the number  of connection ) , this is directly proportion the available dialog process  in BW system. Example if BW has 30 Dialog process then you can try Max.Conn as 20. 
5. Increase Max. Runtime(For example 1800)

Sap Notes

1887368 - tRFC process slow in SM58 and Max.Conn is not fully used in SMQS

3) IDoc processing and Performance

The "Trigger Immediately" \ "Transfer IDoc Immed." options should be always used.

How to change the processing mode for the IDocs in question as follows:

For inbound:
-> go to transaction WE20 -> Select Partner Select Inbound Message Type and change the processing method to "Trigger Immediately" .

For Outbound:
-> go to transaction WE20 -> Select Partner Select Outbound Message Type and change the processing method to "Transfer IDoc Immedi."

What will happen IDocs are scheduled , reports RBDAPP01 \ RSEOUT00 in batch mode will be processed via scheduled runs. This should then leave the majority of dialog work processes free for users and mission-critical processes. Hence you will no longer encounter the resources problems you are currently experiencing.

4. Performance problem in collective job RMBWV3nn

Try to maintain the control parameters for the extraction for MCEX(xx) queue by the method below.
Transaction Code LBWR > Queue name (MCEX Queue) > Customizing > No.Of.Documents = 1000 to 3000.Check if this is reflected in Table TMCEXUPD-UPD_HEAD_COUNT field.

The adjustment of  TMCEXUPD- UPD_HEAD_COUNT will need to be tested for each application, as setting too large a value can result in a memory dump.

Part 2 - Performance Improvements in BW System