โŒ

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

The tech leadership realizing more than the sum of parts

14 January 2026 at 05:00

Waiting on replacement parts can be more than just an inconvenience. It can be a matter of sharp loss of income and opportunity. This is especially true for those who depend on industrial tools and equipment for agriculture and construction. So to keep things run as efficiently as possible, Parts ASAP CIO John Fraser makes sure end customer satisfaction is the highest motivation to get the tech implementation and distribution right.

โ€œWhat it comes down to, in order to achieve that, is the team,โ€ he says. โ€œI came into this organization because of the culture, and the listen first, act later mentality. Itโ€™s something I believe in and Iโ€™m going to continue that culture.โ€

Bringing in talent and new products has been instrumental in creating a stable e-commerce model, so Fraser and his team can help digitally advertise to customers, establish the right partnerships to drive traffic, and provide the right amount of data.

โ€œOnce youโ€™re a customer of ours, we have to make sure weโ€™re a needs-based business,โ€ he says. โ€œWe have to be the first thing that sticks in their mind because itโ€™s not about a track on a Bobcat that just broke. Itโ€™s $1,000 a day someoneโ€™s not going to make due to a piece of equipment thatโ€™s down.โ€

Ultimately, this strategy helps and supports customers with a collection of highly-integrated tools to create an immersive experience. But the biggest challenge, says Fraser, is the variety of marketplace channels customers are on.

โ€œSome people prefer our website,โ€ he says. โ€œBut some are on Walmart or about 20 other commercial channels we sell on. Each has unique requirements, ways to purchase, and product descriptions. On a single product, we might have 20 variations to meet the character limits of eBay, for instance, or the brand limitations of Amazon. So weโ€™ve built out our own product information management platform. It takes the right talent to use that technology and a feedback loop to refine the process.โ€

Of course, AI is always in the conversation since people canโ€™t write updated descriptions for 250,000 SKUs.

โ€œAI will fundamentally change what everybodyโ€™s job is,โ€ he says. โ€œI know I have to prepare for it and be forward thinking. We have to embrace it. If you donโ€™t, youโ€™re going to get left behind.โ€

Fraser also details practical AI adoption in terms of pricing, product data enhancement, and customer experience, while stressing experimentation without over-dependence. Watch the full video below for more insights, and be sure to subscribe to the monthly Center Stage newsletter by clicking here.

On consolidating disparate systems: You certainly run into challenges. People are on the same ERP system so they have some familiarity. But even within that, you have massive amounts of customization. Sometimes thatโ€™s very purpose-built for the type of process an organization is running, or that unique sales process, or whatever. But in other cases, itโ€™s very hard. Weโ€™ve acquired companies with their own custom built ERP platform, where they spent 20 years curating it down to eliminate every button click. Those donโ€™t go quite as well, but you start with a good culture, and being transparent with employees and customers about whatโ€™s happening, and you work through it together. The good news is it starts with putting the customer first and doing it in a consistent way. Tell people change is coming and build a rapport before you bring in massive changes. There are some quick wins and efficiencies, and so people begin to trust. Then, youโ€™re not just dragging them along but bringing them along on the journey.

On AI: Everybodyโ€™s talking it, but thereโ€™s a danger to that, just like there was a danger with blockchain and other kinds of immersive technologies. You have to make sure you know why youโ€™re going after AI. You canโ€™t just use it because itโ€™s a buzzword. You have to bake it into your strategy and existing use cases, and then leverage it. Weโ€™re doing it in a way that allows us to augment our existing strategy rather than completely and fundamentally change it. So for example, weโ€™re going to use AI to help influence what our product pricing should be. We have great competitive data, and a great idea of what our margins need to be and where the market is for pricing. Some companies are in the news because theyโ€™ve gone all in on AI, and AI is doing some things that are maybe not so appropriate in terms of automation. But if you can go in and have it be a contributing factor to a human still deciding on pricing, thatโ€™s where we are rather than completely handing everything over to AI.

On pooling data: We have a 360-degree view of all of our customers. We know when theyโ€™re buying online and in person. If theyโ€™re buying construction equipment and material handling equipment, weโ€™ll see that. But when somebodyโ€™s buying a custom fork for a forklift, thatโ€™s very different than someone needing a new water pump for a John Deere tractor. And having a manufacturing platform that allows us to predict a two and a half day lead time on that custom fork is a different system to making sure that water pump is at your door the next day. Trying to do all that in one platform just hasnโ€™t been successful in my experience in the past. So weโ€™ve chosen to take a bit of a hybrid approach where you combine the data but still have best in breed operational platforms for different segments of the business.

On scaling IT systems: The key is weโ€™re not afraid to have more than one operational platform. Today, in our ecosystem of 23 different companies, weโ€™re manufacturing parts in our material handling business, and thatโ€™s a very different operational platform than, say, purchasing overseas parts, bringing them in, and finding a way to sell them to people in need, where you need to be able to distribute them fast. Itโ€™s an entirely different model. So weโ€™re not establishing one core platform in that case, but the right amount of platforms. Itโ€™s not 23, but itโ€™s also not one. So as we think about being able to scale, itโ€™s also saying that if you try to be all things to all people, youโ€™re going to be a jack of all trades and an expert in none. So we want to make sure when we have disparate segments that have some operational efficiency in the back end โ€” same finance team, same IT teams โ€” weโ€™ll have more than one operational platform. Then through different technologies, including AI, ensure we have one view of the customer, even if theyโ€™re purchasing out of two or three different systems.

On tech deployment: Experiment early and then make certain not to be too dependent on it immediately. We have 250,000 SKUs, and more than two million parts that we can special order for our customers, and you canโ€™t possibly augment that data with a world-class description with humans. So we selectively choose how to make the best product listing for something on Amazon or eBay. But weโ€™re using AI to build enhanced product descriptions for us, and instead of having, say, 10 people curating and creating custom descriptions for these products, weโ€™re leveraging AI and using agents in a way that allow people to build the content. Now humans are simply approving, rejecting, or editing that content, so weโ€™re leveraging them for the knowledge they need to have, and if this going to be a good product listing or not. We know there are thousands of AI companies, and for us to be able to pick a winner or loser is a gamble. Our approach is to make it a bit of a commoditized service. But weโ€™re also pulling in that data and putting it back into our core operational platform, and there it rests. So if weโ€™re with the wrong partner, or they get acquired, or go out of business, we can switch quickly without having to rewrite our entire set of systems because we take it in, use it a bit as a commoditized service, get the data, set it at rest, and then we can exchange that AI engine. Weโ€™ve already changed it five times and weโ€™re okay to change it another five until we find the best possible partner so we can stay bleeding edge without having all the expense of building it too deeply into our core platforms.

SAP, S/4HANA ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ์ง€์› ์ข…๋ฃŒ ์•ž๋‘๊ณ  โ€˜5๊ฐœ์›” ์œ ์˜ˆโ€™ ์นด๋“œยทยทยทโ€œ์ด์ „ ์‹œ์ž‘ํ•œ ๊ธฐ์—…๋งŒ ํ•ด๋‹นโ€

9 January 2026 at 02:00

SAP๊ฐ€ ๋ฐ์ดํ„ฐ์„ผํ„ฐ ํ™˜๊ฒฝ ๋‚ด S/4HANA ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€(Compatibility Pack)์˜ ์ด์ „ ์ž‘์—…์„ ๋งˆ๋ฌด๋ฆฌํ•˜์ง€ ๋ชปํ•œ ๊ธฐ์—…์„ ์ง€์›ํ•˜๊ธฐ ์œ„ํ•ด ํ•œ์‹œ์ ์ธ ์œ ์˜ˆ ์กฐ์น˜๋ฅผ ๋‚ด๋†จ๋‹ค. ํ•ด๋‹น ํŒจํ‚ค์ง€ ์‚ฌ์šฉ ๊ถŒํ•œ์€ 2025๋…„ 12์›” 31์ผ์— ๋งŒ๋ฃŒ๋  ์˜ˆ์ •์ด์—ˆ์ง€๋งŒ, SAP๋Š” ์•„์ง ์ด๋ฅผ ์‚ฌ์šฉ ์ค‘์ธ ๊ธฐ์—…์ด ๋„ค์ดํ‹ฐ๋ธŒ ๊ธฐ๋Šฅ์œผ๋กœ ์˜ฎ๊ธธ ์ˆ˜ ์žˆ๋„๋ก 5๊ฐœ์›”์˜ ์ „ํ™˜ ๊ธฐ๊ฐ„์„ ์ถ”๊ฐ€๋กœ ์ œ๊ณตํ•œ๋‹ค๊ณ  ๋ฐํ˜”๋‹ค.

ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€๋Š” ์˜จํ”„๋ ˆ๋ฏธ์Šค ํ™˜๊ฒฝ์—์„œ S/4HANA๋กœ ์ „ํ™˜ํ•˜๋Š” ๊ธฐ์—…์ด ๊ธฐ์กด SAP ECC(ERP ์„ผํŠธ๋Ÿด ์ปดํฌ๋„ŒํŠธ)์˜ ๊ธฐ๋Šฅ์„ ์œ ์ง€ํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๊ธฐ ์œ„ํ•ด 2015๋…„ ๋„์ž…๋๋‹ค. ์ด๋Š” S/4HANA ์ดˆ๊ธฐ ๋ฒ„์ „์— ํฌํ•จ๋˜์ง€ ์•Š์•˜๊ฑฐ๋‚˜ ์ด์ „ํ•˜๋Š” ๋ฐ ์‹œ๊ฐ„์ด ํ•„์š”ํ•œ ๊ธฐ๋Šฅ์„ ๊ณ„์† ์‚ฌ์šฉํ•  ์ˆ˜ ์žˆ๋„๋ก ํ•˜๊ธฐ ์œ„ํ•œ ์กฐ์น˜์˜€๋‹ค. SAP์— ๋”ฐ๋ฅด๋ฉด ๋ˆ„๋ฝ๋œ ๊ธฐ๋Šฅ์€ 2023๋…„ ๋ฒ„์ „์˜ S/4HANA๋ฅผ ํ†ตํ•ด ๋ชจ๋‘ ์ œ๊ณต๋๋‹ค. SAP๋Š” ๋ธ”๋กœ๊ทธ ๊ฒŒ์‹œ๊ธ€์—์„œ, ๋ผ์ด์ฆˆ ์œ„๋“œ SAP(Rise with SAP) ๋˜๋Š” SAP ํด๋ผ์šฐ๋“œ ERP ๊ณ„์•ฝ์„ ํ†ตํ•ด ํด๋ผ์šฐ๋“œ ์ „ํ™˜์„ ์ง„ํ–‰ ์ค‘์ธ ๊ธฐ์—…์ด ์•„๋‹Œ ๊ฒฝ์šฐ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ์‚ฌ์šฉ ๊ถŒํ•œ๊ณผ ์ง€์›์ด 2025๋…„ ๋ง์— ์ข…๋ฃŒ๋œ๋‹ค๊ณ  ๋ฐํžŒ ๋ฐ” ์žˆ๋‹ค.

ํ•˜์ง€๋งŒ ์ƒ๋‹น์ˆ˜ ๊ณ ๊ฐ์ด ์ด์ „ ์ž‘์—…์„ ์™„๋ฃŒํ•˜๋Š” ๋ฐ ์ถ”๊ฐ€ ์‹œ๊ฐ„์ด ํ•„์š”ํ•œ ๊ฒƒ์œผ๋กœ ๋‚˜ํƒ€๋‚ฌ๋‹ค. ์ด์— ๋”ฐ๋ผ SAP๋Š” 2026๋…„ 5์›” ๋ง๊นŒ์ง€ ์ถ”๊ฐ€ ์—ฐ์žฅ ๊ธฐ๊ฐ„์„ ์ œ๊ณตํ•˜๊ธฐ๋กœ ํ–ˆ๋‹ค๊ณ  ๋ฐํ˜”๋‹ค. ๋˜ํ•œ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ๊ธฐ๋Šฅ์„ ๋Œ€์ฒดํ•˜๋Š” ํด๋ผ์šฐ๋“œ ์ œํ’ˆ์œผ๋กœ์˜ ์ „ํ™˜์„ ์•ž๋‹น๊ธฐ๊ธฐ ์œ„ํ•ด โ€˜๋งž์ถคํ˜• ํ”„๋กœ๊ทธ๋žจโ€™๋„ ์ œ๊ณตํ•  ๊ณ„ํš์ด๋‹ค.

SAP ๋Œ€๋ณ€์ธ์€ โ€œ์ „ํ™˜ ์ธ์„ผํ‹ฐ๋ธŒ์™€ ํด๋ผ์šฐ๋“œ ํ™•์žฅ ์ •์ฑ…์„ ๋น„๋กฏํ•ด ์—”ํ„ฐํ”„๋ผ์ด์ฆˆ ์•„ํ‚คํ…ํŠธ์˜ ์ง์ ‘ ์ง€์›, AI ๊ธฐ๋ฐ˜ ๋„๊ตฌ, ํผ๋ธ”๋ฆญ ํด๋ผ์šฐ๋“œ ์ด์ „์„ ์œ„ํ•œ ๋ชจ๋ฒ” ์‚ฌ๋ก€ ๊ฐ€์ด๋“œ๋ฅผ ์ œ๊ณตํ•œ๋‹ค. ๊ธฐ์—…์ด ์–ด๋–ค ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ๊ธฐ๋Šฅ์„ ์‚ฌ์šฉํ•˜๊ณ  ์žˆ๋Š”์ง€ ์‹๋ณ„ํ•˜๊ณ , ์ด๋ฅผ ๊ถŒ์žฅ๋˜๋Š” ํด๋ผ์šฐ๋“œ ์†”๋ฃจ์…˜์œผ๋กœ ๋Œ€์ฒดํ•˜๊ฑฐ๋‚˜ ์ด์ „ํ•  ์ˆ˜ ์žˆ๋„๋ก ์ „๋‹ด ์„œ๋น„์Šค๋ฅผ ์ œ๊ณตํ•ด ๋น„์ฆˆ๋‹ˆ์Šค ์šด์˜์— ์ฐจ์งˆ์ด ์—†๋„๋ก ์ง€์›ํ•˜๊ณ  ์žˆ๋‹คโ€๋ผ๊ณ  ์„ค๋ช…ํ–ˆ๋‹ค.

์œ ์˜ˆ ๊ธฐ๊ฐ„์ด ์ œ๊ณต๋˜์ง€ ์•Š๋Š” ๊ฒฝ์šฐ

๋‹ค๋งŒ ์ด๋ฒˆ 5๊ฐœ์›” ์—ฐ์žฅ์€ ์ด๋ฏธ ์ด์ „ ์ž‘์—…์„ ์‹œ์ž‘ํ•œ ๊ธฐ์—…์—๊ฒŒ๋งŒ ์ œ๊ณต๋œ๋‹ค. SAP ๋Œ€๋ณ€์ธ์€ โ€œ์ด์ „์„ ์•„์˜ˆ ์‹œ์ž‘ํ•˜์ง€ ์•Š์€ ๊ธฐ์—…์ด ์žˆ๋‹ค๋Š” ์‚ฌ์‹ค์„ ์ตœ๊ทผ ํ™•์ธํ–ˆ๋‹ค. ์ด๋“ค์— ๋Œ€ํ•ด์„œ๋Š” ๋งˆ๊ฐ์ผ ์ดํ›„ ์„ ํƒ์ง€์— ๋ณ€ํ™”๊ฐ€ ์—†์„ ๊ฒƒโ€์ด๋ผ๊ณ  ์–ธ๊ธ‰ํ–ˆ๋‹ค.

์—…๊ณ„ ๋ถ„์„๊ฐ€๋“ค์€ ์ด๋ฒˆ ์—ฐ์žฅ์ด ํ•ฉ๋ฆฌ์ ์ธ ํŒ๋‹จ์ด๋ผ๋Š” ๋ฐ์—๋Š” ๋™์˜ํ•˜๋ฉด์„œ๋„, ๊ทธ ์˜๋ฏธ์— ๋Œ€ํ•ด์„œ๋Š” ์„œ๋กœ ๋‹ค๋ฅธ ์‹œ๊ฐ์„ ๋ณด์ด๊ณ  ์žˆ๋‹ค.

์ธํฌํ…Œํฌ ๋ฆฌ์„œ์น˜ ๊ทธ๋ฃน์˜ ์ž๋ฌธ ์—ฐ๊ตฌ์› ์Šค์ฝง ๋น„ํด๋ฆฌ๋Š” โ€œECC/R3์—์„œ S/4HANA๋กœ ์ด์ „์„ ์ง„ํ–‰ ์ค‘์ธ ๊ธฐ์—…์ด ๋งŽ๊ณ , ์ด๋“ค ๊ธฐ์—…์€ ์—ฌ์ „ํžˆ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€๊ฐ€ ์ œ๊ณตํ•˜๋Š” ๋‹ค์–‘ํ•œ ๊ธฐ๋Šฅ์„ ํ™œ์šฉํ•˜๊ณ  ์žˆ๋‹ค. ์ด๋Ÿฐ ์ƒํ™ฉ์—์„œ SAP๊ฐ€ ์ง€์› ๋ฐ ์‚ฌ์šฉ ๊ถŒํ•œ์„ ์ผ๋ฐฉ์ ์œผ๋กœ ์ค‘๋‹จํ•œ๋‹ค๋ฉด, ๊ธฐ์—… ๋‚ด๋ถ€ ์—…๋ฌด์™€ ๊ณ ๊ฐ ๋Œ€์ƒ ๋น„์ฆˆ๋‹ˆ์Šค ํ”„๋กœ์„ธ์Šค ์ „๋ฐ˜์— ์น˜๋ช…์ ์ธ ํ˜ผ๋ž€์„ ์ดˆ๋ž˜ํ•  ์ˆ˜ ์žˆ๋‹คโ€๋ผ๊ณ  ๋ถ„์„ํ–ˆ๋‹ค.

๊ฐ€ํŠธ๋„ˆ์˜ ๋ถ€์‚ฌ์žฅ ๊ฒธ ์• ๋„๋ฆฌ์ŠคํŠธ ๋งˆ์ดํฌ ํˆฌ์ฐจ๋กœ๋„ค๋Š” ์ด๋ฒˆ ์กฐ์น˜๊ฐ€ ๊ธฐ์—…์˜ ํ˜„์‹ค์ ์ธ ๊ฑธ๋ฆผ๋Œ์„ ๋ฐ˜์˜ํ•œ ์‹ค์šฉ์ ์ธ ๊ฒฐ์ •์ด๋ผ๊ณ  ํ‰๊ฐ€ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ2025๋…„ ํ•œ ํ•ด ๋™์•ˆ ๊ฐ€ํŠธ๋„ˆ ์• ๋„๋ฆฌ์ŠคํŠธ๊ฐ€ ์ฒ˜๋ฆฌํ•œ ์ˆ˜์ฒœ ๊ฑด์˜ SAP ๊ณ ๊ฐ ๋ฌธ์˜ ๊ฐ€์šด๋ฐ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ๋ฌธ์ œ๊ฐ€ ์–ธ๊ธ‰๋œ ๋น„์ค‘์€ 1% ๋ฏธ๋งŒ์ด์—ˆ๋‹ค. ํ•˜์ง€๋งŒ ๊ทธ 1%์—๊ฒŒ๋Š” ๋งค์šฐ ์‹ฌ๊ฐํ•œ ๋ฌธ์ œโ€๋ผ๊ณ  ์„ค๋ช…ํ–ˆ๋‹ค. ์ด์–ด โ€œ์ด๋ฒˆ ์—ฐ์žฅ์€ ์˜ค๋Š˜๋‚  ๋งŽ์€ ๊ธฐ์—…์ด ํšจ์œจ์„ฑ ์ œ๊ณ ์™€ ๋น„์šฉ ์ตœ์ ํ™”์— ์ง‘์ค‘ํ•˜๋Š” ์ƒํ™ฉ์—์„œ ์ด์ „ ์ž‘์—…์ด ์ƒ๋‹นํ•œ ๋ถ€๋‹ด์ด๋ผ๋Š” ์ ์„ ์ธ์ •ํ•œ ๊ฒƒโ€์ด๋ผ๊ณ  ๋ถ„์„ํ–ˆ๋‹ค.

๋ฐ˜๋ฉด ๊ทธ๋ ˆ์ดํ•˜์šด๋“œ ๋ฆฌ์„œ์น˜์˜ ์ˆ˜์„ ์• ๋„๋ฆฌ์ŠคํŠธ ์‚ฐ์นซ ๋น„๋ฅด ๊ณ ๊ธฐ์•„๋Š” ์ด๋ฅผ ์ •์ฑ… ๋ณ€ํ™”๋กœ ํ•ด์„ํ•ด์„œ๋Š” ์•ˆ ๋œ๋‹ค๊ณ  ์ง€์ ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ์ด๋ฏธ ๊ฐœ์„  ์ž‘์—…์„ ์‹œ์ž‘ํ•œ ๊ณ ๊ฐ์—๊ฒŒ๋งŒ ์ ์šฉ๋˜๋Š”, ๋งค์šฐ ์ œํ•œ์ ์ธ ์œ ์˜ˆ ๊ธฐ๊ฐ„์ผ ๋ฟโ€์ด๋ผ๋ฉฐ โ€œ๊ฒ‰๋ณด๊ธฐ์—๋Š” ์œ ์—ฐํ•ด ๋ณด์ด์ง€๋งŒ ์‹ค์ œ๋กœ๋Š” ์„ ๋ณ„์ ์ธ ์„ ํƒ์ด๋‹ค. ์ด๋Š” ์ „ํ™˜ ๊ธฐ๊ฐ„์ด์ง€, ๊ตฌ์ œ ์กฐ์น˜๊ฐ€ ์•„๋‹ˆ๋‹คโ€๋ผ๊ณ  ๊ฐ•์กฐํ–ˆ๋‹ค.

์ž„์‹œ ๋ฐฉํŽธ

๊ณ ๊ธฐ์•„๋Š” SAP๊ฐ€ ์žฅ๊ธฐ์ ์ธ ๋กœ๋“œ๋งต์„ ํ›ผ์†ํ•˜์ง€ ์•Š์œผ๋ฉด์„œ ๊ณ ๊ฐ ๋ฐ˜๋ฐœ์„ ๊ด€๋ฆฌํ•˜๊ธฐ ์œ„ํ•ด ์˜๋„์ ์œผ๋กœ ์งง์€ ์œ ์˜ˆ ๊ธฐ๊ฐ„์„ ์„ค์ •ํ•œ ๊ฒƒ์ด๋ผ๊ณ  ๋ถ„์„ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ์—ฐ์žฅ ๊ธฐ๊ฐ„์ด ์งง๋‹ค๋Š” ์ ์ด ์ด๋ฅผ ๋ถ„๋ช…ํžˆ ๋ณด์—ฌ์ค€๋‹ค. 5๊ฐœ์›”์ด๋ผ๋Š” ๊ธฐ๊ฐ„์€ ๋ฐฉํ–ฅ์„ ๋ฐ”๊พธ๊ธฐ ์œ„ํ•œ ๊ฒƒ์ด ์•„๋‹ˆ๋ผ, ์ด๋ฏธ ์ „ํ™˜์„ ์ง„ํ–‰ ์ค‘์ธ ๊ณ ๊ฐ์ด ๋ฌด๋ฆฌ ์—†์ด ๋งˆ๋ฌด๋ฆฌํ•  ์ˆ˜ ์žˆ๋„๋ก ์—ฌ์ง€๋ฅผ ์ค€ ๊ฒƒโ€์ด๋ผ๊ณ  ์„ค๋ช…ํ–ˆ๋‹ค. ์ด์–ด โ€œ์ด๋ฅผ ํ†ตํ•ด ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ์ œ๊ณต์ด ์• ์ดˆ๋ถ€ํ„ฐ ์ž„์‹œ ๋ฐฉํŽธ์— ๋ถˆ๊ณผํ–ˆ๋‹ค๋Š” ์ ์„ ๋‹ค์‹œ ํ•œ๋ฒˆ ๋ถ„๋ช…ํžˆ ํ–ˆ๋‹คโ€๋ผ๊ณ  ํ‰๊ฐ€ํ–ˆ๋‹ค.

๋˜ํ•œ ๊ณ ๊ธฐ์•„๋Š” ๋งŽ์€ CIO๊ฐ€ S/4HANA ์ด์ „์„ ์„ฑ๊ณต์ ์œผ๋กœ ์™„๋ฃŒํ–ˆ๋‹ค๊ณ  ํŒ๋‹จํ–ˆ์Œ์—๋„ ๋ถˆ๊ตฌํ•˜๊ณ , ์‹ค์ œ๋กœ๋Š” ๊ธฐ์—…์ด ์—ฌ์ „ํžˆ ์œ„ํ—˜์— ๋…ธ์ถœ๋ผ ์žˆ๋‹ค๋Š” ์‚ฌ์‹ค์„ ๋’ค๋Šฆ๊ฒŒ ์ธ์‹ํ•˜๊ณ  ์žˆ๋‹ค๊ณ  ์ „ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ์ด์ „ ์ดํ›„ ๋” ์ด์ƒ ๋ฌธ์ œ๊ฐ€ ์—†๋‹ค๊ณ  ์—ฌ๊ฒผ๋˜ ๊ธฐ์—…์ด ๋‚ด๋ถ€ ์ค€๋น„ ์ƒํƒœ ์ ๊ฒ€ ๊ณผ์ •์ด๋‚˜ SAP ๋ผ์ด์„ ์Šค ๊ฐ์‚ฌ, ํ˜น์€ ์—…๊ทธ๋ ˆ์ด๋“œ ๊ณ„ํš ๋‹จ๊ณ„์—์„œ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ์š”์†Œ๊ฐ€ ์—ฌ์ „ํžˆ ํ™œ์„ฑํ™”๋ผ ์žˆ๋‹ค๋Š” ์‚ฌ์‹ค์„ ๋ฐœ๊ฒฌํ•˜๋Š” ์‚ฌ๋ก€๊ฐ€ ์ ์ง€ ์•Š๋‹คโ€๋ผ๊ณ  ์„ค๋ช…ํ–ˆ๋‹ค.

์ด์–ด ๊ทธ๋Š” โ€œ์ด ๋ฌธ์ œ์˜ ์œ„ํ—˜์€ ๋‹จ์ˆœํžˆ ๊ธฐ์ˆ ์ ์ธ ์ฐจ์›์— ๊ทธ์น˜์ง€ ์•Š๋Š”๋‹ค. ์žฌ๋ฌด์ , ์šด์˜์ , ํ‰ํŒ ๋ฆฌ์Šคํฌ๋กœ๊นŒ์ง€ ํ™•๋Œ€๋  ์ˆ˜ ์žˆ๋‹คโ€๋ผ๊ณ  ๋ถ„์„ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ์ง€์›์ด ์ข…๋ฃŒ๋˜๋ฉด ๋” ์ด์ƒ ํšŒํ”ผํ•  ์—ฌ์ง€๊ฐ€ ์—†๋‹ค. SAP๋Š” ํ–ฅํ›„ S/4HANA ๋ฆด๋ฆฌ์Šค์—์„œ ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ๊ธฐ๋Šฅ์„ ๊ธฐ์ˆ ์ ์œผ๋กœ ๋น„ํ™œ์„ฑํ™”ํ•  ๊ฐ€๋Šฅ์„ฑ๋„ ์—ด์–ด๋‘๊ณ  ์žˆ์–ด, ์ด๋Š” ๊ทœ์ • ์ค€์ˆ˜ ๋ฆฌ์Šคํฌ๋ฅผ ๋„˜์–ด ์‹ค์ œ ๋น„์ฆˆ๋‹ˆ์Šค ์ค‘๋‹จ์œผ๋กœ ์ด์–ด์งˆ ์ˆ˜ ์žˆ๋‹คโ€๋ผ๊ณ  ๊ฒฝ๊ณ ํ–ˆ๋‹ค.

๋น„ํด๋ฆฌ๋Š” ๊ทœ์ œ ์ค€์ˆ˜ ์ธก๋ฉด์˜ ๋ฌธ์ œ๋„ ์ง€์ ํ–ˆ๋‹ค. ๊ทธ๋Š” โ€œ๊ธฐ์กด์— ์„ค์ •๋œ 2025๋…„ ๋งŒ๋ฃŒ ์‹œ์ ์„ ๊ธฐ์ค€์œผ๋กœ ๋ณด๋ฉด, ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€๋ฅผ ๊ณ„์† ์‚ฌ์šฉํ•˜๋Š” ๊ธฐ์—…์€ ๊ธฐ์ˆ ์ ์œผ๋กœ SAP ์†Œํ”„ํŠธ์›จ์–ด ์‚ฌ์šฉ ๊ถŒํ•œ์„ ์ค€์ˆ˜ํ•˜์ง€ ์•Š๋Š” ์ƒํƒœ์— ๋†“์ธ๋‹ค. ์ด๋ฒˆ ์—ฐ์žฅ์€ SAP์™€ ํ˜‘๋ ฅํ•ด ํ˜ธํ™˜์„ฑ ํŒจํ‚ค์ง€ ๊ธฐ๋Šฅ ์‚ฌ์šฉ์„ ์ค‘๋‹จํ•˜๋ ค๋Š” ๊ธฐ์—…์—๊ฒŒ ์ˆจํ†ต์„ ํ‹”์›Œ์ฃผ๋Š” ์—ญํ• ์„ ํ•œ๋‹คโ€๋ผ๊ณ  ์„ค๋ช…ํ–ˆ๋‹ค.

๊ณ ๊ธฐ์•„๋Š” ์ด๋ฒˆ ์กฐ์น˜๋ฅผ ๊ด€ํ†ตํ•˜๋Š” ํ•ต์‹ฌ ํ‚ค์›Œ๋“œ๋กœ โ€˜๊ธด๊ธ‰์„ฑโ€™์„ ๊ผฝ์•˜๋‹ค. ๊ทธ๋Š” โ€œ๊ธฐ๊ฐ„ ์—ฐ์žฅ์€ ๊ธฐ๋Œ€์น˜๋ฅผ ๋‚ฎ์ถ˜ ๊ฒƒ์ด ์•„๋‹ˆ๋ผ, ์˜คํžˆ๋ ค ๊ธฐ์ค€์„ ๋ถ„๋ช…ํžˆ ํ•œ ๊ฒƒโ€์ด๋ผ๋ฉฐ โ€œ๊ธฐ์—…์€ ์ด์ œ ๋งค์šฐ ์งง์€ ๊ธฐ๊ฐ„ ์•ˆ์— ์ด์ „์ด ์‹ค์ œ๋กœ ์ง„์ „๋˜๊ณ  ์žˆ๋Š”์ง€, ์•„๋‹ˆ๋ฉด ์—ฌ์ „ํžˆ ์œ„ํ—˜์— ๋…ธ์ถœ๋ผ ์žˆ๋Š”์ง€๋ฅผ ๋ณด์—ฌ์ค˜์•ผ ํ•˜๋Š” ์ƒํ™ฉโ€์ด๋ผ๊ณ  ๋ถ„์„ํ–ˆ๋‹ค. ์ด์–ด โ€œ์„ ์ œ์ ์œผ๋กœ ๋Œ€์‘ํ•˜๋Š” ๊ธฐ์—…์€ ์ด๋ฅผ ์ผ์ •๊ณผ ์ฑ…์ž„์ž, ์˜ˆ์‚ฐ์ด ๋ช…ํ™•ํ•œ ์‹คํ–‰ ํ”„๋กœ๊ทธ๋žจ์œผ๋กœ ์ „ํ™˜ํ•˜๊ณ  ์žˆ์ง€๋งŒ, ๊ทธ๋ ‡์ง€ ์•Š์€ ๊ธฐ์—…์€ SAP๋ฟ ์•„๋‹ˆ๋ผ, ์•„์ง ์‹œ๊ฐ„์ด ์žˆ์—ˆ์„ ๋•Œ ์™œ ์œ„ํ—˜์„ ํ•ด์†Œํ•˜์ง€ ์•Š์•˜๋А๋ƒ๊ณ  ๋ฌป๋Š” ๋‚ด๋ถ€ ์ดํ•ด๊ด€๊ณ„์ž๋“ค์˜ ๋ฌธ์ œ ์ œ๊ธฐ์— ์ง๋ฉดํ•  ์ˆ˜ ์žˆ๋‹คโ€๋ผ๊ณ  ์ง€์ ํ–ˆ๋‹ค.
dl-ciokorea@foundryco.com

SAP tosses some Compatibility Pack users a (short) lifeline

8 January 2026 at 06:57

SAP is throwing a lifeline to customers who are running late on their transition away from S/4HANA Compatibility Packs in their data centers. Although usage rights were set to expire on December 31, 2025 for most users, SAP has announced a โ€œfinalโ€ five-month transition period for customers still using them to move to native capabilities.

Compatibility Packs were introduced in 2015 to allow customers shifting to S/4HANA on premises to retain functionality from their legacy SAP ECC (ERP Central Component) that was either not in the initial release of S/4HANA or that would have taken time to migrate. According to SAP, the missing functionality was delivered in the 2023 release of S/4HANA, and it said in a 2022 blog post, updated in 2025, that given this, Compatibility Pack usage rights, and support for them, would expire at the end of 2025 unless the customer had signed a Rise with SAP or SAP Cloud ERP deal and was making the move to the cloud.

[ Related: More SAP news and analysis ]

But a number of customers needed extra time to complete their migrations, prompting the company to offer an additional extension until the end of May 2026, a SAP spokesperson said in an email. The company will also offer what it calls โ€œtailored programsโ€ to these customers to expedite the move to the cloud products that replace Compatibility Pack functions.

โ€œWeโ€™re offering programs like transformation incentives and cloud extension policies, along with hands-on support from enterprise architects, AI-powered tools, and best-practice guidance for public cloud migrations,โ€ the spokesperson sajd. โ€œWe also provide dedicated services to identify which compatibility pack functions a customer is using and help replace or migrate them to the recommended cloud solutions, ensuring a smooth transition without disrupting business operations.โ€

No reprieve for laggards

However, the extra five months are only being offered to customers who have already begun their transition. โ€œWe recently discovered that there are customers who have not even started. โ€ฆ Nothing has changed about their post-deadline options,โ€ the spokesperson noted.

Analysts agree that the extension makes sense, though they see the move in different ways.

โ€œSAP has a multitude of customers in the process of migrating from ECC/R3 to S/4 HANA, and those customers are still leveraging the functionality provided by various Compatibility Packs,โ€ said Scott Bickley, advisory fellow at Info-Tech Research Group. โ€œIt would be quite the rug-pull for SAP to arbitrarily cut off support and use rights for these customers, resulting in potentially catastrophic disruptions to their internal and customer-facing business processes.โ€

And Gartner VP Analyst Mike Tucciarone views it as a purely practical move by SAP that โ€œreflects the real-world hurdles organizations are facing today.โ€ Gartner data shows that these compatibility pack issues came up in less than 1% of the thousands of SAP client calls analysts had in 2025, he said, โ€œbut for that 1%, itโ€™s a serious issue. This extension acknowledges that these migrations are a big lift, especially when organizations today are focused on driving efficiencies and cost optimization.โ€

However, it shouldnโ€™t be viewed as a policy change, said Sanchit Vir Gogia, chief analyst at Greyhound Research. โ€œItโ€™s a tightly framed grace period for customers who have already started their remediation journeys. Thatโ€™s it,โ€ he said. โ€œSAP has chosen a path that appears flexible but is actually highly selective. This is a transition period, not a reprieve.โ€

Temporary scaffolding

SAP is using a calculated delay to manage customer pushback without compromising its long-term roadmap, he said. โ€œThe short duration of the extension makes that crystal clear. Five months is not about changing course. Itโ€™s about giving those in motion a chance to land safely, while reinforcing the message that Compatibility Packs were always temporary scaffolding.โ€

Gogia is also seeing CIOs waking up to the fact their organizations are still at risk, despite believing they had successfully completed their transitions. โ€œMany assumed they were in the clear post-migration, only to discover Compatibility Pack elements still quietly active, sometimes flagged during internal readiness checks, sometimes triggered by SAP licensing audits, and occasionally revealed only during upgrade planning,โ€ he said. โ€œThe risk here isnโ€™t just technical. Itโ€™s financial, operational, and reputational. Once support ends, thereโ€™s nowhere to hide. SAP has even left the door open to technically disabling CP functionality in future S/4 releases, which would push this from compliance risk into outright business disruption.โ€

Bickley, too, sees compliance issues. โ€œUnder the existing 2025 expiration date, companies still using the Compatibility Packs would technically be non-compliant with their software use rights with SAP,โ€ he pointed out. โ€œThis extension provides relief for this subset of customers as they work with SAP to migrate away from these solutions.โ€

One theme is consistent, said Gogia: urgency. โ€œThe extension didnโ€™t lower expectations, it clarified them. Enterprises now have a very short path to demonstrate either progress or exposure. The smart ones are turning this into a structured program with timelines, ownership, and budget. The ones that donโ€™t risk being caught flat-footed, not just by SAP, but by their own stakeholders asking why the risk wasnโ€™t addressed when they still had time.โ€

More SAP news:

Epicor sets timeline to sunset on-prem ERP as cloud becomes the only path forward

7 January 2026 at 21:35

Reflecting the continued push by ERP vendors to the cloud, Epicor has announced its schedule to sunset several of its legacy on-premises tools.

The company will roll out final releases for Epicor Kinetic, Epicor Prophet 21, and Epicor BisTrack, and will offer tiered support levels in a phased schedule beginning later this year.

Epicor says this will allow enterprises to take advantage of tools exclusive to Epicor Cloud without having to maintain infrastructure. But the move will present challenges for some organizations, particularly those in highly regulated and data-sensitive industries, analysts point out.ย 

โ€œThese organizations shouldnโ€™t just see this change as a hosting decision shift; it signals a long-term operating model change,โ€ noted Manish Jain, a principal research director at Info-Tech Research Group. Itโ€™s not customers choosing the cloud, he said, โ€œItโ€™s about vendors taking alternatives off the table.โ€

Not an overnight shift, but a fundamental one

With this move, customers will have quicker access to new features and AI-powered capabilities, such as the first ERP AI agent with outcomes-based pricing, as well as a โ€œa modern, resilient platformโ€ that reduces IT burden and operational risk, Epicor said.

Customers using on-premises versions of Kinetic, Prophet 21, and BisTrack will continue to receive support, the company noted, but final releases will roll out between 2026 and 2028, based on platform. Enterprises will then transition into โ€˜active supportโ€™ until 2029 at the latest, and โ€˜sustaining supportโ€™ will begin as early as 2027.

More than 20,000 businesses run on Epicor Cloud. Generally, Epicor Kinetic is used by mid-market and upper mid-market manufacturers, such as discrete manufacturers with complex production, supply chain, and shop-floor requirements, explained Robert Kramer, VP and principal analyst at Moor Insights & Strategy.

Wholesale and industrial distributors who require strong inventory management, pricing, and order fulfillment steer toward Prophet 21, while BisTrack is popular among building materials, lumber, and construction supply distribution sectors, he explained.

โ€œEpicor is not turning off on-premises systems overnight,โ€ Kramer emphasized, but all new capabilities, platform improvements, and long-term roadmap investments will be cloud-only.

The Epicor sunset timeline is as follows:

Kinetic

  • Final on-premises release tentatively scheduled for January 2028
  • Active support, which provides full access to Epicor phone support, security updates, new issue investigation, and more, will be offered through December 31, 2029
  • Sustaining support, which offers limited phone support, access to the latest release (but not to new modules), and an online knowledge base, begins January 1, 2030

Prophet 21

  • Final on-premises release tentatively scheduled for May 2028
  • Active support through June 30, 2029
  • Sustaining support beginning July 1, 2029

BisTrack

  • Final on-premises BisTrack Web Browser & API release tentatively scheduled for July 2028
  • Active support for on-premises BisTrack Web Browser & API through June 30, 2029
  • Sustaining support for on-premises BisTrack Web Browser & API release beginning July 1, 2029

BisTrack Desktop

  • Final on-premises release tentatively scheduled for December 2026
  • Active support through December 31, 2028
  • Sustaining support beginning January 1, 2029

BisTrack UK 3.9 (2017)

  • Active support through December 31, 2026
  • Sustaining support beginning January 1, 2027

New possibilities, different risks

This move will benefit customers looking to modernize and take advantage of the ERP systems of tomorrow: agentic AI and event-driven, noted Moorโ€™s Kramer. Benefits will include simpler infrastructure, more predictable upgrades, and access to new capabilities without the need to manage servers, databases, or patches, or to cycle through time and resource-intensive upgrades.

โ€œStaying on-prem becomes a supportable maintenance decision, not a growth one,โ€ said Kramer.

Organizations will gain the freedom to innovate and โ€œdynamically match costsโ€ with revenue through unit economics, noted Info-Techโ€™s Jain. โ€œThis move will be projected as one that favors organizations prioritizing speed, scalability, and reduced infrastructure management, especially those with limited IT capacity to maintain ERP environments at production-grade reliability.โ€

For businesses with continuous operations, tight schedules, or requiring limited downtime, operational risk moves from internal IT to the vendorโ€™s architecture, SLAs, and incident response, he explained.

Going forward, enterprises must plan for vendor-led upgrade cycles, tighter dependency on release roadmaps, and reduced control over infrastructure, he said. Cloud ERPs (whether Epicor, Microsoft, or SAP) donโ€™t eliminate risk; they reshape it. Companies trade on-prem localized failures for platform-wide dependencies that can halt entire value chains if resilience and governance arenโ€™t engineered deliberately.

โ€œFor organizations that rely on these solutions, the strategic shift is from deployment flexibility to dependency management, and many CIOs arenโ€™t fully resourcing that transition,โ€ said Jain.

Highly-regulated sectors wonโ€™t be excluded, he noted. Rather, they will be forced to adopt and combine cloud ERP cores with stricter data controls, residency requirements, and compensating governance mechanisms. Or, if they require strict data sovereignty, they may need to shift to sovereign clouds.

โ€œGoing forward, regulated industries arenโ€™t cloud-blocked; theyโ€™re architecture blocked,โ€ Jain emphasized. โ€œAs on-prem options disappear from the ERP space, compliance becomes an engineering challenge.โ€

The cloud is the future, and all enterprises must adapt

Across the board, ERP vendors, and most SaaS providers, have been converging on cloud-first models.

This helps them โ€œaccelerate innovation, standardize platforms, embed AI capabilities, and, most importantly, sustain recurring revenue,โ€ Jain pointed out. ERP companies have considered on-premises architectures as roadblocks in achieving these objectives.

Concentrating development in the cloud has become the primary way vendors deliver continuous updates, embed AI integrated analytics, and provide security at scale without โ€œforcing disruptive upgrade projects every few years,โ€ said Kramer.

โ€œMaintaining parallel on-prem and cloud platforms slows innovation and increases cost, which is why vendors are trying to draw a clearer line now,โ€ he said.

The move will allow Epicor to focus engineering, security, and innovation on a single deployment model instead of โ€œfragmenting effort across cloud and on-prem versions,โ€ he said.

Customers do give up some control and accept dependencies on a centralized service. Cloud platforms are resilient, Kramer emphasized, but outages are no longer local events that customers can mitigate with internal failover or workarounds.

For regulated or sensitive industries that canโ€™t fully pivot to public cloud, โ€œthis does not mean an immediate cliff, but it does narrow long-term options,โ€ he pointed out. Hybrid, private cloud, and sovereign deployments will become the middle ground, but they come with their own challenges, requiring more deliberate planning, stronger governance, and clearer accountability.

โ€œOver time, even highly regulated organizations will be pushed to modernize how they consume ERP,โ€ Kramer noted. โ€œNot because on-prem stops working, but because it gradually stops evolving in ways that support new business and regulatory demands.โ€

โŒ
โŒ