📄 ch01.htm
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<SCRIPT LANGUAGE="JavaScript">
<!--
function popUp(pPage) {
popUpWin = window.open('','popWin','resizable=yes,scrollbars=no,width=525,height=394');
figDoc= popUpWin.document;
zhtm= '<HTML><HEAD><TITLE>' + pPage + '</TITLE>';
zhtm += '</head>';
zhtm += '<BODY bgcolor="#FFFFFF">';
zhtm += '<IMG SRC="' + pPage + '">';
zhtm += '<P><B>' + pPage + '</B>';
zhtm += '</BODY></HTML>';
figDoc.write(zhtm);
figDoc.close();
popUpWin.focus();
}
//-->
</SCRIPT>
<META NAME="GENERATOR" Content="Symantec Visual Page 1.0.1">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
<TITLE>Sams Teach Yourself ABAP/4® in 21 Days -- Day 1- The Development Environment</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF">
<CENTER>
<H1><IMG SRC="../button/sams.gif" tppabs="http://pbs.mcp.com/ebooks/0672312174/button/sams.gif" BORDER="0"></H1>
</CENTER>
<CENTER>
<P><A HREF="gla01.htm" tppabs="http://pbs.mcp.com/ebooks/0672312174/ch01/gla01.htm"><IMG SRC="../button/previous.gif" tppabs="http://pbs.mcp.com/ebooks/0672312174/button/previous.gif" BORDER="0"></A>
<A HREF="../index.htm" tppabs="http://pbs.mcp.com/ebooks/0672312174/index.htm"><IMG SRC="../button/contents.gif" tppabs="http://pbs.mcp.com/ebooks/0672312174/button/contents.gif" BORDER="0"></A>
<A HREF="../ch02/ch02.htm" tppabs="http://pbs.mcp.com/ebooks/0672312174/ch02/ch02.htm"><IMG SRC="../button/next.gif" tppabs="http://pbs.mcp.com/ebooks/0672312174/button/next.gif" BORDER="0"></A>
<H1>Sams Teach Yourself ABAP/4<sup>®</sup> in 21 Days</H1></CENTER>
<HR SIZE=4>
<H1>Day 1</H1>
<H1>The Development Environment</H1>
<UL>
<LI><A HREF="#ChapterObjectives">
Chapter Objectives</A>
<LI><A HREF="#WhatisR">
What is R/3?</A>
<UL>
<LI><A HREF="#WhatIsthePurposeofR">
What Is the Purpose of R/3?</A>
<LI><A HREF="#WhyDoYouNeedtoKnowThis">
Why Do You Need to Know This?</A>
</UL>
<LI><A HREF="#DiscoveringWhatRLooksLike">
Discovering What R/3 Looks Like</A>
<UL>
<LI><A HREF="#UsingtheRSystemConceptualAreas">
Using the R/3 System Conceptual Areas</A>
<LI><A HREF="#DiscoveringtheRUserInterface">
Discovering the R/3 User Interface</A>
</UL>
<LI><A HREF="#UnderstandingBasis">
Understanding Basis</A>
<LI><A HREF="#UnderstandingClientServer">
Understanding Client/Server</A>
<LI><A HREF="#RSystemArchitecture">
R/3 System Architecture</A>
<UL>
<LI><A HREF="#PresentationServer">
Presentation Server</A>
<LI><A HREF="#ApplicationServer">
Application Server</A>
<LI><A HREF="#DiscoveringtheDatabaseServer">
Discovering the Database Server</A>
<LI><A HREF="#ConfiguringtheServers">
Configuring the Servers</A>
<LI><A HREF="#DefininganRSystem">
Defining an R/3 System</A>
<LI><A HREF="#DefininganRInstance">
Defining an R/3 Instance</A>
</UL>
<LI><A HREF="#ApplicationServerArchitecture">
Application Server Architecture</A>
<UL>
<LI><A HREF="#UnderstandingaUserContext">
Understanding a User Context</A>
<LI><A HREF="#UnderstandingaRollArea">
Understanding a Roll Area</A>
<LI><A HREF="#UnderstandingaDialogStepBR">
Understanding a Dialog Step<BR>
</A>
<LI><A HREF="#UnderstandingRollInRollOutProcessing">
Understanding Roll-In/Roll-Out Processing</A>
<LI><A HREF="#DiscoveringHowtheDataIsSenttothePresentationServer">
Discovering How the Data Is Sent to the Presentation Server
</A>
<LI><A HREF="#UnderstandingtheComponentsofaWorkProcess">
Understanding the Components of a Work Process</A>
<LI><A HREF="#UnderstandingtheTypesofWorkProcesses">
Understanding the Types of Work Processes</A>
<LI><A HREF="#UnderstandingtheLogonClient">
Understanding the Logon Client</A>
<LI><A HREF="#UnderstandingClientDependentandClientIndependentTables">
Understanding Client-Dependent and Client-Independent Tables
</A>
</UL>
<LI><A HREF="#UsingSAPsOpenSQL">
Using SAP's Open SQL</A>
<UL>
<LI><A HREF="#Portability">
Portability</A>
<LI><A HREF="#BufferingDataontheApplicationServer">
Buffering Data on the Application Server</A>
<LI><A HREF="#AutomaticClientHandling">
Automatic Client Handling</A>
</UL>
<LI><A HREF="#Summary">
Summary</A>
<LI><A HREF="#QampA">
Q&A</A>
<LI><A HREF="#Workshop">
Workshop</A>
<UL>
<LI><A HREF="#Quiz">
Quiz</A>
<LI><A HREF="#Exercise">
Exercise 1</A>
</UL></UL>
<HR>
<H2><A NAME="ChapterObjectives"><FONT SIZE=5 COLOR=#FF0000>
Chapter Objectives</FONT></A></H2>
<P>
After you complete this chapter, you should be able to answer
the following questions:
<UL>
<LI>What is an R/3 system?
<LI>What is an R/3 instance?
<LI>What is Basis?
<LI>What platforms does R/3 support?
<LI>What are the possible R/3 system configurations?
<LI>What is the R/3 server architecture?
<LI>What is a logon client?
</UL>
<H2><A NAME="WhatisR"><FONT SIZE=5 COLOR=#FF0000>
What is R/3?</FONT></A></H2>
<P>
R/3 is an integrated suite of applications designed to handle
the data processing for large corporations. It was developed in
Germany by the company named SAP (an acronym for Systems Applications
and Products for data processing).<P>
<CENTER>
<TABLE BORDERCOLOR=#000000 BORDER=1>
<TR VALIGN=TOP><TD WIDTH=600><B>TIP</B></TD></TR>
<TR VALIGN=TOP><TD WIDTH=600>
<BLOCKQUOTE>
When you see the word SAP by itself, it is pronounced "<I>ess-ay-pea</I>." When it is combined with another word, it is pronounced sap, as in "tree sap." You should never say "sap" when referring to the company SAP. Always pronounce it as "<I>ess-ay-pea</I>." Saying "sap" is the surest way to say, "I don't know anything about SAP."
</BLOCKQUOTE>
</TD></TR>
</TABLE>
</CENTER>
<P>
Within R/3 is a runtime environment and an integrated suite of
application programs written in SAP's 4GL-ABAP/4. These application
programs are designed to meet the data processing needs of very
large businesses. R/3 and its predecessor R/2 are particularly
popular with the manufacturing sector.
<P>
R/3 is the system in which your ABAP/4 programs will run. Logically,
it looks like Figure 1.1.
<P>
<A HREF="javascript:popUp('f1-1.gif')"><B>Figure 1.1 :</B> <I>Application modules are all written in ABAP/4,
which is interpreted by Basis executables, which in turn, run
on the operating system</I>.</A>
<H3><A NAME="WhatIsthePurposeofR">
What is the Purpose of R/3?</A></H3>
<P>
The sole purpose of an R/3 system is to provide a suite of tightly
integrated, large-scale business applications. A few of these
can be seen at the top of Figure 1.1. The standard set of applications
delivered with each R/3 system are the following:
<UL>
<LI>PP (Production Planning)
<LI>MM (Materials Management)
<LI>SD (Sales and Distribution)
<LI>FI (Financial Accounting)
<LI>CO (Controlling)
<LI>AM (Fixed Assets Management)
<LI>PS (Project System)
<LI>WF (Workflow)
<LI>IS (Industry Solutions)
<LI>HR (Human Resources)
<LI>PM (Plant Maintenance)
<LI>QM (Quality Management)
</UL>
<P>
These applications are called the <I>functional areas,</I> or
<I>application areas</I>, or at times the <I>functional modules</I>
of R/3. All of these terms are synonymous with each other.
<P>
Traditionally, businesses assemble a suite of data processing
applications by evaluating individual products and buying these
separate products from multiple software vendors. Interfaces are
then needed between them. For example, the materials management
system will need links to the sales and distribution and to the
financial systems, and the workflow system will need a feed from
the HR system. A significant amount of IS time and money is spent
in the implementation and maintenance of these interfaces.
<P>
R/3 comes prepackaged with the core business applications needed
by most large corporations. These applications coexist in one
homogenous environment. They are designed from the ground up to
run using a single database and one (very large) set of tables.
Current production database sizes range from 12 gigabytes to near
3 terabytes. Around 8,000 database tables are shipped with the
standard delivery R/3 product.
<H3><A NAME="WhyDoYouNeedtoKnowThis">
Why Do You Need to Know This?</A></H3>
<P>
This is important for you, as an ABAP/4 programmer, to know because
these applications are all written entirely in ABAP/4. These are
the applications you must understand to be a proficient developer
in R/3.
<P>
For example, assume you know ABAP/4 and you have been asked to
write a financial report summarizing debits and credits by fiscal
year for each vendor in the enterprise. You might know how to
code in ABAP, but would you know how to begin to solve such a
request?
<P>
Or perhaps your job entails new development in ABAP/4. You are
asked to design a system that provides stock quotations to potential
buyers. If you do not know the financial and sales and distribution
systems, you won't know if you are creating something that already
exists in R/3. Nor can you know if there are R/3 tables that already
contain data similar to or identical to the type of data you want
to store. These applications are highly integrated. A developer
who takes the approach "I'll build my own tables and keep
my own copies of the data," might soon find his data is redundant
and must be routinely synchronized with the rest of the database.
He has built an application that does not take advantage of the
highly integrated nature of the R/3 environment.
<P>
I only point this out because many developers who wish to become
independent consultants think that learning ABAP/4 is all they
need to develop in the R/3 system. It is certainly a great start,
but it is only the start. The importance of training in a functional
area can be overlooked or unknown to those interested in becoming
proficient ABAP/4 consultants. Obviously, much of this learning
can and will be done on the job. However, I hope to illustrate
the point that learning the ABAP/4 language is only the beginning
of a long journey into SAP. If you desire to be successful as
an independent consultant, you will eventually need to acquire
functional area knowledge.<P>
<CENTER>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -