Naming Conventions and Other Standards

Does anyone have a set of standards and conventions you use when publishing Captivate Flash files to the Web? I'm looking for a laundry list of settings to check while publishing? Thanks

Hi,
You want to post this to the OWB forum:
Warehouse Builder
Thanks, Mark

Similar Messages

OWB Naming Conventions and Development Standards

Hi all,
I am developing a project in OWB. Could any one give me 'OWB Naming Conventions and Development Standards' document.

Hi,
You want to post this to the OWB forum:
Warehouse Builder
Thanks, Mark

Naming Conventions and Development Standards'

Hi all,
I am developing a project in OWB. Could any one give me 'OWB Naming Conventions and Development Standards' document.
Thanks

Hi,
You want to post this to the OWB forum:
Warehouse Builder
Thanks, Mark

Question about CEP Naming Conventions and or Standards

Hello,
CEP is new to the organization that I am working with. I have been asked to draft a few standards around CEP to help promote standardization and proper reuse of CEP artifacts. Can anyone share with me examples of CEP artifacts with a naming convention or their experiences with naming conventions around CEP in general. This is a living standards document for us. We plan on using CEP heavily going forward. Your experiences will help us start off on the right foot.
Thanks in advance,
JJE
Spelling Edited by: JJ.Everett on Sep 7, 2010 11:16 PM

Hi,
Oracle CEP supports reuse of components in several ways. For example, you can design your application as a set of modules that can be deployed independently (different teams can develop each module). Modules can register services, such as an event source or event consumer, and these services can be used by other modules. So, it's possible to plug modules developed by different teams of developers together and reuse them in different applications or environments. A component instance registers itself as a service when its advertise attribute is set to true in the Spring application context that defines a module.
A component implementation can also register a factory as a service that allows instances of the component to be created by other modules. Section 13.1.5 in the CEP Developer Guide describes this. http://download.oracle.com/docs/cd/E14571_01/doc.1111/e14301/adapters.htm#CIHBHEDA
Hope that helps.
Regards,
Seth

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

Naming Convention and way to locate Table Names in B.I

Hello All,
I like to know information about
How to find a table
Naming convention of table
Important Tables
I will be thankful ,if anyone provide this information..

Hi Path,
I will provide information what i had got through various sources...
1) Identifying Table
The best way to find out from which tables the data source is getting updated is to search in help.sap.com by using the selection criteria "datasource and the name of the data source".
This displays a table which gives the name of the fields and the table names
2) Naming Convention
1./bic/f (cube name) is the fact table of a content cube
2./bic/D (cube name) P is the package dimension of a content cube
3./bic/D(cube name) U is the unit dimension of a content cube
4./bic/D(cube name) T is the time dimension of a content cube
5./bic/D(cube name) I is the user defined dimension of a content cube
6./bic/m (object name) master data of object
7./bic/t (object name) text data of object
8./bic/H (object name) hierarchy data of object
9./BIC/I* SID Structure of Hierarchies
10./BIC/K* Conversion of Hierarchy Nodes - SID
11./BIC/P* Master Data (Time-Ind.): Characteri
12./BIC/Q* Master Data (Time-Ind.): Characteri
13./BIC/S* Master Data IDs: InfoObject
14./BIC/T* Texts: Char.
15./BIC/X* Attribute SID Table: InfoObject
16./BIC/Y* Attribute SID Table (Time-Dep.):
17./BIC/B* Transfer structure PSA/Changelog
18./BIC/A* ODS Active records
19./BIC/F* Info cube F-Fact table
20.BIC/E* Info cube E-Fact table (compressed records)
21./BIC/D* info cube dimension tables
3) Important tables
I has collected some important tables that may help you..
authorization:
RSSTOBJDIR (Management Table for Authorization Objects): Link between specific authorization object and Info source (table used by transaction RSSM)
InfoPackage
RSLDPIO Links datasource to infopackages
RSLDPIOT InfoPackage Text Description
RSLDPRULE ABAP source code for InfoPackages
RSLDPSEL Hardcoded selections in InfoPackages
ProcessChain
RSEVENTCHAIN Event Chain Processing Event Table
RSEVENTHEAD Header for the event chain
RSEVENTHEADT Header for the event chain
RSPCCHAIN Process chain
RSPCCHAINATTR Attributes for a Process Chain
Queries
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
Workbooks
RSRWBINDEX?
List of binary large objects (Excel workbooks)
RSRWBINDEXT?
Titles of binary objects (Excel workbooks)
RSRWBSTORE?
Storage for binary large objects (Excel workbooks)
RSRWBTEMPLATE?
Assignment of Excel workbooks as personal templates
RSRWORKBOOK?
Where-used list for reports in workbooks

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

Naming conventions, corporate governance standards, etc.

We're beginning the process of setting up the Oracle portal in our company to support over 300 communities of practice as well as several other applications. Getting our corporate governance, naming standards, taxonomy usage guidelines, etc. outlined up front (and right!) will be critical to the success of the program. There seem to be infinite options within the portal product.
Have you developed standards, governance, guidelines, etc. for usage within your portal environment? What lessons did you learn along the way? What advice and recommendations would you give someone starting out to do the same?
Thanks.

Hi,
Did You get or made your own portelt and portlet parameter conventions?
If yes could you share it with me please?
At least the viewpoints, cornerstons of it?
Thanks.

Any comments about this code regaarding naming conventions and flow and e

CREATE OR REPLACE PACKAGE SEODS02.ODS_APPEND_REPLACE
AS
/* Description : This procedure will start the process step for moving
data from staging to live table for Append and Replace paradigms
/**************** Change History ***********************************/
/* Date Version Author Description */
-- Global Specifications.
package_name_in VARCHAR2(50) :='ODS_APPEND_REPLACE';
v_location INTEGER := 10;
v_cntl_schema VARCHAR2(20):= 'SCNTL02';
-- Procedure Specifications.
PROCEDURE APPEND_REPLACE_INSERT (job_name_in IN VARCHAR2,
schema_name_in IN VARCHAR2,
proc_cd_in IN VARCHAR2,
proc_step_cd_in IN VARCHAR2,
bch_dte_in IN DATE,
fl_nbr_in IN VARCHAR2,
verbose_log_flag_in IN INTEGER,
pred_check_req_in IN INTEGER,
error_code_1_in IN VARCHAR2,
ibd_id_in IN INTEGER,
proc_step_status_out OUT INTEGER,
sp_hier_inout IN OUT VARCHAR2);
PROCEDURE APPEND_EXPOSE (job_name_in IN VARCHAR2,
schema_name_in IN VARCHAR2,
proc_cd_in IN VARCHAR2,
proc_step_cd_in IN VARCHAR2,
bch_dte_in IN DATE,
data_grp_cde_in IN VARCHAR2,
verbose_log_flag_in IN INTEGER,
pred_check_req_in IN INTEGER,
ibd_id_in IN INTEGER,
proc_step_status_out OUT INTEGER,
sp_hier_inout IN OUT VARCHAR2);
END ODS_APPEND_REPLACE;
CREATE OR REPLACE
PACKAGE BODY SEODS02.ODS_APPEND_REPLACE
AS
PROCEDURE APPEND_REPLACE_INSERT (job_name_in IN VARCHAR2,
schema_name_in IN VARCHAR2,
proc_cd_in IN VARCHAR2,
proc_step_cd_in IN VARCHAR2,
bch_dte_in IN DATE,
fl_nbr_in IN VARCHAR2,
verbose_log_flag_in IN INTEGER,
pred_check_req_in IN INTEGER,
error_code_1_in IN VARCHAR2,
ibd_id_in IN INTEGER,
proc_step_status_out OUT INTEGER,
sp_hier_inout IN OUT VARCHAR2)
AS
/* Local Variables Declaration*/
v_curr_date DATE := CURRENT_DATE;
v_procedure_name VARCHAR2(100):= 'APPEND_REPLACE_INSERT';
v_stg_tbl VARCHAR2(100);
v_act_tbl VARCHAR2(100);
v_whr_clause_out VARCHAR2(1000);
option_in VARCHAR2(30);
v_common_col_list VARCHAR2(10000);
v_stg_col_list VARCHAR2(10000);
v_act_col_list VARCHAR2(10000);
v_query VARCHAR2(10000);
v_thrshld_query VARCHAR2(10000);
v_actl_inpt_query VARCHAR2(10000);
v_proc_step_stat_query VARCHAR2(10000);
v_error_msg_in VARCHAR2(10000);
v_part_val_out INTEGER;
v_row_cnt NUMBER(10);
v_cmit_nbr NUMBER(10);
v_actl_inpt_cnt NUMBER(10);
v_rec_inserted_cnt NUMBER(10);
v_rec_errored_cnt NUMBER(10);
v_thrshld_nbr NUMBER(10);
v_data_grp_query VARCHAR2(10000);
v_data_grp_cde VARCHAR2(30);
v_proc_step_upd_out NUMBER(1);
proc_step_start_out NUMBER(1);
proc_step_status VARCHAR2(30);
handled_exception EXCEPTION;
BEGIN
/* Enable the logging if verbose log flag is 0*/
IF verbose_log_flag_in = 0 THEN
DBMS_OUTPUT.ENABLE();
ELSE
DBMS_OUTPUT.DISABLE();
END IF;
/* Start the Append/Replace Update process step after all the predecessor process steps are complete */
ODS_CONTROL_UTILITY.PROC_STEP_START( proc_cd_in => proc_cd_in,
proc_step_cd_in => proc_step_cd_in,
ibd_id_in => ibd_id_in,
bch_dte_in => bch_dte_in,
job_name_in => job_name_in,
verbose_log_flag_in => verbose_log_flag_in,
pred_chk_reqd_in => pred_check_req_in,
proc_step_stat_out => proc_step_start_out,
sp_hier_inout => sp_hier_inout);
IF proc_step_start_out = 0 THEN
dbms_output.put_line('Process Step '|| proc_step_cd_in ||' started for Process '||proc_cd_in);
/*If process step is successfully started then get the active and stage table names */
ODS_CONTROL_UTILITY.GET_TABLE_NAME( proc_cd_in => proc_cd_in,
proc_step_in => proc_step_cd_in,
ibd_id_in => ibd_id_in,
actv_tbl_out => v_act_tbl,
stg_tbl_out => v_stg_tbl,
sp_hier_inout => sp_hier_inout);
IF v_act_tbl IS NULL THEN
v_error_msg_in := 'Active table name is null. Please check the parameters passed';
option_in := 'others';
RAISE handled_exception;
/* If Active table is not null then get the active partition of the table*/
ELSE
dbms_output.put_line('Active table name is : '||v_act_tbl);
v_data_grp_query := 'SELECT data_grp_cde
FROM '||v_cntl_schema ||'.proc
WHERE proc_id = '||chr(39)||proc_cd_in ||chr(39)||
' AND ibd_id = '||ibd_id_in;
EXECUTE IMMEDIATE v_data_grp_query INTO v_data_grp_cde;
ODS_CONTROL_UTILITY.GET_ACT_PART(tbl_name_in => v_act_tbl,
data_grp_cde_in => v_data_grp_cde,
meta_data_in => 'VIEW DYN METADATA',
part_val_out => v_part_val_out,
sp_hier_inout => sp_hier_inout);
IF v_part_val_out IS NULL THEN
v_error_msg_in := 'Incorrect table name ' || v_act_tbl;
option_in := 'others';
v_location := 20;
RAISE handled_exception;
END IF;
dbms_output.put_line('Active partition for the table '|| v_act_tbl ||' is : '||v_part_val_out);
/*Get the list of active table columns*/
ODS_APPLICATION_UTILITY.GET_TAB_COLS (schema_name_in => schema_name_in,
table_name_in => v_act_tbl,
col_name_out => v_act_col_list,
sp_hier_inout => sp_hier_inout);
v_act_col_list := SUBSTR(v_act_col_list,1,LENGTH(v_act_col_list)-1);
IF v_act_col_list IS NULL THEN
v_error_msg_in := 'Failed fetching columns for ' || v_act_tbl || '. Check for the columns in table name';
option_in := 'others';
v_location := 30;
RAISE handled_exception;
/*Get the list of active table columns and concatenate the columns with 'stg_array(i)' */
ELSE
dbms_output.put_line('Active Table Columns List: '||v_act_col_list);
ODS_APPLICATION_UTILITY.GET_TAB_COLS (schema_name_in => schema_name_in,
table_name_in => v_act_tbl,
identifier_name_in => 'stg_array(i)',
col_name_out => v_common_col_list,
sp_hier_inout => sp_hier_inout);
v_common_col_list := SUBSTR(v_common_col_list,1,LENGTH(v_common_col_list)-1);
IF v_common_col_list IS NULL THEN
v_error_msg_in := 'Failed fetching columns for ' || v_act_tbl || ' and get concatenated with ' || 'STTG_ARRAY' ||'. Check for the columns in table name';
option_in := 'others';
v_location := 40;
RAISE handled_exception;
ELSE
ODS_APPLICATION_UTILITY.GET_TAB_COLS (schema_name_in => schema_name_in,
table_name_in => v_stg_tbl,
col_name_out => v_stg_col_list,
sp_hier_inout => sp_hier_inout);
v_stg_col_list := SUBSTR(v_stg_col_list,1,LENGTH(v_stg_col_list)-1);
IF v_stg_col_list IS NULL THEN
v_error_msg_in := 'Failed fetching columns for ' || v_stg_tbl || '. Check for the columns in table name';
option_in := 'others';
v_location := 50;
RAISE handled_exception;
ELSE
/* Form the WHERE clause on the primary key columns to update the proc_flag
column of appropriate record in stage table */
ODS_APPLICATION_UTILITY.GET_WHERE_CLAUSE( schema_nme_in => schema_name_in,
tbl_nme_in => v_stg_tbl,
trg_id => 'stg_array(i)',
whr_clause_out => v_whr_clause_out,
sp_hier_inout => sp_hier_inout);
IF v_whr_clause_out IS NULL THEN
v_error_msg_in := 'No columns fetched for ' || v_stg_tbl || '. Check for the columns in table name';
option_in := 'others';
v_location := 60;
RAISE handled_exception;
ELSE
dbms_output.put_line('Where Clause is : ' || v_whr_clause_out );
v_thrshld_query := 'SELECT proc_step_thrshld_nbr FROM '|| v_cntl_schema ||'.proc_step
WHERE proc_id = '|| chr(39) ||proc_cd_in|| chr(39) ||
' AND proc_step_cde = '|| chr(39) ||proc_step_cd_in|| chr(39) ||
' AND ibd_id = ' || ibd_id_in;
EXECUTE IMMEDIATE v_thrshld_query INTO v_thrshld_nbr;
dbms_output.put_line('Threshold number for the process step '||proc_step_cd_in||' is '||v_thrshld_nbr||' for the process '||proc_cd_in);
END IF;
END IF;
END IF;
END IF;
END IF;
v_query := 'SELECT proc_cmit_nbr FROM '||v_cntl_schema||'.proc
WHERE proc_id = '|| chr(39) || proc_cd_in || chr(39) ||
' AND ibd_id = '|| ibd_id_in;
EXECUTE IMMEDIATE v_query INTO v_cmit_nbr;
IF v_part_val_out = 999 THEN
/* Execute the dynamic pl/sql block to append the data to the active table*/
dbms_output.put_line('Executing Dynamic Insert Block for Append Paradigm');
dbms_output.put_line('--------------------------------------------------');
v_location := 80;
EXECUTE IMMEDIATE q'{
DECLARE
v_rec_inserted_cnt_in NUMBER(10):=0;
error_msg_in VARCHAR2(1000);
v_dyn_proc_step_upd_out NUMBER(1);
v_rec_updt_cnt_in NUMBER(10):=0;
v_actl_inpt_cnt NUMBER(10):=0;
v_rec_errored_cnt_in NUMBER(10):=0;
v_dyn_option_in VARCHAR2(30);
v_dyn_sp_hier VARCHAR2(30);
v_dyn_handled_exception EXCEPTION;
v_dyn_verbose_flag NUMBER(1):=0;
CURSOR c IS
SELECT }' || v_stg_col_list ||
' FROM ' || v_stg_tbl ||
' WHERE fl_nbr = ' || fl_nbr_in ||
' AND proc_flag = ' || chr(39) || 'N' || chr(39) ||
' AND to_date(bch_dte,'||CHR(39)||'DD-MON-YY'||CHR(39)||') <= '||CHR(39)|| bch_dte_in || CHR(39)||q'{;
TYPE array IS TABLE OF c%ROWTYPE;
stg_array array;
BEGIN
/* Enable the logging if verbose log flag is 0*/
IF v_dyn_verbose_flag = }' || verbose_log_flag_in || q'{ THEN
DBMS_OUTPUT.ENABLE();
END IF;
OPEN c;
LOOP
FETCH c BULK COLLECT INTO stg_array LIMIT }'|| v_cmit_nbr ||q'{;
FOR i IN 1..stg_array.COUNT LOOP
BEGIN
INSERT INTO }' || schema_name_in || q'{.}'|| v_act_tbl || q'{( }'|| v_act_col_list ||q'{,crte_pgm, updt_pgm, crte_tstp, updt_tstp, expsd_rec_ind) VALUES }' || q'{ ( }' || v_common_col_list || q'{,'}' || job_name_in || q'{','}' || job_name_in ||q'{','}' || v_curr_date ||q'{','}' || v_curr_date||q'{','N' );}' ||
q'{
v_rec_inserted_cnt_in := v_rec_inserted_cnt_in + 1 ;
v_actl_inpt_cnt := v_actl_inpt_cnt + 1 ;
error_msg_in := 'Error in updating PROC_STAT as inserted';
UPDATE }' || schema_name_in || q'{.}' || v_stg_tbl || q'{
SET proc_flag = 'I' ,
updt_pgm = '}' || job_name_in || q'{',
updt_tstp = '}' || v_curr_date || q'{'
WHERE }'|| v_whr_clause_out ||q'{;
EXCEPTION
WHEN DUP_VAL_ON_INDEX THEN
error_msg_in := 'Record duplicated';
v_actl_inpt_cnt := v_actl_inpt_cnt + 1 ;
v_rec_errored_cnt_in := v_rec_errored_cnt_in + 1;
IF v_rec_errored_cnt_in >}' || v_thrshld_nbr || q'{ THEN
error_msg_in := 'Threshold limit }' || v_thrshld_nbr || q'{ Reached';
v_dyn_option_in := 'proc_step';
RAISE v_dyn_handled_exception;
ELSE
error_msg_in := 'Error in updating PROC_STAT as error';
UPDATE }' || schema_name_in || q'{.}' || v_stg_tbl || q'{
SET proc_flag = 'E',
-- err_code = }' || error_code_1_in || q'{, --need to uncomment once the err_code column is created in stage table
updt_pgm = '}' || job_name_in || q'{',
updt_tstp = '}' || v_curr_date || q'{'
WHERE }'|| v_whr_clause_out ||q'{;
END IF;
END;
END LOOP;
EXIT WHEN c%NOTFOUND;
END LOOP;
CLOSE c;
ND ODS_APPEND_REPLACE;
/

DUPLICATE
Any suggestions about this program to improve performance and effective cod

BPEL naming convention

Hi Folks,
I am looking for Oracle BPEL naming convention and coding standards. Tried to search at oracle site as well as on internet but didnt find anything.
Could you please help me with some document/link for naming convention and coding standards.
Thanks
Amit

Hi Amit,
Was able to pull this info from my inrenal repo..thanks to the people who made this :)
Naming Convention: ActivityDescription_suffix_
* ActivityDescription should use camel casing.
copyLeadInfo_asgn
Process Activities
     Services
     ESB Services
Item      suffix      Item      suffix      Item      suffix
Assign      asgn      AQ Adapter      aq      Routing Service      rs
Compensate      cmpnst      Database Adapter      db      SOAP Service      ss
Decide      dcd      Decision Service      dsvc      Custom Adapter      ca
Email      eml      EJB Web Service      ews
Empty      ept      File Adapter      fl
Fax      fax      Java Web Service      jws
Flow      flw      JMS Adapter      jms
FlowN      flwn      MQ Adapter      mq
Human Task      hmntsk      Oracle Applications      oraapps
Invoke      invk      Partner Link      pl
Java Embedding      jvEmbd      FTP Adapter      ftp
Pager      pgr
Pick      pck
Receive      rcv
Reply      rply
Scope      scp
Sequence      sqn
SMS      sms
Switch      swth
Terminate      trmnt
Throw      thrw
Transform      xfrm
Voice      vc
Wait      wt
While      whl
Sensor Actions      snrctn
Sensor Activity      snsrcvt
Sensor Variable      snsrvrbl
Fault Sensor      snsrflt
Also, you can refer : http://my.oracle.com/portal/page/myo/emea/Communities/Technology/EMEA_SOA_Integration/KA
Hope it helps!
Regards
Anirudh Pucha

Data Modeler - Naming Conventions

I was using Oracle Designer for several year.
This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
Naming conventions as example:
We work with surrogate keys.
Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
They have one relation 1:N one department has many employees
In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
Then i would create a relation between this two tables.
Last step is to generate the relational model.
a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
It was really easy to get your scripts.
Things i don't understand in Data Modeler:
In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
P.S.
Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
There is no support for surrogate keys in current release.
Philip

Naming Conventions

Hi All
Im new to BI implementation
Can any1 Please Tell me the Naming Convention to be Given for a Scenario which is Completely Customised.
Please Specify the Naming Conventions for each of the Following Objects:
1)Datasource
2)Infopackage
3)Transfer Rules
4)Infosource
5)Update Rules or DTP
6)DSO
7)Update Rules
8)Cube
9)Multiprovider
10)Query
11) Infobjects
Points are assured
Thanks

Hello,
There is no specific Naming convention and it all depends how the company adopts, anyway you can use these naming conventions for better understanding
Please find the naming convention in the end of each line
1)Datasource - DS
2)Infopackage - IP
3)Transfer Rules - TR
4)Infosource - IS
5)Update Rules or DTP UR or DTP
6)DSO - DSO
7)Update Rules - UR
8)Cube - IC
9)Multiprovider - MP
10)Query - QRY
11) Infobjects - IOC (Chars) or IOK (Keyfigures)
Sometimes its better if your are Customizing the standard to prefix with Z .
Example if you want to customize 0SD_C01 InfoCube, then ZSD_C01 will be easy to maintain
Thanks
Chandran
Edited by: Chandran Ganesan on Mar 7, 2008 3:02 PM

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

Role Naming convention

Good Morning All..!
I have a brand new sand box SCM, I am creating new roles on the system..
The roles should meet the Global naming standards, team want to go with location, system and org. unit in the naming convention..
I came up with
Eg:
ZM_US_SCM_0101AB_XXXX_ALL (Business role)
Description of above example:
M= Role type..like configure/x, composite/c......
US= location
SCM=system
0101AB=company and dep code
xxxx= role description
I wonder how to customize the naming convention for Basis, Helpdesk, security, abap and configuration
Am I complicating the role name?
Team want location code in the naming, so please suggest how should I go about it......?
Thanks in advance..!

Hi Anil,
I'm sure it is important to you, but please don't forget that a good number of posters on this board are based in Europe and the time you posted is end of working day for those on the mainland.
There are always many ways to do naming conventions and there is no right answer.
First of all, you talk about "global naming convention" - are there other non-SRM implementations that have roles created? If so, what is their naming convention? It may be worth using whatever they are using so as to retain consistency across environments.
What you want from your naming convention is the ability to search easily and to identify the purpose of roles.
Your naming convention contains a load of useful data but depending on how you use it, you may want to move some of the elements around
First of all, they don't have to start with Z. Avoid S but the rest is fair game, though Z is very safe.
Role Type: Stick to the technical type of the role here, don't mix composite and config for example. Composite, derived, parent etc make sense if you need the info.
Location: Is this more important that the system? if you search on US roles then maybe not, your call.
System: as above
Company and dep code: Usually I prefer this later on. This is because I typically search on type of role, func area, variant/description and then company or org unit. Again it is your call and nothing wrong with your suggestion.
Role description: Personally I prefer to use a numerical system here. The reason for this is that role descriptions change and transactions in a role change. By sticking to numbers then I find that when these things are changed, you don't have to worry so much about the role no longer matching the description.
depending on the build requirements, I find something like the following is reasonably flexible
ZS_R3_UK_<process area>_<role number>_<org unit>
where <process area> could be fi, ap, security, basis etc
<role number> is an arbitrary number e.g. 00001 - 99999
<org unit> plant/comp code etc - whatever the role is derived to etc
hope that helps

Naming Conventions and Other Standards

Similar Messages

Maybe you are looking for