212 bpp en_uk

EHP4 for SAP ERP 6.0

March 2010

English

Sales of Planned Services (212)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Sales of Planned Services (212): BPD

Copyright

© 2010 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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

© SAP AG of 32


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include Field names, screen titles, pushbuttons as well as menu names, paths, and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 32


Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites.......................................................................................................................... 5

2.1 Master Data and Organizational Data.............................................................................5

2.2 Roles............................................................................................................................... 6

2.2.1 Defining Queries for POWL`s...................................................................................7

3 Process Overview Table.........................................................................................................9

4 Process Steps...................................................................................................................... 10

4.1 Creation of a Framework Purchase Order.....................................................................10

4.2 Creating a Customer Contract.......................................................................................12

4.3 Creating a Maintenance Plan........................................................................................14

4.4 Scheduling the Maintenance Plan.................................................................................15

4.5 Displaying Maintenance Plan........................................................................................16

4.6 Displaying the Scheduling Overview List.......................................................................17

4.7 Changing the Service Order..........................................................................................18

4.8 Ordering: Assigned Purchase Requisitions...................................................................20

4.9 Maintaining Service Entry Sheet...................................................................................20

4.10 Approving the Service Entry Sheet............................................................................22

4.11 Invoice Verification.....................................................................................................23

4.12 Closing the CS Order Technically..............................................................................24

4.13 Creating a Billing Request.........................................................................................25

4.14 Creating the Billing Document...................................................................................26

5 Follow-up Processes............................................................................................................27

6 Appendix.............................................................................................................................. 27

6.1 Reversal of Process Steps............................................................................................27

6.2 SAP ERP Reports.........................................................................................................31

6.3 Used Forms...................................................................................................................32

© SAP AG of 32


Sales of Planned Services

1 Purpose

A customer has signed a long-term contract with a service provider. The service provider carries out services on a frequent basis. Typically, such contracts are service level agreements between the service provider and the customer.

The business process starts with a customer who requests frequent or permanent services from a service provider. As a result, a maintenance plan is created, a service order is subsequently automatically generated, and the necessary material parts are ordered.

The costs (fee, spare parts, and travel expenses) that result from the service order are entered into the service order and billed to the customer, according to the corresponding effort and expenses.

2 Prerequisites

2.1 Master Data and Organizational DataRequired master and organizational data was created in your system during implementation, such as the data that reflects the organizational structure of your company, and master data for materials, vendors, customers, and so on.

This master data primarily consists of standardized SAP Best Practices default values and enables you to go through the process steps of this scenario.

Additional Master Data (Default Values)

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Service

Service Plant

© SAP AG of 32


Master data Value Master / org. data details

Comments

Material/Services D102 Services

Service Master 4000000 Planned Service

Sold-to party 100100 Customer Services

Ship-to party 100100 Customer Services

Payer 100100 Customer Services

Plant 1000 Plant 1

Storage Location 1040 Storage Location 1040

Company Code 1000 Company Code 1000

CO Area 1000 CO Area 1000

Purchasing Organization

1000 Purch.Org. 1000

Purchasing Group 001 Purch. Group 001

Sales organization 1000 Inland

Distribution channel 10 Sales Direct

Division 10 Product Division 10

Functional Location YB50000/00000001 Functional Location

Work Center SERV01 Services: Work Center Technical Serv.

2.2 Roles

UseThe following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality

Purchaser SAP_NBPR_PURCHASER-S Creation of a Framework Purchase Order,

Ordering: Assigned Purchase Requisitions

Service Agent SAP_NBPR_SERVAGENT-S Create a Customer Contract,

Create a Maintenance Plan

© SAP AG of 32


Business role Technical name Process step

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality

Service Employee SAP_NBPR_SERVEMPLOYEE-S Schedule the Maintenance Plan,

Display Maintenance Plan,

Display the Scheduling Overview List,

Change the Service Order,

Maintain Service Entry Sheet,

Approve the Service Entry Sheet,

Create a Billing Request

Accounts Payable Accountant

SAP_NBPR_AP_CLERK-S Invoice Verification

Billing Administrator

SAP_NBPR_BILLING-S Create the Billing Document

2.2.1 Defining Queries for POWL`s

2.2.1.1 Defining Queries for Service Order (POWL)

UseThe following queries must be defined to test this scenario in the SAP NetWeaver Business Client (NWBC). You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

The queries are necessary to access role specific worklists in the SAP NetWeaver Business Client (NWBC).

For more information on the creation of queries, see the section Creation of Queries in Personal Object Working Lists (POWLs) in the Quick Guide to Implementing the SAP Best Practices Baseline Package (DE) document.

ProcedureChoose the menu path Customer Service Service Processing Service Order

Business role

Application Object Type Variant Name

Variant Selections

Selection Criteria

Query Name

Service Employee

Service Order

Service Orders - - Order Status Outstanding: x

In process: x

Service Order

ResultYou can now process the steps Changing the Service Order and Closing the Internal Repair Order - Technically in the scenario Sales of Planned Services (212).

© SAP AG of 32


2.2.1.2 Defining Queries for Service Entry Sheet (POWL)




ProcedureChoose the menu path Customer Service Service Processing Time Management Service Entry Sheet.

Business role


Variant Selections

Selection Criteria

Query Name

Service employee

Service Entry Sheet

Purchasing Documents Ready for service Entry

- - Company Code: 1000

All Purchasing Documents Ready Service Entry

ResultYou can now process the step Approve the Service Entry Sheet in the scenario Sales of Planned Services (212):

2.2.1.3 Defining Queries for Invoicing (POWL)




ProcedureChoose the menu path Accounts Payable Posting Invoices.

Business role


Variant Selections

Selection Criteria

Query Name

Accounts Invoice Purchasing - - Company All

© SAP AG of 32


Business role


Variant Selections

Selection Criteria

Query Name

Payable Accountant

Documents Ready for Invoicing

Code: 1000

Purchasing Documents Ready for Invoicing

ResultYou can now process the step Invoice Verification in the scenario Sales of Planned Services (212):

3 Process Overview TableProcess step External

process reference

Business condition

Business role

Trans-action code

Expected results

Create a Framework Purchase Order

- – Purchaser ME21N The framework purchase order has been created.

Create a Customer Contract

– – Service Agent VA41 Customer Contact is created.


– – Service Agent IP50 Maintenance Plan is created.

Schedule the Maintenance Plan

– – Service Employee

IP10 Maintenance Order is created for the first call.

Display Maintenance Plan


IP03 Check the purchase requisition created in the background of the maintenance plan.

Display the Scheduling Overview List


IP24 Check the Maintenance Plan.

Change the Service Order


IW32 Add details to the service order.


– – Purchaser ME58 Creation of the Service Entry Sheet.

Maintain Service Entry Sheet


ML81N Performed Services are reported in the Service Entry Sheet.

Approve the Service Entry Sheet


ML81N The Service Entry Sheet is approved by the company.

© SAP AG of 32


Process step External process reference

Business condition

Business role

Trans-action code

Expected results

Invoice Verification

– – Accounts Payable Accountant

MIRO The invoice is verified with the Service Entry Sheet and booked against the purchase order.

Close the Service Order – Technical Completion


IW32 Set the status to ‘Technically complete’.



DP90 A billing request is created with reference to the service order.

Create the Billing Document

– – Billing Administrator

VF01 Generation of the invoice from the debit memo request.

Settlement Service Orders

189: Period End Closing CO Orders

– See scenario no. 189

See scenario no. 189


Closing the Service Order – Business View

189: Period End Closing CO Orders

– See scenario no. 189



4 Process Steps

4.1 Creation of a Framework Purchase Order

UseIn this activity, a framework purchase order is created with the document type: FO. The framework purchase order is the document that is sent to the vendor.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Material Management Purchasing Purchase Order Create Vendor/Supplying Plant known

Transaction code ME21N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Purchaser

(SAP_NBPR_PURCHASER-S)

Business role menu Purchasing Purchase Order Purchase Order Create Purchase

© SAP AG of 32


Order

2. On the Create Purchase Order screen, make the following entries:

Field name Description User action and values Comment

Order type Framework Order Order type ‘FO’

Vendor 300100 Vendor Services

Org. data tab Choose

Purchasing org. Purchasing_org_1 (1000) Purchasing Org.

Purchasing group

001 Purchasing group 001

Company Code Company_Code_1 (1000)

3. Choose the Additional Data tab.

4. On the Additional Data tab, make the following entries:


Validity Start <Today’s date>

Validity End <Today’s date + 90 days>

5. Choose Expand Item Overview.

6. Choose line item 10, and make the following entries:


A F Account Assignment Category

I D Item Category in Purchasing Document

Short Text Planned Service

Order quantity 1 Any other value can be entered here, as appropriate.

Delivery date <Date in future>

Material group YBSVS1 SP-Services

Plant Plant_1 (1000)

7. Choose Expand Item Details.

8. Choose the Services tab.

9. In line 10, make the following entries:


Service No. 4000000 Planned Service

Quantity 10

Gross Price 20 GBP

10. Choose Enter.

11. On the Account Assignment tab, make the following entries:

© SAP AG of 32



G/L Account 500900 Third party fee with hours (Service Provider)

Cost Center 1321 Services/Consulting

12. Save your entries.

13. A purchase has been created.

Confirm the message with OK and print the Purchase Order.

14. The purchase order number is displayed in the PO column.

15. Note the purchase order number. Purchase order: _______________________________.

16. Go Back to return to the SAP Easy Access screen (SAP GUI).

Or

Choose Exit (Shift + F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe framework purchase order has been created.

4.2 Creating a Customer Contract

UseThis transaction is used for defining the service level agreement between the services company and the customer.



SAP ECC menu Logistics Sales and Distribution Sales Contract Create

Transaction code VA41


Business role Service Agent

(SAP_NBPR_SERVAGENT-S)

Business role menu Service Processing Service Agreements Contracts Create Contract

2. On the Create Contract: Initial Screen, make the following entries and choose Enter.


Contract Type

Sales document type of the contract

YBC1

© SAP AG of 32



Sales Organization

Selling entity responsible for the customer

1000

Distribution Channel

Customer grouping 10

Division Product or service grouping

10

3. On the Create SD Contract: Overview screen, make the following entries and choose Enter. (Default data remains unchanged.)


Sold-to Party

Alphanumeric key uniquely identifying the customer

100100

Description Description of contract <Description of contract>

Contract start

Start date of the contract <Today’s date>

Contract End

End date of the contract <Today’s date + 90 days>

Material Alphanumeric key uniquely identifying the service product

D102

Target Quantity

Number of service units 100

4. Choose Enter.

5. To enter a price for the Technical Service, mark line item 0010, and choose item conditions

6. On the Create SP: SD-Contract: Item Data screen, enter the following data into the next first empty row:


CnTy Condition Type PR00

Amount Rate (condition amount or percentage)

Enter the price for the service, for example, <7.50>

UoM Unit of Measure AU

7. To assign a functional location to contract, choose (NWBC: More…) extras Technical objects in the menu.

8. Go to the Functional loc field and enter YB50000/00000001.

9. Go Back to the Create SP: SD-Contract: Item Data screen.

10. Go Back to the Create SP: SD-Contract: Overview screen.

11. Choose Save.

12. Write down the generated contract number 4XXXXXXX for future reference.

Contract number: _________________________

13. Go Back to the SAP Easy Access screen (SAP GUI).

Or

© SAP AG of 32



ResultThe system displays the message: SP: SD-Contract 4XXXXXXX has been saved.

4.3 Creating a Maintenance Plan

UseIn this activity, a service is planned: a maintenance plan delivered weekly for the next 90 days. This transaction is used to create the maintenance plan using a predefined task list.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Maintenance Plans Create For Contract Item

Transaction code IP50




Business role menu Service Processing Preventative Maintenance Maintenance Planning Create ref. for maint. contract item

2. In the Create Maintenance Plan: Initial, make the following entries: and choose Enter.


Maintenance Plan

Leave this field empty.

Maint.Plan Cat.

Service order with outline agreement

Sales Document

<Created in step Create a Customer Contract>

Item <Item of sales document>

For example, 0010.

Planning Plant

1000

3. Choose Enter.

4. In the Create Maintenance Plan: Single Cycle plan, in the header area, make the following entries:


Cycle/Unit 1 / wk

Cycle text Weekly Cleaning

© SAP AG of 32



Offset/Unit Leave this field empty.

Counter Leave this field empty.

5. On the Create Maintenance Plan: Single Cycle plan screen, make the following entries in the Item area:


Functional location

YB50000/00000001 Reference object area

MaintActivityType

YB1 Planning data area

6. On the Create Maintenance Plan: Single Cycle plan screen, check the following entries in the Item area:


Order type YBS1 Planning data area

MainWorkCtr SERV01 Planning data area

Typ A Task list area

TaskLstGrp 100000 Task list area

GrpCr 2 Task list area

Description Global Task List Default value when typing in TaskLstGrp

The task list group can contain predefined operations; the operation can be assigned to external vendors using a purchasing outline agreement.

7. Choose the Maintenance plan Scheduling parameters tab.

8. On the Maintenance plan scheduling parameters tab, make the following entries.

Call horizon Scheduling period Start of cycle

70 90 <today’s date>

9. Confirm your entries with Enter.

10. Save the maintenance plan.

11. Make a note of the Maintenance plan number. Maintenance plan: _____________.

ResultThe maintenance plan has been created.

4.4 Scheduling the Maintenance Plan

UseIn this step, the plan is scheduled.


© SAP AG of 32



SAP ECC menu Logistics Customer Service Service Agreements Maintenance Planning Scheduling for Maintenance Plans Schedule



Business role Service Employee

(SAP_NBPR_SERVEMPLOYEE-S)

Business role menu Customer Service Service Agreements Maintenance Plans Schedule Maintenance Plan

2. On the Schedule Maintenance Plan: Initial screen, enter the Maintenance Plan Number created in the step Create a Maintenance Plan.

3. Choose Enter.

4. On the Schedule Maintenance Plan: Single cycle plan xxxxxxxxx screen, choose Start.

5. In the start date dialog box, the default date is today’s date.

6. Choose Continue.

7. A list of scheduled calls is now on the Scheduled calls tab. To release the first call, select the row and choose Release Call.

8. To save the changes to the maintenance plan, choose Save.

9. Confirm by choosing Enter.

ResultMaintenance plan X is scheduled. The maintenance order is now created for the first call.

4.5 Displaying Maintenance Plan

UseIn this step, you display the maintenance plan.



SAP ECC menu Logistics Customer Service Service Agreements Maintenance Planning Maintenance Plans Display





Business role menu Customer Service Service Agreements Maintenance Plans Display Maintenance Plan

2. On the Display Maintenance Plan: Initial screen, enter the maintenance plan number.

© SAP AG of 32


3. Choose Enter.

4. On the Display Maintenance Plan: Single cycle plan 0000000000xx screen, choose the Maintenance plan schedule calls tab.

If the tab is not visible, the screen size may be too small. Choose the dropdown button next to the tab strip to choose tabs.

5. To show the order created for the first call, choose the first row

6. Choose Display Call object.

7. The maintenance order created in the step Create Maintenance Plan is displayed. Make a note of the maintenance order number. Maintenance order: __________________.


Or


ResultA purchase requisition is created in the background because external procurement has been chosen for the task.

4.6 Displaying the Scheduling Overview List

UseIn this activity, you display the scheduling overview list, using the start date for the selected period as a search criterion.



SAP ECC menu Logistics Customer Service Service Agreements Maintenance Planning Scheduling for Maintenance Plans Scheduling Overview Scheduling Overview and Simulation





Business role menu Customer Service Service Agreements Maintenance Plans Maintenance Scheduling Overview

2. On the Maintenance Scheduling overview and simulation : Selection screen, make the following entries:

© SAP AG of 32



General Object Selection :

from date

<Start date from the actual week>

To date <End date from the last week for the interval>

In the to date field, enter the end of interval, for example, one week or one month from the start date.

With Equipment X

With Orders X

Work Scheduling / Task List Data: Main work center

SERV01 Leave the to field blank.

Display of Maint. Scheduling Overview

Tabular with Navigation tree

X

3. Choose Execute.

4. In the navigation tree area, choose the relevant maintenance plan by double-clicking.

5. To display the service order, double-click the relevant service order number.


Or


ResultThe scheduling overview list is displayed.

4.7 Changing the Service Order

UseIn this activity, you assign a service contract to the service order.



SAP ECC menu Logistics Customer Service Service Processing Order Service Order Change

Transaction code IW32


© SAP AG of 32




Business role menu Customer Service Service Processing Service Order Change Order

2. Enter your order number.

3. Confirm your entry with Enter.

4. In the Service area, check the following entries:


Sales document Check the contract number and item.

You can use input help (F4) for item selection.

5. On the Change Service order Central Header screen, choose the Operations tab and make the following entries:


Short Text Operation short text Overwrite the short text from the global task list with a short description of the planned service.

Control Key PM03 Change the control key to PM03.

6. Choose External.

7. Make the following entries:


External: FW Order Framework Order Enter the framework order created in the step Creation of a Framework Purchase Order and the purchase order item 0010.

Confirm the messages by choosing Enter.

8. To refer to the conditions of the framework order, go to Service Sel., choose the line From Purch.Document and enter the FW Order No./Item number

9. Confirm with Enter.

10. Select the line 10 and choose Adopt services.

11. Overwrite the proposed quantity with the required value (for example, 1 m²).

12. Go Back.

13. Choose Release Order to release the service order.



Or


© SAP AG of 32


ResultThe service order has been changed.

4.8 Ordering: Assigned Purchase Requisitions

UseIn this activity, the system automatically creates a service entry sheet out of the purchase requisition, which was created automatically in the service order.



SAP ECC menu Logistics Materials Management Service Entry Sheet Environment Requisition Selection

Transaction code ME58


Business role Purchaser

(SAP_NBPR_PURCHASER-S)

Business role menu Purchasing Purchase Requisition Purchase Requisition Ordering: Assigned Requisitions

2. Enter the framework order number created in the step Creation of a Framework Purchase Order in this document.

3. Choose Execute. The system shows the line with the outline agreement number you initially created for your vendor.

4. Double-click the outline agreement number. A dialog box shows you the automatically created service entry sheet 1000000xx.

5. The service entry sheet has been created. Make a note of the entry sheet number.


7. The service entry sheet has been created.


Or


Result The service entry sheet has been created.

4.9 Maintaining Service Entry Sheet

UseIn this activity, the performed services are reported in the service entry sheet.

© SAP AG of 32




SAP ECC menu Logistics Materials Management Service Entry Sheet Maintain

Transaction code ML81N




Business role menu Customer Service Service Processing Time Management Service Entry Sheet

For NWBC: Choose the query All Service Entry sheets. Choose the line with the service entry sheet number created in step 4.8. Go to step 7.

2. On the Display Entry Sheet screen, choose Other Purchase Order.

3. In the Select Purchasing Order/Entry Sheet dialog box, make the following entries:


Purchase Order <Purchase order number from the step Creation of a Framework Purchase Order in this document >

4. Choose Enter. The purchase order is selected and shown in the Purchase Orders/Entry Sheets area.

5. In the Purchase Orders/Entry Sheets area, select the entry sheet created in the previous step by double-clicking.

6. Choose Display Change (F5)

7. NWBC: Choose More actions process service entry sheet

8. On the 10000000xx Change Entry Sheet screen, make the following entries:


Short Text Overwrite the existing text with Cleaning report week <week number>

The short text is at the top of the screen, below the purchase order number.

9. Choose Continue (Enter).

10. Save the service entry sheet by choosing Save.

11. Confirm the message with Yes.

12. Make a note of the entry sheet number. Entry sheet: ____________________________.

13. Choose Back to return to the SAP Easy Access screen (SAP GUI).

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

© SAP AG of 32


ResultThe performed services are reported in the service entry sheet.

4.10 Approving the Service Entry Sheet

UseIn this activity, the service entry sheet is approved by the company. When this is complete, the vendor can send an invoice for the approved amount to the service provider.



SAP ECC menu Logistics Materials Management Service Entry Sheet Maintain

Transaction code ML81N

2. On the Display Entry Sheet screen, choose Other Purchase Order.

3. On the Select Purchasing Order/Entry Sheet screen that appears, make the following entries:


Service Entry Sheet

<Entry Sheet number from previous step>

4. Choose Continue (Enter).

5. To change the service entry sheet, choose Change (F5).

6. In the 10000000xx Change entry Sheet screen, choose Accept (Ctrl + F1) to accept the service entry sheet as it is.

7. Save the entry sheet.





8. Select the query All Service Entry Sheets for changing the Service Entry Sheet. In the POWL shown beside mark the line with the service entry sheet number created earlier and choose More Actions Process Service Entry Sheet.

9. For NWBC: Choose Entry Sheet Set Status Acceptance.

10. For NWBC: Choose Save (Ctrl. + S), to save the service entry sheet.


Or


© SAP AG of 32


ResultThe service entry sheet is approved by the company.

4.11 Invoice Verification

UseThe vendor sends an invoice for the service provided. This invoice must be booked against the purchase order and verified with the entry sheet.



SAP ECC menu Logistics Materials Management Logistics Invoice Verification Document Entry Enter Invoice

Transaction code MIRO


Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable Posting Invoices Enter Incoming Invoice w/ PO Reference

2. On the Enter Incoming invoice: Company Code 1000: Overview screen, make the following entries.

If you have not worked in the system before and do not have a default company code, you must enter the company code 1000 in the dialog box.

Invoice Date Amount Reference Calculate tax

<Today's Date>

<value booked in the service entry sheet in step Maintain Service Entry Sheet of this document>

Cleaning week <week number>

X

3. On the PO reference tab, choose Purchase Order/Scheduling Agreement from the dropdown list.

4. In the Purchasing Document Number field, enter the purchase order number created in the step Creation of a Framework Purchase Order in this document.

5. Choose Enter.

You can also search for the purchasing order using F4. Use vendor 300100.

6. Select the check box in the Booking OK column for the line item.

7. In the item overview area, select the check box in the Final Invoice column.

8. Choose Post. The invoice is posted.


© SAP AG of 32


Or


ResultThe invoice has been created and blocked for payment

4.12 Closing the CS Order Technically

UseOnce all the activities are complete and the completion confirmations are posted, you can set the status of the maintenance order to technically complete.



SAP ECC menuLogistics Plant Maintenance Maintenance Processing Order Change

Transaction code IW32

2. Enter your order number and confirm with Enter.

3. Check again that all expenses for the repairs have been entered on the Costs tab. You can also choose Document flow to display the assigned confirmation (double-click confirmation item) and choose Back.

4. Choose Complete (technically) to complete the service order technically.




Business role menu Customer Service Service Processing Service Order

1. Select the active query service order.

2. In the POWL shown, mark the line with the order number created earlier and choose Change.

In case you cannot find your document number in the POWL, choose the button Refresh in order to display all the documents relevant for the selection.

3. Scroll down to the bottom of the screen. Choose Complete Technically

4. A screen window appears where additional information regarding the completion can be updated, to continue choose Enter.


Or


Result

© SAP AG of 32


The Service Order is completed technically.

4.13 Creating a Billing Request

UseIn this two-step process, you create an invoice based on the service activity performed by the third party.

A billing request or debit memo request is created with reference to the service order.



SAP ECC menuLogistics Customer Service Service Processing Completion Billing Request Process Individually

Transaction code DP90




Business role menu Customer Service Service Processing Billing CS:Resource-Related Billing Doc.

2. On the Resource-Related Billing Request: Initial Screen, make the following entries:


Service order <The service order number you noted earlier>

Sales document Leave this field blank.

3. Confirm with Enter.

The expenses screen for the billing request appears automatically (Billing request for resource-related billing document <new>: Expense). This screen shows the actual expenses that the company incurred in providing the service. Choose Sales price to display the amounts that are invoiced to the customer.

4. To save the billing request, choose Billing request.

5. Confirm the dialog box with Yes.

6. Make a note of the billing request number: ___________________________.

7. On the Sales tab, make the following entries:

© SAP AG of 32



Billing block Leave this field blank. Absolutely necessary for billing purposes.

Order reason No warranty (YR1)

8. Select the item.

9. Go to (NWBC: More…) Goto Items Conditions.

10. Add condition type YBS1 SP: Surcharge with an amount of 10.

11. Choose Enter. The surcharge of 10 percent has been added to the Price.

12. Go Back.

13. Save the billing request.

14. Go Back to the SAP Easy Access menu.

ResultThe billing request is created with reference to the service order.

4.14 Creating the Billing Document

UseIn this activity, you generate the invoice from the debit memo request.



SAP ECC menuLogistics Customer Service Service Processing Completion Billing Document Create

Transaction code VF01

2. On the Create Billing Document initial screen, maintain the following fields:


Document Debit memo request from the previous step

3. Confirm your entries with Enter.

4. On the Debit Memo (L2) Create: Overview of Billing Items screen, items for services are proposed. Save the proposed debit memo. This generates the billing document. The number of the billing document created is displayed in the status bar. The corresponding accounting document is created in the background.

5. Go Back to the SAP Easy Access menu.


Business role Billing Administrator

© SAP AG of 32


(SAP_NBPR_BILLING-S)

Business role menu Sales Billing

1. In the POWL shown, choose the All Sales Documents Due for Billing tab. Select the line with the sales document and choose Individual Billing Document and then Save. Choose Exit (Shift + F3) to return to the SAP Easy Access menu.

You can also post the document as a PDF-Document. To do this, choose Individual Billing and Show as PDF instead of Individual Billing.

ResultThe billing document has been created and assigned to accounting.

5 Follow-up ProcessesYou have finished all activities that are part of the business process described in this document.

To accomplish subsequent activities of this business process, carry out the process steps described in one or more of the following scenarios, using the master data from this document.

Period End Closing Service Orders (189) (optional)

UseAdditional activities must be carried out in this project. These are performed collectively as a part of month-end closing. For more information about the month-end closing procedure, see the Business Process Documentation for Period End Closing Service Orders (189).

Month-end closing can only be performed once a month.

To complete the scenario activities, perform the process steps Settlement Service Orders and Close Completed Service Orders (Business View).

6 Appendix

6.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document,

Create a Customer Contract

© SAP AG of 32


Transaction code ( SAP GUI) VA41

Reversal: Change the customer contract




Business role menu Service Processing Service Agreements Contracts Change Contract

Comment You can change the customer contract.


Transaction code ( SAP GUI) IP50

Reversal: Change the Maintenance Plan




Business role menu Service Processing Preventative Maintenance Maintenance Planning Change Maintenance Plan- Transaction-IP02

Comment You can change the maintenance plan. If you do not need the maintenance plan, set a deletion flag by choosing Maintenance plan Functions Deletion flag Set.

Schedule the Maintenance Plan


Reversal: Change the call object (service order)

Transaction code ( SAP GUI) IW32

Business role Production Planner

(SAP_NBPR_PRODPLANNER-S)

Business role menu Production Worklist Change Order

Comment Mark the line and choose the button change order.

If you do not need the call object (service order),

use one the following options:

If the order is not released:

1. Set the system status NCMP (Not completed) with the function Do Not Execute.

2. Set the system status DLFL (Deletion Flag).

If the order is released:

1. Set the system status CLSD (Closed) with the function Complete (Business).

© SAP AG of 32



Change the Service Order


Reversal: Change the Service Order


Business role Service Employee(SAP_NBPR_SERVEMPLOYEE-S)

Business role menu Customer Service Service Processing Service Order Change Order

Comment If the order is not released:

1. Set the system status NCMP (Not completed) with the function Do Not Execute.


If the order is released:

1. Set the system status CLSD (Closed) with the function Complete (Business).



Transaction code ( SAP GUI) ME58

Reversal: Change Entry Sheet

Transaction code ( SAP GUI) ML81N




Comment You can delete the service entry sheet.

Maintain Service Entry Sheet







Comment You can delete the service entry sheet.

Approve the Service Entry Sheet

© SAP AG of 32








Comment Choose Revoke acceptance (Ctrl + F2).

Invoice Verification

Transaction code ( SAP GUI) MIRO

Reversal: Cancel Invoice Document

Transaction code ( SAP GUI) MR8M

Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable Posting Invoices Cancel Invoice Document

Comment Enter the invoice number you want to cancel into the POWL or choose it if already on the POWL and select Reversal Reason.

Close the Service Order – Technically


Reversal: Cancel the Technical Completion


Business role Production Planner

(SAP_NBPR_PRODPLANNER-S)

Business role menu Production Worklist Change Order

Comment Mark the line and choose the button Change Order

Use Order Functions Complete Cancel technical completion


© SAP AG of 32


Transaction code ( SAP GUI) DP90

Reversal: Cancel Billing Request


Business role Sales Administrator

(SAP_NBPR_SALESPERSON-S)

Business role menu Sales Sales Orders Sales Order Processing Change Sales Order

Comment You can change the billing request document before invoicing if necessary.

Create the Billing Document

Transaction code ( SAP GUI) VF04

Reversal: Cancel Billing Document

Transaction code ( SAP GUI) VF02

Business role Billing Administrator

(SAP_NBPR_BILLING-S)

Business role menu Sales Billing Change Billing Document

Comment You cancel the customer invoice and posting to the accounting.

6.2 SAP ERP Reports

UseThe table below lists the most frequently used reports that help you to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following Business Process Documentation, which provides a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

The descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction code Comment

Service and Maintenance Orders

IW39 A printed list of orders.

Equipment list IH10 An equipment list with general data and other information.

Cost Analysis MCI8 A list of order types that contains

© SAP AG of 32


information about the numbers of unplanned and complete orders.

Scheduling Overview IP24 A list of the maintenance plans with assigned call objects or call dates.

Orders: Actual/Plan Variance

S_ALR_87012993 An overview of the actual and plan data on internal orders.

List: Orders S_ALR_87012995 A list of orders by controlling area for a plan/actual comparison

Actual Line Items KOB1 A report for actual line items for orders.

Execute Report KE30 A report on plan/actual activities.

6.3 Used Forms

UseIn some of the activities of this business process, forms were used. The table below provides details on these forms.

Common form name Form type Used in process step

Output type

Technical name

YB_QM_PM_COMMON SapScript After Release of the Service Order

Shop Paper

© SAP AG of 32

212 bpp en_uk

Documents

sap products

sap businessobjectsexplorer

sap netweaver

sap erp6

registered trademarks

sap group products

sap ag page

example text names of