SAP question

[threaded]

I've been asked to manage a large SAP project by a client. I could really do with some pointers, some buzz words so I can bullsh1t my first few meetings with my staff until I get up to speed.

I was thinking of asking everyone to give me a report on what they're doing, then I'll chop the odd attractive paragraph from them, mix 'em up, and post to bods in other teams, judge the reactions and basically home in on what are sensible things to say in meetings.

Thoughts, comments, miscellaneous personal abuse...

[The Lone Gunman]

Google dear boy google, like you do for the rest of your bulltulip (ahem allegedly)

[eternalnomad]

I've been asked to manage a large SAP project by a client. I could really do with some pointers, some buzz words so I can bullsh1t my first few meetings with my staff until I get up to speed.

I was thinking of asking everyone to give me a report on what they're doing, then I'll chop the odd attractive paragraph from them, mix 'em up, and post to bods in other teams, judge the reactions and basically home in on what are sensible things to say in meetings.

Thoughts, comments, miscellaneous personal abuse...

threaded, are you managing the overall project (i.e the business implementation elements), the "technical implementation" (i..e the overall IT implementation) or specific technical parts of the project (e.g. ABAP developments) ?

[threaded]

I appear to have quite a bit of everything, I have people in expensive suits all the way through to a bunch of Indian abap programmers.

[Antman]

Just out of interest, how do you get a gig like that?

[EternalOptimist]

tell em your aim is to 'optimize back-end niches'

[Antman]

sounds a bit gay but in this game you never know

[SAPBoy]

Do you know how SAP projects work?

Have you ever worked on a SAP implementation before? What is the area of business? Is it just R/3 or APO, CRM, EBP etc.

[eternalnomad]

I appear to have quite a bit of everything, I have people in expensive suits all the way through to a bunch of Indian abap programmers.

Sounds like a rather challenging role but one where luckily for you basic project and people management skills are going to be important rather than specific SAP configuration or technical skills - cos that is what you are paying the other ferkers to know.

In the role you are doing I would suggest as a "starter for 10" following key things in a SAP project (yes I know they can be applied to many implementations but trust me if you get them wrong with a SAP implementation you will be ferked):-

1) Landscape design - make sure you have a system landscape that can support the business and project requirements i.e. the release management needs. SAP landscapes are now more complex than they have ever been and its quite amusing to see project having "forgotten" about certain key components.

2) Your client strategy (not the PC client software but the MANDANT (buzzword) clients in each SAP system) needs to be well thought through - is allied with the landscape strategy and is a wonderful buzzword to use to make you sound like you have worked with SAP before. You should also ensure that all you non-dev instances (buzzword) are locked down against changes.

3) Release management via the TRANSPORT (buzzword) system and promote to production paths - get this wrong and your prod. system will get out of sync from you dev system then you are ferked.

4) Integration and interfacing strategy. Will you use traditional flat file, IDOC (buzzword), RFC (buzzword) over ALE(buzzword), XML or newer XI (buzzword) integrations or a combination thereof. (or even MS Biztalk if you really want to make life difficult for yourself)

5) Development changes (this includes ABAP (buzzword) programs and configuration elements (buzzword)) are stored in TRANSPORTS (buzzword) which are basically moved through the "landscape" by the BASIS (buzzword) or release management team.

6) Get to know the common SAP module name acronyms as people will say "I have x year YY knowledge" where YY is could be for example..(google for the rest as there are loads)...

FI - Finance and accounting
CO - Controlling (usually linked closely with FI)
PP - Production planning
PM - plant manintenance
MM - materials management
SD- sales and distribution
ABAP - sap programming language a bit like cobol
BASIS - all the truly "technical stuff" like database, operating systems, networking, desktop, performance management & tuning, integration

If you happen to need a person with >10 years SAP implementation knowledge specialising in SAP systems, landscape and infrastructure architecture, BASIS, technical project management, release management etc then I may just know a chap who could be interested for the right sort of deal


p.s. Dont worry about not knowing any ABAP - your whole injun ABAP team wont know it either

If you need more help or info then send me a PM

[SAPBoy]

Business driven

I agree totally with the previous post but the other thing you have to consider is that SAP implementations are supposed to be (have to be if it's to work) business driven. Generally the teams will be split by function - Finance, logistics, sales etc. There will also be teams for tecnical - Basis, developments etc. The functional team needs to be made up of SAP consultants (identified by their blue shirts and cufflinks) and business people. The business people have to be the ones who really understand how their business currently works and how it should work in the future. The key is to get consultants who know what they're doing and business people who believe in the future processes, otherwise they'll try to sneak back to their day jobs.

If you want a basic roadmap for project stages then PM me.