IP Naming Convention Recommendation

Hello all!
Do any of you have a recommendation on how to name agg levels, filters, functions, sequences, and queries in IP?
Thanks
T

Hi Tim,
I have put together a naming standard for my IP project and it is approximately:
where ff is the functional area
         nn is a number for cubes, aggregation level, etc.
         mm is a sequential number for filter, functions, sequences, etc.
         xxx os a sequential number for queries, layouts, WAD templates.
ZIPff_Cnn - basic cube
ZIPff_Pnn - Planning / Realtime Infoprovider.
ZIPff_Onn - ODS
ZIPff_Mnn - Multi-Provider
ZIPff_Ann - Aggregation Level
ZIPff_Ann_FIL_mm - Filter
ZIPff_Ann_PF_mm - Functions
ZIPff_Ann_PS_mm - Sequence
ZIPff_Ann_Qxxx or ZIPff_Cnn_Qxxx - queries / reports
ZIPff_Ann_Lxxx - input enabled query Planning query / layout
ZIPff_Ann_Wxxx or ZIPff_Cnn_Wxxx - WAD template, etc.
If you want more specifics, E-mail me.
Cheers,
Mary

Similar Messages

Enhancements Naming Conventions - Recommended

Hi All,
Can somebody suggest me the Recommended Naming Covention for:
1. Project
2. Business Add-In Implementation
3. Composite Enhancement Implementation
4. Composite Enhancement Spot
5. Enhancement Implementation
6. Enhancement Spot
Thanks,
Prashant Singhal

It really does depend on the project. Each project has its own defined standards but some examples are below.
Datatype: DT_
Message Type: MT_
Message Interface: MI_<Async/Sync>_<Direction>_
Message Mapping: MM_<SourceMessage>_<TargetMessage>
Message Interface: IM_<SourceMessage>_<TargetMessage>
Communication Channels: CC_<AdapterType>_<Send/Recv>_
Integration Process: IP
These are just a few and should give you some idea... but the main thing is to make sure they are always meaningful and easily distinguishable.
But as I said each project has its own flavour

Logical System Naming Convention

Hi Guruz,
Is it mandatory to name your logical system starting with SAP system name. I went through SAP Documentation for creating logical system, it says <sap system name>CLNT<client number>. I didn't put my SAP system name for the first part<sap system name> instead some random letters. I know this question may sound stupid but I am right now in the middle of the integration so, I don't want to change it. Please confirm.

I'm work for the customer who has ~4000 logical systems defined (not all represent SAP boxes though). Which I find quite a lot, yet given the rules of naming convention helps a lot.
I would say that having the system name should be used whenever we talk about Logical Systems representing SAP boxes. But in case of external non-SAP applications, it is helpful to represent them by the external system.
Say, you have 20 SAP installations, each sending interface to application A. Then it is easier to monitor in XI/PI interfaces for single receiving logical system 'A'. But if you want to find out messages from given sending SAP system, then using SAP system name is recommended to extract such data quickly.
Regards,
Dominik Modrzejewski

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.

SAP Naming Conventions for DB Data Files

Hi Everyone!
We are about to install a SAP ECC 6.0 SR3 ABAP on Windows Server 2008 (R2) & SQL Server 2008 SP1 and we want to name the DB data files as follows:
<sid>DB_Data_001.MDF/NDF
Do you see any problem with this or think this could lead to a problem in the future?
We were unable to find a SAP note or SAP recommendation about this, we only found SAP Note 27428 but itu2019s for Oracle.
Thanks in advance!
Best Regards,
Nicolas

Hi Nicolas,
I thought about all corners where this could possibly lead to a problem (e.g. monitoring, DB13, ...) but couldn't think of a single report or transaction where this would cause problems.
To the database itself the names of the files do not matter at all and in the SAP transactions the datafiles are only read to display them in monitoring transactions like DB02 or RZ20. These transaction do not expect a certain naming convention so I don't see anything that would count against using different filenames.
Regards,
Beate Grötschnig

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

Best Practices for farm naming conventions

Hi
I wanted to get some basic best practices and recommendations for farm naming conventions when setting up multiple farms in our environment.
what are the do's and don'ts?

First, figure out why you need multiple farms :-)
I generally name machine accounts based on purpose and location, with a numeral. For example, a SharePoint server in Redmond might be:
REDSP01, REDSP02, REDSP03...
And a SQL Server dedicated to this SharePoint farm might be:
REDSPSQL01, REDSPSQL02...
If using a SQL cluster, I might use:
REDSPSQL01A, REDSPSQL01B...
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

PI SWC Naming convention

Hello, I've read this SAP [document|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40a66d0e-fe5e-2c10-8a85-e418b59ab36a] about best practices naming convention and I still don't have a clear idea about how many software components I have to create in 1 scenario.
There are 3 posible ways in the document:
- 1 SWC with all the ESR objects - Not recommended.
- 2 SWC one with the receiver objects and the other with the sender objects. But where you keep the mapping objects??? Always in the sender SWC? Always in the Receiver???
- 3 SWC with receiver, sender and mapping objects respectively. I don't like that solution because I think that the SWC object loses its meaning and you will have all the objects of a simple scenario "spreaded" along the ESR.
Have you an better alternative to help me???
Best regards,
Marshal

Thank you for your answers.
It looks like it's really personal to decide which its the better option to define the SWC. I will think about it...
To Madhusudana Reddy and abhishek salvi: I think that organization way it's very clear but if you do that, the SLD is meaningless, because you are using a SWC as a "business area" not as a software, and I'm not sure about it. Maybe the problem is how the SWC object is used in SAP PI.
To Patrick Koehnen: I think that the 3 SWC approach is too much confusing too, and the 3rd SWC with the mappings it's not really a "software" of our landscape....

When using Creative Cloud Library assets created in Illustrator why are the naming conventions I use not being pulled over into the Photoshop layers?

I create the Creative Cloud Library asset in illustrator and give it a name such as "camera-icon". It shows up in my Creative Cloud Library pane in Photoshop as "camera-icon". When I use that asset in Photoshop the layer is randomly named "a56bd81d-d81f-4815-82b3-5795d410b527". Why is this happening? Shouldn't that layer resolve the name back to "camera-icon" so that when I extract files for use in my application the naming convention is correct. Right now I have to manually rename that layer again. Is this a bug or have I just not done something correctly?

I think you have pasted the entire crash log. In case of such issues in future, please paste the error screenshot.
Seems to be a permission issue. Lets follow the below suggestions:
Solution 1: Rename the following folders on your machine:
'/Library/ColorSync/Profiles/Profiles'
'/Library/ColorSync/Profiles/Recommended'
Solution 2: Rename the following files:
'/Library/Application Support/Adobe/caps/Media_db.db'
'/Library/Application Support/Adobe/caps/pdb.db'
Make sure you dont touch caps.db under the same folder. Now run the installer again. Let me know if you need more help.
Solution 3:
Please Run following commands on terminal on the machine (this will remove the corrupt fonts and should allow you to run the installer successfully) -
sudo mv "/Library/Fonts/ACaslonPro-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/SavedFonts/current/AdobeArabic-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/HelpCfg/de_DE/goURL_lr_photoshop_de.csv" /tmp/
Please feel free to respond to this thread if you have any questions about the steps listed within the document. If you could also respond with the specific error message you receive, It would be appreciated.

Naming Convention - Best Practices

Hi,
Do you'll have a recommendation for naming convention/standards in BPC. I am referring to naming convention for objects like Dimensions, Models, Task Profiles, Data Access Profiles, Rules, Process Flows and so on...
Thanks in advance for your support
Thanks.

Hi Jon,
Usually no. Quite often we try to create names as much familiar to user as we can. Since like: dimensions the ID is what is shown in the reports, and despite have a description, you can't use this description as the main mask for that dimension. So the ID should be a "semantic" name, something the user identify what it is. Models, Rules and Process Flows is the same.
The exception is regarding security. I.e. data access profiles depends on the client you can create some sort of standards. Such as: The security is made by entity and cost center, so my DAP is:
- EEEE_CCCCCCC_T
Where: E = Entity ID
C = Cost Centre ID
T = Type: R - Read, W - Write and D - Denied.
But it's all very generic. The only thing I reckon important is to keep coherence while creating objects.
Cheers.
Lucas

Powershell naming conventions for functions

There is a lot of information about the Verb-Noun naming convention for cmdlets. I am trying to understand what the recommendation / best practice is for naming functions. Personally, I like the idea that if I see Verb-Noun, I know it's
a cmdlet, and it supports the standard parameters. However, I'm not sure I see the entire picture.
Thanks!

There are as many opinions around this as there are people. TechNet has some good recommendations for naming conventions, but you should adopt whatever standard you are most comfortable with. In the end it doesn't much matter which convention
you adopt, as long as you stick to it and keep it consistent. Most corporate code doesn't get outside or shared with other businesses and vendors, so the whole purpose of standards and conventions is to keep things straight for YOUR people. As
long as you consistently apply your conventions, it doesn't matter.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

Whats most common naming convention for MP3s (what does iTunes store use?)

Trying to organise all my tags and music.
I am using iTunes and some other tag (tag%rename) WMP etc, as some seem to not show all the tgs of other programs)
However what is the generalised, most common naming convention for MP3 files?
ie. track no, Album, artist etc.
Also Ive never bought music from iTunes store yet, only got podcasts and stuff, but when you do , what is the filename convention they use please?
cheers
Mac OS X (10.5) iMac 20" 2Ghz (1st ever Mac Comp)

iTunes has no automatic tag look up function for anything other than CDs (through GraceNote). I import a lot of mp3s (legally obtained) that need tweaking. Also, GraceNote doesn't provide lyrics. If I just need to edit a couple of tracks, the iTunes interface is fine. But for bulk adding of artwork or searching for release dates or lyrics, I use MpFreaker. I find it works best if you do small batches and keep an eye on what it comes up with. Sometimes, well, rarely, it's way off base.
There may be better utilities out there but MpFreaker was recommended to me by someone I trust who spends a lot of time reviewing such things and it works for me so I haven't looked for anything else. You might find more reviews of other software at www.ilounge.com
Best of luck.

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

NWDI naming conventions

Hi,
does anybody know about documentation with proposals of naming conventions for
- products
- software units
- Software components
- Tracks
and so on?
Would be great to get a link.
Thanks in advance
Norbert

Hi Norbert,
there are not much conventions for naming of that entities. The most obviuos and well known ones are given/referenced below.
the very first and the most important is namespace (aka vendor aka prefix - depending on the context)
in order to avoid any collisions it is always strongly recommended to use a reverse internet domain reserved by your company as a vendor or prefix for all named entities.
in that way for SAP the vendor/prefix should be "com.sap", for MSFT - "com.microsoft", for W3C - "org.w3" etc.
Further constraints you might find in SLD:
- help
- namereservation dialogs contain additional information
- you might also have a look at <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/5a1babec592a4de10000000a11466f/frameset.htm">NW CE 7.1 SP3 help</a> (the rules are about the same for other releases)
A few more hints
- it is not recommended to repeat the vendor/prefix in the main part of the name,
instead of vendor "org.demo.my", name "my.org.demo.abc"
recommended: vendor "org.demo.my", name "abc"
- there is no need to include entity type in the name, e.g.
instead of name "my.demo.org.DC.my.application"
recommended: vendor "my.demo.org", name "my.application"
- if necessary (only you may now if it is the case), define a prefix per product and use it consistently in all entities those belong to the product. That would be particularly hepful if you plan to develop more than one product
- pay attention to the case(!)
If the information is too generic - you might give few examples those would help you to get better feeling.

IP Naming Convention Recommendation

Similar Messages

Maybe you are looking for