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 (prgramming) 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
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
but now that names can be longer, it is really down to your own definitions and how managable the naming needs to be.
Some things I DON'T agree with:
Naming forms F_
I don't see any point to it. It is always apparent in code when a form is being called.
Using pa_ or so_ for parameters and select options. It wastes a char in my opinion.