7/23/2019 PPOMW - Changes in Production Not Allowed _ How to Allow Changes by T77S0 Setting X

http://slidepdf.com/reader/full/ppomw-changes-in-production-not-allowed-how-to-allow-changes-by-t77s0-setting 1/5

6/21/2015 PPOMW - changes in production not allowed | SCN

https://zend2.com/monday3.php?u=V2%2BY31OrR1Cr6nZ45t4cBIY8SeenqGb3Ri8oz3s%3D&b=29&f=norefer

 

Log On Join UsHi, Guest

 Activity Communications Actions

Browse

Tweet

13 Re plies   Latest reply: Apr 28, 2011 1:48 PM by Suresh Subramanian  

3196 Views

PPOMW - changes in production not allowed

Hi, We would like to assign a cic-profil to a user in trans action PPOMW in production environment. After 

saving the changes the error messages u201Cmandant 100 changes not allowedu201D occurs.

 Our consultants told us, that we have to change to status of the production environment in SCC4

before changing profiles in PPOMW.

 In my opinion this solution is not useful.

 Is there another solution or workaround ?

 Kind regards,

  Andreas Ament

 Andreas Ament   Apr 21, 2011 1:46 PM

Re: PPOMW - changes in production not allowed

Hi,

 you can always use report RHMOVE30 to transport HR related stuff.

 Kind regards, Rob Dielemans

Like (0)

Rob Dielemans  Apr 21, 2011 2:00 PM (in response to Andreas Ament)

Re: PPOMW - changes in production not allowed

Hi,

 Please contact with your basis team as it is a wuthorization issue.

Tou may also ty tcode PPOMA/PPOME.

 Thanks and regards,

SNJY

Like (0)

Sanjay Pal   Apr 21, 2011 2:13 PM (in response to Andreas Ament)

Zend2 Home

7/23/2019 PPOMW - Changes in Production Not Allowed _ How to Allow Changes by T77S0 Setting X

http://slidepdf.com/reader/full/ppomw-changes-in-production-not-allowed-how-to-allow-changes-by-t77s0-setting 2/5

6/21/2015 PPOMW - changes in production not allowed | SCN

https://zend2.com/monday3.php?u=V2%2BY31OrR1Cr6nZ45t4cBIY8SeenqGb3Ri8oz3s%3D&b=29&f=norefer

Re: PPOMW - changes in production not allowed

Hi

 Did you have access previously?

 It is likely that the problem comes from the automatic transport connection configuration in your 

productive system. You have more information on this regard in notes 208746, 163897 and 33582.

 Please check the following switches in table T77S0:

  TRSP ADMIN (Deactivate automatic transport in infotype 0001)

  TRSP CORR (Transport Switch (X = No Transport))

 Please check the result with both switches set to 'X' (= no transport). After this change you should not

be getting any error message when saving.

 Regarding this parameter change in T77S0 view, please take into account that you have two

possibilities: you might want to change this in all the systems, or you might want instead to change

these values just in the productive system.

 a) For the first option it will be enough to set these "X" in the development system and then transport

the corresponding request

  with this change to the quality and production systems.

 b) For the second option, you can allow changes in T77S0 view in the productive and pre-productive

system, so you can mantain a different value there compared to development and quality.

 1- enter SOBJ transaction

  2- search T77S0 object

  3- double click on it

  4- activate the current settings flag

 Regards,

Eddie

Like (0)

Eddie Morris  A r 21, 2011 5:19 PM in res onse to Andreas Ament

Re: PPOMW - changes in production not allowed

Hi,

 

No, did not have access previously?

 the problem is that we do not have all the end users in the development system (D) and cannot

transport them to test (Q) and production (P) system. So I think the solution from Rob Dielemans

to use report RHMOVE30 would not work for me.

 I also tried PPOMA/PPOME with the same error message.

 So I think i will tried your solution. My problem is that I don't know which object and processes

are affected by changing the values in T77S0 and SOBJ in P-System. I tried to test this scenario

in Q but there I need a SCCR for development and object. The second thing is that the T77S0 is

a system table and after trying to change the value in TRPS-ADMIN an error message appears

that the SAP is owner of the field.

 I think our consultants have to solve this problem in case of something does not work after 

applying the changes. I have not enough expiriences to apply your solution myself.

 

Thanks. Kind regards,

  Andreas Ament

Like (0)

Andreas Ament  Apr 26, 2011 4:01 PM (in response to Eddie Morris)

Re: PPOMW - changes in production not allowed

Hello Andreas !

 Changes not reflecting in production system is BASIS issue.

Suresh Subramanian   Apr 26, 2011 8:21 PM (in response to Andreas Ament)

7/23/2019 PPOMW - Changes in Production Not Allowed _ How to Allow Changes by T77S0 Setting X

http://slidepdf.com/reader/full/ppomw-changes-in-production-not-allowed-how-to-allow-changes-by-t77s0-setting 3/5

6/21/2015 PPOMW - changes in production not allowed | SCN

https://zend2.com/monday3.php?u=V2%2BY31OrR1Cr6nZ45t4cBIY8SeenqGb3Ri8oz3s%3D&b=29&f=norefer

 Is the configurations for workflow related transportation is allowed in OOCR

transaction or T77S0 table ?

  It should be as follows :

  Under the columns Group, Sem. abbr and Value abbr. should be TRSP,CORR and

blank space( do not enter any thing in third field.Leave it blank) respectively.

 Regards,

S.Suresh

Like (0)

Re: PPOMW - changes in production not allowed

Hello Suresh,

 hope Suresh is your first name.

 the third field in OOCR for TRSP,CORR is blank in all systems (D,Q,P).

 "Changes not reflecting in production system is BASIS issue." 

Can you give me some details ?

 Kind regards,

  Andreas Ament

Like (0)

Andreas Ament  Apr 27, 2011 8:58 AM (in response to Suresh Subramanian)

Re: PPOMW - changes in production not allowed

Hello Andreas !

 You've asked

  "Changes not reflecting in production system is BASIS issue." Can y

Say, some changes are made in quality system.When those changes are

transported to production system, the changes made in quali ty system also can beseen apparently as such in production system too.This is what I meant so.

 The third field should be blank to allow transportation.

  Are you getting a ny other error message apart from u 201Cmanda nt 100

changes not allowedu201D ?

 Regards,

S.Suresh

Like (0)

Suresh Subramanian   Apr 27, 2011 9:47 AM (in response to Andreas Ament)

Re: PPOMW - changes in production not allowed

Hello Suresh,

 Ok. I will try to describe the whole process.

 PPOWM -> Task assignment -> Assign position to user xyz -> Delimit vacancy

on -> User is assigned in table task assignment

 After saving the foll owing error message s occurs:

Error in object editing

Client 100 has status 'not modifiable'

Choose 'Display object' or 'Cancel'

 After choosing 'Display object' the informational message 'Save was canceled'

occurs.

 Kind regards,

Andreas Ament  Apr 27, 2011 10:21 AM (in response to Suresh Subramanian)

7/23/2019 PPOMW - Changes in Production Not Allowed _ How to Allow Changes by T77S0 Setting X

http://slidepdf.com/reader/full/ppomw-changes-in-production-not-allowed-how-to-allow-changes-by-t77s0-setting 4/5

6/21/2015 PPOMW - changes in production not allowed | SCN

https://zend2.com/monday3.php?u=V2%2BY31OrR1Cr6nZ45t4cBIY8SeenqGb3Ri8oz3s%3D&b=29&f=norefer

  Andreas Ament

Like (0)

Re: PPOMW - changes in production not allowed

Hello Andreas !

  I hope this is due to "user type" in client 100.Try to change the

user type under "Logon data" tab in SU01 transaction.Hope it is in

"System".Try to change as "Dialog".It should work.

 Client 100 is your production system ?

 Regards,

S.Suresh

Like (0)

Suresh Subramanian   Apr 27, 2011 11:39 AM (in response to Andreas Ament)

Re: PPOMW - changes in production not allowed

Hello Suresh,

 I think, it has nothing to do with the user type. The user which has to

be assigned is already type "Dialog".

 Yes. Client 100 is our production system.

 Kind regards,

  Andreas Ament

Like (0)

Andreas Ament  Apr 27, 2011 2:21 PM (in response to Suresh Subramanian)

Re: PPOMW - changes in production not allowed

Hello Andreas !

 I request you visit the following to resolve your issue :

  URL : http://www.ikew.co.za/wp-content/uploads/OB52-

issue-on-SAP-ERP-61.pdf 

 Regards,

S.Suresh

Like (0)

Suresh Subramanian   Apr 28, 2011 8:39 AM (in response to Andreas A

Re: PPOMW - changes in production not allowed

Hello Suresh,

 I visited the link, but I don't know if this will work for me.

 I think the solution to deactive the PD-Transport Connection

in OOCR by setting 'X' in table T77S0 may work. But after 

saving the changes an error message will be raised. "Do

not make any changes (SAP entry)". The Infobox tells me

"Message no. SV117...Avoid changing this data ..."

 I am not sure what happens if I change this value in

production.

Andreas Ament  Apr 28, 2011 11:54 AM (in response to Suresh Sub

7/23/2019 PPOMW - Changes in Production Not Allowed _ How to Allow Changes by T77S0 Setting X

http://slidepdf.com/reader/full/ppomw-changes-in-production-not-allowed-how-to-allow-changes-by-t77s0-setting 5/5

6/21/2015 PPOMW - changes in production not allowed | SCN

https://zend2.com/monday3.php?u=V2%2BY31OrR1Cr6nZ45t4cBIY8SeenqGb3Ri8oz3s%3D&b=29&f=norefer

Follow SCN

Tweet

 I found the table in which the relations were stored.

HRP1001. May this be a approach for another solution.

 Kind regards,

  Andreas Ament

Like (0)

Re: PPOMW - changes in production not allowed

Hello Andreas !

 Entering "X" in T77S0 will not allow th eobjects to

transport for the group " TRSP" and sem.abbr "CORR".

 Lest, either ythe use of transaction SCC4 or SE03

would help.

 Regards,

S.Suresh

Like (0)

Suresh Subramanian   Apr 28, 2011 1:48 PM (in response to Andre