NewABAP, RAP and ABAP Cloud
In the last 90 days
109 changes
Today
Document outputcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the service is a provider on this door and the text named it without the link. Wording otherwise unchanged; the state stays core-only.Document output
Event Meshcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note made a claim about every provider and named none, and the SAP services that arrived since the block was assessed (Advanced Event Mesh, the Integration Suite event broker, Cloud Application Event Hub) shape the answer. The state stays core-only, since every provider counting for the door is sap-official.Event Mesh
Notificationscore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed every provider is independent, a statement about who has built something; it now names the kinds, including the process framework that mails about failed objects.Notifications
RFC connectivitycore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): erpl-node-rfc, pyrfc-mcp, rfc-connector and Cloud Connector reached this door after the block was written and change its shape from callee only to callee and caller.RFC connectivity
Mon 19
Edge Integration Cell - what's new?publishedA Devtoberfest 2026 integration-track session (INT-41) on Edge Integration Cell, the runtime of SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp a customer runs on their own Kubernetes cluster while design, configuration and monitoring stay in the cloud tenant. It names what the customer has to provide — a supported Kubernetes platform, SAP HANA or PostgreSQL, Redis or Valkey as data store, a load balancer — then the Edge Lifecycle Management cockpit with its monthly rolling updates, the inbuilt and the external Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp options and why a DMZ placement calls for the second, and the adapters available only on Edge: RFC sender, NFS, OFTP2 and UNF. The demo deploys an OFTP-to-file flow to the Edge runtime and shows the same flow rejected when its runtime profile is switched to cloud, which is where the Integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only edge holds.RFC connectivity
How to Build Application Jobs in SAP Business AI Platform, ABAP environmentpublishedA Devtoberfest 2026 session on the application job framework in the cloud ABAP environment, built from the repository objects outwards: a class implementing the new application job interface, whose public attributes become the parameters and select options, the application log object it writes to, a job catalog entry that lays out sections, groups and value helps, and a job catalog template that works like a report variant. The demo schedules and monitors runs in the Application Jobs Fiori app, starts a job from a RAP action through the scheduling API under a job user of its own, and debugs one through the template's run-for-testing entry. It closes on the alternatives for work that should not be a job — the background processing framework for short-running work, and RAP events consumed locally or sent over the event mesh — which is the async processing this session covers for SAP BTP ABAP environmentSAP BTP ABAP environmentSAP's ABAP runtime on BTP: ABAP systems developed in the ABAP Cloud model on SAP HANA Cloud, for cloud apps, OData services and side-by-side extensions of SAP S/4HANA.sap official, btp.Async processing
S/4HANA Custom Development - What happens in case of errors in BAPIs or RAP BOs?publishedA Devtoberfest 2026 session on what a custom S/4HANA process does when a BAPI or a RAP business object fails. It is framed from project work rather than product development, with the same issues and challenges turning up on project after project, and it offers the ABAP Processing Center, ABAP-PRCABAP-PRCA framework for custom multi-step ABAP processes: a process class declares the states, and the framework runs each document through them and monitors the run.independent, abap, as what fills the gap it names in modern ABAP development. The edges rest on the opening, which states the session's subject as errors in S/4HANA custom development, read as error handlingError handlingTurning a failure into a response a client can act on — protocol-correct error payloads, correlation, and a boundary between internal detail and what a caller sees.SAP and community, unassessed on the ABAP door, and names that framework.Async processing
Sat 17
Cloud-Native with ABAP Cloud – The Transactional Outbox PatternpublishedImplements the transactional outbox pattern in ABAP Cloud's background processing framework (bgPF): a RAP business object's save sequence registers a bgPF handler implementing IF_BGMC_OP_SINGLE, and the RAP runtime runs it, and only then emits the message, after the database commit succeeds, so a rolled-back transaction emits nothing. The post walks through the full working example published as SAP-samples/abap-platform-rap-transactional-outbox-with-bgpfSAP-samples/abap-platform-rap-transactional-outbox-with-bgpfA reference example of the transactional outbox pattern in ABAP Cloud, using the background processing framework (bgPF) to decouple a database change from the follow-up action it triggers.sap official, abap.Async processing
erpl-node-rfcadded to the atlasRFC client for Node.js and TypeScript without the NW RFC SDKRFC connectivity
rfc-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over RFCRFC connectivity
[Blog Post] SAP Event Mesh - Consuming S4 events simultaneously in CAP-based applications and SAP Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Event Mesh
Show 19 more
ABAP code to wait for the end of "inbound bgRFC type Q" unitsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Async processing
Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
AWS Mail configuration for SAP ABAP Systemsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Notifications
Configure Journal Entry Posting Approval from Store Template in Build Process Automationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
Configuring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integrationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
Consume ABAP RFC Function Modules in CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Consume Remote Services in a Full-Stack CAP Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Custom Form with Custom Data Source in SAP Public Cloud (Grow with SAP)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Document output
Event Meshdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Event Mesh
How to use SAP Data Intelligence with SAP Cloud Connectorexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Integrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Event Mesh
Merge multiple PDF forms into a single document for download or printing.explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Document output
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Destinations
Print Preview from RAP Action with v4 OData and Multiple Selectionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Document output
Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud Servicesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Using RFC Function Modules and BAPIs in SAP Build Process Automationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).RFC connectivity
Thu 15
On‑the‑Fly Excel Download in a RAP Fiori App — No Database Table, No Persistence, Pure CDS + ABAPpublishedBuilds a CDS custom entity backed by an ABAP class that implements IF_RAP_QUERY_PROVIDER and assembles an XLSX workbook at request time — hand-built from Open XML parts with cl_abap_zip for multiple sheets, or in one line via cl_salv_table=>to_xml for one — then streams it to the browser through the @Semantics.largeObject annotation. The same annotation makes Fiori annotationsFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed render the field as a download link with no backing database table, trading the usual persisted-blob approach to document outputDocument outputProducing a document a person receives — a printed form, a generated PDF, a filled template — and getting it to a printer or a queue rather than returning it as a payload.SAP and community, narrow by design for a file rebuilt fresh on every click.Document output
open-abap-pdfadded to the atlasStandalone PDF generator written in ABAPDocument output
Cloud Connectorprovides[capability:authentication] revisedThe edge read as though the connector propagated the user by itself. SAP's own page names three authentication types towards an internal system and says the calling application's destination configuration picks one, and that trust to the cloud entities whose tokens are accepted has to be configured explicitly. The property the BTP door compares on rests on the same sentence.RFC connectivity
Tue 13
How to use SAP Data Intelligence with SAP Cloud ConnectorpublishedWalks through reaching an on-premise network from SAP Data Intelligence Cloud with Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp: installing the client, assigning the Cloud_Connector_Administrator role, registering the subaccount, and mapping on-premise systems as ABAP, HANA or HTTP back-ends in Data Intelligence's Connection Manager. For an ABAP back-end it names the function-module whitelist and the gateway port format RFC access needs, per SAP Note 2835207.RFC connectivity
Sun 11
Rethinking security for modern SAP solution landscapespublishedWhere risk goes when clean core moves custom logic out of SAP S/4HANA: into integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only, CAP extensions, ABAP Cloud code and platform configuration, told through real attack stories, then scanning code, modelling attack paths, adding security gates to CI/CD pipelinesCI/CD pipelinesA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. Deployment describes getting the build onto its target runtime.SAP only and automating safely with TerraformTerraformAn infrastructure as code tool that defines cloud and on-premise resources in configuration files and creates or changes them through provider plugins. SAP publishes a plugin for BTP, so Terraform is the CLI a reader installs to run a BTP account's configuration.. The scanning edge is to static analysisStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.SAP and community, narrow by design, the atlas's concern for security findings in ABAP code; the abstract lists the four surfaces and the four practices and describes none of them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Tsovinar Chugaszyan, written here from SAP's abstract; the recording is not yet published.Integration flows
SAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhookspublishedA step-by-step walkthrough of wiring Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp to publish and consume events between an on-premise S/4HANA system and Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp, contrasting persistent queues (one subscriber, kept until consumed) against unpersisted topics, and WebSocketWebSocketPushing to a browser that already has the page open, rather than making it ask again — the half of a UI that polling imitates badly.Community only's AMQP transport against webhook delivery for the same queue. Two tested findings support it: a queue consumer running in continuous consumption mode receives a message ahead of a webhook on the same topic, and a message stays queued and is retried (almost 8770 times in under a minute, in the author's test) until the consumer processes it successfully.Event Mesh
WebSocket RFC to Cloud Using SAP Business ConnectorpublishedWalks through wiring RFC connectivity between an on-premise ABAP system and a cloud ABAP system (SAP S/4HANA Cloud or Steampunk) through SAP Business Connector, which tunnels classic RFC over a WebSocket/HTTPS connection past firewalls. Covers the RFC destination of type T on the source system, the Communication User, Communication Scenario and Communication Arrangement needed on the cloud side to allow-list the function modules being called, and the three configuration steps on the Business Connector itself, closing with a list of common connection errors and their fixes.RFC connectivity
Sat 10
A Natural Choice: SAP AIF can now expose events to Advanced Event Mesh to power your EDApublishedAnnounces AIFAEM, a new software component of SAP Application Interface Framework that lets SAP ECC and older SAP S/4HANA backends create custom events from BOR objects and IDocs, in CloudEvents format, and publish them to SAP Integration Suite, advanced event meshSAP Integration Suite, advanced event meshAn event streaming, event management and monitoring platform for event-driven architecture, offered within SAP Integration Suite.sap official, btp — closing the gap for backends that predate S/4HANA's own RAP-based standard events. It ships as the ABAP add-on AIFAEM731 (SAP NetWeaver 7.31, i.e. ECC) or AIFAEM800 (NetWeaver 7.55 and later), and its usage is included in an advanced event mesh subscription.Event Mesh
Communicate from a Java Application to ABAP via WebSocket RFC using JCo - Migration GuidepublishedWalks a JCo setup from classic CPIC-based RFC to WebSocket RFC: swap the application- or message-server logon properties for jco.client.wshost and jco.client.wsport, and implement DestinationDataProvider's getSSLContext (and, for mTLS, getClientCertificate) since the new connection runs over TLS. It covers building the PKI trust on both sides — a local PKCS12 keystore for the Java side, STRUST's SSL-Server Standard certificate exported and imported for mutual trust on the ABAP side — and notes that on BTP, JCo paired with the Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp already implements this via the Connectivity serviceSAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp, so the custom SSLContext work can be skipped there.RFC connectivity
Recommendations for Customers on using the Direct Push-Based IntegrationpublishedExplains SAP's direct push-based integration, where two ABAP systems (SAP BTP ABAP environmentSAP BTP ABAP environmentSAP's ABAP runtime on BTP: ABAP systems developed in the ABAP Cloud model on SAP HANA Cloud, for cloud apps, OData services and side-by-side extensions of SAP S/4HANA.sap official, btp, SAP S/4HANA Cloud or SAP S/4HANA on-premise) exchange business events by calling each other over RFC connectivityRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.SAP and community, narrow by design, carried over CPI-C or WebSocketWebSocketPushing to a browser that already has the page open, rather than making it ask again — the half of a UI that polling imitates badly.Community only depending on the release, through a sender channel on one side and a matching receiver channel on the other that lists which events it wants. It recommends the mechanism only between systems in the same location or subaccount, without public exposure, and for prototyping event-driven scenarios before moving to Event MeshEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to async processing.SAP and community, narrow by design or SAP Integration Suite, Advanced Event Mesh at a larger scale.RFC connectivity
Fri 9
SAP: Email Functionality in SAP with a Custom Function ModulepublishedA custom ABAP function module, ZFM_SEND_EMAIL, sends mail through Business Communication Services' CL_BCS and CL_DOCUMENT_BCS classes, adding TO/CC/BCC recipients and multiple attachments by building the HTML document in application code on top of what CL_BCS delivers, which is how ABAP's notificationsNotificationsTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.SAP and community, narrow by design capability describes mail going out. The send sits in a TRY structure whose three CATCH blocks for CL_BCS's class-based exceptions are empty, so what reaches the caller is a BAPIRET2 table that BAPI_MESSAGE_GETDETAIL fills on the paths without an exception: no recipients given, sent to all, or not sent. That conversion into a caller-facing message table is what ABAP's error handlingError handlingTurning a failure into a response a client can act on — protocol-correct error payloads, correlation, and a boundary between internal detail and what a caller sees.SAP and community, unassessed capability leaves to the application.Notifications
Mon 5
ABAP-PRCadded to the atlasFramework for multi-step ABAP processes with monitoringAsync processing
Connecting SAP S/4HANA On-Prem Directly to Advanced Event Mesh using Cloud Connector - finally!publishedPackage Integration 1.4.0 for the Advanced Event Mesh Adapter adds official support for routing through SAP Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp, so an on-premise SAP S/4HANA system can produce events that SAP Advanced Event MeshSAP Integration Suite, advanced event meshAn event streaming, event management and monitoring platform for event-driven architecture, offered within SAP Integration Suite.sap official, btp distributes without exposing a public endpoint. The same release changes the adapter's default acknowledgment mode from Automatic Immediate to Automatic On Exchange Complete, altering delivery semantics and error handling. The release notes warn against mixing proxy configurations within one tenant, since that causes unpredictable routing in complex hybrid tenants.Event Mesh
ABAP-PRCentry revisedEntered by intake from the repository README, the repository description and the maintainer's landing page.Async processing
Async processingcoverage by flavor revisedABAP-PRC is the first option here to state ABAP Cloud: its README says the framework core is written in ABAP for Cloud Development on released APIs, and it runs its steps through the background processing framework or as application jobs. The paragraph on SAP's own mechanisms is unchanged and keeps its 2026-09-14 assessment date; no survey of the other providers was made. Its README lists SAP BTP ABAP Environment and S/4HANA Cloud Public Edition as coming soon, and its Fiori apps are classic BSP objects.Async processing
Sun 4
Merge multiple PDF forms into a single document for download or printing.publishedFaced with bundling several Adobe-Forms-generated PDFs into one file, where FP_JOB_OPEN could not handle the parameters a bundled FP_GET_PDF_TABLE output needed and the forms themselves could not be changed, the author merges the individual PDFs at runtime with the CL_RSPO_PDF_MERGE class instead. Walks through opening the spool job with FP_JOB_OPEN, generating each form via its FP_FUNCTION_MODULE_NAME-resolved function module, adding each result's xstring to the merger with add_document, then calling merge_documents and converting the result for GUI_DOWNLOAD or printing.Document output
Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud ServicespublishedA step-by-step walkthrough of installing Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp, adding a subaccount, managing identity and trust certificates in STRUST, and mapping cloud-to-on-premise paths for an SAP HANA backend. It ends by creating a DestinationsDestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.SAP and community, unassessed entry in SAP BTP with proxy type OnPremise and basic authentication, then testing it from SAP Business Application StudioSAP Business Application StudioSAP's development environment for business applications, delivered as a cloud service and opened in a browser, where work happens in preconfigured dev spaces.sap official, btp.RFC connectivity
Sat 3
ABAP code to wait for the end of "inbound bgRFC type Q" unitspublishedWalks through inbound bgRFC type Q — ABAP's queue-based flavor of async processingAsync processingDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.SAP and community, narrow by design built on background remote function calls — and gives a helper ABAP class that polls
cl_qrfc_client_inbound for each unit's and queue's state until every unit submitted across a set of parallel qRFC queues has finished. The method assumes no single unit spans more than one inbound queue, and the author flags the classes it relies on, cl_qrfc_client_inbound=>get_unit_state and get_queue_state, as unverified for this use.Async processingConfiguring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integrationpublishedWalks through creating the two BTP destinations an Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp iflow needs for an IBP-to-S/4HANA integration: one of type RFC with a WebSocket RFC server host and port for the IBP tenant, and one of type RFC with the on-premise proxy type, a Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp location ID and a virtual host for the S/4HANA system. It then has the reader copy SAP's prebuilt IBP integration packages into the Design workspace and deploy every reusable iflow in them before a business iflow can call the S/4HANA extractor through SAP Connectivity serviceSAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp.Destinations
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration SuitepublishedWalks a BAPI-based interface from SAP PO through three paths to SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp: lift-and-shift, which keeps the RFC connection to the ABAP system as-is and calls it through Integration Suite's RFC adapter; protocol modernization, which re-exposes the same BAPI as a SOAP web service; and clean core modernization, which replaces it with an SAP-managed API surfaced by the migration assessment report. Follows a BAPI_MATERIAL_AVAILABILITY interface through the first and third paths, showing the generated RFC-adapter iFlow against the OData API found for it.RFC connectivity
Fri 2
A method to create an Adobe form attachment for a work item using the class concept.publishedWalks through an ABAP workflow class, ZCL_WF_PDF, whose methods call an Adobe form through a Form-Builder-generated function module, convert the returned PDF between hexadecimal string and binary with SCMS_XSTRING_TO_BINARY and SCMS_BINARY_TO_XSTRING, and attach it to a work item via SAP_WAPI_ATTACHMENT_ADD and SAP_WAPI_WRITE_CONTAINER, with the class, background-task and SWDD workflow steps shown in full. It explains document outputDocument outputProducing a document a person receives — a printed form, a generated PDF, a filled template — and getting it to a printer or a queue rather than returning it as a payload.SAP and community, narrow by design's ABAP route, rendering a PDF through the Form Builder and getting it back into the program, and a route into attachmentsAttachmentsStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.SAP and community, unassessed's ABAP side distinct from Generic Object Services: a file attached to an SAP Business Workflow work item instead.Document output
Enhancing SAP Business Events with Custom Payload Fields using RAPpublishedWalks through enriching an outbound Business Partner event for Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp that by default carries only the partner ID: a derived RAP business event, raised from a behaviour definition with RAISE ENTITY EVENT and bound through SWE2 event linkage to a receiver function module, adds first and last name to the payload. The custom event is defined on a root view entity over BUT000 and verified in /IWXBE/EVENT_MONITOR, where the enriched JSON payload shows the extra fields reaching subscribers without an additional callback to the source system.Event Mesh
Pattern Function for RFCpublishedA custom ABAP Editor pattern, defined once under SE38 > Utilities > More Utilities > Edit Pattern as Z_RFC_FUNCTION, that generates a CALL FUNCTION ... DESTINATION block for a chosen remote-enabled function module: an EDITOR_EXIT function on the calling system reaches the target system over RFC to fetch that function's generated source, then inserts the DESTINATION clause before handing the pattern back to the editor. It automates writing the RFC call itself rather than explaining RFC destinations as a concept, and the destination name in the sample is hardcoded to the author's own system.RFC connectivity
Using Communication Targets for Outbound RFC Communication in ABAPpublishedWalks through calling a remote-enabled ABAP function module through a communication target instead of a direct RFC destination: on-premise, the APPLDEST transaction creates an application destination (client, CPIC type, host from SM51, authentication); in the cloud, saving a communication arrangement for an outbound-RFC communication scenario creates one automatically. ABAP code reaches the function with
CALL FUNCTION (...) IN REMOTE SESSION, naming the application_destination parameter when a communication target has more than one assigned destination, and the piece walks a worked call to RFC_SYSTEM_INFO.RFC connectivitySun 27
Async processingcore coverage revisedcapire audit 2026-09-27, proposed pages read a fourth time: the description draws the line between queued work and messaging, and the events index states that line in SAP's words.Async processing
Event Meshcore coverage revisedcapire audit 2026-09-27, proposed pages read a fourth time: the paragraph says messaging rests on intrinsic eventing, and the events index says the same in SAP's words.Event Mesh
Sat 26
AWS Mail configuration for SAP ABAP SystemspublishedWalks through routing an SAP ABAP system's outbound mail through Amazon SES instead of an on-premises mail server or a dedicated EC2 SMTP instance: verifying a sender address and generating SMTP credentials in SES, creating the SMTP node in transaction SCOT, importing the SES endpoint's certificate into the SSL client via STRUST, and testing delivery through SO01 and SOST. It covers the SMTP relay underneath ABAP's mail delivery, the layer NotificationsNotificationsTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.SAP and community, narrow by design marks as where the core stops and where a channel like this is written on top.Notifications
Configure Journal Entry Posting Approval from Store Template in Build Process AutomationpublishedWalks through deploying SAP's Journal Entry Posting Approval template from the SAP Build Process AutomationSAP Build Process AutomationSAP's low-code and no-code tool for business processes: graphical process models, drag-and-drop forms, decision tables and robotic process automation bots, with dashboards over running process instances.sap official, btp Store against an on-premise S/4HANA system that has no Secure Network Connection: destinations for S/4HANA via Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp, for SAP Document Management service, integration optionSAP Document Management service, integration optionA BTP service of APIs and a reusable UI5 component for adding document management, with folders, versions and status, to a business application over SAP's repository or a CMIS-compliant one.sap official, btp to hold the approval's supporting documents, and for the BPA service and its SMTP mail. It then swaps the template's SNC action groups for basic-connection BAPI calls and deploys the approval's UI5 applications so the task lands in My Inbox, with a Desktop Agent registered to run the unattended document-check and document-post automations.Destinations
Tue 22
Document outputcore coverage revisedThe boundary held, but the reader had nothing to check it against. The README's model requirement is the test: the document has to be a LargeBinary attribute before the plugin will print it.Document output
Sat 19
Cloud Connectorconnects revisedThe Connectivity service required the Cloud Connector, and nothing said which of the two opens the connection. SAP's documentation does: the connector registers with the service.RFC connectivity
Thu 17
Extract Rev-Trac requests by custom program and Rev-Trac APIpublishedA custom ABAP report that does a full-text search across custom long-text fields of Rev-Trac change requests — a search the change-management tool has no built-in feature for — by calling Rev-Trac's own RFC-enabled function modules from a separate connected ABAP system. It walks through the mechanics of RFC connectivityRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.SAP and community, narrow by design on the ABAP side: looking up the RFC destination at runtime from a system table via a remote-enabled function module, then calling further remote function modules with
CALL FUNCTION ... DESTINATION, including the read/update APIs' parameter-naming convention and their commit-on-connection-end behaviour.RFC connectivityHow to Merge Two Separate Smart Forms into a Single PDF in SAPpublishedWalks through generating two separate Smart Forms as OTF, converting each to PDF with CONVERT_OTF, then combining them into one file with cl_rspo_pdf_merge before downloading the result to the frontend. The whole flow runs inside the ABAP system that holds the data, from SMARTFORMS-built forms to a single merged PDF on the local device.Document output
Wed 16
Custom Form with Custom Data Source in SAP Public Cloud (Grow with SAP)publishedBuilds a custom Adobe-based output form for SAP S/4HANA Cloud Public Edition when SAP ships no standard data source: a RAP business object exposes header and item CDS views through a service definition, one view marked as the form's data provider, and the layout is designed offline in Adobe LiveCycle Designer against the exported XML schema before upload and rendering back in the tenant. It draws the line against SAP Forms Service by AdobeSAP Forms Service by AdobeAdobe Document Services on BTP: renders print and interactive PDF forms from stored templates, called over a REST API from a cloud application or connected to an ABAP system.sap official, btp on BTP, which the post sets aside in favour of building the form inside the S/4HANA Cloud system itself.Document output
Print Preview from RAP Action with v4 OData and Multiple SelectionpublishedA RAP action's implementation calls SAP Interactive Forms by Adobe through
cl_fp for each of several selected keys, merges the resulting PDFs into one file, and returns it as base64 from the action result. A Fiori elements list report invokes the action for the current selection through a controller extension's editFlow.invokeAction, grouped as a single ChangeSet so every selected document is generated and merged in one round trip before the merged file is offered back to the user.Document outputTue 15
Cloud Connectoradded to the atlasSAP's on-premises agent linking SAP BTP to customer-network systemsRFC connectivity
SAP Forms Service by Adobeadded to the atlasAdobe Document Services on BTP for print and interactive PDFsDocument output
Triggering Background Jobs from RAP Actions – A Practical GuidepublishedWalks through a RAP business object whose Saver Class calls a function module IN BACKGROUND TASK from the save phase, and that function module in turn uses JOB_OPEN, SUBMIT ... VIA JOB and JOB_CLOSE to schedule a classic background job that finishes the long-running work, so the triggering UI transaction stays lightweight. The mechanism shown — an asynchronous function-module call plus a submitted executable report — is Standard ABAP background processing rather than ABAP Cloud's released scheduling APIs.Async processing
Mon 14
abap_fm_jsonadded to the atlasJSON adapter exposing ABAP function modules over HTTPRFC connectivity
abap2xlsxadded to the atlasLibrary that reads and generates Excel spreadsheets from ABAPDocument output
ADELE RFC APIadded to the atlasRFC-callable ABAP API for SAP data extraction for ADELERFC connectivity
aditheos/ApplicationLogsNotificationToFioriadded to the atlasFiori launchpad notification for application log errorsNotifications
Show 20 more
agiguere/SCPmsPushNotificationREST_APIadded to the atlasABAP classes sending push notifications to Mobile ServicesNotifications
cesar-sap/abap_kafka_rest_proxyadded to the atlasABAP connector to Kafka through the Confluent Kafka REST ProxyEvent Mesh
Clean Core by Design: Event Enablement Cockpit as a Core Integration Enabler in SAP S/4HANApublishedWalks through wiring an on-premise SAP S/4HANA system into Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp as an event producer, using the Enterprise Event Enablement framework: creating the service instance and its service key, then an RFC destination and OAuth 2.0 client configuration in SPRO so a channel can publish native S/4 business events over AMQP or MQTT. Covers the channel's reconnect and quality-of-service parameters and activating the Event Discovery Service, and notes that SAP ECC needs a third-party add-on for the same events since S/4's native Business Events are not available there.Event Mesh
DryDumbHead/easyHtmlEmailadded to the atlasABAP helper class building HTML emails from templatesNotifications
gregorwolf/AWS_SNS4ABAPadded to the atlasICF handler receiving Amazon SNS notifications in an ABAP systemEvent Mesh
HandlebarsABAPadded to the atlasSingle-file Handlebars templating for ABAP 7.40 SP02 and upDocument output
INVIXO/abapMQadded to the atlasMQTT 3.1.1 client implemented in ABAPEvent Mesh
MQBAadded to the atlasMQTT publish/subscribe in ABAP with an external broker bridgeEvent Mesh
peterlangner/zrssadded to the atlasRSS feed publisher for content from an SAP NetWeaver ABAP systemNotifications
SAP Spool PDFadded to the atlasSubmits an ABAP report to the spool and converts the output to PDFDocument output
SAP-samples/forms-service-by-adobe-samplesadded to the atlasProjects integrating SAP Forms Service by Adobe with ABAP Environment
srijan9864/zrfcreadadded to the atlasAn RFC-enabled ABAP function module that counts the entries of any table against dynamic where and join criteria.RFC connectivity
XTTadded to the atlasABAP template engine for Excel, Word, HTML and PDFDocument output
zcl_docxadded to the atlasABAP class filling a tagged Word .docx template with dataDocument output
zcl_pdfadded to the atlasStandalone ABAP class drawing PDFs without Adobe Document ServerDocument output
Async processingcoverage by flavor revisedNo ABAP-door artifact carries a provides edge to this capability, so the reading rests on SAP's own documentation: ABAP Cloud runs deferred work through the released Background Processing Framework (bgPF), built on bgRFC and integrated with RAP's COMMIT WORK, and through the released application job framework, while bgRFC itself, CALL FUNCTION ... STARTING NEW TASK and SM36 batch jobs are Standard ABAP mechanisms that SAP-samples/abap-cheat-sheets places outside ABAP for Cloud Development.Async processing
Document outputecosystems revisedWidened to ABAP and BTP: abap2xlsx, AntonSikidin/zcl_docx, beraadim/zcl_pdf, bizhuka/xtt, victorizbitskiy/zspool_pdf and monstermichl/HandlebarsABAP produce spreadsheets, Word files, PDFs and filled templates from ABAP, and SAP-samples/forms-service-by-adobe-samples integrates SAP Forms Service by Adobe with the ABAP Environment.Document output
Event Meshecosystems revisedWidened to ABAP: cesar-sap/abap_kafka_rest_proxy produces to and consumes from Kafka, INVIXO/abapMQ and MDJoerg/MQBA speak MQTT, and gregorwolf/AWS_SNS4ABAP receives AWS SNS notifications in an ABAP system.Event Mesh
Notificationsecosystems revisedApplicationLogsNotificationToFiori, SCPmsPushNotificationREST_API, easyHtmlEmail and zrss send launchpad notifications, mobile push, HTML mail and RSS feeds from an ABAP system, so the concern has answers behind the ABAP door.Notifications
RFC connectivityecosystems, description revisedThe old wording put the caller in a CAP service, which is false behind the ABAP door, where the repositories answer the side being called. The caller is now anyone outside the system.RFC connectivity
Sun 13
Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'publishedWalks through the two pieces of connectivity a SAP Build Process Automation action needs to call an on-premise BAPI: mapping the virtual host to the internal S/4HANA host in Cloud Connector over the RFC protocol, and creating an RFC-type destination in the BTP cockpit so BAPI_BILLINGDOC_CREATEMULTIPLE becomes a selectable action. The resulting process creates an SD billing document from a sales document number and is reached through SAP Build Work Zone, including from the Joule Work mobile app.RFC connectivity
Using RFC Function Modules and BAPIs in SAP Build Process AutomationpublishedWalks through calling an S/4HANA BAPI (BAPI_BILLINGDOC_CREATEMULTIPLE, to create a billing document) from an SAP Build Process Automation action: mapping the virtual host to the internal system in SAP Cloud Connector over the RFC protocol and exposing the needed function modules, then creating an RFC-type destination in the BTP cockpit with the virtual message server and SMLG logon group. Once those two are in place, SAP Build lists the exposed BAPIs and RFCs for use in an action.RFC connectivity
Event Meshname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Event Mesh
Wed 9
Async processingecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Async processing
Event Meshecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Event Mesh
RFC connectivityecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.RFC connectivity
Tue 8
[Blog Post] SAP Event Mesh - Consuming S4 events simultaneously in CAP-based applications and SAP Integration SuitepublishedOne S/4HANA event, two consumers at once: a CAP Java application and SAP Integration Suite. Late in a long Deep Dive series and written as such — the queues, the S/4HANA connection and the Integration Suite side were all established in earlier posts, so this is the part where they meet.Event Mesh
Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe opening of a three-part series on reaching more than one S/4HANA system from one CAP application with the user's identity carried through. This part sets up the business problem; the propagation itself is in the parts that follow.Destinations
Consume ABAP RFC Function Modules in CAPpublishedCalling an existing RFC function module from CAP instead of asking somebody to build an OData service for it — which is the actual decision, since the alternative is custom development on the ABAP side for a function that already works.RFC connectivity
Consume Remote Services in a Full-Stack CAP ApplicationpublishedExtending the Developer's Guide application with a remote S/4HANA service — connectivity, importing the Business Partner API, and running against it. SAP publishes this as four separate paths: mock server or real S/4HANA Cloud, times Cloud Foundry or Kyma. One entry covers all four, because the difference between them is which backend and which runtime, not what you learn.Destinations
Show 3 more
Integrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPpublishedA concrete regulatory deadline rather than a demo topic: every Polish invoice has to pass through KSeF, the national e-invoice platform, and this proposes the route — S/4HANA business events onto Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp, a CAP application consuming them and talking to KSeF. Short, and offered as an example to argue with.Event Mesh
Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe final part, and the one with the most CAP in it — the service consuming the propagated destinations, and what the handler sees. Read the three together; the series is one piece.Destinations
Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe middle part: the destinations and the trust that make principal propagation work against several backends rather than one, which is where the configuration stops being a copy of the tutorial.Destinations
Mon 31
Async processingcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Async processing
Document outputcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Document output
Event Meshcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Event Mesh
Notificationscore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Notifications
Show 1 more
RFC connectivitycore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.RFC connectivity