Customizing Request While Implementation SAP HR

[Former Member]

Dear SAP Gurus,

My name is Rohit and i have recently put into one big implementation project. So for that i need some clarification.

While configuring Personnel Administration, Time Mgmt. Payroll etc in development client only one customizing request will be created or everytime we have create new customizing requesting.

For E.g - In P.a we configure Personnel Areas, Persoonel Subareas, Actions...etc so for this all configuration only 1 customizing request will be there or separate for each new configuration.

2. If it is same request then will it also be continued for TM & Payroll...for transporting to another client..or not

Please share your views earlier as i am in big trouble...as this is my 1st implementation.

[Omid · Accepted solution]

Hi Rohit,

I think it depends on your project specification. Usually project management should give you such standards and arrange to be unique for whole implementation.

My colleagues in logistic team would separate per module and task but I would separate just per module. For example you can define a naming conversion and define request for PA, OM, PT, PY and so on. You should define a version number for each request of each module and by transferring each request you will increase version number.

You should talk about this issue with a basis consultant. You know request definition has some effects for example in back of request and so on. Generally it's not a good idea to keep requests so small or so big. To have an idea have a look at my document at http://scn.sap.com/docs/DOC-45570

Cheers,

Omid

[Former Member]

Dear Omid Sir, Kedhar, Kartik and Mr. Ringling,

Thanks a lot for your quick reply.

So you mean to say that per module there will be only one  customizing request in most of the cases.

And basis consultant needs to be approached for the same to have more clarification.

Regards

Rohit

[Former Member]

HI rohit

let me reiterate there is no hard and fast rule,it all depends on the consultants comfort level..its good if we have a repository of TR for project metric.

the transport of requests depends on client landscape and client itself..if its open we ourself can transport using SCC1 and STMS TCD's...seldom you will come across clients who will allowe  to play around and learn

no worries

karthik

[Omid]

Hi Rohit,

Yes I recommend this but I as I said you have to transfer your request during implementation so I recommend to add a version number.

By the way, after go live I recommend to create specific request for each issue with a meaningful description.

Regards,

Omid

[Former Member]

Hi Rohit

There is no hard and fast rule i reckon

if we go to se09 we will find the parent request and beneath thaat you wil  find the child request which wil have the IMG nodes and Tables as well

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d04c8c3c-40bf-2e10-139a-f7c5cd6e6...

gud luk Rohit!Play around

hope it helps

no worries

karthik

[Former Member]

I basically agree with Omid: this is a guideline project management needs to provide.

Throwing in my experience: in most cases I'd use one transport only until the first transport is to be moved into the QA environment. Using many usually leads to confusion and errors re objects needed in several transports.

From that point onwards, you need to think in testable packages to go onto separate transports and be tested.

Be cautious about schemas as one schema might be involved in two separate activities.

Kedhar's note about sequence is important! Particularly when moving on to production later. Always remember that the objects are on the transport in the version they had, when the transport was released. So, to avoid older versions overwriting current versions, you need to transport in sequence of release - not transport number.

Just my 2p - there are different ways to approach the problem.

Kind regards

Sven

[Former Member]

Hi Rohit,

It is not a big deal, you can continue with one request or multiple as per modules,

if it is multiple then you need to transport in sequence while moving from one client to another.

As said by Omid it's depends on Project config specifications required.