Change Existing objects naming conventions in a Query

Hi all,
I Need to change the Naming Conventions of the Query Objects of a Query at the Infoprovider level. Is there any Routine to change the naming conventions or do i need to do it Manually.

Hi gopinath,
mine is also a similar case, the problem with the option u gave me is that our implementation is in EDW environment and rework from the scratch is not an option for me. Is it possible to change the query objects naming convention at particular info-provider level, i have about 200 objects created with random naming convention and to be now changed according to a standard naming convention. I need to also consider how the changes effect other queries and reports as well.. So is there any possible way of Custom coding a routine or a program that can solve my purpose.. has any one gone through the same situation?
thanks,
kishore

Similar Messages

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

Update existing package - naming convention/workflow questions

OK, so we have an existing package:
Adobe_CS6_MasterCollection_en_US_20120910_Install.pkg
Fast forward 1 month...
We now want to update the package so it has latest patches and so it is also renamed:
Adobe_CS6_MasterCollection_en_US_20121010_Install.pkg
How do we do this with AAMEE 3.1...there doesn't seem to be an opportuntity to rename the package.
Is it safe to simply rename the package before we begin to update it? Or can/should we rename it after we have updated it?
And what do we rename...just the *.aamee file? Or do we also need to rename the existing packge that we are updating? Before or after?
Lots of questions....
Our goal/intent is to be able to provide monthly or quarterly updates...this would require our naming convention to show correct date on the package.
Thanks,
Don

Hi,
I understand your problem about maintining the AAMEE packages without renaming them. May be a low cost solution for you right now is to add 1 more level of folder structure where you dont rename the AAMEE packages (and AAMEE package folder name) but rename its parent folder.So if you have an X.pkg made inside X folder on mac, keep this X folder inside Y folder. And you can change this Y manually after successfully updating the package to reflect current status. Doing this, you you are actually changing the path where the AAMEE package is kept on your machine but not the package itself. So you can keep modifying the current package and still maintain the version information.
I completely agree with rahul that the ability to rename the AAMEE package after modifying it is a good utility, but right now this solution may help you in maintainence.
Thanks,
Saransh Katariya | Adobe Systems | [email protected]

BO Business Object Naming Convention

Hi experts,
we are about to implement SAP Business objects (previously using only using SAP BW). As part of the implementation we are creating a naming convention / standard for Webi and Universe. Is there anything published on SDN or the web regarding naming conventions / standards or is anyone willing to share some tips.
BR
Anders

Hi Anders,
In regards to naming your universe objects, please take a look at my blog post re Universe Best Practices (Link: [http://geek2live.net/posts/universe-design-best-practices/]).
I would always recommend naming universe objects (classes, dimensions, measures etc) in business terminology and being explicit in the definition. For instance, an object called 'Sales' could be interpreted many different ways. Is it Sales Revenue, Count of Sales Orders, Count of Sales Order Lines, Average Sales Amount, etc etc?
Your universes should also be named explicitly so users understand exactly what it contains. Another example - a Finance universe could contain many things - is it General Ledger Actuals, General Ledger Budgets, Fixed Assets, Accounts Payable etc..
The most important thing imho, is to define a standard that everyone who is designing universes uses, without exception. Otherwise the standards don't mean anything to the end users.
Good luck!
Josh

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 Conventions for EP

Hi all,
There some official document about Naming Conventions for EP?
Thanks.

Hi,
Portal objects naming convention.
The portal objects should utilize the following naming convention.
Folders: com.companyname.[functional area].[sub functional area].folders.[folder name]
Iview: com.companyname.[functional area].iviews.[Iview name]
Pages: com.companyname.[functional area].pages.[page name]
Transports: com.companyname.[functional area].transports.[Transport name]
Role: com.companyname.[functional area].[sub functional area].roles.[role name]
Worksets: com.companyname.[functional area].[sub functional area].worksets.[workset name]
Hope it helps.
Thanks
Mona

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?

What are the naming conventions we should follow while creating an object

hi
what are the naming conventions we should follow while creating an object in ABAP dictionary, i.e while creating zee table.

Hi,
Namespaces and Naming Conventions
SAP has reserved name ranges for customer objects and SAP objects. Use these customer name ranges to make sure that your objects are not overwritten by SAP objects during the import of corrections or an upgrade.
This documentation lists the customer name ranges for the different system objects.
Only use the customer name ranges. If you do not keep to the name ranges for customer objects you may lose your development objects.
SAP delivers a few system objects with names that fall within the customer name range. These objects already existed when the customer name range was extended from YY/ZZ to Y/Z. These objects are listed in table TDKZ.
Regards

Oracle Object Naming Standards/Conventions

I did a search on the Inet regarding recommended object (table, column, keys, ..., audit columns) naming conventions. I found different approaches, but I would like to know if there's a document with the naming conventions Oracle recommends/is using?
Thanks.

I have visited http://www.dba-oracle.com/standards_schema_object_names.htm
Oracle column naming Standards
Column Naming Standards
Column names should be spelled out whenever possible.
If a column name should exceed 30 characters, reduce the size of the column name in this order:
From the left of the column name, remove vowels from each word in the table name except for the first vowel of each word.
If the column name is still greater than 30 characters, use standardized shorthand indicators. Record this standard for consistent use.
I agree with the author that column names should be spelled out whenever possible. Some Oracle official database examples use abbreviations for column names but
I would prefer to user long Column Name that spells out the actual name.
For example, in Scott/tiger sample database, for EMP table, it is better to spell out the full name of column name so that UI design could be easier for the programmers.
EMPNO Employee_No
ENAME Employee_Name
JOB Job
MGR Manager_Employee_No
HIREDATE Hire_Date
SAL Salary
COMM Commision
DEPTNO Departmen_No
Since Forms Builder 10g and JDeveloper ADF can generate forms/applications using wizards, using a full column name will be better than an abbreviation, as the prompt for Item is automatically converted by Forms,
e.g. The prompt for Customer_Number becomes "Customer Number"
If you use abbreviation in column names, you need to change the prompts of generated forms manually.
Message was edited by:
wyfwong

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

[svn:cairngorm3:] 15438: -Change initialization objects of Cairngorm Parsley extensions to Parsley convention (i.e.

Revision: 15438
Revision: 15438
Author:   [email protected]
Date:     2010-04-15 03:39:34 -0700 (Thu, 15 Apr 2010)
Log Message:
-Change initialization objects of Cairngorm Parsley extensions to Parsley convention (i.e. CairngormModuleLib>CairngormModuleSupport). Every initialization object has a static initialize method and implements Parsley's ContextBuilderProcessor, which allows it to be specified within a ContextBuilder definition.
-API Change in Navigation library: Changed -FirstEnter metadata to Enter(time="first"), -Enter metadata to Enter(time="next") and -EveryEnter metadata to Enter(time="every")
-Added convenience isValid get accessor to ValidationGroupEvent
Modified Paths:
    cairngorm3/trunk/libraries/IntegrationDMS/.flexLibProperties
    cairngorm3/trunk/libraries/IntegrationRPC/.flexLibProperties
    cairngorm3/trunk/libraries/IntegrationTest/src/CommandScopeSample.mxml
    cairngorm3/trunk/libraries/IntegrationTest/src/LocalConnectionConsumer.mxml
    cairngorm3/trunk/libraries/IntegrationTest/src/LocalConnectionProducer.mxml
    cairngorm3/trunk/libraries/Module/.actionScriptProperties
    cairngorm3/trunk/libraries/Module/.flexLibProperties
    cairngorm3/trunk/libraries/ModuleTest/.actionScriptProperties
    cairngorm3/trunk/libraries/ModuleTest/.flexProperties
    cairngorm3/trunk/libraries/ModuleTest/src/CairngormModuleLibRuntimeSample.mxml
    cairngorm3/trunk/libraries/ModuleTest/src/CairngormModuleLibSample.mxml
    cairngorm3/trunk/libraries/Navigation/.actionScriptProperties
    cairngorm3/trunk/libraries/Navigation/.flexLibProperties
    cairngorm3/trunk/libraries/Navigation/pom.xml
    cairngorm3/trunk/libraries/Navigation/src/com/adobe/cairngorm/navigation/landmark/Abstrac tNavigationDecorator.as
    cairngorm3/trunk/libraries/NavigationTest/src/NavigatorSample1.mxml
    cairngorm3/trunk/libraries/NavigationTest/src/ToggleButtonBarSample.mxml
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/contacts/BusinessContactsPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/contacts/ContactsPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/contacts/PrivateContactsPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/ContentPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/dashboard/DashboardFoo terPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/dashboard/DashboardPM. as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/dashboard/NestedChild1 PM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/dashboard/NestedChild2 PM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/dashboard/NestedChildP M.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/messages/MessagesPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/news/NewsPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/tasks/ExpensePM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/tasks/TaskPM.as
    cairngorm3/trunk/libraries/NavigationTest/src/sample1/presentation/tasks/TimeTrackingPM.a s
    cairngorm3/trunk/libraries/ObserverParsley/.flexLibProperties
    cairngorm3/trunk/libraries/PersistenceTest/src/com/adobe/cairngorm/persistence/sample/pre sentation/CreateDatabasePM.as
    cairngorm3/trunk/libraries/PersistenceTest/src/com/adobe/cairngorm/persistence/sample/pre sentation/PeoplePM.as
    cairngorm3/trunk/libraries/Validation/src/com/adobe/cairngorm/validation/event/ValidatorG roupEvent.as
    cairngorm3/trunk/libraries/ValidationTest/src/SampleModelValidationWithCombos.mxml
    cairngorm3/trunk/libraries/ValidationTest/src/combo/ComboDomain.as
    cairngorm3/trunk/libraries/ValidationTest/src/combo/ComboDomainValidatorGroup.mxml
    cairngorm3/trunk/libraries/ValidationTest/src/combo/ComboPM.as
    cairngorm3/trunk/samples/insync/insync-basic/src/InsyncBasic.mxml
    cairngorm3/trunk/samples/insync/insync-modularExtended-contacts/src/ContactsModule.mxml
    cairngorm3/trunk/samples/insync/insync-modularExtended-shell/src/InsyncModularExtendedShe ll.mxml
    cairngorm3/trunk/samples/insync/insync-modularExtended-shell/src/insync/presentation/Expe nsesPM.as
Added Paths:
    cairngorm3/trunk/libraries/IntegrationDMS/src/com/adobe/cairngorm/CairngormIntegrationDMS Support.as
    cairngorm3/trunk/libraries/IntegrationRPC/src/com/adobe/cairngorm/CairngormIntegrationRPC Support.as
    cairngorm3/trunk/libraries/Module/src/com/adobe/cairngorm/CairngormModuleSupport.as
    cairngorm3/trunk/libraries/Module/src/com/adobe/cairngorm/CairngormModuleXMLSupport.as
    cairngorm3/trunk/libraries/Navigation/src/com/adobe/cairngorm/CairngormNavigationSupport. as
    cairngorm3/trunk/libraries/ObserverParsley/src/com/adobe/cairngorm/CairngormObserverSuppo rt.as
Removed Paths:
    cairngorm3/trunk/libraries/IntegrationDMS/src/com/adobe/cairngorm/CairngormIntegrationDMS Lib.as
    cairngorm3/trunk/libraries/IntegrationRPC/src/com/adobe/cairngorm/CairngormIntegrationRPC Lib.as
    cairngorm3/trunk/libraries/Module/src/com/adobe/cairngorm/CairngormModuleLib.as
    cairngorm3/trunk/libraries/Module/src/com/adobe/cairngorm/module/ModuleXMLSupport.as
    cairngorm3/trunk/libraries/Navigation/src/com/adobe/cairngorm/CairngormNavigationLib.as
    cairngorm3/trunk/libraries/Navigation/src/com/adobe/cairngorm/navigation/landmark/EveryEn terDecorator.as
    cairngorm3/trunk/libraries/Navigation/src/com/adobe/cairngorm/navigation/landmark/FirstEn terDecorator.as
    cairngorm3/trunk/libraries/ObserverParsley/src/com/adobe/cairngorm/CairngormObserverLib.a s

Hi Karl,
I'm sorry to barge into this dicussion. I've been trying to get in touch with you regarding Chrome Lib. Have sent a mail at the id given on the Chrome lib website. Kindly reply to that or give your mail id for contact.
M Puns
m_puns AT rediffmail DOT com

Naming Conventions für PDC Objects

Dear all,
has anybody a document describing the naming conventions for PDC Object.
Example:
iv_xxxx for iViews
ro_xxxx for Roles
etc.
Thanks for help
Roman

Hi Roman,
check the SAP ASAP Roadmap for Enterprise Portal which can be found in [the SAP Service Marketplace|http://service.sap.com/roadmaps].
There you have several so called "accelerators" - one of those is a best practice document for naming conventions.
Look at Chapter 3.3.1.3
(I know because it is my slide set setup during an implementation project )
Hth,
Michael

SAP naming conventions: customer DDIC objects, ABAP programming

SAP Note 16466 Customer name range for SAP objects contains the SAP naming conventions for customer DDIC objects. Rule of thumb is that the names reserved for customer objects start with 'Y' or 'Z'. However, this note contains the naming convention for DDIC objects only.
ABAP Code Inspector (transaction SCI) contains the following naming convention for ABAP programming:
- Global types: T_
- Global constants: C_
- Global data: gv_
- Global field-symbols: FS_
- Global parameters: P_
- Global select-options: S_
- Global field-groups: FS_
- Local types: LT_
- Local constants: LC_
- Local data: v_
- Local field-symbols: LFS_
This is the only place I know for ABAP programming naming convention. Does SAP has somewhere else any additional naming convention guidelines for ABAP programming?
Thanks in advance for your help.
Regards,
Jarmo Tuominen

Naming convention guidelines for ABAP programming is available in here: [Manage Successful Customer Development|https://websmp206.sap-ag.de/~sapidb/011000358700004444532001E].
Naming Data Types and Objects
The names of data types and objects have the form: <Classifier>_<Data type>_<Descriptor>.
The names of data types and objects have up to 30 characters.
Exceptions: names of input parameters and select options have up to 8 characters, and <Data type> and _ are omitted.
First component: Classifier
T Data type
C Constant
G Global data object
L Local data object
FS Field symbol
P Input parameter
S Select option
P Formal parameter in form
FM Formal parameter in function
Second component: Data Type
<t> Elementary data type, optionally followed by length
C<n> Type C of length <n>
N<l> Type N of length <n>
X<l> Type X of length <n>
D    Type D
T    Type T
I    Type I
P<d> Type P with <d> decimals
F    Type F
WA Work area
IT Internal table
Third component: Descriptor
Use meaningful English names. Later, your code may be maintained or analyzed by a programmer or support consultant who is not familiar with another language.
Use only alphanumeric characters (A-Z and 0-9) and separate words with underscores (_). Hyphens are reserved for separating components in structured data types.
Examples:
G_I_COUNTER (global counter)
T_IT_BOOKING_LIST (type for list of bookings)
G_IT_BOOKINGS (global internal table of bookings)
PSMOKER (input parameter for smoker flag: note omission of data type and _ for brevity)
Edited by: Jarmo Tuominen on Feb 21, 2011 2:13 PM

Change view angle of 3D grid with existing objects

Hello,
I am new to the perspective grid in Adobe Illustrator and would really appreciate some help. I have created a simple room interior with a 2 point perspective and a view angle of 45 degree. I would now like to display the same room with a view angle of 60 degree. Is it possible to change the view angle of the 3D with existing objects in it or do I have to re-create the room with a different view angle each time? I can change the numbers in the define perspective setting and the grid changes but the room doesn't seem to change with it.
Thanks, Conny

the perspective grid is just a load of fancy guidelines. it can't affect what you draw after the fact any more than a similar grid drawn on paper could.
Wrong. The Perspective Grid is essentially an envelope distortion, and it is live. Otherwise, objects wouldn't automatically reshape as you move them on the plane to which they are attached.
Is it possible to change the view angle of the 3D with existing objects in it or do I have to re-create the room with a different view angle each time?
Even in pre-CC versions, pressing Shift while moving a perspective plane handle moves the attached objects also. Pressing Alt duplicates the objects as they move with the plane.
By the way, though, it's not "3D". Couching your question in the terms of 3D will suggest to some you're talking about 3D Effect.
JET

Changing view angle of 3D grid with existing objects

Hello,
I am new to the perspective grid and would really appreciate some help. I have created a simple room interior with a 2 point perspective and a view angle of 45 degree. I would now like to display the same room with a view angle of 60 degree. Is it possible to change the view angle of the 3D with existing objects in it or do I have to re-create the room with a different view angle each time? I can change the numbers in the define perspective setting and the grid changes but the room doesn't seem to change with it.
Thanks, Conny

NO. You fundamentally misunderstand. It's a drawing aid like any other guide, not a real 3D space. You need to draw from scratch.
Mylenium

Change Existing objects naming conventions in a Query

Similar Messages

Maybe you are looking for