Scribd Logo
Upload

Welcome to Scribd!

  • 13 views

    01 31 2017 Test Pointer

    Uploaded by

    Nick G
    The document discusses SAP architecture, users, and user master data. It describes the standard 3-tier architecture with presentation, application, and database layers. It defines clients as independent organizational units that can share master data. The document outlines the types of SAP transactions and users, including dialog, communication, and development vs production servers. It provides the steps to deactivate a user and lists mandatory fields for creating a user record. Finally, it notes that user master data is client dependent and cannot be seen across clients.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    01 31 2017 Test Pointer

    Uploaded by

    Nick G
    13 views2 pages
    The document discusses SAP architecture, users, and user master data. It describes the standard 3-tier architecture with presentation, application, and database layers. It defines clients as independent organizational units that can share master data. The document outlines the types of SAP transactions and users, including dialog, communication, and development vs production servers. It provides the steps to deactivate a user and lists mandatory fields for creating a user record. Finally, it notes that user master data is client dependent and cannot be seen across clients.

    Original Description:

    Objects Are

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses SAP architecture, users, and user master data. It describes the standard 3-tier architecture with presentation, application, and database layers. It defines clients as independent organizational units that can share master data. The document outlines the types of SAP transactions and users, including dialog, communication, and development vs production servers. It provides the steps to deactivate a user and lists mandatory fields for creating a user record. Finally, it notes that user master data is client dependent and cannot be seen across clients.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    13 views2 pages

    01 31 2017 Test Pointer

    Uploaded by

    Nick G
    The document discusses SAP architecture, users, and user master data. It describes the standard 3-tier architecture with presentation, application, and database layers. It defines clients as independent organizational units that can share master data. The document outlines the types of SAP transactions and users, including dialog, communication, and development vs production servers. It provides the steps to deactivate a user and lists mandatory fields for creating a user record. Finally, it notes that user master data is client dependent and cannot be seen across clients.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    3 Tier Architecture in SAP:

    - Presentation layer
    - Application layer
    - Database
    Explain Client:
    - Client is an independent organizational unit. Check online literature
    - All the master data can be shared within the cient
    System Landscape:
    Two main types of transactions in SAP:

    Order-to-cash:
    Procure to Pay:

    Types of users:

    Dialog users. Password expires as per company policy. End User


    Communication users: Used for servers communicate between each other
    and compare data. Cannot login with communication user. Password never
    expires. (SM59)

    Development Production Server


    Server

    Aa
    Aa
    Aa
    Aa

    Components of User Master Record: ALDRPGR??

    Steps to deactivate the user:


    1. Lock the user
    2. Expire the user
    3. Remove the access
    Mandatory Fields required to create user: Lastname, Password

    User Master Data is client dependent Because if you create user master record in
    one client, you cannot see it in other client.

    You might also like