ABAP Programming Standards

[Former Member]

Hi ,

Does SAP give any guidelines / document on Programming standards ? I understand that it is specific to individual implementations , but wondered if there could be any guideline by SAP .

Regards ,

Sujatha

[Former Member]

Hi,

Copy and paste the link ..

www.ams.utoronto.ca/Assets/output/assets/Developmentstandards_guidelines_335678.pdf.pdf

<b>Standards --></b> http://web.mit.edu/sapr3/dev/newdevstand.html

Regards

Sudheer

[Former Member]

Hi,

There wont be any guideline from SAP.

Your client may give you some guide lines, which u need to follow.

Thanks,

Deepti

[Former Member]

Hi,

Check these links

http://sapland.com/index.php?option=com_content&task=view&id=68&Itemid=35

http://www.sap-basis-abap.com/abap/abap-4-development-code-efficiency-guidelines.htm

Thanks

Naren

[Former Member]

Hi,

Normally the client have their won programming standards and guidelines. Do ask ur client ...what programming std are they follow or will be use..

This programming standard speaks about how will the custom program named, transaction ,

newly created packages etc will be named, how will the variable, internal tables, field sysmbols etc will be declared in program.. what status to choose under what scenario... etc etc ...

Kindly check the link below which speaks about how MIT SAP team has set standards and guide

lines for their SAP system developement.

<b>Reward points</b>

regards

[Former Member]

Lots of things can be included in standards.

It somewhat depends on your system size, number of users, how much development etc. as to how detailed you want to get.

Some of the common (programming) standards I have used at various sites:

P_ for parameters

s_ for select options

gv_ for global variables

lv_ for local variables

pv_ for passed variables in forms

gt_ for global itabs

lt_ for local itabs

gs_ for global structures

ls_ for local structures

co_ for constants

V_ = For local & global Variables; Field Strings.

W_ = For workflow container elements.

I_ = For internal tables

Program names need to be something that you and your company are comfortable with. Many sites used to do something like

Z - custome prefix

FI - module

R - report

nnnn

reward points if it is usefull ..

Girish

[Former Member]

Hi,

if ur declaring the fallowing things U have to maintain some naming standards :

internal table : IT_<name>.

structure : S_<name>.

workarea : WA_<name>.

parameter : P_<name>.

select-options : SP_<name>.

if ur creating the fallowing things then :

Report name : R_<name>.

Smartform : SF_<name>.

Function module : FM_<name>.

BAPI : BAPI_<name>.

<b>reward points if helpful,

Regards

Raghunath.S</b>