Naming standards for BW queries

where could i get the naming standards for BW queries? Can somebody email me at singhpra(at)yahoo.com. thank you.

Hi Prakash,
in our company we use the following convention:
<Project_ID>_<CUBE>_Q<authorization>N
The Project ID is a 2-digit code for the project, the cube consists of 5 digits. After the Q there's one letter for special authorization purposes, N is a 2-digit-number starting at 01.
Example: P1_STMX1_QA01
This works fine for all our cases.
Greetings,
Daniel

Similar Messages

Naming standards for reports in Business Objects?

Dear colleagues,
I am about to start development of universes, queries and reports in Business Object for a client. Does anyone of you have any tips on naming standards for the reports? The source system that the dataware house is based on is a fund system. Often the name can be some letters and some numbers. Is there any logic behind this that I can follow?
I will sign points!
Kind regards
Silje

Hi Silje,
Naming convetions should really tie in with your own processes. So it hard to say there is one for all.
I generally create a report library. This is a simple list in Excel of the reports. It will contain the following
Report Id: A number that is unique to each report, e.g. 1000
Report Name: A short descriptive name, Monthly_Returns
Report Location: The folder path to the report
Report Description: A full descriptive name
Report Contact: The person to contact about the report, developer or support person
Report Owner: Business Owner of the report
In WebI I would then call the report 1000_Monthly_Returns. I generally use the folder name to point to the area, so in the case of funds this report would be in the Funds folder.
Hope this helps
Alan

How to set naming standards for SQL Developer

I am using SQL Developer version 3.0.04.
In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
Any help in setting such preferences would be appreciated.

Hi,
If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
You can then drag Tables from SQL Developer's Connections tree onto the diagram.
Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
(or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
David

NAMING STANDARDS FOR WEB DYNPRO ABAP

Hi All,
Do we need to follow any naming standards in WebDynpro ABAP, could you please send some documents or any links for Naming Standards .
Thanks,
Raju.

Hi Raju,
This is a very good question which we cant answer as we are not working in your company.
Well, the naming conventions standards vary based on different company Standards. So the best I could say is, check out your company Standards documents to get to understand the Naming Convention standards.
Regards
Raja Sekhar

Naming standard for creating a interface

Hi,
This question to be silly but i want to know
Is there any naming standards to create any interface
like in staging i defined WC_Dim_DS ( warehousecustom table_name dimension staging )
how normally a ODI project naming conventions......?
For interfaces/packages
Any suggestions?
thanks,
saichand.v

My Suggestion is
I_<Target DB>_<Target Schema>_<Target Table>
But if you are loading the table with 2 or more interfaces then you should add an explanation at the end. Explanation can be source system or purpose.
I_<Target DB>_<Target Schema>_<Target Table>_<Explanation>
And definitely schema and table name should contain some kind of metadata. For example divide staging table and final target tables into different schema such as STG and DWH.

Naming standards for Document Routing ID

I was wondering if there are any standards or edits in place for the Document Routing ID? While setting up the X12/EDIFACT Tutorials, it mentioned filling these in, but I did not see anything on how this is used or what format the data should be in.
I ran into an issue trying to use the value of '204' as a Document Routing ID. When this document would be processed by B2B, I would fine errors in the log stating it could not write to the IP_IN_QUEUE because of an "Invalid Agent '204'". Once I changed this value to X12_4010_204, this issue went away.
Since setting up the initial Tutorials, I have figured out how this Routing Id is useful in processing, but still wonder why the value '204' wouldn't work.
Thanks in advance for you input.

Hello,
Can you please try your setup with X12_204.
Rgds,Ramesh

Naming Standards for SAP's Component Model Objects....

In using SAP's Component Model, Scenario 3, there's a great deal of confusion in trying to version tracks, sc's, dc's, etc.
Since SAP does not currently have Best Practices for the use of the NWDI and the Component Model, can someone else provide me with some advice?
Thank you

Hi Peggy,
to find out more about all the NWDI terms it is a good idea to first read the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/01/9c4940d1ba6913e10000000a1550b0/frameset.htm">architecture manual</a> about NWDI/JDI.
Regards,
Benny

DataModeler v3.3.0 - Naming standards template for surrogate keys creation

I'm using DM 3.3.0.734 and in the logical model we now can define in the entity properties to "Create Surrogate Key".
When we use Engineer to relational model, for each entity is automatically created a new column using the naming template {entity}_ID as NUMERIC (without precision) and is defined as primary key.
My questions are:
Is possible to define a different naming standard for surrogate key creation?. We define id_{entiry}
Is possible to set the precision of NUMERIC surrogate key?
If we define entity's column as Primary UID, these columns are included in an unique constraint, but are using the naming standards for PK.
As consequence are created the following:
Unique constraint name: entity_PK
Primary key(surrogate)name: entity_PKv1
There is any way to define naming standards like "{entity}_UID" for unique constraints, or even, "{entity}_SK" for surrogate primary key name?
Can anyone help with some of these topics?
Regards,
Ariel.

Hi Ariel,
Naming standards template for surrogate keys creation I logged enhancement request for that.
How to change those bad names (going to change them one by one is not an option):
1) If those "transformed" unique keys are the only ones you have in relational model then simply can apply naming standards
2) You can write transformation script to do that for you
3) you can use new functionality - search, export to excel file, change the names there (using find/replace will be faster) and return changed data back to relational model
you can find description for that here:
https://apex.oracle.com/pls/apex/f?p=44785:24:13179871410726::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:6621,16
http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-search/
http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-collaborative-design-via-excel/
You should search for _PK, then filter result on Index and you can export result using report functionality (to XLS or XLSX output format). You can create template and include only table and name (of index) as properties to be included into report.
Regards,
Philip

Channel and Dist naming standards

I'd like to solicit any advice on naming standards for Channels and
Distributions. We are in our design phase and looking to put standards
in place that could easily scale to a larger entity if necessary.
Thank you,
Dave

On Thu, 26 Jan 2006 18:30:13 GMT, [email protected] wrote:
> I'd like to solicit any advice on naming standards for Channels and
> Distributions. We are in our design phase and looking to put standards
> in place that could easily scale to a larger entity if necessary.
very hard to do that in a short time.. for channels
1) figure out what you want to patch / install / do
2) figure out which kind of services you have you want to do 1) with
3) figure out which kind of hardware / os you are running 2) on
4) figure out which locations have different requirements to 1) to 3)
5) think about having an at least 2 phase approach, better 3 to rollout
distributions, 2 phase = testing and rollout, 3 phase = testing, initial
rollout, final rollout
for example...
some people would like to patch their webservers... so you create a
webserver channel... but perhaps not all of them have to same content... so
you create another channel for every content
some people would like to use ZDM application distribution so they create
an app channell... but than they figure out they would like to do
loadbalancing in a site so you need one channel for every site...
some people would like to patch their nw server... but it is not a good
idea to rollout the patch to all servers at the same time... so you create
a channel to test the patch, one channel to do a initial install on a
average of you server environment, and another one for the rest of the
servers..
and so on ;-)
best way is to really play around with the product first to find the
limitations to your ideas and after that good planning.
if you put 1 to 5 into the channelname the channels should scale very well
distribution naming is similar
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

CSM/SSLM Naming standards

G'day,
I'm starting to rollout a largish CSM/SSLM configuration and was wondering if people have any good ideas for naming standards.
I can envisage configs becoming quite a mess and very confusing if there are not clear naming standards for all the various components.
Any ideas that others have would be great.
Cheers
Andrew

It's a very good idea to have CSM/SSLM Naming standards

MDM-Naming Standards

Hi all,
I am intend to work with a new client through my my company.
My client dont know about the Naming standards used for MDM.
So i have built a Naming standards . for example if i am creating a new workflow,port,sub table etc,, i dont know what name should i suggest.
And also i want to know the bussiness process between client & company.
For example. creating new requests.
Wiating for valuable reply.
Thanks
Vijay

Hi Vijay,
There is no such predefined Nmaing standard in MDM but there are some recommended ways of writing names for ports and remotes sytems as used by the standard business packages:
Remote system:
MDM
MDC R/3
Business warehouse
Business One
Port:
MDC R/3_Inbound
MDC R/3_OUtbound
Roles:
Business exprt
Data Custodian
Distributor
Master data expert
OCI Subscriber
Users:
Expert
Administrator
Hope It Helped,
Thanks & Regards
Simona Pinto

Development Naming Standards

Hi
To save us re-inventing the wheel, does anyone have a suggested set of naming standards for development in BPEL that they would be willing to share?
I can see that the tutorials follow some sort of standard, but does anyone have anything document we could utilise?
Thanks
Pete

Here's a summary of our BPEL naming conventions. We prefix the BPEL process names with Request_, Reply_, Pub_, Sub_ etc for Request/Reply (sync processes) or Pub/Sub (async processes). For file reads/ftps, we start them with File_ or FTP_. For interprocess activities, we use the following matrix as a guide.
Partnerlinks:
     DBOperationType_Schema_Table (i.e. DBSelect_LOGGER_LOGITEM)
     ENQ_QueueueName (i.e. ENQ_OMS_SYNC)
     DEQ_QueueName (i.e. DEQ_ALLETE_BUS)
     FileOperationType_FileNamingConvention (i.e. FileRead_connectdisconnect)
     WSType_Name (i.e. WSInt_ for internal, WSExt_ for external web service followed by a name for the service such as WSInt_PubLogger)
Transformations:     Transform_Source_Target (i.e. Transform_clientInput_InvokeLogItem)
Assigns:     Assign_From_To (i.e. Assign_clientInput_InvokePubLogger)
Invokes:     Invoke_PartnerlinkName (i.e. Invoke_WSInt_PubLogger)
Receives:     Receive_PartnerlinkName (i.e. Receive_DEQ_ALLETE_BUS)
Hope this helps.
Candace

ODI Naming Standards

Hi All,
If anyone has a naming standards document....can you please forward it to [email protected]
when i searched ...i found a thread regarding this..my replies to that thread is not working.....so opened this new thread.
Regards

hi,
Refer
Naming standard for creating a interface
Thanks,
Saichand.v

Naming standards within the NWDI

As we're getting ready to dive into a development project with the JDI/NDWI/whatever-it's-called-this-week, I'm working on a set of naming standards.
What are other folks using for naming standards for SCs, DCs, Tracks, and so forth? Sap has published some guidelines, but nothing really substantial that could be morphed into a Best Practices document.
Regarding DC names, SAP seems to be all over the map - sometimes the name of the DC is reflected in the package naming withing the public jar files, sometimes there doesn't seem to be any obvious relationship.
A thread such as this could be very useful both for me, and anyone else who is just starting to use the Developer Infrastructure, so let's get a bunch of ideas out in the open, and get a discussion going.

Hi Ken,
Great innitiative. I'll try to start the ball rolling:
I have noticed that the DC name (without SC name) is apparently the key in SDM, i.e. you cannot deploy two DCs with the same name even if these are in different SCs. This means that reflecting at least part of your package hierarchy in the DC names is essential.
Regards,
Thorsten

How to set naming standard that sets max number of words in column name?

Hi all,
Is it possible to set naming standard that sets max number of words in colum (or table) name?
I was looking video (1:08min)
http://download.oracle.com/otn_hosted_doc/sqldev/UserDefinedDesignRules/UserDefinedDesignRules.html
And here you can see how rule is triggered.
"...Name has 2 words; Max permitted - 1".
Thanks a lot

Hi,
you need to create glossary and set it in naming standards for your design.
This document is still valid - http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
Naming standard settings are located :
- DM 3.x - "Preferences>Data Modeler>Naming Standard"
- DM 4.0 - Design dialog>Settings>Naming Standard
If you want only check on number of words then glossary can be empty and you can set "Incomplete modifiers" option in that glossary.
Philip

Naming standards for BW queries

Similar Messages

Maybe you are looking for