EXP_0004

Prévia do material em texto

�
�
�
�
An enterprise structure is mapped to SAP applications using organizational units. Organizational units handle specific business functions.
Organizational units may be assigned to a single application. (for example, sales organization assigned to Sales) or to several applications (for example, plant assigned to Materials Management and Production Planning).
The enterprise structure is organized hierarchically in the SAP System. The client is at the highest level and may cover several company codes.
Several plants may be assigned to one company code and several warehouses may be assigned to one plant.
�
The highest-level element of all organizational units is the client. This may be a company group with several subsidiaries. All the enterprise data of the R/3 installation is broken down at least into client area, usually also into lower level organizational structures.
Flexible organizational units in the R/3 System R/3 enable more complex enterprise structures to be modeled. If there are many organizational units, the legal and organizational structure of a company can be presented in different views.
By linking the organizational units the separate enterprise areas can be integrated and the structure of the whole enterprise represented in R/3.
�
There are 3 different types of data in the R/3 system. 
Transactional data is the day-to-day information that is put into or generated by the system. It includes transactions in all applications.
Master data is core information that is shared across applications.
Table data is the data that is specially configured for your business.
�
Master data refers to data records held for a long period of time in the database. (For example, customers, suppliers, materials, accounts).
Master data is stored on a central system (cross-application).
Example: The customer master data - delivery, invoice, payment and so on could be used in one customer order. 
Master data has an organizational function. It is assigned to organizational units. 
Master data may be used across modules
Example: Customer master data share the sales and distribution and financial accounting data. One customer master record may be assigned to the following organizational units:
company code
sales organization
distribution channel
division
�
Using the R/3 Basis System, you can run applications can on different platforms with increased performance and adapt them to customers’ individual requirements. 
The R/3 Basis software processes the application’s requirements and forwards them to the database. It also 
ensures that the application is optimally embedded in the system environment
defines a stable architecture framework for system enhancements
contains the tools for managing the whole system
enables distribution of resources and system components
provides interfaces for decentralized system components and external products
�
Client/Server Basic Principles
In SAP terminology, a software component provides a service (software-oriented view). This type of component can consist of a process or a group of processes and is then called a server for that service.
Software components that use this service are called clients. At the same time, such clients can also be servers for specific services. 
A server often also means a computer (host) on which software components run that provide specific services (hardware-oriented view).
�
Each time you save a quotation request, order, outline agreement, quotation request confirmation, delivery note and so on, an output format is generated by the document concerned. This output format represents a message (message type). The message is then placed in the message queue and then, from here it can be released for printing or output via EDI, or whatever is required. Messages can be released either automatically or manually using a message control program.
You can release individual messages during processing via the different communication media, provided that the relevant message types and communication media have been assigned in Customizing. You can define when and how messages are sent for each document type. 
A form can be defined for each message type, containing for example the format of the message
Message control can be the default value in the master record of the business partner.
�
State-of-the-art data warehouse concepts use a three-tier model as the starting point for implementing efficient, integrated information systems. 
The three tiers subdivide the flow of data, from data acquisition in the operative systems right through to the presentation of information at the top level. 
Integrated, operative applications in OLTP systems form the basis for obtaining information. They are filled with large quantities of master and process data. The Information Systems serve to present this information in a compact and structured form. 
This is achieved by compressing the application data to obtain more compact, informative key figures and then managing it in the database tables of a data warehouse. 
The statistical data obtained in this way can then be analyzed using a variety of analysis tools which are available in the third tier.
These tools offer a wide range of methods that allow statistical data to be analyzed and presented in an efficient and impressive way. They can therefore make a huge contribution towards reducing the time needed to make decisions in modern management.
�
The Logistics Information System is a component of the SAP Open Information Warehouse and provides information from the areas of Sales and Distribution, Purchasing, Production, Inventory Management, Warehouse Management, Plant Maintenance, and Quality Management.
Important information is stored in the Logistics Data Warehouse’s own database, which is maintained in parallel to the operational systems. The key concept here is that the detailed data in the operational systems is transformed into significant key figures.
Further information systems are available for the Financial Accounting, Controlling, and Human Resources modules.
�
SAP Business Workflow is a support tool that can optimize the execution of activities. Work steps carried out consecutively can be automated, the information flows can be coordinated.
Workflow enables the electronic workflow management of structured flows that:
Cover a sequence of activities
Always occur in the same or similar form
Involve several departments or people 
Workflow controls flow according to a predefined model and are especially suited for structured organizations divided into departments/divisions
Workflow brings the ”right” work in the ”right” order at the ”right” time to the ”right” people. This can be done through automated mail or through a workflow item. 
A workflow item is a workflow task that has itself been generated from a workflow and appears in the inbox of the office component.
If human/manual intervention is required, employees can deal with messages in their electronic mail boxes.
Workflow is not: E-mail, EDI, ALE or management of screen sequences within a transaction - Workflow can make use of all these processes.
�
Internet / Intranet Applications in the R/3 System
The Internet Transaction Server (ITS) is the technological basis for Internet application components. The ITS constitutes the interface between an HTTP server (HyperText Transfer Protocol) and the R/3 System. The WebBrowser acts as a presentation program. The HTTP server transfers the data to the browser client. The software is available as of R/3 Release 3.1G and runs under a server for Windows NT® 4.0.
To make it easier for users to connect the R/3 System to the Internet, SAP has developed Internet application components for important business application scenarios. These scenarios can either be used directly or as as a reference for your own developments.
The range of applicationsis not limited to the worldwide Internet. For internal communication in a company, the significance of the Intranet is increasing. In both networks the same protocols and services are used that were originally developed for the Internet. 
A description of the Internet scenarios is available in the online documentation.
�
(C) SAP AG	TAMM40	4-� PAGE \* MERGEFORMAT �1�