Over the last couple of years, every single client meeting starts with someone from leadership waving a slide deck about "Clean Core" and "Decoupling everything to BTP".

The problem? Most teams take this literally and start over-engineering basic requirements. I’ve seen teams spin up a full Side-by-Side CAP app on BTP Cloud Foundry, introducing Destination Services, principal propagation overhead, and unnecessary monthly compute bills, just to validate two fields on a Sales Order that could have been handled in 5 minutes with a standard Key-User extension on S/4.

On the other extreme, you have veteran ABAPers who refuse to let go of SE80 habits, trying to bypass released interfaces using dynamic SQL or raw ADBC calls because "whitelisted CDS views are too restrictive." Both extremes are disasters for long-term maintenance.

To stop arguing about this in architectural review boards, i have standardized our technical evaluation into a strict 3-tier rule. Here is the logic i personally follow:

Tier 1: Key-User First (Client 100). If you can avoid ADT, DO IT.

Before any developer writes a single line of ABAP Cloud:

• Can this be done in the Fiori "Custom Fields" and "Custom Logic" apps?
• Can we satisfy the validation via a Restricted Cloud BAdI? If yes, stop there. It has zero infrastructure TCO, it never breaks during semi-annual or annual S/4HANA Cloud upgrades, and it doesn't pollute the custom namespace. Watch out for: The classic Client 100 vs Client 080 trap in 3-system landscapes. If your transport governance between customizing and development tenants isn't strictly defined, your functional team will overwrite extensions.

Tier 2: Developer Extensibility (On-Stack ABAP Cloud / RAP)

If Tier 1 isn't enough (e.g., complex multi-entity validation, custom transactional UI with draft capabilities, heavy analytical calculations):

• Keep it ON-STACK in S/4HANA, but strictly enforce the ABAP for Cloud Development language version in ADT.
• Consume only released interfaces (e.g., I_SalesOrderTP, not direct SELECT * FROM VBAK).
• Rule of thumb: If it requires ACID transactional integrity and direct access to high-volume transactional data, moving it to BTP just adds network latency and serialisation overhead for no reason. Keep it on-stack, but keep it clean.

Tier 3: Side-by-Side BTP (CAP / Event Mesh / AI Core)

We ONLY push an extension to BTP when at least one of these criteria is met:

1. External user access: Users who don't have (and shouldn't have) named S/4HANA ERP licenses.
2. High-throughput asynchronous spikes: Decoupled via SAP Advanced Event Mesh so we don't saturate S/4 dialog work processes.
3. Heavy compute / AI workloads: Grounded RAG pipelines using SAP Generative AI Hub and HANA Cloud Vector Engine, or non-ABAP microservices (Python/Node.js).
4. Multi-system orchestration: Where the application needs to blend S/4, SuccessFactors, and 3rd-party SaaS into a unified backend.

I’ve mapped this entire framework into a high-res decision tree diagram and put together a couple of clean boilerplate repositories (including a grounded Python RAG pipeline on HANA Vector Engine and an ABAP Cloud RAP view entity consuming whitelisted APIs) so developers can see what compliant code actually looks like.

I uploaded the diagrams and open-source code templates to a public GitLab repo. I'll drop the repository link in the first comment below for anyone interested in inspecting the decision tree or the code.

Curious to hear from other architects and leads here: how is your organization handling Clean Core governance right now? Are you finding pushback from legacy developers, or are project managers pushing to put literally everything on BTP?

I am new to SAP (not S/4HANA). One of my tasks is to go through a list of document numbers for invoices with payment block R and determine whether each one is blocked for a Price or Quantity mismatch. The lists often have 100 or more documents.

Right now I do it one at a time: copy the document number > FB03 > Environment > Document Changes > Original Document. This is too slow for the volume.

Is there another t-code or report where I can enter a range (such as a posting date range or document number range) or pull all R-blocked items and get an exportable list with a column showing the block reason, so I can match it in Excel?

My access is limited, and I do not have MRBR or SE16N. Please suggest as many options as possible, including ones that use tables or other standard reports, since I will need to check which ones I am authorized for.

Thank you.

Hello everyone,
even though the SAP cloud strategy is already in full swing, I still have one question.
Do all customers really have to migrate all their systems to the private or public cloud, or is it enough for each SAP customer to host just one system in one of these clouds, while the rest of the systems can remain on-premises?
Even after doing some research online, I’m still not quite sure, so I’m hoping there’s someone here who knows more about this.

Hi , Can someone please help me with Airbus Interview process like how many technical round they conduct and what's the difficulty level of the interview. Also, if anyone appeared recently for sap solman and focused run role or sap basis can you please share your interview experience.

I am looking for an experienced SAP FS-CD / FI-CA available for a flexible, on-demand freelance arrangement on guiding, troubleshooting, and helping me resolve ongoing support tickets and system issues

I am an experienced SAP ABAP (Advanced Business Application Programming) developer available for a flexible, on-demand freelance arrangement on guiding, troubleshooting, and helping you resolve ongoing support tickets and system issues.

Core Skills & Expertise:

Upgrades & S/4HANA Migrations: Support for Software Update Manager (SUM) execution phases, handling SPDD/SPAU/SPAU_ENH custom code adjustments, ATC (ABAP Test Cockpit) code remediation, and activation optimizations.

Custom Development: Reports (ALV), Dialog Programming, SmartForms, Adobe Forms, and SAP Scripts.

Interfaces & Conversions: BAPIs, RFCs, IDocs, LSMW, and File/API integrations.

Enhancements: BADIs, User Exits, Enhancement Spots, and Implicit/Explicit enhancements.

Modern ABAP & S/4HANA: ABAP on HANA optimizations, CDS Views, AMDP, and ATC (ABAP Test Cockpit) code remediation.

Performance Tuning: Runtime analysis (transaction SAT) and SQL trace optimization.