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

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

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

Business Object Explorer - Convention Excel-Sheet

Hi,
the business object explorer allows to upload excel sheets. i search a convention for an excel sheet because sometimes the excelsheet would not be accept from the business object explorer.
regards,
thomas

Hi,
the business object explorer allows to upload excel sheets. i search a convention for an excel sheet because sometimes the excelsheet would not be accept from the business object explorer.
regards,
thomas

Attributes Problem in Business Object

Hi,
We had a requirement of creating a new Business Object with a couple of attributes(both Database and Virtual Attributes)
So, as per the requirement, I created my Business Object with all the required attributes. And I have coded the required Business Logic for my Virtual Attributes.
Now, I created my Business Object's method's using these attributes(OBJECT-ATTRIBUTE_NAME) in my methods wherever required.
Finally, I tested the Business Object in SWO1(Business Object Builder), here are my observations...
1) The Database attributes is getting created properly and I can see the values for the required
2) The Virtual Attributes are getting created as per the Business Logic and I can see the desired result for this also.
3) The methods are giving desired results.
Now, my doubt is, when I trigger one of this Business Object's method from workflow, the attribute values(OBJECT-ATTRIBUTE_VALUE) are not visible inside the method. But if I test the same BO using SWO1, I can see all the Attribute values(OBJECT-KEYFIELDS).
I can only see the KEY FIELDS of the Business Object in Debug mode, I mean, I can view OBJECT-KEY-KEYFIELD value, but not the OBJECT-ATTRIBUTENAME inside the BO'S method in Debug mode-when triggered from Workflow.
Well, I am triggering the Workflow using the SWUD transaction and infact I am creating the required Instances in the first screen of SWUD.
Can anyone make me clear why this is happening?
Regards,
Raja Sekhar

Hi people,
Thanks for immediate reply.
Well, I think I didnt explain my problem clearly...
Well, here is my clear explanation.
I created a new Business Object named ZOBJECT say...
It has 3 key fields...
PERNR(Employee Number),BEGDA(Start Date) and ENDDA(End Date)
It has 2 attributes...
One is a Databsase Attribute - ENAME which gets populated from database PA0001.
Another is a Virtual Attribute - EMAILID which gets populated from some Business Logic.
And it has one Event...ZEVENT
It has one method...
SENDMAIL - Which sends the email to the EMAILID Attribute.So my coding looks something like this...
METHOD SENDMAIL.
DATA : W_FROMEMAIL TYPE PA0105-USRID_LONG,
 W_TOEMAIL TYPE PA0105-USRID_LONG,
 W_SUBJECT(100),
 IT_TEXT TYPE STANDARD TABLE OF SOLI.
W_FROMEMAIL = '[email protected]'.
W_TOEMAIL = OBJECT-EMAILID.
W_SUBJECT = 'Test Mail'.
Populate the mail content into IT_TEXT Internal table
call function 'YHSENDEMAIL'
 EXPORTING
 FROMEMAIL = W_FROMEMAIL
 TOEMAIL = W_TOEMAIL
 SUBJECT = W_SUBJECT
 TABLES
 IT_TEXT = IT_TEXT.
ENDMETHOD.
So as shown above I designed my Business Object.
And I tested this Business Object from SWO1(Business Object Builder) Transaction itself. I am able to get the desired result. Everything seems perfect till now.
Now, I created my workflow with ZOBJECT-ZEVENT as the Start Event.
I created one Standard Task to send EMail which in turn calls up my ZOBJECT-SENDEMAIL Method.
So when I called this method, I found that OBJECT-EMAIL inside the method is not populated, ultimately, no mail is going.
I dont understand why the attribute values are not populated when I call the same method from workflow.
When I checked the workflow log, I can see my attribute values for the ZOBJECT. But in the Method, I cant access the attribute values as such...But I am able to access the Key fields of the method...
Can anybody explain me the reason for this behavior?
I checked the BINDING, Everthing seems perfect from this side...So I dont think it's a binding problem.
Regards,
Raja Sekhar
Message was edited by: Raja Sekhar

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

Modeling recursive Business Object in Oracle SOA Suite 11g

I'm trying to model a complex Business Object (named Prenda) that contains an attribute of the same type of the object (Prenda) using JDeveloper 11g.
This is my xsd
<?xml version="1.0" encoding="UTF-8"?>
<?bpmo version="11.1.1" build="6.84" fullName="Mx.Org.Frd.Bo.Prenda" modifiers="0"?>






<xs:schema targetNamespace="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns3="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Reloj" xmlns:ns2="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Metal" xmlns:ns1="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Diamante" xmlns="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" xmlns:bpmo="http://xmlns.oracle.com/bpm/bpmobject/" >
 <xs:import namespace="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Reloj" schemaLocation="Reloj.xsd"/>
 <xs:import namespace="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Diamante" schemaLocation="Diamante.xsd"/>
 <xs:import namespace="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Metal" schemaLocation="Metal.xsd"/>
 <xs:import namespace="http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" schemaLocation="Prenda.xsd"/>
 <xs:complexType name="PrendaType">
 <xs:sequence>
 <xs:element name="id" nillable="true" type="xs:long"/>
 <xs:element name="valor" nillable="true" type="xs:decimal"/>
 <xs:element name="precioVenta" nillable="true" type="xs:decimal"/>
 <xs:element name="fechaCreacion" nillable="true" type="xs:dateTime"/>
 <xs:element name="fechaModificacion" nillable="true" type="xs:dateTime"/>
 <xs:element name="tipoPrenda" nillable="true" type="xs:string">
 <xs:annotation>
 <xs:documentation>
 <bpmo:documentable>
 <bpmo:description>
 prenda, grupo, elemento
 </bpmo:description>
 </bpmo:documentable>
 </xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="tipoElemento" nillable="true" type="xs:string">
 <xs:annotation>
 <xs:documentation>
 <bpmo:documentable>
 <bpmo:description>
 diamante, metal
 </bpmo:description>
 </bpmo:documentable>
 </xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="diamante" type="ns1:DiamanteType"/>
 <xs:element name="metal" type="ns2:MetalType"/>
 <xs:element name="reloj" type="ns3:RelojType"/>
 <xs:element name="padre" type="PrendaType"/>
 </xs:sequence>
 </xs:complexType>
 <xs:element name="Prenda" type="PrendaType"/>
</xs:schema>But I'm having troubles to deploy the composite because of the attribute padre is of the same type: PrendaType as my whole object. I'm getting this error:
Caused by: oracle.fabric.common.wsdl.XSDException: oracle.xml.parser.schema.XSDException: imported namespace "http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" must different from namespace "http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" [Cause=imported namespace "http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda" must different from namespace "http://xmlns.oracle.com/bpm/bpmobject/Mx/Org/Frd/Bo/Prenda"]
 at oracle.fabric.common.wsdl.SchemaManager.buildXDKSchema(SchemaManager.java:384)
 at oracle.fabric.common.wsdl.SchemaManager.lookupSchema(SchemaManager.java:216)
 at oracle.fabric.common.wsdl.SchemaManager.lookupXSDElementDeclaration(SchemaManager.java:399)
 at com.collaxa.cube.xml.xsd.SchemaToXML.generateXMLElement(SchemaToXML.java:367)Any idea how to do this?, I was thinking into something like heritage but the IDE doesn't show options to extends the XSD, so I don't know if it is possible.
thanks
Edited by: alfredozn on Nov 9, 2010 12:56 PM

937471 wrote:
When we are working with Correlations in BPEL where the correlation information will be saved in composite or DB ?Why is this relevant? What are you trying to achieve here?

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

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

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

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

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

Enterprise Object (EO) Naming Conventions for Controls

Post Author: rnagahori
CA Forum: Nsite
When naming controls you should follow standard naming conventions. Good names
describe the control, such as prodName, effectiveDate, and dateRequired. Avoid
special characters like "-" ," /", "<" , or ">" when naming your controls.

Post Author: rnagahori
CA Forum: Nsite
Additional notes ... Avoid using the following list of Reserved Variable Names:Application Builder uses several reserved variable names. Please do not use
these as the names of controls, or as variables within Action Builder
routines.
Reserved Names
sum
min
max
avg
abstract
boolean
break
byte
case
catch
char
class
const
continue
default
do
double
else
extends
false
final
finally
float
for
function
goto
if
implements
import
in
instanceof
int
interface
long
native
new
null
package
private
protected
public
return
short
static
super
switch
synchronized
this
throw
throws
transient
true
try
var
void
validate
while
with
_allowSubmitOnError
_fields
_form
_locked
_name
_queue.errorFields
_queue.errors
_queue.validation
_parent
_pointers
_showAlerts
_skipValidation
_status
obj
addEvent
addField
addMethod
addValidator
changedFields
checkForErrors
disabled
dump
forceValidation
hasChanged
getFields
optional
onSubmit
onValidate
removeField
required
reset
setFields
submit
submitCheck
description

User Tables Naming convention / Namespaces

Dear all,
Does anybody know where to get Informations about SBO NameSpace Conventions ?
I have 2 Questions for naming conventions
1) Creating a UserDefinedTable like this
   Table Name : Z_NameSpace_MyTableName
   Is it necessary that any FieldName of the
   table uses the NameSpace Prefix ?
   Like this: NameSpace_PosNo
2) Adding UDF to SBO Tables
   Is it necessary that UDF Fields uses the
   NameSpace Prefix ?
Thanks

Thomas,
The NameSpaces are only used while creating a UserDefined Table.
UserDefined Table :
The convention for the name is NameSpace_MyTableName (without the Z_). Its length can't exceed 19 characters.
When adding a user table, SAP Business One automatically adds the symbol @ as a prefix to the table name. For example: if you add a table named "ABC", the resulting table name will be "@ABC".
When referring to a user defined table you must use the name including the prefix @.
UserDefined Field :
you do not have to add the NameSpace in the name of the field. Its length can't exceed 8 characters.
When you create it using the UserFieldsMD object, the character "U_" will be added to its name, and created in the table.
To conclude, the NameSpace is only used for the table.
The DI API will add @ for the table, and U_ for the field.
You can see SAP note 647987 about NameSpace
Sebastien
Message was edited by: Sébastien Danober

Export-Import and Naming convention question

All,
Newbie here. Have a question related to the naming convention for SAP R/3 system and XI manual export/import process. We are currently in the development environment where our R/3 systems are named as D55CLNT400, D56CLNT300 etc (first 3 characters are the system id, and last 3 are the client number.) This is per the XI best practices convention.
The question i have is - if we name the technical system as above - and export the configuration objects from the Dev to Test environment - where the R/3 systems are named as T55CLNT400, T56CLNT300 (similar naming structure). Does it mean that we need to manually change almost all of the items in the Test environment on the configuration side (like business sytem name, interface determination, receiver determination etc)
Is this the correct way or are we missing something??? I would have preferred a way - where we needed to only update the communication channel parameters.
Thanks.
Message was edited by:
thezone

In the SLD, create three Business System Groups: DEV, QAS and PRD.
In each of these groups, you must have the relevant application servers (in your case, R/3s) and one integration server (XI).
Then, for each Business System in Group DEV, define a transport target in QAS group.
In your case, the transport landscape should be like this:
D55CLNT400 -> T55CLNT400
D56CLNT300 -> T56CLNT300
XI_DEV -> XI_QAS
Do the same for the QAS group (defining transport targets in PRD group). Observe that you need to have the same number of Business Systems in each group for this to work properly.
Now, when you transport your configuration objects from XI_DEV to XI_QAS, all the Business Systems in DEV landscape will be replaced for the equivalent ones in QAS landscape.
More info: http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm
Regards,
Henrique.

BO Business Object Naming Convention

Similar Messages

Maybe you are looking for