Authorization Default values .....

[Former Member]

In PFCG I am maintaing a role --when i click on the ' Change authorization Data " the message I get is

"Authorization default values of transaction sm36 for object S_BTCH_JOB inconsistent"

Background:

I am maintianing the roles during the upgrade -to ECC6. Idid two stand alone (meaning no transports ) upgrades and i didnot get this error at all --any inputs ??

[jurjen_heeck]

Have a look at SU24 for that transaction. When in change mode they will be adapted automatically. All you have to do is save (if on dev, otherwise transport the customer tables).

[Former Member]

Juergen transport the customer tables on SU25 process ?

[jurjen_heeck]

> transport the customer tables on SU25 process ?

That's the one.

[Former Member]

Will this table be needed to be transported across until PRD ??- i amnow in the DEV only.

The reason why I ask is while creatign the role we need to maintian only in the dev box and this goes across the landscape ....I am bit unclear here

of all the roles that I have maintained only one TCD - SM36 - has come with the problem !!

[jurjen_heeck]

> Will this table be needed to be transported across until PRD ??- i amnow in the DEV only.

You really want to keep these tables in sync throughout your landscape.

[koehntopp]

While you're at it, you might also want to make sure all your developers are aware of SU24 and maintain it religiously.

I reommend reading Julius' blog on the topic:

(Btw., Julius, where is Part 2?)

Frank.

[Former Member]

Juegen,

I am not partly convincedby your anwer of Step 3 - transports.The reason for this is as follows;

1. I am now in the DEV BOX and I should be able to maintain the role in the SAME DEV Box without the transports ! --am Iright ?

Ican understand if I need to move it to QAS .

Looking forward to hear from you !

[jurjen_heeck]

> 1. I am now in the DEV BOX and I should be able to maintain the role in the SAME DEV Box without the transports ! --am Iright ?

Yes, that should work. Did you go into SU24, enter tr. SM36, go to object S_BTCH_JOB and into change mode?

Accept the new values and save. That should straighten out the issue.

As far as I can imagine your original problem can only have come from an upgrade/support pack where the number of fields in an authorization object changed. I've seen it with a dfps package. Changeing in SU24 or (re-)reading the customer tables in SU25 are the ways I know to fix this.

Afterwards you should still transport the tables to keep your landscape consistent.

[Former Member]

You are right ! I fully agree and am convinced fully !!

But my problem is this Do i need to do the " step1 of su25?" meaning intial fill of Customer tables ?? I thought this is done only when PFCG is used first.

My DEV isthe golden client so the changes to SU24 are not permitted for whatever reason --> I know you will yell at me but thats the way its here !

[jurjen_heeck]

> But my problem is this Do i need to do the " step1 of su25?" meaning intial fill of Customer tables ?? I thought this is done only when PFCG is used first.

That should be done after every upgrade. Your biggest challenge is to safeguard your changes to the customer tables USOBT_C and USOBX_C before overwriting the tables and restoring everything you've done afterwards.

I'll look into this tomorrow (no system at hands now).

If you've never changed any settings you can safely re-load the customer tables.

Jurjen

P.S. I won't yell. SU24 settings are often considered as customizing. Just find out in which client those are done.

Edited by: Jurjen Heeck on Oct 1, 2008 6:57 PM

P.P.S. Come to think of it, these tables are cross client, you need a workbench transport for changes. So a 'golden client' is kind of irrelevant here...

Edited by: Jurjen Heeck on Oct 1, 2008 7:29 PM

[Former Member]

Unanswered