Forcing naming convention for queries and views

Hello Friends,
Can anyone tell me how to Force user to save queries with starting letter 'Q' and all views with 'V'.
I know how to restrict queries ..
Please tell me how to Froce Views to save with first letter 'V'.
Thanks,
Ram

you need these values in your role to restrict them save queries with starting letter 'Q' and all views with 'V'.
S_RS_COMP
         RSZCOMPID-Q*
         RSZCOMPTP - REP
S_RS_COMP
         RSZCOMPID-V*
         RSZCOMPTP - QVW
S_RS_COMP1
         RSZCOMPID-Q, V
         RSZCOMPTP - REP,QVW
and as you know activity will be 01 for giving create ability, don't forget to restrict on infocube and infoarea. one thing you have to rethink is why you want to use Q, V as a starting letter, I would prefer Y,Z.
and lot of companies do restrict for different naming conventions on different infoarea/infoprovider. just a casual suggestion, it will be better for your company in future, if you restrict the reporting component's naming conventions more specific. something like Zinfoprovider name_reporting component_*.
regards
Message was edited by:
        Keerti Vemulapalli

Similar Messages

Implement a technical naming convention for queries depending on user

Hello,
I'd like to implement a technical naming convention for queries depending on the user, because I want to make sure that the users are taking care of the naming conventions.
For example a user defines a query and would like to save this query.
During the save process he should only have the possibility to save the query with the name C_Name-of-Infoprovider_Text.
The C should be unchageable for the user.
The Name-of-Infoprovider should set automatically (if possible).
The Text could be defined by the user.
Another user would have this naming convention: X_Name-of-Infoprovider_Text
Is there a possibility to implement such a function? (or just a part of this)
Thank you.

Thank you for your answer!
Your answer helped me to implement a part of the naming conventions.
Maybe some as an idea to implement the rest of the naming convention.
--> Technical query name depending on technical name of the InfoProvider.
Has anyone an idea?

Naming convention for packages and classes

Hi all,
Is there any naming conventions for packages and classes which uses a design pattern ?. If yes what are the conventions used for business delegate,session facade, service locator,DAO and any other patterns.
rgds
Anto Paul

Hi,
that is a good question and one we have considered also. We dont yet cover the naming conventions for classes based on patterns but maybe will in the future. Currently, in the blueprints apps we tend to do some things like naminga class
-AccountDAO etc for DAOs
-For servicelocator we have a class called ServiceLocator viewable at https://adventurebuilder.dev.java.net/source/browse/adventurebuilder/ws/components/servicelocator/src/java/com/sun/j2ee/blueprints/servicelocator/web/ServiceLocator.java?rev=1.4&content-type=text/vnd.viewcvs-markup
-for session facade, its a bit trickier since the name is so long and we cant add "SessionFacade" to the end of each facade class. I think in general we put "Facade" in the name, usually near the end
-For Business Delegat, again it seems too long to add to each class name. So in the past we have added
a "BD" to the names of the delegates. Some examples are at http://java.sun.com/blueprints/patterns/BusinessDelegate.html
-For transfer objects we usually add a TO to the end of the name. Some examples at http://java.sun.com/blueprints/patterns/TransferObject.html
Seems like something we could get a bit more consistent about.
hope that helps,
Sean

New query naming convention for Queries in Prod (Y-queries)

Hi,
We are trying to implement a new naming convention for ad-hoc queries in production. Currently we do not allow queries to be created in Production. Users would like to create Y-queries in production. Using security we can allow users to create Y-queries, without being able to create or change Z-queries (z's are official queries).
Can we also allow users to create Y-Calculated or restricted key figures? Is there anything else we need to be aware of?
Thanks,
Mike

Hi Mike,
When we create Y queries in production, we have trouble using Z calculated key figures in those queries. When we try to save the Y query (containing Z calculated key figures) we receive an error "The query could not be saved due to a problem in the transport". I believe it is due to the fact that our Z calculated key figures are transported. To work around this, we recreate the calculated key figure and save it as a Y key figure and then save the query. Not sure if this will happen to you as well, but it may be worth testing to determine if you will need to grant access for your users to create calculated key figures.
Regards,
Charla

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

Oracle Recomanded Naming Conventions for SOA

Hi,
We are working on a 12i implementation project using SOA (BPEL) for interface development and Oracle Data Integrator for conversion. Could you please let us know about oracle recomanded naming conventions for
1. Adapter Service
2. Adapter Connection Factories
3. Routing Services
4. XSD Files
5. XSL Transformation Files
6. ...etc
Is there any oracle corporation provided naming conventions document on these? If so please let us know. Your quick help would be highly appreciated.
Regards

If the names are meaningful (which will depend on what objects are in the different schemas) and the underlying architecture is reasonable, then the naming convention would be a good practice.
- How do the objects in the ABC schema relate to the objects in the ABC_ADMIN schema?
- What, exactly, does the _ADMIN suffix indicate?
My unfounded guess is that you have two related schemas because you're creating one schema that owns the objects and another schema that has restricted access to those objects (ideally just via procedures, functions, and views) for applications to use to log in. If that's the case, it's not obvious to me which of ABC and ABC_ADMIN would own the objects for the ABC application. But if you're actually separating the objects for other reasons, then _ADMIN may make perfect sense.
Justin

Can anyone tell me the naming conventions for PSa tables

hi all,
After the data is loaded into the psa. how to look at the records that are there in psa. And can anyone tell me the naming conventions for psa tables.
like BIC/????
thanxs in advance
regds
hari

Hi Hari,
You want to know the naming convention of PSA table. For that there is a simple technique try this.
Go to - T code SE11
In the database table check box give /BI* and click search
next window in the Description Text box give the r data source name(master) like
YIO_ID_ATTR which is assigned to infosource. then click OK.
then you get the psa table structure.
You can take structure and check in the T code SE 11
Hope this is fine.
Regards
Sreekanth

Naming Convention for path in Application Server

Hello Guru's,
I asked my basis team to create flat file source system. he asked me " what path to follow, any sub directories"?.
they are asking me naming convention for a path in App server to create i think ? usually what will be the naming convention for path.
please help me
Thanks,
Prashanth

Hi,
Create flatfile source system is no need path and sub directory on app server. You can create yourself go TCODE RSA1>Source system>file-->create.
path and sub directory only need if you want to load data from flatfile which is stored in application server. This will be determined in extraction tab of your datasource and infopackage.
Hope this helps.
BR
TRUC

What is the filenameing convention for DVD and why?

Is there any reason to use a button name like "My_Button" rather than "My Button" in DVDSP? I have a book on the subject but haven't run across the rationale for the naming convention using underlines rather than spaces, for instance. It looks like a DOS file name but I just don't know what it is and why such format is used in DVDSP.
I'm using DVDSP 4.

Is there any reason to use a button name like "My_Button" rather than "My Button" in DVDSP?
No, this is not required. In fact Apple use names for buttons in their templates like "Button 1" , "Button 2" et c.
The only reason to name things "Button_1" with an underscore, or "Button1" without a space, is if you like following Unix naming conventions - where spaces aren't possible. This is (quite) useful for files and folders, so that the actual underlying Unix filename is the same as the name that mac OS X displays.
I have a book on the subject ...
The author of your book probably likes to use traditional computer naming conventions for everything, so won't use spaces. Personally I think there's no harm in not using spaces when naming elements "Menu1", "Track1", "Button1" et c. But it is a matter of personal preference.

Naming conventions for CMS tracks

Hello all,
i want to setup CMS for XI transports and create some naming conventions for track id, track name and track description. I studied the howto guides, help.sap.com and searched the forum but i still have no satisfying answer for some questions.
Repository Transports
As i read on a blog it would be a good idea to create separate tracks for each SWCV. To think about an unique name for track id and track name it's worth knowing if one SWCV can be assigned to more than one track. If not the SWCV would be sufficient to identify the track. Otherwise i have to add some prefix/suffix to make the track unique.
Directory Transports
For Integration Directory track there is only one SWC on CMS available, SAP-INTDIR. Is it possible to create two tracks on one CMS with SAP-INTDIR for supplying two independent XI lines with directory content? For example one track for XD1 -> XQ1 -> XP1 and another for XD2 -> XQ2 -> XP2. If so the SWC alone is again not sufficient to identify the track.
If anybody has already thought about naming track id and track name i would be pleased to hear about your approach.
Kind regards,
Frank Opitz

Experts from the JDI forum might help you on this.
SAP NetWeaver Development Infrastructure (NWDI)

Naming Conventions for Workflow

Hello,
does anybody have a document for Naming Conventions for Workflow.
I found nothing the last hour.
Thanks in advance for any help ...
Stefanie

Hi,
I am sending you naming convention which we followed in our project.
Workflow Template & Standard Task:
SAP/R3 Limitations:
Workflow Template & Standard Task names are limited to 12 bytes.
Standard:
Bytes 1-3 of the Workflow Template & Standard Task (see following table) are intended to give an overview of general information regarding the Workflow Template & Standard Task.
Characters 4-12 of the name should be chosen to impart some idea of the Workflow Template & Standard Tasku2019s use and/or contents. (The portion of the Workflow Template & Standard Task name that forms the unique identifier may, or may not, contain underscores characters to enhance Workflow Template & Standard Task name readability.)
Position     Description     Sample Values     Sample Meanings
1     Table system life     Z/Y                Permanent/Temporary
2     Application Type     *                    See Application Designators (Appendix B)
3     OPCO/Region     *                    See OpCo Initial Chart (Appendix A)
4-12     Unique identifier     text                     Unique identifier; may include underscores
Example: ZS7_IDEL9 (I:-Inbound, DEL: - OILDEL 9:- Original)
Business Object:
SAP/R3 Limitations:
Business Object names are limited to 10 bytes.
Standard:
Bytes 1-3 of the Business Object (see following table) are intended to give an overview of general information regarding the Business Object.
Characters 4-12 of the name should be chosen to impart some idea of the Business Objectu2019s use and/or contents. (The portion of the Business Object name that forms the unique identifier may, or may not, contain underscores characters to enhance Business Object name readability.)
Position     Description     Sample Values     Sample Meanings
1     Table system life     Z
Y     Permanent
Temporary
2     Application Type     *     See Application Designators (Appendix B)
3     OPCO/Region     *     See OpCo Initial Chart (Appendix A)
4-12     Unique identifier     text     Unique identifier; may include underscores
Example: ZS7_OILDEL (Business Object for OILDEL Message Type)
Methods
Method names should begin with a verb:
Examples: GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
For Parameters:
IMPORTING parameters     IM_<parameter name>
EXPORTING parameters     EX_<parameter name>
CHANGING parameters     CH_<parameter name>
RESULT     RE_<result>
Events
Event names should have the form
<noun>_<participle>:
Examples: BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Note: There is no specific naming convention for Container Variables in workflow & for Key Fields & Attributes in Business Object. These variables name should be chosen to impart some idea of the variablesu2019 use and/or contents.
Appendix A
ABAP Programming Standards: OpCo/Region Initial Chart
Old #     Company Name                               Proposed #     Accounting Location
98     Common                                                     A              San Ramon
95     FSC                                                     B              San Ramon
80     Chevron Chemical Company                      C              San Ramon
89     Chevron USA-Downstream & General     D     Walnut Creek
75     Chevron Real Estate Management      E     San Francisco
76     Chevron Information Technology Company      F     San Ramon
77     Gulf Oil Great Britain                                    G     London
85     Corporation (Acct. by Corp.)                    H     San Francisco
83     Chevron International Oil company              J     San Ramon
87     Chevron U. K. Limited                               K     England
86     Corporation (Acct. - Local Office)                    L     Various
96     P&M Coal & Mining Company                   M     Denver
94     Corporation (New York)                   N     New York
90     Chevron Pipeline Company                    P     San Ramon
79     Chevron Canada Resources, Ltd.              R      Calgary
92     Chevron Shipping Company                  S                     San Francisco
81     Chevron Petroleum & Tech Co.                  T                     Houston
91     Chevron USA Upstream                  U                     Concord
78     Chevron Canada, Ltd.                              V                     Vancouver
93     CUSA Warren Petroleum                  W     Tulsa
84     Chevron Overseas Petroleum, Inc.            X                     San Ramon
88     Chevron Research & Tech. Company        Y      Richmond
-     Corp. GLX Common validations                   Z      San Ramon
-     PCA                                                   3                     San Ramon
-     Tax                                                   4                     San Ramon
-     Audit                                                   5                     San Ramon
-     Asia-Pacific                                   6                     Global
-     Africa                                                   7                     Global
-     Latin America                                   8                     Global
Appendix B
ABAP Programming Standards: Application Designators
A     Assets Accounting
C     PPC
D     DASS (control station)
E     RIVA/IS-Oil
F     Financial Accounting (incl. Joint Venture)
G     General Ledger
H     Human Resources Planning
I     Plant Maintenance
J     Publishing
K     Cost Accounting
L     Inventory Management
M     Materials Management
N     Hospital
O     unassigned
P     Human Resources
Q     QSS (Quality assurance)
R     PRA (Prod & Revenue Acctg)
S     Basis
T     Projects
U     Enterprise Data Model
V     Sales
W     MMS (Merchandise mgt. System)
X     unassigned
Y     Customer head office
Z     Customer branch
<inappropriate content removed by moderator>
Thanks
Yogesh Sharma
Edited by: Mike Pokraka on Jul 2, 2008 10:34 AM

Help on error message: Naming convention for menu enhancements not observed

Hi all,
I was trying to enhance a transaction and got into entering function code without following naming conventions (i.e. function codes should start with '+'). It is not allowing me to change it by throwing an error "Naming convention for menu enhancements not observed".
This question was previously posted in the thread -- Re: Error in SMOD ?
which was not answered. Can you help me in resolving this error or revert my modifications that I have done while enhancing?
I appreciate any help in regard.
Thank you,
Deepak

You shouldn't get this message if you just create the implementation. I feel that you are trying to change the definition part of the standard extension, using SMOD transaction. That's bad
If you want to enhance, create a project using CMOD transaction, enter the extension name, then simply double-click the +... function code and enter your text.

Powershell naming conventions for functions

There is a lot of information about the Verb-Noun naming convention for cmdlets. I am trying to understand what the recommendation / best practice is for naming functions. Personally, I like the idea that if I see Verb-Noun, I know it's
a cmdlet, and it supports the standard parameters. However, I'm not sure I see the entire picture.
Thanks!

There are as many opinions around this as there are people. TechNet has some good recommendations for naming conventions, but you should adopt whatever standard you are most comfortable with. In the end it doesn't much matter which convention
you adopt, as long as you stick to it and keep it consistent. Most corporate code doesn't get outside or shared with other businesses and vendors, so the whole purpose of standards and conventions is to keep things straight for YOUR people. As
long as you consistently apply your conventions, it doesn't matter.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

Whats most common naming convention for MP3s (what does iTunes store use?)

Trying to organise all my tags and music.
I am using iTunes and some other tag (tag%rename) WMP etc, as some seem to not show all the tgs of other programs)
However what is the generalised, most common naming convention for MP3 files?
ie. track no, Album, artist etc.
Also Ive never bought music from iTunes store yet, only got podcasts and stuff, but when you do , what is the filename convention they use please?
cheers
Mac OS X (10.5) iMac 20" 2Ghz (1st ever Mac Comp)

iTunes has no automatic tag look up function for anything other than CDs (through GraceNote). I import a lot of mp3s (legally obtained) that need tweaking. Also, GraceNote doesn't provide lyrics. If I just need to edit a couple of tracks, the iTunes interface is fine. But for bulk adding of artwork or searching for release dates or lyrics, I use MpFreaker. I find it works best if you do small batches and keep an eye on what it comes up with. Sometimes, well, rarely, it's way off base.
There may be better utilities out there but MpFreaker was recommended to me by someone I trust who spends a lot of time reviewing such things and it works for me so I haven't looked for anything else. You might find more reviews of other software at www.ilounge.com
Best of luck.

Revised naming convention for photo-merging

After a photomerge from Bridge from "Process Collections in Photoshop", the filenames seem arbitrary and could be more helpful.
I would prefer something like the first file in the merge, then either the last, or the count of files involved. Also, consider having the "pano" at the end so it is easier to associate the pano with the files that make up the pano.
IMG_1234.dng
IMG_1235.dng
IMG_1236.dng
IMG_1237.dng
would become either
IMG_1234_4.psd
or
IMG_1234__IMG_1237_pano.psd

john.giarrusso wrote:
Is it possible to change the naming convention for photo's on a device from IMG_0001 (as an example) to something else?
Sorry, no, not on the device itself.

Forcing naming convention for queries and views

Similar Messages

Maybe you are looking for