SAP Knowledge Base Article

1964223 - No Idocs Arrived from the Source System

Component: BC-BW (Basis Components > BW Service API), Version: 19, Released On: 09.01.2024

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.

Environment
BW system as the target system
Release independent

Reproducing the Issue

Run InfoPackage in the BW system to load data from an SAP source system.

Cause
It is usually caused by the following reasons:
Reason (1)
The Remote-User has no sufficient authorization. It may also lead to the dump below in the source system during the data
extraction:

Category ABAP Programming Error

Runtime Errors DYNPRO_SEND_IN_BACKGROUND
ABAP Program RSARFCRD
Application Component BC-MID-RFC

Client................. 001
User.................. ALEREMOTE <-- Remote user

Reason (2)
The OLTP system could not find its corresponding BW system due to incorrect/incomplete RFC settings
Reason (3)
There are no enough work processes or resource to handle the load
Reason (4)
For issue "IDoc ready for dispatch (IDoc status 30)" in the Infopackage monitor, it is because the IDoc in ECC system hangs
at status 30.
 Resolution
Check the followings one by one:
Solution (1）
Run transaction SU01 to check and make sure the Remote-User has enough authorization according to SAP Note 150315
Solution (2)
In the source system, check the Partner Profiles and IDoc settings with the following steps:
1. Start transaction WE20
2. Expand node 'Partner Type LS'
3. Find the target BW system (e.g. POTCLNT001)
4. Double click Message Type 'RSINFO'

5. Make sure the Output Mode is set to "Transfer IDoc Immed" for message type RSINFO:

6. Double click on the 'Receiver port' (eg. Port A000000054)

7. Check whether the 'RFC destinatination' is correct: it should be the correct target BW system
 8. Double click Message Type 'RSSEND' and perform silimar check for this message type as 2.5~2.8
9. Double click Inbound parameter, Message Type "RSRQST" and check it according to Note 2689728.
Solution (3)
You see entries in status "Transaction Recorded" in SM58. Check the Scheduler Status of qRFC using transaction SMQS. If it's
RES_LACK, follow the instructions from SAP Note 1970757. Otherwise, please see SAP Note 2556150.
In case further questions about this step, please raise case under BC-MID-RFC component.
Solution (4)
For error "IDoc ready for dispatch" (IDoc status 30). Check below SAP Notes:
1575852 - Outbound IDocs remain in status 30
1862248 - Delays sending outbound Idocs (status 30) which have been configured to transfer immediately

See Also
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 43024 - COM: ALE and EDI remote user authorisations
SAP Note 2689728 - InfoPackage extraction fails with: "Request IDoc : sent, not arrived ; Data passed to port OK"

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

Attributes
Key Value

Other SAP Business Warehouse > Data Warehouse Management > Data Staging > Source Systems (BW-WHM-DST-
Components SRC)

Other Basis Components > Middleware > Integration Technology ALE (BC-MID-ALE)
Components

Products
Products

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

This document refers to

SAP Note/KBA Component Title

2689728 BC-BW InfoPackage extraction fails with: "Request IDoc : sent, not arrived ; Data passed to port OK"

1970757 BC-MID-RFC Outbound/Inbound qRFC scheduler with status RES_LACK

1548446

This document is referenced by

SAP Note/KBA Component Title

2556150 "Transaction Recorded" status in transaction SM58