SAP-GCP Block Traceability Architecture
About This Architecture
Enterprise SAP ECC 6.0 block traceability system streaming customer blocking events (AUFSD/FAKSD/LIFSD) to Google Cloud Platform via SAP BTP Cloud Integration Suite. On-premise BAdI triggers capture 25 fields through ABAP Proxy, traverse SAP Cloud Connector secure tunnel (TLS 1.2+, no inbound ports), transform XML to JSON in CPI iFlow, and publish to Cloud Pub/Sub topic with dead-letter handling after 5 retries. Cloud Run service validates JSON payloads with CHANGENR-based idempotency, streams to BigQuery partitioned table (25 columns), while Cloud Storage handles historical CSV batch loads (50K records) via Cloud Function triggers. Apigee X exposes OAuth2-secured REST API (30 req/s spike arrest) for Salesforce CRM and future consumers, with Terraform modules automating entity_pipeline provisioning (topic, subscription, BigQuery table) and Cloud Monitoring SLOs tracking end-to-end latency. Fork this SAP-GCP integration reference architecture on Diagrams.so to customize field mappings, adjust Pub/Sub retry policies, or add your own downstream consumers.
People also ask
How do I stream SAP blocking events to BigQuery in real-time using Google Cloud Platform?
Use SAP BTP Cloud Integration Suite to transform ABAP Proxy SOAP messages to JSON, publish to Cloud Pub/Sub, process via Cloud Run with idempotency checks, and load into BigQuery partitioned tables. This SAP-GCP architecture diagram shows the complete flow including Cloud Connector secure tunnel, dead-letter handling, and Apigee X API exposure.
- Domain:
- Cloud Gcp
- Audience:
- SAP integration architects building real-time event pipelines on Google Cloud Platform
Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.