2011 Aug 12 7:56 AM
Hi Experts,
Initially I try to add new field into Organizational Levels (i.e.PERSA) using program PFCG_ORGFIELD_CREATE
/ UPGRADE / DELETE and encounter RunTime Error which might cause this issue. Then, I found note that refer me to SU24 to check missing fields in P_ORGINCON and I found field PERSA is missing. I try to add but not able to (perhaps do not know how)
Error Message: 'Authorization default values of transaction PA30 for object P_ORGINCON inconsistent'
Steps to reproduce:
1) Transaction Code: PFCG - create new role
2) Menu Tab: Add transaction Code PA30/PA20 and save.
3) Authorization Tab: click 'Change Authorization Data' button to maintain and you will get the above mentioned error
Appreciate your advice in this matter and million thanks in advance.
2011 Aug 12 8:46 AM
One of the solutions I've heard on similar occasions is to go to a system where this inconsitence does not exist and transport the object from there. Importing it will overwrite your broken object.
Hope this helps
Jurjen
Thanks Raghu,
The issue has been resolved by different resolution and steps taken are:
1) Go to SU25 (step->3) in other client which does not have this issue
2) Create transport request (TR)
3) Transport TR into the affected client to overwrite the inconsistency
Best Regards
2011 Aug 12 8:46 AM
One of the solutions I've heard on similar occasions is to go to a system where this inconsitence does not exist and transport the object from there. Importing it will overwrite your broken object.
Hope this helps
Jurjen
2011 Aug 12 9:04 AM
Hi,
Here is a simple solution:
1. Goto Su24 for the said transaction code.
2. Make P_ORGINCON check indicator to Check from Check/Maintain.
3. Save
4. Again change the P_ORGINCON from Check to Check/Maintain.
5. Save and create a transport request.
You will not see the inconsistency error back.
All the best!!
Regards,
Raghu
2011 Sep 28 5:02 AM
Thanks Raghu,
The issue has been resolved by different resolution and steps taken are:
1) Go to SU25 (step->3) in other client which does not have this issue
2) Create transport request (TR)
3) Transport TR into the affected client to overwrite the inconsistency
Best Regards
| User | Count |
|---|---|
| 6 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |