Report Designer error

@bdoucette I remember that after an upgrade to 23R1 SU4, users were also experiencing access issues / warning messages.

In 22R1 we used to have all our permissions as grant full or grant read only. After the upgrade we noticed that most of our permissions were Custom access level → I assume this happened because maybe there’s new functionality coming in 23R1 for some projections and that functionality is not implicitly granted to existing permission sets.

What we did is the following:

• created a quick report to see how many such cases we have

select a.projection
       , a.role 
       , FND_PROJECTION_GRANT_API.Get_Grant_Access(a.projection, a.role) access_level
       , to_date(to_date(a.objversion, 'YYYYMMDDHH24MISS'), 'DD-MON-YY') Last_Changed
from FND_PROJECTION_GRANT a
where 1=1
and ifsapp.report_sys.parse_parameter(a.projection,'&[-C--L]Projection')='TRUE'
and ifsapp.report_sys.parse_parameter(a.role,'&[-C--L]Permission_Set')='TRUE'
and FND_PROJECTION_GRANT_API.Get_Grant_Access(a.projection, a.role) = 'CUSTOM'

• run a DB script via delivery to grant Full or Readonly

DECLARE
   CURSOR GetProjRoles IS
      SELECT a.projection
       , a.role 
       , FND_PROJECTION_GRANT_API.Get_Grant_Access(a.projection, a.role) access_level
       , to_date(to_date(a.objversion, 'YYYYMMDDHH24MISS'), 'DD-MON-YY') Last_Changed
      FROM FND_PROJECTION_GRANT a
      WHERE 1=1
      AND FND_PROJECTION_GRANT_API.Get_Grant_Access(a.projection, a.role) = 'CUSTOM';
   rec_   GetProjRoles%ROWTYPE;  
BEGIN  
   FOR rec_ IN GetProjRoles LOOP 
      IF rec_.role LIKE '%_FULL' THEN 
         Fnd_Projection_Grant_API.Grant_All(rec_.projection,rec_.role); 
      ELSIF rec_.role LIKE '%_READ' THEN 
         Fnd_Projection_Grant_API.Grant_Query(rec_.projection,rec_.role);
      END IF;
   END LOOP;      
   COMMIT; 
END;

Maybe this will be helpful in your case also.