On analysing the Autho Objects enabled in GRC for Organisation mgmt module of HR I notice that :
1. A key OM Authorisation Object 'PLOG' is disabled and instead P_ORGIN is Active. for e.g - Tcodes like PO14 & PO01, included in HR05
2. In some instances the values of field 'Otype' for PLOG are inadequate for e.g. A.) for Tcodes- PPOC, PPOCE only values C & P have been included which are inadequate. B) Tcode PP01 - only C & P are enabled.
My Concern :
P_ORGIN controls PA modules in HR & also maybe getting called due to integration between PA & OM. However, without PLOG object , OM tcodes cannot be executed. On testing I find that without P_ORGIN I can still make changes on the OM side, but PLOG is mandatory (these changes maynot get reflected in PA side due to missing P_ORGIN). Hence I am trying to understand why PLOG is disabled in standard ruleset for certain OM tcodes.
I have tried numerous searches on SCN/ net to find any relevant notes / updates on these objects & treatment in GRC , but barring a few notes wherein new tcodes have been included in some function ids, I donot get any reference.( for e.g in Note 1083611, PPOC is updated with Autho object P_ORGIN, but not PLOG! )
Since I am neither a developer/programmer or functional consultant working actively on any project right now, I donot have any means to raise an incident in SAP market place.
Hence requesting the experts to please provide insight