SAP Knowledge Base Article - Preview

1964223 - No Idocs Arrived from the Source System

Symptom

You create a full/delta/initial loading request for a DataSource from an OLTP system. The InfoPackage monitor displays some messages below:

  • No Idocs arrived from the source system.
  • No IDocs could be sent to BW using RFC.
  • Request IDoc : sent, not arrived ; IDoc ready for dispatch (ALE service)  (IDoc status 30)
  • Info IDoc 1 : sent, not arrived ; Data passed to port OK
  • Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
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

  • BW system as the target system
  • Release independent

Product

SAP BW/4HANA all versions ; SAP ERP Central Component all versions ; SAP ERP all versions ; SAP NetWeaver all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

system copy, data loading, request, infopackage, No Idocs arrived, IDoc, not arrived, Data passed, remote-user, RFC, authorization, sm37, we20, we21, receiver port, partner, message type, RSAP_IDOC_SHOW_TRFC, no selection information arrived from the source system, if no job was terminated in the OLTP, errors while sending packages from OLTP to BW, RSM2011 , KBA , BC-BW , BW Service API , BC-MID-ALE , Integration Technology ALE , BW-WHM-DST-SRC , Source Systems , Problem

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.