Quantcast
Channel: SCN: Message List - Security
Viewing all articles
Browse latest Browse all 5338

Demoting an org-level - what to transport and when to do so

$
0
0

Dear gurus,

 

I am confronted with a question where it seems there is no answer except trying, so thought it best to see if anyone has done this before...

 

Background is SAP notes 323817 and 727536 regarding demoting customer org.level fields.

 

Someone promoted 28 fields to org.levels in a system here. PFCG_ORGFIELD_CREATE has a transport connection, so at the time the USORG and USVAR table entries were also transported through the landscape.

 

Now I have degraded to the fields to normal fields again using PFCG_ORGFIELD_DELETE, which converts the SU24 and PFCG data and the USORG and USVAR tables, but it does not ask for a transport request...

 

New roles which include the now "normal fields" can be imported successfully into QAS and PROD systems, and the old roles will clear themselves out and are being completely replaced anyway.

 

So my question is: should I transport the USORG and USVAR tables through the landscape as well? If yes, then before the roles are transported would seem correct to me, but there is no dialog I can find to add these to a transport request, so I suspect that maybe SAP's intension was simply to leave the data there as "dead wood" in QAS and PROD. The only way I can think of is to manually insert the tables as "table contents" into a workbench transport and send that through  - but that seems a bit suspect to me...

 

Has anyone done this before? Did you sync the tables in QAS and PROD or just leave them as inconsistent in the landscape?

 

Cheers,

Julius


Viewing all articles
Browse latest Browse all 5338

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>