Discover millions of ebooks, audiobooks, and so much more with a free trial

Only $11.99/month after trial. Cancel anytime.

SAP ABAP Programming Guidelines
SAP ABAP Programming Guidelines
SAP ABAP Programming Guidelines
Ebook88 pages23 minutes

SAP ABAP Programming Guidelines

Rating: 0 out of 5 stars

()

Read preview

About this ebook

Comprehensive ABAP programming guidelines to be used in a SAP project.

LanguageEnglish
PublisherGaurav Mehra
Release dateJun 24, 2017
ISBN9781386998891
SAP ABAP Programming Guidelines

Related to SAP ABAP Programming Guidelines

Related ebooks

Enterprise Applications For You

View More

Related articles

Reviews for SAP ABAP Programming Guidelines

Rating: 0 out of 5 stars
0 ratings

0 ratings0 reviews

What did you think?

Tap to rate

Review must be at least 10 words

    Book preview

    SAP ABAP Programming Guidelines - Gaurav Mehra

    Introduction

    1.1  Purpose of this document and target audience

    This Guideline provides development standards and examples for the Spares SAP R/3 system. Therefore design, style, naming and documentation conventions for an optimised Customizing and Development are defined in here. The document is created for all internal and external employees, which are involved in SAP- development, customizing and maintenance.

    All conventions and procedures of this document have to be considered. Objects that does not fulfil the defined standards within this guideline, will not be accepted and not transported from the development instance.

    The relevant official SAP-guidelines are the base for all developments and are linked within this document. This document is a further detailed guide for Spares development.

    This document should be read in conjunction with further linked documents like the User exit administration

    ⇨ P:\ATLAS-enhanced\00_OverallProject\45_ConfigurationManagement\Customer user exit administration_V1.1.doc

    The naming convention is mandatory for all new or extensively changed objects and recommended for smaller changes of objects.

    Developments have to be proceeded in English, always.

    1.2  Principles of software development and customizing

    ––––––––

    Software has to be correct and stable to achieve low costs at a high service level. Therefore processes of software developments have to be structured and created with a unique logic and naming convention to be reusable.

    All transport activities are coordinated and controlled by the Configuration Management.

    All data design and development activities are coordinated and controlled by the Development Management.

    Overview

    The module abbreviations are furthermore used to identify object names (compare topic 3).

    Development classes are created and managed only by the system administration.

    1.3

    Stepwise implementation

    All developments which are not classified as local objects (using the ‘$TMP’ development class) can be transported. In general the procedure is carried out in the following steps:

    Customizing: Client-copy of request (transaction SCC1) from AT1 client 300 to 303

    Transport to quality-assurance-system (AQ1/AQ2/AQ3)

    Testing of development or changes in environment close to production system

    Functional test

    Extended syntax check and check of development

    Enjoying the preview?
    Page 1 of 1