2
WWW.TITANCONSULTING.NET 972.377.3500 C O N S U L T I N G INSIGHTS JUNE 2017 THE THREE BIGGEST PROBLEMS WITH SAP! And How Titan Consulting Solves Them! What are your biggest challenges with SAP? We have listened to our clients complain about their SAP problems, and the biggest ones fall into these three categories: 1. User Experience, 2. To Avoid Brain-Drain, You Need Connuous Training, 3. Sustainment and Evoluon (Care and Feeding). Yes, there are many other topics we could list such as Applicaon Development and Customizaon, Lack of Flexibility, System Maintenance and Security Patches, etc. But these three are menoned the most frequently. User Experience: SAP’s GUI has prey much stayed the same since its incepon of the R/3 plaorm in 1992. There were some enhancements with Enjoy SAP in the 1996 meframe. But the GUI has changed lile which includes fields and screen sequencing. And users sll complain about it! With the introducon of Fiori, many expected this UI to break through these obstacles and enhance the user experience. Fiori does improve the experience for task oriented requirements, but lacks in the flexibility of how it handles mulple task within the enre business process. One of our clients, a Manufacturing Company, has a division they have wanted to convert to SAP for many years. The biggest pushback was that these users had homegrown screens and when they saw the GUI, they resisted the change. The legacy system could sll support the business, therefore, it was alright to run two systems. But as new requirements and acquisions occurred, it was obvious the legacy system could not connue to run the business: the roadmap to SAP was set. When we met with the project team from the division on the legacy system, they were thrilled that we could build a UI5 front-end and layout the screens to reflect how they worked. IT was happy because they could jusfy the migraon to SAP and take advantage of the expanded system improvements: a win-win for business and IT. To Avoid Brain-Drain, You Need Connuous Training: I recently heard an interesng stasc, the average age of IT professionals supporng SAP is over 50 years old. This will create a knowledge vacuum in a few years as these employees move towards rerement. How are you addressing your SAP Knowledge Workers (KWs)? And if you implemented SAP more than five years ago, you already are experiencing the brain-drain of your workforce. The math and reality according to KWs: KWs retain 80% of what they learn! Each successive generaon of KWs retain 80%. Each generaon is three years, the average me a resource is in a role. Conclusion: aſter 5-6 years into your SAP journey, your SAP KWs may understand 50%-65% of ‘what’ and ‘why’ you implemented this funconality – interesng stasc! The resulng acvies for users and super users drives inefficient behavior in the form of workarounds, code-on-code fixes, misinterpretaons of best pracces, and other decisions that drive-up the cost of ownership.

THE THREE BIGGEST PROBLEMS WITH SAP! And How … common request is for training on the SAP Report Writer/Painter. The finance team for an electronics company ... or UI5 for Approvals

Embed Size (px)

Citation preview

Page 1: THE THREE BIGGEST PROBLEMS WITH SAP! And How … common request is for training on the SAP Report Writer/Painter. The finance team for an electronics company ... or UI5 for Approvals

WWW.T I TANCONSULT ING .NET972 .377 .3500

WWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NET

C O N S U L T I N G

INS IGHTS JUNE 2017

THE THREE BIGGEST PROBLEMS WITH SAP!And How Titan Consulting Solves Them!

What are your biggest challenges with SAP? We have listened to our clients complain about their SAP problems, and the biggest ones fall into these three categories:

1. User Experience, 2. ToAvoidBrain-Drain,YouNeedContinuousTraining, 3. SustainmentandEvolution(CareandFeeding).

Yes, there are many other topics we could list such as ApplicationDevelopmentandCustomization,LackofFlexibility,System Maintenance and Security Patches, etc. But these three arementionedthemostfrequently.

User Experience:SAP’sGUIhasprettymuchstayedthesamesinceitsinceptionoftheR/3platformin1992.ThereweresomeenhancementswithEnjoySAPinthe1996timeframe.ButtheGUIhaschangedlittlewhichincludesfieldsandscreensequencing.

And users still complain about it!

WiththeintroductionofFiori,manyexpectedthisUItobreakthrough these obstacles and enhance the user experience. Fioridoesimprovetheexperiencefortaskorientedrequirements,butlacksintheflexibilityofhowithandlesmultipletaskwithintheentirebusinessprocess.

One of our clients, a Manufacturing Company, has a division they have wanted to convert to SAP for many years. The biggest pushbackwasthattheseusershadhomegrownscreensandwhen they saw the GUI, they resisted the change.

Thelegacysystemcouldstillsupportthebusiness,therefore, itwasalrighttoruntwosystems.Butasnewrequirements

andacquisitionsoccurred,itwasobviousthelegacysystemcouldnotcontinuetorunthebusiness:theroadmaptoSAPwas set.

When we met with the project team from the division on the legacy system, they were thrilled that we could build a UI5 front-endandlayoutthescreenstoreflecthowtheyworked. ITwashappybecausetheycouldjustifythemigrationtoSAPandtakeadvantageoftheexpandedsystemimprovements: a win-win for business and IT.

To Avoid Brain-Drain, You Need Continuous Training:Irecentlyheardaninterestingstatistic,theaverageageofITprofessionalssupportingSAPisover50yearsold.Thiswillcreateaknowledgevacuuminafewyearsastheseemployeesmovetowardsretirement.

HowareyouaddressingyourSAPKnowledgeWorkers(KWs)?AndifyouimplementedSAPmorethanfiveyearsago,youalreadyareexperiencingthebrain-drainofyourworkforce.

The math and reality according to KWs: • KWsretain80%ofwhattheylearn! • EachsuccessivegenerationofKWsretain80%. • Eachgenerationisthreeyears,theaveragetimea resource is in a role. • Conclusion:after5-6yearsintoyourSAPjourney,your SAPKWsmayunderstand50%-65%of‘what’and‘why’ youimplementedthisfunctionality–interesting statistic!

Theresultingactivitiesforusersandsuperusersdrivesinefficientbehaviorintheformofworkarounds,code-on-codefixes,misinterpretationsofbestpractices,andotherdecisionsthat drive-up the cost of ownership.

Page 2: THE THREE BIGGEST PROBLEMS WITH SAP! And How … common request is for training on the SAP Report Writer/Painter. The finance team for an electronics company ... or UI5 for Approvals

C O N S U L T I N G

WWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NETWWW.T I TANCONSULT ING .NET

WWW.T I TANCONSULT ING .NET

A prime example, while advising a client on their Accounts Payable processes, is they wanted to build a separate system totracksomecelebrityassets.Therequirementwastoensure paying royalty payments and contractual agreements on-time.

Ratherthanbuildingthisseparateapplication,wepointedout that SAP has this capability to set up PO’s and recurring invoiceprocessingthattracktheserequirementsandpaycelebritiesaccordingtolicenseterms.AfterareviewoftheoriginalBPML,wenoticedthatthisrequirementwasonthelist, but dropped from the scope.

AnothercommonrequestisfortrainingontheSAPReportWriter/Painter.Thefinanceteamforanelectronicscompanyhad problems with the month-end close. The volume of spreadsheets was piling up. The controller needed help and thoughtthetrainingwouldreducethetimetoclose.

We reviewed the case, and many of the reports they needed were either available or close to the format they needed. Thisfindingputaspotlightonthebrain-drainthatoccurredaftermanyyearsofperformingrecurringtasksandnotinvestingintheirknowledgeworkers.

Wherecanyoustart?Lookforwhereyouhaveabuild-upofspreadsheetsandmanualworkaroundsandseeifthereareSAPprocessesthatcouldeliminatetheseinefficientpractices.

Sustainment and Evolution (Care and Feeding):HowdoyoukeepevolvingyourERPsystems?Shouldwefollow an agile or waterfall methodology?

Agile projects are the rave in PMO circles. Agile is the way togetfunctionalityfastertousers;quicklyandefficiently.

Unfortunately,agiledoesn’talwaysworkintheSAPworld.Wheredoesitworkandwheredoesitnotwork?Wecould

probablywriteafullarticleorbookonthemanymethods and approaches for this.

We have found success with the agile approach for point solutionssuchasnewreportcubesforSalesAnalytics.Or,rollingoutsinglemobileapplicationfunctiononeitherFiori orUI5forApprovalsoftimeorvendorinvoices.

Thescopeoftheworkfocusedonasmallgroupofusers,andtheriskislimited.Wefoundapilotapproachfollowingagilemethodsworkedeffectivelyinthissituation.

Agileapproachfailswhenyouhavecross-functionalrequirements,impactorrisk.OneofourclientswasrollingoutSAPtoaplanttheyacquired.Therolloutaffectedenterprisedata,pricing,customers,materials,andvaluationarea.

Thetraditionalwaterfallmethodworksbestforscenarioswithintegratedrequirements,andallrequirementsneedtoworktogether. The plant rollout is a perfect example due to the needforeachsubsequentsteporphasehavingadependencyon the prior phase.

WehaveworkedwithourclientstodemonstratehowbothmethodscancoexistinthePMO.Havingtheflexibilitytodeliver in both the waterfall, agile or lean method can save youtime,moneyandimproveyourSLA’swithyourinternaland external customers.

WithasystemthesizeandcomplexityofSAP,therearemanyother problems that may challenge you. These are a few that we have solved for our clients.

TellusyourbiggestproblemswithSAPandlet’stalkabouthowwecansolvethemforyou?ContactKentLamb,[email protected],214.632.5621.;or,contactyourTitanConsultingDirector.YoucanseeadditionalinformationonourAdvisory Services page at www.titanconsulting.net.

Looking forward to seeing you at:

972 .377 .3500

ASUG Southwest Region Energy & Utilities Days 2017 July27-July28 CenterPoint Energy Houston, TX

ASUG Fall Focus Conference September19-September21 LoewsChicagoO’HareHotel Rosemont,IL