ADF BC naming convention suggestions

Ok, I havent found too many topics on this matter, but here is a list of naming conventions our team is debating over. I would also like to hear the rest of the community's thoughts.
Entity: Use underlying table's name and postfix with Eo. If the table is a W view, it should prefix with W.
eg. EmployeeEo, WEmployeeEo
View Object (Single entity based): Use the Entity's name postfix with Vo.
eg. EmployeeVo, WEmployeeVo
View Object (Multiple entity based): Use the primary entity's name followed by a "busniess task" name.
eg. DepartmentEmployeeSearchVo (employee search being the task).
View Object (Non-entity based): Use the primary query table name followed by a "busniess task" name.
eg.EmployeeCountVo
View Link & Association: Combine the master entity name and child entity name postfix with Vl/Ao.
eg. DepartmentEmployeeVl, DepartmentEmployeeAo
(The issue with this is our legacy tables are not that intuitivly named, so its hard to distinguish the master/child tables. I was thinking of splitting it with lets say 2, like Department2EmployeeVl)
Application Module: Apply a "busniess process" name and suffix with AppModule.
eg. AcmeAccountingAppModule.
If anyone has any suggestions or see any conventions left out please post them.
Thanks,
Z

Without discounting your object name conventions, don't forget the Java package they are placed in helps gives context for the object. This is what I tend to do:
com.acme.appmodules
com.acme.entities (all entities)
com.acme.entities.associations
com.acme.views (common VOs)
com.acme.views.links (common VO links)
com.acme.views.reference (common read only VO lookups)
com.acme.views.<business task> (to group logical business VOs together)
com.acme.views.<business task>.links
...the last 2 are repeated for each business task area (eg. HR, accounts, etc)
My ideas partially based on the SRDemo from the JDev team.
Hope this helps.
CM.

Similar Messages

SAP File System Access - SLD Naming Convention/Suggestions

I would like to access our ECC file system to pick up files we will use to create Idocs.
I'm wondering the best way to describe the file system access in the SLD.
I have a business system for the main client on the ECC system (BS_ED1CLNT010) for example but the OS isn't client specific.    I could use this as the Business System in the scenario and define a file adapter that connects to the unix server.
Any thoughts?

Maybe I didn't frame my question properly.
In the ECC system we have multiple clients (20,30,40, etc). If I am going to post an Idoc to a client in this system I need to define each as a business system in the SLD and import this to the Integration Directory.    So I would have BS_XXXCLNT010, BS_XXXCLNT020, etc, one for each client.   These all share the same Technical System.    If I want to post an Idoc to a client on the ECC system I have to define a Business System and interface to that and every client that will receive an Idoc. (as well as the ALE settings on the ECC)
Each of these reside on the same SAP server (sap00001 for example) and there is a directory (/public for example) on this server.     This isn't client specific.
I wish to pick up a file from the ECC file system and post a client on the ECC system (maybe different ones based on the data in the file).
I don't want to define the file adapter under BS_XXXCLNT020 since it isn't specifc to client 020 although that would work.
Do I create a new TS in the SLD as third party, stand alone java, and a BS for that?    TS_XXX_FILESYSTE (3rd party). BS_XXX_FILESYSTEM for the TS?
I'm really looking for clarity in the definition of the SLD.

ADF class naming convention when content compression is turned on

Hi all,
I am a user experience designer and I am now working on a project that requires to use numbers of custom styleClasses, and in order to style the objects to meet the requirements, I referenced the custom styleCalsses in the skin file and everything works fine just as I expected.
But when my colleagues turned on the content compression to boost the performance of the application, all the class names including my custom styleClasses are converted into things like x25, x26, x1nh, x1ni...
So I manually duplicated all the skin css attributes and changed all the class names to the newly generated ones, although this method seems to be working, I am still not sure if this is the safe way and best practice for future development ,because there is no clue to prove that these new class names are static and unique, which means some day my css may lose effect entirely.
Does anyone have the same experience when using content compression and what's your recommendation when dealing with content compression?
Thanks in advance,
Joey

Thank you so much for your reply during the holiday season.
I guess both scenarios exist, I can see some of styles did get picked up, like those on the buttons. But some styles that contain customized styleClass names seemed to have lost track of.
see example bellow:
.........working styles when compression is on.......
.loginButton {
    -moz-box-shadow:inset 0px 1px 0px 0px #7a8eb9!important;
    -webkit-box-shadow:inset 0px 1px 0px 0px #7a8eb9!important;
    box-shadow:inset 0px 1px 0px 0px #7a8eb9!important;
    background:-webkit-gradient(linear, left top, left bottom, color-stop(0.05, #637aad), color-stop(1, #5972a7));
    background:-moz-linear-gradient(top, #637aad 5%, #5972a7 100%);
    background:-webkit-linear-gradient(top, #637aad 5%, #5972a7 100%);
    background:-o-linear-gradient(top, #637aad 5%, #5972a7 100%);
    background:-ms-linear-gradient(top, #637aad 5%, #5972a7 100%);
    background:linear-gradient(to bottom, #637aad 5%, #5972a7 100%);
    filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#637aad', endColorstr='#5972a7',GradientType=0);
    background-color:#637aad!important;
    border:1px solid #314179;
    border-radius: 1px;
    display:inline-block;
    color:#ffffff!important;
    font-weight:bold;
    padding: 1px 15px;
    text-decoration:none;
    text-shadow:0px 1px 0px #39690d;
    position: relative;
    top: -2px;
    left: -6px;
    height: 22px;
......loose track when compression is on......
.LoginUsername .AFPanelFormLayoutContentCell .af_inputText_content {
    height: 18px;
    margin: 2px 3px 0 8px;
    border-radius: 1px;
    box-shadow: 0 0 5px #DDDDDD inset;

Naming conventions in XI !

Hi,
do we have any pdf or blog or links for the naming conventions to be followed in XI?
are there any standard naming conventions suggested or set by SAP for XI?
thank you,
regards,
Babu

Satish,
thank you for quick reply.
this link doesnt work;
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm .
I have downloaded ASAP zip file from one of the link,if you think this is not useful then its fine otherwise can you give me the correct one.
thanks.
Babu

OSB Naming Conventions

Hi ,Can someone provide the OSB naming standards and conevntions to follow. We need it for my current proj.
Thanks.
Srikanth

I doubt if there is any formal naming convention suggested by Oracle.
http://orasoa.blogspot.com/2008/11/osb-standards-and-guide-lines.html has some insights from Marc Kelderman of this forum.

Do you have suggestions for naming conventions within AIF?

Hi Folks!
Being new to AIF I'm currently in the information gathering phase for myself and colleagues as we are starting to think about implementing interfaces with the help of this toolbox. I already found and read (or at least skimmed!) through various of your discussions as well as the very helpful blog posts from Verena, Michal and Andrey.
One of the first things we want to do - before we really get started for real - is to come up with some feasible naming conventions for the various customizable bits and pieces like
Namespace
Interface Name
SAP Data Structure (if applicable?)
We also have some general questions:
Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?
Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?
Searching SCN for "naming convention aif" didn't find anything related and while scrolling through the discussion forum I also didn't see any titles which might go into this direction. In order for us to not re-invent the wheel - or to start off in the wrong direction - I'm hoping to get some helpful pointers from you.
Thanks much for any feedback you have!
Cheers from Germany
Baerbel

Hi Bärbel,
Your question is very good. We had the same and decided for following own approach:
Namespace
A Namespace is a concatenation of business process and SAP module, e.g. O2C_AR, P2P_AP, P2P_MM, R2R_GL.
We have one global namespace for global objects as checks on currency code, date format value mappings, etc.
Interface NameEvery interface has its own name. To be honest for inbound interface the names are more a user friendly description, for outbound we follow a little rule that they start with OUT_.
SAP Data Structure (if applicable?)
We try to do the structure mapping in the middle-ware and AIF is only responsible for the functional mappings.
The root structure name is different between raw data and SAP data. But the sub structure and field names are equal. Because of this we can use the move corresponding fields or in some only monitoring interfaces even move corresponding structures.
We also have some general questions:
Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?Because AIF support and business users differ in different business processes we separated in these processes and modules. In addition the recipients groups are similar to the name spaces.
Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?For namespaces (six characters) and interface names (10 characters) we don’t.
Best wishes
Christoph

AppleScript To Save Messages As PDFs With Specific Naming Convention

I am looking for an Applescript that:
1: Prompts and allows the user to select one or more Apple Mail email messages from within Mail (10.4, 10.5, 10.6).
2: Prompts and allows the user to select a save-to folder.
3: For each message, saves it as a PDF file in the save-to folder, using the following naming convention for the PDF file:
"YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME - SUBJECT",
"YYYY-MM-DD HH.MM.SS Email To FIRSTNAME LASTNAME - SUBJECT",
where in the email date-sent stamp (if I am the sender) or date-received stamp (if I am the recipient):
YYYY = the year
MM = the two-digit month
DD = the two-digit day
HH = the two-digit hour (in 24-hour time)
MM = the two-digit minute
SS = the two-digit second
FIRSTNAME is the email sender's first name for email that I receive (or is the email recipient's first name for email that I send)
LASTNAME is the email sender's last name for email that I receive (or is the email recipient's first name for email that I send)
SUBJECT = the email's subject line
For example: 2010-04-10 16.32.48 Email From Kris Ryan - Status Of Payroll Updates.pdf
For example: 2010-04-10 16.33.55 Email To Sue Anderson - RE Status Of Payroll Updates.pdf (Colon omitted after "RE".)
4: For each attachment to the message, saves it as a PDF file in the same directory using the naming convention:
"YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME Z Attachment - NUMBER - FILENAME",
where:
YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME = as above
NUMBER = an integer representing the attachment number (1, 2, ...) sorted according to filename alphabetical order
FILENAME = the name of the file attached to the email, including its extension (.docx, .xlsx, etc.)
The letter "Z" sorts the attachment PDFs after its respective parent email in the directory.
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 1 - List Of Suggestions To Moore.doc.pdf
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 2 - Proposed Salary Adjustments.xls.pdf
For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 3 - Salary History.pps.pdf
Note: The email attachment may consist of a PDF or MS Office file (Word, Excel, Power Point); however, a smart implementation will be able to handle any attachment kind. If the attachment is a PDF file, then save it "as is" using the stipulated naming convention, without passing it through Distiller.
Thank you.
Kurt Todoroff

Well, that's quite a spec sheet.
Here's a start, you can easily edit the script to get what you need:
<pre style="
font-family: Monaco, 'Courier New', Courier, monospace;
font-size: 10px;
font-weight: normal;
margin: 0px;
padding: 5px;
border: 1px solid #000000;
width: 720px; height: 340px;
color: #000000;
background-color: #E6E6EE;
overflow: auto;"
title="this text can be pasted into the AppleScript Editor">
Set a Mail Rule to Save Message and Attachment to Desktop.
To save attachments to another another folder on the desktop (i.e. Attachments) create the folder and then
change tell application "Finder" to set pathToAttachments to (path to desktop folder as string) & "Attachments:"
using terms from application "Mail"
on perform mail action with messages theMessages
tell application "Finder" to set ptd to (path to desktop folder) as string
tell application "Finder" to set pathToAttachments to (path to desktop folder) as string
tell application "Mail"
repeat with theMessage in theMessages
set d_recd to date received of theMessage as string
set d_recd to ReplaceText(d_recd, ":", " ") of me
set d_recd to ReplaceText(d_recd, ",", " ") of me
set theText to content of theMessage
if theMessage's mail attachments is not {} then
repeat with theAttachment in theMessage's mail attachments
set theFileName to pathToAttachments & (theMessage's subject) & " (Attachment From " & (theMessage's sender) & " Sent " & d_recd & ")" & space & theAttachment's name
try
save theAttachment in theFileName
on error errnum
end try
end repeat
end if
set theFile to ptd & (theMessage's subject) & " (From " & (theMessage's sender) & " Sent " & d_recd & ")" & ".txt"
set theFileID to open for access file theFile with write permission
write theText to theFileID
close access theFileID
end repeat
end tell
end perform mail action with messages
end using terms from
on ReplaceText(theString, fString, rString)
set current_Delimiters to text item delimiters of AppleScript
set AppleScript's text item delimiters to fString
set sList to every text item of theString
set AppleScript's text item delimiters to rString
set newString to sList as string
set AppleScript's text item delimiters to current_Delimiters
return newString
end ReplaceText</pre>

Variable naming conventions

Hi all,
I come from a mostly JAVA background. Big emphasis in that arena on encapsulation and modularization of code to help facilitate ease of maintenance and reuse...in theory I sometimes struggle with variable naming conventions within my ABAP code because I'm not all together certain there are any. In C or C++ I might use a derivation of Hungarian notation to name varaibles...and in JAVA I might observe certain object oriented rules regarding varaible naming...I find myself using a combination of those two protocols in my ABAP code. Does anyone have any suggestions for how I might name global and lcoal variables within my code?
regards,
Mat

Hi,
Please check this links perhaps they may help.
http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm
https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73
http://web.mit.edu/sapr3/dev/newdevstand.html
Regards,
Ferry Lianto

Naming conventions / Naming conventions for Trading Partner Management

Hello Experts,
Can any one share the Naming conventions / Naming conventions document for Trading Partner Management ?
Thanks
Saurabh

Hey Saurabh,
We usually go with the name and description for partners ,
Below blog might help
ISA and GS segments mapping - Value mapping v/s Predefined TPM UDFs - II
Suggestions-
Template - TM_Description
Function Profiles - FP_Description
Partners - TP_Description or PartnerName
Agreement - TPA_Description
Code List - CL_Description
Property key - lower case, description separated by dot (.) ( eg. seg.sep)
TPM Export file - Config_description .tpm
Regards,
Pooja

HR report category naming conventions..

Hi All,
As few of you suggested me in my last post, I decided to assign new HR report category to my report for LDB PNP. Now it does not let me change the selection fields of in-built categories which is quite obvious. Now when i create a new one it gives me the error message of choose the key from allowed namespace?
does anyone know if there is special naming conventions for HR report categories??
i tried Z but does give me the same error..
stuck up..
plz help..
Reena..

Hi Reena,
I checked ur error. For me also it is giving the same error. I analysed & found as below.
In se38->RDDKOR54 check this report & give table name as T599C.
This will give you the customer name space for this table.
So you can give the name starting with only spscified letters in this report.
So use 0test or anything 0* to 7* it will work.
All the Best!
Thanks,
Sarika.

Adobe Interactive Forms - Standards & Naming Conventions

Does anyone know where I can locate any documentation pertaining to recommended standards and naming conventions for interactive forms within the SAP NetWeaver '04 platform?

Hi David,
I suggest you start here: https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=AdobeForms.htm. This is where we have collected background information, demos, eLearning materials, and links to the standard documentation for the integrated forms solution. We work together with Adobe on the content of this site.
In due course, we will provide more tips & tricks and best practices.

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

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

Transport with CTS+ : Naming convention

Hi SDNers,
I need your suggestion.
This is wrt CTS+.
My doubt is:
I need to transport changes between the Dev, QA & Production system.
I have a repository in Development system: Repo_Dev
Now I want to create a repository in Quality / Production system, similar to Repo_Dev , but with different Repository names as Repo_QS / Repo_Prod respectively. My doubt is, will I be able to create the repositories in the Quality or Production systems with the name I want.... or is it because I am using CTS.. it will create a repository with the same name i.e Repo_Dev.
With reference to the SAP document "Setup und Use the MDM Change Transport with CTS+ Transport Management Environment", my understading is to
1. Create a repository in QS / Production side.
2. Using the option "Create Transport Reference" , I will get a reference file of Repo_Dev.
3. Then Import the reference file in the Repo_QS / Repo_Prod will result in synchronisation between all 3 (Repo_Dev, Repo_QS, Repo_Prod ) repositories.
This way I can have the same Data modelling etc in all the 3 repositories, with the naming convention as required.
If anyone has worked on it... please confirm it.
Thanks & Regards,
Priti Rani Patnaik

Hi Priti,
For transport with CTS+ you need to follow the steps which you have mentioned. You need to create a repository and then import the ref. in this repository. By doing so you are only importing the tables and fields present in your Dev repository. The sync between all three is only related to data modelling and it will not effect the name of reposiotry as you have already created a repository and I guess renaming of repository is not possible.
I hope I am able to help you.
Thanks & Regards
Dilmit Chadha

Implementing Transport Naming convention with the help of BAdIs (Urgent)

Hi Gurus,
We need to implement Transport Naming convention in our landscape.
Transport request should follow the following naming conventions and to enable this we have to enable some necessary BAdIs?
Scenario would be like this....!
Customization
LC-<Track>-<Description> (Non Transportable Request)
<Module>-<Track>-<Configuration Type>-<Change No>-<Description of the Customisation.>
ABAP Developments
AB-<Track>-<Configuration Type>-<Development No>-<Description of the Development>
OSS Notes
BC-<Track>-OSS#<OSS Note No>-<Version>-<Patch Number>-<Process Team>-<Note Description>
Authorization
BA-<Track>-<Version>-<Authorisation Description>
Details :
Track : 01 u2013 Hot fixing, 02 u2013 Implementation, 03 u2013 BIW / EP, 04 u2013 Support
Module : SAP Module (FI, CO, MM, SD, PP, etc..)
Configuration Type : I u2013 Initial Configuration, R u2013 Change due to TPR or Additional Functionality
Change No / Development No : Unique no to trance the base documentation
Please suggest .....................!
Which are the necessary BAdIs needs to be enabled and what other configuration needs to be done.
If anybody has any document please provide.
Thanks in advance..............!!!
Regards,
Jai Sach

Hello,
SPRO --> SAP NetWeaver --> Application Server -->
System administration --> Change & Transport domain
--> BADI -->Business Add-In when Editing Requests
IF_EX_CTS_REQUEST_CHECK~CHECK_BEFORE_CREATION
Happy Tony

ADF BC naming convention suggestions

Similar Messages

Maybe you are looking for