SAP experts recent­ly pro­vid­ed the ASUG mem­ber com­mu­ni­ty with insights into the ben­e­fits orga­ni­za­tions can unlock from the SAP Busi­ness Tech­nol­o­gy Plat­form Enter­prise Agree­ment (BTPEA), a new con­sump­tion-based mod­el for SAP BTP services. 

Dur­ing an April 15 web­cast (includ­ed with ASUG mem­ber­ship; watch the replay now), Sylvie Sol­lod, Vice Pres­i­dent of Mar­ket­ing & Solu­tions for SAP BTP at SAP, and Loren Cor­bridge, Glob­al Pric­ing Con­sul­tant at SAP, explained why SAP is imple­ment­ing this new mod­el, how it can help cus­tomers pur­su­ing dig­i­tal trans­for­ma­tion, and what key dif­fer­ences exist between SAP BTPEA and lega­cy SAP BTP licens­ing options.

The mod­el enables SAP BTP cus­tomers to only lever­age the ser­vices they need, as they require them, accord­ing to Sol­lod. ​“SAP BTPEA helps accel­er­ate inno­va­tion and increase cus­tomer val­ue through improv­ing return on invest­ment (ROI) and flex­i­bil­i­ty,” she explained.

How This Change Affects Cur­rent SAP BTP Cus­tomers  

SAP is pri­mar­i­ly imple­ment­ing SAP BTPEA for net-new SAP BTP cus­tomers, but Cor­bridge not­ed that cur­rent cus­tomers lever­ag­ing the exist­ing Cloud Plat­form Enter­prise Agree­ment (CPEA) com­mer­cial mod­el for SAP BTP will be able to do so ​“for the fore­see­able future.”

How­ev­er, cus­tomers inter­est­ed in adopt­ing the new mod­el can do so with­in their stan­dard renew­al process­es. ​“No one is going to start pres­sur­ing you to move off CPEA,” Cor­bridge said. 

One of the most impor­tant notes for exist­ing cus­tomers is that adopt­ing BTPEA does not impact an organization’s tech­ni­cal land­scape. ​“Your tech­ni­cal land­scape will be pre­served if you move [to BTPEA] at con­tract renew­al,” Cor­bridge said, dis­cussing the expe­ri­ence of cus­tomer-man­aged glob­al accounts shift­ing to BTPEA. More­over, no tech­ni­cal migra­tion is required to make the switch. 

“There’s no change,” she told atten­dees. ​“We can just flip a switch on your glob­al account.”

Cor­bridge also dis­cussed how cus­tomers lever­ag­ing ser­vices not cur­rent­ly includ­ed in the BTPEA mod­el can still make use of those ser­vices once adopt­ing the mod­el. SAP will allow cus­tomers to pur­chase short-term and long-term sub­scrip­tions to any ser­vices not includ­ed in the BTPEA mod­el so enter­pris­es can con­tin­ue lever­ag­ing them in their land­scape with­out interruption.

CPEA v. BTPEA  

Dur­ing the webi­nar, Cor­bridge also dis­cussed how the new BTPEA mod­el dif­fers from CPEA, not­ing that the sim­i­lar­i­ties between these two mod­els out­weigh the differences.

The over­all struc­ture remains the same; BTPEA allows cus­tomers to pre-pay for cloud cred­its, and dis­counts are applied depend­ing on the num­ber of cred­its cus­tomers pur­chase. Orga­ni­za­tions can use those cred­its over a spec­i­fied cred­it peri­od — typ­i­cal­ly one year. Addi­tion­al­ly, SAP main­tains a min­i­mum price guar­an­tee. So, if the price of SAP BTP ser­vices drops after cus­tomers sign their con­tracts, SAP will bill them at the new, low­er price. 

One key dif­fer­ence between the two billing mod­els is an updat­ed scope of eli­gi­ble ser­vices. SAP includ­ed new ser­vices with­in BTPEA — such as SAP Ana­lyt­ics Cloud, pub­lic sys­tem option (BI and Plan­ning) — while remov­ing some lega­cy ser­vices with very low adoption. 

Addi­tion­al­ly, BTPEA will also fea­ture a new dep­re­ca­tion pol­i­cy to ​“stream­line SAP BTP ser­vices,” accord­ing to Cor­bridge, who not­ed that this pol­i­cy will have two groups. Group one will func­tion sim­i­lar­ly to CPEA and pro­vide sup­port for any dep­re­ca­tion ser­vice through the end of the cur­rent con­tract term. Group two includes inno­va­tion ser­vices, which can either be rolled into the first group over time or removed after a six-month notice. 

Learn how to get involved with the ASUG Com­mu­ni­ty with our Com­mu­ni­ty Con­ver­sa­tions and Region­al Chap­ter Meetings.