Creation of variant to paas on list of users using a table

Question

Hello All,
I got a requirement to create a report in FI-GL  with the requirement for selection and layout  as follows and how to incorporate the same in the
List of Users (through variant)  and Doc. Type (user input) :
To exclude transactions, which are not manual journal entries, a table should be created with exclusions.
*This table will contain two types of exclusions:*
Document types which will never been used for manual journal entries, since their nature is system related (SAP R/3 standard). In principle, this table will be fixed
List of Users
which are not related to persons, but to automatic transactions. This table needs to be verified and updated on regular basis.
Could any one suggest me how to do a vaiant for the user  through a table and that too this table should ba updated on regular basis.

Answer 1

Hi,
rcc50886 wrote:
We have a situation where we need to allow particular users which are stored in a table.Why don't you simply revoke the CONNECT privilege of the users who shouldn't log in, or lock those accounts? AFTER LOGON triggers can cause huge problems when they don't work right, eg., if for some reason they become invalid.
create table system.ALLOW_RESTRICTED_USERS (username varchar2(30), insert_date date default sysdate );
CREATE OR REPLACE TRIGGER SYS.RESTRICTED_USERS_TRIG
AFTER LOGON
ON DATABASE
DECLARE
BEGIN
IF DBMS_STANDARD.LOGIN_USER NOT IN (SELECT USERNAME FROM system.ALLOW_RESTRICTED_USERS)
--  IF SYS_CONTEXT ('USERENV','SESSION_USER') NOT IN (SELECT USERNAME FROM system.ALLOW_RESTRICTED_USERS)
         THEN
               RAISE_APPLICATION_ERROR (-20001, 'Unauthorized login');
       END IF;
END;
Warning: Trigger created with compilation errors.
SQL> show error
Errors for TRIGGER SYS.RESTRICTED_USERS_TRIG:
LINE/COL ERROR
3/3      PL/SQL: Statement ignored
3/38     PLS-00405: subquery not allowed in this contextHow to use subquery on the above trigger ? or is there any better way to achive required results .... IN (x, y, z)           works in PL/SQL, but
... IN (SELECT ...)       only works in SQL.
Don't use IN. Use some other way to query the table, some way that will return usable results no matter what (if anything) is in the table, like this:
DECLARE
   username_found     allow_restricted_users.username%TYPE;
BEGIN
  SELECT  MAX (username)
  INTO       username_found
  FROM       allow_restricted_users
  WHERE       username     = dbms_standard.login_user;
  IF  username_found  IS NULL
  THEN
     ...As mentioned already, don't create your own objects in Oracle-supplied schemas, especially SYS and SYSTEM.