Home | Contact Us | Log In | Help
HOME NEW LISTING MOST POPULAR HIGHEST RATED SCRIPTS ADD SCRIPT DOWNLOADS FORUM
Tutorials
  ASP.Net & C#
  ASP
  Perl and PHP
  Java Scripts
  C and C++
  Ajax Tutorials
  J2ee, J2Me, Java
  Python & Ruby Rail
  Crystal Report
  Sap
  CGI
  XML
  Cold Fusion & CFML
  HTML, DHTML & CSS
  Dreamweaver
  FLASH
  Photoshop/Web Designing
  Tools & Utilities
  Oracle/D2K
  Sql Server
  MySql
  Domain Name Registration
  Remotely Hosting
  Web/Server Application
  Hotel Marketing
  Internet and Law
   Search Engine Optimization/SEO
E-Commerce
Interview Questions
Previous< 1 2 3 4 5 6 > Next
SAP 3
SAP DB Documentation

If SAP DB is new to you, we recommend that you first read the manual The SAP DB Database System.
This manual will give you an overall idea of the SAP DB database system, its architecture, user and security concepts, database tools, the directory structure, important database parameters, the data management architecture as well as an overview of the available documentation and relevant database terms.
A second source of general information is the Reference Manual: SAP DB 7.4. This document outlines the syntax and semantics of the SQL statements for performing operations on the SAP DB database system.

SAP Application Modules

SAP has several layers. The Basis System is the heart of the data operations and should be not evident to higher level or managerial users. Other customizing and implementation tools exist also. The heart of the system from a manager's viewpoint are the application modules. These modules may not all be implemented in a typical company but they are all related and are listed below:

Designing SAP Transactions

For performing any kind of task in the SAP R/3 ERP system, a transaction is used. SAP provides a standard set of transactions to manipulate i.e insert, update, delete and display data in the system. But sometimes, the need to create a customer specific transaction may arise due to the following reasons
Standard SAP may not support that task
A particulartransaction needs to be customized to suit the customer requirements.
A transaction is defined as a sequence of dynpros (sap term for screens) having input and output fields and corresponding processing logic behind them to perform a particular task.

SAP R/3 System Architecture

SAP based the architecture of R/3 on a three-tier client/server model.
Presentation Server
Application Server
Database Server

Presentation Server

The presentation server is actually a program named sapgui.exe. It is usually installed on a user's workstation. To start it, the user double-clicks on an icon on the desktop or chooses a menu path. When started, the presentation server displays the R/3 menus within a window. This window is commonly known as the SAPGUI, or the user interface (or simply, the interface). The interface accepts input from the user in the form of keystrokes, mouse-clicks, and function keys, and sends these requests to the application server to be processed. The application server sends the results back to the SAPGUI which then formats the output for display to the user.

Business Processes and SAP Functionality

In order to understand a system like SAP a thorough understanding of the events and relationships that take place in a business is required. It is not enough to just realize the Sales, Production, Finance and Accounting have jobs to do in a business. The exact details of each action, the timing of that action and its interrelationships with every other process must be understood. In many large operations there may be no person that has a complete grasp of the situation. Before an operation can be automated or computerized a thorough study of the business must be undertaken. This task is called Business Process Engineering.

Previous< 1 2 3 4 5 6 > Next
  Copyright 2000-2006 © SoloScript.com, All rights reserved.