SAP R/3 for Everyone: Step-by-Step Instructions, Practical Advice, and Other Tips and Tricks for Working with Sap

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $29.68
Usually ships in 1-2 business days
(Save 46%)
Other sellers (Paperback)
  • All (11) from $29.68   
  • New (7) from $29.68   
  • Used (4) from $33.90   

Overview

SAP R/3 for Everyone is the nontechnical user's guide to working with SAP R/3, the leading business enterprise software product in the world. Written and road-tested by experienced SAP R/3 users and trainers, this book saves typical SAP R/3 users time and trouble by providing them with the universal skills needed to work with any module of this complex software.

SAP R/3 can be used effectively by anyone who can perform a handful of simple procedures that are employed in nearly every SAP R/3 transaction. The authors explain these procedures in plain English, using illustrations and real-world examples.

After a brief explanation of the architecture and operation of SAP R/3, readers get step-by-step instruction in

  • Logging on and off, managing passwords, and customizing the SAP application window and screens
  • Navigating between screens with menu folders, transaction codes, and the menu bar
  • Setting up customized favorites folders with quick links to the initial screens of transactions and other useful resources
  • Understanding the four basic transaction types
  • Working on initial screens, including tips and techniques for entering codes, searching for codes, customizing initial screens, and using multiple selection screens and selection options
  • Customizing output reports with filters, sorts, sums, and display variants
  • Exporting output reports to Microsoft Excel and Word and e-mailing output reports to other SAP users

Practical and jargon-free, SAP R/3 for Everyone provides readers with the skills and confidence they need to efficiently conduct any business activity with SAP R/3.

Read More Show Less

Product Details

  • ISBN-13: 9780131860858
  • Publisher: Prentice Hall
  • Publication date: 7/22/2005
  • Pages: 320
  • Sales rank: 793,095
  • Product dimensions: 7.00 (w) x 9.23 (h) x 0.68 (d)

Meet the Author

Jim Mazzullo is a consulting scientific and technical trainer, curriculum developer, and writer. Previously he worked as a training coordinator for a large electric utility company in the Pacific Northwest for which he developed, coordinated, and delivered training in SAP and other system and desktop applications. Jim began his career as a research professor and instructor of geology at Texas A&M University. You can learn more about him at www.JimMazzullo.com.

Peter Wheatley oversees SAP implementations as a customer engagement manager in the Southwest region of SAP America. In the last seven years, he has been employed by SAP America as a consultant, technical consultant manager, and technical solutions architect. He has also worked at IBM as a developer and at Compaq as an SAP developer and production planning analyst.

Read More Show Less

Read an Excerpt

Welcome to the world of SAP! You are now embarking on a journey into the workings and use of SAP R/3, the leading business enterprise software in the world. (SAP stands for Systems, Applications and Products in Data Processing; R/3 stands for Runtime System 3—in other words, the third release of the software.)

This book is written for the nontechnical end user of SAP R/3; that is, an average person in a company who has perhaps had some experience with desktop applications like MS Word and Excel but little or no experience with more complex enterprise software. This book provides these users with detailed instructions for working with this outstanding and versatile software product.

These instructions do not address any specific purpose, such as working with budget and cost data or managing the inventory of a warehouse. Rather, they describe general or universal procedures for working with any part of the software for any purpose. We firmly believe that a solid grasp of these general procedures and the development of the skills for executing them are the real secret for learning and managing SAP R/3 and using it effectively at your job.

In addition, this book is not intended to be comprehensive. SAP R/3 is very complex in its design and operation, and a comprehensive description of this software would require a much larger- not to mention more expensive- "bible" of a book that most people could not lift. Rather, this book describes the techniques and procedures that are most frequently employed by nontechnical end users when they work with SAP R/3. We decided on its contents after years of using this software, afterconsulting with other experienced users (the so-called superusers) like ourselves, and after many hours in the classroom teaching it to people like you.

Finally, this book is not intended to be a technical treatise about SAP R/3. If you were looking for instructions about programming, developing, or implementing the software at your workplace, you bought the wrong book. We do not describe the inner workings or architecture of the SAP software (except very briefly in the following pages), because we have found that such information does not help the typical end user work with the software any more effectively. We also avoid the use of technical jargon throughout this book, and instead say our piece in plain, simple English. We do not use a 25-cent word when a 5-cent word will do.

Before we describe the contents of this book, we must devote some words to the origin, design, and operation of SAP R/3. What Is SAP R/3?

SAP R/3 is a package of integrated applications called modules that record and track the activities and costs of doing business. Its roots extend back to 1972, when five system analysts, all former employees of IBM in Germany, created the software for collecting large volumes of business data in a single computer and then processing this data in real time, when the user needs it. Real-time processing was a particularly novel development at the time because the computers of the 1970s were slow, lumbering machines that required minutes, and sometimes even hours, to process large volumes of data.

Since that time, SAP has grown from a small regional company to the leading provider of business enterprise software in the world. At last count, SAP R/3 is now installed at 84,000 locations in 120 countries around the world, and it is used by more than 10 million people every day. SAP is now the world's third-largest independent software vendor, and it is still growing strong.

The great strength and utility of SAP R/3 are due to a large degree to its architecture or structure, which consists of functional modules, the SAP database, and the graphical user interface or GUI. We use the term system throughout this book to describe this three-part assemblage of software.

The functional modules are discrete software packages that are dedicated to specific tasks, such as accounting, payroll management, and inventory control). They are typically installed in application servers, which are computers that are capable of rapidly processing or "crunching" large volumes of data and then assembling the output of their work in a format that can be read by the user.

The database is the actual collection of business data. These data are stored inside database servers, which are computers with huge amounts of storage memory and the capacity to rapidly exchange data with the application servers.

The graphical user interface or GUI appears on the desktops of the computers or clients that you use to access the software. The centerpiece of the GUI is the application window (called a session by SAP), where you enter commands and data on scenes or screens by means of your mouse and keyboard. Note: Some users may access the SAP software through Web browsers such as MS Internet Explorer. In these cases, the SAP GUI appears inside the frame of the browser window.

There are many modules in the complete version of SAP R/3, but most business enterprises do not use all of them. Rather, they purchase and install or implement only those modules that they need to do their business. The selected modules are then integrated or linked to one another and to the database servers and clients by programmers, and the screens are customized or configured to fit the enterprise's needs. Once the modules are integrated, the boundaries between them vanish and they work with one another as a single, seamless software package. This aggregation of modules is also very flexible: The enterprise can often add more modules whenever they want so that the software grows as their business needs grow. SAP Transactions

The word transaction describes a single business activity that is conducted with SAP R/3. Some examples of end user transactions are

  • Creating a purchase requisition
  • Generating a budget report for a company department
  • Scheduling the shipment of a material to a plant
  • Recording the activities of a maintenance job
  • Entering employees' weekly work hours
  • Displaying the yearly sales for a product

Every transaction progresses through a four-step workflow of actions, commands, and events.

The typical workflow begins when the end user logs on the SAP system (Step 1). This action calls up the SAP Easy Access screen, which is the default "home page" for the software. The end user works with the elements on this screen to call up or navigate to the initial screen of a transaction (Step 2), where they instruct the software on its specific objectives and then execute it (Step 3). A few seconds later, the output of the transaction appears (Step 4) in one of two forms:

  • A confirmation that some business process, such as the creation of a requisition or the entry of an employee's work hours into the database, was accomplished. This message appears by default at the bottom of the initial screen.
  • A display of data from the database. This usually appears on its own output screen.

A good bit of the communication between the SAP R/3 software and the end user is accomplished during Steps 3 and 4 of this SAP workflow via technical object codes.

A technical object is anything that is monitored and tracked by SAP R/3. This includes tangible objects, such as employees, consumable materials, equipment, and physical plants, and intangible ones, such as work orders, purchase requisitions, and shipping orders.

Every technical object has a unique object code, which is assigned to it when its specifications are entered in the SAP database and which is the primary shorthand means of identifying it. There are literally thousands of such codes in every SAP database, but, fortunately, the software provides a way to search for them, so you do not have to memorize or record them. Organization and Contents of This Book

The body of this book consists of 17 lessons on the general use of SAP R/3. They are grouped into four parts, which correspond to the SAP workflow.

  • Part I, Getting Started, describes the procedures for logging on and off the SAP R/3 software, customizing the SAP application window and screens to suit your preferences, entering personal and logistical data about yourself, setting default values for the use of the software, and managing your password.
  • Part II, Navigating Between Screens, describes three methods for navigating from the SAP Easy Access screen to the initial screens of transactions, and a fourth method for navigating between initial and output screens.
  • Part III, Setting Up Initial Screens, describes the procedures for entering and searching for object codes and creating customized versions of initial screens.
  • Part IV, Working With Output Reports, describes the procedures for customizing the output reports of certain transactions and e-mailing them to other SAP users.

These lessons are preceded by the Introduction, which describes the design and operation of the SAP application window and its screens, and followed by a Coda, which presents a simple model of the four basic transaction types that are commonly executed by end users.

The instructions in the lessons of this book were written around and illustrated with screens from version 4.7 of the SAP R/3 software. However, they can also be applied to SAP 4.5 and 4.6, which are very similar in their design and operation to SAP 4.7. And with a little effort, they can also be applied to SAP 4.0, which differs slightly in its screen design but not its operation. Some Words About the Text and Screen Images

This book uses two conventions for highlighting certain texts:

  • The names of all screens and screen elements, including all menus, buttons, and fields, are always presented in bold type.
  • The names of transactions and software, as well as commands, options, and slang terms, are always presented in italic type.

These conventions are intended to help the reader scan through the instructions and easily pick out the critical references within them. The bold text can also be found with page references in the index at the back of this book. In addition, we hereafter refer to the SAP R/3 software simply as SAP, and to people who work behind the scenes to install, configure, operate, and monitor the use of the software as the SAP administrators.

Finally, we should point out that you will often see small differences between the screen images in this book and your versions of the same screens. Some of these differences arise because our screens are customized in a slightly different way from your screens. For example, every business enterprise makes use of a unique group of modules in their system, and so they display their own unique set of folders on their SAP Easy Access screen. We are no exception to that rule. In addition, we have the most current versions of screens at our disposal, and they contain a few more or different elements, more "bells and whistles," than your screens.

In addition, we have altered many screen images in this book with Adobe Photoshop and other tools. For instance, we have routinely cropped nearly all images to fit them on the pages and not consume too much space- otherwise, this book would probably be twice its present length, weight, and price! In addition, we have hidden screen elements and data that are either proprietary in nature or distracting and not relevant to the points of the lessons.

However, these are differences of degree, not of kind. For the most part, you will not even notice the differences between our screens and your scresens, and the noticeable differences will neither confuse you nor obscure the lessons in this book.

Read More Show Less

Table of Contents

Acknowledgments

About the Authors

Preface

Introduction: Design and Operation of the SAP.

Application Window

Menu Bar

Standard Toolbar

Title Bar

Application Toolbar

Status Bar

Central Work Area

Popup Screens

SAP on the Web

PART I. GETTING STARTED.

Lesson 1: Logging On and Logging Off.

Logging On

Procedure: Logging On With the SAP Logon Pad

Procedure: Logging On With a Desktop Shortcut

Logging Off

Procedure: Logging Off

Lesson 2: Working With SAP Sessions.

Controlling the Application Window Geometry and Location

Creating Multiple Application Windows

Procedure: Creating Multiple Application Windows

Killing a Session

Procedure: Cancelling a Transaction

Customizing the Layout of Application Windows and Screens

Procedure: Customizing With the Options Command

Procedure: Customizing With the New Visual Design Command

Customizing the SAP Easy Access Screen

Procedure: Customizing the SAP Easy Access Screen

Creating Desktop Shortcuts

Procedure: Creating Desktop Shortcuts

Lesson 3: Entering User Profile Data.

Procedure: Entering User Profile Data

Lesson 4: Changing Your Password.

Changing Your Password

Procedure: Changing Your Password When You Log On

Procedure: Changing Your Password After You Log On

PART II. NAVIGATING BETWEEN SCREENS.

Lesson 5: Navigating to Initial Screens With the Menu Folders.

Navigating With the Menu Folders

SAP and User Menu Folders

Searching for Transactions

Procedure: Searching for a Transaction With Keywords

Lesson 6: Navigating to Initial Screens With the Favorites Folders.

Working With the Favorites Folders

Adding Favorites Folders

Procedure: Creating a Favorites Folder

Adding Transaction Links to the Favorites Folders

Procedure: Adding a Transaction Link With Its Code to the Favorites Folder

Procedure: Adding a Transaction Link Without Its Code to the Favorites Folder

Adding Web, Intranet, and E-mail Links to the Favorites Folders

Procedure: Adding a Web or an Intranet Link to the Favorites Folders

Procedure: Adding a Link to Your External E-mail Application in the Favorites Folders

Changing the Names of Favorites Folders and Links

Procedure: Changing the Name of a Folder or Link in the Favorites Folders

Deleting Favorites Folders and Links

Sharing Your Favorites Folders

Procedure: Downloading Your Favorites Folders

Procedure: Uploading Favorites Folders

Lesson 7: Navigating to Initial Screens With Transaction Codes.

Navigating With Transaction Codes

Procedure: Selecting Transaction Codes From the Command Field List Menu

Identifying Transaction Codes

Procedure: Displaying Transaction Codes on the SAP Easy Access Screen

Procedure: Identifying Transaction Codes With the Menu Bar

Procedure: Identifying Transaction Codes With the Status Bar

Searching for Transactions by Transaction Codes

Procedure: Searching for Transactions With Keywords

Lesson 8: Navigating Between Screens With Menu Bars.

Navigating from the Initial Screen of a Transaction

Navigating from the Output Screen of a Transaction

Exploring SAP

PART III. SETTING UP INITIAL SCREENS.

Lesson 9: Entering Codes and Text.

Tips for Entering Codes and Text

Lesson 10: Searching for Codes.

Short Hit List Screens

Multiple-Tab Search Screens

Procedure: Searching for a Code With a Single Search Criterion

Procedure: Searching for a Code With Multiple Search Criteria

Tips for Using Multiple-Tab Search Screens

Structure Search Tree

List-Display Search Screens

Lesson 11: Entering Codes on Multiple Selection Screens.

Design and Operation of a Multiple Selection Screen

Procedure: Copying Multiple Codes Onto the Multiple Selection Screen

Using the Multiple Selection Screen: An Example

Using the Multiple Selection Button

Procedure: Searching for Multiple Codes for the Multiple Selection Screen

Lesson 12: Using Selection Options on Data Entry Fields.

Attaching Selection Options to Data Entry Fields

Procedure: Attaching a Selection Option to a Data Entry Field

Procedure: Removing a Selection Option From a Data Entry Field

What Do the Green Selection Options Do?

What Do the Red Selection Options Do?

Lesson 13: Working With Screen Variants.

Adding Data Entry Fields With the Dynamic Selections Button

Procedure: Adding More Selection Criteria to an Initial Screen

Creating Screen Variants

Procedure: Creating a Variant of an Initial Screen

Changing a Screen Variant

Procedure: Changing a Screen Variant

Procedure: Changing a Screen Variant 2

Calling Up a Screen Variant

Procedure: Calling Up a Temporary Variant

Deleting a Screen Variant

Procedure: Deleting a Screen Variant

Procedure: Creating a Single Default Data Entry on an Initial Screen

PART IV. WORKING WITH OUTPUT REPORTS.

Lesson 14: Sorting, Filtering, and Summing Up Line-item Reports.

Sorting and Grouping Line-item Reports

Example 1: Single-Column Sort of a Line-item Report

Procedure: Single-Column Sort of a Line-item Report

Example 2: Multiple-Column Sort of a Line-item Report

Procedure: Multiple-Column Sort of a Line-item Report

Example 3: Single-Column Sort of a Hit List

Filtering Line-item Reports

Example 1: Filtering the Line-item Report of the IH08 Transaction

Procedure: Filtering a Line-item Report

Example 2: Filtering the Line-item Report of the Cost Center A/P/V Transaction

Procedure: Filtering Positive and Negative Values in a Line-item Report 1

Example 3: Filtering Positive and Negative Values on the Usual Filter Screen

Summing Up Data Columns in Line-item Reports

Procedure: Summing Up Data in a Column of a Line-item Report

Procedure: Grouping and Subtotaling Data in a Line-item Report

Lesson 15. Display Variants for Line-item Reports.

Accessing the Display Variant Functions

The Change Layout Screen

Creating a Display Variant

Procedure: Creating a Display Variant for a Line-item Report

Saving a Display Variant

Procedure: Saving a Display Variant

Applying a Display Variant

Procedure: Applying a Display Variant After the Fact

Deleting a Display Variant

Procedure: Deleting a Display Variant

Working With Display Variants on Other Screens

Lesson 16. Exporting Line-item Reports to Microsoft Excel and Word.

Front-Door Exports

Procedure: Exporting to MS Excel With the Option/Office Integration Button

Procedure: Exporting to MS Excel With the List Menu

Back-Door Exports

Procedure: Back-Door Export of a Line-item Report to MS Excel

Lesson 17. Sending Line-item Reports via SAP E-mail.

The Create Document and Send Screen

The Upper Subscreen

The Lower Subscreen

Entering and Searching for the Names of Recipients

Procedure: Searching for Recipients

Working With Distribution Lists

Procedure: Creating Distribution Lists

Procedure: Searching for Distribution Lists

Reading SAP E-mail Messages

Procedure: Reading E-mail in the Business Workplace

Procedure: Storing or Deleting an E-mail Message

Sending E-mail From the Business Workplace Screen

Procedure: Creating and Sending New E-mail

Procedure: Replying to E-mail

Procedure: Forwarding E-mail

Coda: The Basic Transaction Types

Transaction Type 1: Displaying an Object

Transaction Type 2: Displaying a List of Related Objects

Transaction Type 3 : Creating an Object

Transaction Type 4: Changing an Object

Appendix: Create a Plant Maintenance Order (IW31).

Index.

Read More Show Less

Preface

Welcome to the world of SAP! You are now embarking on a journey into the workings and use of SAP R/3, the leading business enterprise software in the world. (SAP stands for Systems, Applications and Products in Data Processing; R/3 stands for Runtime System 3--in other words, the third release of the software.)

This book is written for the nontechnical end user of SAP R/3; that is, an average person in a company who has perhaps had some experience with desktop applications like MS Word and Excel but little or no experience with more complex enterprise software. This book provides these users with detailed instructions for working with this outstanding and versatile software product.

These instructions do not address any specific purpose, such as working with budget and cost data or managing the inventory of a warehouse. Rather, they describe general or universal procedures for working with any part of the software for any purpose. We firmly believe that a solid grasp of these general procedures and the development of the skills for executing them are the real secret for learning and managing SAP R/3 and using it effectively at your job.

In addition, this book is not intended to be comprehensive. SAP R/3 is very complex in its design and operation, and a comprehensive description of this software would require a much larger- not to mention more expensive- “bible” of a book that most people could not lift. Rather, this book describes the techniques and procedures that are most frequently employed by nontechnical end users when they work with SAP R/3. We decided on its contents after years of using this software, after consulting with other experienced users (the so-called superusers) like ourselves, and after many hours in the classroom teaching it to people like you.

Finally, this book is not intended to be a technical treatise about SAP R/3. If you were looking for instructions about programming, developing, or implementing the software at your workplace, you bought the wrong book. We do not describe the inner workings or architecture of the SAP software (except very briefly in the following pages), because we have found that such information does not help the typical end user work with the software any more effectively. We also avoid the use of technical jargon throughout this book, and instead say our piece in plain, simple English. We do not use a 25-cent word when a 5-cent word will do.

Before we describe the contents of this book, we must devote some words to the origin, design, and operation of SAP R/3.

What Is SAP R/3?

SAP R/3 is a package of integrated applications called modules that record and track the activities and costs of doing business. Its roots extend back to 1972, when five system analysts, all former employees of IBM in Germany, created the software for collecting large volumes of business data in a single computer and then processing this data in real time, when the user needs it. Real-time processing was a particularly novel development at the time because the computers of the 1970s were slow, lumbering machines that required minutes, and sometimes even hours, to process large volumes of data.

Since that time, SAP has grown from a small regional company to the leading provider of business enterprise software in the world. At last count, SAP R/3 is now installed at 84,000 locations in 120 countries around the world, and it is used by more than 10 million people every day. SAP is now the world's third-largest independent software vendor, and it is still growing strong.

The great strength and utility of SAP R/3 are due to a large degree to its architecture or structure, which consists of functional modules, the SAP database, and the graphical user interface or GUI. We use the term system throughout this book to describe this three-part assemblage of software.

The functional modules are discrete software packages that are dedicated to specific tasks, such as accounting, payroll management, and inventory control). They are typically installed in application servers, which are computers that are capable of rapidly processing or “crunching” large volumes of data and then assembling the output of their work in a format that can be read by the user.

The database is the actual collection of business data. These data are stored inside database servers, which are computers with huge amounts of storage memory and the capacity to rapidly exchange data with the application servers.

The graphical user interface or GUI appears on the desktops of the computers or clients that you use to access the software. The centerpiece of the GUI is the application window (called a session by SAP), where you enter commands and data on scenes or screens by means of your mouse and keyboard. Note: Some users may access the SAP software through Web browsers such as MS Internet Explorer. In these cases, the SAP GUI appears inside the frame of the browser window.

There are many modules in the complete version of SAP R/3, but most business enterprises do not use all of them. Rather, they purchase and install or implement only those modules that they need to do their business. The selected modules are then integrated or linked to one another and to the database servers and clients by programmers, and the screens are customized or configured to fit the enterprise's needs. Once the modules are integrated, the boundaries between them vanish and they work with one another as a single, seamless software package. This aggregation of modules is also very flexible: The enterprise can often add more modules whenever they want so that the software grows as their business needs grow.

SAP Transactions

The word transaction describes a single business activity that is conducted with SAP R/3. Some examples of end user transactions are

  • Creating a purchase requisition
  • Generating a budget report for a company department
  • Scheduling the shipment of a material to a plant
  • Recording the activities of a maintenance job
  • Entering employees' weekly work hours
  • Displaying the yearly sales for a product

Every transaction progresses through a four-step workflow of actions, commands, and events.

The typical workflow begins when the end user logs on the SAP system (Step 1). This action calls up the SAP Easy Access screen, which is the default "home page" for the software. The end user works with the elements on this screen to call up or navigate to the initial screen of a transaction (Step 2), where they instruct the software on its specific objectives and then execute it (Step 3). A few seconds later, the output of the transaction appears (Step 4) in one of two forms:

  • A confirmation that some business process, such as the creation of a requisition or the entry of an employee's work hours into the database, was accomplished. This message appears by default at the bottom of the initial screen.
  • A display of data from the database. This usually appears on its own output screen.

A good bit of the communication between the SAP R/3 software and the end user is accomplished during Steps 3 and 4 of this SAP workflow via technical object codes.

A technical object is anything that is monitored and tracked by SAP R/3. This includes tangible objects, such as employees, consumable materials, equipment, and physical plants, and intangible ones, such as work orders, purchase requisitions, and shipping orders.

Every technical object has a unique object code, which is assigned to it when its specifications are entered in the SAP database and which is the primary shorthand means of identifying it. There are literally thousands of such codes in every SAP database, but, fortunately, the software provides a way to search for them, so you do not have to memorize or record them.

Organization and Contents of This Book

The body of this book consists of 17 lessons on the general use of SAP R/3. They are grouped into four parts, which correspond to the SAP workflow.

  • Part I, Getting Started, describes the procedures for logging on and off the SAP R/3 software, customizing the SAP application window and screens to suit your preferences, entering personal and logistical data about yourself, setting default values for the use of the software, and managing your password.
  • Part II, Navigating Between Screens, describes three methods for navigating from the SAP Easy Access screen to the initial screens of transactions, and a fourth method for navigating between initial and output screens.
  • Part III, Setting Up Initial Screens, describes the procedures for entering and searching for object codes and creating customized versions of initial screens.
  • Part IV, Working With Output Reports, describes the procedures for customizing the output reports of certain transactions and e-mailing them to other SAP users.

These lessons are preceded by the Introduction, which describes the design and operation of the SAP application window and its screens, and followed by a Coda, which presents a simple model of the four basic transaction types that are commonly executed by end users.

The instructions in the lessons of this book were written around and illustrated with screens from version 4.7 of the SAP R/3 software. However, they can also be applied to SAP 4.5 and 4.6, which are very similar in their design and operation to SAP 4.7. And with a little effort, they can also be applied to SAP 4.0, which differs slightly in its screen design but not its operation.

Some Words About the Text and Screen Images

This book uses two conventions for highlighting certain texts:

  • The names of all screens and screen elements, including all menus, buttons, and fields, are always presented in bold type.
  • The names of transactions and software, as well as commands, options, and slang terms, are always presented in italic type.

These conventions are intended to help the reader scan through the instructions and easily pick out the critical references within them. The bold text can also be found with page references in the index at the back of this book. In addition, we hereafter refer to the SAP R/3 software simply as SAP, and to people who work behind the scenes to install, configure, operate, and monitor the use of the software as the SAP administrators.

Finally, we should point out that you will often see small differences between the screen images in this book and your versions of the same screens. Some of these differences arise because our screens are customized in a slightly different way from your screens. For example, every business enterprise makes use of a unique group of modules in their system, and so they display their own unique set of folders on their SAP Easy Access screen. We are no exception to that rule. In addition, we have the most current versions of screens at our disposal, and they contain a few more or different elements, more “bells and whistles,” than your screens.

In addition, we have altered many screen images in this book with Adobe Photoshop and other tools. For instance, we have routinely cropped nearly all images to fit them on the pages and not consume too much space- otherwise, this book would probably be twice its present length, weight, and price! In addition, we have hidden screen elements and data that are either proprietary in nature or distracting and not relevant to the points of the lessons.

However, these are differences of degree, not of kind. For the most part, you will not even notice the differences between our screens and your scresens, and the noticeable differences will neither confuse you nor obscure the lessons in this book.

0131860852P06282005

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
  • Anonymous

    Posted December 27, 2009

    No text was provided for this review.


If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)