Many times a person or company can do a thousand things right but it is the one thing out of the thousands that went wrong that gets the attention. Apple, BMW, Amazon, Burger King, Walmart, Coca Cola, PepsiCo,3M, Home Depot, Ford Motors, Samsung Electronics, Harley Davidson,The United States Army, The United States Navy, all use SAP. Yes SAP is a complex system but when you are running incredibly complex multi-billion dollar companies or operations you need an ERP system that can handle the gambit of highly complex transactions that will flow through that system for real time management reporting. No other ERP system presently available can meet the future 500 requirements like SAP can.

I m working with S/4 HANA SAP H2R AND IT GIVES GOOD UNDERSTANDING

It’s too complex and too rigid once deployed. It’s massively over engineered for most companies.

@danawhiteisagenius8654

11 ай бұрын

Sounds like ServiceNow

@fredyuldashev

11 ай бұрын

because its a good fit large and complex company structures

@richardhoulton4016

11 ай бұрын

@@fredyuldashev Maybe, but you have to be careful how you deploy it, and you can overcomplicate the data structures to the point where they become unintelligible, and it can become very difficult to change business models and be “agile” because of the complexity…and agility is desirable these days. Rigidity has its pros but also its cons.

@Efilenow

11 ай бұрын

Projects also fail because the client's Subject Matter Experts are useless.

@richardhoulton4016

11 ай бұрын

@@Efilenow Also agree…but half the time they don’t know what they don’t know and need facilitated guidance

Any proofs? It looks like a commercial to gain business for your company as the one who can guarantee success with a risky approach. I agree planning, good planning is a must.

With my knowledge of SAP and domain expertise, I can few reason are 1) functional team in client still think transformation is technical and their process will remain same. Which cannot be the case. 2) Normally expectation are no disruption in business process, which again will lead to deviation and complexity, 3) Business team think onborading a vendor with expertise will solve all problem, but case should be business need professionals l,who have both core skills and SAP skill to guide business and vendor. Great insight sir...thanks

@terarows3

11 ай бұрын

Is it reasonable for businesses to spend money to "upgrade" ERP software that disrupts their business processes?

Is there any specific change between ECC and HANA? I've been using ECC for 3 to 4 years. I never used HANA

Thanks again for the interesting thoughts. There would be a lot to say about SAP and S/4HANA. 1) The product has maintained its historical limits by creating a complex system that is also very complicated. More complicated than ECC already was. 2) SAP's commercial policy is very invasive and the ecosystem is a cage that does not make customers or partners happy. It is clear that in this way it is very unlikely to be able to manage the complexity. 3) It has always been difficult for SAP client companies to own their own SAP project (as it would be obvious and legitimate). Creating internal resources is too expensive and carries additional risks. 4) Expectations: by adopting SAP you must be aware that you are acquiring a really solid backend system. This is also the reason why many customers prefer to stay on ECC: the "solid" part already works well and they already know that the other promises will not be kept.

@AllenBoxingClub

11 ай бұрын

But with SAP Rise helping companies get to S/4 HANA in the cloud it should be almost fool proof when and always best practices are adhered.

@beppino21

11 ай бұрын

@@AllenBoxingClub The problem is precisely this: are the best practices credible? ASAP, RRR, RDS and now RISE, are some of the acronyms with which SAP tries to reassure the customer. Useful material during the sale. Under various names, SAP partners have always proposed and sold some sort of preconfigured, also because it is the only thing of them that the partners can sell. But the presets never really worked. From the mid-90s to the early 2000s, to manage their project, many customers found themselves creating and having to manage a SAP consulting company. Consulting firm subordinated to the SAP supplier. Not a big business but rather a very expensive franchise! Today this model is somewhat finished for very good reasons that I will not describe in detail. Today, as always, SAP is credible as a backend but not as a solution capable of responding quickly to the needs of companies that have to continuously change their business model and organization. The reasons are both technical and organizational of the SAP partner network. However good SAP if it still finds customers who agree to work as SAP requires and also manages to get paid a lot of money. It's good for me that I've always worked to fix badly done projects: doing and undoing is always work!

I am learning SAP FICO is it good job or any other finance module is better to continue career in as a accounts.... Kindly share your experience... Thankyou in advance

In one case we had a S4 implementation that had to be restarted twice at great cost.

The Lidl implementation failure was because Lidl sorts their inventory management based on the purchase price, whereas S/4 HANA would sort by the retail price. Sorting my retail price is the standard best practices. In addition, there was a major executive reorganization within the company while the implementation was going on. This has nothing to do with the quality of S/4 Hana but poor management decisions and poor business practices. In regards to National Grid: The integrator Wipro: As Wipro knew or should have known, it had neither the ability nor intent to assign appropriately experienced and skilled consultants to the Project because... it in fact had virtually no experience implementing an SAP platform for a U.S.-regulated utility. - National Grid USA They had to bring in Deloitte and E&Y to fix the mess. It wasn’t the quality of the system but the quality of the consultants that caused the failure.

@terarows3

11 ай бұрын

Regarding the comment on Lidl, the mindset that users must comply with the ERP software's so-called "standard" instead of the other way around is to me arrogant. About National Grid, the fact is that the ready-made ERP applications that meet most of utilities companies' requirements just do not exist. They only way to successful ERP implementation for companies in this sector is writing almost all new applications on an ERP framework from ground up. The real reason National Grid failed was that the company chose the wrong, complex and extremely unproductive ERP framework that the company had to spend unreasonable sums of money hiring a huge army of programmers over the years to create tons of apps in ABAP roughly in the the same era of COBAL.

I don’t agree with many of your observations regarding S/4 Hana cancellations. The major issue why companies are running into issues is because they don’t want to pay the hourly rates to hire top talent. They want to save on costs so they will hire a consultant that will accept $50 or $60 per hour but that consultant only looks good on paper. I see post where a consultant is on a project and will be asking for complete configuration guidance because they have no idea what they are doing. I have see consultants asking what is a cost element which is elementary. I have watched several of your posts and you don’t appear to be an advocate of SAP. I worked with Siemens on a project moving from oracle ERP to SAP because Oracle could not handle the complex manufacturing this company was doing. SAP is a very good system but if companies are going to nickel and dime the expert consultants they are going to get what they pay for.

@terarows3

11 ай бұрын

Why do businesses like Lidl and National Grid hire expensive consultants to write extensive programs from scratch on complex ERP frameworks that few people really fully understand? Why can't the IT staff of large enterprises do the implementation? Is it their incompetence or the ERP software is too complicated? Who exactly is responsible for the ongoing maintenance of these ERP applications after the contract ends? Don't the top managers of large organizations who hire external so-called "experts" to direct their IT staff look down on their own IT staff?

@siddheshghag9107

11 ай бұрын

Hi , I have just completed learning SAP FICO S4hana Global certification...Any ideas which company should I lead upto as an Fresher role ???

@sandyj342

10 ай бұрын

@@terarows3 ERPs like SAP are the next Mainframes. In an era of on demand computing and cost pressures. These Fortune 500s will be in line for bailouts or bankruptcy.

jeezus

I think erpnext is way better than sap

S/4HANA Is not as mature as ECC? One word - Integration. Here's why companies are failing and cancelling projects: Resource quality. You can throw bodies into a production environment who know how to configure SAP. They are making a living off the talents of consultants 20 years ago. Allot of offshore companies have made big bucks in the $50 an hour game. S/4 projects require industry knowledge, business function fluency SAP architecture / config skills / PM expertise. Can't find that offshore. Ask the next FI consultant you meet if he was ever an accountant. HANA requires the caliber of skills typical on a projects back in 2000. Truly enjoy the comment about putting a project on hold, as if you can pick it back up in 6 months. It's all about the people.

@terarows3

11 ай бұрын

I'm almost certain that anyone trying to implement on National Grid's ERP system would have to write an entirely new application from scratch, because no ready-made "standard" applications exists for this industry. What State Grid should do instead is to choose a high-productivity ERP framework such as a low-code ERP framework. In this case, the accounting module is only the smallest part of the overall applications.

Who are you brother ?? .. do u have sap experience??

@murugeshdm5945

11 ай бұрын

Please share your experience