10542289 SRM210SRM Enterprise Planning Config

? SAP AG 2004

SRM210 SAP Enterprise Byer 4.0 Configuration

THE BEST-RUN E-BUSINESSES RUN SAP

© SAP AG 2004

SRM210SAP Enterprise Buyer 4.0 Configuration

? Software Components: EBP, SAP R/3 ? 2004/Q3 ? Material number: 50068069

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

COPYRIGHT

Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

? Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

? Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. ? IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

? Oracle is a registered trademark of Oracle Corporation. ? UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. ? Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc. ? HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology. ? Java is a registered trademark of Sun Microsystems, Inc. ? JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by

Netscape. ? MaxDB is a trademark of MySQL AB, Sweden. ? SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

? These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Course Prerequisites

Recommended? SAPSRM mySAP SRM solutionoverview

Prerequisites

? Basic knowledge of Microsoft Windows

? Knowledge of SCM500 Processes in Procurement

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Target Group

Duration? 5 days

Audience

? SRM or Enterprise Buyer consultants.

? Customer Project Team Members involved in an SRM implementation

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Overview

Content

? Course Goals

? Course Objectives

? Course Overview

? Main Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Course Goals

This course will prepare you to:

? Bring your knowledge of the technical and application-specific requirements of EBP to a level that will enable you to effectively participate in an implementation

? Customize the core functionalities of an EBP system

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Course Objectives

? Overview on mySAP SRM E-Procurement

? SAP EBP roles and E-Procurement processes

? Configuration of all major scenarios of an SAP EBP system to enable the web-based procurement process

? Explain major interfaces to SAP and Non-SAP components from a conceptual point of view

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Course Overview - Content

mySAP SRM E-Procurement

Appendix

Backend Integration Principles

Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration

Plan Driven Procurement

Self-Service Procurement

Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

? SAP AG 2004

Main Business Scenario

? Your company, Phoenix Enterprises, recently purchased the SAP solution mySAP SRM. As a firststep in the implementation of all Supplier RelationshipManagement scenarios, the project team members need to configure Enterprise Buyer to support all self-service procurement and plan-driven procurementprocesses for the procurement of material as well as services.

? Our project team is responsible for configuring and customizing EBP to meet the requirements of the US organization. In a second phase, other subsidiaries of Phoenix Enterprises will follow.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 1-1

? SAP AG 2004

mySAP SRM E-Procurement - Content


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004


Contents

? mySAP SRM E-Procurement overview

? The procurement process with EBP

? Roles in EBP

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Enterprise Buyer: Unit Objectives

? mySAP SRM E-Procurement

? SRM procurement processes

? Roles in EBP

At the conclusion of this unit, you will be able to describe:

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

mySAP SRM E-Procurement: Business Scenario

? Prior to installing the productive environment, some core team members are to set up a test environment with some of Phoenix Enterprise‘s original organizational data. In a configured client, delivered by SAP Educational, they do their first review of the major processes within Enterprise Buyer.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Evolution from BBP to Enterprise Buyer

March

B2B Procurement 1.0

May

B2B Procurement 2.0

Sept March

Enterprise Buyer 2.0

Employee-Self-ServiceCatalog Search

TenderingComponent PlanningBW-IntegrationStandalone Scenario

Hosted version/IntegrationMarketSet 1.0

Direct ProcurementContract ManagementContent ManagementHosted Version(Enhancements)Mobile Procurement


1999 2000 2001

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Evolution from EBP to SRM

mySAP SRM 2.0

Vendor ListConditions

Sourcing CockpitPlan-driven Procurement

2001 2002

October December

Enterprise Buyer 3.0 Enterprise Buyer 3.5

2003


December

Extended Classic ScenarioSourcing

Change Documents

mySAP SRM 3.0

New WorkflowsVendor Evaluation

Service Procurement

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Components of mySAP SRM

? Exchange Infrastructure ? Master Data Management (MDM)

Integration components

mySAP SRM

mySAP SRM – eProcurementmySAP SCE

Supplier Collaboration Engine

? Enterprise Buyer Prof. 4.0

? Business Inf. Warehouse 3.1

? Requisite Bugs Eye 3.5

? Requisite eMerge 3.5

? Enterprise Portal 5.0

? IPC 4.01

? ITS 6.10

? Supplier Self -Services 2.0

? Bidding Engine 4.0

? Live Auction 1.0

? User Management 3.0

? SRM can be acquired in different configurations. The smaller package is mySAP SRM eProcurement. This solution builds around the established component EBP – now in version 4.0. The BW reporting tool can be attached and the third-party catalog management tools from Requisite are included, as well as the Enterprise Portal from SAP.

? If you want more functionality, you can select components from the mySAP Supplier Collaboration Engine. This area includes the components of the SRM eProcurement and additional collaboration components such as Supplier Self Service, auctioning tools, and User Management.

? Supplier Self-Service (SUS) enables suppliers to take part in the procurement process to improve the communication between business partners and thus, to reduce process costs. Standardized formats (XML) are used to receive and send standard orders, confirmations, and invoices. After an order comes in to SUS, the supplier responds whether and when he can deliver. At delivery, the supplier captures the delivered quantity and invoices the items.

? The Exchange Infrastructure comes with the SCE to integrate the SRM components but can also be acquired separately to map and route documents between other non-SRM applications. The Exchange Infrastructure is subject to separate licensing for ? Integration of mySAP SRM to non-SAP back ends ? Integration of suppliers’ systems ? Integration of SAP or non-SAP components outside mySAP SRM

? SAP Master Data Management (MDM) offers features for supplier and product harmonization between SAP EBP and multiple back ends. This is only included for the global spend analysis scenario.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Common E-Procurement Scenario

Execution Buying

? Browse through online catalogs

? Create shopping cart

? Check status

? Receive product

? Create Confirmation and Invoive or approve them

? Receive purchase order

? Confirm goods deliveryor service performed

? Create invoice

? Approve or rejectrequirement

? Changes Requirement

Employee

Employee

Manager

Vendor

? Company employees are responsible for the procurement of the goods and services that they need for their work area. This takes the pressure off of the purchasing department, who in turn can concentrate on strategic tasks, such as contractual negotiation.

? Employees either search in a catalog for a suitable material or service, or enter the requirement directly on the entry screen and transfer this to the shopping cart. Employees can hold the requirements or order them.

? When an order is placed, the Enterprise Buyer system checks whether the shopping cart needs to be approved.

? If the manager rejects the document, employees receive a work item in their inbox, informing them of the rejection. Employees can then process the requirement coverage request directly from the work item.

? The vendor receives the purchase order. After the goods are delivered or the service is performed, employees can confirm this. If business partners enter the confirmation, the system starts a workflow and places the confirmation in the employees’ inbox for their approval.

? Employees check the documents that the business partner created (invoice or confirmation) and release the document. If the document contains errors, employees can also reject it. The system then notifies the vendor or service provider via e-mail.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Enterprise Buyer Offers More...

Strategic Procurement

Operational Procurement

? Process purchase Orders

? Carry out Sourcing

? One-Step Buying over Exchanges

? Integration Exchanges

Analysis

? Business-warehouse-based enterprise reporting

? Negotiate Contracts

? Vendor Evaluation

? Complete Purchase orders

? Sourcing

? Process Contracts

? Process Bid Invitations

? Process Auctions

? Maintain Vendor List

StrategicPurchaser

OperationalPurchaser

? Operational purchasers are responsible for processing and issuing purchase orders in the Enterprise Buyer system. If the requester creates a shopping cart in which the data is incomplete, for example, the vendor is missing for an item, purchasers receive the incomplete purchase order in their worklist. They can complete the data and send the purchase order to the vendor.

? Purchasers can define templates for recurring procurement processes that employees can then use when creating shopping carts. Purchasers can also shop on behalf of other users, for managers, for example.

? Purchasers are also responsible for processing of shopping carts with value limit and for the purchasing data in the business partner master records.

? The strategic purchaser is responsible for strategic procurement tasks. Creating public and restricted bid invitations, and comparing received bids belongs to this work area.

? The strategic purchaser is responsible for the creation of contracts and for the purchasing data in the business partner master records. The strategic purchaser compiles vendor lists.

? Enterprise Buyer is integrated with the Business Information Warehouse (BW) to provide sophisticated reporting. The Business Information Warehouse is used for both operational and strategic analysis.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Analytics with SAP BW S

AP

BW

So

urc

esy

stem

s

Data retrieval

Data storage

Data presentation

APO Non-SAP

EBP R/3 ExternalFiles

BW

? SAP BW integrates with SAP systems as well as non-SAP systems. This is partly due to the three-level Data Warehouse architecture of data storage, data extraction, and data presentation.

? The source systems from which the usable data is extracted to the Business Information Warehouse are on data retrieval level. These can be SAP systems (R/3 or R/2) but can also be non-SAP systems or external files.

? In the data storage process, data is extracted from the various source systems and loaded into the Data Warehouse.

? Finally, the reports are called and the data is evaluated at the data presentation level. There are two types of evaluation, Excel evaluations and HTML evaluations.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Role-based Analytics in EBP

Strategic Purchaser

T M

? The analyses are integrated into the role concept of Enterprise Buyer and can be run from the user‘s browser launchpad. For example, strategic purchasers can analyze purchase orders, confirmations, invoices, bid invitations, and bids without having to leave Enterprise Buyer. Managers and purchasing managers have different analyses that provide information on the procurement behavior of their organization.

? This graphic provides a screenshot from an operational analysis where procurement values per vendor are analyzed initiated from the Purchaser‘s launchpad.

? You can add the following SAP BW single roles to any role in EBP: ? SAP_BW_BBP_PURCHASING ? SAP_BW_BBP_STRATEGIC_PROCUREM ? SAP_BW_BBP_MANAGER ? SAP_BW_BBP_QUOTATION.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP Implementation Scenarios

Implementation scenarios

? Classic

? Extended Classic

? Decoupled

? Standalone

Enterprise Buyercan operate in different scenarios

? The classic scenario You implement Enterprise Buyer and one or more ERP systems. All Materials Management is mapped in the ERP system.

? The extended classic scenario The purchase order is created locally within Enterprise Buyer. If the data in the shopping cart is insufficient to generate a complete purchase order, the data is supplemented manually within Enterprise Buyer before being transferred to the back-end system. The purchase order in Enterprise Buyer is the leading purchase order. Goods receipts (confirmations) and invoices can be entered in Enterprise Buyer or in the back end.

? The decoupled scenario Requirement coverage requests for materials and services are directly processed further, and purchase orders are placed, in the Enterprise Buyer system. The follow-on documents for the purchase orders are also created in the Enterprise Buyer system (confirmation, goods receipt / service entry and invoice). You can continue to procure production materials and services using the Materials Management functions in your ERP system.

? The standalone scenario You have no materials management in your ERP system and are using the procurement functions in the Enterprise Buyer.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping cart created

Product Master

Global Business Partner

Classic Scenario

Workflow approval

Invoice

Goods Receipt

Purchase Order

Purchase Requisition

Message to vendorXML, e-mail, fax

Invoice

Confirmation

Enterprise Buyer R/3-back end orNon-SAP back end

? You implement Enterprise Buyer and one or more back-end systems (SAP or Non-SAP). All Materials Management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entry sheets, and invoices) exist in the back-end system.

? When the shopping cart is ordered, a workflow is triggered that checks whether approval is necessary. ? If approval is required, a work item is sent to the Inbox of the relevant approver. ? If approval is not required, the necessary purchase requisitions, purchase orders or reservations are

created for the shopping cart. Which documents are created, and in which back-end system, depends on the information in the shopping cart and on the settings in Customizing for Enterprise Buyer.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004


Extended Classic Scenario

Workflow approval

Invoice

Confirmation


Purchase Ordercomplete/incomplete

Invoice

Purchase Order

Goods Receipt

Enterprise Buyer

Product Master


R/3-back end orNon-SAP back end

? This scenario is an extension of the classic scenario, which continues to exist. In the classic scenario, all Materials Management takes place in the back-end system, while in the extended classic scenario, the complete procurement process takes place locally. Communication between Enterprise Buyer and the back-end system is via RFC. The purchase order is created locally in Enterprise Buyer.

? If the data in the shopping cart is insufficient to generate a complete purchase order, the data is supplemented manually within Enterprise Buyer before being transferred to the back-end system. The purchase order in Enterprise Buyer is the leading purchase order. The plant is the criterion used for splitting shopping cart items into different purchase orders because the purchasing organization is determined in the back-end system on the basis of the plant. Goods receipts (confirmations) and invoices can be entered in Enterprise Buyer or the R/3 back end.

? The following takes place in the Enterprise Buyer system: Search for source of supply, pricing , tax determination. Commitments are updated in the back-end system, account assignment and budget check are performed against the back-end system.

? Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the back-end system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the back-end system.

? This process does not support: Purchase orders based on limit shopping carts or procurement card functions. These require the invoice to be local.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Standalone Scenario

Enterprise Buyer


Workflow approval

Invoice

Confirmation



Invoice posting in FI, only

Product Master



? The customer does not have a productive Materials Management system and wants to handle the entire process locally within the Enterprise Buyer, integrating only to an accounting system.

? Accounting processes (including FI, CO, and AM) must still be handled by a back-end system. All validations and approvals are handled directly within Enterprise Buyer rather than in a back-end system. This is possible by incorporating Material Management functions into the application, which will have its own product master. Migration tools are provided to bring Material Master data from SAP back-end systems into the application product master.

? A shopping cart is created locally and will be further processed locally to create a purchase order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Decoupled Scenario

Enterprise Buyer



Invoice

Confirmation


Workflow approval

Backend


Local

ProductCategory

Invoice

Goods Receipt

Purchase Order


Product Master



? You have a productive MM back-end system, but want to handle parts of the process locally and other parts within the MM system. This means that specific shopping basket items create POs or requisitions with all follow-on processes in the back end MM, while others are processed locally.

? For example, office supplies could be processed locally while all items for plant maintenance goods are processed in the back-end system (makes sense if you have already defined your communication interface to your supplier, for example, EDI-Interface).

? The requirement requests for non-production materials and services are processed directly in the EBP System, where the purchase orders are also created. If data for the purchase orders is missing, the data is- completed in the EBP system. The follow-on documents (GR/service confirmation and invoice) are also created in the EBP system. Using the Materials Management functions in your ERP system, you continue to purchase production goods and services.

? Whether the system creates a PO in the back-end system or locally depends on the product category. You have to define in the customizing whether the product category is a local product category or a back-end product category,. By using a BADI, you can define your own rules.

? Where there are several back-end systems, you can define how back-end systems are determined using Customizing.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Roles in EBP Business Scenario

? Create Shopping Cart, ? Check Status? Confirmation? Invoice

? Approve? Analyze

? Employee? Secretary

? Manager

? EBP? Any Product Catalog

? EBP? SAP BW

? EBP? Business Connector

? OperationalPurchaser

? Vendor

? Sourcing, RFQ? Execute Purchase Order

? Confirm Goods Delivery or Service Performance, Invoice

? EBP? SAP BW? DB

? ContentManager

? EBP? eMerge? Exchange Infrastructure

? Connect Catalog? Import and Export Data

? Administrator ? Monitoring ? User Management

? EBP

? Analyze? Create Contracts? RFQ

? StrategicPurchaser

? EBP? SAP BW

? People perform Roles to participate in Business Scenarios implemented by Components

? Roles describe the activities that internal employees or external business partners perform in a business scenario.

? After logging on to the system, users see all functions that they need to process their tasks. In the Implementation Guide (IMG) under: Enterprise Buyer professional edition ? Application-Specific Basic Settings ? Roles, you can find the tasks that are assigned to each role.

? Independent of the role, all users need a user master record to log on to the system. SAP provides the following composite roles for Enterprise Buyer: ? SAP_EC_BBP_EMPLOYEE - Employee ? SAP_EC_BBP_MANAGER - Manager ? SAP_EC_BBP_SECRETARY - Purchasing assistant ? SAP_EC_BBP_PLANNER - Component planner ? SAP_EC_BBP_OP_PURCHASER - Operational purchaser ? SAP_EC_BBP_ST_PURCHASER - Strategic purchaser ? SAP_EC_BBP_RECIPIENT - Internal dispatch manager ? SAP_EC_BBP_ACCOUNTANT - Accountant ? SAP_EC_BBP_ADMINISTRATOR - Administrator ? SAP_EC_BBP_CONTENT_MANAGER – Content manager ? SAP_EC_BBP_BIDDER - Bidder ? SAP_EC_BBP_VENDOR - Vendor

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Enterprise Buyer: Unit Summary

? mySAP SRM E-Procurement

? SRM procurement processes

? Roles in EBP

You are now able to describe:

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: mySAP SRM E-Procurement

Topic: Process Overview

At the conclusion of this exercise, you will be able to:

? Perform the procurement process for SAP EBP

Your company has been given a pre-configured SAP EBP system to use for practicing and understanding the associated business processes. In this exercise, you will walk through some of these processes before beginning to configure and customize the SAP EBP system for your company.

NOTE: Throughout these exercises, the ## designation refers to your group number.

1-1 Create a shopping cart containing two items (product master and catalog item).

Log on to CLIENT 300 of the EBP SYSTEM from the BROWSER:

User ID: SRM210-##

Password: init

Client : 300

Change your password to learn.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Order a product

Choose Shop in the launch pad

Go to Internal Goods/Services in area Step1: Select Goods/Service

Enter Cas* in the Product Description field.

Select Start.

Choose T-SRM## as Product.

Select Add to Shopping Cart

View the availability of this product in the details of the line item.

Choose Details.

Open Availability.

Is this item available?

Select to close the Item Details.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-2 Order from the Catalog.

Select Step 1 Select Goods/Service

in Shop in 3 Steps.

Choose BugsEye (own window)

Enter ‘Alkaline Batteries AA’ as Search text.

Choose Find.

Select <first item of vendor Arami-15>

Enter 300 in the Quantity field.

Choose

to add item to BugsEye shopping cart.

Choose Order Items to transfer the BugsEye shopping cart to the EBP shopping cart.

1-1-3 Check the Basic data in the Details of the new item.

Select Detail for the second item.

What product category is assigned to this item?

Before you order your shopping cart, check the total value of the cart. The total value should exceed $500 USD. (It should also not exceed $10,000 USD.)

Choose to close the item details.

Choose Continue.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-4 Order your shopping cart.

Select Order.

What is the name of the shopping cart?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Check the status of your shopping cart.

Select Check Status in the launch pad

Choose Today as Timeframe.

Choose Start

If necessary click on

'your shopping cart' to expand the item overview.

What is the status of each line item?

1-2-1 Which manager has to approve your shopping cart?

Select Detail in the shopping cart item.

Choose Approval Preview.

Who has to approve your shopping cart?

1-2-2 Check the individual settings for your user.

Select Settings at the top off the screen.

Go to Required data tab.

What is your full name?

Select Log off at the top off the screen.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Assume the role of the manager and approve your shopping cart.

Log on to CLIENT 300 of the SAP EBP SYSTEM from the BROWSER:

User ID: MANAGER210

Password: init

Client : 300

Change the password to learn.

1-3-1 Find your shopping cart in the inbox of the manager and approve it.

Select Approval in the launch pad.

Choose Detail for your shopping cart.

Check that both items are marked as approved.

Select Save.

Choose Log off at the top off the screen.

1-4 Check the status of your shopping cart and confirm the goods receipt for the batteries.

Log on to CLIENT 300 of the SAP EBP SYSTEM from the BROWSER:

User ID: SRM210-##

Password: learn

Client : 300

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4-1 Again check the status of your shopping cart.

Select Check Status in the launch pad.


Select Start.

If necessary select


What is the status of each item now?

Status of item 1:

Status of item 2:

1-4-2 Record the type of document and the document number that was created for each line item.

Choose Details for the first item.

Go to Follow-On Documents Area.

What document was created?

Document number:

Select Details for the second item.

Go to Follow-On Documents Area

What document was created?

Document number:

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4-3 Confirm the good receipts for the batteries.

Select Confirm Goods / Services

in the launch pad.

Choose ‘Confirm Goods Receipt/Services Performed’

in the Make a selection field.


Select Start.

Select <item with your back-end purchase order 30083000## for Alkaline Batteries>

Select Create confirmation.

Type in SRM-## as Confirmation Name.

Select Confirm

What message do you get after you perform the confirmation?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4-4 Post the invoice for the purchase order.

Select Enter Invoice / Credit Memo

in the launch pad.

Choose Invoice as document.

Choose Create with PO reference for action.


Select Start.

Choose <your back-end purchase order 30083000## for Alkaline Batteries>

Select Enter Invoice.

Type in ##0001 as Invoice number (Vendor).

Select Calculate Total Amount.

Select Post.

Confirm with OK the upcoming message.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4-5 View the history of the item.

Select Check Status in the launch pad.


Select Start.

If necessary, click on


What is the status of the batteries?

Select Details for this item.

Go to Follow-On Documents area

What documents were created?

Select Log off at the top of the screen.

1-5 Back-end Processes

You have a decoupled scenario and process a local Purchase Order with the corresponding follow-on documents. Are processes triggered at all in the back-end and if yes, which ones?

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-6 Implementation Scenarios

Why could a Buyer not be able to change a Back-end Purchase Order in the SAP EBP system, when processing the classic scenario?

When can you change a document in the SAP EBP system?

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions

Unit: mySAP SRM E-Procurement

Topic: Process Overview

1-5 Back-end Processes

You have a decoupled scenario and process a local Purchase Order with the corresponding follow-on documents. Are processes triggered at all in the back end and if yes, which ones?

When processing a local Purchase Order, first check the accounting assignments in the back-end system. Then a purchase commitment is built up.

The Goods receipt confirmation has no effect in the back-end system because a product assigned to a local product category is held in the Enterprise Buyer. When entering the invoice in Enterprise Buyer, the posting is triggered in the back-end system and the Commitment is abolished.

1-6 Implementation Scenarios

Why could a Buyer not be able to change a Back-end Purchase Order in the SAP EBP system when processing the classic scenario?

When can you change a document in the SAP EBP system?

When processing a Back-end Purchase Order in the Enterprise Buyer, the Purchase Order document is sent to the back-end system where it is held and can be changed. Because the document is not held physically in the Enterprise Buyer, it cannot be changed there.

With the extended classic scenario, the documents for Back-end Purchase Orders are also held in the Enterprise Buyer System and can only be changed there.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Backend Integration Principles - Content


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Back-end Integration Principles: Business Scenario

? Before starting the core back-end integration and configuration steps, the team members have to familiarize themselves with the integrated e-procurement architecture. This will include the SAP ITS as well as basic interfacing technology and integration principles such as ALE and RFC communication.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Enterprise Buyer Architecture

? Elements of an E-Procurement scenario

? Backend Integration

? Integration Principles

? Integration Configuration

At the conclusion of this unit, you will be able to explain:

Backend Integration Principles: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Connects to (multiple) back -end systems without modifications (R/3 Plug-In)

SAPBackend

Non-SAPBackend

-------------

Release 3.1Honwards

JDE, Oracle, Baan, Peoplesoft**

** via SAP Exchange Infrastructure or SAP Business Connector and appropriate adapter

Architectural Flexibility

RFC (RemoteFunction Call)

XML-Messages

----- -- - -----

-------------

-------------

Enterprise Buyer ALE/ IDOC

SAPSupplier

SelfService

XML-Messages*

* via SAP Exchange Infrastructure

? Enterprise Buyer can connect to multiple ERP instances. This is especially useful in larger corporations that have varied functionality spread over multiple servers. For example, different purchasing organizations are often set up on separate back-end systems within one company. Enterprise Buyer can communicate and coordinate document creation across these various instances.

? Enterprise Buyer is a separate SAP System that you can use in a heterogeneous system environment. The system environment can include SAP as well as non-SAP back-end systems. The components Financial Accounting and Controlling must exist in your ERP system.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

System Landscape

Browser / SAP Enterprise Portal

BW

R/3

APO

Business Partners / Marketplaces

SAP Exchange Infrastructure

Catalog ITS

RFC / ALEXML

XML

IDoc

ITS

OCI

SUS EBP

? RFC = Remote Function Call ? OCI = Open Catalog Interface ? ALE = Application Link Enabling ? XML = Extensible Markup Language ? ITS = Internet Transaction Server ? EBP = Enterprise Buyer ? BW = Business Warehouse ? APO = Advanced Planner and Optimizer ? Benefits: ? Stronger decoupling of presentation and application logic ? SAP R/3 as primary back-end business execution system ? Possibility to integrate third-party back ends ? Protect back-end system from high Internet/intranet user interaction ? Distribute workload across different, specialized server components ? High scalability ? Exchange business documents with SAP Exchange Infrastructure (XI)

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Component Architecture

? Independent SAP component that communicates with an ERP system.

? Familiar SAP R/3 infrastructure remains.

? ABAP virtual machine

Database

Web Application Server

Application Logic

EBP / SAP CRMComponent

ABAP Workbench

Standard Admin & Monitoring Tools

Business Workflow

EBP System

? ERP is Enterprise Resource Planning. ? EBP is an SAP R/3-like system that contains purchasing application and basis components. ? EBP holds all shopping carts and other documents.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SAP ITS - Web-Enabling Technology

InternetTransaction

Server

? The SAP Internet Transaction Server (ITS) provides the Web-enabling technology.

? 3 ways to maintain templates

? SAP@Web Studio

? Transaction SE80 in EBP

? Copy existing templates

Database


Application Logic


ABAP Workbench


Business Workflow

EBP System

? The SAP Internet Transaction Server (ITS) allows internet and intranet users to communicate directly with the SAP R/3 by running standard transactions, function modules, and reports as Internet applications.

? When a user starts an application from a Web browser, the request is passed to the Web server. The Web server transmits the request to the SAP ITS, which sets up a connection to the SAP R/3. When a connection has been established, the SAP ITS controls the communication and the data exchange between the SAP R/3 and the Web server.

? The SAP ITS consists of two main components - the WGate (Web gateway) and the AGate (application gateway).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SAP ITS – Internet Transaction Server

SAP ITS translates DIAG into HTML

? Due to the technical differences between SAP R/3 and the Internet, a special program is needed to connect the two systems. This is achieved with the SAP Internet Transaction Server (ITS), which is one of the basic modules in Web Basis.

? The SAP ITS acts as a gateway between the Web server and SAP R/3. SAP ITS has been available since SAP R/3 release 3.1G.

? The SAP ITS controls the user logon procedure and the data flow between SAP R/3 and the Internet. The SAP ITS also manages the user session.

? When you call an Internet Application Component, all requests are passed from the Web browser to the connecting HTTP server. The HTTP server prompts the SAP ITS to set up a connection to SAP R/3. When the connection has been established, the SAP ITS controls communication and the data flow between the HTTP server and SAP R/3.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SAP ITS – Internet Basics

Browser/ Webserver

Enterprise Buyer

MIME-Objects?Pictures? Icons

ITSW-Gate

ITSA-Gate

TCP/IP

Service?Transactions?Template?Field entries

RFC

Transaction callData transfer

ITS Server

Windows NT ServiceIACOR

Enterprise Buyer

<SE80>TemplatesMime Files

Publishingvia RFC

Publishing Templates to the ITS

Templates Display Process:

? As preparation for displaying the templates within the Web browser, they first have to be published to the ITS.

? It is possible to publish single templates via transaction SE80 or to publish all templates, for example,. during system setup via report W3_PUBLISH_SERVICES, whereby all templates will be copied to the ITS.

? First you have to select the ITS Destination where you want to publish. As a prerequisite for publishing, the IACOR (Internet Application Component Object Receiver) Service has to be active.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Catalogs

? Multimedia catalogs can be accessed from Enterprise Buyer .

? Open Catalog Interface (OCI) allows any supplier catalog to be interfaced.

Database


Application Logic


ABAP Workbench


Business Workflow

EBP System

? Connectivity to any e-catalog - mySAP SRM provides the Open Catalog Interface (OCI) where you can map to various catalog scenarios, including external vendor catalogs, catalog content on e-marketplaces, external catalogs from purchasing service providers, and local/internal catalogs.

? The OCI describes the data exchange between the Enterprise Buyer and external catalog applications. It enables the transmission of selected goods and services from an external catalog to the Enterprise Buyer. Together with the business workflow, a document, for example, a purchase order, is created and will be sent to the vendor.

? An external catalog is located either within the intranet or on the Internet. It also enables the seamless integration of the SAP Online Store or SAP Internet Sales as well as third-party catalogs such as Requisite, Intershop, Harbinger and Grainger.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Interfacing Technology: IDoc

ApplicationApplication

System 1

SAP R/3

System 2

SAP R/3,non-SAP

IDocIDoc

? Object related by message types

? IDoc as data container

? Asynchronous communication

? Release independent

? Extensive exception handling

? Goods receipt, invoice and Procurement Card statement

Intermediate Document

? ALE = Application Link Enabling ALE is a communication between logical systems. Logical systems can be SAP R/3, SAP R/2 or non-SAP systems. ALE distribution models are based on message types that indicate the appropriate IDoc types. ? IDOC = Intermediate Document

The IDoc interface is used to exchange business data between two different systems. The IDoc interface consists of the definition of a data structure and the processing logic for this data structure. Different message types (for example, delivery notes or purchase orders) usually have specific formats, the SAP IDoc types. However, several related message types can be assigned to one IDoc type. For example, the IDoc type ORDERS01 transfers the “logical” message type ORDERS (purchase orders) and ORDRSP (purchase order confirmation). ? Batch Transfers ? Update document status ? Synchronize document changes in SAP R/3

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Call

Result

System XYZ

Processes parameter values

1, 2, 3 and returns results

Function ABC

RFC client RFC server

Remote Function Call Principles

Remote Function Call (RFC)

Callingfunction ABCin system XYZ

with parameters1,2,3

? A Remote Function Call (RFC) is the call of a function module (routine) in a partner system. The caller is the RFC client and the called partner is the RFC server.

? RFC is based on the known RPC model (Remote Procedure Call) from the UNIX-TCP/IP environment. ? RFC in the SAP environment is based on a CPI-C interface implemented by SAP. ? The remote call of a function module is easier for an application programmer to use than program-to-

program communication based on CPI-C, because data is exchanged only using defined parameters. ? Information about where to call a function module is stored on the client side.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

3rd Party

Integration with SAP Exchange Infrastructure (XI)

WebAS 6.20

XMLMessage

iDochttp(s)

Integration Repository

Integration Directory

Firewall

PublicMarket-place

Enable XI in EBP

BusinessPartner

BusinessPartner

BusinessPartner

SAP Exchange Infrastructure 3rd party adapter

EBP SUS

The following documents can be sent in XML format: ? Purchase Order ? Order Acknowledgment ? Shipping Notification ? Confirmation ? Confirmation response ? Invoice ? Invoice response ? Data can be exchanged in XML format between Enterprise Buyer and any vendor system. Data can be

exchanged either directly using EBP XML or any XML dialect. The data is transferred between the vendor system and the SAP Exchange Infrastructure via HTTP. The SAP Exchange Infrastructure communicates with Enterprise Buyer via HTTP. The graphic illustrates the data exchange between the Enterprise Buyer system and external systems.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Integration - Abstraction Layer

Function Call

Push

Pull

Plug- In

BAPI SAP Back-endSystem

non-SAP Back-endSystem

SAP Exchange

Infrastructure

SAP Back-endSystem

XML XML

Abstraction Layer

Enterprise Buyer

Dispacher Driver Spooler

? Depending on the release level used, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the back-end system. The abstraction layer encapsulates the BAPI calls in the back-end system that are necessary to generate the back-end documents from requirement coverage requests. The abstraction layer accesses the following sources of information:

? Dispatcher: This function module analyzes the Customiz ing settings and then knows: ? Which driver it must call ? Which back-end system it is communicating with ? The back-end system release

? Driver: For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back-end system.

? Spoolers : The spooler controls the transfer of documents from the Enterprise Buyer system to the back-end system. If errors occur during the transfer, for example, the back-end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back-end system at regular intervals and to transfer the documents.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

BADI: Business Add-Ins for Enterprise Buyer

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects.They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery.

What are Business Add-Ins? ? Business Add-Ins (BAdIs) are programmer-defined places in source code where application

development, industry sectors, customers, and partners can add their own code, without modifying the original object.

? Business Add-Ins are designed for SAP R/3 users who require certain functions that are too specialized to be included in the standard system, but that are needed often and therefore have been designed to be integrated into SAP R/3.

? SAP R/3 users can implement Business Add-Ins with the needed logic, or they can use one of the delivered standard solutions.

? The interface of a Business Add-In is upward compatible so the call of an enhancement from the standard software and the validity of the calling interface remain unaffected. They do not need to be registered in SSCR.

? While customer exits (enhancements using SMOD/CMOD) are designed for use in a two-level system landscape (SAP, customer), Business Add-Ins are designed for use in a multiple -level system landscape (SAP, country versions, IS solutions, partner, customers, and so on). In addition, Business Add-Ins can be created and delivered at any level of the system landscape.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

* Business Add-In BBP_DETERMINE_LOGSYSMETHOD IF_EX_BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS.

DATA: ATTRIBUTES TYPE TABLE OF BBP_ATTRIBUTES,WA_ATTRIBUTES TYPE BBP_ATTRIBUTES,WA_ITEM_DATA TYPE BBP_OCI_ENRITEM.

* Einlesen der Attribute zum angemeldeten UserCALL FUNCTION 'BBP_GET_ATTRIBUTES'

EXPORTINGUSER_ID_P = SY-UNAME

TABLESIT_ATTR_P = ATTRIBUTES

EXCEPTIONSUSER_NOT_FOUND = 1ORGUNIT_NOT_FOUND = 2OBJECT_ID_NOT_FOUND = 3AMBIGUOUS_POSITION = 4OTHERS = 5.

CHECK SY-SUBRC = 0.

* Suchen nach dem Attribute SYSREAD TABLE ATTRIBUTES WITH KEY ATTR_ID = 'SYS' INTO WA_ATTRIBUTE S .CHECK SYS-SUBRC = 0.

* Wenn das Attribut da ist, überschreibt es das logische SystemLOOP AT ITEM_DATA INTO WA_ITEM_DATA.

WA_ITEM_DATA-LOGICAL_SYSTEM = WA_ATTRIBUTES-VALUE.MODIFY ITEM_DATA FROM WA_ITEM_DATA.

ENDLOOP.

ENDMETHOD.

Example of a BAdI

For product category OFFICE SUPPLIES, back-end system A is determined. However, you also want to take into account the field Vendor when determining the back -end system. For the vendor OFFICE1 and Purchasing organization 0001, the system is to create the purchase order in back-end system B.

? Using Business Add-Ins, you can change the SAP standard program without having to make any modifications to it.

? Example of a Business Add In: Determine Back-end System/Company Code ? You can use the Business Add-In BBP_DETERMINE_LOGSYS to define your own criteria for

determining the back-end system/company code. ? In the standard system, the back-end system is determined using the product category. ? The back-end system is then placed in the field ITEM_DATA-LOGICAL_SYSTEM. Then the system

calls the Business Add-In BBP_DETERMINE_LOGSYS. ? The company code is put in the field ITEM_DATA-BC_CO_CODE. Then the system calls the Business

Add-In BBP_DETERMINE_LOGSYS. ? In the method DETERMINE_LOGSYS, two table parameters are available:

ITEM_DATA - This contains the most important item data for the shopping cart.. ACCT_DATA - This contains the account assignment data for the shopping cart item.

? This means that you can now determine the back-end system /company code depending on other item data (or any combination of data) and overwrite the fields ITEM_DATA-LOGICAL_SYSTEM and ITEM_DATA-BE_CO_CODE.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Maintain Local Product Categories

? Product Hierarchies

? Product Categories?R/3 Material Group? Local EBP categories

? Loaded Schema ? ecl@ss?UNSPSC

<comm_hierarchy>

Enterprise Buyer

? Product categories make it possible to group products together according to different criteria. ? If a product type (for example, material or service) is assigned to a product category, only products of

this product type can be assigned to the category. Assigning a product type to a category makes it possible to assign as many set types as required to the category. In product maintenance, these set types appear as subscreens in the views (that is, on the tab pages such as Basic Data) that can be maintained for a product.

? Product categories are arranged in category hierarchies, of which there can be several. All lower-level categories inherit the product type and the set types of the higher-level category. Additional set types can be assigned to lower-level categories.

? A set type may be assigned to several product categories in a category hierarchy. However, a set type may be assigned only in one hierarchy. This prevents a set type being assigned to a product more than once using different categories.

? A product can be assigned to several product categories so long as each category is in a different category hierarchy, that is, a product can be assigned to only one category per hierarchy.

? Back-end product categories are replicated via the CRM Middleware; local product categories can be maintained directly in transaction <comm_hierarchy>.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Check Account Assignment: Procedure in Detail

Check FI data: Function Module META_ACCSERV_CHECKACCASSIGNMT

Account Assignment

Account Assignment

No validation

Enterprise Buyer

Create Shopping Cart Item

Enterprise Buyer R/3 back-end

ACCOUNTING (FI/CO)

There are three options for checking account assignments:

? After creating an item in the shopping cart, you need to validate the account assignments. ? Check Account Assignment ? Validation can be done in the following environments: ? In the Enterprise Buyer Professional (local validation of FI data) ? In the back-end system (real-time validation of FI data) ? You can choose not to validate at all

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Back-end Determination Using Product Category

Document in EBP withitems and Product category

BADI to determine Back-end System: BBP_DETERMINE_LOGSYS

Back-endSystem I

(non-SAP)

Back-endSystem II(SAP R/3)

Back-endSystem III

(EBP)

Enterprise Buyer

? The following customizing steps have to be performed to determine different back-end systems for different product categories: ? The RFC destinations to different back-end systems have to be assigned (and vice versa). ? ALE customizing (logical systems, distribution model) ? Back-end systems and EBP system have to be defined in IMG. ? Each product category is assigned to a back-end system as target (a wildcard “*“ can be used).

? A BAdI (BBP_DETERMINE_LOGSYS) can be implemented to change the logic of the standard.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Technical Basic Settings

<spro>

?RFC Destinations

?ALE Distribution Model (IDocs)

?Backend System Definition

?Define Backend for Product Category

Enterprise Buyer

? The Implementation Guide (IMG) of the Enterprise Buyer displays two different sections for Basic Settings: Technical Basic Settings and Cross-Application Basic Settings

? In Technical Basic Settings, you define technical parameters like: ? The RFC destination for the back-end system(s) , the ALE settings (This is necessary only if you want

to post goods receipt documents and invoices in the back-end system) ? Back-end system(s) that you work with, the back-end system that the documents are posted in,

depending on the product category. (The product category is in the requirement coverage request item. ? The subsequent document (such as a purchase order) for the item is created in the system that you

enter here for the product category. ? Information about the spooler and information about the update frequency.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Cross-Application Basic Settings

? EBP Number Ranges

? Number Ranges per Back-endSystem

? EC/ ECDP Transaction Types

? Enable Use of ExchangeInfrastructure if in use

? Tax Calculation

Enterprise Buyer

<spro>

? In Cross-Application Basic Settings, you define application-specific parameters like: ? Number ranges for the Materials Management (MM) documents in the Enterprise Buyer system. ? Number ranges used by various back-end systems for back-end purchase orders, purchase requisitions,

and reservations. ? The transaction type for all MM documents that are to be created in the Enterprise Buyer system,

controlling the number range intervals that the document numbers are determined from information related to companies. ? Tax codes that can be entered in invoices. ? The rules that the Enterprise Buyer system uses to automatically determine the payment conditions. ? The documents that are to be created in the back-end system from a requirement coverage request.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Scheduling Reports/Background Jobs

CLEAN_REQREQ_UP

BBP_GET_STATUS_2

RSPPFPROCESS

Background jobs have to bescheduled to run periodically.

BBPERS

RSWUWFMLEC

Background Jobs

? RSPPFPROCESS (optional): To transfer your purchase orders to the vendors, schedule this report to run at regular intervals.

? BBP_GET_STATUS_2: This report updates requirement coverage requests (shopping carts). To ensure that information on the status of back-end purchase requisitions, purchase orders, and reservations is up-to-date, schedule this report to run daily in the Enterprise Buyer system.

? CLEAN_REQREQ_UP: Updating of documents is executed asynchronously in the back-end system. You can only process the shopping cart in the Enterprise Buyer system after the update has been carried out. For example, it updates the shopping cart with the back-end PO information. The system checks whether the documents have been updated. You need to schedule the job periodically.

? BBPERS (optional): If you use ERS (evaluated receipt settlement) for local purchase orders for which confirmations exist, you have to start BBPERS.

? RSWUWFMLEC (optional): This report sends an e-mail to the mail client of employees who have specified that their work items are to be forwarded there. The report creates an e-mail for each work item that can be processed.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Enterprise Buyer Architecture

? Elements of an E-Procurement scenario

? Backend Integration

? Integration Principles

? Integration Configuration

You are now able to explain:

Backend Integration and Principles: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Back-end Integration Principles

Topic: Communication Configuration


? Configure the logical system

? Create a distribution model to send IDocs from EBP to the back-end system as well as for procurement cards

? Schedule background jobs

Your technical team members have installed the SAP EBP system and it is ready to be configured and customized. In this exercise, you will perform the necessary configuration steps required to establish communication between SAP EBP and the Back-end SAP R/3.

1-1 Locate the RFC Destination T90CLNT90 defined for the back-end R/3 that will be connected to the EBP SYSTEM.

Log on to YOUR CLIENT of the EBP SYSTEM from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: init (or learn)

Change your password to learn, if necessary.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Add the customizing Transaction Codes SPRO (Customizing – Edit Project) and SM59 (RFC Destinations) to your favorites.

Choose Menu path

Favorites ? Insert Transaction

Enter SPRO as the Transaction code.

Choose Continue.

Choose menu path Favorites ? Insert Transaction

Enter SM59 as the Transaction code.

Choose Continue.

1-1-2 Locate the RFC Destination T90CLNT090 defined for the back-end R/3 that will be connected to the EBP system.

Never change any RFC settings!

Start transaction RFC Destination (SM59) from you favorites.

Select R/3 connections.

Double- Select R3_00_800

Verify R3_00_800 is the RFC destination.

Select Test connection.

Choose Back.

Return to the SAP Easy Access screen.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Configure the logical system.

1-2-1 View the logical system definition in the EBP component.

Start transaction Customizing – Edit Project (SPRO) from your favorites.

Goto ? SAP Reference IMG

SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Technical Basic Settings ? ALE Settings (Logical System) ? Distribution (ALE) ? Sending and Receiving Systems? Logical Systems ? Define Logical System

Choose Continue to confirm the information Table is cross-client.

Verify that SRM_00_3## is listed.

Verify that EBP Client 3## is the name of the Logical System SRM_00_3##.

Select Back.

1-2-2 Locate your client 3## and logical system assignment and view its details.

… ? Technical Basic Settings ? ALE Settings (Logical System) ? Distribution (ALE) ? Sending and Receiving Systems ? Logical Systems ? Assign Client to Logical System

Choose Continue to confirm the information Table is cross-client.

Select your client 3##.

Verify that USD is the currency.

Choose Details

Verify that Changes to Repository and cross-client Customizing

are allowed.

Verify that 0 (No restriction) is the Protection level.

Select Back (twice).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Create a distribution model for sending IDocs between EBP and the back-end R/3.

… ? Technical Basic Settings ? ALE Settings (Logical System) ? Distribution (ALE) ? Modeling and Implementing Business Processes ? Maintain Distribution Model and Distribute Views

Select Switch between display and edit mode

to switch to Change mode.

Choose Create model view

Enter SRM_00_3## to T90CLNT090

as the Short text.

Enter SRM3##T90 as the Technical name.

Choose Continue

1-3-1 Add message types to your model.

Select Add message type.

Choose SRM3##T90 as the Model view.

Choose SRM_00_3## as the Sender.

Choose T90CLNT090 as the Receiver.

Choose ACC_GOODS_MOVEMENT as the Message Type.

Select Continue.

To simplify the next steps, expand the model you just created and select the Receiver System R/3 Back end T90CLNT090.

(To expand the model, Select on the right sight of the text.)

Repeat the following steps for each message type in the table.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select R/3 Back end in the Model.

Select Add message type each time.

Choose ACLPAY as the Message type.

Select Continue.

Choose BBPCO as the Message type.

Select Continue.

Choose BBPIV as the Message type.

Select Continue.

Choose MBGMCR as the Message type.

Choose Continue.

Select Save.

What does each of the message types mentioned do?

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3-2 Add the BAPI for procurement cards to your model.

Select SRM_00_3## to T90CLNT090 as the Model.

Choose Add BAPI.

Choose T90CLNT090 as the Sender/client.

Choose SRM_00_3## as the Receiver/server.

Choose BBP_PCSTAT as the Obj. Name/interface.

Choose Create as the Method.

Select Continue.

Select Save.

1-3-3 Generate the partner profiles for your model.

Select SRM_00_3## to T90CLNT090.

Choose menu path

Environment ? Generate Partner Profiles

in the menu bar.


Choose T90CLNT090 as the Partner system.

Choose 3 as the Version.

Set Transfer IDoc Immediately as the Output mode.

Select Execute.

For which message types parameters were created?

________________________________________________________

________________________________________________________

________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



1-3-4 Distribute the model to the back-end R/3.

Select SRM_00_3## to T90CLNT090.

Choose menu path

Edit ? Model View ? Distribute

in the menu bar.

Select T90CLNT090 as Receiver of model view.

Choose Continue.

Choose Back.

1-3-5 Optional: Now you could log off from the EBP system.

1-4 Find the distribution model in the customizing of the back-end R/3.

Log on to the BACK-END R/3:

Client : 800

User ID: BACK-##

Password: init (or learn)

Change your password to learn, if necessary.

1-4-1 Add the transaction code SPRO (Customizing – Edit Project) to your favorites.

Choose menu path Favorites ? Insert Transaction

Enter SPRO as the Transaction code.

Choose Continue.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4-2 Generate the partner profiles for the model view on the back-end R/3.



SAP Customizing Implementation Guide ? SAP Web Application Server ? Application Link Enabling (ALE) ? Modeling and Implementing Business Processes ? Maintain Distribution Model and Distribute Views

Verify that SRM_00_3## to T90CLNT090 is listed.

Verify that SRM3##T90 is the Description/technical name of SRM_00_3## to T90CLNT090.

Select SRM_00_3## to T90CLNT090

Choose menu path

Environment ? Generate partner profiles


Choose SRM_00_3## as the Partner system.

Choose 3 as the Version.

Set Transfer IDoc immediately as the Output mode.

Select Execute.


1-4-3 Log off from the back-end R/3.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 Define the back-end system and set the control parameters.

Log on to YOUR CLIENT of the EBP SYSTEM using the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn

1-5-1 Verify the definition of the back-end R/3.



SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Technical Basic Settings ? Define Back-end Systems

Check All entries for T90CLNT090.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-2 Create a new entry for your EBP logical system. Define this for use as a local EBP system.

Select New Entries.

Choose SRM_00_3## as the Logical system.

Enter Local EBP System as the Description.

Choose SRM_00_3## as the RFC Destination.

Choose Local B2B System as the Sys.type.

Do not set Indicator RFC.

Set Indicator Local.

Choose real-time back-end validation of FI data

as the FI valid.

Select Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-3 Set the control parameters that facilitate the communication to the back-end R/3

… ? Supplier Relationship Management ? SRM Server ? Technical Basic Settings ? Set Control Parameters

Enter EBPADMIN as the Value control record for the SPOOL_JOB_ USER.

Enter 60 as the Value control record for the SPOOL_LEAD_ INTERVAL.

Enter 10 as the Value control record for the SPOOL_MAX_ RETRY.

Select Save. .

What is the purpose of the entries SPOOL_JOB_USER, SPOOL_LEAD_INTERVAL and SPOOL_MAX_RETRY?

__________________________________________________________

__________________________________________________________

__________________________________________________________

__________________________________________________________

Return to the Easy Access screen.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Cross-Application Basic Settings


? Create product categories

? Define the back-end and local systems

? Define the number ranges required in the EBP Component and the back-end R/3

? Define the objects to be created from shopping basket items

? Define the G/L accounts to be used

? Define Transaction Types

? Define the tax codes used for invoicing

You are now ready to customize the specific requirements for your company. In this exercise, you will perform the steps necessary to create the appropriate documents in the destination systems.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1 View the current product categories that reside in the EBP component and create a new product category to add to the sub-hierarchy.

2-1-1 Add the product hierarchy transaction code, COMM_HIERARCHY to your favorites in the EBP System.

Choose menu path

Favorites ? Insert Transaction

Enter COMM_HIERARCHY as the Transaction code.

Select Continue.

2-1-2 Standard EBP determines the appropriate back end based on the product category. View the product categories that are currently housed in the EBP component.

Start transaction Maintain Categories and Hierarchies (COMM_HIERARCHY) from your favorites

Select Start on the Search tab.

Double- click on

R3MATCLASS to display this hierarchy

Expand R3MATCLASS (Material group)

(hierarchy)

Expand R3MATCLASST90CLNT090 (Material group R/3 back end)

(sub-hierarchy)

The product categories that are included in the sub-hierarchy have been replicated from the R/3 back end.

Select the product category 001 at the top level and take a look at the tabs underneath.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-3 Create a product category under the sub-hierarchy associated with manually created product categories.

Select R3MATCLASSSRM_00_3## (Material group EBP Client 3##)

Select Display ? Change to switch to the Change mode.

Select Continue.

Select Category … to create a new category.

Enter LOCAL1 as the Category ID.

Enter Office Supplies (L) as the Description.

Select Continue.

Verify that Indicator Product/ Object Assignment Possible

is set.

Select R3MATCLASSSRM_00_3##

Select Category … to create a new category.


Enter Food and Beverage (L) as the Description.

Select Continue

Verify that Indicator Product/ Object Assignment Possible

is set.

Select Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-4 Add the product hierarchy transaction code, COMM_PRAPPLCAT to your favorites.

Choose menu path

Favorites ? Insert Transaction.

Enter COMM_ PRAPPLCAT as the Transaction code.

Select Continue.

Start transaction

COMM_ PRAPPLCAT (Assign Hierarchy to Applications)

from your favorites

Verify that Hierarchy ID R3MATCLASS is assigned to application Purchasing

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-5 Define the R/3 back end and local system determination based on the product categories.



SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Technical Basic Settings ? Define Back-end System for Product Category

Select New Entries.

Choose LOCAL1 as the Category ID.

Choose SRM_00_3## as the Target System.

Select Enter

Choose LOCAL2 as the Category ID.

Choose SRM_00_3## as the Target System.

Select Enter

Enter * as the Category ID.

Choose T90CLNT090 as the Source System.

Choose T90CLNT090 as the Target System.

Select Enter.

Select Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Define the number ranges to be used for shopping carts, purchase orders, requisitions, reservations, and service entry sheets.



SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Number Ranges ? Define Number Ranges for Shopping Carts and Follow-On Documents.

2-2-1 Within the Reqt. Coverage Request number range object, create the number range for Shopping Carts using the following information:

Select Intervals to change the intervals.

Select Interval to insert a new interval.

Enter 01 as the No.

Enter 1000000000 as the From number.

Enter 1999999999 as the To number.

Select Insert.

2-2-2 Within the Reqt. Cov. Request number range object, create the number range for the Back-end Purchase Orders using the following information:

Select Interval.

Enter PO as the No.

Enter 30083##000 as the From number.

Enter 30083##999 as the To number.

Select Insert.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2-3 Within the ‘Reqt. Cov. Request’ number range object, create the number range for the Back-end Requisitions using the following information:

Select Interval.

Enter RQ as the No.



Select Insert.

2-2-4 Within the Reqt. Cov. Request number range object, create the number range for the Reservations using the following information:

Select Interval.

Enter RS as the No.



Select Insert.

Select Save.


Confirm every messages regarding transport of number range intervals with Enter.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2-5 Define the number ranges to be used for local purchase orders.

… ? Number Ranges ? Define Number Range for Local Purchase Orders

Select Intervals.

Select Interval.

Enter 01 as the No.



Choose Insert.

Select Save.

Select Continue.

Choose Back (twice).

2-2-6 Define the number ranges to be used for confirmations.

… ? Number Ranges ? Define Number Range for Local Confirmations of Services and Goods Receipts

Select Intervals.

Select Interval.

Enter 01 as the No.



Select Insert.

Select Save.

Select Continue.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2-7 Define the number ranges to be used for local invoices

… ? Number Ranges ? Define Number Range for Local Invoices

Select Intervals.

Select Interval.

Enter 01 as the No.



Select Insert.

Select Save.

Select Continue.



… ? Number Ranges ? Define Number Range for Local Bid Invitations

Select Intervals.

Select Interval.

Enter 01 as the No.



Select Insert.

Select Save.

Choose Continue.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



… ? Number Ranges ? Define Number Range for Local Bids

Select Intervals.

Select Interval.

Enter 01 as the No.



Select Insert.

Select Save.

Select Continue.


2-2-10 Optional: Now you could log off from the EBP system.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-3 Back end: Find the number ranges and document types that were created for purchase orders.


Client : 800

User ID: BACK-##

Password: learn

2-3-1 Find the number range that corresponds to your number range for purchase orders (PO).



SAP Customizing Implementation Guide ? Materials Management ? Purchasing ? Purchase Order ? Define Number Ranges

Select Intervals to display the intervals.

Verify that 3004000000 to 3009999999 is the Number range for No. PO.


2-3-2 Find the number range that corresponds to your number range for requisitions (RQ).

…? Materials Management ? Purchasing ? Purchase Requisition ? Define Number Ranges

Select Intervals.

Verify that 4000000000 to 4009999999 is the Number range for No. RQ.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-3-3 Find the number range that corresponds to your number range for reservations (RS).

…? Materials Management ? Inventory Management and Physical Inventory ? Number Assignment ? Define Number Assignment for Reservations

Select Intervals.

Select Intervals.

Verify 0030000000 to 0039999999 is the Number range for No. RS.

2-3-4 Log off from R/3.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-4 View the transaction types in the EBP system.

Log on to YOUR CLIENT of EBP from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn

2-4-1 What transaction types are defined for confirmations, invoices, local purchase orders, bid invitations and vendor quotations?



SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Define Transaction Type.

Verify that AUC is the Transaction type for Auction.

Verify that BID is the Transaction type for Bid Invitation.

Verify that CONF is the Transaction type for Confirmation.

Verify that EC is the Transaction type for Purchase Order.

Verify that GCTR is the Transaction type for Purchase Contract.

Verify that INV is the Transaction type for Incoming Invoice.

Verify that PCTR is the Transaction type for Purchase Contract.

Verify that QUOT is the Transaction type for Vendor

Quotation.

Verify that SHC is the Transaction type for Shopping Cart.

Verify that VL is the Transaction type for Vendor List.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-5 Define Objects to be created in the target system.

… ? Cross-Application Basic Settings ? Define Objects in Back-end System (Purch. Reqs, Reservations, Purch. Orders)

2-5-1 Define the objects to be created in the R/3 back end using the following information:

Select New entries..

Enter * as the Purch. Grp.

Choose 001 (with F4) as the Category ID.

Choose Reservation generated if stock available, …

as the Int. Proc.

Choose Purchase order if item data complete …

as the Ext. Proc.

Select Enter.

Enter * for the Purch. Grp.

Choose 002 (with F4) from Category ID.


as the Int. Proc.


as the Ext. Proc.

Select Enter.

Enter * for the Purch. Grp.

Choose 003 (with F4) from Category ID.


as the Int. Proc.


as the Ext. Proc.

Select Enter.

Select Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



2-6 Financial Configuration

2-6-1 View the account assignment categories used in the EBP system.

…? Cross-Application Basic Settings ? Account Assignment? Define Account Assignment Categories

Verify that AS is the local counterpart of the back-end account assignment category A.

Verify that CC is the local counterpart of the back-end account assignment category K.

Verify that FI is the local counterpart of the back-end account assignment category K.

Verify that NET is the local counterpart of the back-end account assignment category N.

Verify that OR is the local counterpart of the back-end account assignment category F.

Verify that SO is the local counterpart of the back-end account assignment category C.

Verify that WBS is the local counterpart of the back-end account assignment category P.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-6-2 Define the G/L account to be used based on product category and account assignment category.

…? Account Assignment ? Define G/L Account for Product Category and Account Assignment Category

Select New entries.


Choose CC as the AcctAssCat.

Enter 400000 as the G/L account no.

Select Enter.


Select OR as the AcctAssCat.

Define 400000 as the G/L account no.

Select Enter.


Select AS as the AcctAssCat.

Define 11000 as the G/L account no.

Select Enter.

Select Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-6-3 Define the system for tax calculation.

…? Cross-Application Basic Settings ? Tax Calculation? Determine System for Tax Calculation

Verify that Tax Calculation Occurs in R/3 is selected as Choose.

Select Back.

2-6-4 Define the two tax codes (from R/3 back end) to be used for invoicing.

… ? Cross-Application Basic Settings ? Tax Calculation ? Enter tax codes

Select New entries.

Enter I0 (i zero) as the Tax ind.

Enter Input Tax 0% as the Tax Description.

Set Indicator No tax.

Set Indicator Default.

Select Enter.

Enter I1 (I one) as the Tax ind.

Enter Input Tax 10% as the Tax Description.

Select Enter.

.Select Save.

.Select Back (twice).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-7 Schedule the following background jobs for the EBP component.

2-7-1 Define the background job CLEAN_REQREQ_UP.

Choose menu path

System ? Services ? Jobs ? Define Job

Enter Cleaner_3## as the Job name.

Select Start condition.

Select Immediate.

Select Period values.

Select Other period.

Define the job to run every

2 minutes.

Select Save (three times).

Select Step.

Select ABAP program.

Enter CLEAN_REQREQ_UP as the name.

Select Save (twice).

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-7-2 Check the background job Cleaner_3##.

Choose menu path

System ? Services? Jobs ? Job Overview

Enter Cleaner_3## as the Job name.

Select Execute.

Check if your job Cleaner_3## has the status released.

2-7-3 Define the background job BBP_GET_STATUS_2.

Choose menu path

System ? Services ? Jobs ? Define Job

Enter GET_STATUS_3## as the Job name.

Select Start condition..

Select Immediate.

Select Period values.

Select Other period.

Define the job to run every

2 minutes.

Select Save (three times)

Select Step

Select ABAP program

Enter BBP_GET_STATUS_2 as the name

Select Save (twice).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-7-4 Which job is used to check whether all data has been transferred correctly to the back-end system, delete obsolete table entries in EBP and maintain the numbers of the created documents?

____________________________________________________________

____________________________________________________________

Which job retrieves new information from the back-end system, for example, the purchase number after it was converted from a purchase requisition?

____________________________________________________________

____________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Test you Knowledge

Test your knowledge about the following topics:

? Product Categories

? Back-end and local systems

? Number ranges

? Definition of the G/L accounts to be used

? Transaction Types

? Tax Codes

?

Question to Exercise 2-1-2

What is the name of the main hierarchy to which all of the product categories are assigned?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

What is the name of the sub-hierarchy to which the product categories replicated from the back end are assigned?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Name the replicated product category at the top of the list?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________


What is the name of the sub-hierarchy to which the product categories created manually in the EBP component will be assigned?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________


Why must the hierarchy R3MATCLASS be assigned to an application?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________


Apart from the way shown in exercise 2-1-5, what other method can be used for determining the back-end system?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Is the number range for purchase orders internally or externally defined and why?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

What is the document type to which the number range for purchase orders is assigned?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions


Topic: Communication Configuration

General information and technical details:

The target host and IP address depend on the training system you are working with. If you enter a host name as the target host in an RFC destination, its IP address is stored internally in the database table RFCDES (destination administration). This speeds up the RFC connection initiation, since the host name does not need to be converted into its IP address.

Together with the target host, the System number identifies the RFC Destination, no matter which logical name is maintained.

If you test the connection, the test should perform successfully. You can see the Connection Type, as well as the time the system needs to connect.

1-3-1 What does each of the message types mentioned do?

ACC_GOODS_MOVEMENT, ACLPAY – only necessary in the Procurement Card Scenario that the invoice and the current turnover figures can be passed on to the back-end system

BBPCO – transfers commitments to the back-end CO for local Pos

BBPIV – transfers invoicing information to the back end in FI

MBGMCR – posts the material document of the goods receipt on the back-end system

1-3-3 For which message types parameters were created?

Six outbound parameters were created for the following message types:

ACC_GOODS_MOVEMENT, ACLPAY, BBPCO, BBPIV, MBGMCR, SYNCH

One inbound parameter was created for the message type BBP_PCSTAT.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-3 What is the purpose of the entries SPOOL_JOB_USER, SPOOL_LEAD_INTERVAL and SPOOL_MAX_RETRY?

The purpose is to define the user for the spool job, the time that passes between two tries, and the maximum number of tries until the spool job is carried out.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions


Topic: Cross-Application Basics Settings

2-7-4 Which job is used to check whether all data has been transferred correctly to the back-end system, delete obsolete table entries in EBP and maintain the numbers of the created documents?

CLEAN_REQREQ_UP

Which job retrieves new information from the back-end system, for example, the purchase order number after it was converted from a purchase requisition?

BBP_GET_STATUS_2

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions


Topic: Test your Knowledge


What is the name of the main hierarchy to which all of the product categories are assigned?

R3MATCLASS

What is the name of the sub-hierarchy to which the product categories replicated from the back end are assigned?

R3MATCLASST90CLNT090

Name the replicated product category at the top of the list.

001 Metal processing


What is the name of the sub-hierarchy to which the product categories created manually in the EBP component will be assigned?

R3MATCLASSSRM_00_3##


Why must the hierarchy R3MATCLASS be assigned to an application?

You have to specify which Category Hierarchy is being used by Enterprise Buyer.


Apart from the way shown in exercise 2-1-5, what other method can be used for determining the back-end system?

The Business Add-in (BADI) BBP_DETERMINE_LOGSYS can be used.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Is the number range for purchase orders internally or externally defined and why?

The number range is externally defined. This is because the EBP system determines the number and sends it to the back-end R/3.

What is the document type to which the number range for purchase orders is assigned?

The number range PO is assigned to the document type EC.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organization - Content


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? After maintaining the basic configuration steps in EBP, parts of the organizational structure of Phoenix Enterprises have to be mapped to the organizational plan in EBP, which the system administrator has to create. The project team members should familiarize themselves with the role of purchasing organizations and groups and product categories, and with user attributes and user creation tools.

Organization: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? The key components of an organizational plan

? Attributes and attribute inheritance

? User Maintenance Tools


Organization: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organizational Plan

For example: Departments, groups or project teams.

For example: Board of Directors

Organizational Structure

For example: Employees and managers

For example: Company code, catalogs, document type, cost center, Storage location,product categories, plant,…

Users (US)

Organizational Unit (O)

Attributes

ACS

BSA

BUK

BWA

CUR

KNT

WGR

WRK

Root Organizational Unit

? The organizational structure forms the hierarchy in which the various organizational units of an enterprise are arranged according to tasks and functions.

? A root organizational unit is the unit at the highest level of an organizational structure. When you build up organizational structures, you build them from the root organizational unit down. You have to start by creating the root organizational unit.

? An organizational unit represents any type of organizational entity found within a company, for example, subsidiaries, divisions, departments, or special project teams. Organizational units are one of the objects that make up organizational plans.

? Each user attribute represents a value that is stored under a particular name within the organizational structure.

? You can define multiple values for attributes. ? Default values for attributes are possible. ? You can define different values for host-dependent attributes in configurations with back-end systems.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organizational Plan

Create Root ppoca_bbp

Change ppoma_bbp

Display pposa_bbp

Productions Newtown Square

Edward Employee - S 50000728

Edward Employee - BP 000000109

Edward Employee – US EMPLOYEE

Edward Employee – US EMPLOYEE

Organizational Unit

Position

Central Person

Business Partner-Id

SU01- User

<PPOMA_BBP>

? When creating the organizational units you have to assign at least the previously-mentioned attributes to give users the values they need to use the Shop-functionality in EBP.

? First you have to create a root organization. It can be one but also more than one. ? Afterwards, you create the organizational units belonging to the root organization underneath the root. ? After having the complete structure, you can create user. EBP users are an integral part of the

organizational plan. They belong to a certain organization and have to have a position, a business partner ID, a central person and a SU01-User ID.

? There are technically no EBP users until they belong to the structure that is automatically created when you create a user in the organizational plan

? If they have the mandatory attributes, then they are allowed to act as EBP users via the browser.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Attributes for Enterprise Buyer scenario

Attributes Extended Attributes

? A set of user attributes is required for working with Enterprise Buyer professional edition. Each user attribute represents a value that is stored under a particular name within the organizational structure. Depending on a user's role, a different set of attributes is required. You maintain attributes by scenario. The scenario for Enterprise Buyer is called BBP. For a list of the user attributes for the scenario BBP, see Attributes for the EBP Scenario in the documentation.

? The user attributes are integrated into the organizational plan. ? You can define attributes either for a particular user (that is, per position) or for an organizational unit: ? System administrators can define the most important user attributes at organizational unit level using the

Customizing activities Create Organizational Plan and Change Organizational Plan. The purchasing organization and purchasing group are also defined using attributes.

? Managers can change the attributes defined for their organizational unit(s) or for users in their organizational unit(s) using the Web application Changing Attributes.

? Users can change their own attributes, provided they are authorized, using the Web application Changing Attributes.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

IDES ROOT

Organization DEUser ...

Organization UKUser ...

Purchasing Group 001

Purchasing Group 002

Central Purchasing Department

VENDORS ROOT

BBP_Vend01

ACSSYS

BUKWRK

WGR

KNT

ACSSYS

Attribute Inheritance

? An attribute is inherited by all organizational units below the organizational unit where it was defined. ? Attributes can be defined at any level of the organizational structure. In order to avoid redundant work,

maintain attributes at highest possible level. ? Attributes can be defined as visible or changeable for every user in customizing ? If there are several values for one attribute, you can select one as a default. ? Values for attributes can be excluded.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Attribute Description

Maintain Attributes

Attributes

Scenarios

<sm30>T77OMATTR

Table information

Description in PPOMA

Type of Inheritance

Visibility in PPOMA

Local values overwrite inherited

Normal inheritance (additiv)

No inheritance

Invisible

CAT Catalog ID

ACS System Alias

Table

BBP_ATTR_F1CRM_ORGMAN_ACTBBP_ATTR_F1

Local values cannotbe redefined

Attributes/Scenario

Object Types

Table T77OMATTR

? To configure attributes used in the organizational plan, go to transaction SM30, and table T77OMATTR. Choose the correct Scenarios (BBP) and maintain the type of inheritance, the visibility in PPOMA_BBP, the description in PPOMA_BBP, and check the table and search function module information in the table column.

? Caution: you should not change any delivered settings without reason, for example, an SAP Note. However, you can maintain your own attributes in this table and change the inheritance logic for common attributes, depending on your company’s requirements.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

How To Find The Purchasing Data

50000003

IDES Root

50000002

US2US1

Org DE

50000004Central PurchOrg US

Dept DE1 Dept DE2 Purch Grp DE50000005 5000... 50000008

Dept US1 Dept US2 Purch Grp US500000095000... 50000012

Organizational Resp.:50000002 Organizational Resp.:50000003

Organizational Resp.:50000001

Product Resp.:Electronics Product Resp.:Electronics

Product Resp.:Office supply

Responsible Purchasing GroupOrdered Product CategoryUser

US1 Electronics Purch Grp DEUS1 Office Supply Central Purch US2 Electronics Purch Grp USUS2 Office Supply Central Purch

50000001

? Example: User US1 orders a material from product category ‘Office supply’ via shopping cart: ? 1) System will check which purchasing organizations can potentially procure for the department of user

US1 (Organizational Responsibility): ? Purch GRP DE (responsible for the Org DE (50000002) and all departments below) ? Central Purch (responsible for the IDES root (50000001) and all departments below)

? 2) System will look for which product category(s) the potential purchasing organization is responsible (Product Responsibility) ? Only the ‘Central Purch’ is responsible for ‘Office supplies’. This is the purchasing group that will be

selected. ? If system finds several purchasing groups that are responsible for the same department and the same

product category it will take the first in the table.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Function

Purchasing Organization and Purchasing Group

? Product CategoryResponsibility (optional)

? Organizational Responsibility (mandatory)

? Must be linked to organizations in the PD-Org on Function tab

? Purchasing Organization

? Purchasing Group

The attributes for the purchasing organization and purchasing group are not treated like other attributes

The responsibilities can only be maintainedfor purchasing groupsResponsibility

? Each purchasing organization and purchasing group in a company is defined as a procurement organizational unit.

? If the purchasing organization is local, users (the professional purchasers) will be assigned to the purchasing organizational units. Where the purchasing organization is in R/3 back end, these organizational units are used simply for passing the necessary values from R/3. In this case, no users are linked to the organizational units.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Consistency Check for Organizational Plan

Check Attributes with the ReportBBP_CHECK_CONSISTENCY Check Attributes in PPOMA

CHECK

? The report BBP_CHECK_CONSISTENCY (that can also be called up via transaction BBP_ATTR_CHECK) checks the consistency of the organizational plan. It also checks whether the attributes for companies, purchasing organizations, purchasing groups, and users are defined correctly for the individual applications.

? If the Consistency field is selected, the system checks the consistency of the obligatory attributes of organizational units that are defined as company, purchasing organization, or purchasing group. In addition, the system checks the consistency of the users in these and subordinate organizational units.

? If the User Attributes for Application field is selected, the report checks whether the user attributes for the selected application are defined correctly. The report checks whether the user can execute the relevant application with the existing attribute settings. You can correct the displayed fields in the organizational plan. Red error messages have to be corrected, and yellow error messages are just warnings.

? You have the same logic of checking the organizational units and users in the PPOMA under the Check tab; the only difference is that this checking up is only for the Organizational Unit or User you just marked in the organizational plan.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Who Defines The User Attributes?

Define the most important user attributes at organizational level

Change the attributes defined for their organizational unit(s) or for users in their organizational unit(s)

Display their own attributes, provided they are authorized

IMG Maintain Attribute Access Rights by Role

Employees

Managers

SystemAdministrators

? Attributes can be defined either for a particular user (that is, per position) or for an organizational unit. ? System administrators can define the most important user attributes at organizational level using the

Customizing activities, Create Organizational Plan, and Change Organizational Plan. ? Managers and users can make their changes using the Web application Changing Attributes. ? Nevertheless, in the Implementation Guide (IMG), you can maintain Attribute Access Rights by Role to

change the authorization to change or view attributes. If employees are only authorized to view the attributes they can still set defaults for multiple values.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organizational Plan Maintenance

? SAP Business Workflow can determine which agents are responsible for approving documents and user master records

? The self -service transaction for creating user master records can be used

? The purchasing organizations and purchasing groups responsible for shopping baskets can be determined

? The users are able to maintain their attributes, which are integrated in the organizational structure

The system administrator must create the organizational plan so that:

Administrator can assign attributes to user roles and define access rights

?The system administrator can (from Customizing menu): ? Create and/or change organizational units; maintain addresses of organizational units ? Define purchasing organizations and purchasing groups.

All purchasing organizations and groups must exist as organizational units in the organizational model ? Maintain attributes of organizational units and positions ? Maintain attribute access rights by role:

Depending on user’s role (activity group), a different set of attributes is required. A set of attributes is predefined for each of standard roles supplied with SAP BBP

Specification of access rights for attributes by user roles Definition of mandatory attributes for user roles Different attribute inheritance types: Normal or additive inheritance, Local values overwrite

inherited values, Redefinition of inherited values not allowed, No inheritance ?A user can (from EBP menu): ? Maintain his own attributes at position level depending on user role (activity group)

?Set default values for attributes.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP-User Creation and Maintenance

Single User creation:

? Self-service creation (with approval)

? Administrator creation

Generic user creation:

? via transaction (users_gen)

? Self-service

? Administrator

? Manager

SU01-User

Business Partner

Position

Central Person (technicalobject)

several relations between those objects

? System-independent attributes

? R/3 Backend specific attributes

What is an EBP User?

++++

How do you create an EBP User?

How can an EBP User be maintained?

? The SU01-user is the user in the standard R/3, which can be created and maintained using transaction SU01. This user cannot work in the live EBP system because much of the important information on the user is stored as attributes in the organizational model. For this reason, the user must be integrated in the organizational model. This is carried out using a structure comprising several objects (position, central person, business partner, and SU01 user). This is called the EBP-User.

? You can create user in two ways. For single user creation, you can choose the Self-Service where user can apply for a user-ID themselves or the Administrator creates them individually through the Web.

? The other way is the generic user creation via transaction users_gen, where you can choose whether creating user via RFC or by uploading a file.

? The precise functionality of the users_gen is explained later in the course. ? Whatever way the user has been created, the attributes assigned to them can be seen in the browser under

Settings. The attributes are listed in system-independent and system-specific attributes.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP-User Creation Toolset

generate multiple users

? Create users with sequential number

50000612EBP001 – employee – init EBP002 – employee – init EBP003 – employee – init

? D030456;Smith;50000105;[email protected];de

? C00213445;Meyer;50000106;[email protected];us

<UserId(Char12)>;<Lastname(Char40)>;<OrgUnitID(Char8)>;<email(Char241)>;<CountryCode(Char3)>

? Upload Users from file

? Create users from existing SU01 Users

? Import users from Other System via RFCRFC

<USERS_GEN>

? Import Users from an LDAP DirectoryLDAPServer

EBP

EBP

EBP LDAP

R/3

? Previously, you could either import user data as an ASCII file, create new user data generically or create multiple users by means of a Remote Function Call (RFC). As of Release 3.5, it is now also possible to import multiple Enterprise Buyer users from an LDAP Server.

? LDAP (Lightweight Directory Access Protocol) is a software protocol for enabling anyone to locate organizations, individuals, and other resources such as files and devices in a network, whether on the public Internet or on a corporate intranet. LDAP is a lightweight (smaller amount of code) version of Directory Access Protocol (DAP), which is part of X.500, a standard for directory services in a network. LDAP is lighter because in its initial version it did not include security features.

? The initial password is necessary in cases where the users to be read do not have an e-mail address maintained in their data. Users that do have an e-mail address receive their system-generated, unique, initial password by e-mail.

? Subsequently, system administrators must specify the RFC destination. The system administrators select the users they want to read from a list of existing users in the SAP System (RFC destination). The method for importing user data from a file has been enhanced as follows: You can now browse for a file using the input help.

? Additional fields are available to specify which user data exists in the file. For example, these new fields include: ? First name, Building code, Academic title

? If an error occurs during generation, a message is output containing precise details.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Distribution of Users between Systems

Download

ALE

Upload

Import via Extract via program

<USERS_GEN>

EBP

EBP

EBP

EBP

HR

Non SAP<USERS_GEN>

? Building EBP-Users from an HR-System: The EBP users are built by distributing the positions and employees from the HR System. This is only possible if the organizational units have also been created by distributing them from the HR system using ALE.

? Building EBP-Users from an EBP-System: If you have an existing EBP system with the complete user data, you can download or upload the data to a different EBP system. This is carried out in two steps.

? Building EBP-Users from Non-SAP-Systems: If you want to create EBP users from a system other than R/3, you must write a program that provides the data accordingly or create a .txt file from an Excel spreadsheet that contains the necessary data.. The file structure is described in the documentation of the transaction USERS_GEN

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

<USERS_GEN>

Check and Repair Cockpit for EBP User

Check

Single User

Multiple User

All User

Result

User cannot be repaired for example User is not integrated in organizational plan

The User is consistent.

A defect exist for example User has no Business Partner.

Repair

Level 1Repair of

non critical user

Level 2Deletion and creationof some of the user`s

objects (f.ex. position)

Level 3Deletion and creationof the user and all of

its objects

1

2 3

? In this transaction, you can check your internal EBP users for consistency and repair them if necessary. You cannot process vendor users with this transaction.

? On the entry screen, you select the number of users you wish to check. Individual users: Here you select the name of one user. There is an input help with a search function available. Multiple users: Here you select multiple users. All users: Here you check all users, including those that are locked and those that are not integrated into the organizational structure. If you check the flag Ignore users that are not integrated into the organizational structure , only those users that are integrated are shown. All users that have been created using transaction SU01 are ignored.

? If a user has status green and there are still problems with the user (for example, when changing the address data), you can use this transaction to repair the user. If a user has status yellow, you can use this transaction to repair the user. If a user has status red, you cannot use this transaction to repair the user.

? Note that the organizational unit where the user is located must also be consistent. You can check this in transaction CRM_OM_BP_INTEGRATE. Only when all three displays are green, the organizational unit is consistent. If you wish to repair the user, you should start with a low repair level. If this does not solve the problem, then you should try the next repair levels.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? The key components of an organizational plan

? Attributes and attribute inheritance

? User Maintenance Tools


Organization: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Organization

Topic: Organizational Set-up


? Create an organizational plan

? Add the mandatory attributes to the root organization

? Define the purchasing organization and groups

In this exercise, you will create the organizational plan for your company.

NOTE: Throughout these exercises, the ## designation refers to your group number.

1-1 Setting up the Organizational Plan

Log on to the EBP COMPONENT from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Add the transactions PPOCA_BBP and PPOMA_BBP to your favorites list.

Right-click on Favorites.

Choose Insert transaction.

Type in PPOCA_BBP as the Transaction code.



Type in PPOMA_BBP as the Transaction code.

1-2 Create the organizational plan

The structure below is only information about how your organizational plan should look.

Please use the additional detailed exercise steps to create this structure in the system.

Root Organization

Line Organization

Line Organization

Organization name

Phoenix Phoenix Enterprise

Support Phoenix Support

PUR Back PUR Back Processes

PGRP010 PUR Group Davis, L.

PGRP011 PUR Group Edwards

PUR Local PUR Local Processes

PGRP Local PUR Local Processes

Phoenix-1 Phoenix One

Start transaction Create Attributes (PPOCA_BBP) and confirm the validity date message with Enter.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-1 Create the Organizational Unit.

Go to BASIC DATA tab page

Enter Phoenix to replace New Org. Unit.

Enter Phoenix Enterprises Inc. to replace New Organizational Unit.

Choose Continue.

Go to ADDRESS tab page.

Enter the following address data:

Lancaster Ave / 1717 as the House No./Street

Atlanta / 30003 as the City / Postal code

US / GA (Georgia) as the Country / Region

661-662-12 as the Telephone no.

661-662-13 as the Fax number

Choose Replace.

Enter [email protected] as the E-mail address

Select Continue.

Select Save.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-2 Create the Phoenix Support Organizational Unit.

Start the transaction Change Attributes (PPOMA_BBP) from your Favorites.

Search for Organization unit Phoenix (if necessary).

Double-click on

Phoenix organizational unit.

Select Create.

Select with double-click

Is line supervisor of Organizational Unit.

Go to BASIC DATA tab page

Enter Support to replace New Org. Unit.

Enter Phoenix Support to replace New Organizational Unit.

Choose Continue.

Go to ADDRESS tab page.

Enter the following address data

Lancaster Ave / 1717 as the House No./Street

Atlanta / 30003 as the City / Postal code

US / GA (Georgia) as the Country / Region



Select Replace.

Enter [email protected] as the E-mail address

Choose Continue.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-3 Copy additional Organizational Units for Phoenix Enterprises root.

Double click on

Phoenix Support Organizational unit.

Choose Copy.

Enter PUR Back as the Object abbr.

Enter PUR Back Processes as the Name.

Choose Continue.

Double-click on

PUR Back Processes Organizational unit.

Select Copy.

Enter PUR Local as the Object abbr.

Enter PUR Local Processes as the Name.

Select Continue.

Double-click on

PUR Local Processes Organizational unit.

Choose Copy.

Enter Phoenix-1 as the Object abbr.

Enter Phoenix One as the Name.

Select Continue

Double-click on

PUR Back Processes Organizational unit.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Copy.

Enter PGRP 010 as the Object abbr.

Enter PUR Group Davis as the Name.

Choose Continue.

Double-click on

PUR Group Davis Organizational unit.

Choose Copy.

Enter PGRP 011 as the Object abbr.

Enter PUR Group Edwards as the Name.

Select Continue.

Double-click on


Choose Copy.

Enter PGRP Local as the Object abbr.

Enter PUR Group Miller as the Name.

Choose Continue.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-4 Assign the organization units ‘PUR Group Davis’ and ‘PUR Group Edwards’ to the organization unit ‘PUR Back Processes’. Assign the organization units ‘PUR Group Miller’ to the organization unit ‘PUR Back Processes’.

Double click on

PUR Back Processes Organizational unit

Choose Assign


Is line supervisor of Organizational Unit

Select Start search

Select PGRP 010.

Select PGRG 011.

Choose Copy.

Double click on

PUR Local Processes Organizational unit.

Choose Assign.



Choose Start search.

Select PGRP Local.

Choose Copy.

Select Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Maintain the mandatory organizational attributes to the root Phoenix Enterprises organizational unit.

1-3-1 Add the attributes to the root Phoenix Enterprise organization unit.

Double-click on

Phoenix Enterprises Inc. organizational unit

Go to FUNCTION tab page.

Set Indicator Company

Enter 3000 as the Company Code.

Choose T90CLNT090 R/3 Back end

Go to ATTRIBUTES tab page.

In the table scroll to

the last column Attribute (the attribute abbreviation).

Drag the Attribute column header after column Description.

Select Table control at right corner of the table

Enter 1 as the Variant.

Select Create.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Enter the following data:

In row Enter the value

ACS (System Alias for Accounting Systems)

T90CLNT090

BSA (Trans. Type: Shop. Cart Follow-Up Doc.)

T90CLNT090\EC

BUK (Company Code) T90CLNT090\3000

BWA (Movement type) T90CLNT090\201

CNT (Cost Center) T90CLNT090\1000

Select Continue and then select Insert in the CNT line to add a second value for the attribute CNT.

CNT (Cost Center) T90CLNT090\4140

CUR (Local Currency) USD

ITS_DEST (Current ITS of User) http <get from your instructor>:1080/scripts/wgate/

KNT (Account assignment category) CC

Select Continue and then choose Insert in the KNT line to add a second value for the attribute KNT.

KNT (Account assignment category) AS

PRI (Default printer) LP01

ROLE (User role) SAP_BBP_STAL_EMPLOYEE

SAP_BBP_STAL_SECRETARY

SAP_BBP_STAL_VENDOR

SYS (System Alias) T90CLNT090

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Go to attribute ROLE: SAP_BBP_STAL_EMPLOYEE.

Set Indicator Default .

Go to attribute KNT: CC.

Set Indicator Default.

Choose Save.

1-3-2 Maintain the Extended Attributes for organization unit Phoenix Enterprise.

Go to EXTENDED ATTRIBUTES tab page.

Set Product Category radio button under the Extended Attribute tab page.

Choose R/3 Back end (T90CLNT090) as the Src. System.

Enter 001 as the Product Category.

Enter 007 as the To Product Category.

Select Continue.

Choose EBP Client 3## (SRM_00_3##) as the Src. System.

Enter Local1 as the Product Category.

Enter Local2 as the To Product Category.

Select Continue.

Set Locations radio button under the Extended Attribute tab page.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose R/3 Back end as the Src. System.

Enter 3200 as the Plant (Plnt).

Select Continue.

Set Radio button Storage Locations under the Extended Attribute tab page.

Choose R/3 Back end as the Src. System.

Choose with F4

0001 (in plant 3200) as the Storage Location.

Select Continue.

Choose Save.

Double-click on

one of the sub-organizational units

under the root organization.

Are the attributes inherited from the root Phoenix?

How do you know?

___________________________________________________________

___________________________________________________________

___________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4 Define the purchasing organizations and purchasing groups within the org. structure. The organizational unit named PUR Back Processes will be the purchasing organization for the back-end processes. The organizational unit named PUR Local Processes will be responsible for local processes

Double-click on

PUR Back Process Organizational unit.


Set Indicator Purch. Organization.

Enter 3000 for the corresponding R/3 Purchase Organization.

Choose T90CLNT090.

Double-click on

PUR Local Process Organizational unit.

Go to FUNCTION tab page

Set Indicator Purch. Organization.

Select Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 Define the purchasing organizations and purchasing groups within the org structure. The organizational unit named PUR Group Davis and PUR Group Edwards will be the purchasing groups for the back-end processes. The organizational unit named PUR Group Miller will be responsible for local processes

Double-click on

PUR Group Davis Organizational unit


Set Indicator Purchasing Group.

Enter 010 as the corresponding R/3 Purchasing Group.

Choose T90CLNT090.

Double-click on

PUR Group Edwards Organizational unit.



Enter 011 as the corresponding R/3 Purchasing Group.

In the T90CLNT090

Double-click on

PUR Group Miller Organizational unit.



Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-1 Use the appropriate attribute to denote that the purchasing groups under PUR Back are responsible for the entire organization and for certain Product Categories assigned to the Back end System

Double-click on


Go to RESPONSIBILITY tab page.

Choose R/3 Back end as the Source Sys. under the Product Responsibility.


Choose R/3 Back end as the Source Sys. under the Product Responsibility.


Choose with F4

<the Organiza tional number of Phoenix Root Organization in form ‘50000XXX‘>

as the Organizational Responsibility.

Double-click on

PUR Group Edwards Organizational unit.


Choose R/3 Back-end as the Source Sys. under the Product Responsibility.


Choose with F4

<the Organizational number of Phoenix Root Organization in form ’50000XXX‘>


Select Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-2 Use the appropriate attribute to denote that the purchasing groups under PUR Local are also responsible for the entire organization and for certain Product Categories assigned to the local EBP System.

Double-click on

PUR Group Miller Organizational unit.


Choose EBP Client 3## as the Source Sys. under the Product Responsibility.

Enter LOCAL1 as the Product Category.

Enter LOCAL2 as the To Product Category.

Choose with F4

<the Organizational number of Phoenix Root Organization in form ’50000XXX‘>


Select Save.

1-5-3 Check at the Root Level if the attributes maintained for Phoenix Enterprise Inc. are correct.

Double-click on

Phoenix Enterprise Inc.

Go to CHECK tab page.

Ensure that the message

Check OK Appears.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-4 Running the business partner check transaction.

In a productive EBP environment, you should run the program CRM_COM_ORGMAN_BUPA_INTEGRATE on a regular basis, in order to carry out automatic periodic matching. You therefore need a variant for the report. These implements the comparison in the background for all business partners linked to the organizational units.

The variant must have the following parameters:

All org units: 'X'

Background: 'X'

Reporting day: System day (default)

In this exercise, you will manually trigger the program.

Start the transaction Customizing – Edit Projects (SPRO) from your Favorites.


SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross Application Basic Settings ? Organizational Management ? Integration Business Partner - Organizational Management ? Create Business Partner Initially

Select Organization Unit(s).

Select Execute.

For red light indicators, select line and choose

Execute.

Make sure every light is

Green before leaving transaction.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Verify that all address status indicators are green.

If they are not, you have to correct the address data for this organization unit. In order to do this, start the transaction Change Attributes (PPOMA_BBP) and select the organization unit.

Please note that you have to use the correct Postal Code and Telephone number length for the specific country.

If you want to copy the address data from a valid organization unit select the unit, and go to the Address tab page. Use control Y to copy the address information. Use this copied information for the other organizational units.

After the correction of the address data, you have to synchronize the organization unit again.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-6 Add a delivery address for Phoenix Enterprise

Log on to CLIENT 3## of the EBP SYSTEM from the BROWSER:

User ID: WEBADMIN

Password: init

Client : 3##

Change your password to learn.

Go to Edit Internal Addresses in the launch pad.

Choose Create under Action.

Set Indicator

Ship-To Address.

Set Indicator

Invoice Recipient Address.

Enter or choose the following address data

English as Language

Atlanta as City

30003 as Postal Code

USA as Country

Georgia (USA) as Region

Lancaster Ave. as Street Name

1718 as House Number

Ship1 as Building Code

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1 as Floor

1 as Room Number

661-621-487 as Telephone

USA as Country for Tel. no.

661-621-457 as Fax

USA as Country for Fax no.

[email protected] as E-mail Address

Send via E-mail as Standard Communication Protocol

Select Save Address.

Choose Display List.

Why could you only add an address for the root organization?

Which address number has the newly created ship-to address?

Log off

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Maintain the Address Number for the ship-to-address you just created for the attribute ADDR_SHIPT (Delivery Address) on the root level of your organizational plan in PPOMA_BBP.

Start PPOMA_BBP

Double-click on

Phoenix Enterprises root Organization.

Go to ATTRIBUTES tab page.

Enter <created address number> as attribute ADDR_SHIPT.

Select Save.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Organization

Topic: Creating Manager Roles


? Create manager users

In this exercise, you will create two users who will be managers in your company. Their names are Mary Manager and David Director.

2-1 Create the manager user for the root Phoenix organization.

Log on to YOUR CLIENT of the EBP SYSTEM from the BROWSER:

User ID: WEBADMIN

Password: learn

Client: 3##

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Manage User Data in the launch pad.

Select Create Users.


DIRECTOR as User ID

MR. as Form of Address

David as First Name

Director as Last Name

USA as Country

BLDG1 as Building Code

1 as Room Number

1 as Postal Delivery Office

654-452-25 as Telephone Number

654-452-22 as Fax Number

[email protected]

as E-Mail Address

init as New Password

init as Repeat New Password

Choose Find Phoenix Enterprise Inc. as Organizational Unit.

SAP_BBP_STAL_

MANAGER

as User Role.

Set Indicator Manager.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Create the manager user for the operations organization Phoenix 1 using the following information:



MANAGER as User ID

Ms. as Form of Address

Mary as First Name

Manager as Last Name

USA as Country


1 as Room Number




[email protected]

as E-Mail Address



Choose Find Phoenix One as Organizational Unit

SAP_BBP_STAL_

MANAGER

as User Role

Set Indicator Manager.

Select Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


To search a User, use the Find User area.

Enter MANAGER as User ID.

Choose Go.

Select Detail.

Control User Data.

Choose Log off at the top of the screen.


User ID: MANAGER

Password: init

Client : 3##

Change the password of Mary Manager to learn.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Go to Settings in the header bar.

Choose Maintain Attributes link.

Select OK for the message coming up.

Where do the attributes come from?

Expand Account assignment category

Area.

Set Standard radio button for Cost center.

Choose Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Organization

Topic: User Creation


? Describe the user maintenance tools within EBP

? Create new users with the generic create transaction

Now that the organizational plan of your company has been established, you can use a generic transaction in the EBP system. You will create other employees in the Phoenix One org unit and one additional Administrator using the transaction USERS_GEN. The user WEBADMIN currently is an SU01 user without any connection to the organizational plan. You will also create an EBP user for him by using the Generate Users transaction.

3-1 Create users with the generic user generation transaction in the EBP component.

3-1-1 Add the transaction USERS_GEN to your favorites list.



Type in USERS_GEN as the transaction code.

Double-click on

USERS_GEN (User Generation).

Before performing the next step, verify that you are out of the organizational plan.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-1-2 Create two new users with the role SAP_BBP_STAL_EMPLOYEE.

Select Create New Users with Sequential Number

radio button.

Choose Execute Action

Maintain D000 as Prefix (Alphabetical)

1 to 2 as Suffix (Numerical)

5 as Total Length (Max. 12 Char.)

Smith as Last Name (Default)

init as Initial Password (Default)

<choose the unit ID of Phoenix One>

as Organizational Unit (ID)

USA as Country

Choose Continue.

Verify that Activity carried out successfully

message appears.


Double-click on

PPOMA_BBP.

Verify that Users D0001 and D0002 were created in the organizational structure.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-1-3 Change the name of user SMITH, view the attributes and add an address.


User ID: D0001

Password: init

Client : 3##

Change password to learn.

Choose Settings in the Header bar.

Go to REQUIRED DATA tab page.

Enter <Name of your choice> as First name.

Go to ADDRESS DATA tab page.

Enter <Address data of your choice>.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-2 Import user data from file

In the following exercise you work with the prepared file user_gen.csv. If you want to create this file yourself, you would have to maintain all necessary address data in Excel sheet and save this file in CSV format.

3-2-1 Download the file user_gen.csv from your SAP Business Workplace.

Click on to start the transaction SAP Business Workplace.

Select SAP Business Workplace in the SAP Easy Access screen.

Expand Shared folders

Display folder SRM210 : SRM210 Files

Display file SRM210 Demo File for USERS_GEN.

Go to Attachments tab page.

Select USERS_GEN_DEMOFILE.

Select Export attachment to download the file.

Choose Desktop as Save in.

Select Save to finish the download.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-2-2 Generate users by uploading the user data from the file user_gen.csv.

Start transaction

USERS_GEN.

Select Upload Users from File radio button.

Select Execute Action

Search Users_gen.csv file under C:/.

Choose Select All to set all indicators for the Details on File Contents.

Choose Continue.

Select OK for Display information.

Verify Activity carried out successfully

message appearing

Go Back (twice).

Double-click on

PPOMA_BBP.

Verify that new Users were created in the organizational structure.

Go Back.

USERS_GEN

The generation of users may take a while (20 users/min).

In the blue bottom line, you can check the actual status.

Users can only be deleted one by one.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-2-3 Reset the password for the employee OUTLAW to ‘INIT’ using the WEBADMIN user.


User ID: WEBADMIN

Password: learn

Client : 3##

Go to Manage User Data in the launch pad.

Enter OUTLAW as User ID.

Choose Go.

Select Change.

Choose Change password.

Enter init as New Password.

init to Repeat new Password.

Select Save.

Choose Log off at the top of the page.

OPTIONAL:

Log on as

OUTLAW.

Verify User data.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-3 Create users from existing SU01 users.

Start transaction

USERS_GEN in EBP System.

Select Create Users from existing SU01 Users

radio button.

Choose Execute Action.

Search for Phoenix Support as Organizational Unit (ID).

Choose US as country.

Select Continue.

Select All users radio button.

Select Continue.

Select WEBADMIN in the list.

Select Copy.

Verify that Activity carried out successfully.

message appears.

Select Back.


Verify that User WEBADMIN was created in the organizational structure.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-4 Import users from other systems via RFC.

Start transaction

USERS_GEN in EBP System.

Select Import Users from Other System via RFC

radio button.

Choose Execute Action

Enter init as Initial Password.

Select Phoenix Support as Organizational Unit (ID).

Choose USA as Country.

Select Continue

Select T90CLNT090 as RFC destination.

Choose All users.

Select MANAGER-## from the list.

Choose Copy


message appearing.

Select Back.

Double-click on

PPOMA_BBP.

Verify that User MANAGER-## was created in the organizational structure.

Choose Back.

Verify the newly created users in PPOMA_BBP and log on with your user WEBADMIN to check if he will be able to create shopping carts. Therefore simply press shop, to see if the transaction bbppu99 will open.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-5 Run the report to check the consistency of the attributes for the whole organizational structure and its user.

Choose menu path

System ? Services ? Reporting (or start transaction SA38).

Enter BBP_CHECK_CONSISTENCY as the Program.

Choose Execute.

Choose Company.

Enter 50000###

(ID of the Root Organization)

as the UTYPE.

Select Shopping Cart (SC). as the User Attributes for Application.

Choose Execute.

Are there any read traffic lights? If not, all attributes for Organizational units are ok?

3-6 Integration of Business Partner in Organizational Structure

What is the purpose of the transaction Create Business Partner initially you run after setting up the Organizational Structure? _________________________________________________________________

____________________________________________________________ _________________________________________________________________

____________________________________________________________

_________________________________________________________________

____________________________________________________________

_________________________________________________________________

____________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-7 Attributes for the organizational units

For which purposes do you need the attribute ACS?

____________________________________________________________

_________________________________________________________________

____________________________________________________________ _________________________________________________________________

____________________________________________________________ _________________________________________________________________

____________________________________________________________

3-8 Where in the EBP System can you configure the characteristics of Attribute values and their inheritance?

____________________________________________________________ _________________________________________________________________

____________________________________________________________ _________________________________________________________________

____________________________________________________________

_________________________________________________________________

____________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions

Unit: Organization

Topic: User Creation

3-6 Integration of Business Partner in Organizational Structure

What is the purpose of the transaction Create Business Partner initially you run after setting up the Organizational Structure?

To insure that all of the business partners were created correctly you run this transaction. The system checks the organizational structure regarding missing data like addresses for example. If some inconsistencies are discovered, it shows up. It is important to settle those inconsistencies or this can cause problems later on.

3-7 Attributes for the organizational units

For which purposes do you need the attribute ACS?

The attribute ACS contains the Back-end System in which Accounting has to be checked. You need this attribute value for Invoices without PO reference or for local invoices.

3-8 Where in the EBP System can you configure the characteristics of Attribute values and their inheritance?

In the table T77OMATTR, you can define which value type an Attribute in the organizational structure has to be, or whether it is mandatory to maintain this attribute in the PPOMA. Also the rules for inheritance can be changed there.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflow - Content


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? In this unit the team members continue configuring the EBP system by making the necessary workflow settings. They will familiarize themselves with the different standard workflows supplied by SAP as well as the general architecture of shopping cart approval and authorization levels.

Workflow: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? SAP Business Workflow

? Workflow Usage in EBP

? Spending Limit and User Budget

? Completion Workflow

? Approval Options

? Authorization Levels


Workflow: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Enterprise Buyer Workflow Example

In the above example, tasks may be separated by days / weeks:

The SAP Business Workflow links these disparate tasks

User creates a shopping

cart

Manager is notified

Manager approves

the shoppingcart

Purchasing document is created

Work item created

Work item executed

Workflow started via Workflow API

Business Object Repository method

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

What is SAP Business Workflow?

Business Object

Event Workflow started

Generate Task

Workflow completed

EvaluateStarting

Conditions

User Decision Background Task

Check Attributes

? The SAP Business Workflow is a Event-Driven Process Chain that clarifies the questions: Who should do what, in what order, and when.

? In What Order? (The Workflow Definition) The Workflow Definition is a flowchart that controls the business process. This includes controlling the order in which the individual pieces of work are executed, and any temporary data needed along the way. The workflow container is used to hold all temporary data. A workflow definition consists of a triggering event (which starts the workflow) and steps. Steps may be control logic (for example, if amount > $1000 follow Approval required path, or else follow No approval needed path) or actual pieces of work to be done (for example, approve requisition), which are called tasks.

? When? (Events) Events tell the workflow something has happened so that the workflow can react. Events are usually some activities that have just happened in the system, for instance, document saved, master record created, etc.

? Do What? (Tasks) This question refers to each single piece of work that needs to be done that is, tasks. A task might execute a transaction, a report, a function module, run a routine in an external system, update a spreadsheet, or simply act as a reminder to perform a task. The logic required to perform the task is coded using object-oriented techniques, that is, methods of business process.

? Who Should? (Organizational Plan & Roles) To decide who should receive a work item and therefore, execute the task, we use organization plans and roles. Tasks can be assigned to organizational units, positions, and jobs.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflow example: One Step Approval SC

Business Workflow Explorer < SWDM >

shows the main workflow WS10000129, sub workflows and the single task for user decision (TS*)

Business Workflow Builder < BBPPO >

shows the structure inclusive all technical steps in list form and graphics

? There are several transactions for displaying workflows and applying settings such as the Business Workflow Explorer and the Business Workflow Builder.

? These provide an overview of the workflow tasks or show how the workflow is structured in detail. ? It is possible to perform advanced settings or create new workflows using the Business Workflow

Builder.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflow Customizing

Setup of the technical workflow functionalityby performing the Automatic Workflow Customizing

Setup of the workflow business processes by activating specific workflows and assigning agents

1.) Maintain technical standard settings in customizing

2.) Activate event linking and assign agents for the tasks

3.) Maintain start conditions [see next slide]

? In the implementation guide for the SRM Server (SAP EBP), there is a node that contains the workflow customizing. This node consists of an area for technical basic settings and another for business process relevant settings

? In the technical settings, it is important to perform the Automatic Workflow Customizing. This function automatically sets up most parts of the basic workflow customizing. There is also a standard Verification Workflow that confirms the technical settings have been set up properly.

? In the next steps it is necessary to define which workflows should be used. This is done by activating these workflows.

? Since some workflows contain steps requiring user decisions, you have to define who should be allowed to perform these tasks. You can assign a role to these tasks (for example, Manager role) or they can be set as a general task so that theoretically everyone could perform this action.

? For activating workflows and assigning agents to tasks, it is mandatory to read the documentation because the settings can depend on the workflow.

? If there is more than one workflow active for the same business object, it is necessary to define starting conditions in addition to assigning agents to the tasks.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Start Conditions for Workflows

Start conditions have to be modelled independently to make sure only one of the approval workflows for shopping carts is started

Workflow 1:

Without approval

Workflow 2:

One step approval

Workflow 3:

Two step approval

Start condition 1

Start condition 2

Start condition 3

Event Manager

Workflown:n - step approval

Start condition n

...

active activeinactive inactive

Eventlinkage

Shopping Cart,Confirmation, Invoice ,

Purchase Order,Contract

? There are Conditions for Approving Shopping Carts, Confirmations, Invoices, Purchase Orders and Contracts

? In the start conditions in Customizing, you define which workflow is started under what conditions. The conditions always apply for the entire shopping cart, confirmation or invoice. For example, you decide that shopping carts must be approved if the total value exceeds $1000.

? There are at least three different workflows: ? Without approval (standard) ? One-step approval (standard) ? Two-step approval (standard) ? Plus BAdI’s and Administrator Workflows

? These workflows have as a starting event, for example, SC.Created, and additionally, each event linkage has a start condition assigned, which makes it possible to choose one out of many workflows.

? Note: Event linkages can be active and inactive. Inactive means: the workflow is linked to the event, but ignored by the event manager in runtime. In our example, workflow 1 and 3 can by started.

? Note: Start conditions are created independently. This means the user has to take care that the conditions are exclusive. The system adds the old and new values of all changed fields to the event container of the created event. These values can then be read and evaluated in the workflow started by the event to influence the process flow of this workflow.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflows Supplied – Shopping Cart

? WS10000060 (without approval)

? WS10000129 (one step approval)The employee's manager approves the shopping cart.

? WS10000031 (two step approval)The first manager and the second manager approve the shopping cart.

? WS10000276 (value limit)Value limit and approver (one step) can be set per employee.

? WS14000109 (value limit, n-steps)as WS1000276 but multiple steps

? WS14000133 (multi-step approval)Workflow has to be defined via BADI

Approving Shopping Carts (BUS2121)

? With SAP Business Workflow, you can define whether shopping carts are subject to an approval procedure in the EBP system and the criteria that decides which shopping carts are to be approved.

? Shopping carts without approval: ? You can use a workflow that immediately assigns the status Released to shopping carts that contain,

for example, low-value purchases that you want to pass through the EBP system without going through an approval procedure, or shopping carts that were created by managers.

? Shopping carts with single or multi-level approval: ? You can specify a single -level approval procedure for shopping carts with a low procurement values

(in which case, only one superior would need to approve them) and a multi-level approval procedure for procurement transactions with higher procurement values. ? There are Workflows like WS10000129 and WS10000031 that determine the responsible approver via

the manager of the user, while other workflows like WS10000276 or WS14000133 are more flexible in terms of identifying the responsible approver. ? The new Workflow WS14000133 calls a BADI where the amount of steps and the approvers have to

be defined. The BADI is called BBP_WFL_APPROV_BADI and contains an example, implementation.

? Note: Workflows for the Approval of a shopping cart refer to the business object BUS2121. Other workflows could be taken into consideration for this object as well, please read the additional documentation.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

What happens if:

EMPLOYEE creates a shopping cart with value 80?

EMPLOYEE creates a shopping cart with value 3000?

MANAGER1 creates a shopping cartwith value 7000?

Value Limit Approval Process (single-step)

User

EMPLOYEE

MANAGER 1

MANAGER 2

Spending Limit

100

5000

50000

Approval Limit

2000

50000

SLAPPROVER

MANAGER 1

MANAGER 2

WS10000276

? Prerequisites ? You have defined the start conditions for the workflow WS10000276. ? You have defined the relevant manager(s) as spending limit approvers in the organizational plan using

the user attribute SLAPPROVER. ? You have maintained the spending limit and the approval limit (the value up to which a user is

allowed to approve) for the various roles ? Note: This workflow is a one step approval: if the approval limit for MANAGER1 is exceeded the work

item is automatically sent to the spending limit approver of MANAGER1 (= CEO).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

WS10000276 one stepWS14000109 n- step

? Employee - spending limit $500, approval limit $0

Value Limit Approval Workflows

? Manager – spending limit $1000, approval limit $2000

spending limit/output limitapproval limit

< PFCG >

< PPOMA_BBP >

Approver: provided from org. structureAttribute: SLAPPROVER

? As of SAP EBP 4.0, you can use an one-step spending limit workflow WS10000276 or to use the new N-step workflow WS14000109 for spending limit. While WS1000276 only determines one approver (single-step), WS14000109 creates sequential workitems for all approvers who are responsible according the system customizing.

? Both workflows do not evaluate a budget or something similar but only the actual amount of the shopping cart.

? When an employee's spending limit (the value from which a shopping cart requires approval) is exceeded, this workflow starts. The workflow determines one person authorized to approve the shopping cart in case of the single step workflow.

? When using the N-step spending limit workflow, the system determines the first approver. If this approval limit is exceeded, further approvers will be determined until the last approver has been found with an approval limit that is high enough. All between approvers in this process have to approve so it is a sequential N-step workflow.

? The approver is determined on the basis of the value for an attribute SLAPPROVER (spending limit approver), not on the basis of the next manager in the organizational plan.

? The spending (output limits) and the approval limits can be maintained in the organization structure (PPOMA_BBP) in the Extended Attributes tab or via transaction PFCG in the register personalization of each role.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

User Budget-Workflow: Process

User orders shopping cart

System checks shopping budget

SAVE

System updatesshopping budget

Manager‘s Approval

ConfirmCancel

Exceeded

System message: Budget is exceeded

System updatesshopping budget

AutomaticApproval

Not exceeded

Table: BBP_USRBDGT

Only if the user budget is exceeded, the manager has to approve

? The budget workflow is new process in which a budget is defined for a user. The system checks the user‘s budget to determine if a shopping cart requires approval.

? A shopping budget is the cumulative amount that an employee is allowed to order in a specified period (no approval is necessary). The shopping cart requires approval when the user’s budget is exceeded.

? Process Overview: 1.) The employee orders a shopping cart. 2.) The system checks the budget defined for the user (or role or organizational unit the user belongs to). a.) If the budget is exceeded, the user gets a message. The user either confirms the message or cancels the action. - Confirm: Shopping budget is updated and approval required - Cancel: Shopping cart can be changed or cancelled b.) If the budget is not exceeded, there is no approval necessary. The shopping budget is updated.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

1.) Define User Budget, Validity and Currency

2.) Include UserBudget in the start conditions for BUS2121

User Budget Workflow: Customizing

< PFCG > < PPOMA_BBP >or

? Similar to the Spending Limit Workflows, you can define the budget per role via transaction PFCG, per user via transaction SU01 or in the organizational structure via transaction PPOMA_BBP at the extended attributes. The budget has to be defined for amount, currency, and period (validity).

? The budget workflow can be used together with the standard shopping cart workflows for the approval of shopping carts, for example, the workflows no-approval and one-step-approval. To include the budget in the process, it is only necessary to include the budget workflow in the start conditions and to define the budgets.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart Completion Workflow

Employee orders shopping cart

Check start conditions forCompletion WF

System sends workitem to purchaser(s)

System sends workitem to employee

SAVE

CompletionWorkflow is started

Approval Workflow is started

Do not apply Apply

free text item,item without price,item without vendor

? The completion workflow for shopping card allows a check of the shopping cart by the purchaser in advance of a potential approval.

? There are some new shopping card attributes with EBP 4.0 that should be considered in this case: - Free text items - Items without price - Items without vendor If one of these cases happen, all purchasers responsible for the shopping cart will get the completion workflow.

? To ensure that the system detects such ambiguous items, the start conditions have to be maintained. ? After completion (change of the shopping cart by the purchaser), the shopping cart is sent back to the

employee and the system checks to see if an approval by a manager is required.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Gross AmountCreator of Confirmation Workflow started Approver

Workflows Supplied - Confirmation

Start Conditions for the Approval of Confirmation (BUS2203)

Requestor

Non-Requestor

< 1000 USD

> 1000 USD

< 1000 USD

> 1000 USD

WS10400010Auto Approval

WS104000021-step Approval

-

Manager


Requestor

Requestor& Manager


? If the requester can not be found, confirmation is passed for approval toan administrator (WS10400020).

? No approval required in the case the confirmation is created by a user with the role SAP_BBP_STAL_RECIPIENT.

Confirmation Workflow: ? This process occurs when a confirmation is saved. There are three possible cases: ? Vendors confirm that they have provided the goods or services that were ordered; ? Users who created shopping carts confirm that the goods or services ordered have been supplied ? Secretaries or other appointed employees confirm that goods or services ordered by other users have

been supplied. ? The approval workflow for the confirmation can be a 1- or a 2-step approval. The approver of the

confirmation is determined using the following algorithm: If the user that created the confirmation is also the requester of the corresponding shopping cart, then no approval is required unless the gross-amount from the start conditions is exceeded. The Confirmation has to be approved by the manager of the Requestor.

? If the confirmation was created by a vendor or secretary (that is, by anyone other than the requester of the shopping cart), then the approver is the requester unless the gross-amount of the start conditions is exceeded, then the Confirmation has to be approved by both the Requestor and the manager.

? If the corresponding Approver cannot be found, the work item is assigned to a replacement approver. The replacement approver for the confirmation is defined in the agent assignment for task TS10008107.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflows Supplied - Invoice

Start Conditions for the Approval of Invoices (BUS2205)

Requestor

Non-Requestor

Gross AmountCreator of Invoice Workflow started Approver

< 1000 USD

> 1000 USD

< 1000 USD

> 1000 USD

WS10400016Auto Approval


-

Manager


Requestor

Requestor& Manager


? If the requester can not be found, invoice is passed for approval to an administrator (WS10400021).

? No approval required in the case of Evaluated Receipt Settlement or if the invoice is created by the role SAP_BBP_STAL_ACCOUNTANT

Invoice Workflow: ? This process occurs when a vendor, an employee or accountant creates an invoice with the status Saved.

The approval workflow for the invoice can be a 1- or a 2-step approval. The approver is determined in the following way: ? If the invoice is created by the vendor, it is approved by the user who created the shopping cart. If this

user cannot be determined, the invoice is passed for approval to the responsible administrator. The administrator must be entered as a possible processor for the standard task TS1008118. If the gross amount exceeds the limit in the start conditions the invoice is passed for approval to the Requestor and the manager. ? If the employee created the invoice, the employee’s manager approves the invoice if the gross amount

of the start conditions is exceeded. ? If the accountant creates the invoice, no approval is required.

? The approver can change the account assignment. If an invoice is created without account assignment, the approver is required to add it. When the employee approves the invoice, the invoice information will be transferred to the back end. If one of the invoices created by the employee is rejected, this employee receives a work item. If employees reject the invoice themselves, the back-end system does not get the information. The vendor is notified of the relevant information via e-mail.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Maintaining Table Entries for Stochastic Check in Customizing:

Stochastic Check for Confirmation and Invoice

Which object requires stochastic check?

The character-istic value is the sub-type of the document.

The Business Object Repository event

* The system always takes the next smallest threshold value compared to the gross value of the document

Standard WF that is replaced by the stochastic workflow.

Threshold value* for which the stochastic workflow should begin

Specifies the frequency in percent with which the object type can be stochastically checked.

? This entry is mandatory

? Ex: BUS2203 for CF or BUS2205 for Invoice

? This entry is optional

? Ex: For CF: Return Delivery

? It is always the Event SAVED, this entry is optional

? This entry is mandatory

?Workflows triggered stochastically replace this normal workflow.

? Working with the stochastic check is another possibility for controlling confirmations and invoices. In this case not all documents are covered in an equal manner.

? When you set the stochastic check, you define the frequency of confirmations and invoices approval. This means you could set up a standard approval (for example, no approval) and a special approval (for example, one-step approval) on a regular basis, depending on the object, process, value, and frequency.

? As soon as you define the stochastic check for CF and IV, the appropriate Start Conditions are replaced by workflow templates that are triggered stochastically

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflows for Purchase Order and Contract

?The Workflows for Purchase Orders and Contracts can be used for thecreation of new documents and changes to existing documents

?Purchase Order (BUS2201)?WS140000075 Workflow without Approval?WS140000089 One-Step Approval ?WS140000145 Approvaln-step for PO (BADI)

?Contract (BUS200011)?WS14000086 Workflow without Approval?WS14000088 One-Step Approval

? As of EBP 4.0, purchase orders and contracts are finalized technically by workflows. You must customize the workflows for these objects.

? If you use more than one workflow per business object, you must set up the starting conditions for the workflows.

? Contracts running out of target value, target quantity, or time, can be signaled with the Contract Alert Workflow WS1040022. This workflow will trigger an alert via SAP BW or the report BBP_CONTRACT_CHECK.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflows Supplied - User Creation

? Approving Internal User Master Records (BUS4101)

? Approval of internal user master records (WS10000192)The superior of the employee requesting the user master record approves the request.

? Approving External User Master Record (BUS22101)

? Approval of external user master records (WS10000209)Approval of external business partner registration (vendor, bidder) and their contact persons.The approver must be entered as a possible agent in the agent assignment of the standard task TS10008109.

Approval Workflows for Creating Internal Users : ? When an employee requests a user master record and you have configured Customizing in such a way

that the user needs to be approved, the user’s manager receives a work item. If the superior approves the request for a user, it is released. The employee receives an e-mail containing an automatically generated password at the address that he or she entered when making the request. If the manager rejects the request for a user, the employee is also notified via e-mail.

Approval Workflows for Creating External Users: ? In the EBP system, registered employees of external business partners, for example vendors and bidders,

can submit additional employees from their company to be registered as contact persons in the EBP system. If the external business partner and employee have not yet been registered, external employees can register the company as a vendor, bidder, or portal bidder and register themselves as the contact person of that company. When the registration application is saved, the approver responsible (a professional purchaser or system administrator) receives a work item in the EBP system. Using the work item, approvers reach the application Managing External Business Partners, where they can adopt and complete the relevant data from the registration application. Approvers must inform the applicant of the approval or rejection of their registration application and of the relevant logon data for the EBP system. This can be done via e-mail using the application Managing External Business Partners, if necessary. Prerequisites: You must have defined the responsible processor. To do this, enter the processor as a possible agent in the agent assignment of the standard task TS10008109.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflows Supplied - Password & Procurement Card

? For Approving a Password

? Without approval (WS10000224)The password is generated and sent to the applicant directly via e-mail

? With approval (WS10000223)The password is generated and sent as a work item to the administrator who has to approve it. After the approval procedure an e-mail is sent to the requester. This contains either the password or information regarding the rejection of the application.

? For Approving Procurement Card Settlements (BBP_PCARD)

? First approval (WS10000093)

? Second approval (WS10000100)

For Requesting a new Password: ? If a user of the EBP system has forgotten his or her password, it is possible to make a request for a new password.

The system generates the password, which is sent via one of the following workflows to the applicant: ? WS10000224 - The password is generated and sent to the applicant directly via e-mail. ? WS10000223 - The password is generated and sent as a work item to the administrator who has to approve it.

After the approval procedure, an e-mail is sent to the requester. This e-mail contains either the password or information regarding the rejection of the application.

Procurement Card Process Flow: ? In the EBP system, you can specify procurement card as the payment method when purchasing items provided you

are using the Materials Management functions in the EBP system. In addition, you can manage settlements for purchases made using a procurement card, that is, you can transfer the settlement file that the bank or card company sends you to the EBP system to check that the contents are correct and to specify account assignments. You specify procurement card as the payment method when creating a shopping cart.

? The settlement data is transferred to the EBP system. At the same time, the system generates an invoice for all purchases that were made using a procurement card. The invoice is updated in accounts payable accounting in the back-end system and blocked for payment. The system can then pay the invoice during the payment run.

? If the value of purchases made using the procurement card exceeds the value specified in Customizing, the system places a work item in the cardholder’s EBP inbox when updating the invoice. The cardholder checks the purchases made and can change the account assignment if necessary.

? If you want the manager to monitor expenditure as well, he or she receives a work item in his or her inbox. When the manager has given his or her approval, the system posts the invoice to a G/L account in Accounting.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SC Instancein Buffer

Evaluate StartConditions

Modify WF in Buffer

no event SAVED

Example: Architecture for Shopping Cart Approval

One main Function Module:BBP_PDH_WFL_DB_UPDATE

evaluates start conditions starts workflow

Approval Preview

Add / Change ApproverSC Create

Order

Function Module:BBP_PD_SC_SAVE

Serialize SC

EBP

? There is a new workflow API as of Enterprise Buyer professional Release 3.0. There is only one main function module BBP_PDH_WFL_DB_UPDATE for evaluating the start conditions and eventually starting the workflow.

? The function module BBP_PDH_WFL_CHECK_DOC_CHANGE checks whether a shopping cart can be changed by the current user during the approval depending on his or her authorization level.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Ad-hoc functionality

or

General Task

EBP WorkflowCustomizing

List depending on Agents Assignment

Add Reviewer

Ad-hoc change of approver by requester

Add Approver

Replace

? In the approval preview, employees can specify a different approver for a shopping cart or an other document at runtime. This might be necessary, for example, if a manager is temporarily absent and has not specified a substitute for shopping cart approval.

? Similarly, managers responsible for approval of a shopping cart can specify all subsequent approvers for the shopping cart at runtime when executing an approval work item.

? You have to specify the approvers to be displayed and the group of users that can change these approvers in the organizational plan.

? If the Agent assignment is general task, every EBP user can be found under the approver entry in EBP. If the agent assignment is restricted to users with the role SAP_BBP_STAL_MANAGER, only users with the specific role can be assigned.

? The Approval Preview Screen can be called from shopping cart, confirmation, invoice, purchase order, contract, and bid.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Reviewer Concept

?observe approval process for shopping cart

?Reviewer work item doesn’t disappear until the approvalworkflow is completed.

Adding a Reviewer

Approver

David Director

Approver

Mary Manager

Reviewer

Betty Buyer

? Reviewer Authorities

?Display shopping cart items

?No authority to approve or reject shopping carts

? Reviewer Function Concept: Providing the functionality to observe an approval process for a shopping cart. A reviewer observes the whole approval process (many approvers). The Reviewer work item does not disappear until the approval workflow is complete. The Reviewer does not have the authority to approve or reject shopping carts.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Online vs. Offline Approval

Send report for eMailsReply

Receive report for Workitems

COM Addin

Change/ Approve/ Reject

Online synchronization

Link to EBPApprove/

Reject

E-mail based Standard Solution:

E-mail based solution: COM Addin with Outlook 2000:

Mobile Solution Approve/ Reject

SAP MAPI Solution

Online Solution

Approve/ Reject

EBP

FormsLibrary

ONLINE

OFFLINE

? Users in EBP with approval authorization do not necessarily have to process approval work items via the EBP Web Inbox or the EBP system Business Workplace. Processing possibilities are available that do not require log on (offline mode), where the user processes the work items in an e-mail in his usual mail client. E-Mail-based standard solution This is a true offline solution. The work items with status ready are selected by a send report that is manually triggered or via background processing. These work items are then sent to the appropriate mail clients in HTML mail format. The user is not obliged to log on to the EBP system. Only the reply e-mails that might still be stored locally in the e-mail program after approval/rejection need to be sent (automatically) after data synchronization. The Standard Solution for any mail clients provides the default layout without any additional installations on the client side

? E-Mail-based solution: COM Addin with Outlook 2000 This offline solution is based on a Visual Basic program enhancement for Microsoft Outlook 2000. Prerequisite is Microsoft’s Outlook e-mail program, version 2000. After minor installation effort on client-side, the work item e-mails display in a fashion similar to EBP (variable) mail format. Furthermore, buttons are provided for easy approval/rejection directly from the work item e-mail.

? Mobile Engine Solution: The mobile engine provides a platform-independent framework for offline scenarios in Enterprise Buyer. Mobile devices such as palmtop computers, Personal Digital Assistants (PDAs), and laptops use the Mobile Engine to run business applications offline.

? The SAP MAPI Service Provider allows access to the R/3 mail server Business Workplace and to the SAP Business Workflow from the MAPI-compatible mail clients. Users can therefore use the SAP

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


MAPI working environment to edit and send Workplace documents and to execute work items. Examples of MAPI-compatible mail clients: Microsoft Outlook for Windows TM, etc.

? Note: Before deciding which scenario you want to implement, read note 627397 as there will be changes in the future concerning the Microsoft Outlook and Lotus Notes Integration.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Workflow action:? continue? restart (new approval)? delete? no action

Authorizationlevel

Changingtotal value

Change Shopping Cart During Approval

? change cart during approval

? approve cart

? partially reject cart

? reject cart

Manager

? change cart

? delete cart

Employee

? As of Enterprise Buyer Release 3.0, you can define whether or not a shopping cart can be changed during the approval process, depending on the role settings. You can influence the effect on the approval workflow by defining authorization levels.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

4 (high) Shopping cart changed ? The approval continues

3 (medium) Shopping cart changed ? The approval starts from the beginning, if new workflow found in starting conditions

2 (low) Shopping cart changed ? The approval starts from the beginning

1 (no) Shopping cart could not be changed

Authorization Levels and Workflow Actions

BBP_WFL_SECURITY

<pfcg>

Authorization level Workflow action

? If several roles are assigned to the approver, the system determines the highest available authorization level during runtime.

? With the Business Add-In (BADI) BBP_WFL_SECURE_BADI, you can define ? Whether a shopping cart can be changed during approval

? How approval workflow behaves when the document is changed

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Enterprise Buyer

Customizing Steps

? Maintain prefix numbers

? Maintain Standard Settings for SAP Business Workflow

? Set active Plan Version

? Activate Standard Tasks

? Perform Task-SpecificCustomizing

? Define Conditions for StartingWorkflows

<spro>

? In the mentioned steps, all the settings for the SAP Business Workflow are made. ? These activities should be carried out in the stated order. ? Maintain prefix numbers ? Workflow objects have to be identified by an eight-digit number that consists of the maintained three-

digit prefix number followed by a five-digit internal number. ? Maintain Standard Settings for SAP Business Workflow ? SAP Business Workflow standard settings are maintained by using auto-Customizing. Checks for

completeness are performed. ? Set Active Plan Version ? Only one of the plan versions created in the system is active at a given time. All supplied SAP

workflows are then automatically in the plan version marked as active. ? Activate Standard Tasks

A background report is started to define certain tasks within the workflows of Enterprise Buyer as standard tasks.

? Perform Task-Specific Customizing ? In this activity, you activate event linkages and assign processors for certain tasks.

? Define Conditions for Starting Workflows ? In this step, you define which workflow is started under which conditions.

? Note : The following activities can be carried out at any time: ? Task-specific Customizing ? Start conditions for Workflows

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004


Workflow: Unit Summary

? SAP Business Workflow

? Workflow Usage in EBP

? Spending Limit and User Budget

? Completion Workflow

? Approval Options

? Authorization Levels

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Workflow

Topic: Initializing Workflow


? Verify and complete the necessary workflow settings

? Activate the main standard workflows used in EBP

In this exercise, you will continue configuring the EBP system by making the necessary workflow settings.

1-1 Certain workflow settings need to be made in the system for technical and operational reasons. Verify and complete the necessary settings.

Log on to YOUR CLIENT of the EBP SYSTEM

Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Verify the workflow prefix numbers are maintained for your EBP client.

Start the transaction Edit Project (SPRO) from your Favorites.


? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? SAP Business Workflow ? Maintain Prefix Numbers

What is the unique prefix number assigned to your client?

Choose Back.

1-1-2 Verify that workflow is customized and is operating correctly. The Verification Workflow confirms this.

… ? Cross-Application Basic Settings ? SAP Business Workflow ? Maintain Standard Settings for SAP Business Workflow

Expand Maintain Runtime Environment

root

Select Maintain Workflow System Administrator.

Select Execute.

Choose User.

Enter EBPADMIN as the System administrator for workflow.

Choose Save.

Select Back.

Select RFC Destination Info.

Which user is the background user for logical RFC destinations?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Start Verification Workflow.

Select Continue.

Choose SAP Business Workplace.

Double-click on

(in column class) to execute the first step in the Workflow.

Choose Execute background step immediately.

Select Update.

Verify that you received two messages.


1-1-3 Verify that the active plan version was set in your system.

…? Cross-Application Basic Settings ? SAP Business Workflow ? Set Active Plan Version

Verify that PLOGI is the Active Plan Version.

Select Back.

1-1-4 Activate the standard tasks.

…? Cross-Application Basic Settings ? SAP Business Workflow ? Activate Standard Tasks

What was the result of executing this transaction?

___________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-5 You will verify that the Event Linkage is activated for the workflow: WS 10000192 (Approve new user workflow, EBP 2.0A)

… ? Cross-Application Basic Settings ? SAP Business Workflow ? Perform Task-Specific Customizing

SAP ? SRM ? SRM-EBP ? SRM-EBP-WFL

Choose Activate event linking.

Scroll down to WS entries.

Expand WS 10000192 Workflow tree.

Activate the Workflow if it is deactivated. For this:

Double-click on

Deactivated to activate the Workflow.

What is the business object?

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-6 View the agent assignment of the workflows

… ? Cross-Application Basic Settings ? SAP Business Workflow ? Perform Task-Specific Customizing

SAP ? SRM ? SRM-EBP ? SRM-EBP-WFL

Choose Assign Agents

Select TS 10008118 (Approve or Reject Invoice)

Line.

Choose Attributes … in the application tool bar.

Set General forwarding allowed radio button.

Select Transfer.

Select TS 10008118 line again.

Choose Create agent assignment …

in the application tool bar.

Double-click on

Role. for the assignment.

Enter *MANAGER as the Search Term.

Choose Continue.

Double-click on

SAP_BBP_STAL (EBP Manager)

EBP Manager in Standalone Mode.

Select TS 10008118 line again.

Choose Refresh index in the application tool bar.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-7 Define Conditions for Shopping Cart Approval

…? Cross-Application Basic Settings ? SAP Business Workflow ? Define Conditions for Starting Workflows

Define the conditions that will start the no-approva l, one-step, and two-step approval workflows.

Find the business object BUS2121:

Select Change start conditions.

Select Find object type … for choosing the right Business Object.

Select BUS2121 (EC Requirement Coverage Request)

as the Object Type.

How many start conditions are associated with the business object

BUS2121?

For all start conditions, choose American Dollar as currency:

Select Change Default Currency for Start Condition.

Choose American Dollar from the dropdown list

Change start conditions for Workflow WS10000031 (Two Step Approval of Shopping Cart)

Select white square box for Workflow 10000031.

Double-click on

100.000 in column Express. 2 for the role SAP_BBP_ STAL_MANANGER.

Enter 10.000 in Constant field.

Select Transfer condition.

Change start conditions for Workflow WS10000060 (Workflow Without

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Approval)

Select white square box for Workflow WS10000060

Double-click on

1000 in column Express. 2 for the Employee.

Enter 500 in Constant field.

Double-click on




Change start conditions for Workflow WS10000129 (One Step Approval for Shopping Cart)

Select white square box for Workflow WS10000129

Double-click on

100.000 in column Express. 2 for the Employee.


Double-click on

1000 in column Express. 2 for the Employee


Double-click on




Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Find object type … for choosing the right Business Object.

Select BUS2203 (EC Confirmation

Goods/Services)

as the Object Type.

How many start conditions are associated with the business object

BUS2203?

For all start conditions, choose American Dollar as currency:


Choose American Dollar from the dropdown list

Select Find object type … for choosing another Business Object.

Select BUS2205 (EC Incoming Invoice)

as the Object Type.

How many start conditions are associated with the business object BUS2205?

For all active start conditions, choose American Dollar as currency:


Choose American Dollar from the dropdown list.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


How many levels of approval are required if the shopping cart has a total value of 799 USD?

____________________________________________________________

How many levels of approval are required if the shopping cart has a total value of 100,299 USD?

____________________________________________________________

How many levels of approval are required if the shopping cart has a total value of 10 USD?

____________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-8 Define Authorization level of the Manager and Employee Roles for Shopping Cart Approval

…? Cross-Application Basic Settings ? Roles ? Define Roles

Enter SAP_BBP_STAL_MANAGER as the Role.

Select Change Role.

Go to Personalization tab page.

Select Specifies the authorization level of the user in the approval (BBP_WFL_SECURITY).

Choose Change values.

Choose Medium from dropdown-list.

Select Transfer Data.

Choose Save.

Select Other role.

Select SAP_BBP_STAL_EMPLOYEE as the Role.

Choose Copy.

Select Specifies the authorization level of the user in the approval (BBP_WFL_SECURITY).

Choose Change values.

Choose Low from dropdown list.

Select Transfer Data.

Choose Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Create an employee using the self-service User Create transaction.

1-2-1 In order for users being created with the self-service transaction to require approval, an indicator needs to be set in the EBP system.

Turn on the indicator for the self-service transaction.

(If necessary, start the transaction Customizing - Edit Project (SPRO) from your Favorites and choose Goto ? SAP Reference IMG)

SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Master Data ? Create Users ? Set Approval Indicator

Set the indicator and save the changes.

Log off from the EBP System.

1-2-2 From the web, create the user EMPLOYEE in the Phoenix One organization.


Client : 3##

Choose Log on.

Select Create user ID.

Maintain the following data:

EMPLOYEE as the User ID

Edward as the First name

Employee as the Last name

edward.employee@phoenix-ep. com

as the E-mail address

Enter * as the Approver.

Select Find

Select Mary Manager as the Approver.

Go to Address data tab page.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Mr. as the Title.

BLDG1 as the Building

R12 as the Room number

<enter a number> as the Telephone number

<enter a number> as the Extension

<enter a number> as the Fax number

<enter a number> as the Extension

Select Save.

Choose Return to log on screen and then close and restart the browser.

1-3 Log on as Manager and approve the new user.


User ID: MANAGER

Password: learn

Client : 3##

Go to Approval in the Launch pad.

Select the work item

Approve new user EMPLOYEE.

Select SAP_BBP_STAL_EMPLOYEE as the Role.

Choose Continue to approve the new user.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Log off.

1-4 When the manager approves the new user, e-mail is sent to the user telling them the initial password. Since no valid e-mail address exists for the new user, you must reset the password for log on.

Reset the password for EMPLOYEE to init using the WEBADMIN user.


User ID: WEBADMIN

Password: learn

Client : 3##

Go to Manage User Data in the launch pad.

Enter EMPLOYEE as the User ID for the search.

Select Go.

Choose Change.

Choose Change password

Enter init for New Password (twice).

Choose Save.

Choose Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 View the attributes for the user EMPLOYEE.


User ID: EMPLOYEE

Password: init

Client : 3##

Change password to learn.

Go to Settings in the header bar.

Choose Maintain Attributes link.

Select OK for the message coming up.

Expand Account assignment category area.

Set Standard radio button for Cost center.

Choose Save.


If your attributes do not show up, please inform the instructor.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 OPTIONAL: Verify the Workflow customizing you maintained for shopping carts.

1-5-1 Log on as EMPLOYEE and create three shopping carts.


User ID: EMPLOYEE

Password: learn

Client : 3##

Use free text entry (select Describe Requirement) and select a Local product category.

Shopping cart 1: Choose price value 10 USD and order the shopping cart.

Shopping cart 2: Choose price value 799 USD When you complete the shopping cart, choose Approval Preview and add David Director as a reviewer to your shopping cart. Then order the shopping cart.

Shopping cart 3: Choose price value 100.299 USD and order the shopping cart. Who needs to approve which shopping cart? (To get this information, check the status of your shopping carts and expand the Approval area in the details of the shopping cart.)

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

Log off.

1-5-2 Log on to YOUR CLIENT of the EBP SYSTEM from the BROWSER as David Director (Password: init, change to learn):

Perform a review for the shopping cart with the value of 799 USD.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-3 Log on to YOUR CLIENT of the EBP SYSTEM from the BROWSER as Mary Manager.

Approve the two shopping carts from Edward Employee with the value of 799 USD and of 100.299 USD.

Log off.

1-6 What is the purpose of the prefix numbers you verified earlier?

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-7 Workflow Customizing

You activated the relevant workflow structures in the EBP customizing and assigned the agents for the tasks. In this activity you make all the necessary settings to adapt the standard tasks and workflow templates supplied by SAP.

What does it mean if a task is classified as General?

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-8 Define Conditions for starting Workflows in EBP

In this step, you define which workflow is started under what conditions. What are the standard start conditions and how could you add another logic to that concept, if Phoenix Enterprises should decide that not every user in the system has the same spending limit and that not every manager has the same approval limit?

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions

Unit: Workflow

Topic: Initializing Workflow

1-6 What is the purpose of the prefix numbers you verified earlier?

Standard object numbers must be clearly defined in all systems, so that objects are not overwritten during transports. In the case of standard tasks, workflow tasks, workflow templates, task groups and roles, this eight-digit number consists of a three-digit prefix number followed by a five-digit number which is determined by internal number assignment. From a technical point of view, the prefix number identifies the uniqueness of the number.

1-7 Workflow Customizing

You activated the relevant workflow structures in the EBP customizing and assigned the agents for the tasks. In this activity you make all the necessary settings to adapt the standard tasks and workflow templates supplied by SAP.

What does it mean if a task is classified as General?

The standard workflows for Enterprise Buyer professional edition for the approval of shopping carts are designed in such a way that employees or managers can assign a different approver for a task at runtime (ad-hoc workflows).

Possible processors must be specified for each standard task in order to clearly define the organizational responsibility for processing.

General Task means that any user could potentially perform the task.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-8 Define Conditions for starting Workflows in EBP

In this step, you define which workflow is started under what conditions. What are the standard start conditions and how could you add another logic to that concept, if Phoenix Enterprises should decide that not every user in the system has the same spending limit and that not every manager has the same approval limit?

In this case, you are asked to implement the spending limit workflow to replace the one-step and two-step approval workflows. In standard EBP there are three start conditions, which have to be configured logically: one for the workflow without approval, one for the one-step approval workflow and a third for the two-step approval workflow.

It could be your task to implement the following approval model:

User ID Spending limit Approval limit SLAPPROVER

EMPLOYEE2 300 MANAGER

EMPLOYEE3 750 MANAGER

MANAGER 1000 2000 DIRECTOR

DIRECTOR 10000000 10000000

You would therefore need to carry out the following customizing steps:

1. Deactivate the event linkage for the workflows WS10000129 (one-step approval) and WS10000031 (two-step approval).

2. Activate the event linkage for the workflow WS10000276 (spending limit).

3. Create a new start condition for workflow WS10000276:

ReqtCovRequest.TotalValue > ReqtCovRequest.SpendingLimitofRequester

4. Change the existing starting condition for workflow WS10000060:

ReqtCovRequest.TotalValue <= ReqtCovRequest.SpendingLimitofRequester

5. In the organizational model, maintain the attribute SLAPPROVER for the users EMPLOYEE2, EMPLOYEE3 and MANAGER. Hint: the format for this attribute is US<userdid>, for example, USMANAGER.

6. Maintain a value for BBP_SPENDING_LIMIT for the users EMPLOYEE2, EMPLOYEE3, MANAGER and DIRECTOR: transaction PPOMA_BBP, Extended Attributes tab - enter the value of the spending limit and a currency.

7. Maintain a value for BBP_APPROVAL_LIMIT for the users MANAGER and DIRECTOR: transaction PPOMA_BBP, Extended Attributes tab - enter the value of the approval limit and a currency.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Master Data - Content


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Phoenix Enterprises has one R/3 Backend system with material master and vendor master data. To use the master data in the EBP system, the team members have to learn about the SAP business partner concept and replication. They also need to learn about the role of the CRM Middleware in master data replication.

Master Data: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Describe how business partners are integrated into a company’s organizational plan

? Replicate business partners using specific transactions in EBP

? Describe the functional scope of the CRM Middleware in the EBP system

? Replicate master data from the core R/3 System using the CRM Middleware


Master Data: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP vs. R/3 Master Data

ProductMaster

Product Category

Download via CRM Middleware or

create and maintain manually via<commpr01>


create and maintain manually via<comm_hierarchy>

EBPR/3

BusinessPartner

Vendor Masteror create and maintain manually via<bbpmainint>

Download via transactions

Material or Service Master

Material Group

? Product categories correspond to material groups in R/3. ? Business partner master records correspond to vendor master records in R/3.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Master Data - Overview

Product Master

Product category

Business Partner

R/3-Backend

Release 3.1Release 4.0Release nn

Enterprise Buyer

Non-SAP

? All master data can be found locally in the EBP system. This data includes product master records, business partner master records, and product categories. You can copy the master data from the back-end system to the EBP system.

? Material master data is transferred from R/3 to the Enterprise Buyer system using middleware. The relevant middleware object is MATERIAL.

? A single initial download is necessary in which the required materials are created in the Enterprise Buyer system as products. Subsequent changes (and also new materials) in R/3 are transferred by delta downloads.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SAP Business Partner – Concept and Relationships

CreditorRequester

Marketplaces

is employee

of

is invoice recipient of

is plant of Business-partner

VendorPlant

Organization

is registered

user of

? Role Concept ? Neutral ? Persons as well as organizations ? Uniform and central BP Role concept ? Any number of BP Roles can be defined within a Business Partner ? One BP can have several Roles ? One BP can define each Role once

? Business Partner Relationships ? Describes the relationship between two business partners ? Some relationships are time-dependent ? Attributes are connected to relationships

? Examples Contact person: Relationship among an organization as a BP and a person as a BP.

? Company participation: Relationship among two BPs that are organizations.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

External Business Partners

? Bidder

? Allowed to submit bids (Subset of vendor)

? Vendor

? Known business partner

? Preferred Vendor? Known business partner

? Contact Person? Represents an end user in the vendor or bidder organization

? Portal? Marketplace link (URL)

? Issuing point? Outbound delivery address from where the goods are shipped.

? Invoicing party

? Business partner that sends the invoice.

? Enterprise Buyer uses the SAP Business partner concept. An internal or external business partner is created in Enterprise Buyer for every person, organization, or group of people who could be involved in a business transaction. Within the context of business transactions, for example, a bid invitation or a purchase order, business partners can adopt various partner functions as long as they have fulfilled the relevant requirements.

? Business partners aggregate the master data of a person, organization or group of people.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organizational unit(O)

Position(S)

Business partner (organization)

Business partner (person)

Business Partner Model Organizational Plan

Address /Attributes

Attributes

is manager

is employee

is employee

Business Partner Integration with OrganizationalManagement

SU01 user (US)Central Person (CP)

? It is possible to create business partners for organizational units at a later time, and to ensure that the addresses of the organizational units match those of the associated business partners.

? Positions are different from jobs. A job is not concrete, but rather a resource used to create various positions with similar tasks and features. Positions are concrete and are occupied by holders (employees or R/3 users), purchasing administrator, European sales manager or secretary in the marketing department, for example.

? Following objects get a business partner number assigned: Organizations = Own department, Vendor, bidder, portal Users = Internal user, Contact person for external vendor or bidder

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Download of Business Partner (1)

Download ofvendors fromSAP R/3

<BBPGETVD>

Download of payment terms and qualitymanagement systems from SAP R/3

Rep.: BBP_UPLOAD_PAYMENT_TERMS

Rep.: BBP_UPLOAD_QM_SYSTEMS

? As of EBP 4.0 (or EBP 3.5 and Support Package 07) the terms of payment are not replicated via Transaction BBPGETVC but instead are replicated into the EBP system by means of the new report BBP_UPLOAD_PAYMENT_TERMS. Transaction BBPGETVC is obsolete and must no longer be used. However, Transaction BBPGETVC was not only used to replicate the terms of payment, but also the quality management systems. Report BBP_UPLOAD_QM_SYSTEMS is available now to load the quality management systems into the EBP system

? Transaction BBPGETVD exists to download vendor information as business partner information from the OLTP (R/3) system into the EBP system. You should take the following into account: whether the EBP system is to assign numbers from the internal number range for business partners for the vendors to be copied; whether the vendor numbers are to be copied from the back-end system. If a number already exists in the EBP system, the system assigns a number internally for the vendor. In this case, try to configure to the internal number range so that it does not overlap with the number range in the back-end system. Before the system performs the data replication, the system informs you of possible problems (such as missing purchasing organizations).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Download of Business Partner (2)

to map Vendor Data to different Backend Systems

<BBP_UPDATE_PORG>to adjust purchasing organizations

<BBP_UPDATE_MAPPING>

? To add, change or delete purchasing organizations, you can use transaction BBP_UPDATE_PORG. ? In multiple back-end scenarios, transaction BBP_UPDATE_MAPPING can be very useful because

vendors that once have been replicated do not need to be replicated again from other back ends if their numbers are equal (top area).

? Furthermore, if a back-end has been replaced (for example, from test to productive), this can be switched very easily from this transaction (bottom area)

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Business Partner automated Synchronization

<spro>

? Global Settings

? Settings for each Backend System

? Program only starts the synchronization for modified or added vendor masters from several backends

? Table BBP_VDSYNC_CUST displays when the last synch report ran? Table BBP_NEWVD_LOG or transaction BBP_SNEW_SYNCVD

show which vendors from which backends have when been newly added

<sm36>

? Program : BBP_VENDOR_SYNC

? BBPUPDVD - You can use this transaction to manually adapt the vendor data in the SAP Business-to-Business Procurement system if the master data in the back-end system has changed and no longer corresponds to the replicated data.

? The vendor master data can be synchronized automatically using the program BBP_VENDOR_SYNC. This program can be scheduled as job.

? Before you have to maintain the mentioned Customizing Settings and afterwards, the program synchronizes the Vendor Data automatically.

? Nevertheless for the initial download of Vendor Master Data, you should not use the SYNC Program. ? You can go to SLG1 to see the Synchronization Monitor.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Manual Maintenance of External Business Partners

? Performed by roles:

? ADMINISTRATOR? SAP_BBP_STAL_ADMINISTRATOR

? PURCHASER? SAP_BBP_STAL_PURCHASER

? SAP_BBP_STAL_PURCHASE_MANAGER

? SAP_BBP_STAL_OPERAT_PURCHASER

? SAP_BBP_STAL_STRAT_PURCHASER

<BBPMAININT>

? External business partners (vendors, bidders, portals, and their contact persons) can be maintained within the browser by users with the roles SAP_BBP_STAL_ADMINISTRATOR and SAP_BBP_STAL_PURCHASER, SAP_BBP_STAL_PURCHASE_MANAGER, SAP_BBP_STAL_OPERAT_PURCHASER, SAP_BBP_STAL_STRAT_PURCHASER.

? From this menu, you can create new contact persons for an existing vendor, bidder or portal. ? You can expand, for example, a bidder to become a vendor. ? You can create new and maintain existing vendors, bidders or portals.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP vs. R/3 Master Data


create and maintain manually via<commpr01>


create and maintain manually via<comm_hierarchy>

EBPR/3

BusinessPartner

Vendor Masteror create and maintain manually via<bbpmainint>

Download via transactions

Material Group

ProductMaster

Material or Service Master

Product Category

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP R/3

Data Flow in Enterprise Buyer

CRM Middleware

Ad

apter

Plu

g-In

Trigger InitialDownload

OLTP TriggerDownload

BAPI SaveSend to

Server

KeyGenMapping

R/3 ExtractorProxy Extract

qRFC

qRFC

BDoc

? The Middleware is a set of programs that exist partly in the EBP/CRM System and partly in the R/3 plug-in. These programs initiate the download of Product Categories (Material Groups), Plants, Condition Tables and Product Masters (Material Masters & Service Masters) from the back-end R/3. The initial download extractors are triggered from Middleware. The extractors consist (as main function modules) of: ? Extractor Function Modules ? ID Extractor (determines a list of records to be extracted) ? Data Extractor (extracts the records in bulk)

? The initial download trigger agent calls the OLTP download trigger agent. This triggering is done via qRFC. This ensures that the download is executed exactly once. The OLTP download trigger agent calls the extractor proxies for the selected business object classes that in turn call the R/3 extractors. The RFCs are queued and processed in a restrictive sequence (dependent vs. independent objects). In R/3, a function module call (extractor module call) takes place to extract the requested data according to filter criteria handed over. Moreover, the creation of data containers with the selected data to be sent to CRM Middleware Server takes place. The data is transferred via RFC in the form of tables to the CRM.

? In CRM, the data containers from the OLTP underlie the Mapping, which results in the creation of a BDOC. The BDOC then initiates the update of the database.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Structure

? Product and Category are identified by a product ID. This ID can be entered manually and is not to be confused with the GUID

? GUID = Global Unique Identifier

? Internal identification (GUID); not visible on screens

?External identification (Category ID); visible on screens

?Product type

?Original system

GUID

? All products have at least: ? Material number ? Description (short text) ? Assignment to product category (currently automatic during download from R/3)

Download Categories Products and Assignments

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

R/3 System & CRM Middleware

EBP systemInitial DownloadDelta Download

? Data exchange between EBP and R/3 system

? Automatic and scheduled data exchange

? Middleware Plug Ins in R/3 system act as counterpart to R/3 Adapter in Enterprise Buyer

? Data transport realized through BAPIs via qRFC

? The Plug in package is installed on the back-end R/3 to facilitate communication with the middleware server. It mainly contains BAPIs and data extractors for those objects exchanged between the two systems.

? The extractors extract the data from the R/3 database. They are not specific to the CRM Middleware server but are also used for other areas of application (like APO or BW). Using the extractors implies two steps. In the first step, filter criteria is handed over to an extractor. The extractor determines and returns the keys of all business objects that fit to the filter criteria. In the second step, the extractor is called with the Key list to read out the actual information. The extractors retrieve the data from the tables specified in the call to the extractor, the root table, and the dependent tables.

? Initial download: When configuring the middleware server, all data needed from R/3 is downloaded. ? Delta download: Only delta information is downloaded from the OLTP R/3 during normal operation, for

example, changes to the product master in the R/3 are automatically downloaded to the middleware server.

? The structure mapping converts R/3 structures to CRM structures.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

R/3CRM Middleware

R/3 Adapter Objects

Business

Customizing

Conditions

Objects

Objects

? Adapter Objects are exchanged between R/3 and CRM Middleware

? There is a restrictive sequence the objects must be exchanged (e.g. customizing objects before business objects)

? Differentiation between depending and independent objects

? There is a particular sequence in which objects have to be exchanged between the various systems. A distinction is made for this purpose between the so-called independent objects and the dependent objects.

? Independent objects can always be processed in parallel, thereby improving performance. A dependent object, however, cannot be forwarded until the associated independent object has been transferred to the other system.

? An order can be passed to R/3 only after the customer who placed the order has been created in R/3. Once the customer has been successfully created, the order becomes available to R/3 together with the new customer number. If, however, the new customer is rejected by R/3 (because of missing entries, for example), then the order will also be rejected.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

R/3

? On each system, the other system is known as an RFC-destination

? RFC-access requires a user on the respective other system

? Perform settings in tables:

?CRMRFCPAR in OLTP R/3

?SMOFPARSFA on CRM middleware server

? Define logical systems on each system

Middleware

RFC of type R/3 connection

User : RFCuserPassword: *********

RFC-Destination: OLTP R/3 RFC-Destination: CRM

Communication: Middleware and R/3

User : RFCuserPassword: *********

? SMOFPARSFA, the main parameter file of the CRM Server, contains all system control parameters, including the control information relevant to the R/3 Adapter.

? The CRMRFCPAR parameter file is the main parameter file used on the R/3 side. It contains control parameters for data exchange with the CRM Server.

? In each of the systems involved, a user must be created that can be used as a reference in the RFC destination definition.

? Before two or more systems can communicate with each other, the technical connection between them has to be established. When setting up the RFC destination, the destination address for data transfer is specified.

? Define the logical system and assign it to a client (Refer to OSS Note Nr. 181958). ? The maintenance is necessary in all connected systems. If the assignment is missing on the R/3 side,

material master data, for example, cannot be downloaded. If the assignment is missing on the CRM Server, upload cannot be carried out.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Administration Console

Site Name

Description

Site Type

RFC Destination

Site Type

Site Name

Site attributes

Sites are used to specify both the CRM (EBP) as well as theR/3 Destination for the Middleware Data Flow.

Receiver RFCSender RFC

Load Object

<SMOEAC>

Setting up Sites

? The initial download is needed to fill the CRM Middleware server database before beginning the productive operation. During customization time, the business object classes to be downloaded are determined. Additionally, business object instances can be filtered depending on certain attribute values.

? Sites are used to exactly specify the Sender and Receiver destination. EBP needs the R/3 back-end destination (type R/3) with the RFC Destination maintained in the site attribute information, plus the EBP client destination (type CRM) with the corresponding RFC Destination from transaction SM59. This site information is used to start the initial download of the activated objects. Only those objects relevant for EBP can be replicated without a corresponding CDB site entry.

? When an initial download is performed, business, customizing and condition objects are copied in their entirety from R/3. The initial download provides the CRM Server with an initial data set of R/3.

? Business object structures are determined by R/3. Therefore, modifications to business objects are not supported.

? Customizing Objects are customizing tables (T* tables, for example T100) coming from R/3. ? Condition objects are condition tables for price evaluation.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

CRM Middleware OLTP R/3Employee

Result sender

R/3 Adapter

Flowcontrol

BDOC Creation

Update

Business TransactionEvent (BTE)

Delta Download

qRFCBAPI Save

Mapping

1

2

3 Event distributor

Update function modules

Dialog program

? The in-house employee working online with a dialog program is now the source for changed data. The dialog program calls the update function modules and commits its work. The update modules raise the events about changed business data and the subscribed result sender calls the result save agent in the CRM Middleware server to transport the modified business data. In contrast to the upload process, there is no additional CRM data for the result sender to send to the CRM Middleware server. A new BDoc for the data received from the R/3 is created and flow control is started to process the corresponding control flow for it.

? Different applications can subscribe for the delta data, too (e.g. BW, APO…). This is done by an entry in R/3-table TBE31: Every event can be processed several different times (by several applications using different function modules).

? Delta download is active for certain objects - Source-code is implemented in the update task of the specific business object; queued RFC is then triggered automatically.

? On the R/3 side: ? Make sure that the event interface on R/3 is set to active in the TBE11 table. Although the event

interface is delivered active, events could have been switched off manually for test purposes. If this is the case, activate the entries for application BC-MID and NDI.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

CRM Middleware Portal

Middleware Runtime Information

<SMWP>

? The Middleware Portal provides the administrator with relevant Runtime information and displays important parameters: ? Download Status of Initial Download Objects ? RFC Queues ? Middleware Parameters ? OLTP Parameters ? Generated BDoc Objects ? Generated Message Flow

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Product Master View is a tab

Set types are frames

Attributes are fields

Manual Maintenance of Products

<COMMPR01>

? The product master provides information on all the products that a company purchases and sells. Products can be tangible (such as a PC) or intangible (such as services like PC maintenance). The product master is the central source for retrieving product-specific data. This information is stored in individual product master records. Each product master record contains the data required to manage the product.

? Product master records contain not only data on the product itself, but information from other relevant areas such as sales and purchasing. This data can be grouped together in views. The integration of such data in a single database object eliminates redundant data storage. This data is required, for example, for placing orders in purchasing and for processing sales orders in sales and distribution.

? In EBP/CRM, products are maintained using sets. Sets appear as subscreens in the views (such as the view Basic Data) in product maintenance. You can define set types of your own and assign them to product categories. You can also define the view where the set type appears.

? A set type is made up of the described attributes and is stored in the CRM System as a database table. The use of set types makes it possible to precisely model a product in the system.

? Certain set types are predefined in the standard system. If they are not sufficient for your needs, you can further define set types of your own and assign attributes to them.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Describe how business partners are integrated into a company’s organizational plan

? Replicate business partners using specific transactions in EBP

? Describe the functional scope of the CRM Middleware in the EBP system

? Replicate master data from the core R/3 System using the CRM Middleware


Master Data: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Master Data

Topic: Vendor Replication


? Create an organizational unit for vendors

? Replicate vendor related customizing data from the back-end R/3

? Replicate vendor masters from the back-end R/3

In this exercise, you will replicate the vendors your company has decided to use for EBP.

1-1 Create a new organization in the organizational plan for vendors.


Client : 3##

User ID: CONFIG

Password: learn

Start the transaction Create Attributes (PPOCA_BBP) from your Favorites

Enter through the Validity Period message.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Create the Vendor Root Organizational Unit.

Go to BASIC DATA tab.

Enter External BP to replace New Org. Unit.

Enter Business Partner @ Phoenix to replace New Organizational Unit.

Select Continue.

Go to ADDRESS Tab.

Enter the following address data:

Education Way / 123 as the House No./Street

New York / 12345 as the City / Postal code

US / NY (New York) as the Country / Region



Choose Replace.

Enter [email protected] as the e-mail address.

Select Continue.

Choose Save.

Go Back.

What is the Object ID of the newly created organization?

________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


It is not necessary to enter address data. The Organizational Unit you just created serves merely as a folder in your PD-Org allowing you to replicate vendors. However, it leads to a green traffic light in the BP overview later on.

1-1-2 Add the following attributes to the vendor organization.


Double-click on

Business Partner @ Phoenix

Organizational unit.

Go to ATTRIBUTES Tab.

Enter the following data:

In row Enter the value

ACS (System Alias for Accounting Systems)

T90CLNT090

BUK (Company Code) T90CLNT090\3000

CUR (Local Currency)

USD

EXT_ITS (Current ITS for an External Partner)

http <get from your instructor>:1080/scripts/wgate/bbpstart/

VENDOR_ACS (Accounting System for Vendor)

T90CLNT090

VENDOR_SYS (System Alias for Vendor)

T90CLNT090

Choose Continue and than select Insert in the VENDOR_ACS line to add a second value for the attribute VENDOR_ACS.

VENDOR_SYS (System Alias for Vendor)

SRM_00_3##

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Replicate the customizing data associated with the vendors in the back-end R/3.

1-2-1 Replicate the terms of payment from the back-end R/3.

Start transaction Execute Program (SA38) from the menu bar.

System ? Services ? Reporting

Enter BBP_UPLOAD_PAYMENT_TERMS as the Program.

Choose Execute.

Choose T90CLNT090 as the System.

Select Execute.

Choose Continue to confirm the message.


1-2-2 Replicate the quality management systems from the back-end R/3.

Start transaction Execute Program (SA38) from the menu bar: System ? Services ? Reporting

Enter BBP_UPLOAD_QM_ SYSTEMS

as the Program.

Choose Execute.

Choose T90CLNT090 as the System.

Select Execute.


Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Replicate the vendor master records ARAMI-##, MCCOY-## and EBP-## from the back-end R/3 to the EBP System.

1-3-1 Use the transaction BBPGETVD and the following information to start the transmission of the ARAMI-## vendor master replication.

Enter /n in the Command field of the Standard Toolbar.

Enter BBPGETVD in the Command field of the Standard Toolbar.

Choose R3_00_800 as the System.

Enter ARAMI-## as the Vendor.

Enter <number of the Org. Unit Business Partner @ Phoenix>

as the Object ID.

Verify that Only Transfer R/3 Numbers

radio button is set.

Choose Start Transfer.

Choose Start Transmission.

Select Continue to confirm the message.

Choose Cancel.

The number for the Object ID should be in the form of 50000XXX.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3-2 Use the transaction BBPGETVD and the following information to start the transmission of the MCCOY-## vendor master replication:




Enter MCCOY-## as the Vendor.


as the Object ID.



Select Start Transfer.



Select Cancel.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3-3 Use the transaction BBPGETVD and the following information to start the transmission of the EBP-## vendor master replication.




Enter EBP-## as the Vendor.


as the Object ID.



Select Start Transfer.



Choose Cancel.

1-3-4 Display the Application Log with transaction SLG1.

Enter SLG1 in the Command field of the Standard Toolbar to view Application log.

Enter BBPGETVD as the Object.

Select Execute.


Choose Start SAP Easy Access.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3-5 Run the business partner check transaction.

Start the transaction Customizing – Edit Project (SPRO) from your Favorites.

Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Organizational Management ? Integration Business Partner-Organizational Management ? Create Business Partners Initially

Select Organization Unit(s).

Select Execute.

For all partners with yellow traffic light, select the line and …

Select Start Synchronization Procedure.

Make sure every light is

Green before leaving transaction.

Choose Back (four times).

Verify that all status indicators are green excluding the Dummy Folder in the Organizational Structure of the Vendor Organization.

If they are not, make the necessary adjustments.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3-6 Verify that the vendors were replicated and assigned to the organization.


Double-click on

External Business Partner @ Phoenix

Verify the created

Organizational Units in the Organizational Structure.

What are the business partner numbers assigned to the vendors?

ARAMI-##: _______________________________________

MCCOY-##: _______________________________________

EBP-##: _______________________________________

Leave the transaction.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4 Map the replicated vendors to the Local Purchasing Organization

1-4-1 Map the replicated vendors manually.

Log on to YOUR CLIENT of the EBP from the BROWSER:

User ID: WEBADMIN

Password: learn

Client : 3##

Use the following information to map each of the replicated vendors to your Local Purchasing Organization:

Go to Manage Business Partners

in the launch pad.

Enter ARAMI-## as the Business Partner Data.

Choose Edit.

Select Display/Change.

Choose Send via E-mail as the Standard Communication Protocol.

Go to VENDOR DATA tab

Add a second line in the area Vendor Purchasing Data:

Choose to open the drop-down-list

for the Purch. Org. ID field.

Choose . . .

Choose PUR Local Process as the Purch. Organization.

Choose American Dollar as the PurchOrder Currency.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Print as the Transm. Medium.

Select to open the drop-down-list

for the Terms of Payment field.

Choose . . .

Choose Pay immediately (0001)

as the Terms of Payment.

Select Save.

Log off.

1-4-2 Map the replicated vendors with transaction BBP_UPDATE_PORG.


Client : 3##

User ID: CONFIG

Password: learn

Execute BBP_UPDATE_PORG in the Command field.

Choose PUR Local Processes as the New purch.org.entry.

Choose PUR Back Processes as the Add to purch. org.

Choose Add.

Select Continue.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 Create a contact person for your replicated vendors. Partner MCCOY-## is first.

Log on to YOUR CLIENT of the EBP from the BROWSER:

User ID: WEBADMIN

Password: learn

Client : 3##

1-5-1 Create a contact person for the MCCOY-## vendor using the following information:

Go to Manage Business Partners.

Enter MCCOY-## in the Contact Person for Business Partner field.

Choose Create.

Maintain the following data

Ms. as Title

Cindy as First Name

McCoy as Last Name

English as Language

USA as Country

Eastern Time (New York) as Time zone

USA as Format name

Build1 as Building Code

1 as Floor

1 as Room Number

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Dept1 as Company Dept.

610-661-1000 as Telephone

USA as Country

[email protected] as E-Mail

MCCOY as User ID

init as Password

init as Repeat Password

SAP_BBP_STAL_VENDOR as Role

Choose Save.

What is the partner number that was assigned to this newly created contact person?

1-5-2 Create a second contact person with the User ID ARAMI for your vendor ARAMI-##, similar to exercise 1-5-1. Maintain all required data.

What is the partner number that was assigned to this newly created contact person?

________________________________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-6 View the user data for the business partner and contact person.


User ID: MCCOY

Password: init

Client : 3##


Choose Process User Data in the launch pad.

Select Edit for the Business Partner Data.

Select <each tab> to view the data.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Master Data

Topic: Material Replication


? View the filters needed for material replication

? Change the filter settings and regenerate them

? Replicate material masters from the back-end R/3.

To procure and reserve material masters in the EBP system, the material masters must be replicated from the back-end R/3. Once replicated, these material masters are referred to as product masters. In this exercise, you will replicate material master from the back-end R/3.

2-1 View the products that have already been replicated from material masters in the back-end R/3.


Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-1 Add the transaction COMMPR01 to your Favorites in the Easy Access menu.

Right-click on

Favorites.


Enter COMMPR01 as the Transaction code.

2-1-2 Use the transaction COMMPR01 to search for and view the existing products in the EBP System.

Start the transaction Product (COMMPR01) from your Favorites.

Go to Search Tab.

Choose Material as Find.

Enter * as the ID/Description.

Choose Start.

What materials are listed?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Display the material master T-SRM1## in the back-end R/3.

Log on to the BACK-END R/3.

Client : 800

User ID: BACK-##

Password: learn

Display the plant stock view of the material master T-SRM1## for plant 3200.

SAP Menu ? Logistics ? Materials Management ? Material Master ? Material ? Display ? Display Current

Enter T-SRM1## as Material.

Choose Enter.

Select Plant Stock as View.

Choose Continue.

Enter 3200 as Plant.

Choose Continue.

What is the description of the material?

How many units of unrestricted use stock are available?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-3 Before you start the replication process please check if there are old entries in the inbound queue of your client. Delete all existing items.


Client : 3##

User ID: CONFIG

Password: learn

User menu for CONFIG ? Middleware ? Monitoring ? Queues ? Display Inbound RFC Queues

Enter 3## as the Client.

Enter * as the Queue Name.

Choose Execute.

If there are any Entries

Choose Select All.

Select Delete Selected Objects.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-4 View the current filter settings in the EBP system.

Use the following information to change the current filter settings of MATERIAL filters:

User menu for CONFIG ? Middleware ? R/3 Data Exchange ? Initial Download ? Object Management ? Business Objects

Select Material as Business Adapter Object.

Select in Filter Settings column.

Choose Display ? Change

Go to Filter Settings tab.

Choose R3_00_800 as Source Site Name.

Set Indicator Inactive for the first three existing entries.

Add an entry with the following data:

MARA as Table

MATNR as Field

Equality as OP

T-SRM## as Low

Inclusive defined set/array

as Incl./Exl.

Add another entry with the following data:

Add another entry

MARA as Table

MATNR as Field

Equality as OP

T-SRM1## as Low

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Inclusive defined set/array

as Incl./Exl.

Choose Save.

What is the message text you receive for the filter settings changes?

Choose Continue to confirm the message,

Attention Before you synchronize your filter as mentioned below and before you start replicating as mentioned in exercise 2-5, notify your instructor before you proceed to prevent interfering with each other.

Choose Filter Sync. (R/3).

What is the message text you receive for the filter synchronization?



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-5 Replicate the material master records T-SRM## and T-SRM1## from the back-end R/3 to the EBP System.

2-5-1 Start the initial download of the materials T-SRM## and T-SRM1##

User menu for CONFIG ? Middleware ? R/3 Data Exchange ? Initial Download ? Start

Choose Material as Load Object

Select Enter.

What sites (Sender) is shown for the Data Flow and why?

Enter CRM as Destination Site (Receiver) if necessary.

Choose Execute.

What message do you get after starting the download?

Choose Continue.

Select Back

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-5-2 Verify that the material master records and plants were successfully transferred by viewing the Download Objects Monitor with transaction R3AM1 or

User menu for CONFIG ? Middleware ? R/3 Data Exchange ? Initial Download ? Monitor Download Objects

Choose Material as Object Name

Select Execute.

What is the status of the Material?


2-5-3 View the newly replicated product.

Start transaction

COMMPR01 from your Favorites.

Go to Search tab.


Select Start.

Which materials are listed?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-6 Maintain a local material in the transaction COMMPR01.

Choose Material.

Choose Drinks (MAT_FGTR) as the Category.

Select Continue.

Enter MAT## as the Material.

Enter Champagne Albert Le Brun

as the Description.

Go to General tab.


Enter R3MATCLASS as the Hierarchy ID.

Choose German as the second entry for the Language in the area Descriptions.

Enter Champagne Albert Le Brun

as the German Product Description.

Go to Material tab.

Enter PAL as the Base Unit of Measure.

Enter This Champagne, which is composed of 1/3 Chardonnay and 2/3 Pinot grapes from the best villages, makes it ideal for drinking on any occasion. Its quality enables it to be enjoyed throughout a meal, from the aperitif to the dessert.

as the Basic text.

Go to Purchasing tab.

Maintain PAL as the Order Unit.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Save.


User ID: EMPLOYEE

Password: learn

Client : 3##

Select Shop in the launch pad.

Go to Internal Goods/Services tab.

Search for MAT##.

Choose Add to Shopping Cart.

Select Details.

To which Product Category is the material assigned?

Select Step 3 Complete and Order.

Choose Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-7 OPTIONAL: Upload materials from EBP to the back-end system.

Start transaction Customizing – Edit Project (SPRO) from your Favorites.

Goto ? SAP Reference IMG ? SAP Implementation Guide ? Customer Relationship Management ? Master Data ? Product ? Settings for Product Type ? Allow Upload for a Product Type

Verify that for the Product Type 01, the Indicator Upload Allowed is set.

Go back to the SAP Easy Access Screen.

The Unit of Measurement entry is only needed if you want all units mapped to a certain one in the back end. If units are maintained well at product level, you can leave it empty.

Start the transaction

COMMPR01 from your Favorites.

Go to Search tab.


Choose Start.

Double-click on

MAT## in the list.

Choose menu path

Goto ? Transfer to OLTP …

from the menu bar.

Verify that R3_00_800 R/3 back end connection

is the RFC Destination.

Choose 01507 (Alcohol) as Material Group Ind.

Choose F as Industry Sector.

Select Check

Choose Start Upload.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Client : 800

User ID: BACK-##

Password: learn

View the material master record MAT## in the back-end system.

SAP menu ? Logistics ? Materials Management ? Material Master ? Material ? Display ? Display Current

Enter MAT## as Material.

Select Basic Data 1 as View.

Verify that MAT## has been uploaded successfully.

2-8 Vendor Data:

The replicated data are updated via the synchronization Job. Do you have to run Create Business Partner initially again?

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-9 Material Master:

Your company has a multi-back-end environment where in each ERP system different material masters have the same material master number. How can you use the product information in EBP? How can the EBP system differentiate the product masters?

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions

Unit: Master Data

Topic: Vendor and Material Replication

2-8 Vendor Data:

The replicated data are updated via the synchronization Job. Do you have to run Create Business Partner initially again?

Once the Business Partners in the Organizational Structure have been initially created and the PPOMA has been checked regarding missing data, you do not have to run this transaction after doing an update of the vendor data.

Normally the Create Business Partner initially is planned as a job in the background.

2-9 Material Master:

Your company has a multi-back-end environment where in each ERP system different material masters have the same material master number. How can you use the product information in EBP? How can the EBP system differentiate the product masters?

Use the CRM Middleware to replicate the products from each ERP system. The EBP system differentiates different products by means of Global Unique Identifiers (GUID). Furthermore, the source system information is included in each product master record (Goto – source system) and in the COMM_PRODUCT table.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Catalog Management


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Phoenix Enterprises has decided to use an internally hosted catalog as part of its catalog strategy. In this unit you will connect this catalog to the EBP system and practice searching for items.

? The team members will also learn about the basic concept of content management using Requisite eMerge.

Catalog Management: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Catalog Management: Unit Objectives

? Catalog Definition

? Catalog Scenarios

? Requisite Components

? Open Catalog Interface

? Content Management


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Definition and Value of Catalogs

? Definition:

? External or internal repository containing product information and product graphics

? Includes a search engine that finds products and services

? Uses authoring tools to update and change catalog contents

? Value Added:

? Controls indirect procurement by directing users to strategic suppliers

? Indirect procurement often involves parts and service items which are not usually stored in R/3 Materials Management

? Catalogs provide extended product information through links to manufacturer/supplier data. This ensures that correct items are purchased

? Ability to pull pricing and availability from supplier catalog

? The full functionality of the supplier’s catalog may include: ? Pictures of offered goods/services ? Prices relevant to the customer ? Current availability of goods ? Supplier shopping baskets

? Suppliers may maintain the catalog ensuring up-to-date prices and availability. ? EBP users need to purchase parts and services which are not in R/3 Materials Management (for

example, one-of-a-kind or low value items). ? Catalogs can help control indirect procurement by directing the user to strategic suppliers. ? Negotiated prices are shown so that reduced costs may be achieved. ? Product displays and correct supplier data ensures “clean” orders are passed to the supplier. ? Users may be directed to a particular section of a catalog (for example, a search screen for particular

types of goods or services).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP Catalog Scenarios

Content broker/Marketplace

Procurementworld-wide

External supplier owns catalog

C

C

C

? Multi-supplier catalog

? Maintained and hosted byexternal catalog broker

C

Catalog hosted by company (intranet)

? Purchasing departmentmaintains catalog

? Content is provided by suppliers

Access via Internet

Access via Internet

2

3

1

Company boundary

? Supplier updates catalogs

Internal catalog

? Purchasing from ownstock (within companyboundary)

4

C

C

C

C

C C

C

C C

C

DB

C

? One of the main advantages of using Internet-based procurement software is the integration with online catalogs, enabling easy location of products.

? It is generally possible to allow specific employees specific views on particular catalogs (for example, access restricted to office materials product category.)

? SAP supplies a catalog management tool (Requisite Technology). ? EBP supports the following catalog scenarios: ? You access the vendor catalog directly from EBP via the Internet. The vendor is responsible for

setting up the catalog and maintaining the contents. ? Using the Internet, the purchaser accesses a catalog that combines the offerings of several suppliers.

The catalog broker is responsible for setting up the catalog and maintaining the contents. Catalogs (for example, industry-specific catalogs) can be located on marketplaces.

? The catalog is within the firewall. The company-specific catalog combines the offerings of several vendors. The catalog may be updated, for example, by the vendor accessing his part of the catalog.

? Internal order processing is dealt with using EBP. A catalog also uses internal master data.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Requisite BugsEyeTM Catalog

? Delivered with EBP

? Standard components:

? Requisite BugsEyeTM search engine and user interface

? ECManager Administration, Data Loading, Maintenance, and Reports

? eMerge Requisite Content Management Tool

? Requisite uses a textual search. ? Overview: ? Exact detail is rewarded with exact matches. ? Vague data searches are rerouted to a better search. ? Forgiving searches ignore extraneous detail, spelling mistakes, and wrong order. ? All three components are accessed by Internet browser. Whereas the BugsEyeTM and ECManager

comprise all vital functionality a catalog needs, Requisite sells the enhanced customizing and tool eMerge. ? When exact details are specified, exact matches can be found. Graphics and other multimedia files

attached to the item helps communicate that the correct item has been identified. ? If vague search details are entered into the Requisite BugsEyeTM catalog, the user is directed to

matching categories as well as possible items. In addition to helping the user find the appropriate item at the time, this also educates the user towards giv ing better search details in the future. ? The BugsEyeTM finding engine is forgiving of extraneous detail, spelling mistakes, and wrong order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

SAP Open Catalog Interface

Outbound parameters (catalog call structure)

Inbound parameters (catalog information)

OCI

The SAP Cart Editor is used to construct the Interface between the BugsEye Shopping Cart and the SAP OCI.

Principle of communication between EBP and BugsEye

Enterprise Buyer Professional

REQUISITEBugsEyecatalog

? The Open Catalog Interface (OCI) describes the data exchange between the EBP system and external catalog applications. OCI enables the transmission of selected goods and services from an external catalog to the EBP system. The external catalog is located either within the Intranet or somewhere on the Internet.

? Any catalogs that are used must conform to the OCI specification. This means that instead of goods being ordered directly from the catalog, a button is added to send the shopping cart data back to EBP. This triggers a Web request back to EBP in the format specified in the OCI. The catalog interface consists of two separate and distinct sections, the inbound section and the outbound section.

? In order for BugsEye to send items from its shopping cart to the external system via a URL, it needs an interface to define the parameters between BugsEye's common attributes and the equivalent external attributes. The Catalog Connector creates the mapping between the two sets of attributes, defining the interface between the two systems.

? BugsEye is equipped with a default set of mapped attribute as the generic connector. ? Other attributes need to be mapped to the OCI Name.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Open Catalog Interface - Inbound Parameters

? Description

? Product Master

? Product Category

? Quantity? Unit of Measure

? Price

? Price Unit

? Currency? Lead Time

? Vendor

? Vendor Product Number

? Manufacturer? Manufacturer Material Number

? Contract Number

? Item of a Contract

? Service Flag

? Quote

? Quote Item

? Product Identifier? Long Text

? Attachment title

? Attachment purpose

? Standard schema? Internal Product Category / GUID

? (5) Customer Specific Fields

? The inbound section consists of the information being sent from the catalog application to the Procurement application. This section contains data on the items selected in the catalog, such as the item descriptions, quantities ordered, and prices.

? Inbound specifications are different for catalogs and services. ? As of Release 1.0 of Enterprise Buyer Professional, five customer-specific-fields are available. If these

fields are used, the data has to be evaluated by a BADI. ? The interface is also able to process XML as input. A prerequisite is that you have installed the SAP

Business Connector or the Exchange Infrastructure on the receiving side. ? In Release 3.0 of Enterprise Buyer, some new fields have been added to the interface. These are:

NEW_ITEM-ATTACHMENT_TITLE / NEW_ITEM-ATTACHMENT_PURPOSE / NEW_ITEM-EXT_SCHEMA_TYPE

? For reference to a standard schema, for example, UN/SPSC: NEW_ITEM-EXT_CATEGORY_ID. ? This field is linked to the field NEW_ITEM-EXT_SCHEMA_TYPE. It is used if Enterprise Buyer

provides mapping for a specific standard schema. It supplies the internal product category and GUID.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Integrated Catalog

Integrated Call Structure

Standard Call Structure

open catalog in new window

? Up until now when you accessed catalogs in the Shop application, they were opened in a separate window. As of Release 3.0, catalogs can be opened within the Shop application via a new, Integrated User Interface. This has the following advantages: ? You can see products immediately when you add them to the shopping cart, displayed directly below

the catalog view. ? You do not have to work in more than one window; all information is visible within the application. ? The user interface is seamlessly integrated into Enterprise Buyer, improving usability. ? As before, you still have the option to work with catalogs in a separate window.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Defining the Catalog in EBP

? During EBP Customizing, catalogs are defined using these parameters:? Catalog ID? Catalog name

Sources of Supply Assigned to Catalog:? Business partner

? Purchasing organization

Additional Functions in EBP:? Product is not checked

? Maintain Error Log

? Add contract data

Technical Settings

? HTTP GET or HTTP POST

Additional Functions in the Catalog:? Updated Display of Product

Data possible

? Updated Validation possible

? Source of Supply determination possible

? These parameters can be set when defining the catalog parameters. ? To Identify the Catalog, you have to maintain a Catalog ID and the Catalog name. ? In Customizing, you can assign Sources of Supply to the Catalog. ? Assigning a business partner during Customizing only makes sense for single -vendor catalogs. In the

case of multi-vendor catalogs, no Customizing entry is necessary. In this case, the vendor identification has to be available in the catalog and be passed over by the OCI.

? Assigning a purchasing organization during Customizing only makes sense for a logical catalog that is only used by one organization.

Additional Functions in EBP: ? If you replicate products (materials and services) from a back-end system directly to the catalog and

do not wish to replicate these into EBP because your users always select products from the catalog, you can use this indicator to ensure that the products are transferred without checking into the EBP System (for example, into the shopping cart). ? Maintain Error Log ? This indicator is used to specify whether the application log is used for the respective catalog. If this

indicator is activated, error messages that occurred during catalog data enhancement can be evaluated. ? Add contract data: ? You should set this indicator if you wish to supplement the data displayed in the integrated catalog

with contract data. ? If a contract exists in your system, this is displayed and the prices are updated in an additional step. ? Additional Functions in the Catalog: ? Updated Display of Product Data Possible

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? When this flag is set, an updated display of product detail data and a picture of the catalog can be created in EBP. A prerequisite is the mapping of the Global ID and the NEW_ITEM_EXT_PRODUCT_ID field in the OCI. (BugsEye™ >= 2.8) ? Updated Validation possible:

This Customizing setting checks whether data of items ordered using a stored template is still valid. A prerequisite is the mapping of the Global ID and the NEW_ITEM_EXT_PRODUCT_ID field in the OCI (BugsEye™>=2.8). Supp. Source:

This flag allows you to perform a search in a specified catalog by typing the search string directly in EBP. (BugsEye™>=2.8)

Technical Settings: ? This field contains the HTTP method to be used to call an external catalog.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Catalog Call Structure

? Link to catalog must be configured within EBP

? Contains URL and required login information

? Login information is specific to Requisite BugsEye TM catalog

Define Catalogs

Dialog Structure

Catalogs and Names

Standard Call Structure

REQUISITE Catalog BugsEye

Integrated Call Structure

Catalog URL

Catalog user

Catalog Password

Return information

HTTP commands

Outbound Parameters

? The outbound section defines the information being sent from the EBP application to the catalog applications. This can include information such as the catalog URL and login data.

? In the EBP system, this information has to be set up during Customizing: EBP ? Define Catalogs. ? Note the following when setting up this information: ? Many of the field names and values depend on the particular catalog. ? You must structure the fields in the order shown in the installation guide.

? Once the catalog has been assigned to organizational units (attribute CAT), the Customizing in EBP is finished. Transaction: PPOMA_BBP.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Catalog Views – Integration with Enterprise Buyer

Step 1

Step 2

Step 3

Step 4

Build View in Requisite

Assign View to catalog user

Define Catalogin EBP customizing

Assign Catalogin PPOMA

Requisite

EBP

? To integrate catalog views with Enterprise Buyer, proceed with the following steps: ? Create a search view in Requisite. ? Assign this view to a generic logon user under Edit Users. ? Log on to Enterprise Buyer and define a catalog call structure using the above user. ? Switch to org structure in Enterprise Buyer and assign the catalog ID to your end users.

? The call structure (outbound parameters ? see OCI description) that has to be defined for every single catalog definition, consists primarily of the catalog’s URL, the username, and the password required for the BugsEye’s log on. As every different catalog user has its own limited view on the catalog’s content, every catalog definition in Enterprise Buyer gives access to only those products restricted within this view. Thus, several catalog definitions within Enterprise Buyer can point to the same catalog URL, but depending on the catalog user’s view only a limited number of constrained products can actually be purchased by the individual user.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Content Providers and Content Management

? Can be maintained by the customer

? Suppliers can be content aggregators who collect manufacturer data

? Third parties can build businesses around content aggregation

? Customers can connect directly to manufacturers and overlay with their own sourcing information

? Any of the above can be combined

Portal

ContentBroker

Supplier(manually)

Supplier(file)

? Content issues: ? Most electronic data was not made for finding items ? Not all suppliers have electronic data ? Conversion of paper catalogs to electronic catalogs ? Lack of classification standards ? Too many standards means no standard ? Lack of data format standards

? Catalog issues for content management include: ? Customers would rather have suppliers maintain catalogs ? Customers want to track sensitive data with catalogs, but do not always want suppliers to see this

information ? While supplier catalogs are attractive, every supplier has their own look-and-feel, and this creates a

chaotic environment for procurement by occasional users ? Customers or suppliers can maintain catalog information as needed ? Third parties, content aggregators, or customers can collect appropriate catalogs for their industry and

outsource the catalog collection to other organizations in the same industry

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Requiste eMerge & BugsEye

ContentImport

LoadingRules

Actions

Mappings

• Approved

• Cleansed

• Mapped

ContentExport/Import

EBP

OCIContent

File

Requisite eMerge

Requisite

BugsEye

? Requisite eMerge is a staging catalog system that validates, cleanses, and enhances content prior to moving it to the BugsEye catalog.

? After the content has been validated via eMerge loading rules, mapping tools, and cleansing features, it is exported and then uploaded to the BugsEye catalog.

? Users creating shopping carts in EBP only connect to the BugsEye catalog where users only have access to valid and enhanced content.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Content Management Training

...for further information on Requisite Catalog & Content Management

SRM240

T H E B E S T -RUN E- BUSINESSES RUN SAP

SRM240Requsite Catalog & Content Management

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Catalog Definition

? Catalog Scenarios

? Requisite Components

? Open Catalog Interface

? Content Management


Catalog Management: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Catalog Management

Topic: Define and Search a Catalog


? Connect a catalog to the EBP System

? Use the Requisite catalog to create a shopping cart

Your company has decided to use an internally hosted catalog as part of its catalog strategy. In this exercise, you will connect this catalog to the EBP system and practice searching for items.

A majority of these exercises are case sensitive.

1-1 Define a catalog in EBP with the Catalog ID REQUISITE, and catalog name Requisite Catalog.

Log on to YOUR CLIENT of the EBP System from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Master Data ? Define External Web Services (Catalogs, Vendor Lists etc.)

Select New Entries

Enter REQUISITE as Web Service ID.

Enter Requisite Catalog as Description of a Wed Service.

Choose Product Catalog as Business Type of Web Service.

Choose Enter.

Set the indicator

Do not Check Product.

Set the indicator

Display Prod. Data Again in Catalog

Set the indicator

Validate Product Data from SAP Enterprise Buyer

Set the indicator

Sourcing

Set the indicator

Maintain Error Log

Choose SRM_00_3## as Logical System.

Select Enter.

Double-click on

Standard Call Structure in the Dialog Structure (left side)

Choose New Entries.

The call structure is case sensitive.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Maintain following entries exactly as stated below:

SEQ. Nr

Name Parameter Values Type

10 http:// <get from your instructor>

URL

20 username guest Fixed value

30 password ides Fixed value

40 HOOK_URL Return URL

50 ~OkCode ADDI Fixed value

60 ~Target _top Fixed value

70 ~caller CTLG Fixed value

Select Save.

Choose Back (three times).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Define an Inframe Catalog in EBP with the Catalog ID REQUISITEII and catalog name Requisite Catalog Inframe.

Select the line REQUISITE.

Choose Copy As…

Enter REQUISITEII as Web Service ID.

Enter Requisite Integrated Catalog as Description of a Wed Service.

Select Copy.

Select Copy all.

Choose Continue.

Select the line REQUISITEII

Double-click on

Integrated Call Structure in the Dialog Structure (left side).

Choose New Entries.


Maintain following entries exactly as stated below:

SEQ. Nr

Name Parameter Values Type

10 http:// <get from your instructor>

URL

20 username guest Fixed value

30 password ides Fixed value

40 HOOK_URL Return URL

50 ~OkCode ADDI Fixed value

60 ~Target _top Fixed value

Choose Save.

Select Back (five times).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Assign the catalogs Requisite and Requisite Integrated Catalog to your organizational unit


Double-click on

Phoenix Enterprise Inc. (Root Organization)

from Organizational structure.

Go to Attributes tab page.

Maintain the following data for the attribute CAT (Catalog ID):

Choose REQUISITE as Value.

Select Continue and than choose Insert in the CAT line to add a second value for the attribute CAT.

Choose REQUISITEII as Value.

Select Save.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4 Create a shopping cart and search for items in the Requisite Catalog.


User ID: EMPLOYEE

Password: learn

Client : 3##


Choose Requisite Catalog.

Go to Quick Search tab page.

Enter Pens as Search text.

Choose Find.

Choose Ball Point Pens as Category.

Choose Ink Color in the list header.

Choose Blue as Ink Color from the list.

Choose OK.

Select Vendor Number in the list header.

Choose ARAMI-## as Vendor Number from the list.

Choose OK.

Select Add to the Shopping Cart.

Select Continue shopping.

Go to Product Index tab page.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Answering Machines as Category.

Select item of Vendor NONOCI.

Select Add to the Shopping Cart.

View the Open Catalog Interface Parameters.

Right-click on the template and choose View Source. Then scroll down to the OCI Parameters.

<input type="hidden" name="~Target" value = "_top">

<input type="hidden" name="~OkCode" value = "ADDI">

<input type="hidden" name="~caller" value = "CTLG">

<input type="hidden" name="HOOK_URL" value = "http://igtq2.wdf.sap.corp:1080/scripts/wgate/bbpsc0225ae0044/?~OkCode=ADDI&~Target=_top&~caller=CTLG">

<input type="hidden" name="user" value = "guest">

<input type = "hidden" name = "NEW_ITEM-DESCRIPTION[1]" value = "Single Cassette Answering Machine, White">

<input type = "hidden" name = "NEW_ITEM-MATGROUP[1]" value = "002">

<input type = "hidden" name = "NEW_ITEM-VENDORMAT[1]" value = "SWB90065">

<input type = "hidden" name = "NEW_ITEM-EXT_PRODUCT_ID[1]" value = "0a040f52-57289df:e5d51c0607:-6da8-1pl98t">

<input type = "hidden" name = "NEW_ITEM-UNIT[1]" value = "EA">

<input type = "hidden" name = "NEW_ITEM-QUANTITY[1]" value = "1.0">

<input type = "hidden" name = "NEW_ITEM-LONGTEXT_1:132[]" value = "Full-featured answering machine with beeperless remote, toll saver, variable message length, voice-activated control, message indicator, call screening, branch extension interrupt and one-touch message playback.">

<input type = "hidden" name = "NEW_ITEM-CURRENCY[1]" value = "USD">

<input type = "hidden" name = "NEW_ITEM-PRICE[1]" value = "34.95">

<input type = "hidden" name = "NEW_ITEM-VENDOR[1]" value = "NONOCI">

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Order Items.

Which message do you get? Why?

_____________________________________________________________

_____________________________________________________________

_____________________________________________________________

_____________________________________________________________

Select Detail. for the Answering Machine.

Expand Sources of Supply Area.

Choose Reset Vendor.

Choose Continue. in lower right corner.

Enter From REQUISITE as Name of Shopping Cart.

Select Order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 Check if the Inframe Catalog can be accessed.

Choose Shop in the launch pad.

Select Requisite Integrated Catalog.

Enter Alkaline Batteries as Search text.

Choose Start.

Select <Batteries from Vendor ARAMI-##>

Select Add to Shopping Cart.

Choose Continue in lower right corner.

Enter From REQUISITE Inframe as Name of Shopping Cart.

Select Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Add a View of the Catalog


? Add a view of the REQUISITE Catalog to your EBP system

Your company has decided that some users will only be able to see and select certain items in the catalog. In this exercise, you will add another catalog to your EBP system with a Requisite user that has a limited view. Remember, the views are defined in Requisite and assigned to a Requisite user. This Requisite user is assigned to the catalog call structure set up in EBP.

2-1 Create a new catalog entry in the EBP system using a catalog user that has been created for the SRM210 class.


Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-1 Copy the call structure for the REQUISITE catalog and change the user and password guest to user SRM210, password training.


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Master Data ? Define External Web Services (Catalogs, Vendor Lists etc.)


Select the line REQUISITE.

Select Copy As…

Enter REQUISITE-## as Web Service ID.

Enter Requisite Limited View Catalog

as Description of a Wed Service.

Choose Copy.

Select Copy all.

Select Continue.

Select the line REQUISITE-##.

Double-click on

Standard Call Structure in the Dialog Structure (left side)

Enter srm210 to replace the Username guest.

Enter training to replace the Password ides.

Choose Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-2 Assign the catalog REQUISITE-## to your organizational unit


Double-click on

Phoenix One from Organizational structure.


Maintain the additional value for the attribute CAT (Catalog ID):

Select Insert in the CAT line to add a third va lue for the attribute.

Choose REQUISITE-11 as Value

Select Save.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Create a shopping cart, search for items from your new catalog.


User ID: EMPLOYEE

Password: learn

Client : 3##


Select Requisite Limited View Catalog.

Go to Product Index tab page.

Verify the limited view of this catalog.

Choose Return to SAP at the top of the screen.

Log off.

2-3 OCI Parameters How does the catalog know that it has to deliver information to the Enterprise Buyer and what parameters to pass to Enterprise Buyer?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions


Topic: Define and Search a Catalog

2-3 OCI Parameters

How does the catalog know that it has to deliver information to the Enterprise Buyer and what parameters to pass to Enterprise Buyer?

The Open Catalog Interface describes the data exchange between the EBP system and external catalog applications.

When defining the Call Structure (the inbound structure of the Open Catalog Interface), the value ~OkCode with the content ADDI needs to be defined . This command is telling the catalog to add information to the Enterprise Buyer system.

Which parameters should be added is defined within the catalog itself. This is part of the OCI’s inbound structure. With the help of a Catalog Connector, you define the attribute mappings between for example, Requisite’s shopping cart and the EBP system. You need to map the attributes maintained in the catalog with OCI names that are pre-defined in the OCI specification (five OCI fields can be defined as customerspecific).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004



Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Self-Service Procurement: Business Scenario

? Now that all the settings have been made, the team members need to verify their customizing in their clients. They also wish to test local as well as backend procurement processes and the operational purchaser‘s role in processing incomplete purchase orders. Contracts will also be evaluated in this unit.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Self-Service Procurement: Unit Objectives

? Self-Service Procurement

? Shopping Cart

? Purchase Orders

? Confirmations

? Invoices

? Temporary Labor


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart: Process Flow

SHOPPING CART

NEED APPROVAL?

APPROVALWORKFLOWS

PURCHASE ORDER CONFIRMATIONLOCAL

PROCESS?DATA

COMPLETE?

YES YES YES

PURCHASER‘SWORKLIST

NO

IS IT A STOCK ITEM?

YESRESERVATION

NO

NO

REQUISITIONNO PURCHASE

ORDER

NO

DATA COMPLETE?

YES PURCHASE ORDER

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Example of an EBP Process I: Local Scenario

Backend-System

ACCOUNTING (FI/CO)PURCHASE

COInformation

Accounts Payable

Account Assignment

Check

? In Enterprise Buyer or

? In Backend or

? No check

Create Goods Receipt


Create Purchase Order

CreateInvoice

Enterprise Buyer

Order

? The customer does not have a productive MM system and wants to handle the entire process locally within the Enterprise Buyer, integrating only to an accounting system.

? Accounting processes (including FI, CO, and AM) must still be handled by a backend system. All validations and approvals are handled directly within Enterprise Buyer rather than in a backend system. This is possible by incorporating Material Management functions into the application which will have its own product master. Migration tools are provided to bring Material Master data from SAP backend systems into the application product master.

? A shopping cart or requirement coverage request (RCR) is created locally and can, depending on how the system has been configured, be further processed locally to create a purchase order. An added benefit is increased performance due to the fact that fewer RFC calls are necessary to the backend system.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Example of an EBP Process II: Classic Scenario

Backend-SystemEnterprise Buyer

Account Assignment

Check

? In Enterprise Buyer or

? In Backend or

? No check

ACCOUNTING (FI/CO)PURCHASE

COInformation

Accounts Payable

CreateInvoice

GR Document

Create Purchase

Requisition


Order



CreateInvoice


? You implement Enterprise Buyer and one or more Backend systems (SAP or Non-SAP). All Materials Management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entry sheets, and invoices) exist in the Backend system.

? When the shopping cart is ordered, a workflow is triggered that checks whether approval is necessary. • If it is required, a work item is sent to the Inbox of the relevant approver. • If it is not required, the necessary purchase requisitions, purchase orders or reservations are created

for the shopping cart. Which documents are created, and in which Backend system, depends on the information in the shopping cart and on the settings in Customizing for Enterprise Buyer.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart – Data sources

Internal Goods / Services (from EBP product master)

Old Purchase Orders and Templates

Description of requirement(text item)

Commodities and Services from electronic catalogs

? There are three possibilities for adding an item to a shopping cart: ? Catalog: the catalog is able to supply the product ID, product text, product category, price, vendor,

and other data. It can be displayed in a separate window or inframe. ? Product: the product represents either a material or a service master. They can be searched via

product description, product ID, product type or product category. ? Description of requirement: the user describes via text what he needs; he has to fill in a description,

unit of measurement, quantity, and product category

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart - Wizard

Enter product

Add items from catalog, product master ,old purchase orders , templates or free text

Shopping Cart overview

Complete and Order theshoping cart

Shop – BBPSC02

1

2

3

? The Wizard is the default navigation interface for employees. It helps employees to find, select, and add goods and services to their shopping carts quickly and easily.

? The user will be guided by the transaction through the three steps: ? Create an item from catalog, product master, old purchase order, and templates or via free text. ? Display the shopping cart overview from where the employee can go to the item details like cost

assignment, or source of supply.(If the user needs additional goods, he goes back to step 1, or if not, he goes on to step 3.) ? Complete and order, the user performs an approval preview, creates an approval note and orders or

holds the shopping cart.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart – Simplified Form

All options like

?Default settings for items,

?Additems,

? Item overview,

?Order or hold

are available on one screen

Shop – BBPSC03

? The transaction BBPSC03 in its simplified form is dedicated to professional users like purchasers or purchasing assistants who create shopping carts on a regular basis

? All information in this transaction displays on one screen. This includes detail information like source of supply, cost assignment and other data.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart – Extended Form

The user has the opportunity to work directly in the item overview

Shopping on behalf, limits and temporary labor are included also

Shop – BBPSC01

All options like

?Default settings for items,

?Additems,

? Item overview,

?Order or hold

are available on one screen

? The transaction BBPSC03 in its extended form is dedicated to the professional users like purchasers or purchasing assistants who create shopping carts on a regular basis

? All information in this transaction displays on a vertical screen. This includes detail information like source of supply, cost assignment and other data.

? An important advantage for the user is the opportunity to work directly in the item overview – similar to transaction ME51N in SAP R/3.

? Additional features of this transaction are functions for shop on behalf, items with limits, and items for temporary labor.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shopping Cart – Item Details

provides additional information

?Basic Data

?Account Assignment

?Documents & Attachments

?Ship to Adress / Performance Location

?Sources of Supply

?Availability

? When users select Item Details, they can access additional areas containing the following information: ? Basic Data, Account Assignment, Documents, Ship-To Address, Availability, Sources of Supply.

? In case of a Description, where no Source of Supply is automatically found, users can add a desired vendor on the Sources of Supply tab.

? The area Availability Check displays availability data depending on the plant maintained in PPOMA_BBP. EBP is capable of performing an availability check over several plants.

? After the shopping cart has been ordered, it is possible to display tracking information (for example, shipping notifications)

? You can use Customer fields to enhance standard structures, create your own data to display, or change and forward the contents of non-standardized fields.

? Your fields can be used in shopping carts, purchase orders, confirmations, invoices, and contracts at the header and item level, and for account assignment.

? Note that the contents of the Customer fields are not evaluated by the system and are only saved to the EBP database. If fixed values, search help or check tables are defined, the system automatically provides the (F4) input help.

? To be sure that the contents are passed from shopping cart to invoice, for example, you have to define the field in all documents (shopping cart, purchase order, confirmation, invoice.). Use exactly the same name and data type.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Direct Materials vs. Indirect Materials

? directly used in the production process

? mostly held on stock

Direct Materials

? MRO (maintenance, repair & operations)

? not an integral part of a product

Indirect Materials

Materials

? When you talk about electronic purchasing, it is important to define the difference between direct and indirect materials as the process and nature of integration of your procurement software is quite different.

? Direct materials are used directly in the production process and thus have influence on the value of the final good. This material is mostly held in stock and needs to be kept in inventory management. Indirect material, also known as MRO material, could be office supplies or machine parts, for example.

? In most cases, indirect material is characterized by high-volume and low-dollar transactions.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Self Service Procurement of Direct Material

Details

PressOrder as Direct Materialin the details

Recipient replaced by the plant Accounting data omitted

? Ordering a direct material means ordering a product that will be received into stock. You have to press the Order as Direct Material button in the item detail view.

? Selecting Order as Direct Material replaces the goods recipient with the plant you are ordering for and removes the Account Assignment information. The plants and storage locations are defined in the organizational structure in the extended attributes Locations and Storage Locations . After ordering the material as a direct material, you cannot change back to indirect; so, in case of a mistake you have to delete this item

? If you have a valid and definite source of supply, such as a contract, this will be used. Items without a source of supply will have to be completed by the purchaser in sourcing transaction or in the worklist of incomplete purchase orders. The complete purchase order will then be replicated to the back-end system. Changes to the purchase order is only possible in EBP, which is the leading system for this process. Any changes made in EBP are transferred to the back end.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Prerequisites for Direct Material

? set up transaction type and number ranges

? replicate plants (DNL_PLANT) from backends, ormaintain plants as business partner and maintain table CRMM_LOCMAP

? set up attribute Locations with the plant businesspartner number in the org. structure and maintainattribute DP_PROC_TY as transaction type for directmaterial po‘s

? replicate products from backends

EBP

R/3 Backend

? set up document type and number range for directmaterial purchase orders correspondend to the EBP system

? To use the direct material scenario, you have to ordering products that exist in the back-end system. Therefore, you need to replicate units, product categories, and material types and the necessary products from the back ends.

? In the next step, you have to ensure that your plant appears as business partner in EBP. The easiest way to do this is replicating them via middleware within the object DNL_PLANT. Another possibility is to create business partner data for you plants via transaction BP and map them in table CRMM_LOCMAP with your plants.

? The attribute requester in the org. structure is represented by the business partner number of your plants. ? To ensure that the documents can be transmitted to the back end, you have to maintain corresponding

transaction types, document types, and number ranges in EBP and respectively in the back end

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Confirm Service or Goods Receipt

Create confirmation

Create confirmationDisplay / process confirmation

Roles:?Employee: can only access their own purchase orders / confirmations

?Vendors: can only access their their own purchase orders / confirmations

?Central Goods Recipient: can manage all purchase orders / confirmations

Single entry screen for both goods and services (products)

With displaying a confirmation you can create a return delivery or a cancellation

? Both goods receipt and service entry are handled by one confirmation scenario. Since no distinction is made in EBP between materials and services, they are both referred to as products. There are two ways for employees or central goods recipients to save their confirmations: ? Hold - The confirmation is created in the EBP system. It can be completed at a later time. ? Confirm - A final confirmation screen appears that lists the items and quantities you have confirmed. The

approval workflow is now started. The manager of the employee who created the confirmation is responsible for approval.

? The workload for the confirmation is determined by the role of the user. Employees only can confirm goods or services that they ordered themselves or if they are the recipient of these goods/services. Vendors only can confirm purchase orders addressed to themselves, whereas central roles like the Central goods recipient (SAP_BBP_STAL_RECIPIENT) can perform confirmations for all purchase orders.

? Classic scenario: Automatically creates goods receipt in R/3 by passing an IDOC. Goods receipt can either be entered in R/3 or EBP. Local scenario: Purchase order and confirmation are entered and stored on the EBP component. Canceling a confirmation will roll back all corresponding business activities. When a confirmation is reset, it can be deleted. In the case of local confirmations, it can also be changed after reset. When a confirmation is reset, all corresponding workflow items are deleted.

? Restrictions on canceling: Only confirmations that have not yet been invoiced can be canceled. Only cancellation of all items included in the confirmation is allowed. Restrictions on deleting: Confirmations can be deleted by all user types if the document status is Held, Saved or In approval process. Confirmations can only be deleted when the document status is Approval reset. Return delivery: for back-end processes, a separate material movement document with movement type 122 will be posted; for local processes, a local return document will be posted.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? is transferred to Purchase Order and Shopping Cart

? is reset if the confirmation is deleted or cancelled

? is available for unplanned items (total limit is updated)

? is transferred to Backend for goods receipt and service entries

? is transferred to BW reporting

Delivery Complete Indicator

Delivery complete indicator...

? Previously (until EBP 3.0), it was only possible to manually set the delivery complete indicator (dci) in the PO. Now dci can also be set in the confirmation.

? Planned items: the delivery complete indicator can be manually checked in each confirmation item, either in the item list or in the details. After saving the confirmation, the information is passed to the PO and SC (not in status Held).

? Unplanned items: the delivery complete indicator can be checked in the confirmation item only for overall limits, not for partial limits. Once you have checked delivery complete , no further deliveries are possible for partial limits.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Confirmation - Possible Scenarios

Backend-System

Service entry sheet

Goods receipt

EBP System

Confirmation

Confirmation

Confirmation Confirmation

AP

PR

OV

AL

WO

RK

FL

OW

Backend service

purchase order item

Backend purchase

order(Material,

free text item)

Local purchase

order

IDoc

RFC

? Confirmations that refer to purchase orders for materials created in a back-end system: To make it possible for the confirmation documents to be transmitted to the back-end system via the ALE interface, you must have made the ALE settings in Customizing.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Invoice and Credit Memo

Invoice

Invoice

Credit MemoCreate with PO reference

Create with PO reference

Create w.out PO reference

Display / Process

Single entry screen for both invoice and credit memo

With displaying an invoice you can create a cancellation

Roles:?Employee: can only access their own purchase orders / invoices and memos

?Vendors: can only access their their own purchase orders / invoices and memos

?Accountant: can manage all purchase orders / invoices and memos

? Invoices (& Credit Memos) can be entered for the following transactions: ? Invoices are entered locally in the EBP without reference to a purchase order or delivery. In this case,

you must have defined the Financial Accounting (FI) component that is used in the vendor's user attributes and which company code is used for posting. ? Purchase orders have been created in the back-end system via the shopping cart scenario in EBP. ? Purchase orders and confirmations have been created locally in EBP.

? The purchase order history data is read from the system in which the purchase order was created. This can be an EBP system or R/3.

? When the invoice is posted and approved, or when the credit memo is posted, the payment information is transferred to the corresponding back-end systems that contain the components Financial Accounting (FI) and Controlling (CO). The Enterprise Buyer system can communicate with the one or more back-end systems. After the amounts have been checked and the accounts to be posted to have been determined, the following happens in the back-end system: ? Update accounting documents ? Update Controlling documents ? Commitments are reduced

? The workload for the invoices is determined by the role of the user. Employees only can confirm goods or services that they ordered or if they are the recipient of these goods/services. Vendors can only confirm purchase orders addressed to themselves, whereas central roles like the Accountant (SAP_BBP_STAL_ACCOUNTANT) can perform invoices for all purchase orders.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Tolerances for Invoice / Confirmation

TOG

Purchase OrderItem Description Quantity Price

1 Control Unit 10 each 555 USD

ConfirmationItem Description Quantity Price


? Quantity entered is greater than allowed

? Price too high

? Quantity entered is greater than allowed

InvoiceItem Description Quantity Price


TOGPPOMA_BBPAttribute: TOG

Message

Messages

? Using the attribute TOG, you can assign tolerance groups to organizational units. The tolerance group consists of tolerance keys with limits specified as value, percentage or day.

The following tolerance keys are used for confirmations (CF) and/or invoices (IV). ? DA Exceed cumulated value (value / percentage) Value or percentage definition for upper limit. Checks

the cumulated total invoice value (previous invoices and this invoice) against the total purchase order value.

? DQ Exceed amount: quantity variance (value / percentage) Value: quantity depending upon the price. A high quantity difference can be tolerated if the price is low. If the price is high only a small quantity difference will be tolerated. Percentage: Regardless of the price, the system calculates the percentage variance from the expected quantity and compares the result with the defined limit.

? LA Amount of limit purchase order (value / percentage). Tolerance key used for invoices only. Total value invoiced so far (including this invoice) compared to the value limit of the purchase order. Result is compared to defined limits.

? LD Limit purchase order, time limit exceeded (value) Compares invoice posting date with validity period. Difference to the first or last day of the validity period is checked against the defined upper limit.

? PP Value variance for single value (value / percentage). Checks the variance from the expected value, based on preceding documents (purchase order or confirmation value). Quantity x price is calculated per item and compared to the defined lower and upper limits.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Collective Invoice

now possible for purchaser orders as long as they have the same? vendor? invoice recipient (company code)? currency? backend system

the system checks all flagged purchase orders if they meet the requirements

if yes you can proceed and poste the invoice

if not you’ll get an error message

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Evaluated Receipt Settlement (ERS)

ACC DocArami-00

10 each control unit600 USD

__________6.000 USD

Backend

<SA38>

AutomatedSettlement flag in Business Partner Master for ERS

Purchase OrderItem Description Quantity Price


ConfirmationItem Description Quantity Price


BBPERS ? Printer

? Fax

? Email

Output Medium Credit Memo

? EBP automatically posts the invoice on the basis of the purchase order and the confirmation. ERS within EBP applies to local purchase orders and confirmations. Determines invoice amount for this ordering transaction from price entered on PO, terms of payment, tax information, and delivery quantity. ERS must be specified on the business partner master record.

? Purchase orders generated in a R/3 back-end system can be settled using the ERS functionality within R/3.

? ERS only recommended when you and your vendor have a clear agreement on the conditions.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Invoice / credit memos – Possible Scenarios

Backend-System

Accountingdocument

EBP System

Invoice /credit memo

Invoice /credit memo

AP

PR

OV

AL

WO

RK

FL

OW

Backend purchase

order

Local purchase

order

IDocInvoice /

credit memo

Accountingdocument

IDoc

LocalInvoice /

credit memodocument

? As soon as the invoice / credit memo for a back-end purchase order is posted in the Enterprise Buyer system, then the following occurs in the back-end system: ? An invoice / credit memo document is created in materials management and visible in the purchase

order history. ? An accounting document is written in Financial Accounting. ? A controlling document is written in the Controlling component.

? As soon as the invoice / credit memo for the local purchase order is posted in the Enterprise Buyer system, then the following occurs in the back-end system: ? The invoice / credit memo remains in the local EBP system. ? An accounting document is written in Financial Accounting. ? A controlling document is written in the Controlling component.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Status information & Express Confirmation / Invoice

Status shows the type of the follow on documents per item

Express Confirmation,Express Invoice

? As of EBP 4.0, the status overview shows the type of follow on documents created per item. The system displays the following status: Purchase order(s) created; Purchase order (incomplete); Purchase order confirmed; To be processed; Purchase requisition(s) created; Approved

? Express Confirmation and express invoice: ? Enter Confirmation: When you select this action, an Express Confirmation is created. The total order

quantity currently open is posted automatically. This scenario currently isn’t available for services or items with limits. ? Enter Invoice: When you select this action, an Express Invoice is created. The total confirmed

quantity currently open is automatically posted.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

The Purchaser Roles

Operational Purchaser

? Process and Issue Incomplete Purchase Orders

? Output Purchase Orders

? Process Bid Invitations ? Create Standard Templates

for Shopping Carts? Shop on behalf of someone? Process Shopping Carts with

Value Limit ? Display Contracts

? Analyze Purchase Orders ? Manage Business Partner Data

Strategic Purchaser

? Process Bid Invitations and Auctions

? Create Contracts

? Manage Business Partner Data? Compile Vendor Lists

The Purchaser can have two single roles: ? The Operational Purchaser is responsible for: ? Process Purchase Orders (find POs, process and check POs, transfer POs to vendor, PO’s header data,

item data) ? Output Purchase Orders (search PO, execute PO, process PO) ? Process Bid Invitations ? Analyze Purchase Orders (analyze local materials management, analyses of individual documents for

local materials management, bid invitations and bids, strategic procurement: analysis of vendors and purchases) ? Manage Business Partner Data (create, change and display company data on bidder, vendor, portal

provider or contact persons) ? Process Standard Shopping Carts (create, display) ? Display Contracts ? Shop on behalf of someone (if allowed via organizational structure)

? The Strategic Purchaser is responsible for: ? Creating Contracts, ? Compile Vendor Lists ? Manage Business Partner Data and Process Bid Invitation

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Incomplete Purchase Orders – Sources of Supply

Enterprise Buyer provides the following starting points for the sourcing proposal:

Processing Purchase Order?Sourcing Application is NOT

activated? Incomplete purchase order in

purchaser`s worklist

Vendor List?Assistance in the search

for a source of supply?Vendors and backend

contracts for products or product categories

Sourcing of Requirements?Process requirements

(local purchase orders, bid invitations and contracts)

?Provide information for decision-making when determining sources of supply

?Process of External Requirements

Operational

Strategic

? Enterprise Buyer provides the following starting points for the sourcing proposal: ? If in customizing the Sourcing Application is not activated, all incomplete purchase orders are sent to the

purchaser’s worklist as you know from previous EBP releases. ? There the purchaser can change the document and complete it to send it out to the vendor. ? Depending on the product category, it can define whether incomplete purchase orders will be handled in

the Sourcing Application of the purchasers. ? There the purchasers can make use of more information as for example: ? which back-end contracts exist ? whether this vendor is integrated into the vendor list ? other sources of supplies

? The Vendor List is the third starting point for the sourcing proposal. The Vendor List assists the purchaser in the search for a source of supply.

? Because the Sourcing Application and the Vendor List belong more to the strategic application, we will refer to it later in the course.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Processing Incomplete Purchase Orders

? Enter a Vendor? No price exists

Messages

Buyer add’s vendorand/or pricesand orders the purchase order

Buyer changes the purchase order

Status: Held = Incomplete Purchase Order

? Operational Purchasers have to complete local purchase orders in the Enterprise Buyer system. A purchase order is incomplete if no vendor exists, or a price is missing. In the header data, the Operational Purchasers can add a vendor or change a desired vendor. In the item area they can add or change prices and other data. They may add or delete items, too.

? If for a certain Product Category the Sourcing is not activated, the Operational Purchaser gets the incomplete purchase orders in the worklist when processing purchase orders.

? In their worklist, purchasers receive every incomplete purchase order for approved shopping carts of the employees, if their purchasing group is responsible.

? Some functions of the operational purchaser in the EBP: ? Display basic data, for example, purchasing organization and document date, change the purchasing

group, currency, or partner details (requester, goods recipient, vendor). ? Display and process purchase order texts or internal notes. If the purchase order is to be sent, then

only the purchase order texts are of importance, not the internal notes ? Maintain expected value and overall limit that the cost for unplanned goods/services may not exceed.

Display confirmed and calculated value. ? Choose a different communication medium, if required. The prerequisite being that the relevant fax, e-

mail, and XML data exist in the vendor master record. Using the function Preview, purchasers can display the purchase order once again, before output. Using the function Order and send immediately, purchasers can start the processing of actions for purchase order output.

? Display and define the follow-on documents.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Issuing the Purchase Order

Standard Output Customizing:

<SMARTFORMS>

? Printer

? Fax

? Email

? XML

Output Medium

One Output Action foreach purchaseorder

Several Output Action for each purchase order

TIME

Form

? Processing usingselection report

? Processing when savingdocument

Condition-dependent output

Detail and technical

data of thepurchase order

Output Action

? In EBP, the application purchase order output is available to purchasers for controlling the issue of the purchase orders (trigger management).

? You can define output settings in the vendor data. Detailed settings have to be done in customizing Set Output Action and Output Formats. Individual Output and Preview is possible directly in the purchase order.

? You can set up the following output media: ? Print ? E-mail ? Fax ? XML

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Version Management – Example: Purchase Order

Possible to activate forPurchase Orders and Contracts

if version control is activated the system logs not only the changes but creates a version of the document

existing versions can be compared

in this case the quantity and net value has changed

? SAP Enterprise Buyer provides you with version management for purchasing documents. As a first step, you can display versions of purchase orders and contracts .

? The system creates a version in the background if you, as a purchaser, carry out one of the following actions: ? You change a posted purchase order ? You order a posted purchase order again ? You change a contract that has already been released ? You release an already released contract again

? You cannot change or output versions. This is only possible for the active document ? Version control can be combined with the workflows for purchase order. For example, you define that if

accounting data has been changed or due to another change the total amount changed for more that 500 USD – a purchaser manager has to approve this.

? In contrast to the change documents that retain a change history, a version displays the status of a document at a specific point in time.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shop on behalf of

as of EBP 4.0 now part of transaction BBPSC01

? In the default settings you decide for which person you want to shop

? The attribute REQUESTER determines the persons or organization units you are allowed to shop for

? The system works as if the person you are ordering for is creating the shopping cart, only giving access to their data, routing to their manager for approval, etc.

Shop – BBPSC01

? As of Enterprise Buyer 3.0, secretaries and purchasers can buy products on behalf of other users, for example, their manager. With EBP 4.0 this functionality has moved into transaction BBPSC01. They do this by specifying the user for whom they want to place an order. If the user is unique, they can enter the Shop application directly as the user‘s representative by choosing the Continue button. If more than one user meets the entered criteria, secretaries or purchasers have to select the user from the displayed results before entering the Shop application.

? The users for whom secretaries or purchasers can shop, must be specified as values for the attribute REQUESTER in the organizational structure.

? The attribute values can be populated by either several users (USEMPLOYEE, USSMITH) or organizational units (O 50000###).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Shop with Value Limit

Goto Create Limit itemand enter Description, Value Limit, Expected Value and

The follow on documents depends on the Follow-Up-Actions (Invoice only or Confirmation and Invoice) and on the scenario (local or classic)

Shop – BBPSC01 as of EBP 4.0 now part of transaction BBPSC01

? Shopping with Value Limit is possible for local and back-end product categories. ? The amount of the expected value in the shopping cart with limit is used for the approval workflow. ? The follow-up actions determine if there will be an invoice only or a confirmation and an invoice. ? You can enter the Account Assignment in the Shopping Cart, the Confirmation or the Invoice unless the

follow-on documents are to be created in the ERP-System and then only invoices are expected. ? You can assign Local Contracts to Local Product Categories and Back-end Contracts to Back-end

Product Categories. ? As of Enterprise Buyer 3.5 it is possible to assign partial limits. A partial limit specifies that a certain

proportion of the overall limit is to be used for a particular material or service. You assign existing local or back-end contracts to this partial limit. This allows you to take advantage of special conditions that purchasers have negotiated with particular vendors.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Order Services and Temporary Labor

Goto Order temporay Labor and enter Description, Quantity, Price, Supplier & Service Provider

Shop – BBPSC01 part of transaction BBPSC01

? In the previous Enterprise Buyer releases, you could order simple services via EBP product master, free-text or limit items. Now, new SAP SRM functionality focuses on Temporary Labor & Consulting Services, with improvements to the shopping cart and a new time entry form for temporary labor.

? To support the procurement of temporary labor, Enterprise Buyer has a new easy-entry screen with service-specific fields in the extended form shopping cart. To enter your service request, you can use free-text entry or refer to product master data. The easy-entry screen offers service-specific fields for the service provider and performance period. You define the performance location on header level. You can also specify limit positions for expenses and overtime.

? The requester specifies a supplier and then selects a favored service provider that is an employee of this supplier. You can select a service provider that is already maintained as a partner in Enterprise Buyer, or you can select a special job description profile from the catalog. If there is no entry for the supplier, the incomplete purchase order is sent to the sourcing cockpit. The purchaser can enter the source of supply manually or through tendering.

? The limit pos itions within the shopping cart for temporary labor enable you to set a provision for unplanned services (expenses or overtime ) that are not precisely definable in amount or duration during the planning phase of a procurement project. This combines planned and unplanned positions that belong together in a single temporary labor shopping cart. Confirmations for services can be created and invoiced within a predefined limit. The type of service can be specified at the time of service entry. This guarantees cost monitoring.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Time Recording

Time recording is possible via the standard transactions for the confirmation of goods/services in relation to local orders for temporary labor

Confirm Goods / Services – BBPCF02 Enter Times

? As of EBP 4.0, you can maintain a time sheet for detailed service documentation. ? If you want to use default values, for example, the beginning and end of the working time, it is possible

to define them in customizing ? To further limit items, you can create a default button that provides you with text, product category, and

unit of measurement. This may help you to ease the effort of manual entries for processes on a regular basis.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Self-Service Procurement

? Shopping Cart

? Purchase Orders

? Confirmations

? Invoices

? Temporary Labor


Self-Service Procurement: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Self-Service Procurement

Topic: Create Shopping Carts


? Create shopping carts

? Check the status of shopping carts

? Approve Requirement Coverage Requests

? View the documents created on the R/3 back-end system and in the EBP system

Now that all of the settings have been made, you will create different shopping carts. You would like an Overhead Projector, a Palm V and a Casing. These items will be selected from a catalog or entered manually.

1-1 You will create a shopping cart that does require a one-step approval. The shopping cart will have three line items.

Line item one will be selected from the catalog and will create a back-end R/3 purchase order.

Line item two will be entered manually and will create a back-end purchase requisition.

Line item three will be a product that was replicated earlier and will create a reservation in the back-end R/3.


User ID: EMPLOYEE

Password: learn

Client : 3##

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Create a shopping cart and select the first item, an Overhead Projector, from the catalog.


Select BugsEye (own window).

Enter Projector as Search text.

Choose Find.

Select Vendor number link.

Select EBP-##.

Choose OK.

Choose Add to Shopping Cart to add to the shopping cart.

Select Order Items.

1-1-2 Add the second item, a Palm V, to the shopping cart:

Choose Step 1 Select Goods/Service

in area Shop in 3 Steps.

Select Describe Requirement.

Enter Palm V Organizer as Text.

Enter 1 as Quantity.

Choose Each as Unit of Measurement.

Enter 259 USD as Price.

Choose Electronics as Product Category.

Enter <today + 1 week> as Requested Delivery Date.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-3 Add the third item, a casing for electronic drives, to your shopping cart.

Choose Step 1 Select Goods/Service.


Select Internal Goods/Services.



1-1-4 Split the account assignment of the Overhead Projector between two cost centers. 75% of the line item will be charged to cost center 1000 and 25% of the item will be charged to cost center 4140.

Choose Details of the first item.

Select Cost Assignment Area.

Select Cost Distribution.

Enter 75 as Percentage (line 1).

Select Cost Center 1000 as Assigned to (line 1).

Enter 25 as Percentage (line 2).

Select Cost Center 4140 as Assigned to (line 2).

1-1-5 Enter the Purchase Order text for the Overhead Projector.

Expand Documents and Attachment Area.

Choose Vendor Text.

Verify that <the text coming from the catalog>

is inserted.

Choose Close Area to close the Item details.

You should now have three items in your shopping basket (Overhead Projector, Palm V and casing).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-6 Rename and order your shopping cart.

Choose Step 3 Complete and Order


Enter Cart 1 as Name of Shopping Cart.

Select Order.

What is the total value of the shopping cart?

____________________________________________________________

1-1-7 Check the status of the items in your shopping cart.

Choose Check Status in the launch pad.

What is the status of Cart 1?

Select Details in the shopping cart item.

Choose Approval Preview.

Who needs to approve the Shopping Cart?

For each item of the shopping cart, display the details.

Choose Details for each item.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 As Mary Manager, you have to approve the shopping chart created by your employee.


User ID: MANAGER

Password: learn

Client : 3##

In the Inbox on the main screen, you will find your workflow items.

Select Approval in the launch pad.

Choose Details for your shopping cart.

Check that all items are marked as approved.

Choose Save.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 After approval, record the documents that were created for each line item.


User ID: EMPLOYEE

Password: learn

Client : 3##

Check the Follow-On Documents for the three items in shopping cart Cart 1.


Select for Cart 1 to expand the item overview.

For each item, select to display the details and check the Follow-On Documents Area.

What type of document was created for the Overhead Projector?

Document type: ____________________________________

Document number: ____________________________________

What type of document was created for the Palm V?

Document type: ____________________________________

Document number: ____________________________________

What type of document was created for the Casing?

Document type: ____________________________________

Document number: ____________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


It may take a couple of minutes for the records to update.

1-4 View the documents created.

Log on to the BACK-END R/3 SYSTEM:

Client : 800

User ID: BACK-##

Password: learn

1-4-1 Find the Purchase Order that was created for the Overhead Projector to view the accounting details.

SAP menu ? Logistics ? Materials Management ? Purchasing ? Purchase Order ? Display

Choose Other purch. Order.

Enter <your purchase order number for the projector>

as Purchase order.

Select Other document.

Who is the Vendor?

Go to the Item Details to check the account assignment and the text of the purchase order item.

Go to Item Details.

Choose Account assignment tab page.

Was the accounting information transferred successfully?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Who is the recipient?

Select Texts tab page.

Was the PO Text transferred successfully?

Choose Back.

1-4-2 Find the Purchase Requisition that was created for the Palm V Organizer.

SAP menu ? Logistics ? Materials Management ? Purchasing ? Purchase Requisition ? Display

Select Other purch. Order.

Enter <your purchase requisition number for the Palm>

as Purchase Requisition.

Choose Other document.

What is the delivery date of the Palm?

Who is the Requester?

Choose Back.

1-4-3 Find the Reservation that was created for the Casing.

SAP menu ? Logistics ? Materials Management ? Inventory Management ? Reservation ? Display

Enter <your reservation number for the casing>

as Reservation.

Select Enter.

What is the movement type used for this material?

Who is the Goods Recipient?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5 Create a shopping cart for only local items.


User ID: EMPLOYEE

Password: learn

Client : 3##

1-5-1 Create a shopping cart with a special request and a local product.


Select Describe Requirement.

Enter Catalog Envelopes, 9x12, white, 500 each.

as Description .


Choose each as Unit of Measurement.

Enter 5 USD as Price.

Office Supply (L) as Category.

Choose Add to shopping cart.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Add a local product to your shopping cart by using MAT##, the Champagne you created before.

Choose Step 1 Select Goods/Service.



Enter LOCAL2 as Category ID.

Choose Start.

Choose MAT##.




Enter Cart 2 as Name of Shopping Cart.

Select Order.

What is the total value of the shopping cart?

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-5-2 Check the status of the items in your shopping cart and view the Follow-On Documents.


What is the status of Cart 2?

Select for Cart 2 to expand the item overview.

For each item , select to display the details and check the Follow-On Documents Area.

What type of document was created for the Catalog Envelopes?

Document type: ____________________________________

Document number: ____________________________________

What type of document was created for MAT##?

Document type: ____________________________________

Document number: ____________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Self Service Procurement

Topic: Direct Material


? Create a transaction type and corresponding number range for direct material purchase orders and define the transaction type as the value for the attribute DP_PROC_TY

? Populate the attribute Requester and the attribute DP_PROC_TY in the organizational plan

? Create a shopping cart containing direct material

Enterprise Buyer professional edition supports the end-to-end procurement of direct materials.

In this exercise, you will make the necessary settings for the manually triggered direct procurement process and test your settings via creating a shopping cart.

2-1 Customizing for the Direct Procurement process:


Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-1 For the Direct Procurement process, you need to define a new Transaction Type.


…? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Define Transaction Types

Choose New Entries.

Enter DP## as Trans. Type.

Enter Direct Procurement as Description.

Enter 04 as Int. No.

Choose with F4

BUS2201 Purchase Order.

as Doc. Description.

Choose Enter (twice) to confirm the message.

Select Save.


2-1-2 Maintain the number range 04 for the Transaction Type DP##.

…? Supplier Relationship Management ? SRM Serve r? Cross-Application Basic Settings ? Number Ranges ? Define Number Range for Local Purchase Orders

Choose Intervals.

Select Interval.

Enter 04 as No.

Enter 403##00000 as From number.

Enter 403##99999 as To number.

Select Insert.

Choose Save.

Choose Continue. to confirm the message.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-3 Check the corresponding Document Types and Number Ranges in the Back end.


Client : 800

User ID: BACK-##

Password: learn

Add SPRO to your favorites list and start the transaction.


SAP Customizing Implementation ? Materials Management ? Purchasing ? Purchase Order ? Define Document Types

Find your document type

DP## in the list.

Which is the external number assignment? ____________________

Select Back.

… ? Materials Management ? Purchasing ? Purchase Order ? Define Number Ranges

Select Intervals.

Find the number ## of your external number range in the list.

Check your number range

403##00000 to 403##99999

in the list.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-4 Define the transaction type as the value for the attribute DP_PROC_TY in PPOMA_BBP


Client : 3##

User ID: CONFIG

Password: learn


Double-click on Root Organization Phoenix Enterprises Inc.


Enter DP## as Value for the Attribute DP_PROC_TY.

Choose Continue.

Select Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Create a shopping cart, defining an item as “direct material”.

Log on to YOUR CLIENT of the EBPSYSTEM from the BROWSER:

User ID: EMPLOYEE

Password: learn

Client : 3##


Choose Internal Goods/Services.



Select Details in the Shopping cart item.

Expand Basic Data Area.

Choose Order as Direct Material button in the Basic data area.

Notice that the Account Assignment and the Availability information areas disappear.



Enter Direct Procurement as Name of Shopping Cart.

Select Order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Check the status of your newly created shopping cart and note the Document Number.


Choose your Shopping Cart

Direct Procurement.

Select Details in the Shopping cart item.

Go to Follow-On Documents Area.

What is the Purchase Order Number created? ________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Set up Operational BUYER Role

At the conc lusion of this exercise, you will be able to:

? Create a user with the buyer role

In this exercise, you will create a buyer who will process incomplete local purchase orders and handle contracts from within EBP.

3-1 As the Administrator, create a Professional Purchaser to handle the local incomplete purchase orders.

Log on to YOUR CLIENT of the EBP System from the BROWSER:

User ID: WEBADMIN

Password: learn

Client: 3##

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Select Create users.

Enter BUYEROP as User ID.

Select Ms. as Form of Address Text.

Enter Betty as First Name.

Buyer as Last Name

Select USA as Country

Enter BLDG1 as Building code

12 as Room number


661 5511 as Telephone number

661 5522 as Fax number

[email protected] as E-mail address


init as Repeat new Password

Click on Find and choose

<50000xxx> PUR Group Miller as Organizational unit.

Choose SAP_BBP_STAL_OPERAT_ PURCHASER

as Role.

Choose a <date format> you want

Choose Save.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Process Purchase Order


? Process an incomplete purchase order and shopping carts containing direct materials

The shopping cart Cart 2 created incomplete purchase orders. In this exercise, you will process these purchase orders and order them. At the next step, you will complete the purchase order with your direct material.

4-1 View the professional purchaser’s work list and process the incomplete purchase order from Cart 2 you created earlier.


User ID: BUYEROP

Password: init

Client : 3##


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Expand Purchase Orders in the launch pad.

Choose Process Purchase Orders in the launch pad.

Select purchase order number for the envelopes

from the work list.

Choose Change.

Select Check at the top of the screen.

What is missing?

4-1-1 Add the vendor McCoy-## to this order.

Select Find for the vendor field, to search

Enter MCCOY* as Business Partner.

Choose Go.

Select McCoy-##.

Select Check.

View the item details of this purchase order.

Choose Item Data tab page.

Enter 4.80 USD as Gross Price, to change the price

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


4-1-2 Add an additional item, printing paper, to the purchase order.

Enter Printing paper as Description for item 2.

Choose Search to choose the Product Category.

Enter Local1 as Category ID.

Select Go.

Select Office Supplies (L).


Choose PACK as UOM.

Enter 2 as Price per 1.

Enter <today + 1 week> as Required on.

Choose Cost center 1000 as Assigned to.

Choose Add Items at the end of the item overview.

4-1-3 Order the purchase order.

Choose Header Data tab page.

Select Output.

Choose Order and send immediately.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


4-1-4 View the operational buyer’s worklist and process the other incomplete purchase order you created earlier.

Choose Change for the second item of Cart 2 in the worklist.

Select Search for the Vendor.

Enter * as Business Partner.

Choose Go.

Select ARAMI-## as Vendor.


Enter 12 USD as Gross Price.

Select Check.

Choose Order.

4-2 Complete the shopping cart named “Direct Procurement”.

4-2-1 As the professional purchaser, you have to process the incomplete purchase order from the Direct Procurement shopping cart.

Expand Purchase Orders in the launch pad.

Choose Process Purchase Orders in the launch pad.

Select Worklist tab page.

Select your order

Direct Procurement with the number 403##00000

from the list.

What is the Transaction Type? ______________________________

Choose Change.

Enter EBP-## as Vendor.

Go to Item Data tab page.

Add 10 USD as Price .

Select Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


4-2-2 Check the status of your Direct Procurement shopping cart.

Log on to the EBP System via the BROWSER

User ID: EMPLOYEE

Password: learn

Client : 3##

Go to Check Status in the launch pad.

Select Direct Procurement in the Shopping Cart List.

Choose Details in the Shopping cart.

Who is the Goods Recipient? _________________________

Go to Follow-On Documents area

Note the Purchase Order No.: _________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


4-2-3 Check the status of the purchase order in the R/3 back end.


Client : 800

User ID: BACK-##

Password: learn

SAP Menu ? Logistics ? Materials Management ? Purchasing ? Purchase Order ? Change (ME22N)

Choose Other purch. order.

Enter 403##00000 as Purchase order.


Can you change the Purchase Order? Why?

_________________________________________________________

______________________________________________________________

______________________________________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Confirmations


? Perform confirmations as an employee

Edward Employee has received the ordered material at his desk. In this exercise, he will confirm some items.

5-1 Perform a confirmation for the purchase order associated with the Overhead Projector from Cart 1.


User ID: EMPLOYEE

Password: learn

Client : 3##

Select Confirm Goods / Services in the launch pad.

Select <PO 30083##***> for Cart 1.

Choose for <PO 30083##***>| to display the item with the Projector.

Choose Create Conformation.

Enter Conf 1 as Confirmation Name.

Enter ##01 as Reference Document.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Before you finish the confirmation, take a look at the account assignment of the Projector. What does “Multiple” mean, and what consequence would you expect?

_________________________________________________________________

_________________________________________________________________

Choose Confirm.

Select Back to initial screen.


Expand. to display the item.

Select Display history to check the status of the purchase order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


5-2 Check the back-end R/3 PO history of your purchase order.


Client : 800

User ID: BACK-##

Password: learn

Find the Purchase Order that was created for the Overhead Projector to view the accounting details.

SAP Menu ? Logistics ? Materials Management ? Purchasing ? Purchase Order ? Display

Choose Other purch. order if necessary.


as Pur.order.


Choose Purchase order history tab page in the item details.

Choose the number <50000****> of the Material Document

in the history.

Select Doc. info tab page in the Header data.

Select FI Documents.

Why is no subsequent document found in Accounting?

______________________________________________________________

______________________________________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


5-3 Perform a confirmation for the local purchase order(s)


User ID: EMPLOYEE

Password: learn

Client : 3##

The envelopes and ordered champagne arrived at the office of Edward Employee.

Confirm one of them.

Choose Confirm Goods / Services in the launch pad.

Select <one of the local PO from Cart 2>.

Choose Create Confirmation

Enter Conf 2 as Confirmation Name.

Enter ##02 as Reference Document.

Select Confirm

Choose Back to initial screen.


Expand to display the item.

Select Display history to check the status of the purchase order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises


Topic: Posting an Invoice


? Set Tolerance Check for Invo ice / Confirmation

? Enter an invoice for a purchase order

? Enter an Invoice without PO reference

In this exercise, you will enter an invoice for the Overhead Projector you ordered and confirmed earlier. You will also learn to define reasons for rejecting vendor invoices and work with the tolerance check.

6-1 Set Tolerance Check for Invoice / Confirmation.

Log on to the EBP from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Set Tolerance Checks

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select New Entries.

Enter 001 as Group.

Enter Tolerance Group 1 as Description.

Choose Enter.

Select Group 001.

Double-click on

Tolerance keys.

Choose New Entries.

Choose DA as Tolerance Key.

Select Enter.

Enter USD as Currency.

Enter 1000 as Upper limit in the area Absolute limit.

Enter 100 as Upper limit in the area Limit as percentage.

Select Save.


Select New Entries.

Choose DQ as Tolerance Key.

Select Enter.




Choose Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose New Entries.

Choose LA as Tolerance Key.

Select Enter.




Choose Save.

Select Back.

Select New Entries.

Choose LD as Tolerance Key.

Select Enter.

Enter 30 as Upper limit in Days.

Choose Save.

Select Back.

Select New Entries.

Choose PP as Tolerance Key.

Select Enter.


Enter 500 as Lower limit (absolute).

Enter 300 as Upper limit (absolute).

Enter 20 as Lower limit (percentage).

Enter 10 as Upper limit (percentage).

Select Save

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Back (four times).

6-2 Define Reasons for Rejecting Vendor Invoices

…? Supplier Relationship Management ? ? SRM Server ? Confirmation and Invoice Verification ? Define Reasons for Rejecting Vendor Invoices

Choose New Entries.

Enter 0001 as Reason (1).

Enter Quality as Text (1).


Enter Price Deviation as Text (2).


Enter Quantity Deviation as Text (3).

Select Save.


6-3 Maintain Tolerance Group in your organizational structure

Start transaction

PPOMA_BBP from your Favorites.

Select Phoenix Enterprise Inc. as Organizational unit.

Choose Attributes tab page.

Enter 001 (Tolerance Group 1) as Value for the attribute TOG.

Select Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


6-4 Enter an invoice for the Overhead Projector

either: 6-4-1. in the R/3 Back-end System with the transaction MIRO

or: 6-4-2. in the EBP System

For the following exercise you have to decide whether you want to post the invoice in R/3 or in the EBP System.

You only could perform one of the two exercises 6-4-1 or 6-4-2.

6-4-1 R/3 Back-end System Invoice Process

Log on to the R/3 BACK-END SYSTEM:

Client : 800

User ID: BACK-##

Password: learn

SAP menu ? Logistics ? Materials Management ? Logistics Invoice Verification ? Document Entry ? Enter Invoice

Enter <today> as Invoice date.

Enter INV10## as Reference.

Enter 499 USD as Amount /Currency.

Choose Purchase Order/Scheduling Agreement

on the tab page PO reference.

Enter <purchase order number for the Overhead Projector in Cart 1>

in the next field.

Select Enter.

Verify that Balance is 0,00

Choose Post.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Check the Invoice Document.

Choose Other invoice document.

Select Continue.

Choose Show PO structure.

View the Follow-on documents.

Choose Follow-on documents.

Double-click on

Accounting document.

What are the numbers of the G/L accounts?

_________________________________________________________

_________________________________________________________

Why are there two entries with the same G/L Account 400000?

_________________________________________________________

_________________________________________________________

Check the status of shopping cart Cart 1 in the EBP system.

What is the invoice number displayed in the Follow-on documents of your shopping cart item for the Overhead Projector?

_________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


6-4-2 EBP Invoice Process


User ID: EMPLOYEE

Password: learn

Client: 3##

Choose Enter Invoice / Credit Memo in the launch pad.

Select Invoice.

Choose Create with PO reference.

Select <purchase order no. for Cart 1>

to display the item.


Enter INV10## as Invoice Number (vendor).


Choose Check.

Choose Post.

What message do you receive after posting the invoice?

_________________________________________________________

_________________________________________________________

What is the Invoice Number?

_________________________________________________________

Choose OK.

Select Back to initial screen.

Choose Display History in the item line for the Projector.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


View the purchase order history in the R/3 Back-end System.

SAP menu ? Logistics ? Materials Management ? Purchasing ? Purchase Order ? Display

Choose Other purch. Order.


as Purchase order.

Choose Other document.

Select Purchase order history tab page in the item details.


_________________________________________________________

Log off from R/3.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


6-5 Enter an invoice for the local PO in the EBP system


User ID: EMPLOYEE

Password: learn

Client: 3##

Select Enter Invoice / Credit Memo in the launch pad.

Choose Invoice.

Choose Create with PO reference.

Select <local purchase order no. 10000000** for Cart 2>

to display the item.


Enter INV20## as Invoice Number (vendor).

Choose Calculate Total Amount.

If necessary choose

0% Tax as Tax for the item.

Select Check.

Choose Post.


_______________________________________________________________

_______________________________________________________________


_______________________________________________________________

Select OK.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


View the history of the shopping cart item.

Choose Back to initial screen.

Select Display History.

6-6 Optional: Create an invoice without reference to a purchase order. The invoice is for a birthday cake that the EBP-## vendor delivered earlier in the day.

Select Enter Invoice / Credit Memo in the launch pad.

Choose Invoice.

Choose Create w.out PO reference.


Choose Continue.

Enter INV30## as Invoice Number (vendor.)

Enter Birthday Cake as Description.

Enter 50 as Net Value.


Select EA (Each) as UoM.

Choose 0% Tax as Tax.


Choose Check.

Choose Post.


_________________________________________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


6-7 Optional: View the ALE IDocs that were used to transfer the invoicing information to the R/3 back-end system.


Client : 3##

User ID: CONFIG

Password: learn

Add the transaction WE05 to your favorites (Favorites ? Insert Transaction) and start the transaction.

Choose Execute.

Double-click on

BBPIV in the combined list.

What is the status of the IDoc that passed the invoice data to the back end?

Does this status mean that the invoice was posted?

________________________________________________________________

________________________________________________________________

6-8 Optional: View the ALE IDoc containing the invoice data that was transferred from the EBP System.

Log on to the BACK-END R/3 SYSTEM

Client : 800

User ID: BACK-##

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


SAP menu ? Tools ? Business Communication ? IDoc Basis ? Display IDoc

Choose Execute.

Double-click on

BBPIV in the combined list.

What is the status of the IDoc that passed the invoice data from the EBP system?

Does this status mean that the invoice was posted?

________________________________________________________________

________________________________________________________________


View the accounting document that was posted in the back-end system.

SAP menu ? Accounting ? Financial Accounting ? General Ledger ? Document ? Display

Choose Document list.

Enter 3000 as Company code.

Enter <today’s date> as Posting date.

Enter INV30## as Reference number.

Select Execute

Double-click on

<the document number>. to display the document.

Select Display document header.

What is the number of the Reference key?

_______________________________________________________________

What is the logical system?

_______________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises



Test your knowledge about the following topics:

? Create Shopping Carts

? Direct Material

? Process Purchase Order

? Confirmations

? Posting an Invoice

7-1 Shopping Cart:

In which cases are you not allowed to delete items in a shopping cart?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


7-2 Reviewer:

What rights does a Reviewer have when reviewing a Shopping Cart?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

7-3 Invoicing:

How can you prevent users from entering different prices or quantities when entering an invoice?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

7-4 Evaluated Receipt Settlement:

When do you use ERS?

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

________________________________________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solutions



7-1 Shopping Cart:

In which cases are you not allowed to delete items in a shopping cart?

You can delete items in your shopping cart as long as there is no goods receipt or invoice posted in the back-end system and the purchase requisition was created in the Back end and the “completed” indicator was set for it, or the purchase order was created with the “delivery completed” indicator.

7-2 Reviewer:

What rights does a reviewer have when reviewing a shopping cart?

The reviewer can display the shopping cart with all its information.

7-3 Invoicing:

How can you prevent users from entering different prices or quantities when entering an invoice?

To prevent this, you have to maintain a tolerance group with the corresponding tolerance keys that describe the reasons to reject differing entries in the invoice. This can be a value overrun, for example. Each key contains an absolute upper limit and an upper limit in percentage.

7-4 Evaluated Receipt Settlement:

When do you use ERS?

The Evaluated Receipt Settlement (ERS) is a procedure for settling confirmations automatically. You have an agreement with the vendor that they will not create an invoice for an ordering transaction. Instead, the system posts the invoice document automatically on the basis of the purchase order and the confirmation. Ordering transactions can be completed more quickly. You can automatically send the created invoice documents to the vendor.

Purchase orders created locally, and for which confirmations exist, can be settled in the Enterprise Buyer system with the report BBPERS.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sourcing


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sourcing: Business Scenario

? Your purchasing department recently decided to test the sourcing capabilities within EBP

? Your task is to set up the EBP system for sourcing and to test the possible scenarios

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sourcing: Unit Objectives

? Conditions and Contracts

? Sourcing

? Bidding Engine

? Vendor List


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sources of Supply

?Condition for a product and a vendor (interlinkage)

Contract for a product or a product category

Bid Invitation / Auction

? Condition for a product and a vendor: Within the Product Workbench or due to a content load, it is possible to maintain a net price for a product in relation to a vendor. This price can be used as source of supply in the shopping cart, the purchaser’s worklist and the sourcing transaction.

? Contract for a product or a product category: The contract contains a vendor, net prices and –optional- conditions for a product or a special product category. The contract often is used for a long-term source of supply.

? Bid Invitation / Reverse Auction: If there are no sources of supply or, if you are looking for new sources of supply, you can create a Bid Invitation or Auction in the Bidding Engine. Your business partners are able to submit their quotations within EBP. You can accept Bids and create Purchase Orders or Contracts.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Conditions

Vendor Price – price for a product and a vendor (interlinkage)

Valuation Price – price for product only, no vendor1

2

1

2

2

Scales

Relationship: Vendor

COMMPR01ProductWorkbench

? Conditions can be maintained manually, they can be uploaded via the product workbench, or uploaded from a back end

? All conditions in the product workbench are net prices. ? If there is a price for the material only, it can be used as valuation price for the workflow, for example,

but not for purchasing. ? If there are price and vendor data, the prices are vendor specific and can be used as a source of supply.

To enable these vendor conditions, it is necessary to maintain a vendor relationship for this product, the so called interlinkage. Otherwise, the system cannot find the condition.

? If the source of supply is unique, it can be determined by the system. If the price is not unique, the employee or purchaser can select the price manual. Within the system, contracts have a higher priority than an interlinkage.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Contracts

Status:

Target Quantity or Target Value

Released Quantity and Released ValueConditions and Scales

Header Data Item Data

I Status I Text I Output LogsBasic data

Contract type: Purchase contractValid from: 14.07.2002 to 31.12.2005Purchasing Organization: Local Purch. Org.Purchasing Group: PGRP Local MillerVendor: Aramingo-10Responsible employee: Buyer

Header Data Item Data

Item OverviewItem Item Cat. Product Product Cat. Target Qty Price Rel. Qty Rel. Val. Action

1 Normal 100-400 001 10000 16 USD 100 1600

Deactivate all Items for Sourcing Activate all Items for Sourcing

? Released / Locked

? Created

? Held

? Incomplete / Complete

? Purchase contracts are an enhanced sources of supply. Strategic purchasers can create purchase contracts in Enterprise Buyer professional edition. The Item Category defines the type of the item. The item can be a product (item category normal) or a product category only.

? You can enter a target quantity or a target value. (You normally enter either a target quantity or a target value, but not both) The release value and release quantity of the contract are updated when a release order is ordered. Target value and target quantity are available at item level only. A purchase order can only refer to a single contract. To be a valid source of supply the contract has to be released.

? Release quantity and value are kept up to date (available only at item level) ? Updated as soon as release order was ordered ? Info in detail for each purchase order available ? A workflow via a BW alert can be triggered when the target quantity or value is close to being reached

? On the item level, there are several condition types as relative and absolute discounts available. In addition, it is possible to define scales for the conditions. Plants can also be restricted in the item level.

? Contracts can be created via the Process Contracts transaction, the Sourcing transaction or the Bidding Engine.

? Contracts can be created via the Sourcing transaction locally or in the back-end system. Back-end contracts can be created using the BADI Determine Back-end System/Company Code in back-end systems with a release of 4.6B of higher.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Global Outline Agreements

SRM Global OutlineAgreements

BackendR/3

BackendR/3

BackendR/3

? Global Outline Agreements are distributed to thebackend systems.

? Operational contracts arecreated in the backend systems as a result of thedistribution.

? Releases are made againstthe operational contracts in the backend.

? Releases can be monitoredin EBP and BW

BW

Create and update Operational Contracts

Update call-offs

? Global outline agreements are new in EBP 4.0. See Note 646903 for more information. ? Global outline agreements have almost exactly the same functions available as with the purchasing

contract in EBP. ? Global outline agreements can be created via the transaction Process Global Outline Agreements or via

the Sourcing transaction (using a BADI). ? Distribution occurs in the background after the global outline agreement has been released. By means of

the distribution, operational purchase contracts arise in the back-end systems. EBP currently distributes global outline agreements only to SAP R/3 of release 4.6B or higher.

? The global outline agreement (for example, in Sourcing) is not the source of supply; the source of supply is represented by the operational contracts in the back-end systems that arise as a result of the distribution. Releases are only possible against the operational contracts.

? Prerequisites: ? Product and product category master date need to be harmonized over the back-end systems. ? Back-end purchasing organizations need to be maintained in PPOMA_BBP.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Price Determination

? Price Determination in EBP

Priorities

R/3 Backend

? Purchaser can always change prices or other data in a purchase order

? Manual price (only if field is open for input)

? Contract

? Catalog

? Price from product linkage or from product

? Priorities for price determination: Manual price (in the shopping cart only if no other price could be determined), Contract, Catalog, Interlinkages, Product. The purchasers always are able to change prices.

? Supply source determination is used to find applicable contracts and interlinkages. If you have products in your shopping cart referring to your back end, the system displays info records and back-end contracts as additional information, but without price.

? If the system cannot propose a source of supply, or if you want to have a different source, you can fill in a desired vendor.

? An employee orders a product but does not know a vendor. In that case, as soon as the purchaser adds a vendor to the purchase order, the system performs a new price determination and overwrites the price from the shopping cart.

? Pricing normally uses the Internet Pricing and Configurator (IPC) component. In the classic scenario, pricing can occur without IPC in certain circumstances. You can find more information in SAP Note 539720 (Simplified Pricing - classic scenario) including which BAdI implementations have to be activated or deactivated if you wish to implement this Pricing variant.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sourcing Hub Scenario

Sourcing Cockpit

SRM

Bidding Engine

Auction

Contract Manage-

ment

Open requirements

Purchase Orders,

Contracts

Firewall

Materials Manage-mentSystems

Enterprise Buyer Systems

Maintenance & Project Systems

Planning Systems

Spend Analysis, Vendor Scorecard, Supplier Directory

Process Steps1. Demand from R/3

backend or EBP is transferred to Sourcing

2. Requirements are processed either in Sourcing and/or Bidding Engine

3. Create PO or contract in either Local or Backend system.

Bidder

Bidder via SUS

Live Auction

? The Sourcing Hub is a central concept in SRM where open requirements from local and/or back-end systems are assigned sources of supply either in the Sourcing Application and/or via SAP Bidding Engine. The resulting document (purchase order or contract) resides either in the local or back-end system, depending on the scenario being used (classic, extended classic, or standalone).

? The Sourcing application integrates with the SAP Bidding Engine and SAP Business Warehouse. ? You can link vendor directories from commercial providers with SAP Enterprise Buyer via the Open

Partner Interface (OPI) and transfer partner data as sources of supply.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

?Bidding Engine

?Vendor directories (OPI)

?Public marketplaces

?Vendor List (VL)

?Contracts

?Business Warehouse Information

?Catalog, Product Master

?Vendor Master Data

Create requirementsvia shopping cart orexternal system

Transferrequirementsto sourcingcockpit

‘Sourcing Cockpit’

WorklistInternal and externalrequirements

Create P.O.

Create Contract

Create Bid Invitation

Create Auction

Operational Purchaser’s View

? The Operational Purchaser is responsible for processing requirements in the Sourcing application. ? You can process requirements with the local, classic or extended classic scenario. ? The requirements initially appear on the purchaser’s worklist. Only those requirements for which the

purchasing group of the logged on user is responsible will appear on the worklist. The purchaser can use the Find option to locate other requirements that were not routed to their worklist for which other purchasing groups have responsibility.

? Requirements can be sorted and then added to the Work Area. ? In the Work Area, requirements can be individually or collectively processed using these options: ? Propose Sources of Supply ? Create Purchase Order ? Create Bid Invitation (Bidding Engine) ? Create Contract ? Create Auction (Bidding Engine) ? Hold ? Remove from Work Area

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Propose Sources of Supply – Create Purchase Order –Create Bid Invitation – Create Contract – Create Auction

Worklist of Requirements

Work Area sourcing method options:

Sourcing Application

? The requirement number in the Work Area in the case of requirement for shopping carts is the shopping cart number/shopping cart item number. External requirements also use the shopping cart number range, however in the History of the requirement you can see, for example, the Purchase Requisition number from a back-end system that created the requirement.

? Once you create a purchase order or a contract for a requirement it no longer appears in Sourcing. If you create a Bid Invitation via the Bidding Engine, the requirement remains in Sourcing with a hyperlink to the Bid Invitation. Once a Bid has been accepted and a Purchase Order or Contract is created for the Bid, it will no longer appears in Sourcing.

? The purchaser can change requirements that have been created from shopping carts, but cannot add any new items. The system does not start new approval workflows for requirements that have been changed.

? You can only display external requirements and assign a source of supply to them.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Sourcing - customizing

? Sourcing Never Carried Out

? Sourcing Always Carried Out

? Sourcing Carried Out for Items without Source of Supply

? Auto creation of Bid Invitations for Items without Source of Supply

Sourcingvia Vendor List

SourcingBy product category

? If Sourcing for Product Categories is not configured, the system creates purchase orders in the local scenario for all requirements; these are incomplete if the source of supply is missing.

? Sourcing is never carried out: This is the default setting. Enterprise Buyer does not transfer any items to the purchaser's sourcing application - independent of the status of the shopping cart.

? Sourcing is always carried out: Enterprise Buyer transfers each item to Sourcing - independent of the status of the shopping cart.

? Sourcing is carried out for items without a source of supply: Enterprise Buyer transfers all requirements that have multiple sources of supply of which none is assigned, to Sourcing. Once you select a source of supply in the shopping cart, the item does not go to Sourcing.

? Automatic bid invitation for items without a source of supply: Enterprise Buyer creates a bid invitation for all requirements that do not have any source of supply.

? Enterprise Buyer evaluates the Sourcing Customizing after the approval of a shopping cart and notes in the shopping carts whether they should undergo sourcing or not.

? If you require additional control options, for example, the facility to control processing at product level, you can use the following BAdI: Define Execution of Sourcing.

? Define Sourcing via Vendor List only: With this set, only sources maintained in the Vendor List will be available in the shop transactions. The purchaser can assign any sources to a requirement or P.O., regardless of this setting. This restricts sources of supply available to the requisitioner, not the purchaser.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Bidding Engine: Bid Invitation

Create Dynamic Attributes in Header

and/or Item Data

Publish – Hold – Set to Ready

? Purchasers can create either Public or Restricted bid invitations in the Bidding Engine. ? Public Bid Invitation: Made available on the Web and published on a portal. For example, bidders can

access the bid invitation through a hyperlink and enter the bids in the purchaser’s Bidding Engine system.

? Restricted Bid Invitation: These are made accessible only to known bidders through e-mail. Bidders can access the bid invitation through the hyperlink provided in the e-mail.

? Dynamic Attributes are specific characteristics of products and services that can be incorporated into the bidding process in the Bidding Engine. They are used to customize bid invitations and appear as additional fields requesting specific information.

? Dynamic Attributes can be created and used for a specific bid invitation or made available to all bid invitations.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Bidding Engine: Submit Bids

Register – Change Bid – Delete Bid

? Bidders access the Bidding Engine by choosing Submit Bid from the menu. ? On the initial screen, the bidder can search for a new bid invitation or auction and create a bid, or search

for bids they have already created. ? Bidders can download bid Invitations to Microsoft Excel. ? Bids can be Held so that changes will be saved and they can be processed later before submitting them. ? Submitted bids are binding. The purchaser who created the bid invitation sees that bids have been

received and can display them once the opening date has passed.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Bidding Engine: Live Auction Process

Bidding EngineBidding Engine

Bid InvitationBid Invitation AuctionAuction

Live Auction Cockpit for monitoring and bidding

Create

Convert

? Auction created and maintained in Bidding Engine

? Create from Bid Invitation

? Create manually

? Create from sourcing

? Price as determinating factor

? Rule driven and interactive:

? Bid decrements

? Real time ranking of bids

? Real time graphs

? Chat capabilities

? Automatic and manual extension of aution

SourcingSourcing

Transfer

Live Auction CockpitLive Auction Cockpit

? Purchasers can use the Bidding Engine to create live auctions for products and services. The live auction itself takes place in a Java applet.

? You can create a live auction: ? Manually, as an initial step in the Bidding Engine. In this case, the resulting purchase order from the

auction can only be saved locally. ? By converting a bid invitation to a live auction: If you convert a bid invitation to an auction, any

attributes, bids that have already been submitted will not be transferred. Bid invitations for which the detailed price indicator has been set cannot be converted to a live auction. ? From the Sourcing transaction: If you create an auction from the sourcing transaction, you cannot add

new items. Any purchase orders created can be saved locally or in the back-end system.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Bidding Engine: Live Auction Roles

Purchaser: Bidders:Bidding Engine:?Search?View auction details?Supplier Portal / SUS

integration

Live Auction:?Monitoring

?My bid? Rank? Leading bid? Countdown timer

?Chat?View graphs?Submit bids

Bidding Engine:? Create Auction? Copy, Search and Modify? Status change? Error checklist

Live Auction: ? Monitoring

? Best (leading bid)? Countdown timer? View all bids? View graphs? Chat and alerts? User list and logon status

? Broadcast chat messages

? Both purchasers and bidders can monitor the auction and bidding activity in real time. ? Real-time charts and graphs provide a visual representation of the auction data. ? The chat function provides instant messaging capability. ? Live auctions are started, ended, and extended automatically according to the time parameters set by the

purchaser when creating the auction. ? The connection status of each invited bidder is indicated in the applet for the purchaser. For the bidder,

the indicator refers to the connection status of the purchaser. ? A bid calculator provides bidders with an overall total bid price before they submit their bids.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Purchaser: Auction Item Details (Default)

“Details” selected

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Bidder: Auction Item Details (Default)

“Details” selected

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Vendor List

? Which Supplier can deliver products or commodities from a specific product category?

? Who are my favorite vendors ?

? Which supplier must not be used for specific products or product categories ?

? How can I prevent using unauthorized vendors in a shopping cart?

Vendor List(VL)

? Users can use a vendor list when they search for sources of supply for their purchases. ? Purchasers can compile vendor lists on the basis of vendor evaluations, vendor master data and

contracts. ? Vendor lists can be created for products or for product categories. The lists can contain back-end

contracts. ? Using hierarchically assigned product categories (for example eCl@ss or UNSPSC), you can create a

vendor list for a subtree of a product category hierarchy. This vendor list is valid for several product categories.

? The Vendor list is integrated into all applications that contain a vendor search help and in which you can display sources of supply such as: ? Shop and Shop with Value Limit: You can specify that only vendors maintained in the vendor list can

be selected or just have them highlighted in the sources of supply overview. ? Sourcing: A purchaser can which vendors are maintained in the vendor list when assigning a source,

but is not limited to these. If the Open Partner Interface (OPI) is connected, sourcing can be extended to cover external vendor lists. ? Bidding Engine: You can search for Bidders via a vendor list.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Vendor List - Creation

Create for Productor for

Product Category

? The vendor list contains the preferred vendors for products or product categories. Each entry of the vendor list can be marked as active or inactive. This enables you to define your favorite or sources of supply that are temporarily not suggested.

? When maintaining the vendor list, you will see a proposal of possible sources of supply from the system, but prices are not displayed.

? It is possible to refer to back-end contracts but there is no search help for the contract number, it has to be typed in manually. There is no validation on back-end contracts. Local contracts are not supported in the VL at this time.

? In Sourcing, you can see all sources of supply coming from the vendor list marked with a special flag. ? If the system finds an entry for a product, it overwrites an entry for the product category, which is less

specific. ? The Edit Documents button displays the generic screen for adding Internal Notes and Attachments. ? If you defined vendor lists, you can search for them by purchasing organization, product category,

product, description, vendor, status, time frame, and those you created.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Vendor List & Open Partner Interface (OPI)

Opportunity to search for vendors in an external list and to transfer them to EBP

? The Open Partner Interface (OPI) allows you to search for possible Business Partners in external vendor catalogs, for example, the German Hoppenstedt vendor list

? It is possible to transfer matching vendors as business partners to the BEP system and use them for procurement or bidding processes.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Vendor List – Shopping Cart and Sourcing

Vendor List for MATLOCAL1 with two activeitems

Shopping Cart with MATLOCAL1

Sourcesof Supply

Overview Sources of Supply within the SourcingTransaction

Shopping cart

Sourcing

? In both the shopping cart and the sourcing transaction, you can see whether a source of supply is maintained in the vendor list.

? Depending on the customizing, all sources of supply not maintained in the vendor list will become invisible.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Conditions and Contracts

? Sourcing

? Bidding Engine

? Vendor List

You are now able to use and set up:

Sourcing: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Sourcing

Topic: Contracts and Pricing


? Define a price for a product master (product price)

? View the product price in a shopping cart

? Create a local contract (Purchase Contract Material)

? Choose the contract as a source of supply in a shopping cart

In this exercise, you will enter a price for a product master (product price) you have created local in EBP. You will also create a contract for your local material. The resultant local contract release order updates the release documentation for the contract.

1-1 Maintain a product price in the product workbench.


Client : 3##

User ID: CONFIG

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


User menu for CONFIG ? Master Data ? Product ? Product Workbench (COMMPR01)

Choose Search tab page.

Enter MAT## as ID / Description.

Select Start.

Double-click on

MAT## in the list.

Select Conditions tab page.

Choose Purchasing as Conditions For.

Maintain a price without reference to a vendor:

Choose 01PV as Condition Type

Choose Product as Key Combination

Enter 65 as Amount

Choose USD as Currency

Maintain a price with reference to the vendor EBP-##:

Choose 01PV as C Type.

Choose Vendor/Product as Key Combination.


Enter 60 as Amount.

Choose USD as Currency.

Select Continue.

Choose Relationships.

Go to Vendor tab page.

Enter EBP-## as Business Partner.

Select Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 As the Administrator, create a Strategic Purchaser to maintain contracts.


User ID: WEBADMIN

Password: learn

Client : 3##




BUYERST as User ID

Mr. as Form of Address

Billy as First Name

Buyer as Last Name

USA as Country


12 as Room Number




[email protected]

as E-mail Address



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose (Click on Find)

<50000*** PUR Group Miller>

as Organizational Unit.

SAP_BBP_STAL_ STRAT_PURCHASER

as User Role.

Select Save.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-3 Log on as Strategic Buyer and create a shopping cart for MAT##.


User ID: BUYERST

Password: init

Client : 3##

Change the Password to learn.



Enter MAT## as Product ID.

Choose Start.

Select MAT## in the Search Result.


What is the price of the item? _________________________________

Choose Details in the item line.


What is the source of supply for the item? _______________________

Choose Continue > button in lower right corner.

Enter Price as Name of Shopping Cart.

Choose Order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-4 Create a Contract in the EBP system for your local product.


Contract Management to expand this node in the launch pad.

Choose Process Contracts in the launch pad.

Choose Purchase Contract as Contract Type.

Select Create.

Choose USD as Currency.

Enter <today> as Valid From.

Enter <today + 15 months> as To.

Enter McCoy-## as Vendor.


Enter MAT## as Product.

Enter 1000 as Target Quantity.

Enter 60 as Price.

Select Conditions in the item line.

Choose Discount (Percent.) as an additional condition.

Enter 5 (%) as Amount.

Select Create Scales.

Enter the two additional scale levels

50 as Fr.

10 (%) as Amount

100 as Fr.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


15 (%) as Amount

Choose Check.

Select Release.

What is the contract number? __________________________________

1-5 Verify that the contract displays as a source of supply.




Choose Start.

Select MAT## in Search Result.

Choose Add to shopping cart.


Expand Sources of Supply area.

Is there an assigned source? _________________________________

Add a second item for MAT## with 50 pieces and a third with 100 pieces and verify the prices concerning your contract data.

Select Continue > button in lower right corner.

Enter Contract-Price as Name of Shopping Cart.

Choose Order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-6 Assume the role of the DIRECTOR and approve your shopping cart Contract-Price.


User ID: DIRECTOR

Password: learn

Client : 3##

Find your shopping cart in the inbox of the director and approve it.

Choose Approval in the launch pad.

Select Approve in the line of your shopping cart.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-7 Display the contract release statistics.


User ID: BUYERST

Password: learn

Client : 3##

Choose Process Contracts in the launch pad.

Select Extended Search link.

Enter MAT## as Product .

Choose Start.

Select <your contract 44000000**> in the Search Result.


Flag Display Release Quantity and Release Value.

Choose Details.

Select Releases to display detailed release info.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-8 Maintain another contract for MAT##. This time, choose vendor ARAMI-## and maintain a price of 53 USD.

Select Process Contracts in the launch pad.

Choose Purchase Contract as Contract Type.

Select Create.

Choose USD (American Dollar) as Currency.

Enter <today> as Valid From .

Enter <today + 6 months> as To.

Enter ARAMI-## as Vendor.

Select Item Data tab page.


Enter 1000 as Target Quantity.

Enter 53 as Price.

Choose Check.

Select Release.

What is the contract number? __________________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-9 Order the product MAT## again.




Choose Start.

Select MAT## in Search Result.

Select Add to shopping cart.



How many sources of supply are listed? ________________________

Is there an assigned source? __________________________________

Do not manually assign a source of supply. This item will be processed in sourcing


Enter Without Source of Supply as Name of Shopping Cart.

Select Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Sourcing

Topic: Sourcing


? Set up the sourcing customizing

? Work with the sourcing transaction

In this exercise, you first activate the sourcing functionality for the product categories LOCAL2 and 003.

You will create a shopping cart with several items and process them via the sourcing transaction.

2-1 Setup Sourcing for product categories LOCAL2 and 003.

Log on to YOUR CLIENT of the EBP system from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Sourcing ? Define Interactive Sourcing for Product Categories

Select New Entries.

Choose with F4

LOCAL2 (Food & Beverage (L))

as Category ID.

Choose Sourcing Always Carried Out as Sourcing.

Choose with F4

003 (Bulbs) as Category ID.

Choose Sourcing Carried Out for Items Without Assd Source of Supply

as Sourcing.

Choose Save.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Order a shopping cart with three items that will create requirements in the sourcing transaction.


User ID: BUYEROP

Password: learn

Client : 3##

Choose Shop.

Enter the following data in the area Items in Shopping Cart.

Item 1

MAT## as Goods / Service

<today + 1 week> as Required on

1 as Quantity

Item 2

Halogen bulb 150W as Description

Choose 003 (Bulbs) as Category


100 as Quantity

Choose EA (Each) as UOM

3 as Price / Limit

Item 3

Standard bulb 60W as Description

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose 003 (Bulbs) as Category


24 as Quantity

Choose EA (Each) as UOM

1 as Price / Limit

Choose Check.

Enter For Sourcing As. Name of Shopping Cart

Select Order.

2-3 Process your shopping cart items within the sourcing transaction.


Sourcing to expand this node in the launch pad.

Choose Carry Out Sourcing in the launch pad.

Select Champagne Albert Le Brun in the Overview of Requirements.

Choose Add to Work Area.

Choose Propose Sources of Supply.

Select <all Sources of Supply> in the Overview.

Choose Compare Prices.

Select <the cheapest contract> as Assigned Source of Supply.

Select Copy Changes and Back.

Choose Create Purchase Order (twice).

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


You should get a success message that a purchase order was created. This is a local purchase order that only exists in EBP.

Log off.

2-4 Create an Operational Purchaser who can process classic requirements with back-end product categories.


User ID: WEBADMIN

Password: learn

Client : 3##




R3BUYER as User ID

Ms. as Form of Address

Bonnie as First Name

Buyer as Last Name

USA as Country


12 as Room Number



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



[email protected]

as E-mail Address



Choose (Click on Find)

<50000*** PUR Group Davis>

as Organizational Unit

SAP_BBP_STAL_ OPERAT_PURCHASER

as User Role

Choose Save.

Log off.

2-5 Log on as the Operational Buyer R3BUYER and process the requirements with a back-end product category. You will create a purchase order for one and a bid invitation for the other.


User ID: R3BUYER

Password: init

Client : 3##





Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Standard bulb 60W in the Overview of Requirements.


Enter MCCOY-## as Vendor.

Enter 2 as Price.

Select Create Purchase Order (twice).

You should get a success message that a purchase order was created. This P.O. exists only in the back-end system.

Select Halogen bulb 150 W in the Overview of Requirements


Select Create Bid Invitation (twice),

You should get a success message that a bid invitation was created. Notice the reference to the Bid Invitation in the worklist.

Select Process Bid Invitations in the launch pad.

Choose Today as Processed Since.

Choose Start.

Choose <your Bid Invitation 81000000**>

in the Search Result.

Select Change.

Enter <today + 1 week> as Submission Deadline.

Choose Partner/Bids.

Enter MCCOY-## as Bidder.

Choose Add Bidder.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Enter ARAMI-## as Bidder.

Select Add Bidder.

Select Check.

Select Publish.

Choose OK to confirm the message.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-6 Log on as the contacts of the bidders assigned to the bid invitation and submit bids.


User ID: ARAMI

Password: init

Client : 3##


Choose Submit bid to in the launch pad.

Choose Current Bid Invitations as Status.

Select Start.



Select Create Bid.

Enter 4 as Price.

Select Submit Bid.

Log off.


User ID: MCCOY

Password: learn

Client : 3##

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Submit bid to in the launch pad.

Choose Current Bid Invitations as Status.

Choose Start.



Select Create Bid.

Enter 3 as Price.

Select Submit bid.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-7 Log on as the Operational Buyer and process the bids that have been received in response to your bid invitation. Accept the bid from MCCOY-## and create a purchase order. Reject the bid from ARAMI-##.


User ID: R3BUYER

Password: learn

Client : 3##



Choose Process Bid Invitations in the launch pad.

Choose Published as Status.

Select Start.



Select Partner/Bids.

Reject the bid from ARAMI-##:

Select Check Bid for the bid from ARAMI-##.

Choose Change.

Choose Reject.

Select Back to Bid Invitation.

Accept the bid from MCCOY-## and create a purchase order.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Choose Check Bid for the bid from MCCOY-##.

Choose Change.

Select Accept.

Choose Back to Bid Invitation.

Choose Check Bid for the bid from MCCOY-## again.

Select Create Purchase Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Sourcing

Topic: Vendor List


? Set up the customizing for the Vendor List (VL)

? Use the Vendor List within Sourcing and Shopping Cart

In this exercise, you first set up the Vendor List functionality in the IMG. In the next step, you maintain a vendor list with a preferred and a forbidden vendor.

3-1 Setup the Vendor List (VL) Customizing


Client : 3##

User ID: CONFIG

Password: learn


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Number Ranges ? Define Number Ranges for Vendor List

Choose Intervals to change the intervals.

Choose Interval to insert a new interval.

Enter 01 as the No.



Select Insert.

Select Save.


Confirm every messages regarding transport of number range intervals with Enter.

3-2 Verify that the transaction type VL exists for your vendor list

SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Cross-Application Basic Settings ? Define Transaction Types

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-3 Maintain your Vendor List for the product MAT##.


User ID: BUYERST

Password: learn

Client : 3##


Business Partner to expand this node in the launch pad

Select Process Vendor List in the launch pad.

Choose PUR Local Processing as Purchasing Organization.


Choose Create.

Enter MCCOY-## as Vendor.

Enter ARAMI-## as Vendor.

Choose Refresh.

Set Indicator Inactv. for ARAMI-##.

At this moment, you do not want to order from ARAMI-## due to quality problems.

Choose Release.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-4 Create a Shopping Cart for MAT##.




Select Start.

Choose MAT## in Search Result.

Select Add to shopping cart.

Select Details in the item line.


How many sources of supply are listed? ________________________

Are there sources flagged as contained in the vendor list? __________

Is there an assigned source? __________________________________


Enter Vendor List as Name of Shopping Cart

Choose Order.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3-5 Complete the Shopping Cart via the Sourcing transaction


User ID: BUYEROP

Password: learn

Client: 3##




Select Champagne Albert Le Brun in the Overview of Requirements.


Choose Propose Sources of Supply.

Select <all Sources of Supply> in the Overview.

Select Compare Prices.

Can you find your contract with the active source on the Vendor List (VL)?

Select <the contract from the VL> as Assigned Source of Supply.

Choose Copy Changes and Back.

Choose Create Purchase Order (twice).

You should get a success message that a purchase order was created.

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004



Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? You want to deal within EBP with backend purchase requisitions resulting out of MRP, Project Systems or Plaint Maintenace

? Our project team is responsible for configuring the EBP and the R/3 backend system, to ensure that specific purchase requisitions can be transferred to EBP and processed further via the sourcing transaction.

Plan Driven Procurement: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Plan Driven Procurement

? Necessary customizing steps


Plan Driving Procurement: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Plan Driven Procurement - Overview

1

?Payment sent

?Accounting updatedin FI backend

72

APO

ERP

?Requisitions by planning run

?Results transferred

ERP

8

3b

4

5

6

?Issue order ?Assign

source of supply

?Goods receipt

?Invoice

XML

XML

PDF

FAX

XML

3a

Bid Invitationor Live Auction

ERP

EBP

? 1. The planning in APO or MRP in an ERP system calculates the amount and type of required materials. These requirements can be transferred to the EBP system. Requisitions from SAP Plant Maintenance or Project System are also possible requirements.

? 2. The requisitions are passed to EBP. If the data is complete and unique, purchase orders can be created automatically. If data is missing, the professional purchaser has to complete the missing information in Sourcing or via Process Purchase Orders. Customizing determines the route. Note: The sourcing transaction is currently not supported with APO Processes in this case you have to deal with classic purchase order transaction.

? 3a. An option for the professional buyer is to assign unsourced POs to an RFQ and send out for bids. ? 3b. The professional purchaser completes orders: assigns a source of supply, adds items or deletes

items. ? 4. Once complete, the order is issued manually by the professional purchaser or automatically by a

scheduled program. XML is the up and coming medium since the data can be automatically integrated in more and more supplier’s systems, or you can send orders by e-mail, fax or print them.

? 5. Goods receipt is either done in EBP by the supplier using an XML confirmation, by the employee who requested the item, by a general goods recipient (the last two options may require approval from the requester); or in the back-end system. Inventory is updated in back end.

? 6. The invoice is processed in EBP manually by the requester or an accountant, submitted by the supplier using an XML invoice, possibly from SUS or in the back-end system.

? 7, 8. These steps are the same as for Self Service Procurement.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

R/3

Plan Driven Procurement – System Landscape

MRP


PM/PS


Non-SAP

ExternalRequirement

RFCXML

ContractBid Invitation or

AuctionPurchase

order

RFC

InterfacecustomizingEBP

SourcingProcessPurchase Orders

? Plan driven procurement supports working within EBP on external requirements. Requirements out of R/3 Back-ends are replicated via RFC into the EBP system. External requirements can be uploaded too, but as XML documents. The requirements coming from an R/3 system could result from an MRP run or a PM or PS document, or could be created manually.

? Requirements from non-SAP planning systems can be transferred using the appropriate adaptor and XI communication.

? Depending on the sourcing, customizing the requirements can be handled in the sourcing transaction or in the purchase order work list.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Plan Driven Procurement – Requirement out of R/3

Reservation

MRP

Transfer to EBP via report

BBP_EXTREQ_TRANSFER

Purchaserequisition

? The graphic shows an example for an external requirement out of a R/3 system. ? In this case, an MRP run causes a purchase requisition referring to a reservation. ? As a result of the settings in the views V_T160EX and V_T160PR, the requisitions are determined to be

transferred to the corresponding EBP system. ? Schedule the report BBP_EXTREQ_TRANSFER in the back end and the requisitions transfer to the

EBP system.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Plan Driven Procurement – Sourcing in EBP

Worklist in Sourcing


Purchase Requisition out of R/3

? If customizing is set up for sourcing, the requirements appear in the sourcing transaction, otherwise they can be processed in the purchasers work list.

? As of EBP 4.0, you have full access to all sources of supply located in the corresponding back end (contracts and purchasing information records) within the sourcing cockpit. These can be assigned to requirements coming from the back end with a resulting purchase order created directly in the back end (External classic requirement.)

? EBP will not automatically assign a source or supply to external classic requirements. The search for back-end contracts and purchasing information records must be triggered interactively.

? Sourcing with back-end contracts and purchasing information records is not supported for requirements processed in the Extended Classic scenario.

? After assigning a source of supply, the items can be ordered. The document flow in EBP and R/3 shows the relationship between the purchasing documents.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Plan Driven Procurement - Prerequisites

? perform all steps for direct material

? set up entry channel for external requirements

? assing an RFC user for this entry channel

? assign your local purchasing group as responsible for this channel

? set up sourcing configuration

EBP

R/3 Backend

? maintain tables V_T160EX and V_T160PR

? make sure to have a RFC connection to the EBP system, withthe same RFC user as in the entry channel

? schedule report BBP_EXTREQ_TRANSFER to transfer the requisitions to EBP

After customizing the direct material, there are additional steps necessary: ? Using an entry channel, the requisitions are transferred into EBP. This channel must have at least one

entry user. ? Corresponding to this entry user, you have to set up a RFC connection from back end to EBP by using

this special RFC user. ? To get the requisitions in the work list for purchase orders, or in sourcing, there is a local purchasing

group required with the responsibility for the entry channel and the product category of the back-end requisitions.

? Customizing of sourcing or a BADI decides if the sourcing transaction or the work list for purchase orders will be used

? View V_T160EX in the R/3 back end determines which material groups and purchasing groups are grouped into a profile. View V_T160PR determines which profile targets to which RFC connection.

? The transfer itself is carried out by the report BBP_EXTREQ_TRANSFER. These can be scheduled (for example, once a day.)

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Organizational Structure Settings in EBP

Maintain entrychannel and RFC user

Setup responsibility forentry channel and product category

Define local purchasing group

? This graphic shows the steps as described in the Plan Driven Procurement: Prerequisites graphic .

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Technical settings in R/3 Backend

ViewsV_T160EX and V_T160PR

Schedule report

BBP_EXTREQ_TRANSFER

RFC-Connection

RFC-ConnectionSM59

RFC-User

? This graphic shows the steps as described in the Plan Driven Procurement: Prerequisites graphic .

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Plan Driven Procurement: SRM 3.0 Enhancements

? In mySAP SRM 3.0 the old reportRPRSEL01 is not used anymore.It has been substituted byBBP_EXTREQ_TRANSFER.

? This new transfer report allowsyou to

? group line items (either services or materials)

? transfer customer fields on item level to SAP Enterprise Buyer (e.g. fields in account assignment)

? The grouping of materials can be done based on a customerspecific logic. Therefore, a newBADI is offered as part of thebackend plug-in:BBP_BADI_EXTREQ_OUT

Backend

Backend

mySAP SRM 3.0

Purchase requisition? line item 1 (material)? line item 2 (service)? service A? service B

...

Requirement? line item 1 (material)? line item 2 (service)? service A? service B

...

Transfer viaBBP_EXTREQ_

TRANSFER

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Procurement of direct material

? Plan driven procurement

? Necessary customizing steps


Plan Driven Procurement: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Plan Driven Procurement

Topic: Prerequisites


? Setup the customizing steps in the R/3 back end and EBP system to enable plan driven procurement

In this exercise, you validate and maintain some data in customizing, tables and the organizational structure

1-1 View your material data reserved for the plan driven procurement scenario and check some table entries.

Log on to CLIENT 800 of the R/3 back end from the SAP GUI:

Client : 800

User ID: BACK-##

Password: learn

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-1 Display the Purchasing view for the material T-SRM1##.

SAP menu ? Logistics ? Materials Management ? Material Master ? Material ? Display ? Display Current


Choose Select view(s).

Verify that the following views are listed:

Basic Data, Purchasing, MRP, General Plant Data/Storage

Select Purchasing view

Choose Continue.


Select Continue.

Verify that 00201 is the Material Group

Verify that 0## is the Purchasing Group.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-1-2 Check the table entries in V_T160EX and V_T160PR for purchasing group 0##.

SAP menu ? Tools ? ABAP Workbench ? Overview ? Data Browser (SE16)

Enter V_T160EX as Table Name.

Select Table Contents

What profile number corresponds to the combination of material group 00201 and your purchasing group 0##?

Profile number: ______________________________________

Select Back

Enter V_T160PR as Table Name.

Choose Table Contents

What is the corresponding RFC-Connection to your profile?

RFC-Connection: ____________________________________

Log off.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2 Set up the organizational data in the EBP system.

Log on to CLIENT 3## of the EBP system from the SAP GUI:

Client : 3##

User ID: CONFIG

Password: learn

1-2-1 Maintain an entry Channel for the plan driven procurement.


Search for Phoenix Enterprise Inc. (if necessary).

Double-click on

Phoenix Enterprise Inc. organizational unit

Select Create.



Go to Basic data tab page

Enter Channel to replace New Organizational Unit.

Enter Channel R/3 to replace New Organizational Unit.

Select Continue

Go to Address tab page.

Maintain any address data.

Choose Save.

Choose Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-2 Display the predefined user TRA_RFC.

User menu for CONFIG ? Basis Tools ? Administration ? User Maintenance ? Users

Enter TRA_RFC as User.

Select Display

Go to Logon data tab page.

Verify that the User Type is set as Service user.


1-2-3 Transfer the user TRA_RFC via USERS_GEN into your channel.

Start the transaction User Generation (USERS_GEN) from your Favorites.

Select Create Users from existing SU01 Users

radio button

Select Execute Action.

Choose with F4

Channel as Organizational Unit (ID)

Choose US as Country

Choose Continue.

Select All users radio button.

Choose Continue

Select TRA_RFC in the list.

Choose Copy.


message appears.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Select Back.

1-2-4 For handling the back-end requisitions, the local purchasing group needs to have some additional settings in their responsibility.


Search for PGRP Local Purchasing Group.

Double-click on

PUR Group Miller

Go to Responsibility tab page.

Go to Product Responsibility Frame.

Enter 00201 as Product Category.

Choose R/3 back end (T90CLNT090)

as Source System

Go to Organizational Responsibility

frame

Choose with F4

<500006**> Object-ID of Org. Unit Channel R/3

Select Save.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


1-2-5 Set up sourcing for your product category. You want to have all products from category 00201 in your sourcing cockpit.


Goto ? SAP Reference IMG ? SAP Implementation Guide ? Supplier Relationship Management ? SRM Server ? Sourcing ? Define Interactive Sourcing for Product Categories

Select New Entries.

Choose with F4

00201 (Casing) as Category ID.

Choose Sourcing Always Carried Out

as Sourcing Option.

Choose Save.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercises

Unit: Plan Driven Procurement

Topic: Plan Driven Procurement


? Initiate requirements in R/3

? Transfer them to the EBP system

? Complete the requirements in the sourcing cockpit

In this exercise, you will start the process by creating a material reservation. Using MRP run, you’ll create a purchase requisition that has to be transferred to your EBP system. There you have to complete the requisition using the sourcing transaction.

2-1 Create a reservation for the material T-SRM1## and carry out a single- level single- item planning in the R/3 back end .

Log on to CLIENT 800 of the R/3 back end from the SAP GUI:

Client : 800

User ID: BACK-##

Password: learn

2-1-1 Add the stock requirements list to your favorites.



Type in MD04 as the Transaction code.

Select Continue.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-2 Display the stock/requirements list for your material T-SRM1## in plant 3200.

Start the transaction Display Stock/Requirements Situation (MD04) from your Favorites.



Choose Continue.

There should be nothing on stock.

For the following exercise, do not leave the transaction MD04, but select to create a new session!

2-1-3 Create a reservation for the T-SMR1## material in the second mode.

SAP menu ? Logistics ? Materials Management ? Inventory Management ? Reservation ? Create

Enter 201 as Movement Type.


Choose Enter

Enter 400000 as G/L Account No.

Enter 1000 as Cost Center.



Enter 0001 as SLoc (Storage Location).

Select Post.

Select Back.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-1-4 Perform a MRP run for your Material T-SRM1##.

SAP menu ? Logistics ? Materials Management ? Materials Requirements Planning (MRP) ? MRP ? Planning ? Single Item / Single Level



Accept all other default values.

Choose Enter (twice).

You should get a success message.

2-1-5 Switch to your first session with the transaction MD04 and choose to refresh your stock/requirements list for material T-SRM1## and plant 3200.

You should see your reservation and a purchase requisition.

Number of the purchase requisition: ____________________________

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-2 Transfer your purchase requisition to the EBP system by starting the program BBP_EXTREQ_TRANSFER.

In the menu bar choose System ? Services ? Reporting (SA38).

Enter BBP_EXTREQ_TRANSFER as Program

Choose Execute.

Enter <100*****> number of your purch. requisition

as purch. requisition

Choose Execute.

You should get a success message.

If you have trouble with transferring your purchase requisitions, look in table EPRTRANS for your documents. All requisitions to be transfe rred have to be included there before starting the transfer report. After executing BBP_EXTREQ_TRANSFER, the requisitions must not be there.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2-3 Sourcing in EBP

Log on to your client of the EBP SYSTEM from the BROWSER:

User ID: BUYEROP

Password: learn

Client : 3##

2-3-1 Find the requirement in sourcing



Select Carry Out Sourcing in the launch pad.

If you can’t see your purchase requisition, then

Select Find tab page.

Enter T-SRM1## as Product

Choose Start.

Select <the requirement for the Casing SRM1##>.


2-3-2 Optional: Process the requirement further on as you like (see also unit sourcing).

There are several ways to create a purchase order:

a) Enter a price and vendor manually and complete the incomplete purchase order in the purchaser’s work list.

b) Hold your work list, log on as a strategic purchaser BUYERST and create a contract for material T-SRM1## first. After, log on again as an operational buyer BUYEROP and complete the requirement via proposal of source of supply.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Administration


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? The project team members have installed the Enterprise Buyer system successfully.

? In this unit there are some useful hints to prevent difficulties in customizing and maintain the system.

Administration: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Integration Concept of the Exchange Infrastructure

? ITS concept

? Additional Cross-Application Customizing Settings

? Monitoring Tools

? Additional Technical Basic Settings


Administration: Unit Objectives

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Integration with SAP Exchange Infrastructure (XI)

3rd Party

WebAS 6.20

XMLMessage

RFChttp(s)

Integration Repository

Integration Directory

Firewall

PublicMarket-place

Enable XI in EBP

BusinessPartner

BusinessPartner

BusinessPartner

SAP Exchange Infrastructure 3rd party adapter

EBP SUS

The following documents can be sent in XML format: ? Purchase Order ? Order Acknowledgment ? Shipping Notification ? Confirmation ? Confirmation response ? Invoice ? Invoice response ? Data can be exchanged in XML format between Enterprise Buyer and any vendor system. Data can be

exchanged either directly using EBP XML or any XML dialect. The data is transferred between the vendor system and the SAP Exchange Infrastructure via HTTP. The SAP Exchange Infrastructure communicates with Enterprise Buyer via HTTP. The graphic illustrates the data exchange between the Enterprise Buyer system and external systems.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Overview SAP Exchange Infrastructure

Integration ServerIntegration Server

Integration Engine

IntegrationRepositoryIntegrationRepository

IntegrationDirectory

IntegrationDirectory

AdditionalIntegrationServices

configured knowledge

to businesspartners

to other publicor private

exchanges

to existing 3rd

party or SAPcomponents

Share CollaborationKnowledge

Execute CollaborativeBusiness Processes

EnsureCollaborationReliability

IntegrationMonitor

design time knowledge

? The Integration Repository provides integration scenarios, routing objects, mappings, interfaces, and components at design time. The Integration Directory starts with the same knowledge captured in the Integration Repository, but adds configuration-specific information that is needed for execution. This information includes technical specifications on customer and business partner components, mapping and routing information, and Web services.

? The collaboration runtime environment summarizes all runtime components relevant for exchanging messages among the connected software components and business partners. At the center of execution is the Integration Server, which includes the Integration Engine. The Integration Engine exchanges all messages between the different components that are connected.

? To ensure reliability, the Integration Monitor monitors the Integration Server and adapters and supports error handling. It covers events that are published by the Integration Engine, whether deployed as a central server or within the application component supporting peer-to-peer communication. The Integration Server needs to deal with two different error situations. First, it has to be able to provide helpful information on system messages due to exchange infrastructure-related errors. Second, it needs the capability to route back any sort of fault message of the application.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? What is the name of the transaction you are using in the browser?

? In the middle of the browser screen click on right mouse button, then on View Source. Check under Template for example: BBPSC02

? What ITS-version are you using?

? ITS version number

? Check template from EBP via <SE80>

? Maintain / Display

? Choose publish location: Utilities ? Settings ? ITS Tab

? Publish single or all templates

? Publish single service

? Version management of templates

? Publish all services

? <SE38>, W3_PUBLISH_SERVICES

Internet Transaction Server (ITS)

46

Compilation 3

Patch Level

Build Number

D

4640. 3087. 35.7747

? Display / Modify template via <SE80> In the first field on the left side choose Internet Services. In the field below select the service you are going to modify (i.e. BBPSTART). Open the tree below to see all templates belonging to this service. Double click on the template.

? To be able to publish templates, select the ITS you want to publish to: Utilities ? Settings, Publish to ? Select server (IACOR must be running on ITS).

? Publish single service with templates. Utilities ? Publish

? You can keep different versions of your templates and display the differences between two versions. Utilities ? Versions ? Version Management Select versions and choose Compare than on Deltas.

? Path on 'sapservX' for download of latest patch: `sapvervX/general/its/patches/46Dc3

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

IACOR - IAC Object Receiver

ITS instance

AGate

WGate

? In case of JavaScript-errors ? check the path to the Wgate (Type Web)

?Location of IAC-program:

? ... program files\sap\its \2.0\admin\iacoradmin.exe

?Location of IAC-documentation

?… program files\sap\its\2.0\install\iacor _readme.html

? A common error is that the destination paths are not set correctly in the IACOR! ? IACOR = Internet Application Component Object Receiver

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

BBP Framework - Service BBPSTART

The service BBPSTART serves as a framework for the whole EBP functionality? Provides a login screen? Provides a role -based launch pad to start applications? Handles the sessions and external windows? Supports a logoff mechanism

To successfully generate a menu for a user, BBPSTART accesses and requires the following data:

5

4

3

2

1

Transaction Type

Address of WebServer

Menu entries (Transactions)

Role

User and Language

Maintained in transaction SE93 (must be an 'Easy WebTransaction')

Maintained in table TWPURLSVR

Maintained in role definition? transaction PFCG

Maintained in user master data ? transaction SU01

Coming from logon screen

http://<WebServer>/scripts/wgate/bbpstart/!?~client=300&~language=en

? Explicit user logon is done using the EBP logon screen. During log on, the role defined in transaction PFCG is read and the user menu (launch pad) containing all the functions assigned to the user's role is generated.

? A session is opened once a function (= service) is chosen from the launch pad. The session has to be finished if a new service is chosen.

? If the user just closes the browser window or stops EBP running in the browser by typing another URL in the location bar, the service BBPSTART ensures that the session is closed in the ITS and a log off in the component is performed.

? The menu entries generated by the logon procedure outlined in the graphic are used by a JavaScript-function which launches the services.

? For each generated menu, the following steps are performed after generation: 'http://<WebServer>/scripts/wgate/<servicename>/!?~client=300&~language=en' is truncated to '/scripts/wgate/<servicename>/!?~client=300&~language=en‘

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Aligning UoM, Currencies and Exchange Rates

? The Contents of the Customizing table “Units of Measurement” must be identical in the Enterprise Buyer system and in the Backend System.

BBP_GET_CURRENCY

BBP_GET_EXRATE

? Allign the currencies and exchange rates initially in the Backend System with the Enterprise Buyer system and whenever currencies and exchange rates are updated in the Backend.

? The relevant ISO codes have to be allocated, in particular if connecting the system to catalogs.

<CUNI>

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-10

? SAP AG 2004

Shopping Cart - Customer-Defined Fields (1)

? You can use Customer fields to enhance the standard structures, create your own data to display, or change and forward the contents of non-standardized fields.

? Customer fields can be used in shopping carts, purchase orders, confirmations, invoices, and contracts at the header and item level, and for account assignment.

? Customer fields can be displayed in the standard interface or on a custom screen; they can also be filled externally from a back-end system or from the dialog user interface and can be passed from one document to another or to other connected systems.

? Note that the contents of the customer fields are not evaluated by the system and are only saved to the EBP database. If fixed values, search help or check tables are defined, the system automatically provides the (F4) input help.

? To be sure that the contents are passed from shopping cart to invoice, for example, you have to define the field in all documents (shopping cart, purchase order, confirmation, invoice). It is necessary to use exactly the same name and data type.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-11

? SAP AG 2004

Shopping Cart – Customer-Defined Fields (2)

? Customer fields can be maintained, displayed and exported as XML(through META BAPI interface)

? A BAdI is available for customer-defined subscreens

? Function group: BBP_PDH_CUF

? See OSS note 0458591

Customizing: ? For account assignment, database tables BBP_C_ACC_F (field labels) and BBP_C_ACCFD (text for the

fields) need to be enhanced with all customer fields (from include CI_BBP_ACC) so that these are available to the account assignment category. You have to use the following structures in transaction SE11 ? CI_BBP_ACC ? CI_BBP_ITEM ? CI_BBP_ITEM_CONF ? CI_BBP_ITEM_SC

? The BAdI for a customer-defined subscreen is not assigned in the IMG. Use transaction SE18 for BAdIs BBP_CUF_BADI and BBP_CUF_BADI2

? Header customer fields cannot be entered in the user interface and need to be taken into the document via a BAdI

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-12

? SAP AG 2004

Customer-Defined Fields – Maintain Global Data Type

<SE11>

? Use transaction SE11 to define data types/structures for each header or item where customer fields may be used. In this example, CI_BBP_ITEM contains the customer fields for the item screen. In the same way you would define a structure CI_BBP_HDR for the header fields.

? Additional steps are necessary for accounting fields, see Note 458591.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-13

? SAP AG 2004

<SE11>

Customer- Defined Fields –Maintain Document Data Type

? Use transaction SE11 to define data types/structures used, for each type of document. In this example, CI_BBP_ITEM_SC contains a new shopping cart customer field. ? CI_BBP_ITEM_SC CI_BBP_HDR_SC ? CI_BBP_ITEM_PO CI_BBP_HDR_PO ? CI_BBP_ITEM_CONF CI_BBP_HDR_CONF ? CI_BBP_ITEM_INV CI_BBP_HDR_INV ? CI_BBP_ITEM_CTR CI_BBP_HDR_CTR ? CI_BBP_ACC

? Hint: Activate and save all structures!

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-14

? SAP AG 2004

Customer-Defined Fields – Consistency Check

Report BBP_CUF01

<SE38>

? Created customer fields can be checked for consistency with the report BBP_CUF01 via transaction SE38.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-15

? SAP AG 2004

How to Show or Hide Fields in SC Overview (1)

1. Call transaction /nSHD0 and enter screen variant BBP_SC.

Note: You can also search for all available screen variants using BBP_* for different transactions or see the list in the Notes be low.

Screen Variants: ? Item data overview in an invoice without purchase order reference: BBP_IV_NON_PO ? Item data overview in the invoice with purchase order reference: BBP_IV ? Item data overview in the confirmation: BBP_CF ? Item data overview in the confirmation for time recording: BBP_CF_TIMEREC ? Item data overview in the purchase order: BBP_PO; ? Item data overview for contracts: BBP_CTR_ITEMLIST ? Item data overview for selection of contracts: BBP_CTR_ITEM_SELLIST ? Search results for entering an invoice and/or confirmation: BBP_SEARCH_PO ? Search results for entering a purchase order: BBP_SEARCH_SC ? Search results for displaying/processing an invoice: BBP_CHANGE_IV ? Search results for displaying/processing a confirmation: BBP_CHANGE_CF ? Search results for entering/displaying/processing/status of a shopping cart: BBP_SC; ? Worklist for Sourcing: BBP_SOCO_WL ? Work area in Sourcing: BBP_SOCO_GA

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-16

? SAP AG 2004


2. Copy the original screen variant to one with a customer name (Zxxxx).

Screen variant names in the customer name space should begin with a Z or Y.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-17

? SAP AG 2004


Note: You can create multiple screen variants for a screen and assign these in the BADI by user or other criteria.

4. Implement the method in the Business Add-In (BADI) Determine Screen Variant. Fill the export parameter EV_SCVARIANT with the new screen variant.

• IMG ? SRM Server ? Business Add-Ins for EBP ? Interface configuration ? Input Helps and Search Helps ? Determine Screen Variants.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-18

? SAP AG 2004

Application Monitor

Activate Monitor in Customizing

<RZ20>

Use application monitor for trouble shooting

Use additional monitors and trace tools in R/3

? Before the user with the Administrator role can use the Application Monitors, the Application Monitors have to be started in Customizing of the Enterprise Buyer (Cross-Application Specific Settings – Start Application Monitors)

? In the Application Monitor: Select the line(s) with the red light to get more information about the error. Select an error message to display a list of available tools. If the error is fixed, flag it and select Delete selected errors.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-19

? SAP AG 2004

Monitor Shopping Cart (1)

The Shopping Cart Data is transferred and the documents are created in the EBP system or Backend System

Synchronize the Shopping Cart Data with the data in the Backend System

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-20

? SAP AG 2004


< BBP_BW_SC2 >

The detail shows the whole document information like purchasing group, price, logical system, follow on document and so on

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-21

? SAP AG 2004


<BBP_PD>

? Show Header and Item details

? Show Document Status

? To have detailed information about the Shopping Cart objects, you can use transaction BBP_PD and then with a double-click, you get into the information you need.

? Beside the status and document information, you will also get the table information.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-22

? SAP AG 2004

Master Data - Vendor and Materials

? Check Vendor Master Data Transfer

? Check log after initial download <SLG1>

? Check Product Master Data Replication

? Monitor download objects <R3AM1>

? Check inbound queue for incoming master data <SMQ1> (EBP)

? Check outbound queue for outgoing master data <SMQ2> (backend system)

? Check errors with master data transfer<SMO8FT>

? Vendor master data transfer To check whether all vendors have been replicated correctly after the initial download, you can use the transaction <SLG1> with BBPGETVD as application object.

? Product (Materials & Services) Master Data Replication ? You can use the transaction <R3AM1> to check how far the process of replicating master data is.

Traffic light should be on green if replication was successful. ? You can use the transaction <SMQ1> to check the EBP inbound queue for incoming master data. ? You can use the transaction <SMQ2> to check the outbound queue for outgoing master data (in the

back-end system. ? You can use the transaction <SMO8FT> to check errors with master data transfer. Select period and

choose Details or Message LOG.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-23

? SAP AG 2004


Notification Mail recipient

Notification Events


? Perform Task-Specific Customizing ? Activate the event linkage for any new workflow and define the agents involved.

? Define Recipient of Notifications ? For each scenario (shopping cart, confirmation, invoice), select the user role(s) to receive e-mail. In the

details per item, define which events trigger the e-mail.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-24

? SAP AG 2004

? Workflow activated? <OOCU>

? Agent assigned? <OOCU>

? Are there conflicts with the starting conditions? <SWB_PROCUREMENT>

? Workflow Log (work item analysis)

? Display all work items for a certain period <SWI1> or <SWI2_FREQ>

? Display log

? Simulate workflow <SWUD>

Workflow Tools I

? Make sure the workflows are activated <OOCU>. ? Check that the workflows and relevant tasks are assigned to an agent (they can also be defined as general

task) <OOCU>. ? Make sure that there are no conflicts in the starting conditions <SWB_PROCUREMENT>. ? Selection Report for Work items <SWI1> (shows more details on selection screen. Sorted

chronologically) or <SWI2_FREQ> (sorted by workflow). Double click on a work item to see the log. Menu path: Goto ? List with technical details; view the Container, the Agents, the Status or eventual Error messages.

? Simulate Workflow <SWUD> Maintain Workflow ? Test Environment ? Simulate Event, check eventual error messages. Workflow can also be activated from here.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-25

? SAP AG 2004

Workflow Tools II

? Clean / Synchronize Buffer <PPWFBUF> or <SWU_OBUF>

? Reject / Approve directly from work item overview

? Maintain ‘EC_DECISION’ in <SWL1> for corresponding tasks

? Unlock work item in inbox (status ‘In Process‘)

? If the workflow is not running though all customizing is OK, make a buffer synchronization: <PPWFBUF> or <SWU_OBUF> and choose in the Menu path: Runtime Buffer ? Synchronize.

? Details Button disappeared in inbox: <SBWP> (or </n> and Office ? Inbound message processing), and then Settings ? Workflow Settings ? Refresh organizational environment.

? To define whether a manager can approve or reject a work item directly from his inbox overview, go via <SWL1> (Define Dynamic Columns for Integrated Inbox). Maintain EC_DECISION in the column Expression for those tasks where you want to see the buttons on the first screen.

? If a work item in the inbox cannot be processed because of status In Process <SM12>, select user, client and * for table name, lock argument, and delete the lock entries.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-26

? SAP AG 2004

? Check inbound and outbound parameters <WE20>

? Check ports <WE21>

? IDoc status lists <WE05>

? Display and resend IDoc <BD87> (selection screen is based on distribution model)

ALE Tools

? Check partner profiles <WE20> Open the partner type LS and select either your back end or your EBP to check which IDocs are coming in or going out Check the details for the IDocs. All parameters you see in this transaction were generated from the distribution model.

? Check <WE21> to see whether a port has been created correctly. Select Transactional RFC Choose the Port to get details

? IDoc status lists <WE05> Select a time period. Double click on the message type Double click on the IDoc number to see IDoc content and status

? Display and Resend IDoc <BD87> (good selection screen: based on distribution model)

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-27

? SAP AG 2004

Basic Information

? Support Package Info <SPAM>

? Plug-in info on backend system <SAINT>

? System logs <SM21> (that is, table space errors)

? Short dumps <ST22>

? Units of measure <CUNI>: Only those units of measure that have 'commercial measure units' selected can be used for EBP

? Check the support package level of your EBP or back end with <SPAM>. Select Package Level. ? Check the Plug-In and patch level that is installed in your back end <SAINT>. ? System logs <SM21> (for example, table space errors). ? To check the short dumps, you can use transaction <ST22>. Select a period and execute.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-28

? SAP AG 2004

Archiving EBP Documents

? The following documents can be archived:

? Shopping cart

? Purchase order

? Confirmation

? Invoice

? Procurement Card Statements

? EBP archiving as of 3.5 primarily serves to facilitate the cleanup of the database and to restrict accumulation of data

? Restrictions:

? Not possible to restore the archive files to the file system

? No program to read the archived files

? Not possible to archive other EBP document types, such as bid invitations and bids

? Archiving is a process to remove bulk or outdated data from your database that is no longer needed in your system. You can archive: ? Shopping Carts ? Purchase Orders ? Confirmations ? Invoices ? Procurement Card Statements

? The restoration of archived data is not yet possible. ? A program to read the archived data has not been implemented yet.. ? Only documents from completed business processes can be archived. ? Only local documents are checked; there are no RFC calls to the back end.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-29

? SAP AG 2004

? Integration Concept of the Exchange Infrastructure

? ITS concept

? Additional Cross-Application Customizing Settings

? Monitoring Tools

? Additional Technical Basic Settings


Administration: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 10-30

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Appendix: Component Planning


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Phoenix Enterprises has decided to implement the components planning functionality of EBP.

? You use component planning for orders in Enterprise Buyer professional edition if you want to perform component-based planning with Web-based catalogsproposed by means of the Internet/Intranet for your maintenance, service orders or project.

Component Planning: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Component Planning: Unit Objectives

? EBP Component Planner Role in Component Planning

? Component Planning Process


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

EBP Components Planner Role

The components planner can use the following transaction (and functions):

The components planner can process maintenance and service orders, and plan the materials needed for execution of these orders. As employees, they can search for required products in catalogs and order them.

? Component planning for maintenance or service order

? Component planning for projects

? Change Settings

? With the help of this process, you can select additional components from Web-based catalogs that are offered by means of the Internet/intranet in Enterprise Buyer professional edition for: ? Maintenance or service orders ? Projects ? Procurement occurs in Enterprise Buyer.

? Prerequisites: ? You have been assigned to the role Component planner (SAP_EC_BBP_PLANNER). You process the

roles in Customizing. Menu path in the Implementation Guide (IMG): Enterprise Buyer professional edition ? Application-Specific Basic Settings ? Roles ? Define Roles . ? You have assigned certain values to attributes.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Purpose

? You use component planning for orders in EBP if you want to perform component-based planning with internal or external catalogs.

? Advantages

? Easy access to catalogs for materials planning from R/3 Release 4.0

? Cost savings through reduction in time and resources required for entering material master records

Component Planning in EBP

? PM = Plant Maintenance

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Component Planning Process Flow

BACKEND EBP CATALOG

Display component detail data

Component list is

copiedand orders

added

Create and

processorders

Find ordersand display

with component list

Find additional

components using catalog

Select external catalog

Find and selectadditional

components

Transfer new

component list to

SAP backendsystem

Process component detail data or delete

components

Enteradditional

componentsmanually

Transfer components

to EBP

Process Flow ? Create a maintenance/service order or a project. Add components to the order/project-based transaction

as required. ? Choose Component planning in EBP.

Search for orders/select projects in Enterprise Buyer The system uses a function module in the back-end system to search for the relevant orders/project and displays the result in Enterprise Buyer. If you choose an order/project, the transactions for the order also display in the overview tree. In addition, header data of the order/network also displays for the selected transaction. In the project scenario, the header data also contains the ID of the WBS element. The individual order/project components are listed in the component overview. You can only change this data in the back-end system.

? Displaying and changing default values Choose Display default values to edit the values for the following fields: Purchasing group, Purchasing organization, Material group .G/L account, Plant, Goods recipient, Unloading point, Requirement date type (only project scenario).

? Choose the catalog from which you require components. In the catalog, choose the required component in appropria te quantity and order the shopping cart. The system transfers the components contained in the shopping cart to the component overview and assigns the Components transferred from the catalog to the selected transaction. The system also transfers SAP product master data from the catalog, where applicable. (continued)

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Automatic generation of purchase requisitions

or reservations

Materials Planning for Component Planning

Access to external catalog via the Internet

Create component list for order

Plaint maintenaceorder in SAR R/3

List of orders in EBP

? As an alternative: Enter a description or a back-end material number for the component and select Add component. The system adds the component to the component overview.

? You can only change and delete components copied from a catalog during an Enterprise Buyer session, or components that have been manually created.

? You can check all the data for components added in Enterprise Buyer ? Defective components are highlighted in red in the component overview. You can read the error in the

detail screen before correcting the data. Carry out the check again in the component overview. ? Transfer component data to the back-end system: Save the order/project. After a check, the components

added in the Enterprise Buyer system are transferred to the back-end system. ? Order scenario: The updated components for orders or order-based transactions are now in the back-end

system. Components already transferred can no longer be changed in Enterprise Buyer. They do, however, remain in the component overview (without symbol under Action).

? Project scenario: The updated components for projects are now in the back-end system. The system changes to the initial screen where you can enter another project definition or WBS element.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? List and select orders created in the backend system

? Select components from Web-based catalogs and add them to an order operation

? Add components manually to an order operation

? Completely delete components that originate from a catalog or have been created manually in EBP

? Change and delete data for components that originate in a catalog or have been created manually in EBP

? Transport data for components from EBP to the SAP backend system

Component Planning Functions

Functional Scope

? Mandatory attributes with single values ? PM_PUR_GRP Default value in the component detail data ? PM_PUR_ORG Default value in the component detail data ? SYS Definition of backend system

? Mandatory attributes with several values ? CAT Catalog search ? PM_IPHAS Order Search ? PM_WERK Default value in the component detail data ? PM_WGR Default value in the component detail data

? Optional attributes ? PM_ARWRK Order Search ? PM_AUART Order Search ? PM_SWERK Order Search ? PM_VAWRK Order Search ? PM_IWERK Order Search

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004


? EBP Component Planner Role in Component Planning

? Component Planning Process

Component Planning: Unit Summary

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 11-10

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Appendix: Procurement Cards


Appendix


Course Overview

Organization

Workflow

Catalog Management

Master Data

Administration



Sourcing

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

? Your company has decided to use P-cards for procurement of items associated with local purchase orders. In this exercise you will carry out the steps necessary for the process.

Procurement Cards: Business Scenario

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Procurement Cards: Unit Objectives

? Creating Procurement Cards (PCards)

? Using Procurement Cards

? Approving Procurement Cards


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Procurement Cards I

User can choose the procurement card as a method of payment for Local orders

? As a method of payment

? Local orders only

Manager maintains Pcard Approval Amount

Using PCards

Approve

Shop

Create user ID

Procurement Card Data

? In the Enterprise Buyer system, you can specify procurement card as the payment method when purchasing items provided you are using the Materials Management functions in Enterprise Buyer. In addition, you can manage settlements for purchases made using a procurement card, that is, you can transfer the settlement file that the bank or card company sends you to the Enterprise Buyer system to check that the contents are correct and specify account assignments. Individual purchases can be subject to approval procedures that use the SAP Business Workflow.

Process Flow: ? You specify procurement card as payment method when creating a requirement coverage request. The

settlement data is transferred to the Enterprise Buyer system. ? At the same time, the system generates an invoice for all purchases that were made using a procurement

card. The invoice is updated in accounts payable accounting in the back-end system and blocked for payment. The system can then pay the invoice during the payment run.

? If the value of purchases made using the procurement card exceeds the value specified in Customizing, the system places a work item in the cardholder’s Enterprise Buyer inbox when updating the invoice. The cardholder checks the purchases made and can change the account assignment if necessary.

? If you want the manager to monitor expenditure as well, he or she receives a work item in his or her inbox. When the manager has given approval, the system posts the invoice to a G/L account in Accounting.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Background Information

Procurement Cards II

? Procurement Cards (PCards) are commonly used as a means of payment in many companies.

? PCards are credit cards issued by companies such as American Express and VISA except that the invoice goes to the company and not to the individual cardholder.

? PCards are provided to employees or groups of employees (departments).

? PCards are often used for store bought products and services.

? A PCard can be kept on file at the supplier location for organizations to use (Ghost Cards).

? In the Enterprise Buyer system, you can specify procurement card as the payment method when purchasing items if you are using the Materials Management functions in Enterprise Buyer. In addition, you can manage settlements for purchases made using a procurement card, that is, you can transfer the settlement file that the bank or card company sends you to the Enterprise Buyer system to check that the contents are correct and specify account assignments. Individual purchases can be subject to approval procedures that use the SAP Business Workflow.

Process Flow: ? You specify procurement card as payment method when creating a shopping cart. The settlement data is

transferred to the Enterprise Buyer system. ? At the same time, the system generates an invoice for all purchases that were made using a procurement

card. The invoice is updated in accounts payable accounting in the back-end system and blocked for payment. The system can then pay the invoice during the payment run.

? If the value of purchases made using the procurement card exceeds the value specified in Customizing, the system places a work item in the cardholder’s Enterprise Buyer inbox when updating the invoice. The cardholder checks the charges made and can change the account assignment if necessary.

? If you want the manager to monitor expenditure as well, he or she receives a work item in his or her inbox. When the manager has given approval, the system posts the charges to a G/L account in Accounting.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

PO to Vendor

Vendor

Vendor chargesorder to PCard

PO created using PCard

Bank statementPCard Owner

Order sent to bank

IDoc to EBP Work item sent

for reconciliation

Approval(optional)

Poststo G/L

EBP

Vendor Bank Customer Bank

Posts to AP

Posts to AP

Procurement Cards - Data Flow

EBP

EBP

Manager

? Procurement process ? Purchase Order (PO) created using PCard as the method of payment ? PO is sent to the vendor with PCard number ? Vendor charges order to the PCard

? Reconciliation process ? Bank statement for the vendor charge is sent to the EBP component by card issuing institute (via an

IDoc). ? EBP verifies data and creates an invoice ? Invoice is posted to Core R/3 AP system ? PCard owner receives a workflow item and reconciles bank statement ? Statement forwarded to approver via workflow (optional) ? Statement is approved or rejected ? Once approved, statement is posted to Core R/3 G/L and CO

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Process of Reconciliation

? After the procurement card transactions have been loaded from the procurement card statement file provided by the bank, the employee assigned to the procurement card receives a notification to approve the charge.

? Managers can also view charge based on the dollar value.

? The cost assignment can be changed by EBP users:

? different cost assignments (cost centers & projects)

? line items can be split between different cost assignments

Reconciliation of Procurement Cards

Process of Reconciliation

? The Enterprise Buyer system stores the settlement data sent by the bank or card company in the Enterprise Buyer database. It specifies the account assignment that you assigned in Customizing for procurement cards, generates an invoice, and updates this in Accounting in the back-end system. Furthermore, an approval transaction can be started in the Enterprise Buyer system if you have made the appropriate settings in Customizing. After the approval process has been completed, the system makes a posting to a G/L account in the back-end system for each purchasing transaction.

? The settlement data is transferred in the background.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Procurement Card Statement

File Format Conversion

? Each bank can have a unique format for statement data

? Bank and customer will need to establish a common method of exchanging data

? EBP must be configured to load bank specific statement data

? EBP has a format that can support a broad range of statement data

? SAP supports up to ‘level III’ information in the statement

? Level I: Amount, currency, & transaction ID

? Level II: Tax data & reconciliation process

? Level III: Detail data such as description, & UNSPSC

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


? SAP AG 2004

Procurement Card Archiving

? Archive the data generated by procurement card purchasing transactions

? Archive Development Kit (ADK)

? Data for completed transactions is archived to archive files after a specified retention period.

? A reload function allows you to access the archived data later if required.

? You can move the archive files from the file system to tertiary storage media such as CD-ROMs or magnetic tapes.

? This allows you to keep your database to a manageable size while observing statutory data retention regulations.

? The default retention period is two months, but this can changed in Customizing. The archiving functions extract the data from the underlying tables using archiving objects. An archiving object BBP_PC_ARC already exists.

? You have to perform the following steps using transaction SARA: ? Create archive files ? Delete the archived data from the database

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

© SAP AG SRM210 12-10

? SAP AG 2004

Procurement Cards: Unit Summary


? Creating Procurement Cards (PCards)

? Using Procurement Cards

? Approving Procurement Cards

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Date post:	12-Dec-2015
Category:	Documents
Upload:	burra19
View:	213 times
Download:	2 times