Hello All,

Most of the time we are in hurry and import mass transport requests in SAP server (through STMS_IMPORT) and unfortunately due to resource bottleneck , some TRs get hanged with IMPORT symbol. Though we wait for some hours with a hope , but it doesn't get through . So, in that scenario, you can check the following steps to get rid of that showstopper issue :-

You can check below option one by one and meanwhile you can check the TR queue status as all the steps are not mandatory to perform if any pre-step solves the issue ....

1. Delete the TR/ TRs (which are running with TRUCK symbol) from monitor (Press CTRL+ F8 in stms_import to check the list of TRs in monitor) .

2. Delete the TR entry through SE16N (in edit mode -> '&sap_edit' ) for all the TR/TRs from TRBAT, TRJOB, TMSTLOCKR tables.

3. Run RDDNEWPP report to schedule 'RDDIMPDP' job requires for TMS.

4. Terminate all the 'tp' processes running in OS.

5. Delete the TR line entries from <Target SID> file (open in notepad) available under /usr/sap/trans/buffer/.  .

6. Still if you have issue in TR queue then check the logs under STMS_IMPORT > GoTo > tp System Log . Some time it shows that \usr\sap\trans\tmpD:\usr\sap\trans\tmp\<............<SID>> file is being used .......... waiting for 1 min . if you also get that log then delete the mentioned file from the corresponding location and check.

I am sure after following above steps, issue mentioned in the header will surely get resolved.

Regards,

Nilutpal.

Thanks for the response for first two blogs.SAP SCN is a wonderful place to share thoughts

Let me Jump  directly to SAP Extended memory.It is one of the main places where user context is stored.

From the previous blog we know that SAP extended memory is a shared memory.  And it can be used to store the User context.

SAP Extended Memory

Since there are roll in roll outs for different sessions it is convenient to store the user context in Extended memory.

The text which is in bold is explained in the previous blog

What is the Size of the SAP Extended Memory?

The size of the SAP extended memory is allocated when SAP Instance is started up and is defined by em/initial_size_MB

Ztta/roll_extension defines the maximum size of a user context in an extended memory. You know why need this kind of a limit.

SAP Heap memory

The third memory Area where user context can be stored is SAP Heap Memory

Abab/heap_area_dia -SAP heap memory a dialog process can allocate

Abap/heap_area_nondia- SAP Heap memory a non dialogue process can allocate

Abap/heap_area_total-Total SAP Heap memory that can be allocated by all work processes.

Lets do a refresher course and see if all the terms makes sense

We want to look at how memory is allocated during a transaction step.

1.When a transaction starts  ztta/roll_first is allocated which is normally kept to 1 (byte) to reduce the usage of SAP Roll memory.

2.ztta/roll_extension - The remaining part of the user context is stored in Extended Memory up to the limit of this parameter

3.If the extension limit is exceeded the remainder is stored in ztta/roll_area

4.If the Context Continue to grow the work process will go to SAP Heap memory abap/heap_area_dia or non_dia is used depending upon the type of work process .This status is called PRIV mode.

This is a general approach and will vary upon the architecture and the type of operating system. For example in Unix non

Dialog work process uses more of heap memory than shared memory.

SAP EG Memory

As previously noted user context are stored in extended ,roll and heap memory.

However memory areas are required to hold data globally between user contexts.

It is defined by Parameter em/global_area_MB approximately equivalent to 10% of Extended Memory

SAP Paging Memory

It is completely different from Operating system Paging memory

A new user context is created when an ABAP Program calls another program or transaction. The variables are transferred when a new Program is called and is stored in Paging memory. Refer to part1 we have a similar situation like below.

Rdisp/PG_MAXFS

Rdisp/PG_SHM

Conclusion

My intention is to introduce some basic terms which is used on  a daily basis and explain it in a simple way. Hope it was useful .you can step on basics and try to read and understand the memory management .

It will be nice to conclude this way

1.Available memory =Physical memory + Swap Space

2.Virtual memory Required

1. ST02 ->Select Detailed Analysis ->Storage

+

2.abap/heap_area_total

+

3.100MB for OS

+

4.Any  Other Program running (memory Occupied)

The Virtual memory Required MUST less than Available  memory. This will be your starting point for memory tuning.

If this blog was useful and interesting please let me know.

The link to previous blogs

Part1

Part2

This blog gives an insight into SAP Memory management. The contents has mainly data from SAP Performance  optimisation guides, discussions in internet  and most importantly my experience in SAP World.  I tried not to do too much copy and paste (In this Internet world nobody can claim authority of their data  , correct???, So please tell me if it is reproduced from somewhere  else) The blog is my  point of view and any different opinions or approaches are welcome .Have fun!!

What is RAM and Virtual Memory?

When we discuss about memory  in a SAP Perspective , the first thing comes into my mind is Physical Main Memory (RAM). RAM Is physically available main memory .

Well, we have to consider  a bit more we call it virtual memory , The general rule of thumb is RAM and Virtual memory should be in a considerable ratio (I know it is very subjective ) What I mean to say is that there shouldnt be a huge difference . All the processes together cant have more memory than sum of RAM+ Available SWAP SPACE which is almost equal to Virtual Memory .

The conclusion is that you can consider more than RAM in your SAP system .

STOP Here you want o know what is Virtual memory available in your SAP system??

Transaction ST02, Click on storage as per the screenshot

Virtual memory is the sum of local memory and shared memory.

Local Memory?

Only one operating process can read or write from this memory.

Shared Memory ?

Shared memory can be accessed by multiple operating system process (In an SAP World shared memory of Work process can be accessed by a work process of the same instance)

We are talking terms  of 64bit technology. I am not sure about 32 bit architecture it has to do something about address space and the fragmentation which I conveniently ignore it here. Lets make it simple , most of the systems are 64bit and lets discuss from that perspective. Lets make conclusion here

RAM -Physically Available Main memory

Virtual Memory - More than RAM which can be used by all processes

Shared Memory - as it sounds , shared , SAP Buffers reside here

Local Memory- Local to a SAP Work process or Operating system work process

I stop here and get to SAP Terminology which will be based on these base concepts. Have a cup of Coffee Now.

This blog features "How to upgrade SAP Kernel from 700 to 720 (720_REL or 720_EXT)"

Upgrading SAP Kernel (Release Upgrade from 700 to 720) is pretty much straight forward, if you stick to and follow the Master SAP Note: 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11.

For the most part, the upgrade is pretty much similar to applying a Kernel patch without changing the Release, But I thought to rather write a blog post, to layout the epitome and crucial differences as compared to while applying a Kernel patch. And this being my first blog at SCN, so please bare with me in case you feel the blog is not up to the mark as it should be. And of course, I warmly welcome your feedback and suggestions.

So here is the basic overview of the system, before i shoot right into going about upgrading SAP Kernel.

Before beginning, I would like to break this blog in sections, in and around "Kernel 720" so as to get to know other things as well besides just the technical upgrade. I would be covering the following:

• SAP Kernel 720_REL vs 720_EXT? Which SAP Kernel Release 720 should I use?
• Benefits of using SAP Kernel 720?
• SAP Notes relevant for upgrading to SAP Kernel 720
• Upgrading the Kernel (You could just directly scroll down to this section, for Quick How to? )
• Follow-up Activities

SAP Kernel 720_REL vs 720_EXT? Which SAP Kernel Release 720 should I use?

The very first thing that you have to decide while upgrading the Kernel to 720 is, which 720 Kernel to be used? Kernel 720_REL or 720_EXT?

OK, so first let's try to figure out what are these two kernels, what are the differences and which one should be used?

Kernel 720_REL is the standard SAP Kernel, which is downward compatible with older versions of operating systems and database clients. Basically this SAP Kernel was compiled on older versions of OS Compilers and linked to older database client libraries.

Whereas, Kernel 720_EXT is the new extended kernel, which is released for recent OS releases and database clients. Also, it does not support older versions of operating system platforms.

For supported OS & DB releases for Kernel 720_EXT, please check the SAP Note 1553301 - 7.20 EXT Kernel - Usgae

If your platform meets the requirements for Kernel 720_EXT, it's recommended to go for 720_EXT rather than 720_REL.

For Linux, as my operating system RHEL 5 is not supported for SAP Kernel 720_EXT, I will rule out the usage of 720_EXT and hence my target SAP Kernel would be 720_REL. Of course, if I am very keen to use Kernel 720_EXT rather than 720_REL, I do need to upgrade my Operating System first to RHEL 6, which I think I would take it up some other time, but certainly not right now .

Supported Linux Versions for SAP Kernel 720_EXT are: Red Hat Linux 6, SuSE Linux 11 & Oracle Linux 6. Similarly you could check for your  corresponding operating system, and decide on which Kernel 720 type to be used.

Benefits of Using SAP Kernel 720

I won't talk about the mo-jo-jo of SAP Kernel 720, and how is it a game-changer over SAP Kernel 700.

To put simply, you should upgrade from SAP Kernel 700 to 720 because:

• The very obvious, Support of SAP Kernel 700 has ended on 31st August 2012 and now it is replaced by SAP Kernel 720
• Kernel 720 supports Rolling Kernel Switch - What it means for you is that, you can minimize the downtime of SAP system while applying Kernel Patches
• Kernel 720 has got Flexible License Generator - What it means for you is that, License is not linked to the hardware key anymore, thus allowing you to move your SAP systems to another hardware ensuring High Availability.
• Kernel 720 supports SAP GUI for HTML with Unified Rendering - What it means for you is that, you can access SAP System (ABAP per se) on a WEB Browser as a WEBGUI without the need for Installing SAP GUI.
• In Kernel 720, the security has been enhanced via Access Control Lists (ACLs) - What it means for you is that, you should be running SAP with enhanced security. Powerful thought!
• Kernel 720 provides optimized performance via profile based optimization on UNIX platforms.

SAP Notes relevant for upgrading to SAP Kernel 720

You would like to keep the following SAP Notes handy for the Kernel Upgrade:

• 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11
• 1629598 - SAP Kernel 720 will replace older kernel versions
• 1610716 - Correcting run-time objects with incorrect alignment
• 1563102 - Linux Requirements for 7.20 EXT and higher kernel (Alternatively, you can refer the below generic note for all OS)
• 1553301 - 7.20 EXT Kernel - Usage
• 1031096 - Installing Package SAPHOSTAGENT
• 19466 - Downloading SAP kernel patches

Upgrading the Kernel

Without any further delay, let's get straight to the business now:

Get a latest version of SAP Note 1636252, and perform steps applicable for your platform. Below are the steps that I have done specific to my platform.

For Java only systems, check the following:

1) For release 700, there is a incompatibility with jmon, which is eliminated with SAP Java Technology S Offline Component (SAPTECHF.SCA). For release 700,     SAP TECH S 700 OFFLINE SP14 PL24 is required:

   This is on Higher level.

2) For release 700, the tool JSPM must have at least SP 24:

Platform-Specific Checks:

1) Oracle Database: Oracle 10.1 is not supported with the SAP Kernel 7.20. Needs at least Oracle 10.2

2) Oracle Client Library: Oracle Instant Client 11g is required by SAP Kernel 720_EXT.

    This is not applicable for this case as Kernel is 720_REL

Download Required Components / Patches

Download the following from SAP Service Market Place:

• Latest SAPCAR Tool
• SAP Kernel 720_REL 64 BIT UNICODE Latest Patch (DB-INDEPENDENT & DB-SPECIFIC Kernel Files)
• SAP IGS 7.20 (If you have IGS installed, and your target Kernel would be 720_REL)
• SAP IGS Helper (SAP IGS Fonts and Textures, though an optional component, it is recommended to install if you are upgrading to Kernel 720_REL or 720_EXT.
• DBA Tools Package from the Kernel Download Path of DB Specific section
• SAPHOSTAGENT (The SAP OS Collector, onward's Release 7.20)

SAPCAR Tool =>

SAP KERNEL 720_REL 64 BIT UNICODE Latest Patch =>

SAP IGS 7.20 (Internet Graphics Server) =>

Check if IGS is installed (should be as a Software Component / Development Component)

DBA Tools Package for Oracle 10g and 11g =>

SAPHOSTAGENT (The SAP OS Collector onward's release 7.20) =>

Preparations

Stop the SAP System (No need to stop the Database)

Stop SAPOSCOL, assuming that your SAP system release is 700, SAPOSCOL is installed under SAP Kernel.

If the SAP Kernel is added to your path, you can directly execute below command:

Stop processes "SAPSTARTSRV"

Remove any IPC objects that may exist: cleanipc <Instance Number> remove

Install SAPHOSTAGENT

Now as the SAP OS Collector has been stopped, and IPC has been cleaned up, you can install SAPHOSTAGENT 720, which in turn will update SAPOSCOL and deploy under path /usr/sap/hostctrl/exe/

Extract SAPHOSTAGENT.SAR somewhere on a temporary directory (Note: You should use the latest download SAPCAR tool for extracting all the packages)

You should do the extraction using root, or ensure that the extracted contents belong to root ownership.

The extracted archive will contain saphostexec program

Start the installation of SAPHOSTAGENT as per below:

Subsequent to this, you will see that SAP OS Collector saposcol is now installed under /usr/sap/hostctrl/exe/ onward's Kernel 720

Install SAP Kernel 720

Well, the most awaited precious step has arrived now

But, you wouldn't be rushing up, without taking a backup of the current working Kernel before upgrade! Would You?

Take a backup of the existing Kernel 700, from the Global Kernel directory (/sapmnt/<SID>/exe/) and also of Local Instance Specific Kernel Directories (/usr/sap/<SID>/<Instance>/exe/)

Now, switch to directory /sapmnt/<SID>/exe/ with user <sid>adm

Save the following Files & Directories to another path to be used later:

1. Directory jvm or sapjvm* if it exists
2. File protect.lst if it exists
3. Files rfcexec, rfcexec.sec if it exists
4. ICU Libraries (*libicu*), if they exist.

Now, switch to user root and change the owner of all files/directories to <sid>adm as shown below:

Now, delete all the files from the kernel directory, including the sub-directories. This ensures  that there are no remaining files from the earlier release, which have different name in release 7.20 or are in a different place in a sub-directory.

Now extract the new Kernel (using the latest SAPCAR tool) in /sapmnt/<SID>/exe/ as shown below:

Extract the DBA Tools Package now, as shown below:

Extract IGS Packages now, as shown below:

Now, you need to restore the files to the current directory, which you saved earlier:

1. Directory jvm or sapjvm* if copied
2. File protect.lst if copied
3. Files rfcexec, rfcexec.sec if copied
4. ICU Libraries (*libicu*), if copied

To, deploy the optional IGSHELPER.SAR file, switch to the relevant local directory /usr/sap/<SID>/<INSTANCE> on every instance and execute the below command:

I think I have exceeded the max. no of images per blog post, as I cant upload any more images

I Guess, I will have to extend this to Part - II

Upgrading SAP Kernel from Release 700 to SAP Kernel 720_REL / 720_EXT Part II of II

In my previous blog, i have explained the procedure for configuring availability monitoring. This blog explains the way to do automatic alert configuration when the status of system goes down in the availability monitoring(system is down)

1.1  Pre-requisites for configuring auto reaction method

• Done in 000 client (Monitoring system)
• Create a User using T-Code SU01 and do the following configuration
• User must have a mail id
• In address tab Click the other communication option. Double click [RML- remote mail] and check whether the SID is in upper case.  Also check whether the RML client is 000 client.

• Fill all other tab also and save.

1.2   Configuring SAPconnect:

• Go to transaction SCOT
• Double click SMTP

• Make the following changes as shown in the screenshot and click ‘set’(enable node in use)

• Go to Supported Address Types -> Select Inter Net option and click set button ->Enter ‘ * ’ in address area and click continue

• SAPconnect Domain Configuration ( Go to Settiongs -> Default Domain )
• Goto SETTINGS – DEFAULT DOMAIN and give the default domain value as  xyz.COM

• Enter Default Domain Name

• Click send jobs button from the menu

• Click CREATE JOBS ( BUTTON ) -> Schedule for INT

• Enter the Job name, Variant, Address Type, No. Work Process, Period, Start time and Background User
• Click Continue

• Automatically Background Job Triggered, Simply SAVE it.
• SAPconnect created successfully

3.3:  Configuring SMTP Service

• Transaction SMICM (activating SMTP service)
• Click services –> Check whether SMTP service is activated.

NOTE: If the services is not activated create a service throw following steps.

• Select Service

• Click Service -> Create
• Enter Service Port, log type, Alive and Max processing time then Create Service

3.4:  Checking the Mail server configuration:

• Go to Transaction SBWP
• Click new message
• Enter recipient NAME and TYPE.
• Enter needed details

AUTO REACTION METHOD

(TRIGGERS MAIL AUTOMATICALLY, WHEN SERVER IS DOWN)

1.5:  Goto transaction RZ20 –> SAP CCMS monitor template –>Availability and performance overview –> Double click on it.

• In PERFORMANCE ATTRIBUTE type set the threshold values as required.
• In Methods tab -> Select METHOD ASSIGNMENT push button

• Select parameters tab and fill the required details.

Note : Remember to provide the user for which we configure the remote mail at the beginning of the document.

• Save and go back to the auto-reaction tab

• Now check the process by bringing the server down.

following Mike Kerrigan's blog yesterday about frustrations with OSS Messages,
it's high time we share some tips and tricks on working with the OSS system.

Doing my fair share of OSS Messages for Customers where I am engaged has lead
me to develop some tips and tricks and techniques for maximising the response
to OSS Messages.

The goal of this blog is to share those tips and on top of this, furthermore,
request others who have good tips and tricks for OSS Messages to add their gems
and pearls of wisdom in the comments.

I have also included in here (without permission), an items from a SAP
Support CIC Presentation which we were given at one Customer. Hopefully the
good intention and synergy of the content will allow this information to be
published.

Where shall we start, let's start at the very beginning a very good place to start ,

as Julie Andrews said in The Sound Of Music which my daughters keep watching.

• Step 1) The Message Priority

When you post an OSS Message you begin with the priority of the message.

Making the right choice in the beginning between LOW, MEDIUM and HIGH

priority, is extremely important.

Where and when to use a MEDIUM or a HIGH ?

I've experienced regularly, that if you open a MEDIUM as a MEDIUM and it is a
straight black or white question you often get a very very fast response and
closure. I guess it's to do with low hanging fruit, we all do tickets and the
low hanging fruit are the easiest and if an OSS Case comes in as  a MEDIUM

and with a straight yes or no question it's an easy one to close.

I've experienced getting answers to MEDIUM questions within hours on several

occasions in the last couple of years. So my point is, use the message priority

with care.

• Step 2) Selecting Correct Message Component

It can be confusing trying to select the correct or most appropriate Message
Component for your OSS Message.

Quality time invested in choosing the correct Message Component, getting this
right will speed up message processing by reducing the wasted time with the
message ping ponging with the wrong processing Component Team.

How to choose the correct Message Component, or as close as possible to the
correct one ?

Look for OSS Notes which are similar to the issue you are working on, find
and OSS Note similar to the issue you are working on and then in that OSS
Note look for and make a note of the Primary Component of the OSS Note.

Then, use that Primary Component as the Message Component for the OSS

Message.

Here's an example, you have a problem with PDF's generation in HCM through

Portal. Your ADS is the ADS of the Portal. You quickly open a Case to SAP and

put the Message Component as EP something or other. EP something or other

is not the ADS/PDF Team at SAP and therefore, there will be a delay while the

Message Processor from the Portal Component Team at SAP gathers all information

and then concludes this message is for the ADS/PDF Component Team.

How to find the ADS/PDF Component Team, find an OSS Note on ADS and PDF's
similar to your issue, and look at the OSS Note Primary Component and use
that as your Message Component.

• Step 3) Entering the Message Details and Information for SAP

When you enter the information for SAP, remember, garbage in, garbage out.

When entering the Message Details, make as much effort as possible to provide
as much information as possible:

• Describe the issue in detail

• Even provide a word document with screenshots showing all of the

steps required to reproduce the issue and the result

• Provide log files

• Provide full System Information

• Describe the Operating System and Database and their versions

• Open the System Connection and put the logon details in the secure

area

• Make sure the Contact Details in the Message are correct

• email

• telephone number

All of these items, will help speed up the message processing and reduce the
ping ponging, the more effort you make the more you will be rewarded by
faster processing of Message

• Step 4) Working With SAP and Supporting The OSS Message

It is a revolution in OSS Message Support that we now get emails when the
Message status changes, this makes tracking the message much easier and
more fluid. Nevertheless, if you have an important message you should keep you
eye on the status of the message.

It is very important to make a qualified judgement of the quality, correctness,
and standard of the replies from SAP as there may be a need to request and
where necessary escalate to get messages moved to the next layer of support.

If you are not happy with the quality of the response from the Message
Processor then call SAP Global Support CIC and discuss with them and also
provide clear feedback in the Message and politely request with justification
that the Message is moved to the next layer of support

Keep attention on Messages by where necessary giving regular calls to SAP
Global Support CIC to request attention to the Message from the Message
Processor

• Step 5) Be Polite

Treat people as you would like to be treated

• Step 6) When Issues Become More Urgent

(this slide is taken without permission from a SAP presentation, if requested

I will remove it from the blog)

Finally, the icing on the cake is to be a Max Attention Customer. But nonetheless,

from my own experience, yes nothing beats Max Attention, but if you're not

at a Max Attention Customer and you make the right effort then you will get

the highest possibility of efficient message processing.

As already requested, please add your OSS Message Support Tips and Tricks to the
blog comments.

All the best, and remember, have fun with your OSS Messages :-)

Andy.

p.s. Personally I don't agree with using the SCN Platform as an instrument for
complaining about SAP. Personally I see SCN as a positive medium for bringing
out the best and improving in all areas. For me, regarding complaints to SAP,
if there is an issue, there are proper commercial Customer Account channels
which can used to report back to SAP and escalate where necessary.

p.p.s. Note to self - remember to practice what you preach

Having watched, 'Good Morning Vietnam', on a flight on Monday, I have to begin this blog with...

Good Morning SCN,

    SAP Transaction Codes

    Our favourite SAP Transaction Codes

    Who's favourite SAP Transaction Codes ?

          Functional Consultants favourite SAP Transaction Codes by Function

          Functional Consultants favourite SAP Transaction Codes by SAP Component
          - ECC, FI, HR, CRM, BI etc

          Basis Consultants favourite SAP Transaction Codes by task

          Basis Consultants favourite SAP Transaction Codes by SAP Component

          Development Consultants favourite SAP Transaction Codes by task

          Development Consultants favourite SAP Transaction Codes by SAP Component

As we all know, there are thousands of SAP Transaction Codes, everybody has their
favourite most useful SAP Transaction Codes.

There are disperse and diverse websites all over the Internet containing people's
favourite lists of useful SAP Transactions by function, by task, by component.

There's even a hard copy SAP Press book of SAP Transactions which is great and
I even own a copy but it kind of seems an oxymoron every time I look at it,
because a) it's not easy to search, and b) it doesn't get updated, and c) it's big
and heavy.

Isn't it time, the power of the SCN Community was unleashed to compile a
perpetual work in progress list of everybody's favourite SAP Transactions Codes ?

Imagine the power and usefulness of such a list of SAP Transaction codes,
perpetually maintained and compiled by SCN Community Members, divided and
catagorised by Function, Task, Component, in one list, fast searchable
and available to contribute to and take from by all.

This blog proposes we start a new Wiki, The SCN Wiki of SAP Transaction Codes.

We can agree a skeleton for the Wiki, cataloging and classifying SAP
Transaction Codes by SAP Component and Function - Basis or Functional
or Developer. 

We can catalogue something like this:

    SAP Component - ECC

          Functional SAP Transactions

              Tcode xyz - small description & and version validity
           

              Tcode xyz - small description

          Basis SAP Transactions

              Tcode zyx - small description
 

              Tcode zyx - small description

          Developer SAP Transactions

              Tcode qwe - small description
 

              Tcode qwe - small description

    SAP Component - BI

          Functional SAP Transactions

              Tcode xyz - small description
 

              Tcode xyz - small description

          Basis SAP Transactions

              Tcode zyx - small description
 

              Tcode zyx - small description

          Developer SAP Transactions

              Tcode qwe - small description
 

              Tcode qwe - small description

etc

The proposal is one Wiki page, which will then be easier to search and
not require clicking back and forth through layers of catagorisation.

The Wiki will be editable by all.

Together using and unleashing the power of the SCN Community we can
build the world's greatest list of SAP Transaction Codes maintained
in one place on the Internet by the SCN Community and searchable and
editable by all.

How cool is that ?  :-)

Please give your feedback if you would like to contribute from the
beginning and have any ideas how to make this SCN SAP Transactions
list even more valuable and useable for the community.

As we all know, Proper Planning and Preparation Prevents P*** Poor
Performance, and keeping this in mind, the first step, is to agree
the structure of the SAP Transaction Codes catalogue, if you have a
better solution to the cataloging structure than the above proposal
give your feedback in the comments here.

The Wiki is here:

The SCN Community's Wiki of SAP Transaction Codes

It is a work in progress.

All the best,

Andy.

Standards for Human Capital in SAP Delivery

We work in companies where the development and delivery of near perfect products and
services is governed by industry standards such as Six Sigma.

We work in companies where projects are managed according to certified practices and
methodologies eg Prince, PRiSM, Agile.

We work in companies where the SAP IT systems are installed with quality standards and
approaches, documentation and validation and verification.

We work in companies where the SAP investment can be a significant percentage of the
organisation's profit, where failure of a SAP system can affect profit, where failure
to run a SAP system in a qualified way can cost fines (FDA/Pharma).

We work in companies where pretty much anybody, any Human Capital can come through the
door and run these systems if they can make a strong enough case that they are qualified
to complete the task.

The question of determining the qualification of Human Capital in SAP Delivery is one
which has been around for years and more than ever needs addressing.

In today's world it is more difficult than ever for Hiring Managers, Project Managers,
SAP Delivery Managers to ascertain the quality of resources being presented for roles.
Face to face interviews are less and less, because of circumstances there is not always
enough knowledge on the interviewer side to make the technical and project experience
judgement of a candidate. With the internet and the wealth of information available it
is more easy than ever for potential candidates to fill gaps and recalibrate knowledge
and experience. Interviewers are often interviewing somebody on the other side of the
world. Even in large organisations, it is often people who are not from a SAP background,
the HR Team who are providing the service to the organisation and making the initial filter
of potential candidates.

How to improve this ?

There can be only one way, internationally trusted, internationally validated, minimum
basic standards for SAP Human Capital, that is,

      SAP Education and Certification

Our industry needs to standardise measuring SAP Human Capital minimum standards of knowledge
using SAP Education and Certification as the bench mark yard stick.

Using SAP Education and Certification as the minimum bench mark yardstick across the world
will make everybody's lives easier across the whole process of sourcing and delivering
SAP Human Capital.

Admittedly, Certification is not and will never be the only measure of a person's skills and
knowledge, we all know that, but it will provide, a minimum standard with which to filter
candidates making the task of filling roles much easier and creating an accepted level
playing field for SAP Human Capital.

As an example, we all know, there can be good doctors and there can be not so good doctors,
the not so good and the good doctors are all qualified and certified. If they weren't they
cannot be doctors. Would you ever go, or send your children to a doctor who is not certified ?
Big companies do the same with their SAP systems every day, big companies allow uncertified

SAP Human Capital to work on their systems ! Why ?

In practice, how would filtering candidates on certification work ?

First Stage if the Selection Process:

Initial filter of potential candidates - Certified or Not ?

Simple yes of no. Certified candidate goes to the next stage of the selection process,
not certified candidate is disguarded.

Second Stage of the Selection Process:

Candidate's professional experience etc etc

Therefore as can be seen, certification is not the be all and end all, certification is not
the only tool to be used when selection candidates, but, it is the highest level filter,
the first layer of the selection process, the Industry Standard for selection SAP Human Capital.

Anybody who says they are certified by experience, as I too have been an advocate in the past,
if we're so qualified by experience then in a lot of cases, we are able to go to our local
SAP Education Center and pay to sit only the exams we want to sit and not necessarily follow
the whole curriculum, although following the curriculum would be the most productive path as
it would give all certification candidates the full picture from the official SAP perspective.

As I have previously recommended in other discussions on SCN, SAP themselves need to be leading
or as a minimum pushing this direction, SAP can help this goal be reached in may ways, not
least by using their position to:

. Incentivise Customers to have a certain percentage of their SAP Human Capital
certified, perhaps in return for discounted support, because one would have thought
that if Certification is used as the _first layer_ for filtering candidates then
there will be less support calls to SAP from the Human Capital running the
Customer's SAP systems

. Partners are already incentivised to have a certain percentage of certified
consultants, but Customers are not, and balancing and correcting this will be one of the
steps of the strategy implementation

. Running campaigns to promote certification as the SAP Industry standard for hiring
SAP Human Capital

. Leading Customers to resourcing SAP Human Capital using SAP Certification as the
baseline industry standard, this would mean promoting this strategy to Customer's
HR and IT streams

. Leading by example

Such a strategic change will not be overnight, but will gain momentum and critical mass.

Ultimately everybody will benefit from SAP certification as the tool for the first stage
of the selection process of SAP Human Capital, and in the end there will be  no reason not

to be educated  and certified by SAP.

The final note being, would you send your child to an uncertified doctor ?  In the same respect
why are big corporations allowing uncertified people to run their SAP investments ?

I look forward and welcome all feedback to this discussion, it will be an opportunity to openly convert

the nay sayers :-)   Inheriting and extending from Highlander, there can be on one _way_, and

that way is certification and until there is some coherent action taken on this subject, lead by SAP,

the question will pop up, and pop up again and again.

All the best,

Andy.