ERP Database - The Unofficial ERP Knowledge Base

Facebook Twitter del.icio.us Digg it
ERP Database contains a huge collection of articles related to ERP System and Software. Many of the articles are specifically related to SAP. All these ERP/SAP articles are freely available to everyone.

If you would like to submit an article or share any document related to ERP or any specific ERP software. Please mail it to support@erpdb.info. Please make sure that the documents are not copyrighted.
Social Bookmarks:

Basics of SAP Basis

Print This Post Email This Post Written by admin on Aug 21st, 2008 | Filed under: Basis

Are you planning to start a career in SAP Basis, then this Guide on Basics in Basis will help you understand the below questions:

  • What is IT’s role in a SAP implementation? What can Your Implementation Consultants do for Your IT Group?
  • What is a SAP Landscape? What is my role in a SAP implementation?
  • What is a SAP Instance?
  • What are the different kinds of SAP software? What kind of hardware will they need?
  • How does SAP get installed?
  • Do I have to install JDK 1.4x?
  • What is a SAP client?
  • How do I create a new client?
  • What is this permanent key stuff?
  • How do the users communicate with the SAP instance?
  • How do I limit what my users can do when they log on to a SAP instance?
  • How do I patch a SAP instance? How often should I do it?
  • What are all these numbers? “s” number, license number, etc.
  • How do I add users? Do I have to add them all to each client one-by-one?
  • Do I have to add printers to each client too?
  • So what does the Functional Team do in their own little client(s)?
  • What factors affect SAP Performance?
  • What the heck is all that DVEBMGS00 crap? And this thing?
  • Where on the OS level can I look for help with SAP related problems?
  • And if I don’t find my problem in the work directory or don’t understand what the error message is telling me?
  • A working OSS whatie?
  • Why do we need a Solution Manager instance? What does it do?
  • Basis Knowledge Transfer.
  • Basis tasks to be done on a regular schedule.
Share

If you like this post, you may as well like these too:

  1. SAP BIW Basics Tutorial SAP BIW(Business Information Warehouse) or BI (Business Intelligence) now plays a central role in virtually every solution introduced in market by SAP. It facilitates predicting and proper analysis based on...
    2.
  2. Virus Scanner Basics – Overview The Virus scanner interface is a new feature in SAP Systems since the release of the SAP Web AS Version 6.20. It is avaliable for use in Various SAP Modules...
    3.


1 Comment Get FREE daily updates by RSS or e-mail

One Response to “Basics of SAP Basis”

  1. suman, on May 21st, 2010 at 5:46 am Said:

    * What is a SAP Landscape? What is my role in a SAP implementation?

    The SAP Landscape is like a layout of a complex garden – you have areas for roses, and areas for lilacs, and it is all laid out in proper form. A SAP landscape can range from one SAP instance with one client and one user who does all the input into the instance via keyboard to dozens of instances with hundreds of clients and thousands of users, with keyboard input, RFC (Remote Function Calls) and ALE (Automatic Link Exchange) from other SAP instances, links to external databases, EDI (Electronic Data Interchange) via flat file from banks, vendors, etc., and RF units in the warehouse. In other words, a SAP landscape can be very simple, or very complex. A bed of petunias, or the Hanging Gardens of Babylon.

    A normal SAP landscape consists of a Development (DEV) instance, a Quality Assurance (QAS) or Test (TST) instance, and a Production instance (PRD). Some very small implementations will have only a DEV and PRD instance, with the DEV instance containing a QAS client for testing purposes.

    A non-Production SAP server should have 2 (preferably more) processors, at least 4 gig of memory, and at least 100g of disk space. A Production SAP server should have at least 4 processors, from 4 to 8 gig of memory, and at least 200g of disk space. A hefty server with 6 – 8 processors, 6 – 8 gig of memory, and at lease 200g of disk space can host two SAP instances. This can be done for DEV and QAS but PRD should never share a server with any other SAP instance.

Leave a Reply