Best Practices implementing SAP BI solution on high data volumetry environment

[former_member204732]

Dear Expert,

I am working for a big company having sap bi dataflow based on high data volumetry source system.

I would like to share with your experience what are the best practices to implement BI solution in this context.

1. Manage parallel loading process instead of sequential loading.

2. Eliminate not needed records.

3. Adjust system setting on DTP package size

4. Adjust system setting on DSO activation.

5. Improve ABAP performance.

Do you see any other useful point to take care / manage ?

Thanks,

[RamanKorrapati · Accepted solution]

Hi,

Please go thru below additional points which would help you.

1. Focus on housekeeping activities before getting memory/space issues during load time.

2. Check and increase required BGD jobs to speed up your loads as per parallel settings.

3. After completion of your master data loads, pls run/schedule transaction data loads.

4. if daily full loads there, please try to run them on weekend if client accepts

5. Check for DSO settings , Tx - RSODSO_SETTINGS to speed up data loading and DSO activation

6. Fine tune your abap routine by using ST03N.

7. Use partition or SPO.

Thanks

[Former Member]

Hi,

These points also will help.

Loading

  PSA and Change Logs. Delete in every Process chain the PSA and the Change log. (1 moth older for instance).

Create a special Process Chain to delete all PSA from ECC if they are 2 months old.

  If you have the possibility to load several times a day from ECC, do it.

Identify your DSO's.

  You can change the SID generation if your DSO's are not used for Reporting. (better perfomance, load and wirte).

  Avoid reporting from DSO for new models or use Flag (SID generation in reporting)

Identify your larger tables.

  If a Cube or DSO is too big, check this link about Partitioning.

     Why partitioning is important? Have you tried SPO in SAP BW 7.3?

Use Composite Provider

  This new object in BW helps you with some modeling that was not possible before. This helps you to avoid create several DSOs, cube, routines.

Modeling

  Use INFOSOURCE in the middle of complex modeling in order to avoid DSO to store and to load again with new calculations. I mean:

Instead of having:

      DSO - TRANSF (abap) - DSO - TRANSF (abap) - CUBE

You can do this:

      DSO - TRANSF (abap) - INFOSOURCE - TRANSF (abap) - CUBE

Best Regards.