What We’re Reading


SAP BASIS Basics

 1   2   3   4   5   6   7   8   9   10   11   12  13  14  15 …

  • 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.

Read More…


Search