Symptom
There are performance or configuration issues in an InfoPackage Request extracting from ECC to BW. Possible symptoms include, but are not limited to:
- Extraction job is not triggered in ECC when executing InfoPackage in BW;
- Request hanging in Yellow in InfoPackage Monitor (for any reason);
- Entries pilling up/hanging in qRFC Queue (Transaction SM58);
- A lot of Work Processes are used in BW side to process a Request;
- InfoIdocs are not passed from ECC to BW;
In this KBA it is specified an analysis path to cover all possible issues that might affect a data load via SAP Service API to a BW system.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
SAP NetWeaver - All Versions
Product
Keywords
InfoPackage, Performance, Extraction Job, Delta, Full, Partner Profile, WE20, Data Package Size, Work Process, SAPLSENA_GENERAL, S-API, Troubleshoot, Errors while sending packages from OLTP to BW Message no. RSM2011, RSAR_TRFC_DATA_RECEIVED, transaction recorded , KBA , BC-BW , BW Service API , BW-WHM-DST , Data Staging , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview