IKING GOMEZ IKING GOMEZSAP Development Policy GSS DDS
TeamVersion: 1.0Last Update: 31-March-2014 Document ControlRevision
HistoryDate Version Name Description2014/03/31 1.0 Takashi Aibara
Newly created TABLE OF CONTENTModification History 21 DOCUMENT
SUMMARY 41.1 Objectives 41.2 Scope 41.3 Methods 42 SAP OBJECT
NAMING CONVENTIONS 53 APPENDICES 103.1 module Code 103.2 Object
Glossary 103.3 Program Patterns Guideline 134 GUIDELINE FOR
DEVELOPMENT 174.1 GUIDLINE FOR USING ABAP DICTIONARY 174.2 GUIDLINE
FOR DESIGN 171 Document Summary1.1 ObjectivesThe purpose of this
document is to articulate a common set of standards and procedures
for the naming, development, and documentation of custom solutions
within the SAP NetWeaver environment. The objectives of this
document are to maximize the quality, value and maintainability of
each custom solution proposed by the Kubota SAP Project. Thus, it
is essential that each person performing programming activities
familiarizes him/herself with, and adheres to these common set of
standards. 1.2 Scope Consistent naming conventions for custom ERP
objects. Consistent naming conventions for ABAP program elements.
1.3 MethodsThe compilation of the standards and procedures has been
a co-operative effort of many IBM consultants based on their
collaborative experience on multiple projects. The intent is to
combine specific lessons learned from IBM resources with industry
best practices to develop a set of standards that will ensure
quality in applying system maintenance and ensure creative
development of custom solutions for Kubota in the future. This
deliverable includes content from the following sources: SAP ERP
Documentation IBM Systems Management Methodology for ERP IBM/SAP
Best PracticesNote: This document has been compiled, maintained and
discussed at length in a series of open-forum workshops involving
application development resources from IBM and the SAP Competency
Group. Any changes of this document must be approved by the Kubota
SAP Project Technical Lead.2 SAP Object Naming Conventions The
following table is intended as a reference guide to ERP naming
conventions for SAP ABAP developers. For any objects that have been
overlooked or are not defined in the naming convention, kindly
consult the Kubota SAP Project Technical Lead. For additional
information on each entry, please refer to the ERP Object Glossary
in the Appendix. In examples, the following alphabets indicate:aa
... Company Identifier (2-digit) If there are more than one, use a
representative company.bb ... Module Code (2-digit) See 3.1 Module
Code.xx...xx ... Any arbitrary alphanumeric letters.ERP Object
Length ValuePrograms/ Reports 30 Z+ Company Identifier + Module
Code+ arbitrary lettersCode: Zaabbxx...xxe.g.
ZKTSD_OUTPUT_VBAK_DATATransaction Code 20 Z+ Company Identifier +
Module Code + arbitrary lettersCode: Zaabbxx...xxe.g.
ZKTSD_OUTPUT_VBAK
