bp_manage procurement in sap ebp and sus

Manage Procurement in SAP EBP and SUS Best Practice for Solution Management

Version Date: June 2006 The newest version of this Best Practice can be

obtained through the SAP Solution Manager

Contents Applicability, Goals, and Requirements....................................................................................................2 Best Practice Procedure and Verification .................................................................................................4

Preliminary Tasks ...............................................................................................................................4 mySAP E-Procurement Solution Integration Scenarios...............................................................4 MySAP Supplier Relationship Management Business Scenarios ...............................................4 SRM 5.0 System Landscape in General......................................................................................5 SAP SRM 5.0 – Components Overview.......................................................................................6 Core Business Process: Supplier Enablement SUS-MM ..........................................................11 Core Business Processes: Supplier Enablement SUS-EBP handled in different scenarios .....15

Procedure.........................................................................................................................................31 Monitoring Procedure: Business Process Supplier Enablement SUS-MM................................31 Monitoring Procedure: Business Process Supplier Enablement SUS-EBP ..............................43

Further Information .................................................................................................................................53

Best Practice: Manage Procurement in SAP EBP and SUS

© 2006 SAP AG

2

Applicability, Goals, and Requirements To ensure that this Best Practice is the one you need, consider the following goals and requirements.

Goal of Using this Service This Best Practice enables you set up a Business Process Management and Monitoring concept for SAP’s Enterprise Buyer Professional (EBP) solution, valid for the SRM 5.0 The management and monitoring concept focuses on the business procurement processes of Supplier Enablement SUS-EBP and SUS-MM scenarios. The Business Process Management (BPM) service is based on the most common EBP environment, which consists of a SAP EBP system and a SAP R/3 OLTP system. System availability is of particular concern, that is, the availability of the EBP system, the OLTP system, and all other components such as the Internet Transaction Server (ITS), the Internet and Pricing Configurator (IPC), the Business Connector (BC), external Catalog, SAP Catalog and the SAP Exchange Infrastructure (XI).

This business process management and monitoring concept aims to: • Define procedures for business-process oriented monitoring, error handling, and escalation

management for Procurement in SAP EBP, SAP MM, SAP XI and SAP SUS. • Define the roles and responsibilities for all persons involved in the customer’s support and

monitoring organization with respect to Procurement in SAP EBP, SAP MM.

These procedures ensure the smooth and reliable flow of the core business process in order to meet your business requirements. In the best case, this concept is already applied in the late stages of your testing phase to gain experience with these concepts.

Alternative Practices You can have SAP experts deliver this Best Practice on-site by ordering a Solution Management Optimization (SMO) service known as the SAP Business Process Management service.

Staff and Skills Requirements To implement this Best Practice, you require the following teams:

Application Management Team

The EBP business process management concept (which this Best Practice aims to produce) should be created by the Application Management Team. This team combines experts from your company:

Business department.

Solution support organization (for example, the IT department, Help Desk or Customer Competence Center).

Implementation project team.

Execution Teams

The execution teams are the following groups, which taken together form the customer’s Solution Support Organization:

The Business Process Champion for each business process.

Application support.

Development support.

Program scheduling management.


© 2006 SAP AG

3

Software monitoring team.

System monitoring team.

More information about roles and responsibilities of these teams can be found in the superordinate Best Practice General Business Process Management, which you can obtain through the SAP Solution Manager.

Necessary or Useful Trainings

ADM102 SAP Web AS Administration II

ADM105 Advanced SAP System Administration

ADM130 E-Commerce Administration

BIT530 SAP Business Connector BIT400 SAP Business Connector (will substitute BIT530).

SRM210 SAP Enterprise Buyer Configuration

ITS070 SAP Internet Transaction Server: Administration (integrated ITS6.40 not included)

SAPSRM mySAP SRM Solution Overview

SRM230 Deltaworkshop EBP 3.5 to EBP 5.0

SRM240 Requisite eMerge 4.0

SRM250 Strategic Sourcing & Supplier Collaboration

SRM260 SAP Catalog & Content Management

System Requirements None.

Duration and Timing Duration

Creating a business-process management concept could take around one week per business process.

Implementing the business-process management concept could take around one additional week.

Timing

The best time to apply this Best Practice is during the planning phase or during the implementation phase of your mySAP solution.


© 2006 SAP AG

4

Best Practice Procedure and Verification

Preliminary Tasks

mySAP E-Procurement Solution Integration Scenarios SAP Enterprise Buyer Professional (EBP) is the purchasing component of the mySAP E-Procurement solution. SAP EBP supports you in the procurement of non-production materials, goods, and services such as office supply or tools. You can perform the complete procurement process in an Internet browser – from creating a shopping cart to creating the invoice.

The various strategies for using R/3 and EBP in combination are called integration scenarios. There are five different integration scenarios for setting up a mySAP E-Procurement solution using SAP EBP:

o Classic scenario – SRM can be used to create shopping carts, obtain approval if required, enter the goods receipt, and create the invoice. SRM communicates this information to the backend system where the active documents are created.

o Extended Classic scenario – Since SAP EBP 3.0. The procurement process takes place locally in SRM and the data is replicated to the backend system. If the data in the shopping cart is insufficient to generate a complete purchase order, purchasers can complete orders and assign sources of supply manually in SRM before the order is transferred to the backend system. The purchase order in SRM is the leading purchase order. The purchase order in the backend system is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system.

• Standalone scenario – The SAP EBP system is connected to one or more OLTP systems that do not cover functionality for material management. Hence the entire procurement process is solely performed in the SAP EBP system. Financial accounting and controlling is still covered by an OLTP system.

• Decoupled scenario – Certain products such as office supply (or all non-production materials) are solely procured in the SAP EBP system, and other products such as PC hardware are procured in an OLTP system.

• Hosted scenario – The SAP EBP system is hosted on an SAP Marketplace that is connected via a Business Connector to one or more OLTP systems. Like in the standalone scenario, the entire procurement process is solely performed in the SAP EBP system.

MySAP Supplier Relationship Management Business Scenarios From a business point of view the following scenarios are offered by mySAP SRM 5.0. Supplier Enablement – the supplier enablement is a web based scenario that integrates small or medium sized suppliers into the procurement processes of large buying organizations. These suppliers can access the processing capabilities for service or material orders only by using a web browser.

The supplier enablement scenario is deployed in the scenarios listed below:


© 2006 SAP AG

5

Supplier Enablement SUS-EBP Scenario - used for procurement of service and indirect materials. The process flow comprises of supplier registration, supplier-managed content, purchasing, confirmation, invoicing and evaluated receipt settlement. Supplier Enablement SUS-MM Scenario – used for procurement of direct materials. The process flow comprises of purchase order creation in SAP MM, receipt of purchase order in SUS, creation of sales order and transfer of purchase order response, receipt of purchase order response in SAP MM, creation of ASN in SUS, receipt of ASN in SAP MM, goods receipt in SAP MM, creation of invoice in SAP SUS and receipt of invoice in SAP MM.

SRM 5.0 System Landscape in General The main SRM scenario components are summarized in the following table (see also the diagram below).

SAP SRM Server 5.5

SAP Supplier Relationship Management Server 5.5 is based on SAP NetWeaver Application Server 7.0, comprises SAP Enterprise Buyer, SAP bidding engine and supplier self service.

OLTP System The OnLine Transaction Processing system (for example, SAP R/3 System) that is used in the Enterprise Buyer environment as a backend system. It covers functionality for financial accounting, controlling, and material management.

The SAP R/3 OLTP can be as of Release 3.1i up to SAP R/3 Enterprise 4.70, ERP 1.0, ERP 2.0 (SAP R/3 4.6C of higher recommended).

Internet Transaction Server (ITS) integrated

As of SRM 5.0, only the integrated ITS is supported. Recommended ITS Version: 7.00 SP05 or higher (SAP Note 884148).

With ITS integrated in SAP Web Application Sever, the web browser now communicates directly with the SAP system. All ITS related sources (service files, HTML templates or MIME files) are now stored in the system’s database, similar to ABAP sources.

E-Mail Server The e-mail server manages e-mail processing for automatic workflow (optional).

Internet Pricing and Configurator (IPC)

Since EBP 3.5 the system component Internet Pricing and Configurator is being used for tasks like pricing and tax calculation.

SAP Catalog Content Mgmt 2.0

The SAP Catalog Content Management requires SAP Process Integration 7.0, SAP SRM Server 5.5 and the SAP Catalog Content Management 2.0 (Catalog Search Engine and Catalog Authoring Tool).

SAP Catalog Content Management can be run on SAP SRM Server 5.5 in a different client or it can be run on its own catalog server.

Requisite is no longer supported for SRM 5.0.

SAP Exchange Infrastructure (XI)

The SAP Exchange Infrastructure can be used for data exchange between mySAP SRM 5.0 and SAP Catalog Content Management.2.0 of the internal SAP Catalog. MySAP SRM 5.0 contains an XI release 7.0.

SAP Web SAP Web Application Server (SAP Web AS) is the application platform of


© 2006 SAP AG

6

Application Server

(SAP Web AS 7.0)

SAP NetWeaver, i.e. it provides the complete infrastructure to develop, deploy and run all SAP NetWeaver applications.

SAP Web AS consists of SAP WebAS ABAP 7.0 and SAP WebAS Java 7.0.

For the smooth and reliable operation of the core business processes it is required to ensure the general availability and an adequate performance of the following system components:

• SAP EBP system • OLTP System such as SAP R/3 • Internal ITS • IPC • Catalog server hosting the internal catalog • SAP Exchange Infrastructure (XI) • SAP Web AS

A collection of basic instructions for a technical monitoring of these components is given in the Appendix. The aim of this Best Practice is the reliable operation and monitoring of business processes from an application point of view, so for further particulars on setting up technical system monitoring, we refer you to the Best Practice Document ‘mySAP SRM 4.0 / 5.0. System Landscape Monitoring. There you will find a description of steps that are necessary to be performed in order to set up a monitoring of the different technical components and its integration in the Computer Center Management System (CCMS) monitoring environment. This document can be obtained through the SAP Solution Manager at the earliest end of August 2006. The diagrams below give an overview about the SRM 5.0 components and the system landscape related to each business scenario.

SAP SRM 5.0 – Components Overview Diagram and matrix below give an overview about the SRM 5.0 components.


© 2006 SAP AG

7

The process graphics will give an overview about the optional/mandatory requirements for the SUS related business scenarios


© 2006 SAP AG

8

Mandatory for the System Landscape: • Supplier Relationship Management Server 5.5 • Internet Transaction Server • SAP GUI for Windows 6.40 or higher • SAP NetWeaver usage type Process Integration (PI) • Process integration content (PI content) for

o SAP SRM Server 5.5 Optional for the System Landscape:

• SAP NetWeaver 2004s search and classification (TREX) • SAP NetWeaver BI7.0 • SAP NetWeaver Portal 7.0 (Portal Server) • SAP R/3 OLTP as of 3.1i up to SAP R/3 Enterprise 4.70, ERP 1.0, ERP 2.0 • SAP R/3 Plug-In2004.1 or higher if one is available • Business Packages for SAP NetWeaver Portal 7.0:

o Business Package for SAP SRM 5.0 o Business Package for supplier collaboration (2.0)


© 2006 SAP AG

9


© 2006 SAP AG

10

Mandatory for the System Landscape: • Supplier Relationship Management Server 5.5 • Internet Transaction Server • SAP GUI for Windows 6.40 or higher

Optional for the System Landscape: • SAP NetWeaver 2004s search and classification (TREX) • SAP Catalog Content Management 2.0 • SAP NetWeaver BI7.0 • SAP NetWeaver Portal 7.0 (Portal Server) • SAP NetWeaver usage type process integration (PI) • SAP R/3 OLTP as of 3.1i up to SAP R/3 Enterprise 4.70, ERP 1.0, ERP 2.0 • SAP R/3 Plug-In2004.1 or higher if one is available • Business Packages for SAP NetWeaver Portal 7.0:

o Business Package for SAP SRM 5.0 o Business Package for supplier collaboration (2.0)

• Process integration content (PI content) for o SAP SRM Server 5.5


© 2006 SAP AG

11

Mandatory for the System Landscape: • Supplier Relationship Management Server 5.5 • Internet Transaction Server • SAP GUI for Windows 6.40 or higher

Optional for the System Landscape:

• SAP NetWeaver 2004s search and classification (TREX) • SAP Catalog Content Management 2.0 • SAP NetWeaver BI7.0 • SAP NetWeaver Portal 7.0 (Portal Server) • Live auction cockpit web presentation server (LACWPS) 5.0 • SAP NetWeaver usage type Process Integration (PI) • SAP R/3 OLTP as of 3.1i up to SAP R/3 Enterprise 4.70, ERP 1.0, ERP 2.0 • SAP R/3 Plug-In2004.1 or higher if one is available • Business Packages for SAP NetWeaver Portal 7.0:

o Business Package for SAP SRM 5.0 o Business Package for supplier collaboration 2.0

• Process integration content (PI content) for o SAP SRM Server 5.5

Core Business Process: Supplier Enablement SUS-MM The Supplier Enablement SUS-MM business scenario is a Web-based scenario that provides full processing capabilities for direct material orders and integrates small or medium-sized suppliers into the procurement processes of large buying organizations. Such suppliers do not require their own sales systems to offer products and services. They just need an Internet access in order to use hosted order and content management functionality.

The SUS-MM business scenario deploys the supplier enablement capabilities of mySAP Supplier Relationship Management (SRM) with SAP Supplier Self-Services (SAP SUS) and SAP Materials Management (MM).

The purchase order and the follow on documents are created in the SAP MM system.

The business process flow comprises the following process steps:

Creating PO in SAP-MM The purchase order document (for materials only) is created in SAP MM and send to SAP SUS. Even if the PO has been sent to SAP-SUS it is changeable at any time. In this event a change PO is generated and sent to SAP-SUS. In SAP SUS the corresponding sales order is changed and its status is set to ‘changed by customer’.

Receive Purchase Order (PO) in SUS, Create Sales Order and Send Order Response (PO Response) A sales order with the status New is created in SAP SUS. Suppliers can display the sales order in the document list (using the search function if required), or they are sent an e-mail that contains a link to the sales order.

On the document screen, the following functions are available:


© 2006 SAP AG

12

• Save – Any changes made to the sales order can be saved; however, the changed document is not automatically sent back to the purchaser. The sales order is assigned the status In Process and can be further processed at a later date.

• Cancel – Any changes made to the sales order are not saved and the document is not sent back to the purchaser. It retains the status it had prior to the changes and can be further processed at a later date.

• Accept and Send – Suppliers can change the price, quantity, and delivery date in the sales order. A purchase order response is sent back to the purchaser in SAP MM. The status of the sales order is set to Accepted

• Reject and Send – Suppliers can reject POs that they find unacceptable. A PO response is sent to the purchaser in SAP MM. All quantities are set to zero. Since it is not possible to process SAP MM documents with quantities equal to zero, the PO is automatically rejected. This also applies when single items are rejected. The purchaser receives a message that the purchase order was rejected. The status of the sales order in SAP SUS is set to Rejected.

Receive Order Response (PO Response) in SAP MM Depending on the status of the PO response, one of the following options applies:

• If the supplier has rejected the PO, the purchaser can make changes and send a change order to the supplier. The corresponding sales order in SAP SUS is also changed and is given the status Changed by Customer. The PO can be changed right up to the final delivery.

• If the supplier has accepted the PO, there are two alternatives: o Supplier has not changed PO: no effect on the process

o Supplier has changed PO: purchasers only see the change if they display the PO.

Create Advanced Shipping Notification (ASN) in SUS Suppliers can create an ASN for a sales order with status Accepted. The following functions are available: � Save – An ASN document with the status In Process is created in SAP SUS and the entered data is saved but not yet sent to SAP MM. The ASN can be further processed later and then sent. � Cancel – The operation is terminated and the entered data is not saved. � Ship and Send – An ASN document with status Shipped is created in SAP SUS. The entered data is saved and sent to SAP MM. If the purchaser notifies the supplier that the ASN has been received, the supplier can change the status of the ASN in SAP SUS to Delivered. If the purchaser reports an incorrect ASN, the supplier can change its status in SAP SUS to Returned. The following fields in SAP SUS are mandatory:

• Quantity

• Delivery data

• Material (with material ID)

• PO reference

• PO item Create ASN in SAP MM The purchaser receives an inbound delivery in SAP MM and post the goods receipt with reference to the delivery.


© 2006 SAP AG

13

Goods Receipt in SAP MM The goods receipt is posted to the relevant warehouse. In case of a goods return or partial goods return, the status of the ASN in SAP SUS is set to Returned and a new ASN has to be manually created. Later, the supplier has to be directly informed by the purchaser.

Create Invoice in SAP SUS In SAP SUS, invoices are created from ASNs that have the status Shipped. The supplier can perform the following functions:

• Save – An invoice document with the status In Process is created, the data is saved but not yet sent to SAP MM. This document can subsequently be further processed and then sent.

• Cancel – The operation is terminated and entered data is not saved

• Invoice and send – A document with status Invoiced is created and the entered data is sent to SAP MM.

Receive Invoice in SAP MM

The purchasing organization will check and post the correct logistic invoice. In case of differences the incorrect invoice will be deleted and a request for a new and correct invoice will be send to the supplier.

Optional the invoice can be posted manually or via the Evaluated Receipt Settlement (ERS) in SAP MM if it is not intended to create the invoice in SAP SUS.

Evaluated Receipts Settlement (ERS)

SUS MM supports Evaluated ERS. The invoice is created automatically based on the posted goods receipt or the delivery.

The ERS invoice is sent to SAP SUS. Status of the document will be ‘accepted’ and will change to ‘paid’ when the payment has been received from the purchasing organization.

Implementation Remarks for the Standard Process Step ‘Order Response’

The creation of the Standard Process Step ‘Order Response’ can be done or switched off by the purchaser.

To deactivate or activate the Order Response Process the purchaser has to maintain the ‘order response expected’ flag in the purchase order.

Originally the default setting of the flag derived from the vendor master data.


© 2006 SAP AG

14

The following diagram shows all the business process steps covered in the Supplier Enablement

SUS-MM.


© 2006 SAP AG

15

Core Business Processes: Supplier Enablement SUS-EBP handled in different scenarios The Supplier Enablement SUS-EBP business scenario is a web-based scenario that provides full processing capabilities for services and material orders and integrates small or medium-sized suppliers into the procurement processes of large buying organizations. Such suppliers do not require their own sales systems to offer products and services. They just need internet access in order to use hosted order and content management functionality. The SUS-EBP business scenario deploys the supplier enablement capabilities of mySAP Supplier Relationship Management (SRM) with Supplier Self-Services (SAP SUS) and one or more SAP Enterprise Buyer (SAP EBP) systems for the procurement of materials and services. The entire procurement process can be handled in an Enterprise Buyer local scenario or in an extended classic scenario. In the local scenario the procurement process is solely performed in the Enterprise Buyer System. Only the financial accounting and controlling are still covered by the connected OLTP Backend system. In the extended classic scenario, the procurement process takes place locally in SRM but the data is replicated into the connected OLTP Backend systems.

The Supplier Enablement EBP-SUS comprises mainly the business process steps described as follows.

Supplier Registration Suppliers can register in one of three ways:

• If your purchasing organization has the necessary details on the supplier’s company, the supplier is automatically sent an e-mail containing an initial log-on ID and password.


© 2006 SAP AG

16

• You can invite suppliers to register themselves online, sending them an e-mail with a link to SAP SUS.

• Suppliers can register themselves on the homepage of your purchasing organization. Supplier Managed Content Before your purchasing organization can engage in a business relationship with a supplier, you require access to information about the supplier’s products or services. Supplier Enablement allows suppliers to upload new or modified product or service data for inclusion in the purchaser’s catalog. The data entry and maintenance screen in the SAP SUS system guides the supplier through the required fields. Data can either be entered manually or uploaded in the form of a comma-separated value (CSV) file. SAP provides a template file containing the required format. The use of CSV files enables a large number of data entries to be sent in a single operation. The SAP Exchange Infrastructure (SAP XI) converts the data provided by the supplier to XML format for use in SAP Enterprise Buyer. For more information on SAP XI, see below. The content manager at the purchasing organization must verify and approve the data before it can be included in the catalog.

Purchasing A purchase order (PO) is created in SAP Enterprise Buyer and triggers the creation of a sales order in the SAP SUS system. All document exchange between the SAP SUS system and SAP Enterprise Buyer takes place via the XI, using XML as the lingua franca. The seller logs on to SAP SUS, processes the sales order and then create a PO response (optional), which is forwarded to SAP Enterprise Buyer. If the PO response contains the same terms (items, quantities, delivery date, and so on) as the PO, it is automatically assigned the status Accepted by supplier in SAP Enterprise Buyer. If the supplier cannot meet all the terms specified in the original PO, and changes them, the purchaser may not agree to the changes, and decide to change them once again. In this case, the supplier receives a changed PO, and must send a new response. This cycle is concluded when both parties agree on the terms of the PO. Advanced Shipping Notification (ASN) An ASN is created in SUS and sent to EBP and the shipping information is attached to the PO.

Optional the creation of an ASN can be deactivated.

Confirmation When the goods ordered have been shipped, or the service performed, the supplier prepares one or a series of confirmation sheets. For orders that simply state the service type and total cost without including a breakdown of activities and materials (limit-POs for unplanned services or materials), confirmation sheets can be prepared by selecting and including the appropriate items from the catalog. This is possible due to an Open Catalog Interface (OCI) to the product and service catalog. The confirmation is sent to SAP Enterprise Buyer for confirmation or rejection by the purchasing organization. Generally, a workflow is initiated to obtain the necessary approvals. After approval, a confirmation response is sent to the supplier, who updates the status of the confirmation sheet.

Invoicing In the final step, the supplier creates an invoice, which the purchasing organization must verify and then approve or decline. This cycle is repeated until the purchaser and supplier agree on the content of the invoice. For legal reasons, the purchasing organization cannot modify an invoice received from the supplier. Invoices are created within the SAP SUS system (suppliers do not need a financial accounting system to do this). On approval, an invoice response is sent to the supplier, and the invoice status is updated. Optionally, the invoice can be created manually by the EBP employee, if the creation within SAP SUS is not intended or the invoice can be created automatically via the Evaluated Receipt Settlement (ERS).


© 2006 SAP AG

17

Evaluated Receipts Settlement (ERS) mySAP SRM also supports the evaluated receipts settlement (ERS) process – an automatic settlement procedure based on confirmations. The purchasing organization must have an agreement with the supplier concerned, under which the supplier does not create an invoice for each order transaction. Instead, the system automatically posts an invoice document based on the purchase order and confirmation. This eliminates invoice variances and communication errors, and speeds up completion of transactions. mySAP SRM sends the automatically generated invoice documents to the supplier electronically.

Due to the fact that there are small differences within the different scenarios (local, extended-classic and classic) and between the procurement process steps for indirect materials, services and plan-driven materials, a short summary of the standard process steps will be given under each graphical diagram. All the optional Business Process Steps described in the graphical overviews can be implemented in the way mentioned as follows:

Implementation Remarks for the optional Business Process Steps

To deactivate or activate the Order Response Process the purchaser has to maintain the ‘Order Response expected’ flag in the purchase order.

Originally the default setting of the flag derived from the vendor master data.

The same can be done for the following:

1. ASN

2. Confirmation expected from supplier

3. Invoice expected from supplier

4. ERS

The following diagram shows the business process steps of the locally handled Self-Service Procurement (indirect materials) within the Supplier Enablement EBP-SUS.:


© 2006 SAP AG

18

Summary of the Standard Process o Create Shopping Cart in EBP o PO to supplier, commitment data to FI/CO (IDoc) o ASN created in SUS and sent to EBP and information attached to PO o Employee creates confirmation in EBP o Invoice created in SUS and sent to EBP o Employee approves invoice in EBP o Invoice is posted to FI/CO for payment (IDoc)


o Activate Order Response

o Deactivate ASN

o Employee creates invoice

o ERS instead of invoice creation

The following diagram shows the business process steps of the locally handled Service Procurement within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

19

Summary of the Standard Process o Create Shopping Cart in EBP o PO to supplier, commitment data to FI/CO (IDoc) o Order Response from SUS to EBP


© 2006 SAP AG

20

o Confirmation is sent to EBP o Employee approves confirmation in EBP o Invoice created in SUS and sent to EBP o Employee approves invoice in EBP o Invoice is posted to FI/CO for payment (IDoc)

Implementation Remarks for the Optional Business Process Steps

o Deactivate Order Response

o Deactivate Confirmation Expectation

o Deactivate Confirmation from SUS

XML manipulation through BADI in EBP

Create confirmation in EBP (employee or centrally)


The following diagram shows the business process steps of the locally handled Planned-Driven Procurement within the Supplier Enablement EBP-SUS.:


© 2006 SAP AG

21

Summary of the Standard Process

o Requirement (services and MRO) sent to EBP from planning system (PM, PS) (XML interface available, R/3 coupling via RFC)

o PO to supplier (XML), commitment data to FI/CO (IDoc) o Requirement fulfillment set in planning system (XML interface available, R/3 coupling via RFC) o Order Response from SUS to EBP o Confirmation is sent to EBP (if at least one service or limit item)

Employee approves confirmation in EBP o ASN is sent to EBP (for material items only)

ASN information attached to PO Goods recipient creates confirmation

o Invoice created in SUS and sent to EBP o Employee approves invoice in EBP o Invoice is posted to FI/CO for payment (IDoc)


o Deactivate Order Response

o If Confirmation expected

Deactivate Confirmation Expectation

Deactivate Confirmation from SUS

XML manipulation through BADI in EBP

Create confirmation in EBP (employee or centrally)

o If ASN is expected


© 2006 SAP AG

22

Deactivate ASN

o Invoice created by employee


The following diagram shows the business process steps of the Self Service Procurement handled in the Extended Classic scenario within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

23

Summary of the Standard Process o Create Shopping Cart in EBP o PO to supplier, commitment data to FI/CO (IDoc) o PO copy to R/3 for further execution o Confirmation pre-entered by employee in EBP and after approval sent to R/3 MM as GR o Invoice pre-entered by employee in EBP and after approval sent to R/3 MM as logistics

invoice

Implementation Remarks for the optional Business Process Steps o Activate Order Response o ERS run started in R/3

The following diagram shows the business process steps of the Service Procurement handled in the Extended Classic scenario within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

24


o Create Shopping Cart in EBP o PO to supplier, commitment data to FI/CO (IDoc)


© 2006 SAP AG

25

o PO copy to R/3 for further execution o Order Response from supplier to EBP o Confirmation pre-entered by employee in EBP and after approval sent to R/3 MM as SES

(Service Entry Sheet) o Invoice pre-entered by employee in EBP and after approval sent to R/3 MM as logistics

invoice

Implementation Remarks for the optional Business Process Steps o Deactivate Order Response o Run ERS in R/3

Restrictions

A limit in a purchase order can only be used once.

One confirmation in EBP for every backend service item, the confirmation is used to create the SES (Service Entry Sheet) in Backend (Service and Material can not be handled together).

No final delivery and invoice flag for Services.

Confirmation and Invoice can be pre-entered in EBP but no time recording.

Structured items will not be transferred to R/3.


© 2006 SAP AG

26

The following diagram shows the business process steps of the Plan-Driven Procurement handled in the Extended Classic scenario within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

27

Summary of the Standard Process o Requirement (services, MRO and direct materials) sent to EBP from planning system (PM,

PS, MRP) (XML interface available, R/3 coupling via RFC) o PO to supplier (XML), commitment data to FI/CO (IDoc) o PO copy to R/3 for further execution

• For services: SES created in R/3 • For materials GR created in R/3

o Invoice created in R/3


o Activate Order Response

o Confirmation pre-entered by employee in EBP and after approval sent to R/3 MM as SES

o Invoice pre-entered by employee in EBP and after approval sent to R/3 MM as logistics invoice

o ERS creation in R/3

Optional with modification

(For materials only)

ASN is sent to EBP and information attached to PO and sent to R/3 creating new inbound delivery document routing to R/3 System over XI manually.

Invoice created in SUS and sent to R/3 as logistics invoice.

Mapping Partner ID’s.

The following diagram shows the business process steps of the Self-Service Procurement handled in the Classic scenario within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

28


o Shopping Cart transferred to R/3 MM via RFC as PR or PO o R/3 PO to supplier, commitment data to FI/CO (IDoc) o Order Response from SUS to R/3 o ASN is sent from SUS to R/3 creating new inbound delivery document o Confirmation pre-entered by employee in EBP and after approval sent to R/3 MM as GR o Invoice created in SUS and sent to R/3 as logistics invoice

Implementation Remarks for the Optional Business Process Steps o Order Response o GR created in R/3 manually o Invoice pre-entered by employee in EBP and after approval sent to R/3 MM as logistics

invoice o Invoice created in R/3 manually o ERS creation in R/3


© 2006 SAP AG

29

The following diagram shows the business process steps of the Plan-Driven Procurement handled in the Classic scenario within the Supplier Enablement EBP-SUS:


© 2006 SAP AG

30

Summary of the Standard Process o Requirements (only materials) as Purchase Requisitions in MM o R/3 PO to supplier, commitment data to FI/CO (IDoc) o Order Response from SUS to R/3 o ASN is sent from SUS to R/3 creating new inbound delivery document o Invoice created in SUS and sent to R/3 as logistics invoice

Implementation Remarks for the Optional Business Process Steps o Order Response o GR created in R/3 manually o Invoice created in R/3 manually o ERS creation in R/3


© 2006 SAP AG

31

Procedure

Monitoring Procedure: Business Process Supplier Enablement SUS-MM The core of this Best Practice is the monitoring concept for each business process step within Procurement. Under each business process step below, you will find the following information:

• A detailed functional and technical description of the process step • Monitoring activities for the process step • Relevant issues of error handling, restartability and escalation • A monitoring object table listing each relevant monitoring object, showing the:

o Monitoring object o Monitoring transaction or tool o Monitoring frequency o Monitoring time o Indicator or error o Monitoring activity or error handling procedure o Responsible team o Escalation procedure

In applying this Best Practice procedure, you create a company-specific process-oriented monitoring concept. This concept consists of monitoring activities to be performed for each business-process step and its respective monitoring objects.

When adapting this concept for your company, you must specify the times, responsible teams, and escalation paths (teams) for the monitoring activities associated with each business-process step and its monitoring objects. The following seems obvious but should nevertheless be mentioned: besides the monitoring of jobs described in the business process steps below, it is essential that you check all jobs that run in your system several times per day for abnormal termination (status “cancelled”, see Error Handling, Restartability and Escalation) and that you investigate and correct these terminations appropriately. This check can be done easily, for instance, with transaction SM37, by entering the time interval since the most recent check and selecting all jobs with status “cancelled”. If you have no automatic notification in place that informs the people responsible for Program Scheduling Management in your Support Organization of abnormally terminated jobs, you need to take measures to ensure that this is done manually in a reliable and timely manner.

Business Process Step 1: Create Purchase Order in SAP MM The purchase order document (for materials only) is created in SAP MM with transaction ME21N and sent to SAP SUS over the XI Interface. Within the XI Interface the mapping and routing into an XML Order (IDoc Type: Orders02) takes place and the XML Order is sent from the XI Interface to SAP SUS where a sales order document is automatically created. Even the PO has been sent to SAP-SUS it is changeable at any time. In this event a change PO is generated and sent to SAP-SUS. In SAP SUS the corresponding sales order is changed and its status is set to ‘changed by customer’ The vendor chosen in the purchase order needs to be defined as SUS vendor which mean that the vendor master data has to be assigned to the class Z_CRED_SUSMM_<SUS_BS>.


© 2006 SAP AG

32

The line item settings (Invoice receipt, GR based IV, ERS or Tax code in case of ERS invoice, over and under delivery tolerances) of the purchase order will taken as default values to the PO when an information record for the material or material group exist. In case the line item setting for invoice is put on ‘GR based IV’, a goods receipt has to be done before SAP SUS sends the invoice. Otherwise the incoming invoice IDoc will fail in SAP MM. To receive quantity changes on an order response it is necessary to define the over and under delivery tolerances in the line item settings. Separate line item ship-to-addresses can be entered in the line item tab ‘delivery address’ in the purchase order.

Monitoring Activities Apart from safeguarding the general availability of the system and software components OLTP System, XI and SAP-SUS SAP recommends the monitoring of objects listed in the following tables in order to ensure the creation of follow-up documents in the inherited systems.

OLTP System Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error

Monitoring Activity or Error Handling Procedure

Respon-sibility

Escalation Procedure

Statistical records for transaction ME21N

ST03 and STAD

weekly to be defined

Response time of transaction and of single statistical records

Check performance regularly.

Check single portion of response time (CPU, DB, GUI, RFC) in comparison to system load during the week.

Software Monitoring Team

Contact system administrator

OLTP System IDoc Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc Orders02

BD87 WE02 WE05

daily to be defined

Status of message type

Check for IDoc status on the OLTP System

Check for erroneous requests

Application Support

Contact business process champion

XI Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc Orders02

BD87 WE02 WE05

daily to be defined


Check for IDoc status on the XI System




Transaction

SXMB_MONI

SXMB_ MONI

Daily To be defined

Message status

Monitor of Processed XML Messages

Processing Statistics




© 2006 SAP AG

33

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Archived Messages

Job Overview

Persistence Layer Analysis

Status Monitor for Synchron. / Asynchron. Communication

Application Monitor (CCMS)

RZ20

Or

SolutionManager

At least once a day

to be defined

Alert Check the error frequency (number of error per minute)

Check message alerts by error code

Check the component monitoring status

Check the qRFC queues

Check the Java component monitoring

Check the Business Engine monitoring

Application support


Adapter Framework Monitor

http://<XIhost>:<port>/AdapterFramework/monitor/monitor.jsp

At least once a day

to be defined

Adapter Framework Status

Check the status of the Adapter Framework to make sure that all adapters are running properly



Runtime Workbench

Define a link on the Desktop:

http://<XIhost>:<port>/rwb)

from SAP-XI call TA:sxmb_ifr

At least once a day

to be defined

Sub screens

Component Monitoring:

Monitoring of ABAP and JAVA components

Monitoring the component connection status in a specific domain

Monitoring of the component parameter settings

Monitoring the ping of systems and sending of messages

Performance Monitoring

Monitoring of latency (processing time)

Monitoring of throughput

Alert Monitor (works only for XI)

Message alert (necessary configuration has to be done with transaction ALRTCATDEF )



Transaction

SLDCHECK

SLDCHECK To be defined

To be defined

Monitoring of settings within the System Landscape Directory




© 2006 SAP AG

34

Business Process Step 2: Receive PO in SAP SUS, create Sales Order and send Order Response (PO Response) The PO is transferred to SAP SUS over the XI Interface. The mapping and routing of the PO into an XML Order (IDoc type: Orders02) is done within the XI Interface. The XI Interface transferred the XML Order to SAP SUS and there a sales order with status New is created. The document number of the sales order is assigned when the sales order is processed within SAP SUS. Suppliers can display the sales order in the document list (using the search function if required), or they are sent an e-mail that contains a link to the sales order. The line item ship-to-address is displayed on item detail under ‘partner information’, ‘ship-to-party’ Depending on how the order response (PO response) is done, the status of the order response will be set to ‘accepted’, ‘partly accepted’ and ‘rejected’. An order response with quantity 0 is not allowed. In order to reject the entire document with all line items the function ‘reject and send’ has to be executed. Then all quantities are set to 0 and the document is rejected in SAP MM with a message in the IDoc inbound. Single line items can be rejected by deselecting the line items and executing the ‘accept and send’ functionality. A deselected item will show up with blank quantity when processing the order further. For rejected PO lines there is no indication in the PO (transaction ME23N) that the PO line was rejected. Changes to quantity on a sales order line item is handled as a change order and not as a partial order response. A ‘Reply to Purchaser’ is not supported in the MM-SUS scenario; the entered text is only visible in SAP SUS. The order response is sent from SAP SUS over the XI Interface to SAP MM. The XI Interface is doing the mapping and routing into an XML order (IDoc type: ORDRSP) In SAP MM the received order response is displayed in the purchase order at a line item level, visible on tab strip ‘confirmation’ starting with control key ‘AB’. In case the buyer is changing the PO response, the changed PO is sent over the XI Interface to SAP SUS. The mapping and routing into an XML order (IDoc type: ORDERS02) is done by the XI Interface and transferred to SAP SUS where a received changed PO is created. Now the sales order will be updated and a new PO response will be created. The PO response is sent over the XI Interface (IDoc type: ORDRSP) to SAP MM.

Monitoring Activities Apart from safeguarding the general availability of the system and software components OLTP System, XI and SAP-SUS SAP recommends the monitoring of the objects listed in the following tables in order to ensure the creation of follow-up documents in the inherited systems. In SUS normally no transactions are executed by the user directly. All programs are executed via Remote Funtion Call (RFC) from the Web Presentation Server (WPS). Therefore the monitoring activity should check the RFC response time of the function modules which are called via RFC and could have a critical input of the dialog response time.


© 2006 SAP AG

35

SUS Monitoring Monitoring Object Monitor

TA/Tool MonitorFreq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc:

ORDERS02,

ORDRSP

BD87,

WE02,WE05

daily to be defined


Check for IDoc status in the SUS system environment

Check for erroneous requests.

Software monitoring Team



Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc ORDRSP

ORDERS02

BD87 WE02 WE05

daily to be defined







RZ20

Or

SolutionManager

At least once a day

to be defined







Application support




At least once a day

to be defined





Runtime Work-bench



from SAP-XI call TA:sxmb_ ifr

At least once a day

to be defined

Sub screens Component Monitoring:









© 2006 SAP AG

36

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility






Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined




OLTP System IDoc Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc ORDRSP

BD87 WE02 WE05

daily to be defined




Application Support


OLTP System Monitoring (change PO process step) Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transaction ME22N

This transaction is related to checking and chang-ing of the shopping cart.

ST03 and STAD








© 2006 SAP AG

37

Business Process Step 3: Create ASN (Shipping Notification) in SAP SUS The supplier can select a sales order document and create an ASN by pressing the button ‘shipping notification’. The line items and quantities of the sales order will be accepted and the SUS ASN will default the accepted line item values. Deselect line items for which an ASN should not be done. A partial ASN can be done by changing the quantities of the line item. The ASN is sent over the XI Interface to SAP MM. The XI Interface is doing the mapping and routing into XML, IDoc type Delvry01. For the Buyer working in the SAP MM system it is not possible to send an ASN response to the SAP SUS system. Because of this the final document status of the ASN in SAP SUS is “sent”.

Monitoring Activities Apart from safeguarding the general availability of the system and software components OLTP System, XI and SAP-SUS SAP recommends to monitor the objects listed in the following tables in order to ensure the creation of follow-up documents in the inherited systems. In SUS normally no transactions are executed by the user directly. All programs are executed via RFC from the Web Presentation Server (WPS). Therefore the monitoring activity should check the RFC response time of the function modules which are called via RFC and could have a critical input of the dialog response time. SUS Monitoring Monitoring Object Monitor

TA/Tool MonitorFreq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc

DELVRY01

BD87, WE02, WE05

Daily To be defined


Check for IDoc status on the SUS system environment



Contact System Administrator


Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc DELVRY01

BD87 WE02 WE05

daily to be defined







RZ20

Or

Solution

At least once a day

to be defined


Check message alerts by

Application support



© 2006 SAP AG

38

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Manager

error code







At least once a day

to be defined





Runtime Work-bench




At least once a day

to be defined













Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined





© 2006 SAP AG

39

Business Process Step 4: Receive ASN (Shipping Notification) in SAP MM SAP SUS is sending the ASN over the XI Interface to SAP MM. SAP MM is receiving an inbound delivery and the goods receipt can be posted with reference to the delivery. The shipping notification in MM is displayed in the purchase order on line item level, tab strip confirmation with control key ‘LA’. SAP MM creates an inbound delivery number which can be referenced during goods receipt with transaction MIGO. OLTP System IDoc Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc DELVRY01

BD87 WE02 WE05

daily to be defined

Status of message



Application Support


Business Process Step 5: Goods Receipt in SAP MM The goods receipt is posted to the relevant warehouse.

In case of a goods return or partially goods return, the status of the ASN in SAP SUS is set to returned and a new ASN has to be manually created.

Further on the supplier has to be directly informed by the purchaser.

Monitoring Activities Apart from safeguarding the general availability of the system and the software component OLTP System SAP recommends the monitoring of the objects listed in the following tables in order to ensure the creation of follow-up documents in the inherited systems.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transaction MIGO

ST03 and STAD




Check single portion of response time (CPU, DB, GUI, and RFC) in comparison to system load during the week.

Software monitoring team



© 2006 SAP AG

40

Business Process Step 6: Create Invoice in SAP SUS In SAP SUS, invoices are created from ASNs that have the status Shipped. The supplier has to select the shipping notification in status shipped and press the button Invoice. Only line items which should not be part of the invoice have to be deselected. Partial invoices based on quantities can be done. The SUS invoice will default the line items and quantities corresponding to the ASN. After the invoice in SAP SUS is created and send over the XI Interface to SAP MM it is visible in the overview orders with status ‘invoiced’. Within the XI Interface the mapping and routing into an XML invoice, iDoc type invoic01 is done. Status ‘invoiced’ will be the final status of the payment in SAP SUS as SAP MM cannot send an invoice response to SAP SUS. SUS Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc

Invoic01

BD87 WE02 WE05

daily to be defined







Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc

Invoic01 BD87 WE02 WE05

daily to be defined







RZ20

Or

SolutionManager

At least once a day

to be defined







Application support




At least once a day

to be defined





Runtime Workbench


http://<X

At least once a day

to be defined



Monitoring the component connection status in a




© 2006 SAP AG

41

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Ihost>:<port>/rwb)


specific domain








Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined




Business Process Step 7: Receive Invoice in SAP MM The purchasing organization will check and posted the correct invoice. In case of differences the incorrect invoice will be deleted and a request for a new and correct invoice will be send to the supplier.

In SAP MM the invoice is visible under the purchase order history tab on item line level. OLTP System IDoc Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc Invoic01

BD87, WE05

daily to be defined

How many IDocs have been sent

Check status of incoming IDocs



ALE Interface Monitoring–Performance Outbound/Inbound Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


IDoc Invoic01

WE05, STAD

daily to be defined

Amount of sent IDocs

Processing time of IDocs from end-to-end

Average time required for processing an IDoc

Check status of incoming IDocs




© 2006 SAP AG

42

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Minimal/Maximal processing time

Business Process Step 8: Evaluated Receipts Settlement (ERS) SUS MM supports Evaluated Receipts Settlement (ERS). When ERS is in use there is an agreement with the vendor that no invoices for an order transaction are created.

Instead in SAP MM the invoice document is posted automatically based on the data in the purchase order and goods receipt or delivery.

The requirements for using ERS are that the ERS settings (Inv receipt, GR based IV, ERS and tax code) are defined in the PO line items under tab strip ‘Invoice’.

Necessary for posting the ERS invoice in SAP MM is that SAP SUS has sent the order response and the shipping notification.

The shipping notification creates an inbound delivery in SAP MM and the inbound delivery number can be referenced during goods receipt via transaction MIGO.

The ERS invoice is send to SAP SUS and there it is displayed with the MM ERS document number. Status of the document will be ‘accepted’ and will change to ‘paid’ when the payment has been received from the purchasing organization. The ERS invoice can only be displayed in SAP SUS, no further processing is possible.

In SAP MM the ERS invoice is displayed in the purchase order, tab strip purchase order history (transaction ME23N).

Monitoring Activities for posting invoice via ERS Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Report RMMR1MRS

ST03 and STAD








© 2006 SAP AG

43

Monitoring Procedure: Business Process Supplier Enablement SUS-EBP

Business Process Step 1: Create Shopping Cart The EBP Procurement scenario is called by a user via a URL or by clicking on a hyperlink in a Web browser. The procurement application (SAP transaction BBPSTART) starts with the Login process on the ITS and EBP system. After login, the user starts shopping by selecting a corresponding button or via the entry Shop in the menu tree within the browser screen, which triggers the creation of the shopping cart.

In the Shop application, three navigation interfaces have been developed with different types of user in mind. These three navigation interfaces are called Wizard (SAP Transaction BBPSC02), Extended Form (SAP Transaction BBPSC01) and Simplified Form (SAP Transaction BBPSC03).

Purchasing assistants and purchasers can buy products on behalf of other users, for example, their manager. Shopping on behalf can only be used with the Extended Form (SAP Transaction BBPSC01).

For purchasing with Limit as well only the Extended Form (SAP Transaction BBPSC01) can be used. In general a user can fill a shopping cart in various ways:

• Individual Catalog Search: User can search for products in individual catalogs or use a manual search, before transferring individual items or even entire shopping carts from old purchase orders and templates to your new shopping cart.

• Cross-Catalog Search: The catalogs that support cross-catalog searches are displayed in a separate field. You can enter a search term and start the search.

• Special Request: If you have not been able to find an appropriate product in the catalogs, you can enter a description of the required goods or services.

The user may choose the tab strip Catalog in the EBP system and click on one of the listed catalogs. Control is passed from the EBP system to the catalog. In the catalog, the user searches a specific product, adds the product to the shopping cart and orders the product. Control is passed from the catalog back to the EBP system. The data transfer between the EBP system and the catalog is conducted by Open Catalog Interface (OCI). Depending on product specification and customizing, relevant business functions such as Account assignment check, Source determination, Budget check or Determination of Source of Supply are executed in the connected OLTP backend system. Because of the integration between the EBP system and the OLTP backend system, synchronous RFC communication plays an important role. With EBP 4.0 and 5.0 it is necessary to use the Internet Pricing and Configurator (IPC). During customizing of the SAP EBP system, you define whether the shopping cart needs to be approved:

• If an approval is required, the person responsible for approving the shopping cart is informed via workflow. A work item is sent to his inbox.

• If an approval is not required, the system creates the follow-up documents from the shopping cart. These documents can be purchase requisitions, purchase orders and/or reservations. The type of document to be created in a particular system depends on the settings in the SAP EBP system and the information in the shopping cart. If, for example, the follow-up documents are to be created in the OLTP system, you can specify that the system should always create a reservation (if the material is available from the company’s own stock) or that a particular material is always procured externally.

When information is missing from shopping carts (purchase orders) created locally in the Enterprise Buyer system, for example, the vendor has not been specified, the purchaser receives the purchase order in their work list for completion.


© 2006 SAP AG

44

Monitoring Activities for the created shopping carts Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, IPC, catalog server and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure that the business step ‘Create Shopping Cart’ can be performed.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transactions BBPSTART and BBPSC01, BBPSC02, BBPSC03

These transactions are related to business step Create Shopping Cart.

ST03 and STAD

Weekly to be defined






Application monitor Others

This monitor provides a list of errors related to the Catalog.

RZ20 or Web Browser

Hourly to be defined

Alert Check for alerts that are related to the Catalog.

Choose error message from list to get a set of available tools for error processing (browser-based only).

Application support


Error Handling, Restartability, and Escalation See the general issues of Error Handling, Restartability and Escalation, below.

Business Process Step 2: Approve Shopping Cart If the shopping cart has to be approved by one or more supervisors (for example, when exceeding a specific value limit), the system automatically submits it to the inbox of the person responsible via the Web-compatible workflow (optionally using email). The supervisor can approve or reject the request. If the shopping cart is approved, the follow-up documents are created. If the supervisor rejects the request, a message is sent to the employee’s inbox, explaining the reason for the rejection. Then the employee can process the shopping cart again.


© 2006 SAP AG

45

Monitoring Activities Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure that the business step ‘Approve Shopping Cart’ can be performed.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transaction BBPBWSP

This transaction is related to the approval step per-formed by a manager.

ST03 and STAD







Application Monitor Approval

This monitor provides a list of errors caused by approval processing.

RZ20 or Web Browser

hourly to be defined

Alert Check for alerts that are related to approval of shopping carts.


Application support


Application monitor Shopping Cart

This monitor provides a list of errors related to a shopping cart.

RZ20 or Web Browser

hourly to be defined

Alert Check for alerts that are related to approval of shopping carts.


Application support



Business Process Step 3: Check Shopping Cart Status and Change Shopping Cart Employees can check the status of the shopping cart and the individual items in the shopping cart. They can see, for example, whether the request has already been approved or whether the quantity ordered has already been delivered. They also have the option of deleting shopping carts that are no longer required. There are restrictions regarding the deletion of items. For example, you cannot delete an item if the purchase order has already been sent to the vendor and or goods receipt has been entered for it.

In the Check Status application the search for shopping carts can be done by using various criteria, such as shopping cart name, creation timeframe or status.


© 2006 SAP AG

46

Monitoring Activities Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, IPC, and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure the business steps ‘Check Shopping Cart Status’ and ‘Change Shopping Cart’.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transaction BBPSC04

This transaction is related to checking and chang-ing of the shopping cart.

ST03 and STAD








Business Process Step 4: Create Purchase Order (SAP EBP), create Sales Order and send Order Response (SAP SUS) The purchase order (PO) document (for services and indirect material orders) is created in SAP EBP. In the EBP PO document the ship-to-address and vendor texts can be entered per line item. The EBP system sends the purchase order to SAP SUS via the XI interface and in SAP SUS as the sales order is created. Within the XI Interface a simple conversion of the non-XML business purchase order data to XML business data is done. The seller logs on to SAP SUS and checks the overview for orders. The created orders are listed there with status New. A document number will be assigned when the order is processed within SAP SUS. EBP purchase order header text information is displayed as purchaser information at header level of the sales order. The item text information is displayed at the line item detail of the sales order. The seller processes the sales order, and creates a PO response. Important information for the purchaser can be entered on the header in the field reply to purchaser. Deselect line items of the sales order that should not be transferred into an order response. The processed and sent sales order is forwarded to SAP EBP via the XI interface. The XI interface is doing the mapping and routing of non-XML business data into XML business data. In EBP the purchaser receives a received PO response. If the PO response contains the same terms (items, quantities, delivery date, and so on) as the PO, it is automatically assigned the status Accepted by supplier in SAP Enterprise Buyer. If the supplier cannot meet all the terms specified in the original PO he/she may change the terms. This may result in the purchaser not agreeing to the changes and the purchaser could decide to change PO terms once again. In this case, the supplier receives a changed PO, and must send a new response. This cycle is concluded when both parties agree on the terms of the PO.


© 2006 SAP AG

47

Monitoring Activities for the created Purchase Orders Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, IPC, catalog server and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure that the business step ‘Create Purchase Order’ can be performed.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transactions BBPPO01, BBPPO02

ST03 and STAD

Weekly to be defined






Application monitor Others

This monitor provides a list of errors related to the Catalog.

RZ20 or Web Browser

Hourly to be defined

Alert Check for alerts that are related to the Catalog.


Application support



Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



RZ20

Or

SolutionManager

At least once a day

to be defined







Application support




At least once a day

to be defined





Runtime Workbench


http://<X

At least once a day

to be defined



Monitoring the component connection status in a




© 2006 SAP AG

48

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Ihost>:<port>/rwb)


specific domain








Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined




SUS Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Message Interface Inbound:

PurchaseOrderCancellationRequest_In (InterfaceII_BBPX1_SUSPO_CANCEL_REQU_IN)

PurchaseOrderChangeRequest_In (InterfaceII_BBPX1_SUSPO_CANCEL_REQU_IN)

PurchaseOrderRequest_In (InterfaceII_BBPX1_SUSPO_IN)

ST03, ST05, STAD

daily to be defined







© 2006 SAP AG

49

Business Process Step 5: Creating Goods Receipt in SUS / EBP When the goods ordered have been shipped, or the services performed, the supplier can create confirmation sheets for those sales orders that have status accepted.

The items and quantities of the confirmation will default to the items and quantities of the corresponding sales order.

The confirmation can be done on a single line item. Deselect line items that should not be confirmed.

Partial confirmation based on quantities too.

The confirmation sheets are sent to EBP via the XI interface. In EBP the confirmation sheet can be confirmed or rejected by the purchaser.

When the confirmation sheet has been confirmed by the purchaser an approval workflow is initiated to obtain the necessary approval.

After the approval a confirmation response is sent to SAP SUS via the XI interface. In SAP SUS the status of the sales order is updated into confirmed. The mapping and routing of the non XML business data into XML business data are always done within the XI interface. SUS Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



ServiceAcknowledgementConfirmation_In (InterfaceII_BBPX1_SUSCONF_CONF_IN)

Message Interface Outbound

PurchaseOrderConfirmation_Out (KlasseCO_BBPX1_SUS_PCO_OUT)

DespatchedDeliveryNotification_Out (KlasseCO_BBPX1_SUSDDN_OUT)

ST03, ST05, STAD

daily to be defined







© 2006 SAP AG

50


Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



RZ20

Or

SolutionManager

At least once a day

to be defined







Application support




At least once a day

to be defined





Runtime Workbench




At least once a day

to be defined













Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined





© 2006 SAP AG

51

Monitoring Activities for the creation of Goods Receipt and Approval Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, IPC, catalog server and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure that the business step ‘Creation of Goods Receipt’ and ‘Approval of Goods Receipt’ can be performed.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transactions BBPCF01, BBPCF02, BBPCF04

ST03 and STAD







Business Process Step 6: Creating Invoice in SUS / EBP In SAP SUS the supplier creates an invoice which the purchasing organization in the EBP system has to verify and approve or to decline. An invoice can be created in SAP SUS directly from a sales order or from a confirmation depending whether the purchasing organization in EBP is expecting a confirmation or not. On the ‘Overview Order’ the order or the confirmation has to be selected and the ‘invoice’ button has to be pressed. Line items for which invoice should be done have to be selected. The SAP SUS invoice will default the line items and quantities of the corresponding document (sales order or confirmation). A partial invoice based on quantity can be done. In the ‘Overview Order’ the invoiced will be displayed with status ‘invoiced’. The Invoice is sent to SAP EBP via the XI interface where the mapping and routing of the non XML business data into an XML invoice is done. In SAP EBP the purchase organization has to verify and approve or decline the incoming invoice. An invoice response is sent from SAP EBP to SAP SUS via the XI interface. The XI interface is doing the mapping and routing into an XML invoice response. In SAP SUS the incoming invoice response is updating the invoice status accordingly into ‘accepted’. SUS Monitoring Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



InvoiceConfirmation_In (InterfaceII_

ST03, ST05, STAD

daily to be defined

Response time of transaction and of single statistical


Check single portion of response time (CPU, DB, GUI, RFC) in comparison to system load during the




© 2006 SAP AG

52

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


BBPX1_SUSIV_Confirmation_In)

InvoiceRequest_In (InterfaceII_BBPX1_SUSIV_In)

Message Interface Outbound

InvoiceRequest_Out (KlasseCO_BBPX1_SUSIV_Out)

records

week.


Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



RZ20

Or

SolutionManager

At least once a day

to be defined







Application support




At least once a day

to be defined





Runtime Workbench




At least once a day

to be defined











© 2006 SAP AG

53

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility





Transaction:

SLDCHECK

SLDCHECK

To be defined

To be defined




Monitoring Activities for the Approval of incoming invoices Apart from safeguarding the general availability of the system and software components SAP EBP system, OLTP System, ITS, IPC, catalog server and web server SAP recommends the monitoring of the objects listed in the following table in order to ensure that the business step ‘Approval of Invoice’ can be performed.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Statistical records for transactions BBPIV04

ST03 and STAD







Further Information

Troubleshooting If executing this Best Practice did not produce the desired results,

• Search for related notes in the SAPNet. • Open an SAP Customer Message describing your problem.

Literature • For detailed information on how to administer an SAP R/3 system, see the book: Liane Will, SAP R/3 System Administration

• For information on how to monitor and tune the general system performance, see the book: Thomas Schneider, SAP R/3 Performance Optimization

• For background information on administrative tasks with a special emphasis on the system planning and set-up process, see the book:

Hartwig Brandt, SAP R/3 Implementation with ASAP


© 2006 SAP AG

54

Background Information and References

Integrated Internet Transaction Server (ITS 7.00) As of SAP NetWeaver 04, ITS is now available integrated with the NetWeaver component, SAP Web Application Server 6.40, as an Internet Communication Framework (ICF) service. Like other services, it can be accessed through the Internet Communication Manager (ICM).

With ITS integrated with the SAP Web Application Server, the web browser now communicates directly with the SAP System. Furthermore, all ITS-related sources, such as service files, HTML templates or MIME files, are now stored in the system's database, similar to ABAP sources.

The Integrated ITS can only be used to run SAP GUI for HTML and Internet Application Components (IAC) of the SAP System it is part of. Therefore there are no longer questions in regards to downward or upward compatibility. Since the Integrated ITS consists of executables being part of the Kernel and templates, MIMES, etc. being part of SAP_BASIS you can only use the Integrated ITS if you have both SAP Web AS Kernel 6.40 and SAP_BASIS 6.40 or higher installed.

The Integrated ITS is part of the SAP Web AS Kernel CD delivery.

For details on ITS 6.40, see SAP Note 709038

For details on ITS Maintenance Strategy, see SAP Note 197746

For details on ITS 7.00, see SAP Notes 890606

Internet Pricing and Configurator From Release 3.5, SAP Enterprise Buyer uses the condition technique for pricing in purchasing processes. Pricing takes place in the system component Internet Pricing and Configurator (IPC) that is installed together with SAP Enterprise Buyer for this purpose. In the shopping cart, automatic pricing takes place with reference to the document date. This occurs whenever an item is added or whenever the product, quantity, quantity unit, contract, vendor or price of an existing item changes. The system does not display a document. The shopping cart displays the net and gross price. The task of the IPC server is to execute sequences of commands in a defined context (a session). It acts as an RFC server by receiving pricing requests from clients (e.g. the EBP system). The IPC Server reads the request string and executes the command. It encodes and generates a response object, transforms it into a string and sends it back to the client. The server is being used for a variety of different tasks like pricing and tax calculation. Important fact: For SRM 5.0 ‘old’ IPC Versions can not be used anymore. To apply a new IPC 7.00 support package no specific IPC steps are necessary. The IPC is upgraded just by upgrading your system to the newest SAP AP 7.00 support package. The 7.00 IPC is able to access an ERP, CRM or SRM database directly – no local IPC database or IPC dataloader for data model conversion is necessary. For supported IPC platforms see http://service.sap.com/PAM For setting up an IPC on an unsupported platform, see SAP Note 855455

Internal Catalog (CCM 2.0) The internal Catalog (SAP CCM 2.0) is a single ABAP-based Add-On to the SAP Web Application Server (Web AS 7.00). It consists logically of two applications, which are the Catalog Authoring Tool (CAT) and the Catalog Search Engine (CSE).

The Catalog Authoring Tool is used by the Content Managers for managing the structures and contents of catalog.

The Catalog Search Engine enables the fast and sufficient read-only access to published catalogs.


© 2006 SAP AG

55

Several internal Catalogs can be connected to a single Catalog Search Engine and vice versa.

The Catalog Search Engine requires the installation of TREX (Text Retrieval and Extraction) 7.0.

Graphical Overview of the possibilities how to install the Internal Catalog (CCM 2.0):

Distributed Deployment Based on Three Separate Installations


© 2006 SAP AG

59

Monitoring Activities Apart from safeguarding the general availability of CCM2.0 SAP recommends to monitor the upload, editing and publication process in SAP Catalog Authoring Tool as well as in the Catalog Search Engine. Monitoring transactions that can be used are listed in the following table.

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


ST03 and STAD

Depends on the time frame of upload, editing and publication process

to be defined

Response time of trans-action and of single statistical records



Software monitoring team or Content Manager

Contact system administrator or Contend Manager

ST04

ST05

Depends on the time frame of upload, editing and publication process

To be defined

Expensive Statements in Shared Cursor Cache

Identify expensive SQL statements in Shared Cursor Cache



SLG1 Depends on the time frame of upload, editing and publication process

To be defined

Log entries in status ‘Error’ (red traffic lights)

Use logs to determine whether uploading, editing and publication process was successful or not. Determine the cause of error.



SAP Exchange Infrastructure 7.0 (SAP XI 7.0) SAP Exchange Infrastructure (SAP XI) enables customer to implement cross-system processes. SAP Exchange Infrastructure is based on general standards so as to enable external systems to be integrated. At the center of the infrastructure is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in user-defined eXtensible Markup Language (XML) schema from the sender to the receiver using the Integration Server.

SAP XI supports the following methods of communication with the Integration Server:

• ● Direct communication using proxies, which you generate in the application systems using a description in Web Service Description Language (WSDL).

• ● Communication using adapters. In this case, you create interfaces for message exchange in the application system, or use existing interfaces.

The following graphic shows XI components within SAP NetWeaver:


© 2006 SAP AG

61

Design time and configuration time each have a central data storage point providing an overview of all data that is relevant to the cross-component process: the Integration Repository and the Integration Directory respectively. To edit this data, you use a single tool, the Integration Builder. The content of the Integration Repository and Integration Directory is known as collaboration knowledge. The Integration Server is the central ‘distribution engine’ for messages in SAP Exchange Infrastructure at runtime. All systems that use SAP Exchange Infrastructure to communicate use this server to exchange messages. These systems are referred to as business systems at a logical level; within a specific system landscape they are called technical systems or communication parties. Using the configuration data from the Integration Directory, the Integration Server decides to which receiver or receivers it must send the message and whether a mapping needs to be executed beforehand.

EBP Application Monitors

SAP delivers EBP with a special monitor set SAP B2B Procurement-Monitors. In the set there are application monitors for various parts of the EBP process that can be used via SAPGUI using transaction RZ20 (choose node ‘SAP Enterprise Buyer Monitors’) or via web browser using the BBPSTART service with an administrator user. Both possibilities show exactly the same. These monitors show only messages in case of an alert. They do not show messages when everything is all right. For the procurement process with SAP EBP the following monitors are of special importance:

Approval - Starting conditions - Approver assignment - Other errors

Confirmation - Backend goods receipt errors - Backend service entry errors - Local errors - IDoc communication errors - Spooler communication errors

Invoice - Backend invoice errors - Backend commitment errors - Local errors - IDoc communication errors

Others - Catalog

Shopping Cart - Backend application errors - Local errors - Spooler communication errors - Not transferred to backend

Purchase Order - IDoc communication errors - Backend application errors - Output errors - Local errors - Planning system errors


© 2006 SAP AG

62

You start the application monitors during the installation of your Enterprise Buyer system. To activate the application monitors, use the Implementation Guide (IMG) and choose 'Enterprise Buyer professional edition' -> 'Technical Basic Settings' -> 'Start Application Monitors'. In order to prevent errors related to the use of the application monitors, we recommend that you keep the support packages of the EBP system up-to-date. In case you encounter problems related to the application monitor functionality, please open an R/3 Frontend message on component SRM-EBP-APM.

Feedback and Questions Send any feedback by formulating an R/3 Frontend message on message to component SV-GST-SMC. You can do this at http://service.sap.com/message.


© 2006 SAP AG

63

Appendix This Appendix explains:

1. Basic Monitoring Guidelines for the SAP EBP system and the SAP R/3 OLTP System 2. Basic Monitoring Guidelines for an SAP EBP system 3. Basic Monitoring Guidelines for the ITS and Web Server 4. Basic Monitoring Guidelines for the Business Connector 5. Basic Monitoring Guidelines for the Catalog 6. Basic Monitoring Guidelines for the Frontend and Network

Basic Monitoring Guidelines for the SAP EBP system and the SAP R/3 OLTP System For the administration of a SAP R/3 OLTP system as well as for the R/3 basis of a SAP EBP system, there are a number of jobs and monitoring activities we strongly recommend scheduling and supervising on a regular basis. The following list is not complete, especially jobs and tasks for the database administration (such as backups, archiving transaction logs, update statistics for cost base optimizer and so on) are not mentioned, however it gives you an impression of what you have to do in order to keep a system running. As part of the SAP Basis these monitors do not display any EBP specific monitoring data. They should be analyzed using the same procedures as those used in a non-EBP system environment. If you have further questions on these subjects, please refer to the Solution Management Optimization Service System Administration. Schedule Reorganization Jobs There are a number of jobs that must run periodically in a live R/3 installation, for example to delete outdated jobs or spool objects. As of Release 4.6C, you can easily schedule these jobs automatically as follows: Execute transaction SM36, choose Goto -> Standard jobs from the menu bar. For details and comments, see SAP Note 16083.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


R/3 System workload analysis

ST03 daily tbd Average dialog response time < 1000 ms

Review response times in comparison to system load and performance influencing changes within the system of the analyzed period.

Identify and improve performance of any transaction whose response time exceeds the times defined in the Service Level Agreement (SLA), if existing.



Database perform-ance Analysis

ST04 weekly tbd Expensive SQL statements

Monitor database statistics.

Check for missing indices, ensure that the data quality is sufficient, and that there is sufficient space available.




© 2006 SAP AG

64

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Operating system monitor

ST06 hourly tbd High paging rate and CPU utilization

Monitor the CPU and memory consumption.

A hardware bottleneck can have a negative impact on the overall response time as well as the response time of an individual business transaction.



R/3 System buffer monitor

ST02 weekly tbd Swaps To ensure optimal performance check that the R/3 parameters are set correctly with transaction ST02.

Incorrectly sized R/3 buffers or memory allocation can result in poor performance. One such example would be when a work process enter PRIV mode.



Local work process overview

SM50 hourly during peak hours

tbd WP status, WP utilization

Monitor current state of individual work processes. Ensure that enough work process capacity is available at peak times.



System-wide work process overview

SM66 hourly during peak hours

tbd WP status, long running jobs

Similar to SM50 but for system-wide statistics.



Database perform-ance monitor

DB02 daily tbd Table space sizes, table indices for tRFC and aRFC

Ensure that the data quality is sufficient, that there are no missing indexes, and that there is sufficient space available.



ABAP dump analysis

ST22 daily tbd Dumps Check short dumps, analyze aborted programs.

Select a period and click on the List button. Select an error, and then choose Display to see the short dump.

For SAP developed programs that experience frequent terminations, investigate SAPNet for a possible resolution and if necessary open a customer message. For customer developed programs contact the appropriate member of the development team.



System log SM21 daily tbd Entries Check for general system program errors and table space errors or transactions that encounter errors.

Maintain date/time and select Reread system log. Position cursor on a time, and then choose Display.




© 2006 SAP AG

65

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Update tasks

SM13 daily tbd Status Check for entries that have status ‘ERR’.

Update records should be monitored regularly and the appropriate user should be contacted immediately to resolve any outstanding updates. Together with the user, determine whether the update request can be re-started or has to be deleted.



Report RSBTCDEL This report deletes all logs for successfully completed jobs.

SM37 Job Log

daily tbd Status Check if job is running as scheduled. Refer to the Job Log in case of error.

If the report is not scheduled on a regular basis, schedule it to run once a day.

Program scheduling manage-ment

Contact software monitoring team

Report RSPO0041or RSPO1041 (additional functions)

This report deletes obsolete spool objects.

SM37 Job Log



See SAP Note 130978 for details.



Report RSPO1043 This report deletes spool lists, which are remnants of cancelled jobs.

SM37 Job Log



See SAP Note 98065 for details.



Report RSBDCREO This report deletes logs of back-ground input processes.

SM37 Job Log





Report RSBPSTDE This report cleans up the run-time statistics of background jobs.

SM37 Job Log

monthly tbd Status Check if job is running as scheduled. Refer to the Job Log in case of error.

If the report is not scheduled on a regular basis, schedule it to run once a month.




© 2006 SAP AG

66

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Report RSCOLL00 This report collects the general statistical data for R/3 perform-ance analysis.

SM37 Job Log


If the report is not scheduled on a regular basis, schedule it to run every hour.



Report RSBPCOLL This report collects the statistical data to analyze the average run time of periodically executed jobs.

SM37 Job Log





Report RSSNAPDL This report deletes short dumps that are older than six days.

SM37 Job Log





Error Handling, Restartability and Escalation

Error Handling Procedures In case of failure of one of the jobs scheduled, if one of the necessary jobs is not scheduled, or even if a scheduled job has finished check for the current job status (refer to SAP R/3 documentation CD, component BC-CCM, chapter background processing) and proceed as follows: • In case of status scheduled, the job steps have already been defined, but the start condition

has not yet been defined. Contact the program scheduling management in order to clarify when the job will be fully defined.

• In case of status released, the job has been fully defined including a start condition and waits for the condition to fulfill.

• In case of status ready, the start condition of a released job has been met. A job scheduler has put the job in line to wait for an available background work process.

• In case of status active, the job is currently running and cannot be modified or deleted anymore. Check if the job is within the given timeframe, depending on the data volume to be processed. Check for particular dependencies on other jobs. If the job exceeded the given timeframe, contact the software monitoring team.

• In case of status finished, all steps that make up this job have completed successfully. Program scheduling management has to check whether the job ran in the given timeframe, and software monitoring team and / or application support have to check the respective job results (such as spool output lists, message logs, updates, etc.).

• In case of status cancelled, the job has terminated abnormally, which can happen in two ways. If an administrator intentionally cancelled the job, clarify why he did so and whether (and if, when) the job has to be re-run. If a program in a job step produced an error such as issuing an ‘E’ or ‘A’ error message,


© 2006 SAP AG

67

contact the software monitoring team and investigate why the error occurred. In case of an SAP standard program search for appropriate messages in SAPNet and open a customer message, if you cannot solve the problem.

Process Step Restartability In case of the cancellation of a background job, possible succeeding jobs or dependencies on other jobs must be considered when restarting the aborted job. The start of succeeding jobs might be also delayed due to the restart of the aborted job.

Escalation Procedures In general, it is recommended to search for related SAP Notes in the SAPNet R/3 front-end system for any unknown problems or errors. In case of questions or problems that cannot be solved, forward the issue to the next support level. If the corresponding escalation path is not well defined, contact the Application Support. If it is not possible for any of the defined support levels to provide a solution for a particular problem, it is recommended to open a customer problem message in the SAPNet R/3 front-end system.

Basic Monitoring Guidelines for an SAP EBP system Apart from the general administrative tasks for an R/3 System (see section above) there are several important monitoring objects in the SAP EBP system that have to be controlled regularly.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Report CLEAN_REQREQ_UP

This report updates status tables on follow-up objects in the OLTP system.

SM37 Job Log

daily tbd status Check if job is running as scheduled. Refer to the Job Log in case of error.

If the report is not scheduled on a regular basis, schedule it to run at least once a day. If required by your business process, schedule it to run more often.

This report should be finished before you start report BBP_GET_STATUS_2 and BBP_GET_STATUS respectively (for SAP EBP 2.0C)



Report BBP_GET_STATUS_2 and BBP_GET_STATUS respectively (for SAP EBP 2.0C)

This report checks, if there have been changes at the documents in the OLTP System.

SM37 Job Log

daily tbd status Check if job is running as scheduled. Refer to the Job Log in case of error.

If the report is not scheduled on a regular basis, schedule it to run at least daily, but not more often than once every 5 minutes.

Schedule report to run after report CLEAN_REQREQ_UP has finished.



Report RHBAUPAT

SM37 daily tbd status Check if job is running as scheduled. Refer to the Job

Program scheduling

Contact software


© 2006 SAP AG

68

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


(SAP EBP 2.0C) and HRBCI_ATTRIBUTES_BUFFER_UPDATE (SAP EBP 3.0) This job allows buffering of the organizational structures in a cluster table.

Job Log Log in case of error.

If the report is not scheduled on a regular basis, schedule it to run once per day after midnight.

See SAP Notes 354787.and 110909.

manage-ment

monitoring team

Report RSWUWFMLEC

This report handles the email dispatch of work items.

SM37 daily tbd status Check if job is running as scheduled. Refer to the Job Log in case of error.




Report SMO6_REORG This report reorganizes the trace tables.

SM37 daily tbd status Check if job is running as scheduled. Refer to the Job Log in case of error. If the report is not scheduled on a regular basis, schedule it to run once a day. See SAP Note 206366.



Report RBDMOIND

SM37 daily tbd status Check if job is running as scheduled. Refer to the Job Log in case of error. If the report is not scheduled on a regular basis, schedule it to run several times a day.



Size of tRFC tables ARFCSSTATE ARFCSDATA ARFCRSTATE Large tables may result in poor performance for tRFC processing.

DB02 Weekly Upon error

tbd size Check and monitor table size and indices regularly and take administrative actions if necessary. If table sizes are larger than 500MB, reorganize table and decrease its size. See SAP Note 375566.



Error Handling, Restartability, and Escalation Regularly apply SAP Note 375330 concerning procurement performance. See also the general issues of Error Handling, Restartability and Escalation, above.


© 2006 SAP AG

69

Basic Monitoring Guidelines for the ITS 6.40 and ITS 7.00 No separate administration tools are needed anymore for the integrated ITS 6.40 and ITS 7.00. The Admin Tool does not exist any longer. The integrated ITS 6.40 and ITS 7.00 can administer completely with the following SAP Basis tools:

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Responsibility


How to do the monitoring/ Monitoring of

TransactionRZ10 and RZ11

Definition of Profile Parameters

To be defined

To be defined



Viewing of correct Profile Parameter settings

TransactionST11

Error Log Files daily To be defined



To activate ITS tracing, run program rstrc000 (use transaction SE38), set the Trace level to an appropriate value (2 or 3), check WebGui, and enter Save. Then, reproduce the problem you are trying to get traces for, return to rstrc000, reset to the default values (Default val. button), save and use the Display button to view the trace file. Search for the string “SAP GUI for HTML” in the traces.

Transaction ,ST22

Runtime Errors daily To be defined



Check short dumps, analyze aborted programs.

Select a period and click on the List button. Select an error, and then choose Display to see the short dump.

For SAP developed programs that experience frequent terminations, investigate SAPNet for a possible resolution and if necessary open a customer message. For customer developed programs contact the appropriate member of the development team.

Transaction ST05

Performance Analysis

daily To be defined



Check of Performance Time

TransactionSM21

System Log daily To be defined



Check for general system program errors and table space errors or transactions that encounter errors.

Maintain date/time and select Reread system log. Position cursor on a time, and then choose


© 2006 SAP AG

70

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Responsibility


How to do the monitoring/ Monitoring of Display.

Transaction SMICM

ICM Monitor daily To be defined



Program SITSPMON

BHTML runtime measurement

daily To be defined



Measurement of BHTML runtime

Transaction SITSPMON

Actual memory consumption of an ITS application

Estimate size of the prepared tree using this application

daily To be defined



Can be called as own transaction as of NetWeaver 04 SP 4. Prior to this support package use se38 → sitspmon

ABAP Runtime Analysis

Measurement for Kernel Times

daily To be defined



Measurement of the Kernel Time

TransactionSICF

Configuration of the ITS-ICF-services

To be defined

To be defined



Transaction STAD, ST03N

Or Program RSSTATISTIC

Statistical records of the Internet Communication Framework and Workload Statistics

daily To be defined



Statistical records and Workload statistics

Activation:

ST03N -> Choose role "Expert mode“. Then choose in left tree “Collector and Performance DB" -> "Statistical records & file" -> "Online Parameters" -> "Dialog Step Statistics" -> Delete entry "PLUGIN" in column "rdisp/no_statistic".

ST03N -> Choose role "Expert mode“. Then choose in left tree “Collector and Performance DB" -> “Workload Collector” -> “Statistics to Be Created” -> “Web Application Server Statistics”: Choose one of the 3 options to select the summarization level.

Afterwards, you can monitor the statistical records of the Internet Communication Framework in ST03N and STAD under task type “HTTP”.

Important: Statistical records are written only, if an SAP work process is used. (Example: If the ICMAN handles a request from its Server Cache, no statistical record is written

Alternatively you can use the report „RSSTATISTIC“


© 2006 SAP AG

71

Related SAP Education Training Opportunities: http://www.sap.com/education/ Related Workshops: PRTL255, Migration of Existing ITS Services from Standalone to Integrated SAP Internet Transaction Server SCUR201, SAP Infrastructure Security PRTL102, UI Clients for SAP Netweaver’04 Useful SAP Notes: 517484- Inactive Services in the Internet Communication 626073 - Unreleased Internet Communication Framework Services 698329 - Integrated ITS, WEBGUI/IAC logon fails 709038 - SAP ITS Release 6.40: SAP Integrated ITS 721993 - ITS Updates in Release 6.40 (SAP Integrated ITS) 890606– Details on ITS 7.00

Basic Monitoring Guidelines for the Internet and Pricing Configurator The IPC provides a Monitoring Tool to check the status and behavior of the IPC Dispatcher or an IPC Server remotely. We recommend monitoring the following parameters within transaction RZ20 (alternatively, the IPC Monitor can be used):

• Number of active sessions • Number of active threads • Total memory, used memory, and free memory • Regularly a ping check and response test should be performed

See SAP Note 502461 for further information on the implementation of the CCMS agent plug-in on the IPC.

Basic Monitoring Guidelines for the Frontend and Network The frontends cannot be monitored centrally by the SAP infrastructure. In case of performance problems they should be analyzed by frontend operating tools like Perfmon (Windows NT) or Sysmon (Windows 9x). At the frontend potential problems can occur by

• High CPU and memory usage of the browser. • Slow network between ITS and the frontend.

You cannot use Perfmon in combination with PCanywhere to make useful performance measurements. The CPU and network load of PCanywhere are quite high and will falsify the results. To start Perfmon on a Windows NT computer, choose Start -> Run and enter perfmon. Perfmon is an NT standard tool for measuring CPU consumption, network load, and time and other information like paging rate or disk queue length. For a detailed description of the use of the MS Performance Monitor, see SAP Note 203845. Hardware and software dependencies regarding the frontend are described in SAP Note 26417.

Useful SAP Notes for frontend and network performance: 203845 - Performance mySAP.com Workplace 317922 - Workplace Performance: ITS and Browser Cache


© 2006 SAP AG

72

© Copyright 2006 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. 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, SAP NetWeaver, 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

bp_manage procurement in sap ebp and sus

Documents