Authorization Groups and table TBRG

In our system we have tables which are using custom authorization group ZEXC. I am looking at this via SE11 Table Maintenance Generator or SE54 Assign Authorization Group.
I can also see that it is assigned to roles by using SUIM -->Roles-->By Authorization values -->entry auth object (S_TABU_DIS) and click on entry values.
What I am not seeing is that the authorization group is defined in table TBRG.
So my question is.... An authorization group does not need to be defined in order to attach it to a table or assign it to a role? If the authorization group was created then deleted is it still valid to have it attached to tables and roles?

Hi Sharon,
Assign the authorization to user and make it inactive mode.Then authorization will be deactived to tat particular user's.

Similar Messages

Table showing Authorization group and Package

Hi
Is there any table where we can see the list of programs using BOTH selection crieteria Authorization group and package together?
Your help and time will be really appreciate.
Thanks,
Niki.

Hi Niki,
Try se84->Other Objects->Authorization Objects->choose one->Process->Complete list button on aplication toolbar.
Regards
Marcin

How to create checkbox group and table dynamically?

HI All
How to create checkbox group and table dynamically?
Regards
Ravi

hi
check this links for creating tables dnamically
How to Create a table dynamically?
Re: how to create a table dynamically in webdynpro
and for checkboxgroup
IWDTransparentContainer rootContainer =
(IWDTransparentContainer)view.getElement("RootUIElementContainer");
IWDCheckBox check = (IWDCheckBox)view.createElement(IWDCheckBox.class,"Check"+k);
//Here "check"+k k represents a unique value every time u create so that u wont get a duplicate instance
check.setChecked(false);
rootContainer.addChild(check);
or Re: adding checkboxes dynamically

Authorization group for table maintenance view

I need to create table maintenence view for a custom table, client provide name for auth. group, but no clue how to create auth. group.
can someone provide the steps to do this?

Hi,
Follow below steps to create table maintenance for a table and to assign authorization group to a table:
step1: Go to SE11 enter the table name
step2: In the standard toolbar you will find UTILITIES
Go to UTILITIES -> TABLE MAINTENANCE GENERATOR
You will go to first screen of Table maint. gen.
Here you will find to enter authorization group.
Thanks and Regards,
Shravan G.

SE54: Assigning an authorization group to table &SM31&

Has anyone out there tried to assign an authorization group to the symbolic table &SM31& in transaction SE54?
Any success in using it?
Cheers,
Julius

Thanks Bernhard!
> But what I did find was [SAP Note 42563|https://service.sap.com/sap/support/notes/42563] .
> ...-->it's from 1997....!!
Note that the SM31 refered to in the note is not the SM31 we know today. It looks like SAP renamed it to SM31_OLD and replaced by a new SM31 (and the current settings option). The alternative having been changing miles of code, this seems reasonable but can be confusing (release dependently).
> Don't know if this is still used, as the check is in Rep.s SAPMSTBM, which is used in TX SM31_OLD, SM32, SM33 only.....
My rule of thumb is: If something is possible, then someone out there is either already doing it, or still doing it...
Cheers,
Julius

Group and table visibility

Hello Friends,
I am facing a problem as follows:
In an existing application I am trying to modify some code: there is a group which contains two tables the visibility of both tables are set to context element node also called visibility: and its elements table_1 is set to visibility property of first table and table_2 value attribute is set to visibility property of the second table.
Now from the coading as far as I understood it is as follows:
When the first table is set to NONE the second table is automatially visible and first table is disappered, and as soon as in coading it makes the first table visible the second table is automatically disappred ?
Can any one pls help me in understanding how/what is going on ?
Because the issue is I have to place now a third table and when this table is visible then the other two tables should not be visible, .......
Regards

Hi,
In the wdDoModifyView:- Now put the if condition for tables that if one is VISIBLE then other two should be set as NONE.
Regards,
Praveen

Handling substitution groups and Tables generation

Hi
This is concerning the generation of tables from xml schema containing "substitutionGroup" attributes and "extension" elements for
deriving from abstract types.
I want to know how the tables are generated when schema has subsitution groups.
I went through the generated tables and observed that it creates a table for each extension...but also generates a table for the head of the subsitution group.
This table would have columns for each of the members in the derivatives of the abstract type.This is resulting in more than 1000 columns in my case
Any suggestions?
Thanks
Devashish

When a subsitution group is used each of the type of each of the elements in the substition group must be an extension of the type of the head element. In the case where the head type is based on an abstract empty complexType this makes no sense. Since the type inheritiance system implies that anywhere a parent type can appear it is legal for the chlild type to appear in it's place we have to create a storage structure for the head element which can handle any of the possible child types. This means that at the storage level we have to generate a table with a column for each possible descendant of the head element. This means that we are effectively restricting the number of direct elements and attributes that can be defined by members of the substition group to a number that is a little less than 1000.
This can be be seen in the first example below.
However in the case where the substition group contains no common element we can model this as choice. as is shown in the second XML Schema. Since every member of the choice is independant of the other members of the choice there is no need for the inheritance hierarchy in the type definitions. This means that each member of the choice can now be mapped to a seperate table. This structure allows for a choice with approxamately a 1000 entries and no practicle limits on the number of decendant elements and attributes for each member of the choice..
This can be seen in the second example bleow;
The key point is the number of columns in ROOT_TABLE. In the First Example it is 17, the fixed overhead plus the number of columns required to persist headType, member1Type and member2Type. In the Second example it is 12, the fixed overhead plus a REF XMLType to point at instances of member1Type and REF XMLType to point at instnaces of member2Type.
I hope this answers your question
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> --
SQL> column qualified_col_name format A64
SQL> column data_type format A40
SQL> --
SQL> set lines 150 pages 25 long 10000
SQL> --
SQL> begin
2    :schemaURL := 'testcase.xsd';
3    :schemaPath := '/public/testcase.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attribute
FormDefault="unqualified" xdb:storeVarrayAsTable="true">
6     <xs:element name="root" type="rootType" xdb:defaultTable="ROOT_TABLE"/>
7     <xs:complexType name="rootType" xdb:SQLType="ROOT_T">
8             <xs:sequence>
9                     <xs:element ref="head"/>
10             </xs:sequence>
11     </xs:complexType>
12     <xs:complexType name="headType" xdb:SQLType="HEAD_T" abstract="true"/>
13     <xs:complexType name="member1Type" xdb:SQLType="MEMBER1_T">
14             <xs:complexContent>
15                     <xs:extension base="headType">
16                             <xs:sequence>
17                                     <xs:element name="Member1.Child1" type="xs:string"/>
18                                     <xs:element name="Member1.Child2" type="xs:string"/>
19                             </xs:sequence>
20                     </xs:extension>
21             </xs:complexContent>
22     </xs:complexType>
23     <xs:complexType name="member2Type" xdb:SQLType="MEMBER2_T">
24             <xs:complexContent>
25                     <xs:extension base="headType">
26                             <xs:sequence>
27                                     <xs:element name="Member2.Child1" type="xs:string"/>
28                                     <xs:element name="Member2.Child2" type="xs:string"/>
29                             </xs:sequence>
30                     </xs:extension>
31             </xs:complexContent>
32     </xs:complexType>
33     <xs:element name="head" type="headType" xdb:defaultTable="GLOBAL_HEAD_TABLE"/>
34     <xs:element name="member1" type="member1Type" substitutionGroup="head" xdb:defaultTable="GLOBAL_MEMBER1_TABLE"/>
35     <xs:element name="member2" type="member2Type" substitutionGroup="head" xdb:defaultTable="GLOBAL_MEMBER2_TABLE"/>
36 </xs:schema>');
37 begin
38    if (dbms_xdb.existsResource(:schemaPath)) then
39      dbms_xdb.deleteResource(:schemaPath);
40    end if;
41    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
42 end;
43 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> --
SQL> desc ROOT_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "root") STORAGE Object-relational TYPE "ROOT_T"
SQL> --
SQL> desc ROOT_T
ROOT_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
head                                                                                         HEAD_T
SQL> --
SQL> desc HEAD_T
HEAD_T is NOT FINAL
HEAD_T is NOT INSTANTIABLE
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
SQL> --
SQL> desc GLOBAL_HEAD_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "head") STORAGE Object-relational TYPE "HEAD_T"
SQL> --
SQL> desc GLOBAL_MEMBER1_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member1") STORAGE Object-relational TYPE "MEMBER1_T"
SQL> --
SQL> desc MEMBER1_T
MEMBER1_T extends SCOTT.HEAD_T
MEMBER1_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member1.Child1                                                                               VARCHAR2(4000 CHAR)
Member1.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> desc GLOBAL_MEMBER2_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member2") STORAGE Object-relational TYPE "MEMBER2_T"
SQL> --
SQL> desc MEMBER2_T
MEMBER2_T extends SCOTT.HEAD_T
MEMBER2_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member2.Child1                                                                               VARCHAR2(4000 CHAR)
Member2.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'ROOT_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          ROOT_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."head"                                                 HEAD_T
SYS_TYPEID("XMLDATA"."head")                                     RAW
"XMLDATA"."head"."SYS_XDBPD$"                                    XDB$RAW_LIST_T
TREAT("XMLDATA"."head" AS "MEMBER2_T")."Member2.Child1"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER2_T")."Member2.Child2"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER1_T")."Member1.Child1"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER1_T")."Member1.Child2"          VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
17 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER1_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER1_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member1.Child1"                                       VARCHAR2
"XMLDATA"."Member1.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER2_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER2_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member2.Child1"                                       VARCHAR2
"XMLDATA"."Member2.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member1>
4      <Member1.Child1>AAA</Member1.Child1>
5      <Member1.Child2>BBB</Member1.Child2>
6    </member1>
7 </root>'))
8 /
1 row created.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member2>
4      <Member2.Child1>CCC</Member2.Child1>
5      <Member2.Child2>DDD</Member2.Child2>
6    </member2>
7 </root>'))
8 /
1 row created.
SQL> set long 1000 pages 20
SQL> --
SQL> select * from ROOT_TABLE
2 /
SYS_NC_ROWINFO$
<root>
<member1>
    <Member1.Child1>AAA</Member1.Child1>
    <Member1.Child2>BBB</Member1.Child2>
</member1>
</root>
<root>
<member2>
    <Member2.Child1>CCC</Member2.Child1>
    <Member2.Child2>DDD</Member2.Child2>
</member2>
</root>
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'testcase.xsd';
3    :schemaPath := '/public/testcase.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attribute
FormDefault="unqualified" xdb:storeVarrayAsTable="true">
6     <xs:element name="root" type="rootType" xdb:defaultTable="ROOT_TABLE"/>
7     <xs:complexType name="rootType" xdb:SQLType="ROOT_T">
8             <xs:choice>
9                     <xs:element ref="member1" xdb:SQLInline="false" xdb:defaultTable="MEMBER1_TABLE"/>
10                     <xs:element ref="member2" xdb:SQLInline="false" xdb:defaultTable="MEMBER2_TABLE"/>
11             </xs:choice>
12     </xs:complexType>
13     <xs:complexType name="member1Type" xdb:SQLType="MEMBER1_T">
14                             <xs:sequence>
15                                     <xs:element name="Member1.Child1" type="xs:string"/>
16                                     <xs:element name="Member1.Child2" type="xs:string"/>
17                             </xs:sequence>
18     </xs:complexType>
19     <xs:complexType name="member2Type" xdb:SQLType="MEMBER2_T">
20                             <xs:sequence>
21                                     <xs:element name="Member2.Child1" type="xs:string"/>
22                                     <xs:element name="Member2.Child2" type="xs:string"/>
23                             </xs:sequence>
24     </xs:complexType>
25     <xs:element name="member1" type="member1Type" xdb:defaultTable="GLOBAL_MEMBER1_TABLE"/>
26     <xs:element name="member2" type="member2Type" xdb:defaultTable="GLOBAL_MEMBER2_TABLE"/>
27 </xs:schema>');
28 begin
29    if (dbms_xdb.existsResource(:schemaPath)) then
30      dbms_xdb.deleteResource(:schemaPath);
31    end if;
32    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
33 end;
34 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> --
SQL> desc ROOT_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "root") STORAGE Object-relational TYPE "ROOT_T"
SQL> --
SQL> desc ROOT_T
ROOT_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
member1                                                                                      REF OF XMLTYPE
member2                                                                                      REF OF XMLTYPE
SQL> --
SQL> desc GLOBAL_MEMBER1_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member1") STORAGE Object-relational TYPE "MEMBER1_T"
SQL> --
SQL> desc MEMBER1_T
MEMBER1_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member1.Child1                                                                               VARCHAR2(4000 CHAR)
Member1.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> desc GLOBAL_MEMBER2_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member2") STORAGE Object-relational TYPE "MEMBER2_T"
SQL> --
SQL> desc MEMBER2_T
MEMBER2_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member2.Child1                                                                               VARCHAR2(4000 CHAR)
Member2.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'ROOT_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          ROOT_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."member1"                                              XMLTYPE
"XMLDATA"."member2"                                              XMLTYPE
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER1_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER1_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member1.Child1"                                       VARCHAR2
"XMLDATA"."Member1.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER2_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER2_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member2.Child1"                                       VARCHAR2
"XMLDATA"."Member2.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member1>
4      <Member1.Child1>AAA</Member1.Child1>
5      <Member1.Child2>BBB</Member1.Child2>
6    </member1>
7 </root>'))
8 /
1 row created.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member2>
4      <Member2.Child1>CCC</Member2.Child1>
5      <Member2.Child2>DDD</Member2.Child2>
6    </member2>
7 </root>'))
8 /
1 row created.
SQL> set long 1000 pages 20
SQL> --
SQL> select * from ROOT_TABLE
2 /
SYS_NC_ROWINFO$
<root>
<member1>
    <Member1.Child1>AAA</Member1.Child1>
    <Member1.Child2>BBB</Member1.Child2>
</member1>
</root>
<root>
<member2>
    <Member2.Child1>CCC</Member2.Child1>
    <Member2.Child2>DDD</Member2.Child2>
</member2>
</root>
SQL>
SQL>
SQL>

Can we move SAP standard Function Group and Table defintion to BW

Dear Forum,
We are in a pilot process of migrating SAP R/3 Custom development objects to our BW client and we have a few questions that we would like to know if possible.
We are currently in the To Be Blueprint Phase of migrating SAP 45B to ERP2005 as a Ramp-Up customer and we need to determine as soon as possible the feasibility of moving one particular Custom application
from our SAP R/3 environment to BW. This application primarily performs computational processing and does reporting of the results at the
conclusion
We have selected one Custom R/3 ABAP program to do a pilot to determine the feasibility of migrating it to the BW platform. This Custom program utilizes objects from standard SAP Function Groups which are non existent in BW. In this particular case Function groups KMS0
(Cost Center Selection) and KAB2 (CO Reporting: General).
Questions:
Are we allowed to move these 2 standard SAP Function Groups to BW ? Would it alter the BW environment integrity as intended and designed by SAP?
If we move the Function Group KMS0 and KAB2 will
SAP support our BW environment if we decide to move them?
Would it be considered a SAP Best Practice to move standard SAP R/3
objects to BW?
Thank you in advance for your help,
Paulo Silveira
[email protected]

Hi Paulo and welcome on board !
Please don't post twice the same question...(look in the other one...)
..and don't forget to rewards the answers...it's THE way to say thanks here !
Anyway, I'd suggest to close this thread to avoid to receive answers in both threads...
Cheers,
Roberto

Cache groups and table join

Hi,
Is there any limitation regarding an SQL query doing a JOIN of tables from multiple cache groups?
Thanks

No limitations. From a query/DML perspective, cache group tables are just like any other table.
Chris

Authorization Group & TBRG

Hello. I wonder what case should I create records into TBRG for.
Generally, authorization group works when I set it to master record (e.g.vendor, customer,account code) and role (from PFCG).
But, in some case, It is required to insert authorization group and its text to TBRG.
Please tell me weather TBRG setting is essencial or not .
Edited by: Julius Bussche on Dec 28, 2009 6:13 PM
Table name corrected.

Hi Yugo,
Table TBRG - Contains all authorization groups and gives information about relation between authorization object and authorization group. Hence its very much necessary you maintain the authgroups in this table.
Also if you want it to appear as a pick list when you click F4 in the DICBERCLES field in object S_TABU_DIS then you should have those valuse maintained in table:TBRG.
There are several threads based on your query which are already answered. just search by "TBRG Auth Groups" in the same forum.
Hope it helps.Let us know if you need any more information from our side.

Authorization Group in Campaign and Marketing plan

Hi,
I have a requirement as campaigns assigned with "X" authorization group, should be viewed/changed by certain set of users. How can I do this? I have created 3 authorization group and assigned to user's PFCG role and also in 3 different campaigns viz but system allowing user to make changes in all of them. Am I missing something?
Please suggest.
Regards,
Nikhil

Hi PP,
I have campaign type lets say "Brand Promotion". User should be able to change/view/delet/create it. But if the authorization group say XXXX assigned to this campaign and if user is not give authorization for this auth group in role under object CRM_CPGAGR ,then user should not be allowed to make changes in the campaign. How can I achieve both of these functionality together? which are all auth objects involved in this?
I want to restict user from changing campaign if not allowed for XXXX authorization group. Even if he is allowed for campaign type "Brand Promotion".
Regards,
Nikhil

Authorization Group in se38

Hi everybody,
what is the use of Authorization group in se38 attribute? can we create and assign our own one?
The actual scenerio which i am facing here is My report should not be viewed by some grop of users. My friend is saying i can do that through the above said one. But i know i can do that using AUTHORITY-CHEK. What i am asking here is can i accomplish this task by the above said attributes.
Points will be awarded.
Thanx in advance.
Gladiator

Hi,
Authorization Checks
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
The following actions are subject to authorization checks that are performed before the start of a program or table maintenance and which the SAP applications cannot avoid:
·Starting SAP transactions (authorization object S_TCODE)
Starting reports (authorization object S_PROGRAM)
Calling RFC function modules (authorization object S_RFC)
Table maintenance with generic tools (S_TABU_DIS)
Checking at Program Level with AUTHORITY-CHECK
Applications use the ABAP statement AUTHORITY-CHECK, which is inserted in the source code of the program, to check whether users have the appropriate authorization and whether these authorizations are suitably defined; that is, whether the user administrator has assigned the values required for the fields by the programmer. In this way, you can also protect transactions that are called indirectly by other programs.
AUTHORITY-CHECK searches profiles specified in the user master record to see whether the user has authorization for the authorization object specified in the AUTHORITY-CHECK. If one of the authorizations found matches the required values, the check is successful.
The access protection system must ensure that only authorized individuals have access to the system and to particular data. For achieving precise application security concerning authorization and to protect confidential data against unauthorized access it is very important to focus on the use of authorization groups.
The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. They usually occur in authorization objects together with an activity.
The table that contains all authorization objects is TOBJ.
The table that contains all activities is TACT.
The table that contains definition of all authorization groups is TBRG.
TBRG -- Contains all authorization groups and gives information about relation between authorization object and authorization group. The description of the authorization groups is defined in table TBRGT.
The field name for authorization group -- BRGRU -- is used to make additional restrictions on authorizations /e.g. for document maintenance/. In authorization objects and authorization checks, there are fields which are checked to verify user authorizations. Customizing objects are combined in authorization groups, and the authorization group is one of the two authorization fields, for example, in authorization object S_TABU_DIS which is in the object class BC_A (Basis - Administration). This object is for displaying or maintaining tables. It controls access using the standard table maintenance tool (transaction SM31), enhanced table maintenance (SM30) or the Data Browser (SE16), including access in Customizing.
Authorization object S_TABU_DIS has the following fields: DICBERCLS - Authorization group, maximum field length is four characters; and ACTVT - Activity (02: Add, change or delete table entries, 03: Only display table contents).
Generally, SAP standard tables are assigned to authorization groups. These assignments can be changed. You can then assign tables manually to a suitable authorization group. To do this, start Transaction SM30 for maintenance view V_DDAT, and create an entry for each of these tables. In V_DDAT is stored the assignment of Tables/Views to Authorization Groups. V_DDAT is cross-client; therefore, it can be viewed and used in all clients.
Note: If you don't make a selection, all tables maintained in Customizing transactions are assigned to authorization groups.
Reward If Helpfull,
Naresh.

What is authorization group?

Hi all,
Can anyone tell me what is authorization group? I always come across this when I am inside pfcg and look into the authorization object.
I know that authorization object groups authorization fields together. And authorization is an instance of authorization object. But how does authorization group fit into this model?
I have read parts of the help manual that mention auth. group is used to manage Z tables, but they never mention the above relationship.
Thanks.

HI Jockey,
The access protection system must ensure that only authorized individuals have access to the system and to particular data. For achieving precise application security concerning authorization and to protect confidential data against unauthorized access it is very important to focus on the use of authorization groups.
The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. They usually occur in authorization objects together with an activity.
The table that contains all authorization objects is TOBJ.
The table that contains all activities is TACT.
The table that contains definition of all authorization groups is TBRG.
TBRG -- Contains all authorization groups and gives information about relation between authorization object and authorization group. The description of the authorization groups is defined in table TBRGT.
The field name for authorization group -- BRGRU -- is used to make additional restrictions on authorizations /e.g. for document maintenance/. In authorization objects and authorization checks, there are fields which are checked to verify user authorizations. Customizing objects are combined in authorization groups, and the authorization group is one of the two authorization fields, for example, in authorization object S_TABU_DIS which is in the object class BC_A (Basis - Administration). This object is for displaying or maintaining tables. It controls access using the standard table maintenance tool (transaction SM31), enhanced table maintenance (SM30) or the Data Browser (SE16), including access in Customizing.
Authorization object S_TABU_DIS has the following fields: DICBERCLS - Authorization group, maximum field length is four characters; and ACTVT - Activity (02: Add, change or delete table entries, 03: Only display table contents).
Generally, SAP standard tables are assigned to authorization groups. These assignments can be changed. You can then assign tables manually to a suitable authorization group. To do this, start Transaction SM30 for maintenance view V_DDAT, and create an entry for each of these tables. In V_DDAT is stored the assignment of Tables/Views to Authorization Groups. V_DDAT is cross-client; therefore, it can be viewed and used in all clients.
Note: If you don't make a selection, all tables maintained in Customizing transactions are assigned to authorization groups.
Check these links too..
http://help.sap.com/saphelp_crm50/helpdata/en/52/671285439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67129f439b11d1896f0000e8322d00/frameset.htm
http://www.sap4.com/contentid-39.html
Thanks,
Susmitha
Dont forget to reward points for useful answers.
Message was edited by: Susmitha Thomas

Hide price in ALL Tx accg to material authorization group or material group

Hello,
I'm currently working on a customer's need which consists in hiding the material price in all transactions (MM, SD, FI...), according to the material master authorization group OR the material group.
The difficulty remains on the fact that users manage the transactions for other materials for which they can see the price.
I've tested some solutions posted on the forum (Tx OMET + user parameter EFB, use of authorization objects M_BEST_EKG + M_BEST_EKO + M_BEST_BSA) but none is satisfying enough.
Please tell me you have an idea that would prevent me from doing transaction variants + enhancements!!
Thanks for your help
Annabelle

> I am unable to find out the Material or the Material Type that is linked with a material authorization group (QMATAUTH).
>
> Do we have a table where I can find the Material Types or the Materials contained in each material Authorization Group (Q_MATERIAL -> QMATAUTH).
You can get teh details on QM authorization group through table TQ01D. YOu can go through the following post for list of QM tables and tcodes.
QM Tables and T codes
Thanks.
Anjan

Check available authorization groups

Hi ,
if a custom table needs to be assigned to an authorization group in SAP.
Which is the transaction to check users assigned to an authorization group?
Currently i have an idea that Assigning and Creating authorization groups are dealt in SE54 but i cannot find a way to check
whether users are assigned to an authorization group...!!!
thanks
kritika

Checking Assignment of Authorization Groups to Tables:
You can also assign authorization groups to tables to avoid users accessing tables using general access tools (such as transaction SE16). A user requires not only authorization to execute the tool, but must also have authorization to be permitted to access tables with the relevant group assignments. For this case, we deliver tables with predefined assignments to authorization groups. The assignments are defined in table TDDAT; the checked authorization object is S_TABU_DIS.
You can assign a table to authorization group Z000. (Use transaction SM30 for table TDDAT) A user that wants to access this table must have authorization object S_TABU_DIS in his or her profile with the value Z000 in the field DICBERCLS (authorization group for ABAP Dictionary objects).
See also:
· SAP Notes 7642, 20534, 23342, 33154, and 67766
· Documentation for RSCSAUTH
Hope this helps.... if not check the following link
If you still don't find, search google 'table authorization groups in sap' - There are good info on web.
You can assign the authorization group to any custom table via SE11 - table - display - utilities - assign authorization group and rest follow the sap help (where to maintain and how to assign) .This is a developer and security persons work.

Authorization Groups and table TBRG

Similar Messages

Maybe you are looking for