Skip to Content

Role and Naming concpets

Hello All,

While creating custom roles(Z&Y), could anyone explain the importance of having a good naming convention?

Thanks a lot in advance.

Regards, Pradeep

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 02:16 PM

    Pradeep,

    You should create a naming convention in order to make your life easier in the future.

    Imagine having a bunch of roles with numbers that you don't know. I suggest you to do something like this:

    Yxx:vvv.yy_vvv

    xx = to module

    vvv = sequence

    yy = to contry code (yf you do not have different contries than you could use company code, or plant)

    Any questions let me knwo.

    Best Regards,

    Lucas

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Certainly you have to make the standard fixed and describe it. Try to get the document describing your naming convention signed off at highest management level!

      On Org qualifiers be certain to get the right info from business. I have seen big mess made out of that

      as finance people wanted the financial Org Qualifiers to show in the naming convention while others wanted to stick to the organisation like company , plant etc.

      Best approach is to look at how the organization is fiscally situated, like in which office/companies sit and make it as simple as possible.

      One more thing about Org Qualifiers (derived roles) be sure not to use them simply because they are there but ONLY when there is a risk leaving them on STAR (*) this mostly limits the number of qualifiers to be populated to a reasonable number and also gives a nice handle on how to organize your Org Level naming convention.

      Tip Company code is 4 positions in SAP so why not use that code in the naming convention, mostly it looks like 0040, 0060 etc. If you need to go deeper (like to office or plant level you might use 0021, 0022 etc.

      On naming Convention with regards to composites and Singles be sure to make a distinction, here are some examples I have used in the past:

      SINGLE ROLE: Z: or A: or Z_

      Composite role Y: or C: or C_

      What you use is not so important (advise do not use S as that is the starting letter of SAP standard roles)

      The format I prefer : Z:R3_FIN001_0200

      Z= single role

      R3 = SAP R/3 , also BI or BW etc

      FIN= Finance role

      001 = first role in sequence

      0200 = company code as in Org level field BUKRS and for the master roles (basis for derivation) i use XXXX and for roles that have wide access CCCC. If the roles does not contain org fields I use the XXXX varaint in the composites.

      Hope this helps you on the way?

  • Posted on Jun 25, 2008 at 01:41 PM

    It's a bit of a no brainer really

    good naming convention:

    - Easy to identify purpose of role

    - Identify important restrictions (e.g. org level/business unit)

    - gives consistency

    - makes role admin easier

    - Reduces communication errors

    - Makes role reporting easier

    there are plenty more reasons which I'm sure others will chip in

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 01:56 PM

    Hi,

    Others coventions you can use is that you can differenciate between different type of roles:

    for eg

    M for master roles

    D for derived

    C for composite roles

    S for single roles

    These are just examples..Y ou can use your own naming coventions so that you can differenciate between these types of roles

    Regards,

    Tajinder

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 02:23 PM

    I'm a developer (non-ABAP) turned security admin, so it was a no brainer for me after programming for 15 years. We've developed a standard to support our entire landscape of systems with a consitent naming standard.

    <h2>Role Names</h2>

    Role names will be prefixed with Z, followed by three identifiers that are separated by an underscore.

    Z<System Type><Role Type>_<Group ID>_<Description>

    <h2>System Type</h2>

    The following table lists the valid System Types

    ID Description

    E ECC

    G GTS

    B BW

    X XI

    <h2>Role Type</h2>

    The following table lists the valid Role Types

    ID Description

    M Master Role

    D Derived Role

    S Single Role

    C Composite Role

    T Test Role

    <h2>Application Identifier</h2>

    ID Description

    CO Controlling

    FI Finance

    LE Logistics Execution

    QC Quote to Cash

    RP Request to Payment

    BC Basis

    BI Business Intelligence

    DV Development

    <h2>Description</h2>

    u2022 Meaningful abbreviation of role purpose

    u2022 To include clear indications of functional job role, an indication of purpose, and a possible identifier for organizational value indicators (i.e. division / plant / company code) that are used for derived roles.

    Examples

    u2022 ZEM_QC_CUST_SERV_REP

    o Master Role for Quote to Cash Customer Service Representative

    u2022 ZED_QC_CUST_SERV_REP_1340

    o Derived Role for Quote to Cash Customer Service Representative for Sales Organization 1340

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 07, 2008 at 12:31 PM

    Hi,

    For Roles definetly naming convention should be maintained.

    It will be easy for us to make work easy.

    See make naming convention of roles in such a way that for Roles having transaction codes can be named as zt_..... and roles that contain only infotypes can be named as za.......It can be easy to differentiate roles and easy to assign to users or to do modificationswhen required.

    Regards,

    Parimala

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.