3785029 - Note Analyzer: when and why for ABAP integration - SAP Datasphere

• SAP Datasphere Data Flows or Replication Flows use an On-Premise ABAP source system.
• SAP Support requests the output of transaction CNV_NA_DI (Note Analyzer).
• Clarification is required on whether Note Analyzer must be run for every support case and whether all listed SAP Notes must be implemented.
• Implementing the listed corrections may require prerequisites, manual activities, testing, and transports through development, quality, and production systems.

• SAP Datasphere
• ABAP-based Data Flow or Replication Flow integration

• Corrections for the on-premise ABAP integration runtime are delivered through SAP Notes in the connected ABAP system. SAP Datasphere cloud updates do not update this source-side ABAP code.
• Note Analyzer evaluates the correction level for the selected integration scenario and system version. Systems that have not applied the listed corrections may carry known bugs in the ABAP integration runtime.

1. Is a new Note implementation cycle required for every support case?

Implementing all corrections listed by Note Analyzer is the recommended baseline — missing corrections are a known cause of runtime, data transfer, and subscription issues, and historical cases show a significant share of problems trace back to an incomplete correction level.

• Recommended: Implement all corrections listed by Note Analyzer.
• Required: Ensure the TCI Notes are applied. Without them, basic integration functionality may be affected.
• If applying the remaining Notes is not currently possible: Let SAP Support know in advance. Support can investigate configuration, job, or other component-specific issues in the meantime, but the investigation scope will be limited. Note implementation may still be required later to fully resolve the issue.

2. Why is Note implementation requested before further investigation?

Systems missing these corrections remain exposed to known issues that have already been resolved in the ABAP integration runtime. Applying the missing corrections removes known issues from the investigation and provides a consistent system state for further analysis.

If the available evidence already identifies a configuration, authorization, connection, scheduling, or other specific cause, SAP Support will investigate that cause directly. However, Note Analyzer may still be used as a preventive correction-level check.

3. Why are Notes required when the system worked fine before or in development?

SAP Notes fix specific known issues in the ABAP integration runtime. A system without these corrections is not in a fully supported state, but issues may not surface immediately — many bugs are triggered only under specific conditions such as higher data volumes, particular object types, concurrent operations, or certain system configurations.

Development and production environments typically differ in data volume, configuration, and load. A scenario that runs without issue in development may expose a known bug in production or quality. Certain conditions — such as a system upgrade, increased data volume, or a new integration scenario — can trigger issues that were not visible before.

4. How can the implementation effort be managed?

1. Run Note Analyzer periodically instead of waiting for a production incident.
2. Evaluate the listed corrections, prerequisites, and manual activities in the development system.
3. Plan testing and transports through the normal development, quality, and production process.
4. Keep the latest Note Analyzer output and implementation record available for future support cases. Run the check again after an upgrade, refresh, or system copy. 

The number of listed corrections depends on the ABAP system version and its current correction level. Systems on a higher or more current software level may require fewer individual SAP Notes.

5. Do Replication Flows need to be restarted after Note implementation?

A Note Analyzer run or SAP Note implementation does not by itself require every Replication Flow to be deleted and recreated.

1. Read the implementation instructions and manual activities of each applied SAP Note.
2. If the SAP Note does not require any source-side objects to be rebuilt, resume the affected Replication Flow directly.
3. Restart the affected Replication Flow if the SAP Note requires the re-subscription of the runtime artifacts, after Note implementation.
4. Delete and recreate the Replication Flow only if the SAP Note instructions or SAP Support explicitly require it.

6. How to check if a Correction Note has side effect or not?

SNOTE notifies users of related side effect Notes and requires confirmation before implementation, but the side effect Notes must be reviewed and implemented separately if relevant. See 692466 - Note Assistant: Notes with side effects

Also, open SAP Note in SAP for Me, if there is any side effect, there will be a "Side Effects" tab. Click to get more detail information.

• KBA 3643099 - How to check Note Analyzer in on-premise ABAP-based systems for SAP Datasphere Data Flows and Replication Flows
• SAP Note 2890171 - SAP Datasphere / SAP Data Intelligence - ABAP Integration
• SAP Note 3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based migration and replication technology
• KBA 3651722 - Error "Note 0002890171; no entry for software component" when using transaction CNV_NA_DI

CNV_NA_DI, Note Analyzer, missing SAP Notes, implement all notes, mandatory corrections, ABAP integration, Replication Flow, Data Flow, SAP Datasphere, DWC, SAP Data Warehouse Cloud, S/4HANA on-premise, ECC, prerequisite notes, manual activity, system refresh, system copy, system upgrade, transport, restart Replication Flow, recreate Replication Flow, re-subscription , KBA , DS-DI-ABA , Datasphere - Data Flow / Replication Flow ABAP Integration , DS-DI-RF , Replication Flow Runtime , Problem