BTP & Integrationintermediate

BTP SAP Build Part 2: Low-Code or Pro-Code?

Key takeaway

Decide between SAP Build Apps (low-code) and SAP Build Code/CAP (pro-code): criteria like complexity, transactional integrity, performance, reuse, team skills, testing and lifecycle — and hybrid patterns where a low-code UI calls a pro-code CAP service.

Explanation

📌 KEY POINTS
✅ Low-code suits simple UIs, forms and data capture with limited logic.
✅ Pro-code (CAP) suits complex business rules, transactions, integrations and reusable services.
✅ Hybrid: low-code front end calling a pro-code service keeps logic in one governed place.
✅ Consider testing, versioning, performance and who will maintain the app.
⚠️ Stretching low-code tools to implement complex transactional logic creates fragile apps.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced the family. Now the choice.

━━━━━━━━━━━━━━━━━━━━
▶ 1. LOW-CODE STRENGTHS

Speed, business ownership.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PRO-CODE STRENGTHS

Complexity, testing, reuse.

━━━━━━━━━━━━━━━━━━━━
▶ 3. HYBRID PATTERN

Low-code UI + CAP service.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CRITERIA

Complexity, data volume, integrity, skills.

━━━━━━━━━━━━━━━━━━━━
▶ 5. LIFECYCLE

Transports, versions, support ownership.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

List requirements for an app.
Score them against criteria.
Choose low-code, pro-code or hybrid.

✅ CHECKPOINT: decision documented with reasons.

Code example

ABAP Code

===== DECISION CRITERIA =====UI-heavy, simple logic, business-owned → Build AppsTransactions, validations shared by many clients → CAP (Build Code)Mixed → Build Apps UI + CAP OData service ===== HYBRID EXAMPLE =====Build Apps (mobile audit form) → destination → CAP service (validation, S/4 posting) → S/4HANA

Real project scenario

A team implemented pricing validation in three low-code apps; rules diverged and caused wrong quotes. Moving validation into one CAP service used by all apps fixed consistency.

Common mistakes

Complex logic in low-code.
Duplicated rules.
Ignoring maintenance owner.
No testing.
Tool by preference.

Best practices

Criteria-based choice.
Logic in services.
Hybrid patterns.
Clear ownership.
Automated tests for services.

Interview angle

Questions: "When low-code vs pro-code?", "What is the hybrid pattern?", "Who maintains low-code apps?"
Strong answer: strengths, criteria, hybrid, lifecycle.

Practice this lesson

Quick check

1. What is the hybrid pattern in SAP Build?

2. Which practice is risky when choosing low-code?

3. A pricing validation is needed by a low-code app, an API and a workflow. Where should it be implemented?

Interview questions

1. Explain the purpose, end-to-end flow and key design decisions in "SAP Build low-code vs pro-code decisions".

Answer it in your own words first, then compare.

2. A project encounters a problem while implementing "SAP Build low-code vs pro-code decisions". What evidence would you check before changing configuration, code or architecture?