cesar-sap/abap_kafka_rest_proxy

• § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
• § 3 Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
• § FAQ 12 Outbound interfaces. The accompanying FAQ distinguishes external consumption of SAP-provided services from outbound notifications or callbacks sent by an SAP system, which it places outside this policy's scope.
• § FAQ 27 Custom-developed APIs. Customer-namespace ABAP interfaces are not prohibited merely because they are custom, but their underlying SAP dependencies and usage pattern still determine whether the use aligns with the policy.
• § FAQ 38 Large-scale data access. Large-scale extraction and replication must use access mechanisms and patterns documented for that purpose rather than treating a transactional or custom API as a general bulk-data surface.

The connector runs as customer ABAP code and normally calls outward to Kafka, which does not by itself put that traffic in scope. Reassess the concrete use when it fronts SAP APIs or moves data systematically at scale: custom code does not turn a transactional interface into an unrestricted extraction path.

Also, from Event Mesh§ 2.2.2, 3, FAQ 12, FAQ 27, FAQ 38: Direction and usage pattern decide the policy relevance. Customer ABAP code may publish events outward, but it must not be used to bypass SAP API controls or substitute a custom event stream for a documented bulk-data pathway.