Using Procurement and Logistics Execution in SAP ERP, your enterprise can use the appropriate procurement method for every type of good or service, which you intend to procure. The methods range from employee self-service activities to sophisticated plan-driven approaches.
Logistics Execution supports processes for Inventory Management and Warehouse Management, as well as for Transport Execution.
4.5.1 Processes in Detail
Overview
Procurement and Logistics Execution consists of various generic business processes. As with role-based Work Centers, SAP translates and localizes processes according to a given standard (see Section 2.3 - Globalization). However, processes or role-based Work Centers exist, which deviate from this standard, either with respect to their language availability or with respect to their country availability.
With each enhancement package, SAP might add or remove role-based Work Centers or processes from the SAP ERP structure. We thus update this structure of SAP ERP from time to time.
It is possible that processes and role-based Work Centers depend on each other. In these cases, you require more than one process/ role-based Work Center to be able to use a certain product feature.
Documentation References
For more information, see the following additional documentation:
We document the generic business processes or the Role-Based Work Centers of SAP ERP in List of Processes and Role-Based Work Centers SAP ERP EHP
<Number of enhancement package>. You find it in the following path in SAP Service Marketplace http://service.sap.com/erp-ehp - > Media Library - SAP enhancement packages -> Category Enhancement Packages - General.
SAP Note 883072 (Globalization information on SAP ERP) documents the localization and translation status. You find it in SAP Service Marketplace http://service.sap.com/notes.
We describe limitations in SAP Service Marketplace at
http://service.sap.com/notes SAP Note 852235 (Release Limitations for SAP ERP 6.0).
Dependencies among processes and role-based Work Centers are described in SAP Service Marketplace at http://service.sap.com/notes -> SAP Note 824757 (Dependencies between SAP ERP component lists)
For more information about SAP ERP Business Map, see SAP Service Marketplace at http://service.sap.com/businessmaps -> Cross-Industry Maps ->
Enterprise Resource Planning (ERP).
4.5.2 Technical System Landscape
This section lists the software product instances and business packages required to implement the complete key functional area Procurement and Logistics Execution including all business processes or role-based Work Centers. Each product instance consists of different software components. For more information, see Section 5.1 - Application Components.
4.5.2.1 Product Instances
The installation of all processes of the key functional area Procurement and Logistics Execution requires the content instances (see Section 5.3 - Content Instances) shown in the following table:
Table 46: Content Instances Required by the Procurement and Logistics Execution Key Functional Area
Component Name and Version Business Package Name
BI CONT 7.02 SAP NetWeaver Business Intelligence
Content Package
BP ERP05 BUYER 1.0 Business Package Buyer
BP ERP05 INVOICING CLERK 1.0 Business Package Invoicing Clerk BP ERP05 MSS 1.0 Business Package Manager Self-Service BP ERP05 SUPPLIER 1.0 Business Package Supplier
BP SRM 5.0 Business Package Supplier Relationship
Management
BP SUPPLIER COLLABORATION 2.0 Business Package Supplier Collaboration XI CONTENT SRM SERVER 5.5 XI Content for product instance SAP SRM
Server
In addition to the content instances, the following software product instances are required (see Section 5 - Software Components Overview):
Table 47: Software product instances, which are required by the Procurement and Logistics Execution Key Functional Area
Component Name and Version Content of Component
SAP ECC Server SAP ERP Central Component
SAP NW - Business Intelligence SAP NetWeaver 7.0 usage type Business Intelligence
SAP NW - EP Core EP Core (SAP NetWeaver usage type EP
Core)
SAP NW - Process Integration SAP NetWeaver 7.0 usage type Process Integration
SAP NW - Search and Classification SAP NetWeaver 7.0 Stand-Alone Engine Search and Classification (TREX) SAP SRM - Catalog Content Mgmt SAP SRM Catalog Content Management
SAP SRM - Server SAP SRM in SAP ERP
SAP XSS (Self Services) SAP Self Service Product Instance
August 2009 119 Component Name and Version Content of Component
SAP GTS 7.0-SLL-LEG Add-On Package EH&S
Due to possible dependencies with other role-based Work Centers and processes, you may need to implement additional software product instances and business packages. On the other hand, if you choose to implement selected role-based Work Centers or processes only, certain software components shown in the above tables is required.
This Master Guide provides just one way to implement each business scenario or process. For more information about other ways to implement business scenarios, or processes, see SAP Service Marketplace at
http://service.sap.com/scl Scenario & Process Component List.
The Scenario & Process Component List helps you to find realization alternatives for SAP applications, business scenarios, and processes. It shows you which application components you need, to realize a business scenario or process.
Alternatively, install the Software Lifecycle Manager (SLM), described in Section 2.1.4 - Software Lifecycle Manager.
For more information, see SAP Note 824757 (Dependencies between SAP ERP component lists). You can also find more information about
dependencies among processes.
4.5.2.2 System Landscape
The following figure shows an example of a full-fledged system landscape for the key functional area Procurement and Logistics Execution of SAP ERP 6.0.
Figure 15: System Landscape for the Key Functional Area Procurement and Logistics Execution
We do not recommend that you install all components on one host. Rather, you should distribute the components among several hosts. Several possibilities are available to distribute the components. The above figure provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In practice, any distribution of components among hosts is possible. The options are ranging from the minimal system landscape described in Section 3.2.1 - Minimal System Landscape to the maximum distributed landscape in Section 3.2.4 - Individual System Landscape. In the latter option, every component runs on its own host or even on multiple hosts.
You additionally need a dedicated system for SAP Solution Manager and you need to install the related front-end components.
4.5.3 Implementation Sequence
The overall installation sequence in Section 3.4 - Overall Installation Sequence provides a complete overview of the deployment alternatives:
Minimal System Landscape
Extended System Landscape
Extended System Landscape with Firewall
Individual System Landscape
The specific implementation sequence for the key functional area Procurement and Logistics Execution depends on the system landscape you choose and the processes you implement.
If required, review the overall implementation sequence in Section 3.4 - Overall Installation Sequence.
For more information about technical configuration or the configuration of business processes, see SAP Service Marketplace at
http://service.sap.com/solutionmanager:
Component Installation Guides and the Configuration Documentation
Section 2.1.5 - SAP Solution Manager and Section 1.3 - The Main SAP Documentation Types