cancel
Showing results for 
Search instead for 
Did you mean: 

Best practice in defining permission for custom catalogs and groups

subhab1
Explorer
0 Kudos

Hi Experts,

We are using many standard apps from standard catalogs. However we don't want to use SAP id/namespace.

What we have though of:-


Technical Catalogs:
We are planning to create a copy of the standard Technical Catalog and change the SAP in the id to Z_CompanyName_TC_*

Business Catalogs
We are planning to create fresh catalog Z_CompanyName_BC_*, however, to speed things up, we are planning to copy target mapping and tiles from one or more standard catalogs

Business Groups
We are planning to create fresh group Z_CompanyName_BG_* and add tiles from custom Business Catalogs created above.

I have a question here, when copying, the ststem creates a reference, rather than duplicating the catalog/target mapping/tiles etc. Would it be a problem in PFCG role assignment if we assign a role the custom technical catalog, business role and group without assigning the standard technical role/catalog/group?

What is the best practice proposed here?

Accepted Solutions (1)

Accepted Solutions (1)

kammaje_cis
Active Contributor

It is not an issue. You can assign the custom catalog with references to the PFCG role, without assigning the standard catalog to the same PFCG role.

subhab1
Explorer
0 Kudos

Will try this and check. However bit surprised why SAP used the word Reference instead of Copy, if really they can act as independent catalog after doing a "New Catalog with Reference"?

kammaje_cis
Active Contributor
0 Kudos

There are two parts to it.

It is still a reference in terms of target mapping/tile definition. But for authorization purpose, they behave independently.

Otherwise, there is no use of creating the new catalog with reference target mappings/tiles isn't it?

Answers (0)