As orga­ni­za­tions adopt AI and migrate to SAP S/4HANA, main­tain­ing a clean core will only become increas­ing­ly essen­tial to achiev­ing the agili­ty and scal­a­bil­i­ty need­ed in today’s busi­ness envi­ron­ment. This con­cept encom­pass­es the entire ERP envi­ron­ment: data, process­es, inte­gra­tions, oper­a­tions, and extensibility.

For SAP, a clean core means keep­ing sys­tems ​“up to date, doc­u­ment­ed, con­sis­tent, effi­cient, and cloud com­pli­ant,” accord­ing to SAP Senior Prod­uct Man­ag­er Deep­ti Patil, who recent­ly pre­sent­ed a ses­sion on clean-core method­olo­gies along­side Tim Steuer, Vice Pres­i­dent of SAP Appli­ca­tion Life­cy­cle Man­age­ment (ALM), at SAP Sap­phire & ASUG Annu­al Conference.

A mod­ern ERP envi­ron­ment should be stan­dard­ized, agile, and upgrade-friend­ly — enabling faster inno­va­tion cycles and long-term flex­i­bil­i­ty. Patil empha­sized that this approach allows orga­ni­za­tions to keep ​“their core as stan­dard and effi­cient as pos­si­ble,” enabling them to focus on their unique dif­fer­en­ti­at­ing fac­tors rather than man­ag­ing customizations.

Steuer placed this guid­ance with­in SAP’s broad­er strat­e­gy. ​“We want to help our cus­tomers main­ly be in the mode of con­sum­ing enter­prise-grade soft­ware,” he explained. The path varies depend­ing on whether orga­ni­za­tions are new or exist­ing SAP cus­tomers, but the des­ti­na­tion remains the same — mov­ing to the pub­lic cloud to ​“ben­e­fit from inno­va­tion immediately.” 

For exist­ing cus­tomers with exten­sive cus­tomiza­tions, SAP S/4HANA Pri­vate Cloud Edi­tion serves as a valu­able tran­si­tion­al step. Steuer not­ed that this inter­me­di­ate envi­ron­ment helps cus­tomers learn how to deal with a clean core while grad­u­al­ly prepar­ing for their jour­ney to Pub­lic Cloud solutions.

Debunk­ing Mis­con­cep­tions and Shift­ing the Mindset

A com­mon myth is that a clean core pro­hibits all cus­tomiza­tion. ​“That’s not true,” Patil said. ​“We know that for busi­ness­es, it’s not always pos­si­ble to use the stan­dard prod­uct as is. Every busi­ness is dif­fer­ent. But are they real­ly different?” 

While some process­es are unique, she said, the major­i­ty of them are shared across indus­tries. Dif­fer­en­ti­at­ing capa­bil­i­ties should be han­dled via sup­port­ed exten­sion methods.

Patil com­pared a bulk-goods retail­er and a spe­cial­ty gro­cer to illus­trate the nuance. While both sell con­sumer prod­ucts, one may empha­size check­out speed and automa­tion, while the oth­er builds on more human inter­ac­tion. ​“We want our cus­tomers to iden­ti­fy what their dif­fer­en­ti­at­ing fac­tor is,” she said. ​“We’re not let­ting you lose that. We’ll help you with the exten­sions to make sure that part of your busi­ness is tak­en care of.”

Patil empha­sized that a clean core is fun­da­men­tal­ly ​“not a tech­nol­o­gy” but rather ​“a mind­set” that includes gov­er­nance and rep­re­sents an ongo­ing jour­ney rather than a one-time imple­men­ta­tion. She also described a clean core as a fun­da­men­tal ​“IT hygiene fac­tor” that orga­ni­za­tions must main­tain across sys­tems, process­es, and teams.

Steuer rein­forced this per­spec­tive: ​“It’s fine to have your own process­es. The ques­tion is how you imple­ment them.” Rather than mod­i­fy­ing SAP’s code direct­ly, orga­ni­za­tions should lever­age exten­sion plat­forms like SAP Busi­ness Tech­nol­o­gy Plat­form (BTP), SAP Build, or SAP S/4HANA extensions.

This approach ensures that cus­tomiza­tions remain sep­a­rate from SAP stan­dards so it doesn’t break the upgrade process or slow down inno­va­tion cycles. Steuer point­ed out that the ulti­mate goal is to ​“stay as close as pos­si­ble” to the stan­dard solu­tion, enabling com­pa­nies to ​“con­sume inno­va­tion from SAP as quick­ly as pos­si­ble” while main­tain­ing their com­pet­i­tive edge.

Clean Core Principles

The clean core mod­el cen­ters on five pillars:

1. Stan­dard­ize processes.

Patil stressed that orga­ni­za­tions should begin by eval­u­at­ing where stan­dard SAP process­es can be used effec­tive­ly rather than repli­cat­ing out­dat­ed or heav­i­ly cus­tomized work­flows from past sys­tems. She illus­trat­ed this with a com­mon real-world sce­nario: ​“A busi­ness lead comes to me say­ing, ​‘I want to change this process.’ Ask, ​‘Can you do it in a stan­dard way, the way SAP has pro­vid­ed? Will the out­come be dif­fer­ent or the same?’”

2. Extend with purpose.

SAP encour­ages clean exten­sions. ​“Use only the stan­dard ways of exten­sion imple­men­ta­tion,” Patil said. That includes build­ing decou­pled exten­sions using SAP’s rec­om­mend­ed tools, such as BTP, Build Process Automa­tion, and Build Apps. Patil added that SAP pro­vides readi­ness checks to help orga­ni­za­tions iden­ti­fy and doc­u­ment cus­tom code before migration.

3. Elim­i­nate data debt.

Unused, out­dat­ed data bur­dens sys­tems and com­pli­cates oper­a­tions. ​“You don’t want to keep data for decades and decades if it’s not being used any­where,” Patil not­ed. Reg­u­lar cleanup sup­ports both effi­cien­cy and data integrity.

4. Favor stan­dard integrations.

Avoid bur­den­some cus­tom inter­faces. ​“Use stan­dard APIs as much as pos­si­ble. Don’t cre­ate cus­tom inte­gra­tions again; avoid them as much as pos­si­ble,” Patil advised. Before cus­tomiz­ing, teams should assess whether the desired out­comes can be achieved with SAP’s stan­dard functionality.

5. Mon­i­tor oper­a­tional performance.

A clean core isn’t sta­t­ic; it requires real-time insight. ​“Keep that end-to-end focus. If some­thing changes, if there are some anom­alies hap­pen­ing, take care of them right away,” she said.

These pil­lars form the foun­da­tion of a gov­er­nance mod­el that spans project phas­es and tech­ni­cal domains.

Tools to Oper­a­tional­ize a Clean Core

SAP Cloud ALM serves as what Patil describes as ​“the orches­tra­tor” or ​“con­nec­tive tis­sue between busi­ness require­ments and tech­ni­cal imple­men­ta­tions.” The plat­form sup­ports sev­er­al crit­i­cal functions:

• Project and task man­age­ment with Acti­vate methodology
• Fit-to-stan­dard work­shops to col­lect and assess requirements
• Test man­age­ment to gen­er­ate and exe­cute cas­es from doc­u­ment­ed tasks
• Change con­trol, life­cy­cle trace­abil­i­ty, and regres­sion testing

“You col­lect and doc­u­ment and assess every require­ment dur­ing your fit-to-stan­dard work­shop,” Patil said. Fol­low­ing up, Steuer empha­sized com­plete vis­i­bil­i­ty and con­trol over the project: ​“You can trace the require­ments from the fit-to-stan­dard work­shop all the way to deploy­ment in production.”

Steuer also described how SAP Sig­navio sup­ports this process from the start: ​“The busi­ness talks about the process­es in SAP Sig­navio, and the fit-to-stan­dard work­shops are exe­cut­ed there. Then, the derived require­ments are fol­lowed up in SAP Cloud ALM.”

Beyond imple­men­ta­tion, SAP Cloud ALM pro­vides cross-sys­tem mon­i­tor­ing capa­bil­i­ties that both busi­ness and IT users can lever­age to iden­ti­fy anom­alies and process dis­rup­tions. Patil illus­trat­ed this with a prac­ti­cal exam­ple: when an employ­ee record cre­at­ed in SAP Suc­cess­Fac­tors affects down­stream sys­tems, such as cost cen­ters and trav­el man­age­ment, SAP Cloud ALM offers vis­i­bil­i­ty across the entire process flow.

This is sup­port­ed by SAP’s open teleme­try approach, which mon­i­tors how busi­ness process­es exe­cute, includ­ing exten­sions built on SAP BTP, and detects anom­alies in real time.

For exten­si­bil­i­ty, SAP offers clean cus­tom devel­op­ment via on-stack, side-by-side, and hybrid mod­els. ​“Exten­sions are great,” Patil said. ​“But main­tain that clean core while you’re adopt­ing SAP solu­tions and, of course, meet­ing your spe­cif­ic busi­ness needs.” She advised cus­tomers to decou­ple exten­sions and doc­u­ment them thor­ough­ly, not­ing that SAP Cloud ALM sup­ports deploy­ment and test­ing for these extensions.

Steuer acknowl­edged that ​“Some cus­tomers are unfa­mil­iar with SAP BTP and just get­ting start­ed. We have a roadmap that describes step by step how to adopt SAP BTP.” SAP Cloud ALM helps syn­chro­nize thead­op­tion across tech­ni­cal and orga­ni­za­tion­al boundaries.

What Cus­tomers Can Do Now

Both speak­ers high­light­ed that part­ner engage­ment is a crit­i­cal suc­cess fac­tor. ​“Talk to your part­ners and make a plan to get it going,” Steuer said.

With part­ners on board, orga­ni­za­tions should waste no time begin­ning their clean core jour­ney. ​“The steps are easy. Start. Or, as a famous shoe man­u­fac­tur­er would call it, just do it,” Steuer said.

Steuer point­ed to Pana­son­ic as a lead­ing exam­ple: ​“Pana­son­ic has sig­nif­i­cant­ly invest­ed in orches­trat­ing their SAP BTP exten­sions and enabling that to be cov­ered by Cloud ALM monitoring.”

He also cit­ed anoth­er cus­tomer who achieved suc­cess by get­ting their sys­tems inte­gra­tor (SI) ful­ly on board with clean core prin­ci­ples. This orga­ni­za­tion ​“con­vinced their SI to ful­ly embrace the mech­a­nisms of devel­op­ing and adjust­ing cus­tomiza­tion with the clean core approach using Cloud ALM,” which proved crit­i­cal to their implementation.

Cloud ALM is avail­able to all SAP cus­tomers, includ­ing RISE with SAP cus­tomers, and includes accel­er­a­tors to sim­pli­fy onboard­ing. Steuer encour­aged teams to use these tools to imple­ment gov­er­nance from the start and involve part­ners ear­ly. ​“We have great onboard­ing ses­sions that are done as part of the RISE jour­ney but are also avail­able to all cus­tomers,” he said. Steuer not­ed that SAP pro­vides dash­boards to help cus­tomers track their progress.

Patil empha­sized that a clean core is not a one-time con­fig­u­ra­tion. ​“It’s going to be a jour­ney. And we want to help our cus­tomers through­out it,” she said. It requires ongo­ing coor­di­na­tion, process dis­ci­pline, and the right tools at the right time.