Naming Convention (Naming Rule) for CAF GP

Hi, all.
Is there any naming convention for CAF GP?
For its process, action, callable object so and so.
Web Dynpro for Java has very good naming convention like the following.
http://help.sap.com/saphelp_nw2004s/helpdata/en/e4/d7fb402eb5f76fe10000000a1550b0/frameset.htm
Could someone provide the information?
Best Regards.

Hi Sejoon,
Sometimes I see GP provided coding examples and it seems that GP does not have some specific naming convention. It's clear that they use sdandart java naming convention. So, you can use it too.
Best regards,
Aliaksei

Similar Messages

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

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

Naming conventions for data types

In my functional specs I have been given field names
Client Number
Record Type
Customer Name and so on
I need to create custom data types for all these and assign them to std values (vbak-kunnr, adrc-name1)
I am trying to determine what is the best naming convention to use for my custom data types
Would the convention be to use, new_kunnr, new_adrc_name1 or perhaps just ClientNumber, RecordType, CustomerName and so on

I think its best I include my scenario so people can better answer my question
My report has four different parts, each has a filler, record type, customer number which need to be initialized to certain values that are different
The four parts are Name/Address, Credit Order, Sub total and Total
Name/Address has Record type = A , customer number = vbak-kunnr
Credit Order has Record type = R, customer number = vbak-kunnr
SubTotal has Record type= space and customer number = 99
Total has Record type = S and customer number = 9999
So I have to create variables for these and am trying to figure out a proper naming convention
I could do RecordType_Name, RecordType_CreditOrder and so on but that does not seem the best way to me. Any ideas!

-cvs, -git, -snv... is really a good naming convention?

The unstable packages have the name of their relative stable one with added in suffix the concurrent version system installed.
I think it is a bad convention since it mixes implementer choices with the the concept of lastest unstable version.
I think it is better decide a single suffix (e.g., -unstable or -dev) and always use it without difference between the implementer choices of programming.
Moreover it avoids renaming headaches if someone changes program for keeping versions.
No flame wars. I decide nothing. It is only a thought.

Profjim wrote:
I've seen this discussed before on the forums...
Edit: http://bbs.archlinux.org/viewtopic.php?id=25938
I found this in the forum search: http://bbs.archlinux.org/viewtopic.php?id=25938
It doesn't seem like anything came out of that discussion. I haven't really found the naming convention confusing; it is the large variety of SCMs that is confusing, and that is not going to change anytime soon. The current package naming conventions are unproblematic for me so you'd have to point out exactly where a real problem has cropped up.

Project Naming Conventions?

Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon. Thanks!

Kenneth Kirksey wrote:
Would anyone care to share the naming conventions they use for projects? I have a manageable number now so naming doesn't matter so much, but I can see having a large number of projects soon.
hi, ken
do you have clients?
my folder/project naming conventions...
main subject with projects below
for example,
Beach (main subject)
Jetty (sub subject)
Nature (main subject)
Birds (sub)
Birds of Prey (sub sub)
Fashion (main sub)
Model Name (sub)
Calvin Klein (sub sub)
(MGM Grand) (sub sub)
Music (main)
Artist Name (sub)
name of Project currently working on (sub for artist)
I hide photos in yellow folders to keep other clients from viewing photos from others
sometimes 2008 Beach to keep the year separated
victor

Components naming convention

Are there any components naming convention guidelines? For example, for text field components id, should that be prefix with textName or suffix with nameText, etc. In tutorials, I have seen both approach.

We compiled some conventions based in engineering input. You can see them at http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/about_components.html#general (see the id row in the table).
In the tutorials, we decided to not strictly follow these guidelines. Our reason was, we wanted the reader to focus on the lesson on hand. We didn't want to waste the users time renaming ids when it didn't really affect the outcome. These are one-time apps and thus the naming of the ids is not as important as with an app that will be worked on by different people over a span of time. Hope that makes sense.

BRFPlus - naming convention

Does anyone already have a set of
1) naming conventions set up for BRFPlus development. I am looking for naming conventions for BRFplus objects like applications, expressions, data objects, etc...
2) BRFPlus development standards and guidelines
We are planning to use BRFPlus and just making sure that I dont end up reinventing the wheel?
Thanks,
Saurabh

Hi Saurabh,
There are name checks for applications and inside of an application for functions. The names must be unique and you need to adhere to naming conventions same as with DDIC or ABAP objects. All the rest can be named as you like. Means you may give any name to expressions and data objects contained in an application. The only restriction is that only characters, underscore and digits are allowes as well as slashes for namespaces.
In the text of an object anything can be used. You are able to configure the UI in such a way that either text or names are used (as of EHP2) so that the UI looks IT or business-like.
I have seen conventions indicating the type, such as DECT... for Decision Tables.
In case you plan to attend TechEd 2009 we can meet for a discussion. I will be in Phoenix and Vienna. Colleagues will do the Bangalore and Shanghai session.
BR,
Carsten

Naming conventions for CAF?

Hi,
Where can I find naming conventions for CAF?
Regards,
Rahul

Hi Rahul,
Perhaps this [thread|Re: creating development component projects(CAS)] answers your question.
Regards,
Jan

What are the naming convention rules for BAPI and types

what are the naming convention rules for BAPI
points will be rewarded,
thank you,
Jagrut BharatKumar Shukla

Hi,
plz go through the following links....
Business application Prograaming Interface is nothing but the Method of a Business object.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
u can check the below the material also
what is BAPI?
BAPI stands for Business API(Application Program Interface).
I have answered this question before..
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
BAPI
http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
List of all BAPIs
http://www.planetsap.com/LIST_ALL_BAPIs.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://www.geocities.com/mpioud/Abap_programs.html
http://www.sapdevelopment.co.uk/reporting/reportinghome.htm
***do reward if usefull
vijay

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

Best practice for naming convention in BI 7.0

Hi All,
Is there a Best Parctice document for naming convention in BI 7.0?
Thanks,
S.B

hi,
chk this links...
http://help.sap.com/saphelp_nw04/helpdata/en/ba/83343ea7ff6a38e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/da/0318025d64a84b94542641ed77ee74/frameset.htm
hope this helps,
partha

Looking for best practice on naming conventions

Does anyone out there have a best practice on naming conventions that they could share.
I'm starting to find the need to create objects and associated variables and actions.
I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
Thanks
Alan

Hi Alan,
Welcome to Adobe Community.
There are couple of things that you can keep in mind while naming objects.
When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
bitmap images that constitute the new style should be named as follows:
Brightblue1.bmp, an image with no callouts
Brightblue2.bmp, an image with a callout to the right or upper-right
Brightblue3.bmp, an image with a callout to the left or upper-left
Brightblue4.bmp, an image with a callout to the lower right
Brightblue5.bmp, an image with a callout to the lower left
Flash button-naming conventions
Each SWF button contains three layers: a button, an icon, and an action layer.
The SWF filename consists of the following elements:
Acronym for playback control (“pbc”)
Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
Name of the button (“play”).
Hope this helps!
Thanks!

Inconsistent naming conventions for Adobe Reader in software scan

I just want to see if anyone knows why Adobe's free pdf Reader appears both as "Adobe Reader" AND "Adobe Acrobat Reader". I manage software licenses for an organization of 400+, and it's difficult to know if, for instance Adobe Acrobat - Reader 6.0.2 Update - 6.0.2, should or should not be counted as a purchased license without actually visiting each workstation to verify. I've spoken with our network operations personnel and they confirmed that it is not manually entered by our personnel, but that it is something in the software. ??
Furthermore, why are the naming conventions not consistent even among those that can be identified easily? The list below is what I see when I run a report for all Adobe software on our network.
Adobe Acrobat - Reader 6.0.2 Update - 6.0.2
Adobe Acrobat 4.0 - 4.0
Adobe Acrobat 5 -- SC Install
Adobe Acrobat 5.0
Adobe Acrobat 5.0 - 5.0
Adobe Acrobat 5.0 - 5.1
Adobe Acrobat 5.0 SC Support
Adobe Acrobat 6.0 Professional - 006.000.000
Adobe Acrobat 6.0 Standard - 006.000.000
Adobe Acrobat 6.0.1 Professional - 006.000.001
Adobe Acrobat 6.0.1 Standard - 006.000.001
Adobe Acrobat 7.0 Professional - 7.0.0
Adobe Acrobat 7.0.1 and Reader 7.0.1 Update - 7.0.2
Adobe Acrobat 7.0.2 and Reader 7.0.2 Update - 7.0.3
Adobe Acrobat 7.0.3 and Reader 7.0.3 Update - 7.0.4
Adobe Acrobat 7.0.5 Professional - 7.0.5
Adobe Acrobat 7.0.7 Professional - 7.0.7
Adobe Acrobat 7.0.8 Professional - 7.0.8
Adobe Acrobat and Reader 6.0.3 Update - 6.0.3
Adobe Acrobat and Reader 6.0.4 Update - 6.0.4
Adobe Acrobat and Reader 6.0.5 Update - 6.0.5
Adobe Acrobat Reader 3.01
Adobe Acrobat Reader for Pocket PC 1.0
Adobe Reader 6.0 - 6.0
Adobe Reader 6.0.1 - 006.000.001
Adobe Reader 7.0 - 7.0.0
Adobe Reader 7.0.5 - 7.0.5
Adobe Reader 7.0.5 Language Support - 7.0.5
Adobe Reader 7.0.7 - 7.0.7
Adobe Reader 7.0.8 - 7.0.8
Adobe Reader Chinese Simplified Fonts - 1.0
Adobe Reader Japanese Fonts - 1.0
Adobe Reader Korean Fonts - 1.0
If anyone can answer this, I'd appreciate it. Thanks.

Junlie et al,
Starting with Acrobat 9 (announced on 6/2/08), Adobe will support the new ISO/IEC 19770-2 standard for universal software tagging. The new standard will allow customers to correctly identify the name, version, type and licensing status of Adobe software (starting with the Acrobat 9 family and later on as new versions of the products are introduced later this and next year).
I DO understand your frustration with the in consistencies in the naming of our software, but the problem of software discovery goes well beyond our lack of discipline. This is one of the many reasons why Adobe invested time and effort with the industry group defining the new open standard, and in software asset management in general.
More information about tagging standard can be found here: http://www.agnitioadvisors.com/info/content/view/44/1/
- Juan-Carlos

PO Naming Convention for specific company code

Hi experts!
Is there any way to know this PO naming convention is belongs to which company code?
For eg: PO naming convention starts with 600*******.
How will i know which company code is using the naming convention for their purchase order?
Please help.
Thanks.
Crystal

Hi Crystal,
Naming convention is based on document type not company code :
Refer the below customsing path:
SPROMaterials ManagementPurchasingPurchase Order--Define Document Types
SPROMaterials ManagementPurchasingPurchase Order--Define Number Ranges
Regards
Ramesh Ch

Naming Convention (Naming Rule) for CAF GP

Similar Messages

Maybe you are looking for