What to check
A running ODQ daemon does not establish that a particular consumer is receiving the events it needs. Verify that new data is available for the intended source and subscriber, then trace the streaming chain configuration. A successful manual load is useful evidence but does not validate the automatic trigger path.
Troubleshooting steps
- Record the source, ODP context, subscriber, DTP, and streaming chain. Confirm the new data's availability for that exact consumer.
- Review the chain's scheduling and streaming settings, recent run logs, and the source-side notification or queue activity.
- Have the extraction and BW owners test the documented trigger workflow for the installed release and adapter, correcting the proven configuration mismatch.
Confirm the result
Validate automatic processing with a controlled new source change. Preserve subscription continuity and avoid deleting or reinitializing the delta relationship merely because the daemon appears healthy.
References
The SAP KBA link provides a public symptom preview; its full resolution requires SAP Support access. These diagnostic steps are independent guidance. Check the installed release before applying a correction.