Scribd Logo
Загрузить

Добро пожаловать в Scribd!

  • Sap R/3 Abap/4 - F A Q: By: C.Rajasekhar Topic: User Exits

    Загружено:

    DeweshChandra
    7 просмотров1 страница
    This document discusses user exits in SAP R/3. It defines user exits as customer changes made to SAP objects without modifying core code. User exits allow enhancements to be made without affecting standard SAP source code or software upgrades. The document describes identifying user exits using transaction CMOD and development classes marked with a + sign. It also explains that user exits developed in development systems can be transported to quality or production systems.

    Исходное описание:

    Оригинальное название

    FAQ5.PDF

    Авторское право

    © © All Rights Reserved

    Доступные форматы

    PDF, TXT или читайте онлайн в Scribd

    Этот документ был вам полезен?

    Это неприемлемый материал?

    Пожаловаться на этот документ
    This document discusses user exits in SAP R/3. It defines user exits as customer changes made to SAP objects without modifying core code. User exits allow enhancements to be made without affecting standard SAP source code or software upgrades. The document describes identifying user exits using transaction CMOD and development classes marked with a + sign. It also explains that user exits developed in development systems can be transported to quality or production systems.

    Авторское право:

    © All Rights Reserved
    Скачайте в формате PDF, TXT или читайте онлайн в Scribd
    Отметить как неприемлемый контент
    7 просмотров1 страница

    Sap R/3 Abap/4 - F A Q: By: C.Rajasekhar Topic: User Exits

    Загружено:

    DeweshChandra
    This document discusses user exits in SAP R/3. It defines user exits as customer changes made to SAP objects without modifying core code. User exits allow enhancements to be made without affecting standard SAP source code or software upgrades. The document describes identifying user exits using transaction CMOD and development classes marked with a + sign. It also explains that user exits developed in development systems can be transported to quality or production systems.

    Авторское право:

    © All Rights Reserved
    Скачайте в формате PDF, TXT или читайте онлайн в Scribd
    Отметить как неприемлемый контент
    из 1

    SAP R/3

    ABAP/4

    FAQ

    By : C.Rajasekhar

    Topic : User Exits

    1) What is the gap bridging / Enhancement / Gap Development.


    Ans ) Customer Changes to SAP repository objects without modifications

    2) Why do you need to use exits.


    Ans ) They do not affect standard sap source code , do not affect software upgrade .

    3) Various types of enhancement.


    Ans ) Program , menu , screen , field .

    4) How do you identify the user exits ?


    Ans ) Use the transaction CMOD and for that respective development class exits are
    available with + sign .

    5) What do mean by SSCR , OSS.


    Ans ) SAP Software Change Registration
    Online Service System

    6) How does the production system take the benefit from the user exits
    Ans ) Development would be carried out in the development system and the changes /
    user exits can be transported to the target system ( quality or production ).

    Вам также может понравиться