Why train Extension-to-Deploy as an end-to-end process?

Because the user-facing step depends on upstream master data, status, integration and period-end controls.

What should support check first when the process fails?

Start with the source document, status, log, master data and authorization before changing configuration.

ABAP · ABAP / Development

Extension-to-Deploy SAP S/4HANA training

Build clean-core extensions from requirement through API/BAdI design, test and transport.

Prozessueberblick und Geschaeftskontext

ABAP development in S/4HANA should protect the clean core. Developers need to choose released APIs, CDS views, BAdIs, key-user extensibility or side-by-side extensions before writing code.

Learners can evaluate an extension requirement, choose a supported extension point and deploy it with tests and rollback evidence.

End-to-End-Ablauf

1
Analyze requirement
Jira / Solution Manager
Fiori-App: Manage Requirements
ACDOCA-Auswirkung: Defines process, trigger and data ownership.
2
Find extension point
SE18 / ADT
Fiori-App: Custom Fields and Logic; ADT
ACDOCA-Auswirkung: Selects released API, BAdI or side-by-side option.
3
Build and test
ADT / SE80
Fiori-App: ABAP Development Tools
ACDOCA-Auswirkung: Implements code with unit and integration checks.
4
Run quality gates
ATC
Fiori-App: ABAP Test Cockpit
ACDOCA-Auswirkung: Finds syntax, security and clean-core issues.
5
Transport and monitor
SE10 / STMS
Fiori-App: Transport Organizer
ACDOCA-Auswirkung: Moves extension and verifies runtime logs.

Wichtige Tabellen

Table	Erklaerung
TADIR	Repository object directory.
TRDIR	ABAP program directory.
DD02L / DD03L	Dictionary table and field metadata.
SXS_ATTR / Enhancement metadata	Enhancement framework and BAdI metadata context.
E070 / E071	Transport request and object list.

Schritt-fuer-Schritt-Anleitung

Start with standard capability

Check whether configuration, Fiori adaptation or released API solves the need.

Achten Sie auf: Custom code should not replace available standard behavior.

Choose upgrade-stable design

Prefer released APIs, CDS views, BAdIs and side-by-side services.

Achten Sie auf: Direct table updates or modifications are long-term upgrade risk.

Test the process trigger

Validate input structures, authorization, performance and failure behavior.

Achten Sie auf: A BAdI can be technically correct but wrong in a mass-processing scenario.

Document support model

Record owner, trigger, side effects, rollback and monitoring.

Achten Sie auf: Hidden extensions become expensive incidents after upgrades.

Haeufige Fehler und Fehlerbehebung

Extension breaks after upgrade

Wahrscheinliche Ursache: It used unreleased object or implicit dependency.

Loesungsweg: Replace with released API/BAdI and add ATC checks.

BAdI implementation slows posting

Wahrscheinliche Ursache: Expensive logic runs synchronously in a high-volume process.

Loesungsweg: Move heavy logic to asynchronous processing or optimize selection.

Transport misses dependent object

Wahrscheinliche Ursache: CDS, class, authorization or customizing dependency was not included.

Loesungsweg: Review object list and import sequence.

ECC zu S/4HANA Unterschiede

S/4HANA shifts development toward released objects, ABAP Cloud principles, CDS, RAP and clean-core extensibility instead of direct modification of standard code.

Glossar

Clean core: Approach keeping extensions separated from SAP standard internals.
BAdI: Business Add-In extension point delivered by SAP.
CDS view: Core Data Services model for semantically rich data access.
ATC: ABAP Test Cockpit quality and compliance check framework.

Wissenstest

Schließen Sie den Test mit mindestens 70 % ab, um das Zertifikat freizuschalten.

Generator starten