This arti­cle was authored by Her­nan Gioioso, Chief Prod­uct Offi­cer at DataXstream. 

DataXstream has spent more than two decades immersed in SAP envi­ron­ments. The company’s dual iden­ti­ty as both a ser­vice provider and prod­uct inno­va­tor has giv­en it a clear view into the chal­lenges cus­tomers face when sell­ing through com­plex, mul­ti-chan­nel ecosys­tems. As it oper­at­ed its own busi­ness using SAP and OMS+ inter­nal­ly, DataXstream encoun­tered the same fric­tion points that its cus­tomers aimed to resolve.

Those insights became par­tic­u­lar­ly rel­e­vant as momen­tum grew around SAP S/4HANA Cloud Pub­lic Edi­tion. The exist­ing OMS+ solu­tion was opti­mized for on-premise and Pri­vate Cloud envi­ron­ments; and as SAP intro­duced clean-core prin­ci­ples, DataXstream rec­og­nized an oppor­tu­ni­ty to engi­neer a solu­tion pur­pose-built for these new archi­tec­tur­al standards.

This effort involved rethink­ing how order man­age­ment func­tions under cloud con­straints. Con­se­quent­ly, OMS+ Cloud was designed to fit the per­for­mance, scal­a­bil­i­ty, and life­cy­cle expec­ta­tions of S/4HANA Cloud Pub­lic Edition.

Meet­ing the Demands of Mul­ti-Chan­nel Order Management

Sales teams today face a logis­ti­cal real­i­ty that lega­cy sys­tems strug­gle to han­dle. The plat­form is engi­neered to man­age orders con­tain­ing more than a thou­sand line items, processed across a tan­gled web of glob­al regions and vary­ing deliv­ery meth­ods. Regard­less of where the sale hap­pens — at a phys­i­cal counter, in a call cen­ter, or on a mobile tablet — the user demands an inter­face that is fast, uni­fied, and accurate.

OMS+ Cloud solves this by cre­at­ing a cen­tral­ized com­mand cen­ter for orders that auto­mates crit­i­cal checks like pric­ing and inven­to­ry to dras­ti­cal­ly reduce man­u­al work. Designed for clean core stan­dards, the solu­tion is built to deploy instant­ly via the SAP Store and scale glob­al­ly with­out com­pro­mis­ing sys­tem stability.

OMS+ Cloud gives cus­tomers a mod­ern path for­ward. It allows them to imple­ment advanced order man­age­ment process­es in the Pub­lic Cloud while main­tain­ing the archi­tec­tur­al integri­ty need­ed to ensure seam­less future upgrades.

To achieve this bal­ance between inno­va­tion and sta­bil­i­ty, the plat­form uses a com­bined archi­tec­ture: S/4HANA Pub­lic Cloud han­dles trans­ac­tion­al log­ic, while SAP Busi­ness Tech­nol­o­gy Plat­form (BTP) man­ages inte­gra­tion and exten­si­bil­i­ty. Work­loads are dis­trib­uted between ABAP Cloud and SAP BTP to ensure per­for­mance and sup­port growth.

DataXstream’s solu­tion remains tight­ly aligned with S/4HANA’s native data struc­tures. Order pro­cess­ing runs clean­ly, main­tain­ing high per­for­mance and pre­vent­ing mis­matched behav­iors between lay­ers. Mean­while, BTP pro­vides the space for devel­op­ers to add new capa­bil­i­ties, con­nect sys­tems, and sur­face insights through ana­lyt­ics or cus­tom applications.

This struc­ture was cho­sen inten­tion­al­ly to sup­port long-term exten­si­bil­i­ty and sys­tem resilience. It respects SAP’s release cadence and elim­i­nates the risks that come from direct­ly mod­i­fy­ing ERP code. Cus­tomers can con­tin­ue to inno­vate with­out fac­ing upgrade dis­rup­tions or con­fig­u­ra­tion freezes.

Clean Core and Scal­able Delivery

The shift to Pub­lic Cloud intro­duced a new devel­op­ment dis­ci­pline. DataXstream’s engi­neers were expe­ri­enced in enhanc­ing SAP from the inside, but clean-core devel­op­ment required a dif­fer­ent approach. They had to adopt the tools and habits of exten­sion-based design, using only released APIs, CDS views, and sup­port­ed exten­sion points.

The tran­si­tion came with trade­offs. Some fea­tures, such as iden­ti­ty prop­a­ga­tion using Busi­ness Objects, were not ful­ly sup­port­ed in the way the team pre­ferred. To work around miss­ing func­tion­al­i­ty, the team used com­mu­ni­ca­tion-user authen­ti­ca­tion and filed for­mal requests to SAP through the influ­ence channel.

Rather than push­ing ahead with short­cuts, the team adopt­ed a design-first approach requir­ing tighter col­lab­o­ra­tion between func­tion­al and tech­ni­cal teams. Exten­si­bil­i­ty gaps were flagged dur­ing design, before code was written.

Clean-core prin­ci­ples demand­ed more delib­er­ate engi­neer­ing choic­es, but those choic­es result­ed in a prod­uct bet­ter suit­ed for long-term com­pat­i­bil­i­ty. The team replaced man­u­al deploy­ment meth­ods with auto­mat­ed pipelines that sup­port con­sis­tent, glob­al roll­outs. The prod­uct is pro­vi­sioned through SAP Store, and updates are deployed using CI/CD process­es that min­i­mize disruption.

BTP tools mon­i­tor the sys­tem con­tin­u­ous­ly, track­ing key per­for­mance met­rics and sur­fac­ing poten­tial issues ear­ly. Updates are deliv­ered with­out down­time, and cus­tomers receive sup­port through a glob­al esca­la­tion mod­el with options to par­tic­i­pate in SAP Influ­ence programs.

Every imple­men­ta­tion gen­er­ates insight that informs the next. Prod­uct evo­lu­tion is shaped by struc­tured feed­back from cus­tomers and kept in sync with SAP’s own release and inno­va­tion cycles.

SAP’s Pre­mi­um Cer­ti­fi­ca­tion process served as a check­point for the work. OMS+ Cloud was eval­u­at­ed on its tech­ni­cal com­pli­ance, secu­ri­ty pos­ture, upgrade behav­ior, and per­for­mance under load. SAP eval­u­at­ed how OMS+ Cloud lever­ages released APIs and con­firmed that its exten­si­bil­i­ty does not threat­en the sta­bil­i­ty of S/4HANA Cloud.

For cus­tomers, this cer­ti­fi­ca­tion pro­vides assur­ance that the prod­uct is pro­duc­tion-ready and well aligned with SAP’s oper­a­tional stan­dards. The cer­ti­fi­ca­tion con­firms the product’s abil­i­ty to scale, stay cur­rent with releas­es, and func­tion safe­ly with­in the core S/4HANA environment.

Align­ing With What Comes Next

Many SAP cus­tomers con­tin­ue to ques­tion whether S/4HANA Cloud Pub­lic Edi­tion can accom­mo­date advanced order man­age­ment. The work behind OMS+ Cloud has demon­strat­ed that it can. The solu­tion sup­ports com­plex con­fig­u­ra­tions, large-vol­ume trans­ac­tions, and geo­graph­i­cal­ly dis­trib­uted ful­fill­ment, all with­in SAP’s clean-core framework.

Cus­tomers who pre­vi­ous­ly hes­i­tat­ed to move their sales exe­cu­tion to Pub­lic Cloud are find­ing that the capa­bil­i­ties now exist. They are no longer forced to com­pro­mise between meet­ing com­pli­ance stan­dards and sup­port­ing sophis­ti­cat­ed operations.

Its reli­a­bil­i­ty is a direct result of archi­tec­tur­al dis­ci­pline and inten­tion­al design, not just func­tion­al breadth. The archi­tec­ture, tool­ing, and deliv­ery meth­ods all rein­force long-term sustainability.

At SAP TechEd in Berlin, it became clear that DataXstream’s direc­tion aligns with SAP’s broad­er strat­e­gy. The empha­sis on ABAP Cloud, Busi­ness AI, and com­pos­able archi­tec­ture val­i­dat­ed the company’s roadmap for OMS+ Cloud. Those same pri­or­i­ties con­tin­ue to shape new fea­tures under development.

SAP’s 2025 Pin­na­cle Award for Busi­ness AI Part­ner Inno­va­tion acknowl­edged both the progress and the impact of DataXstream’s work. OMS+ Cloud is already explor­ing AI-dri­ven capa­bil­i­ties through OMS+ IA, with future enhance­ments aligned to SAP’s stan­dards for exten­si­bil­i­ty and life­cy­cle safety.

DataXstream’s roots with SAP run deep. Since its first SAP instal­la­tion in 1998, the com­pa­ny has sup­port­ed over 75 cus­tomer SAP sys­tems and con­tin­u­al­ly evolved with the plat­form. OMS+ Cloud is a con­tin­u­a­tion of that lega­cy. It is a prod­uct built for S/4HANA Cloud Pub­lic Edi­tion, designed to han­dle com­plex­i­ty and ready to adapt as SAP’s future unfolds.

Her­nan Gioioso is the Chief Prod­uct Offi­cer at DataXstream.