Naming Convention - Best Practices

Hi,
Do you'll have a recommendation for naming convention/standards in BPC. I am referring to naming convention for objects like Dimensions, Models, Task Profiles, Data Access Profiles, Rules, Process Flows and so on...
Thanks in advance for your support
Thanks.

Hi Jon,
Usually no. Quite often we try to create names as much familiar to user as we can. Since like: dimensions the ID is what is shown in the reports, and despite have a description, you can't use this description as the main mask for that dimension. So the ID should be a "semantic" name, something the user identify what it is. Models, Rules and Process Flows is the same.
The exception is regarding security. I.e. data access profiles depends on the client you can create some sort of standards. Such as: The security is made by entity and cost center, so my DAP is:
- EEEE_CCCCCCC_T
Where: E = Entity ID
C = Cost Centre ID
T = Type: R - Read, W - Write and D - Denied.
But it's all very generic. The only thing I reckon important is to keep coherence while creating objects.
Cheers.
Lucas

Similar Messages

Naming convention best practice for PDB pluggable

In OEM, the auto discovery for a PDB produces a name using the cluster as the prefix and the database name suffix, such as:
odexad_d_alpcolddb_alpcolddb-scan_PDBODEXAD
If that PDB is moved to another cluster, I imagine that name will not change but the naming convention has been violated.
Am I wrong and does anyone have a suggestions for a best practice naming the PDB's

If the PDB moves to another cluster, OEM would auto-discover it in the new cluster. So it would "assign" it a new name.
As a separate question, would you be renaming the PDB (the physical name) when you move it to another cluster ?
Hemant K Chitale

Naming Files - Best Practices?

Since I began using Aperture (v1.0) I've imported files after first giving them a name such as "EventName 041225-001" etc. this added an extra step outside Aperture if I wanted the filename to match my previous filename scheme:
(Event)(2-digit year)(2-digit month)(2-digit date)-(padded index)
This year (2008) I switched to a 4-digit year to adapt to Aperture, but the index still isn't zero-padded. So, I finally began wondering, "why bother?" Why not just import the files as named by my camera?
1) What are the disadvantage of not renaming my RAW files upon import? 2) What happens when my camera starts to recycle the filenames (already happened once)? What will Aperture do when this happens?

DP Roberts wrote:
Why not just import the files as named by my camera?
I let the Nikon D2x name the pix; I name the folder that Masters live in, and I similarly name the Project.
The plus is that it is easy, and the archived original unedited file can always be easily found if need be. The down side is that every 10,000 images there could be another pic with the same name, but since 2/3 of pix are culled that leaves a pic with the same name every ~30,000 images.
Aperture knows which pic is which anyway. If I need to find an archived original file, yes I may have 5-10 to choose among but it happens seldom and it is easy enough to find the correct pic.
-Allen Wicks

Looking for best practice on naming conventions

Does anyone out there have a best practice on naming conventions that they could share.
I'm starting to find the need to create objects and associated variables and actions.
I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
Thanks
Alan

Hi Alan,
Welcome to Adobe Community.
There are couple of things that you can keep in mind while naming objects.
When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
bitmap images that constitute the new style should be named as follows:
Brightblue1.bmp, an image with no callouts
Brightblue2.bmp, an image with a callout to the right or upper-right
Brightblue3.bmp, an image with a callout to the left or upper-left
Brightblue4.bmp, an image with a callout to the lower right
Brightblue5.bmp, an image with a callout to the lower left
Flash button-naming conventions
Each SWF button contains three layers: a button, an icon, and an action layer.
The SWF filename consists of the following elements:
Acronym for playback control (“pbc”)
Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
Name of the button (“play”).
Hope this helps!
Thanks!

Best practices in Internal table naming convention GT , GS , LT , LS ??

Hi Gurus,
 Are GT_ , GS_ , LT_ , LS_ --- the Best practices in Internal table naming convention ????
 I have seen this naming convetions adhered in standard programs .
 What each one of the below signify
 GT_ , GS_ , LT_ , LS_ ???????
Regards
Jaman
Message was edited by:
 ABAP Techie

Hello
I use the following naming conventions:
- G = global variable
- L = local variable
- T = internal table
- S = structure
- D = field
That's how the combinations look like:
- GT_ITAB = global itab
- GS_STRUC = global structure
- GD_FIELD = global field
- LT_ITAB = local itab
- LS_STRUC = local structure
- LD_FIELD = local field
Function module parameters have to stick to the following rules:
- I = importing
- E = exporting
- [C = changing -> never used]
- IT_ITAB = imported table type (itab)
- IS_STRUC = imported structure
- ID_FIELD = imported field
- ET_ITAB = exported table type (itab)
- ES_STRUC = exported structure
- ED_FIELD = exported field
Depending on their semantics TABLES parameters look like:
- IT_ITAB = imported data
- ET_ITAB = exported data
- XT_ITAB = changing data (import & export)
Here are the conventions for FORM routine parameters:
- UT_ITAB = using itab (data are usually treated like constants; no changes will be transfer - although possible - to the calling program)
- CT_ITAB = changing itab (if it is semantically an exporting itab then one of the very
first statements in the routine is: REFRESH ct_itab. )
- US_STRUCT
- UD_FIELD
- CS_STRUCT
- CS_FIELD
Conventions for class/interface parameters:
- IT_ITAB = importing table type
- IS_STRUC = importing structure
- ID_FIELD = importing field
- ET_ITAB = exporting table type
- ES_STRUC = exporting structure
- ED_FIELD = exporting field
- RT_ITAB = returning table type
- RS_STRUC = returning structure
- RD_FIELD = returning field
Conventions for class/interface attributes:
- MT_ITAB = table type
- MS_STRUC = structure
- MD_FIELD = field
- MC_CONST = constant
Question: Are there any advantages of such elaborated naming conventions?
My answer to this question is: Yes, definitively.
I believe that the advantage of semantically differentiating TABLES parameters of function modules is quite obvious:
CALL FUNCTION 'Z_BAD_NAMING'
 TABLES
 itab1 = ...
 itab2 = ...
 itab3 = ... .
CALL FUNCTION 'Z_GOOD_NAMING'
 TABLES
 it_itab1 = ...
 et_itab2 = ...
 xt_itab3 = ... .
I also believe that my naming conventions clearly enhance readability and maintainability of my programs.
Regards
Uwe

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

Oracle BPEL standard, best practice and naming convention

Hi, folks,
Is there any standard or best practice associated with Oracle BPEL, regarding development, performace, what to avoid, etc? And is there any naming convention for the process, variable partner link name, etc? Similar to naming convention in writing Java code?
Thanks
John

Hi,
Here is the best practice guide:
http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf
Thanks & Regards,
Dharmendra
http://soa-howto.blogspot.com

Best Practices for farm naming conventions

Hi
I wanted to get some basic best practices and recommendations for farm naming conventions when setting up multiple farms in our environment.
what are the do's and don'ts?

First, figure out why you need multiple farms :-)
I generally name machine accounts based on purpose and location, with a numeral. For example, a SharePoint server in Redmond might be:
REDSP01, REDSP02, REDSP03...
And a SQL Server dedicated to this SharePoint farm might be:
REDSPSQL01, REDSPSQL02...
If using a SQL cluster, I might use:
REDSPSQL01A, REDSPSQL01B...
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

EP Naming Conventions and Best Practices

Hi all
Please provide me EP Naming Conventions and Best Practices documents
Thanks
Vijay

Hi Daya,
For SAP Best Practices for Portal, read thru these documents :-
[SAP Best Practices for Portal - doc 1 |http://help.sap.com/bp_epv170/EP_US/HTML/Portals_intro.htm]
[SAP Best Practices for EP |http://www.sap.com/services/pdf/BWP_SAP_Best_Practices_for_Enterprise_Portals.pdf]
And for Naming Conventions in EP, please go through these two links:-
[Naming Conventions in EP|naming standards;
[EP Naming Conventions |https://websmp210.sap-ag.de/~sapidb/011000358700005875762004E]
Hope this helps,
Regards,
Shailesh
Edited by: Shailesh Kumar Nagar on May 30, 2008 4:09 PM

EP Naming Conventions and Best Practices documents

Hi all
Please provide me EP Naming Conventions and Best Practices documents
Thanks
Vijay

Hi,
Check this:
Best Practices in EP
http://help.sap.com/saphelp_nw04/helpdata/en/43/6d9b6eaccc7101e10000000a1553f7/frameset.htm
Regards,
Praveen Gudapati

Best practice for naming convention in BI 7.0

Hi All,
Is there a Best Parctice document for naming convention in BI 7.0?
Thanks,
S.B

hi,
chk this links...
http://help.sap.com/saphelp_nw04/helpdata/en/ba/83343ea7ff6a38e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/da/0318025d64a84b94542641ed77ee74/frameset.htm
hope this helps,
partha

Best Practice, naming conventions and Ownership of accounts NEWBIE

Hi Guru's please be gentle with me, I'm a sales manager in the UK and have been asked to check for best practices in naming accounts and who should own accounts in CRM 2011?For example I have Accounts with several sites and many contacts? How should I name
these and who should own these? The office manager or the sales account manager that handles sales directly?
Please help, I'm getting stressed. I think these are very simple for such a bunch of super gurus...

Hello iBrummie,
Regarding the Accounts and their sites, you can always use accounts and sub-accounts. To achieve this you should create the main Account in CRM and afterwards you can create the sites using the account entity as well and afterwards linking them with the
main account using the "Parent Account" lookup field.
About the ownership, CRM's security model works essentially with:
Business Units
Teams
Users
Security Roles
This depends entirely on the way your company works but what I would do (assuming that the accounts information is shareable in your company) is to make the sales accounts the owners of the records and provide read/write access at a business unit level to
the office managers.
Here is some more info on the matter:
Security concepts for Microsoft Dynamics CRM
How role-based security can be used to control access to entities in Microsoft Dynamics CRM
Please mark as answer if I managed to help you.
Regards,
Pedro

Best Practice for Tranport request Naming

Hi,
We are using SolMan 4.0 during implementation of ECC 6.0.
We have placed the blueprint and we are in configuration phase.
We have a IMG project created in the DEV system and was assinged in Solution Manager project under System Landscape->IMG Projects.
Now that consultants are going to dev system and customizing they are creating their transport requests.
Is there any best practice for the naming convention or the transport requests..
By creating one IMG project for entire implementation is that going to create any problem..!!
Please sgugest.
Thanks & Regards
Mrutyunjay

As per MSFT best practices(Mentioned by Scott) keep it short as much as possible. You can use SP for SharePoint-SUBSite
also check this blog for best practices.
http://www.networkworld.com/community/blog/simple-naming-conventions-improve-end-user-experience-sharepoint-sites
also one more thing you should consider, never use the reserved words into the SharePoint URLs. you will able to create the site/lis/library/folder but when you browse get the 404 errors.
check this blog:
http://www.sharepointblog.cz/2012/04/reserved-words-in-sharepoint-url.html
http://techtrainingnotes.blogspot.com/2012/03/names-you-cant-use-for-sharepoint.html
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

What are the best practices in naming a PDF

Using underscores, spaces, dashes, commas, etc. What is the best way to name a PDF so it can be opened on all browsers and all platforms?

Hi Gina D 3333,
Best-practice file-naming conventions for PDF files are the same as for any other file. I found this article on Apple's website that contains some useful pointers to consider when you're naming files that will be used on multiple platforms: OS X: Cross-platform filename best practices and conventions
I hope this helps!
Best,
Sara

Best Practice for naming share point URL

Hi,
Could you please help on this.
If we have,
Site Name : SharePoint Sub Site
URL : SharePoint-Sub-Site or SharePoint_Sub_Site (I would prefer one of these two options) which option is best ( - or _) as per the best practice. I do not want to keep it very short.
Thanks.
srabon

As per MSFT best practices(Mentioned by Scott) keep it short as much as possible. You can use SP for SharePoint-SUBSite
also check this blog for best practices.
http://www.networkworld.com/community/blog/simple-naming-conventions-improve-end-user-experience-sharepoint-sites
also one more thing you should consider, never use the reserved words into the SharePoint URLs. you will able to create the site/lis/library/folder but when you browse get the 404 errors.
check this blog:
http://www.sharepointblog.cz/2012/04/reserved-words-in-sharepoint-url.html
http://techtrainingnotes.blogspot.com/2012/03/names-you-cant-use-for-sharepoint.html
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Naming Convention - Best Practices

Similar Messages

Maybe you are looking for