Please enable JavaScript.
Coggle requires JavaScript to display documents.
General performance problems - Coggle Diagram
General performance problems
Job itself takes a long time
Please focus on the datasource itself, component should be BW-BCT-XX (search note/incident using the name of the datasource).
For the traditional SAPI, the job name is BIREQU_*
For the ODP/ODQ framework (job name can be found in TCode.ODQMON): BIREQU
* for Infopackage, ODQR
* for DTP.
Check if there's use-exit in the job log, such as exit_saplrsap_001 / exit_saplrsap_002 / exit_saplrsap_004. If the user-exit takes a long time, then consulting issue.
No user-exit, search note / incident by : datasource name + performance
No note is helpful, please record a ST12 performance trace:
If TCode.RSA3 can reproduce the performance issue, then record trace for RSA3 using 'Current mode' (see this demo)
If RSA3 cannot, but only the extraction from ERP to BW can reproduce the issue, please record the trace (2469206 - How to collect a trace analysis for delta extraction in the source system) during the extraction -> Aanalyze -> may ask help from DB team.
The data transferring takes a long time
Traditional SAPI
Job finished quickly, however IDOC transformation is very slow, component might be BC-BW. Please check by the steps
Central Note : 597364-FAQ: BW-BCT: Extraction performance in source system. Mainly check: TCode.SMQS -> Max.conn
TCode.SMQS, is there a NONE destination?:
Note 1250813-SAPLARFC uses all dialog work processes ( suggest note 1403974, suggest register NONE in transaction SMQS)
Note 1403974-Determining the maximum connections in transaction SMQS(BC-MID-RFC, how to create NONE )
Reason: The data packages will use RFC Destination with type 3 but the INFO IDocs will use the RFC Destination NONE via TCode.SMQS to transfer the IDocs to BW. Therefore we'd recommend customers to create it.
Both two steps above don't work, please record the ST12 trace in the source system during the extraction.
ODP scenario
2300483-ODQ - performance of ODQDATA_V and ODQTSNLOG
2520897-ODP package size and data load performance
vhgsdfg