IUT221 Work Management

IUT221 Work ManagementIUT221

Release 463 25.09.2003

IUT221 Work Management...........................................................................................................................................0-1

Copyright....................................................................................................................................................................0-2

SAP Utilities (IS-U/CCS).......................................................................................................................................0-3

Course Prerequisites...............................................................................................................................................0-4

Target Group..........................................................................................................................................................0-5

Course Content.......................................................................................................................................................0-6

Course Goals..........................................................................................................................................................0-7

Course Objectives...................................................................................................................................................0-8

Work Management Overview....................................................................................................................................1-1

Unit Objectives.......................................................................................................................................................1-2

Course Overview Diagram.....................................................................................................................................1-3

Main Business Scenario.........................................................................................................................................1-4

Functional Scope of the IS-U/CCS System............................................................................................................1-5

What is the Scope of the Work ManagementSystem?...........................................................................................1-6

Connection Between Generation and Distribution.................................................................................................1-7

The Work Management Process.............................................................................................................................1-8

SAP Components and Interfaces............................................................................................................................1-9

Terms and Concepts in Work Management.........................................................................................................1-10

Summary..............................................................................................................................................................1-11

Technical Objects in Transmission and Distribution.................................................................................................2-1

Technical Objects in Transmission and Distribution: Unit Objectives..................................................................2-2

Technical Objects in Transmission and Distribution: Course Overview Diagram................................................2-3

Technical Objects in Transmission and Distribution: Business Scenario..............................................................2-4

Organizational Structures.......................................................................................................................................2-5

Organizational Structure - Controlling...................................................................................................................2-6

Organizational Structure - Materials Management................................................................................................2-7

Organizational Structure - Sales and Distribution..................................................................................................2-8

Cross-Plant Plant Maintenance...............................................................................................................................2-9

Work Centers in Plant Maintenance and Service.................................................................................................2-10

Functions of the Work Center..............................................................................................................................2-11

Functional Locations and Equipment...................................................................................................................2-12

Equipment............................................................................................................................................................2-13

Functional Location..............................................................................................................................................2-14

Equipment Master Record....................................................................................................................................2-15

Functional Location Master Record.....................................................................................................................2-17

Equipment and Asset Accounting........................................................................................................................2-18

Prerequisites for Equipment Installation..............................................................................................................2-19

Equipment Usage List..........................................................................................................................................2-20

Relationships Between Technical Objects...........................................................................................................2-21

Object Link...........................................................................................................................................................2-22

Structure of Installations in T&D.........................................................................................................................2-23

Substation.............................................................................................................................................................2-24

Line System..........................................................................................................................................................2-25

Supply Grid..........................................................................................................................................................2-26

Distribution Grid (Logical Structure)...................................................................................................................2-27

The IS-U House....................................................................................................................................................2-28

Equipment and Technical Objects in IS-U/CCS..................................................................................................2-29

Technical Data Model..........................................................................................................................................2-30

Technical Objects in Transmission and Distribution: Summary..........................................................................2-31

Technical Objects in Transmission and Distribution: Exercises..........................................................................2-32

Solutions...............................................................................................................................................................2-35

Processes in Plant Maintenance and Customer Service.............................................................................................3-1

Processes in Plant Maintenance and Customer Service: Unit Objectives..............................................................3-2

Processes in Plant Maintenance and Customer Service: Course Overview Diagram............................................3-3

Processes in Plant Maintenance and Customer Service: Business Scenario..........................................................3-4

Notifications and Orders........................................................................................................................................3-5

Notifications and Orders in Plant Maintenance and Customer Service.................................................................3-6

Notification Types..................................................................................................................................................3-7

Notification Functions............................................................................................................................................3-8

Notification Structure.............................................................................................................................................3-9

Catalogs................................................................................................................................................................3-10

Basic Structure of a Work Order..........................................................................................................................3-11

Order Processing Steps.........................................................................................................................................3-12

Fundamental Maintenance Processing Steps........................................................................................................3-13

Work Order Supervisor........................................................................................................................................3-14

Printing: Papers for Orders...................................................................................................................................3-15

Printing Work Orders with IS-U Data..................................................................................................................3-16

Time Confirmations..............................................................................................................................................3-17

Settling a Maintenance Order...............................................................................................................................3-18

Billing & Settling a Service Order.......................................................................................................................3-19

Settlement Rule....................................................................................................................................................3-20

Sales Orders..........................................................................................................................................................3-21

Sales Documents..................................................................................................................................................3-22

Sales Document Flow...........................................................................................................................................3-23

Structure of a Sales Order....................................................................................................................................3-24

Structure of the Billing Document.......................................................................................................................3-25

Plant Maintenance and Customer Service Processes: Summary..........................................................................3-26

Processes in Plant Maintenance and Customer Service: Exercises......................................................................3-27

Solutions...............................................................................................................................................................3-33

Service Products.........................................................................................................................................................4-1

Service Products: Unit Objectives..........................................................................................................................4-2

Service Products: Course Overview Diagram........................................................................................................4-3

Service Products: Business Scenario......................................................................................................................4-4

The Service Product Concept.................................................................................................................................4-5

The Service Product...............................................................................................................................................4-6

The Service Object.................................................................................................................................................4-7

The Service Product...............................................................................................................................................4-8

Characteristics and Characteristic Values..............................................................................................................4-9

Class and Configuration Profile...........................................................................................................................4-10

Configuration of Service Products.......................................................................................................................4-11

Variant Configuration Basics...............................................................................................................................4-12

Components of the Knowledge Base...................................................................................................................4-13

Precondition..........................................................................................................................................................4-14

Selection Condition..............................................................................................................................................4-15

Action...................................................................................................................................................................4-16

Procedure and Constraint.....................................................................................................................................4-17

Reference Characteristics.....................................................................................................................................4-18

Configurable Service Products.............................................................................................................................4-19

Defining a Configurable Service Product.............................................................................................................4-20

Configurable Task Lists.......................................................................................................................................4-21

Configuration and Pricing....................................................................................................................................4-22

Defining Pricing...................................................................................................................................................4-23

Copy of the Settlement Rules...............................................................................................................................4-24

Technical Reference Object for a Service Product...............................................................................................4-25

Characteristic Inheritance.....................................................................................................................................4-26

Copying the Configuration...................................................................................................................................4-27

Multi-Level Structure of Service Objects.............................................................................................................4-28

Multi-Level Service Objects.................................................................................................................................4-29

Configuration in a Multi-Level Structure.............................................................................................................4-30

Multi-Level Order Structure.................................................................................................................................4-31

Further Functions of Variant Configuration.........................................................................................................4-32

Variant Tables and Object Dependencies.............................................................................................................4-33

Example: Table with Service Connection............................................................................................................4-34

Functions..............................................................................................................................................................4-35

Example: Summary of Operations.......................................................................................................................4-36

Summary (1).........................................................................................................................................................4-37

Summary (2).........................................................................................................................................................4-38

Service Products: Exercises..................................................................................................................................4-39

Service Products: Solutions..................................................................................................................................4-46

Installation Services....................................................................................................................................................5-1

Installation Services: Unit Objectives....................................................................................................................5-2

Installation Services: Course Overview Diagram..................................................................................................5-3

Installation Services: Business Scenario................................................................................................................5-4

The Workflow........................................................................................................................................................5-5

Quotation Processing..............................................................................................................................................5-6

Order Processing....................................................................................................................................................5-7

Order Closing and Billing......................................................................................................................................5-8

Workflow Structure................................................................................................................................................5-9

Workflows for Service Connection Processing....................................................................................................5-10

Workflow: Service Connection with Customer Quotation..................................................................................5-11

Workflow: Service Connection Order Processing...............................................................................................5-12

Workflow: Process SM Order..............................................................................................................................5-13

Link Between SD and CS.....................................................................................................................................5-14

Interaction Between SD and CS...........................................................................................................................5-15

Derivation of the Service Order Type (1).............................................................................................................5-16

Derivation of the Service Order Type (2).............................................................................................................5-17

Several Order Types.............................................................................................................................................5-18

Transferring Costs from Work Orders.................................................................................................................5-19

Installation Services: Summary............................................................................................................................5-20

Installation Services: Exercises............................................................................................................................5-21

Installation Services: Solutions............................................................................................................................5-23

Processes in the Utilities Industry..............................................................................................................................6-1

Processes in the Utilities Industry: Unit Objectives...............................................................................................6-2

Processes in the Utilities Industry: Course Overview Diagram.............................................................................6-3

Utilities Industry Processes: Business Scenario.....................................................................................................6-4

Codes for Orders and Notifications........................................................................................................................6-5

Creating Orders and Notifications..........................................................................................................................6-6

Order Code.............................................................................................................................................................6-7

Notification Code...................................................................................................................................................6-8

Selecting a Code.....................................................................................................................................................6-9

Plant and Work Center Determination.................................................................................................................6-10

Example of Plant and Work Center Determination..............................................................................................6-11

Orders and Notifications in Processes..................................................................................................................6-12

Aperiodic Meter Reading.....................................................................................................................................6-13

Disconnection and Reconnection.........................................................................................................................6-14

Customizing Disconnections/Reconnections.......................................................................................................6-15

Overview of Device Inspection............................................................................................................................6-16

Selecting Devices for Work Orders......................................................................................................................6-17

Customizing the Device Inspection......................................................................................................................6-18

Device Repairs.....................................................................................................................................................6-19

Example: Initial Data Creation for a Front Office Process..................................................................................6-20

Inspections............................................................................................................................................................6-21

Subdivision of Inspections...................................................................................................................................6-22

Selecting Technical Objects.................................................................................................................................6-23

CIC Processes for Aperiodic Inspections.............................................................................................................6-24

Overview of Periodic Inspections........................................................................................................................6-25

Periodic Inspections.............................................................................................................................................6-26

Selection Options for Inspections.........................................................................................................................6-27

Bundling Inspections............................................................................................................................................6-28

Example: Switzerland and Spain..........................................................................................................................6-29

Disaggregation......................................................................................................................................................6-30

Deregulated Market..............................................................................................................................................6-31

Service Chains......................................................................................................................................................6-32

Services in the Utilities Industry..........................................................................................................................6-33

Example: Installation Service...............................................................................................................................6-34

Governing Body Electrical Inspections................................................................................................................6-35

Governing Body Electrical Inspections (US Only)..............................................................................................6-36

Example of Permit Determination........................................................................................................................6-37

Permit Determination...........................................................................................................................................6-38

Processes in the Utilities Industry: Summary.......................................................................................................6-39

Processes in the Utilities Industry: Exercises.......................................................................................................6-40

Processes in the Utilities Industry: Solutions.......................................................................................................6-45

Interfaces to External Systems...................................................................................................................................7-1

Interfaces to External Systems: Unit Objectives....................................................................................................7-2

Interfaces to External Systems: Course Overview Diagram..................................................................................7-3

Interfaces to External Systems: Business Scenario................................................................................................7-4

Integration of Complementary Software (CSP).....................................................................................................7-5

Integration of External Systems.............................................................................................................................7-6

How to Integrate a CSP (1)....................................................................................................................................7-7

How to Integrate a CSP (2)....................................................................................................................................7-8

Interfaces for Work Management...........................................................................................................................7-9

Outbound Processing with ALE...........................................................................................................................7-10

Inbound Processing with ALE.............................................................................................................................7-11

Business Objects, BAPIs, Function Modules.......................................................................................................7-12

The GIS Business Connector...............................................................................................................................7-13

Advantages of an Integrated Interface..................................................................................................................7-14

Data Distribution..................................................................................................................................................7-15

GIS Interface: Example........................................................................................................................................7-16

The CAD Interface...............................................................................................................................................7-17

The Principle of the GIS Business Connector......................................................................................................7-18

Properties of the GBC..........................................................................................................................................7-19

System Architecture of the GBC..........................................................................................................................7-20

Customizing the GBC..........................................................................................................................................7-21

Create New Service Connection (I)......................................................................................................................7-22

Create New Service Connection (II)....................................................................................................................7-23

Create New Service Connection (III)...................................................................................................................7-24

Example: New Service Connection......................................................................................................................7-25

Interactive Link Between SAP and GBC.............................................................................................................7-26

GIS Integration: Further Examples......................................................................................................................7-27

Interfaces to Further External Systems.................................................................................................................7-28

OMS: Outage Notification (1)..............................................................................................................................7-29

OMS: Outage Notification (2)..............................................................................................................................7-30

Scheduling and Dispatching with SAP and CADS..............................................................................................7-31

Data Exchange Between SAP and CADS............................................................................................................7-32

SCADA Systems: Principle of the Interface........................................................................................................7-33

SCADA Systems: Interface Scenarios.................................................................................................................7-34

SCADA Systems: Scenario for a Gas Station......................................................................................................7-35

Mobile Data Interface...........................................................................................................................................7-36

Mobile Data Interface (Example).........................................................................................................................7-37

Interfaces to External Systems: Summary............................................................................................................7-38

Interfaces to External Systems: Exercises............................................................................................................7-39

Interfaces to External Systems: Solutions............................................................................................................7-41

0

SAP AG 1999

IUT221 Work Management

SAP AG

IUT221IUT221

Work ManagementWork Management

R/3 System Release 4.63 / IS-Utilities / Customer Care Service August 2001 5004 4896

0.2

SAP AG 1999

Copyright 2001 SAP AG. All rights reserved.

Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translated into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without prior notice.

All rights reserved.

Copyright

Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.

Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation. Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc. ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. TouchSend Index ® is a registered trademark of TouchSend Corporation. Visio ® is a registered trademark of Visio Corporation. IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation. Indeo ® is a registered trademark of Intel Corporation. Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape

Communications, Inc. OSF/Motif ® is a registered trademark of Open Software Foundation. ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. ADABAS ® is a registered trademark of Software AG The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3,

R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime,

SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.

Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

0.3

SAP AG 1999

SAP Utilities (IS-U/CCS)

Introduction to the IS-U/CCS

IUT110 5 days

Level 2 Level 3

Work Management

IUT221 3 days

Customer Service

IUT250 4 days

Contract Accounts Receivable and Payable

IUT240 5 days

Print Workbench

IUT280 2 days

Device Management

IUT220 3 days

Billing and Invoicing

IUT230 5 days

Basic Data/ BasicFunctions

IUT210 3 days

Real Time Pricing

IUT235 2 days

Energy DataManagement

IUT225 2 days

0.4

SAP AG 1999

LO100 Plant Maintenance or LO110 Service

Management

IUT110 Introduction to the IS-U/CCS System or

IUT210 Master Data and Basic Functions

Course Prerequisites

0.5

SAP AG 1999

Audience:

Product managers responsible for implementing IS-U

Project team members modeling business processes with IS-U

Consultants preparing for IS-U implementation

Duration: 3 days

Target Group

Notes to the user: The training materials are not intended for self-study. They complement the course instructor's

explanations. Your material includes space for noting down this additional information.

0.6

SAP AG 1999

Course Content

Unit 5 Installation Services

Unit 6 Processes in the Utilities Industry

Unit 7 Interfaces to External Systems

Unit 1 Work Management Overview

Unit 2 Technical Objects in Transmission and Distribution

Unit 3 Processes in Plant Maintenance and Customer Service

Unit 4 Service Products

Preface

Exercises

Solutions

0.7

SAP AG 1999

This course will prepare you to:

Effectively use the Work Management component

Integrate Work Management with standard components

Describe the interfaces to external systems

Course Goals

0.8

SAP AG 1999

Use the Work Management functions and master data

Explain the Work Management process

Customize Work Management

Course Objectives

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

1

SAP AG 1999

Contents:

Functional scope of IS-U/CCS

Work Management overview

Work Management Overview

(C) SAP AG IUT221 1

1.2

SAP AG 1999

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

Define the scope and purpose of the Work Management system

Outline the Work Management process

Describe the interfaces and integration with other components

Unit Objectives

(C) SAP AG IUT221 2

1.3

SAP AG 1999


Technical Objects in T&D

Processes in Plant Maintenance and Customer

Service

Service Products

Installation Services

Processes in the Utilities Industry

Interfaces to External Systems

Course Overview Diagram

(C) SAP AG IUT221 3

1.4

SAP AG 1999

In IDES Energy Inc., there is a department devoted entirely to customer service. Any calls or letters from customers requesting services are dealt with in this department. These calls or letters may involve individual inquiries, complaints, or notifications of a service change.

To fulfil the customer requirements, IDES Energy Inc. needs to

Manage the technical objects

Set up a process for managing work orders

Define service products

Set up a process for managing services

Main Business Scenario

(C) SAP AG IUT221 4

1.5

SAP AG 1999

Marketing and Sales

InstallationServices

Service Billing

ConsumptionEntry Billing

ConsumptionBilling

CustomerService &

Settlement

Generation/ Procurement

Transmission Distribution

IS-U/CCSIS-U/CCS

Billing

Customer Contact/Information/Service

Contract Accounts

Receivable& Payable

Meter & Device Management

Work Management

CRMCRM

Customer Relationship Management

All customer-related business processesfrom the areas of energy supply, services, and salesAll customer-related business processesfrom the areas of energy supply, services, and sales

PM/CS

SD

FI

Functional Scope of the IS-U/CCS System

IS-U/CCS stands for "Industry Solution Utilities - Customer Care & Service". IS-U/CCS is a business-process-oriented sales and information system for all types of supply and

services offered by a utility company. When dealing with the customer, the clerk uses the Customer Interaction Center of the IS-U/CCS.

The core IS-U/CCS application is the consumption billing system that valuates measured consumption and services. Services can also be billed/invoiced using the standard component Sales and Distribution (SD).

IS-U/CCS also works in conjunction with further SAP components in other applications, such as with installation services and contract accounts receivable and payable.

(C) SAP AG IUT221 5

1.6

SAP AG 1999

What is the Scope of the Work ManagementSystem?

Acceptance, planning, costing, execution of internal and external work orders

Creation of invoices for customers

Examples:

Creation and amplification of service connections

Energy consulting

Unscheduled meter reading

Disconnection and Reconnection

Maintenance

Repairs

Installation, extension or removal of technical equipment

What is the Scope of the Work ManagementSystem?

The daily work of a utility company involves the processing of a large number of work orders. The orders must be accepted, planned, calculated, executed and when neccessary, billed to a customer.In this process, a distinction needs to be made between external work orders relating to the customer "services" and internal work orders. External work orders are modeled using service orders from the Customer Service (CS) component. Internal work orders are modeled using maintenance orders from the Maintenance (PM) component.

(C) SAP AG IUT221 6

1.7

SAP AG 1999

CustomersCustomersWorkManagement

Customer officeInstallation structure

InstallationsInstallations

GenerationGenerationGeneration TransmissionTransmissionTransmission Distribution Service

Distribution Distribution ServiceService

Installation-related processes• New installation• Plant maintenance• Operation

Installation-related processes• New installation• Plant maintenance• Operation

Customer-related processes• Installation • Meter reading• Energy supply

Customer-related processes• Installation • Meter reading• Energy supply

Work orders

Service products

Notifications

.....................

Work orders

Service products

Notifications

.....................

Connection Between Generation and Distribution

(C) SAP AG IUT221 7

1.8

SAP AG 1999

CSP

Work OriginationCustomer-Related

or Internal

Work OriginationCustomer-Related

or Internal

Planning andEstimation

Planning andEstimation

WorkApproval

WorkApproval

SchedulingScheduling

Field ForceReporting

Work Completion

Field ForceReporting

Work Completion

FinancialCompletion

FinancialCompletion

Customer Care and Service Settlement

Customer Care and Service Settlement

ServiceTerritoryDatabase

ServiceTerritoryDatabase

Markout RequestsPermits

Traffic Control

Markout RequestsPermits

Traffic Control

CentralPermit

Log

CentralPermit

Log

Mobile DataApplication

Mobile DataApplication

Sold-to PartyManagement/

External Services

Sold-to PartyManagement/

External Services

Asset RegisterAsset Register

TechnicalObjects orEquipment

TechnicalObjects orEquipment

AM/FM/GISAM/FM/GIS

Compatible UnitsWork Standards

Compatible UnitsWork Standards

External Requirements

(of other offices)

External Requirements

(of other offices)

Preventive Maintenance

Preventive Maintenance

SAP SAP and CSP

OutageRestoration

Orders

OutageRestoration

Orders

Triggers

CSP = Complementary Software Product

The Work Management Process

Work order creation Once the user has entered the order data, the order creation process is mostly automatic. The system uses information provided by service territory data and compatible units.

Work order estimate To estimate costs of an order, a customer quotation can be created. The order costs can be created automatically and transferred to the quotation (SD).

Accounting and Settlement The default values for order accounting and settlement are determined by the system and transferred to the order. Influencing factors may be: (1) order type, (2) technical reference object, (3) service territory, or (4) division.

Scheduling and dispatching The work list of orders is scheduled for work groups or individuals. The planning board (table or graphic) assists the planner in this activity. The planning board allows the contents to be displayed in detail or in compressed form. The contents can be supplemented for a single user. SAP functions for scheduling and dispatching mainly support less frequent orders with longer runtimes (for example, installation extensions, construction or design orders, projects, facilities work). External systems can be connected to manage large numbers of short-term orders. These systems communicate with the Work Management component using standard interfaces. The external systems can be used for detailed planning and distribution of orders based on criteria such as staff requirements, distances, priority, and fixed appointments.

(C) SAP AG IUT221 8

1.9

SAP AG 1999

<Use this for additional introductory slides.>

PM/CS

Orders,TechnicalObjects

SDQuotations,

Sales Orders,Price Determination

IS-U

User Interface, Clerk ViewFront Office/CIC

FI-CACustomer Account

FI-AACosts,

Asset Accounting

GISInstallations and Grid Structure

Scheduling and Dispatching

PSProjects

CSP

SAP

CO-PAControlling,

Profitability Analysis

SAP Components and Interfaces

Work Management uses functions from various standard SAP applications. These functions are grouped together to map IS-U-specific business processes. They are also supplemented with industry-specific functions, if necessary. The flexibility of the SAP System also enables external systems to be integrated in the business processes.

PM/CS Planning control and processing of preventive maintenance and inspection; plant maintenance and service management to allow for a high degree of availability of technical systems and installations delivered to customers.

SD Sales support activities, with flexible functions for pricing, rapid sales order processing and punctual deliveries; with a direct link to Profitability Analysis (CO-PA).

PS Coordinates and controls all phases of a project in direct conjunction with purchasing and controlling, from quotations through planning and approval to resource management and billing.

FI-CA Subledger accounting for the management of a large number of customer accounts. Summarized posting transactions are transferred periodically from this module to the general ledger.

FI-AA Integrated system of planning, controlling and monitoring instruments for company-internal processes and investment measures.

GIS Geographical information system in which the technical systems from PM/CS are represented, with direct data exchange between the two data processing systems.

(C) SAP AG IUT221 9

1.10

SAP AG 1999

Technical Object• Service Connection• Transformer Station

Technical Object• Service Connection• Transformer Station

Service Product• Create ConnectionService Object• Repair Transformer

Service Product• Create ConnectionService Object• Repair Transformer

Task ListTask List

Service OrderMaintenance OrderService OrderMaintenance Order

Sales OrderSales Order

Terms and Concepts in Work Management

Service products describe a service offered to the customer, for example, install service connection, and contain price information. Service objects are, however, not offered to the customers as products, but can subsequently be invoiced. Since the service must be performed internally or by third parties, a task list is allocated to the service product or object. A service order or maintenance order is created on the basis of the task list.

A sales order is a customer request to the company for the delivery of goods or services at a certain time.

(C) SAP AG IUT221 10

1.11

SAP AG 1999

The Work Management System simplifies and standardizes work order processing.

The process includes order planning, work approval, scheduling, field force reporting, work completion, and financial completion.

Work Management integrates various SAP components and complementary software products.

SAP AG

Summary


2

SAP AG 1999

Contents:

Organizational structures

Functional locations and equipment

Structures of installations in transmission and distribution (T&D)

Technical Objects in Transmission and Distribution

(C) SAP AG IUT221 1

2.2

SAP AG 1999


Create master data (functional locations and equipment) for structuring installations in T&D

Describe the links to the technical objects in the IS-U/CCS System

Assign functional locations and equipment to the organizational structures in the SAP R/3 System

Technical Objects in Transmission and Distribution: Unit Objectives

(C) SAP AG IUT221 2

2.3

SAP AG 1999

Technical Objects in Transmission and Distribution: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

2.4

SAP AG 1999

Technical Objects in Transmission and Distribution: Business Scenario

IDES Energy Inc. wants to supply houses in a new development with electricity. To do so, it has to extend the grid and build a new transformer station. The following new master data is generated in the IDES Energy Inc. system for this purpose:

Functional locations and equipment for the grid extension and the transformer station

Equipment for the service connections

Master data such as connection objects and premises

(C) SAP AG IUT221 4

2.5

SAP AG 1999

Organizational Structures

(C) SAP AG IUT221 5

2.6

SAP AG 1999

Company Code 1IDES AG FrankfurtCompany Code 1

IDES AG Frankfurt

Operating ConcernOperating Concern

Controlling AreaEurope

Controlling AreaEurope

Controlling AreaUSA/Australia

Controlling AreaUSA/Australia

Company Code 3IDES USA

Company Code 3IDES USA

Company Code 2IDES UK LondonCompany Code 2IDES UK London

CostCenters

Organizational Structure - Controlling

An operating concern is the central organizational element in Profitability Analysis The controlling area identifies an organizational element for which costs and revenues can be

considered. It represents a closed system for cost accounting purposes. Each company code is assigned to a controlling area. A cost center is the smallest organizational unit in Cost Center Accounting. Cost centers can, however,

also be organized hierarchically.

(C) SAP AG IUT221 6

2.7

SAP AG 1999

Company CodeIDES AG

Company CodeIDES AG

Storage Loc. 2Central Warehouse

Hamburg


Hamburg


Dresden


Dresden

PurchasingOrganization

Germany

Storage Loc. 1Incoming Warehouse

Hamburg

Storage Loc. 1Incoming Warehouse

Hamburg

Organizational Structure - Materials Management

PlantService

TerritoryHamburg

PlantService

TerritoryDresden

A plant is an organizational element within a company where goods are produced or services are provided. With utility companies, a plant may be a service territory. A plant is always assigned to a company code.

The materials can be valuated on the basis of plants or company codes (a company code or plant is the valuation area).

A purchasing organization is an organizational unit that provides materials or services for one or more plants. It also negotiates the conditions of purchase.

Storage locations are organizational units facilitating a differentiation between the various stocks of material within a plant. Vehicles can also be storage locations.

(C) SAP AG IUT221 7

2.8

SAP AG 1999

Sales Organization• Germany (South)• Germany (North)

Sales Organization• Germany (South)• Germany (North)

Distribution Channel• End Customer• Wholesale• Service

Distribution Channel• End Customer• Wholesale• Service

Division• Electricity• Gas• Water

Division• Electricity• Gas• Water

Sales Area• Germany (South)• Service• Electricity

Sales Area• Germany (South)• Service• Electricity

ServicesMaterialsPrices.........

ServicesMaterialsPrices.........

Organizational Structure - Sales and Distribution

A sales organization is responsible for selling materials and services. Each sales organization is allocated to a company code.

A distribution channel is the channel through which goods or services reach the customer. A division is a grouping of saleable products. A sales area is a specific combination of sales organization, distribution channel, and division. For you to be able to sell or offer goods or services to a customer, the customer must be assigned to at

least one sales area.

(C) SAP AG IUT221 8

2.9

SAP AG 1999

Plant 1000Plant 1000

Plant 1300Plant 1300Plant 1200Plant 1200

Work Centers

Work Centers

MaintenanceRequirementsMaintenance

RequirementsMaintenance

RequirementsMaintenance

Requirements

PlanningMaintenance

Requirements

PlanningMaintenance

Requirements

MaintenanceRequirementsMaintenance

Requirements

Material

Warehouse

Cross-Plant Plant Maintenance

A maintenance plant is not a maintenance planning plant: A technical installation needs to be maintained in plant 1200, which generates a maintenance requirement (=maintenance plant). All the remaining functions (such as maintenance planning, order execution, spare parts warehouse) are assumed by plant 1000 (=maintenance planning plant). Plant 1300 takes on the order execution itself while plant 1000 takes on the other subfunctions (order planning, spare part storage). These are examples of cross-plant maintenance.

A maintenance plant is a maintenance planning plant (plant 1000): With most organizational structures, the maintenance requirements are planned in the plant in which they arise. Maintenance orders are executed by work centers in the same plant, which also contains the spare parts warehouse.

(C) SAP AG IUT221 9

2.10

SAP AG 1999

Welding

Mechanics Electrics

MetalworkingProcess Control and

Instrumentation

CarpentryConstruction

Work Centers in Plant Maintenance and Service

A work center may be A machine or a group of machines A person or a group of people

In Plant Maintenance, work centers are used as Main work centers in the equipment and functional location master records Main work centers in a maintenance item, in the order header, or in the header of a task list Executing work centers in the operations in a task list or order

You can link a work center to the following objects A cost center Qualifications Positions People

Work centers can be structured hierarchically.


2.11

SAP AG 1999

11

Work CenterWork CenterWork Center

CostingData

CostingData

Standard Values forTask Lists and

Orders

Standard Values forTask Lists and

Orders

SchedulingData and

Available Capacity

SchedulingData and

Available Capacity

10

CostingCosting

2724,001200,00124,00

4048,00

2724,001200,00124,00

4048,00

Task List/OrderTask List/OrderLead TimeScheduling

Available Capacity

Lead TimeScheduling

Available Capacity

Functions of the Work Center

A standard value is a planned value for the execution of an operation. Costs, execution times, and available capacity can be calculated from this standard value using formulas. In the work center, the standard value key and rules for maintenance are used as a basis to define which standard values must/can be specified in the operation and which units of measurement are displayed for the standard values in the operation.

Costing is used to determine the costs of internal services and activities. It aims to assign the costs incurred to the individual cost objects. Costing links the operation to cost accounting via the work center by maintaining cost centers and activity types. If the work center is used in an operation, standard values can be entered for the activity types defined in the work center.

The dates on which the operations will be performed are determined in scheduling. For this purpose, the execution times must be calculated and referenced to the operating time of the work center. The standard values and quantities in the operations provide the basis for determining the execution time. In scheduling, this data is used to calculate the start and finish dates of the operations via formulas that are entered in the work centers for scheduling purposes.

In capacity planning, the capacity requirements of the operations in the orders are determined and compared to the available capacity defined in the work center. Work center hierarchies enable the available capacity and capacity requirements to be summarized within capacity planning, from subordinate work centers to work centers of the superior hierarchy.



2.12

SAP AG 1999

Functional Locations and Equipment


2.13

SAP AG 1999

Equipment

Individual technical objects that are maintained / for which services are performed

Examples:

Transformers

Meters

Service connections

Vehicles

Creation of multi-level hierarchical structures

Assignment to a functional location

A piece of equipment is an individual, physical object that is to be maintained as an autonomous unit. It can be installed at a functional location or in a superior piece of equipment for a certain period of time.

In the course of its useful life, it can be used at different installation locations. Pieces of equipment can be structured hierarchically, enabling the structure of complex pieces of

equipment to be represented. Pieces of equipment can be linked to one another. In this way the global network structure of a technical

system and the dependencies between the pieces of equipment can be represented.


2.14

SAP AG 1999

Functional Location

Individual technical place that is maintained/where services are performed

Structures a technical system using the following criteria:

Spatial

Technical

Functional

Example:

Transformer stations

Power plants

Buildings

Creation of multi-level hierarchical structures

Allocation of one or more pieces of equipment

A functional location is an organizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

Pieces of equipment are installed at functional locations. The times at which a piece of equipment is in use at a functional location are documented in chronological order.

Functional locations are structured hierarchically to represent the structure of the system to be maintained.

Functional locations of different hierarchies can be linked to one another. In this way, you can represent the global network structure of a technical system, the links between different technical systems and the dependencies between individual functional locations.

From an IS-U perspective, functional locations are data objects in the Plant Management (PM) application component. The connection object and device location in the Utilities Industry (IS-U) component are also functional locations.


2.15

SAP AG 1999

Equipment Master RecordEquipment Master Record

Location data

Configuration

Structure

Organizational data

Serialization data

Internal memosInternal memos

Documents/Documents/technical drawingstechnical drawings

Multilingual textsMultilingual texts

Usage listUsage listLocation A

Location B

ClassificationClassification

PartnerPartner

PermitsPermits

Test equipment 0 4 7 10 1 2 3

General data

Equipment Master Record

An equipment master record contains various types of data: General data – this is fixed data that does not usually change (for example, the acquisition value,

dimensions, and year of production of the piece of equipment). Location data and organizational data - time-dependent data (such as the maintenance planner

group, the responsible work center, address, maintenance plant, and cost center). Time-dependent data gives you a dynamic view of equipment. If you have customized your system accordingly, a new equipment usage period will be created automatically when specific changes are made to master records.

Structure - this data describes the technical objects to which the equipment is linked. Serialization data – you specify this data if you wish to manage the piece of equipment both as a

separate object in its own right and from an Inventory Management point of view. This data includes material data, inventory information, and customer information.

Configuration data – this data shows the various components of a standard product that go to make up a piece of equipment.

Partner data – this data provides information on who is responsible for a piece of equipment (for example, vendor, purchaser, employee).

For IS-U devices, the equipment master record has been extended to include various items of data required in the utilities industry (such as technical data, meter readings, and so on)



2.16

SAP AG 1999

Master RecordMaster Record

Location data

Structure

Organizational data

Internal memosInternal memos

Documents/Documents/technical drawingstechnical drawings

Multilingual textsMultilingual texts

Equipment usage periodsEquipment usage periodsLocation A

Location B

ClassificationClassification

PartnerPartner

PermitsPermits

Test equipment 0 4 7 10 1 2 3

General data

Functional Location Master Record


2.17

SAP AG 1999

Equipment Master RecordEquipment Master Record

Location data

Configuration

Structure

Serialization data

General data

Asset number

AssetsAssets

Organizational data

Equipment and Asset Accounting

The structuring of assets from a bookkeeping perspective in the FI-AA component is not influenced by the technically-oriented structuring in the Plant Maintenance (PM) component. The PM component has its own structural organization (functional location, equipment). This structure enables you to organize installations according to maintenance requirements.

You can create a link between the PM and the FI-AA components by entering the FI-AA asset number in the equipment master record. In this way, you can also

Select, in the PM component, all the installations that belong to a piece of equipmentCapitalize, in the PM component, all maintenance orders requiring capitalization to the respective assetsJump directly from the asset master record to the appropriate equipment master record (Environment)

The link between the asset and the technical object or functional location does not mean that the organizational assignments (such as to a plant) are automatically the same in both. If you change the organizational assignments in the master record of a piece of equipment or a functional location, the change is not automatically carried out in the asset. Likewise, a change made in the asset is not automatically reflected in the equipment or functional location.



2.18

SAP AG 1999

Equipmentinstallationallowed?

Individualinstallation?

Equipment

Equipmentinstallationallowed?

Equipment category

EquipmentFunctional Locations

Prerequisites for Equipment Installation

Prerequisites The master records for the functional location and the pieces of equipment must already be created in

the system. Process

Select the equipment master record in the Change mode. Go to any screen in the equipment master record. Choose Structure => Change InstallLoc. The dialog box Change Equipment Installation Location is displayed. Make all the required entries for the installation location.

Perform the installation. The following options are available for doing this: (1) Choose Inst. w. DataTransfer. The system installs the piece of equipment. You can determine the data transfer manually. Return to the dialog box Change Equipment Installation Location and (2) Choose Installation. The system installs the piece of equipment. In this case, you are not able to influence the data transfer manually. Choose Confirm. You return to the master record screen from which you called up the dialog box.

Save the equipment master record.


2.19

SAP AG 1999

Usage list

S-15S-15

Installation on 03/01/98

Dismantling on 09/20/98

03/01/ - 09/20/98 S-15

Equipment Usage List

The usage of a piece of equipment can be relevant to performance, damage frequency, breakdown behavior and the comparison of products from different manufacturers. For the purposes of maintenance, therefore, it is important that you can find out at any time when and where a piece of equipment is (or was) installed. This information may be found in the usage list in the PM system.

The usage list, or equipment history, documents the maintenance history of the equipment in relation to its usage. This may show phases during which the equipment was installed at a functional location, was directly allocated to a usage site (for example, a cost center), was stored in a warehouse or was passed on to a customer.

Similarly, there is a usage list for the functional location. This indicates in chronological order all pieces of equipment installed. The usage list therefore provides both object-related and location-related information regarding equipment usage.

The system creates "operating time segments" for each piece of equipment. These describe certain data relating to the equipment (for example, the functional location at which it is installed, the cost center to which it is allocated). The system creates new operating time segments every time certain events occur. You can define the events you wish to be relevant to the construction of a usage list in your company using the Customizing function.



2.20

SAP AG 1999

Relationships Between Technical Objects

Technical Objects in the Transmission

Substations, lines, transformer stations, transformers, circuits and so on

Modeled by functional locations and equipment

Technical Objects in IS-U/CCS

Connection objects, connections, devices, and so on

Basically modeled by functional locations and equipment

Relationships Between Both "Worlds"

Hierarchy functionality

Object links

Use of AM/FM or GIS systems


2.21

SAP AG 1999

Object Link

Logical link between objects of the same type (functional locations, equipment)

Can be a one-way link

Such as gas flow

The link itself may be a technical object

A link between two transformer stations is a piece of equipment,for example

Summary of object links of the same type using a network ID

Low voltage, region = South, for example

The object link is a logical link between objects of the same type (functional locations, pieces of equipment).

The link can be controlled (to display the flow of a medium such as water or steam, for example). The link itself may be a technical object (a link between two transformer stations is a piece of

equipment, for example). Links of the same type (such as low voltage, or region = South) can be summarized using a network ID.


2.22

SAP AG 1999

Structure of Installations in T&D


2.23

SAP AG 1999

ST 435ST 435

ST 435-AST 435-A

ST 435-BST 435-B

ST 435-A-1ST 435-A-1

ST 435-A-2ST 435-A-2

10006451000645

10008391000839

...

...

...

Substation No. 435

Conductor rail A

Transformer field 1

Transformer 400 kVA

Conductor rail B

Transformer field 2

Transformer 300 kVA

... Assemblies and spare parts


Functional location Equipment

Substation


2.24

SAP AG 1999

...

L 114L 114

L 114 01L 114 01

L 114 02L 114 02

P 187P 187

P 188P 188

...

200456200456

203478203478

201569201569

...

Line No. 114

Section 01 (0 ... 14.7 km)

Section 02 (14.7 ... 26.8 km)

Pole No. 188


Pole No. 187

Pole top

Crossarm type XA 24

Isolators type IS 45/9

Assembly

Functional Location Equipment

Line System

A technical object can be subdivided into assemblies. An assembly is not an individual object but rather an object category (similar to a material).

If a damaged object is not repaired but exchanged, it makes more sense for it to be managed as an assembly rather than as a piece of equipment.

A notification or an order can also be created for an assembly. The maintenance history of an assembly is not supported.


2.25

SAP AG 1999

Field01

Field 02

Field 03

Field 01

Field 02

Field 03

Field 01

Field 02

Field 03

Substation ST 435Substation ST 435 Substation ST 571Substation ST 571

Substation ST 768Substation ST 768

Line No. 187Line No. 187




Line system with sections

Object link to connect two systems with different hierarchies

Substation with transformer fields

Supply Grid


2.26

SAP AG 1999

...

H 008H 008

ST 114ST 114

...

High Voltage Area 008

Substation No. 114

Circuit A 13

Substation No. 117

CC A13CC A13

CC A14CC A14 Circuit A 14

CC A13-1CC A13-1 Circuit A 13 Section 1

CC A13-2CC A13-2

Transformer Station No. 1274

3008965430089654

Circuit A 13 Section 2

Transformer 400 kVA

......


Functional Location Equipment

Distribution Grid (Logical Structure)

TS 1274TS 1274

ST 117ST 117


2.27

SAP AG 1999

Service connection: gasService connection: electricityService connection: waterSupply Grid

Connection object

Premise = Apartment 1

Apartment 4

Apartment 3

Apartment 2

BusinessPartner

Street

DeviceLoc. 2:Basement

DeviceLoc. 1:Entrance Hall

Installation 1:Water

Installation 2:Gas

Installation 3:Electricity

Contract 1:Water

Contract 2:Gas

Contract 3:Electricity

ContractAccount

The IS-U House


2.28

SAP AG 1999

TechnicalinstallationsTechnical

installations

0539802

125.256.01

0716192

0539802

125.256.01

0716192

Connection object

Connection object

Premise

ConnectionConnection

Premise

DevicesDevices

Device locationDevice location

Trans-formerTrans-former

Object link

Connection objectConnection object

ConnectionConnection

Device locationDevice location

DeviceDevice

TransformerTransformer

Transformer fieldTransformer field

Equipment and Technical Objects in IS-U/CCS


2.29

SAP AG 1999

Optional PM connect.

Optional IS-U connect.

ConnectionObject

ConnectionObject

ConnectionConnectionDevice LocationDevice

LocationPremisePremise

DeviceDevice

TechnicalInstallation Technical

Installation

InstallationInstallation

1:N 1:N

1:N

1:Number of Divisions

1:N 1:N

N:M

IS-U PM PM and IS-U

1:N

Technical Data Model


2.30

SAP AG 1999

Technical objects in T&D and CCS are mapped using functional locations and equipment.

You can structure technical installations by creating hierarchies and using object links.

Structuring of objects depends on the physical structure of the supply grids.

Functional locations and equipment are to be maintained. Services can also be performed here.The functional locations and pieces of equipment are assigned to objects in the organizational structure (such as plants, cost centers).

SAP AG

Technical Objects in Transmission and Distribution: Summary


2.31Technical Objects in Transmission and Distribution: Exercises

Unit: Technical Objects in Transmission and Distribution

Topic: Functional Locations and Equipment Masters

At the conclusion of these exercises, you will be able to:

Describe the purpose of functional locations

Describe the purpose of equipment

1-1 True or False?

1-1-1 A functional location is an organizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

1-1-2 From a Utilities Industry (IS-U) perspective, functional locations are data objects in the Materials Management (MM) application component. The connection object and device location in the IS-U component are maintained as material masters in MM.

1-1-3 A piece of equipment is an individual, physical object that is to be maintained as an autonomous unit. A piece of equipment can be installed at a functional location or in a superior piece of equipment for a certain period of time. In the course of its useful life, it can be used at different installation locations.


Exercises


Topic: Technical Objects in T&D and in IS-U


Understand the functions of connections and connection objects

Understand the functions of devices and device locations

In this exercise, you create an equipment master for a service connection and install the connection in a connection object. Afterwards, you create an object link and display the link to the transformer station.

2-1 Which of the following objects are considered to be technical objects in T&D?

A. Substations

B. Overhead lines

C. Spare parts, such as bolts

D. Transformer stations

E. Business partners

2-2 Which of the following objects are considered to be technical objects in CCS?

A. Connection objects

B. Connection(s)

C. Devices

D. Registers

E. Device locations

2-3 Create an equipment master record for a service connection, install the connection in a connection object, create an object link between the connection and transformer, and display all the links to the transformer station.

2-3-1 Create an equipment master for a service connection PE0201A###. Use the following data:

Group ## equipment as the equipment description.

3000 (Connection Equipment) in the Object type field


U003 in the MaintPlant field.

2-3-2 Install the connection in a connection object TE0202A###.

2-3-3 Create an object link PE0203A### between the connection PE0201A### and a transformer. Use the following data:

Technical system - standard as the link category

In the link description field, enter Gr. ## object link.

00000003 in the Network ID field.

Link to equip. (transformer). Participants with work station numbers 01-09 should use transformer TE0204C001. Those with numbers 10-18 should use transformer TE0204C002. Transformers TE0204C001 and TE0204C002 are already created in the system.

2-3-4 Display all links to transformer station TE0204A000 and transformer field TE0204B000.

To see the links between the transformer and the connections, select transformer TE0204C001 or TE0204C002. This entry depends on your group number (groups 1-9 use TE0204C001 and groups 10-18 use TE0204C002).


2.32Solutions


Topic: Functional Locations and Equipment Masters

1-1 True or False?

1-1-1 A functional location is an organizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

True

1-1-2 From a Utilities Industry (IS-U) perspective, functional locations are data objects in the Materials Management (MM) application component. The connection object and device location in the IS-U component are maintained as material masters in MM.

False. From an IS-U perspective, functional locations are data objects in the Plant Management (PM) application component. The connection object and device location in the IS-U component are maintained as functional locations in PM.

1-1-3 A piece of equipment is an individual, physical object that is to be maintained as an autonomous unit. A piece of equipment can be installed at a functional location or in a superior piece of equipment for a certain period of time. In the course of its useful life, it can be used at different installation locations.

True


Solutions


Topic: Technical Objects in T&D and in IS-U

2-1 Which of the following objects are considered to be technical objects in T&D?

A. Substations

B. Overhead lines

C. Spare parts, such as bolts

D. Transformer stations

E. Business partners

Substations (A), overhead lines (B), and transformer stations (D) are technical objects in Work Management. The technical objects are modeled by functional locations and equipment.

2-2 Which of the following objects are considered to be technical objects in CCS?

A. Connection objects

B. Connection(s)

C. Devices

D. Registers

E. Device locations

Connection objects (A), Connections (B), Devices (C), Device locations (E) are technical objects in CCS. The technical objects are modeled by functional locations and equipment.

2-3 Create an equipment master record for a service connection, install the connection in a connection object, create an object link between the connection and transformer, and display all the links to the transformer station.

2-3-1 Create an equipment master for a service connection PE0201A###.

Choose Utilities Industry Technical Master Data Connection Create

In the Equipment field, enter PE0201A###. In the Valid on field, enter today's date. In the Equipment category field, enter A (Connection).

Choose Enter.

On the Create Equipment screen, enter Group ## equipment as the equipment description.


In the General tab, enter 3000 (IUT221 Connection) in the Object type field.

In the Location tab, enter U003 in the MaintPlant field.

Note that the status of the equipment is AVLB.

Save your entries.

2-3-2 Install the connection in a connection object TE0202A###.

Choose Utilities Industry Technical Master Data Connection Change.

Enter the Equipment, and choose Enter.

To install the connection in the connection object, choose Structure Change InstallLoc.

Enter functional location TE0202A### and choose Enter.

Note that the status of the object is INST.

Save your entries.

2-3-3 Create an object link PE0203A### between the connection PE0201A### and a transformer.

Choose Logistics Plant Maintenance Management of Technical Objects Equipment Object Link Create.

Enter PE0203A### as the link and Technical system - standard as the link category.

Choose Enter.

In the link description field, enter Gr. ## object link.

Enter 00000003 (IUT221 Network) in the Network ID field. The Network ID field provides the identification number of the object network in which the link is to be created.

Specify the Link from equip. (service connection) PE0201A### and the Link to equip. (transformer). Participants with work station numbers 01-09 should use transformer TE0204C001. Those with numbers 10-18 should use transformer TE0204C002.

Choose Enter.

Save your entries.


2-3-4 Display all links to transformer station TE0204A000 and transformer field TE0204B000.

To display the network structure from the Transformer station, choose Logistics Plant Maintenance Management of Technical Objects Functional Location Display.

Select the transformer station TE0204A000 and choose Enter.

Choose Structure Structure list to display the hierarchical structure of the transformer station and transformer field.

Choose transformer field TE0204B000. Choose Expand/collapse to display the related transformers.

To see the links between the transformer and the connections, select transformer TE0204C001 or TE0204C002 and choose Environment Links Link from/to. A list of all the links to connections is displayed. To display the links graphically, set the indicator next to the link and choose Extras Network graphic Network.


3

SAP AG 1999

Processes in Plant Maintenance and Customer Service

Contents:

Notifications and orders

Sales orders

(C) SAP AG IUT221 1

3.2

SAP AG 1999


Create notifications and orders

Explain the structure of maintenance and service orders

Describe the maintenance and service order cycles

Create sales orders

Processes in Plant Maintenance and Customer Service: Unit Objectives

(C) SAP AG IUT221 2

3.3

SAP AG 1999

Processes in Plant Maintenance and Customer Service: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

3.4

SAP AG 1999

IDES Energy Inc. has to maintain the installations in the new development. The residents of the new development require various other services, which involve the following business processes:

Entry of malfunction reports and outage notifications

Maintenance orders for the lines and the transformer station

Sales orders for energy consulting and installing service connections

Service orders for repairing devices

Confirming the orders

Processes in Plant Maintenance and Customer Service: Business Scenario

(C) SAP AG IUT221 4

3.5

SAP AG 1999

Notifications and Orders

(C) SAP AG IUT221 5

3.6

SAP AG 1999

Notifications and Orders in Plant Maintenance and Customer Service

The processes in plant maintenance and customer service involve the following objects

Notifications

Maintenance orders

Service orders

Notifications

Have a purely descriptive function

Do not contain any costs or revenues

Orders

Describe the activities to be performed

Must be processed (released, confirmed, settled)

Contain costs (maintenance orders)

Contain costs and revenues (service orders)

(C) SAP AG IUT221 6

3.7

SAP AG 1999

Malfunction report

Outage notification

Problem notification

Customer request for a service

Maintenance request

Service request

Activity report

Entry of a service activity after the service has been provided

Customer complaint

Notification of defects to vendors

Internal problem notification

Notification Types

You can define your own notification types and screen layout and reference objects, for example.

(C) SAP AG IUT221 7

3.8

SAP AG 1999

Entry of incoming maintenance and customer service requests

Access to information on

Equipment

Customer

Service object

Contracts

Warranties

Initiation and monitoring of follow-up actions

Technical completion confirmation of services

Description of a serviceable item's condition

Documentation

Notification Functions

All mentioned notification types can be created both for functional locations as well as for equipment, with or without an assembly. If these objects are part of a hierarchy, the relevant data is included in the notification. All the data relevant for the equipment and the functional location is copied automatically to the notification if You are creating a maintenance notification for an assembly of a piece of equipment The piece of equipment is assigned to a functional location

However, you can also create maintenance notifications without entering an object number if A malfunction report refers to an object that is not managed using a number in the system, A maintenance request refers to an object that is to be installed as part of an investment.

The data of the maintenance notification is transferred to the history and is of great importance when performing evaluations and future planning.

(C) SAP AG IUT221 8

3.9

SAP AG 1999

Activity carried outActionsActionsActions

TasksTasksTasks DatesTask description

Date/time/person reporting damageDescriptionMaintenance/service object: Functional location

EquipmentAssembly

Location dataAccounting dataDowntime/availability

Damage locationDamageCause of damage

DescriptionDescriptionNotificationitems

NotificationNotificationitemsitems

NotificationNotificationNotification

Notification Structure

Each maintenance notification shows a notification header. A notification header contains data that is used to identify and manage the maintenance notification. Header data is valid for the whole maintenance notification.

In a notification item you enter and maintain the data specifying the damage or problem or the activity carried out. A notification can have several items.

The tasks describe the worksteps that are to be performed, thus stressing the planning and organizational aspects. You can use the tasks to plan the interaction of different people as the notification is processed and to monitor the completion of the worksteps within a predefined period.

Actions document the work carried out on a notification. They are of particular importance for inspections because they prove that certain worksteps have been performed.

(C) SAP AG IUT221 9


3.10

SAP AG 1999

Electrical work

Mechanical work...

Code groupsCode groups

Replace cable

Replace fuse

Replace starter

CodesCodes

Tasks

Cause of damage

Activities

Object parts

Damage

Catalog typesCatalog types

Catalogs

A cross-application catalog system is used for reporting maintenance notifications. The catalog system is structured hierarchically.

The first level of the catalog system is the catalog type. Each catalog type can be subdivided further by means of code groups. You can define individual codes within each group.

For plant maintenance, the standard system contains the following catalog types: Catalog 2 for tasks Catalog 5 for causes of damage Catalog A for activities Catalog B for object parts Catalog C for damage If you would like to define your own catalog types and assign them to PM-relevant catalogs, use

catalog types R to Z.


3.11

SAP AG 1999

Basic Structure of a Work Order

For example: protective clothing, crane, traffic light, fire extinguisher, signs, excavatorFor example: protective clothing, crane, traffic light, fire extinguisher, signs, excavator

For example: materials, quantities, units of measure,storage location, batch, item category, availabilityFor example: materials, quantities, units of measure,storage location, batch, item category, availability

For example: work center, control key,description, standard time,activity type, wages

For example: work center, control key,description, standard time,activity type, wages

Equipment (assembly)Functional locationsMaintenance notifications

Equipment (assembly)Functional locationsMaintenance notifications

OperationsOperations

For example: order type, dates, plant, reference object,priority, description

For example: order type, dates, plant, reference object,priority, descriptionOrder headerOrder headerOrder header

Object listObject list

Material listMaterial list

Settlement ruleSettlement rule

Costs (planned/actual)Costs (planned/actual)

Production resourcesProduction resources

Header data is information used to identify and manage maintenance orders. This information applies to the whole order. Examples of header data are the order number, description, order type, dates for order execution, priority, the person who created the order and the person who last changed it.

The object list contains functional locations, equipment, assemblies, maintenance notifications, and/or materials with serial numbers. A single object can be entered in the order header as a reference object. In the object list, several objects can be entered.

Operations are used to describe the work to be carried out according to the order (the process includes e.g. the work center, the time required and the control key).

Materials are spare parts that are needed and used to execute the order. Production resources (e.g. tools, protective clothing, and special heavy goods vehicles) are also needed

to execute the order, but are not actually used in the order. The data in the settlement rule states who is usually responsible for the costs. The data is taken from the

master record of the reference object. It can, however, be changed during the first steps of the billing process for the order.

The cost data informs you of the estimated costs, as well as the planned and actual costs of the order, the relevant cost categories for the order, the updating of key figures in the PMIS with value categories, and the updating of these key figures with actual costs.



3.12

SAP AG 1999

Order Processing Steps

Only for service orders

Completion confirmationCompletion Completion

confirmationconfirmation

Technical completionTechnical completionTechnical completion

ExecutionExecution

PrintingPrinting

Entry/notificationEntry/notification

PlanningPlanning

ReleaseRelease

Billing documentBilling documentBilling document

SettlementSettlementSettlement

Business completionBusinessBusiness completioncompletion

Processing begins when a customer or employee reports an outage, a malfunction, or submits another request (for a modification, for example). An order can be created directly or on the basis of a notification.

Typical planning tasks include specifying operations, reserving spare parts or determining work hours. The order is then transferred to scheduling and controlling. Availability is checked, required capacity is

provided, required shop papers are printed. The execution phase comprises the issue of spare parts from stock and the actual execution of the order. When the work is completed, the actual times required to do the work are backreported/confirmed. Other

technical information is also entered to document repair and to record the condition of the technical system. The order is then settled in Controlling.

With a service order, billing is performed before the settlement and the customer is invoiced.


3.13

SAP AG 1999

Malfunction, errorRequestActivity

Malfunction, errorRequestActivity

Maintenance notificationWhatWhenWhereTechnical infoOutage

Order creationPlanning the task

WhoWhen, how longWhich stepsAccount assignmentResources

ExecutionMaterial issueMaterial procurementWork steps

Technical informationMalfunctionCausesObjects affectedActivity

Maintenance history

Conclusion

Request atask

111

Order

Confirmation

Close

222 333 444

555

666

777

Maintenance PlantMaintenance Plant Maintenance Planning PlantMaintenance Planning Plant Work CenterWork Center

Fundamental Maintenance Processing Steps


3.14

SAP AG 1999

Work Order Supervisor

Static meter reading note

Connection object Business partnersSD-Customer

Work Order

Meters

A connection object supervisor (e.g. a janitor) can be automatically assigned to a work order The connection object is determined using a device, a technical installation or equipment Customizing / system settings:

Define static meter reading notes Define partner determination procedure and function Define partner function and meter reading notes for the supervisor


3.15

SAP AG 1999

Operationcontrol ticket

Picking list

Job ticket

Proposal per order type

Proposal per order type

Printing: Papers for Orders

Operation control ticket The operation control ticket provides the maintenance planner responsible with a complete overview of the maintenance order. It also contains detailed information about permits.

Job ticket This accompanies the order and provides the person performing the task with an overview of the order. Graphics can be printed on the job ticket if the document management system has been installed.

Picking list This informs stockkeeping of the materials picked for each operation. Material withdrawal slip This authorizes the worker to withdraw the materials required for the order. Time tickets These are printed for operations, for which the control key for the order indicates that

printing should take place. The worker enters the time that was required to perform the operation. Shop papers can be printed individually for one or more orders at the same time, or for individual

operations. They can also be printed retrospectively. As soon as you have printed shop papers for a maintenance order, the system sets the appropriate status

and generates a log. You can use the log to determine which papers have already been printed, who initiated this, and when they were printed.


3.16

SAP AG 1999

Printing Work Orders with IS-U Data

PM work orders shop papers do not include IS-U data

IS-U shop papers:

Extension of the PM printing reports

Extension of the PM printing forms

Definition of IS-U shop papers for business processes

Example:

IS-U Job Ticket: General shop paper with IS-U data

IS-U Meter Reading: Shop paper for aperiodic meter readings

IS-U Disconnection: Shop paper for collection & disconnection

Shop papers are documents required for the execution of a maintenance order. PM work orders shop papers do not include IS-U data.

For IS-U, the following shop papers are available: E030 : IS-U: Job ticket E080 : IS-U: Disconnection/reconnection E090 : IS-U: Aperiodic meter reading

The shop papers can be copied from the configuration of the order type.


3.17

SAP AG 1999

Initial Screen Single entryCollective entryCollective entry via operation list

Scope Partial confirmationCompletion confirmation

Cancellation option

Controlper order type Automatic final confirmation

Allowed deviationsDisplay of cost log

Time Confirmations

The following entry forms are available for the central confirmation function: Individual entry for each maintenance order and operation (you call up an overview of all operations

and sub-operations for a particular maintenance order and enter confirmation data for the desired order operations using the central confirmation function.)

Confirmations for operations are often filled out by the employees executing the operation on a paper form. This data is entered in the system by a typist at a later stage. To facilitate the entry of this data, you can use the collective confirmation.

If certain confirmations have been entered for the operations/sub-operations of a maintenance order, the operations/sub-operations are automatically assigned the status "partially confirmed" by the system.

As soon as all the operations/sub-operations of a maintenance order have been finally confirmed, the maintenance order itself is also assigned the status "finally confirmed".

Confirmations may have been entered for the wrong operations/sub-operations or with incorrect data by mistake. With this in mind, the system provides you with a function for canceling confirmations.


3.18

SAP AG 1999

Maintenanceorder

Resources used

Resources used

LaborMaterialTravel

Overheads

LaborMaterialTravel

Overheads

Costs

SettlementSettlement

AssetCost center

Project (WBS el.)Order

MaterialG/L accountAsset under construction

AssetCost center

Project (WBS el.)Order

MaterialG/L accountAsset under construction

Order profitability

Settlementrule

Settling a Maintenance Order

Costs are charged to the order through order completions, goods issues, travel expense reporting and so on.

In settlement, costs are transferred to: Financial Accounting (G/L account) Asset Accounting (fixed asset) Inventory Management (material) Cost Accounting (order, cost center) The Project System (WBS element, network)


3.19

SAP AG 1999

Resource-relatedbilling

Revenue

Billing & Settling a Service Order

Service order

SettlementSettlementProfitabilitysegment orG/L account

Profitabilitysegment orG/L account

Order profitability

Settlementrule

Resources used

Resources used

LaborMaterialTravel

Overheads

LaborMaterialTravel

Overheads

Costs

Billing document

Billing document

The service has been provided and the customer is to pay for the service received. Costs are charged to the order through order completions, goods issues, travel expense reporting and so on.

The billing process is run. As a result of this process, a new cost object (revenue) has been added to the service order.

The order is settled to Profitability Analysis (CO-PA) or general ledger: a profitability segment is a combination of account assignment features, such as company code, sales organization, division, customer, article, and sales order. If CO-PA is not in use, costs and revenues can be settled to G/L accounts.

During the service order process, costs and revenues are collected in (or assigned to) the order. This is why it is often referred to as a cost collector (not a holder or a container).

With service orders without revenues, the costs are settled to the following elements: Sales document item (for service contracts, for example) Cost center (for processing warranties) Orders from Controlling Work breakdown structure elements G/L accounts.



3.20

SAP AG 1999

Settlement Rule

The order settlement is controlled by the settlement rule.

This determines the sender and receiver for costs and the receiver for revenues of the order.

It is determined automatically on the basis of the object and customer data entered.

Manual changes can be made.

Prerequisites for settling an order: The order must be released A settlement rule must be available The order must contain costs and revenues that have not yet been settled


3.21

SAP AG 1999

Sales Orders


3.22

SAP AG 1999

Customer quotation

Legally-binding offer to a customer

Sales order

Order placed by the customer (which refers to a quotation, for example)

Orders and quotations usually include the following:

Items with the offered or ordered quantity of a material or service

Customer and material information

Pricing conditions for each item

Schedule lines and delivery information

Billing information

Sales Documents

An overall distinction is made between the following groups of sales documents: Customer inquiries and quotations Sales orders Outline agreements, such as contracts and scheduling agreements Complaints, encompassing free of charge deliveries, credit/debit memo requests and returns

From the sales document, you can create and process deliveries and billing documents. In addition, some sales documents, such as cash sales and rush orders, automatically trigger the creation of subsequent delivery and billing documents.

The total quantity can be subdivided between the schedule lines in different amounts and relevant delivery dates.

Items can be structured hierarchically. This enables a differentiation according to batches or an explosion of combined materials (BOMs).

The valid conditions for the items are listed in the item conditions. The conditions for an item can be derived from a global condition that is valid for the complete quotation or order.


3.23

SAP AG 1999

InvoiceDelivery Accountingdocument

Sales documents represent business processes.

The business processes represent a chain of consecutive documents, the document flow.

The R/3 System copies data from one document into another to reduce manual data entry and makeproblem solving easier.

Document flow of a sales order

Order 900. Service order 80000459. . Confirmation 1000000062. .. Invoice 90000333. . . Accounting document 100000276

Serviceorder

OrderQuotation

Contract

Sales Document Flow

The document flow displays the progress of a sales order. It shows all the documents associated with the sales order.


3.24

SAP AG 1999

Header

Item 1

Schedule line 1

Item 2

Schedule line 1

Schedule line 2

Customer-related data for the whole orderCustomer-related data for the whole order

Data for the material ordered or for the serviceData for the material ordered or for the service

Delivery information, such as• Delivery quantity• Delivery date• Service order that is linked to

the sales order

Delivery information, such as• Delivery quantity• Delivery date• Service order that is linked to

the sales order

Structure of a Sales Order

The sales order is a contractual agreement between a sales organization and a sold-to party about delivering products or providing a service for defined prices, quantities and times. In the sales order, functions such as pricing and printouts are available. The system checks whether the material is available for the requested delivery date and, if necessary, transfers the requirements to materials planning. The system generates shipping dates and points in delivery scheduling.

When you process a sales order using the standard version of the SAP R/3 System, the system can carry out basic functions, including:

Price determinationAvailability check (if this function is defined in the material master record)Transferring requirements to materials planning (MRP)Scheduling agreement schedule lineShipping point and route determinationChecking credit limits


3.25

SAP AG 1999

Header

Item 1

Item 2

Billing documents are similar to sales documents in their structure.

Information on the whole invoiceInformation on the whole invoice

Information on the material or service that is to be invoicedInformation on the material or service that is to be invoiced

Structure of the Billing Document

Billing document is an umbrella term for invoices, credit memos, debit memos, pro forma invoices and cancellation documents.

The billing document is created with reference to a preceding document, to create an invoice or a credit memo.

All billing documents have the same structure. They are made up of a document header and any number of items.


3.26

SAP AG 1999 SAP AG

The processes in Plant Maintenance and Customer Service use notifications, maintenance and service orders.

The standard work order cycle consists of entering, planning, releasing, printing, executing, confirming, completing, billing, and settling orders.

Maintenance orders and service orders use the same structure. Service orders can be billed in a resource-related manner and invoiced to the customer.

Service orders with revenues are settled in profitability analysis to profitability segments or G/L accounts.

Plant Maintenance and Customer Service Processes: Summary


3.27Processes in Plant Maintenance and Customer Service: Exercises

Unit: Processes in Plant Maintenance and Customer Service

Topic: Notifications

At the conclusion of these exercises, you will be able to

Understand the notification process

Understand the functions of notifications

1-1 Which of the following elements are functions of notifications?

A. Entry of incoming maintenance and customer service requests

B. Access to equipment, customer, serviceable, contracts, warranties

C. Initiation and monitoring of follow-up actions

D. Technical completion confirmation of services

E. Description of a serviceable item’s condition

F. Documentation

1-2 True or False? The structure of notifications includes header, items, activities and tasks.

1-3 Which of the following are notification types?

A. Malfunction report

B. Activity report

C. Maintenance request

D. Service notification

E. Customer complaint

F. Notification of defects to vendors

G. Internal problem notification


Exercises


Topic: Maintenance Orders


Understand the maintenance order functions

Understand the basic structures of maintenance orders

2-1 True or False?

2-1-1 The maintenance order functions are planning, execution, and completion and settlement.

2-1-2 The basic structures of maintenance orders are order definition, network, activities, activity elements and milestones.


Exercises


Topic: Service Orders


Understand the functions of service orders

Describe the structure of the service order and the characteristics of each part of the structure

You will now create a service order in the CIC, and then display and release the order. You will also create a time confirmation and create an activity report.

3-1 Describe the three functions of service orders and the characteristics of each function.

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

3-2 Describe the structure of the service order and the characteristics of each part of the structure.

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________


3-3 Create a service order using the CIC. Make sure that the relevant caretaker is also transferred to the service request. Release the order, perform a time confirmation, and create an activity report.

3-3-1 Define business partner TE0501A### as the janitor responsible for the connection object in which business partner TE0301A### lives.

3-3-2 Create a service order using the CIC and the following master data:

Business partner number TE0301A###

Service orders Create repair order

3-3-3 Display the service order in CIC and release it for processing. Is the janitor entered as the partner? Make a note of the order number.

Service order number = ___________________________

3-3-4 Perform a time confirmation (completion confirmation) for the service order. Use the following data:

Service order in the Order field

Parameters - Final confirmation.

3-3-5 Create an activity report (notification) for the service order. Use the following data:

Notification type S2


Exercises


Topic: Sales Orders


Understand the structure of the sales order

Understand the sales order process

Describe the data stored in the sales document header, items, and schedule lines

Create a sales order and invoice the customer for the service

4-1 True or False?

The sales order is a contractual agreement between a sales organization and a sold-to party about delivering products or providing a service for defined prices, quantities and times.

4-2 (Optional) Create a sales order for energy consulting services for your customer.

Order Type OR (Standard Order) and enter Organizational data.

Business partner TE0302A### as the Sold-to party

IUT221 Material for energy consulting and Order quantity.

4-3 (Optional) Create an invoice for energy consulting services for your customer.


Exercises


Topic: Billing the Service


Understand the definition of the billing document

Understand the structure of the billing document

Describe the data found in the billing document header and items

5-1 True or False?

5-1-1 Billing document is an umbrella term for invoices, credit memos, debit memos, pro forma invoices and cancellation documents.

5-1-2 Billing documents and sales documents are the same type of document. They consist of header and schedule line items. The header contains information on the complete invoice. The schedule line items contain information about the material being invoiced.


3.28Solutions


Topic: Notifications

1-1 Which of the following elements are functions of notifications?

G. Entry of incoming maintenance and customer service requests

H. Access to equipment, customer, serviceable, contracts, warranties

I. Initiation and monitoring of follow-up actions

J. Technical completion confirmation of services

K. Description of a serviceable item’s condition

L. Documentation

All of the above are functions of notification.

1-2 True or False? The structure of notifications includes header, items, activities and tasks.

True. A notification header contains data that is used to identify and manage the maintenance notification. Header data is valid for the whole maintenance notification. In the notification item, you enter and maintain the data specifying the damage or problem or the activity carried out. Activities document the work carried out on a notification. They prove that certain worksteps have been performed. Tasks describe the worksteps that are to be performed, thereby stressing the planning and organizational aspects.

1-3 Which of the following are notification types?

H. Malfunction report

I. Activity report

J. Maintenance request

K. Service notification

L. Customer complaint

M. Notification of defects to vendors

N. Internal problem notification

All of the above are considered to be notification types.


Solutions


Topic: Maintenance Orders

2-1 True or False?

2-1-1 The maintenance order functions are planning, execution, and completion and settlement.

True. Components of the planning phase are objects, object links, work centers, operations, capacity planning, materials, BOMs, task lists and costs. The execution phase includes shop papers, material withdrawals, purchase order, goods receipts and invoice receipt. Completion and settlement consists of completion confirmation, technical confirmation, and settlements to cost center, assets, projects, orders, and so on.

2-1-2 The basic structures of maintenance orders are order definition, network, activities, activity elements and milestones.

False. The basic structures of maintenance orders consist of header data (information used to identify and manage maintenance orders); object list (functional locations, pieces of equipment, assemblies); operations (describing the work to be carried out on the order); materials (spare parts needed for and used up during the order execution); production resource/tools (tools, protective clothes needed during order execution but not used up); settlement rule (determines who will be debited with the costs); and cost data (estimated, planned and actual order costs).


Solutions


Topic: Service Orders

3-1 Describe the three functions of service orders and the characteristics of each function.

Planning services includes functions such as repair, servicing and inspection, installation, and modification. The characteristics of planning include (1) description of work to be performed, (2) resource planning (internal and external employees, materials and tools) and (3) scheduling for execution.

Execution and monitoring includes characteristics such as (1) printout of order papers containing information relevant for execution, (2) documentation of work papers using activity reports and completion of operations and (3) confirmation of times, materials withdrawals, goods receipts and billing documents.

Settlement of expenses incurred as a result of the order includes characteristics such as (1) internal settlement of costs and revenues to cost objects or to a contract and (2) external billing of expenses to a customer.

3-2 Describe the structure of the service order and the characteristics of each part of the structure.

The order header contains the description, responsibilities, dates, reference objects, settlement rules, and planned and actual costs. Address data, internal and external partners as well as permits can also be assigned to the order header.

If the order applies to several serviceable items, these are entered in the object list. If the order has been created from several notifications, these also appear in the object list.

The order contains one or more operations. These are the individual worksteps that are executed by internal or external employees.

If a more detailed structure is required, one or more sub-operations can be created for each operation.

Components, which may or may not be stock material, can be assigned to each operation.

Tools required for the execution are also assigned to the operation. These may be materials (that is, materials that are not consumed), equipment or documents.

3-3 Create a service order using the CIC. Make sure that the relevant caretaker is also transferred to the service request. Release the order, perform a time confirmation, and create an activity report.


3-3-1 Define business partner TE0501A### as the janitor responsible for the connection object in which business partner TE0301A### lives.

Choose Utilities Industry Customer Service Front Office/Customer Interaction Center Customer Interaction Center

Using the search criteria in Front Office, identify your business partner by entering the Business partner number TE0301A###. Choose Enter twice.

In the business partner's data environment, open the menu using the right mouse button at premise level and then choose the front office process connection object environment.

Select the connection object and choose Change Object.

Choose Notes.

Enter H1 (caretaker) in the SN (Static note) field.

Enter TE0501A### in the Business partner field.

Select Enter, save and return to the CIC.

3-3-2 Create a service order using the CIC.

In the business partner's data environment, open the menu using the right mouse button at device level and then choose the front office process Create repair order

The service order is created in the background.

A customer contact is also created. Save the entries on the Create Contact screen.

3-3-3 Display the service order in CIC and release it for processing. Is the janitor entered as the partner? Make a note of the order number.

Call up the Documents tab page and choose Refresh.

Select Service orders and choose the Change function for the device repair.

Change the status of the service order by choosing Put in process. In the dialog box, choose W/o print.

Display the service order again and make sure the status has changed to REL.

Select the Partner card and check that the caretaker has been entered.

Service order number = ___________________________


3-3-4 Perform a time confirmation (completion confirmation) for the service order.

Choose Utilities Industry Work Management Processing Service Processing Confirmation Entry Individual Confirmation (Time)

In the Order field, specify the service order number and choose Enter.

Select Parameters and set the Final confirmation indicator.

Select all of the operations and choose Actual data.

You can view the confirmation data of the individual operations by using the Previous operation and Next operation options.

Save your entries.

3-3-5 Create an activity report (notification) for the service order.

Choose Utilities Industry Work Management Processing Service Processing Order Service Order Change.

Choose Notification.

In the Notification type field, enter the Notification type S2 (Activity Report).

In the activity report, maintain the data on Object part, Damage, and Cause code under Items.

Save your entries.


Solutions


Topic: Sales Orders

4-1 True or False?

The sales order is a contractual agreement between a sales organization and a sold-to party about delivering products or providing a service for defined prices, quantities and times.

True.

4-2 (Optional) Create a sales order for energy consulting services for your customer.

Choose Logistics Sales and Distribution Sales Order Create.

Enter order type OR (Standard Order) and the organizational data.

Enter your business partner TE0302A## as the Sold-to party, a Purchase order number, IUT221 Material for energy consulting, and the Order quantity 1.

Choose Enter and the material data is automatically completed.

Save your entries and note the order number.

4-3 (Optional) Create an invoice for energy consulting services for your customer.

Choose Logistics Sales and Distribution Sales Order Change.

Enter your order number and choose Enter.

Choose Sales document Billing

Choose the desired items and save.


Solutions


Topic: Billing the Service

5-1 True or False?

5-1-1 Billing document is an umbrella term for invoices, credit memos, debit memos, pro forma invoices and cancellation documents.

True

5-1-2 Billing documents and sales documents are the same type of document. They consist of header and schedule line items. The header contains information on the complete invoice. The schedule line items contain information about the material being invoiced.

False. Billing documents are the same as sales documents. They contain header and line items. The header contains information for the entire invoice. The line items contain information about the material being invoiced.


4

SAP AG 1999

Contents:

The service product concept

Variant configuration basics

Configurable service products

Multi-level structure of service objects

Further functions of variant configuration

Service Products

(C) SAP AG IUT221 1

4.2

SAP AG 1999


Describe the concept of the service product and the service object

Define configurable service products

Use simple variant configuration functions

Describe further variant configuration functions

Service Products: Unit Objectives

(C) SAP AG IUT221 2

4.3

SAP AG 1999

Service Products: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

4.4

SAP AG 1999

IDES Energy Inc. wants to create maintenance and service orders more efficiently and offer their customers certain services as products.

To do so, IDES Energy Inc. wants to define service objects and service products that standardize and automate the order creation process. Examples:

The service product "Create Connection"

The service object "Device Repair"

The service object "Mainline Extension"

Service Products: Business Scenario

(C) SAP AG IUT221 4

4.5

SAP AG 1999

The Service Product Concept

(C) SAP AG IUT221 5

4.6

SAP AG 1999

Service order

Customerorder

Sales viewPrice information Characteristics

ValuesDependencies

Functional locationEquipment

TechnicalObject

Serviceproduct

Task list

Service material

Configur.

Work description Resources for work, material.....

External resources

The Service Product

To process customer-related business transactions, IS-U uses the sales order from Sales and Distribution (SD) and the service order from Customer Service (CS). The service product is a service that is offered and sold in SD and provided in CS. When the SD order is created (or even earlier, when the SD quotation is generated - you specify which of the two in Customizing or in your master data), a service order is automatically generated at the same time.

You can also assign a task list to a service product and specify a technical object (a piece of equipment, for example) for which the service is to be carried out. The task list describes the work to be carried out using a list of individual operations. Each operation can be assigned components (materials, production resources/tools) that are necessary for the work to be carried out. Validity periods are also specified for the operations.

The service is described in more detail by assigning values to special characteristics for the service product (= configuration).

The system copies the task list and the technical object to the service order. Using the configuration in the sales order or in the technical object you can define the task list individually.

A material master record of material type DIEN (service) or material type KMAT (configurable material) belongs to each service product

(C) SAP AG IUT221 6

(C) SAP AG IUT221 7

4.7

SAP AG 1999

CharacteristicsValues

Dependencies

Functional locationEquipment

Technicalobject

Serviceobject

Task list

Configur.

PM/SM order

Work descriptionResources for work, material...

External resources

The Service Object

The service object (also known as a compatible unit) is a service product without a sales view. This means that it is not offered to the customer but is sold with a sales order. It is used to create maintenance and service orders in a standardized manner. Like a service product, the service object is also configurable.

(C) SAP AG IUT221 8

4.8

SAP AG 1999

Service Product "Install Service

Connection"

Service Product "Install Service

Connection" Task List

1. ExcavationTime: 0.5h per mTool: Excavator

2. Protect trenchonly with loose soil

3. Lay cableMaterial: X m cable

4. Install connection boxTime: 1hMaterial: Connection box

5. Refill trenchTime: 0.2 h per m

Configuration

Chars Values

Soil Condition: Loose

Length: 10m

Connection type: A

Work by sold- Yesto party

Service Material

Cable per m 60

Excavation per m 150

Connection box Type A 1200Type B 1500

Discount for work 300by sold-to party

Service objectService object

Service orderService orderQuotation, sales orderQuotation, sales order

The Service Product "Install Service Connection"

The Service Product plays the central role in service processing for service connection. The clerk enters the configurable service product Install Service Connection as an item in an SD quotation (or directly in the SD order, if created without reference to a quotation) and configures it.

(C) SAP AG IUT221 9

4.9

SAP AG 1999

Work by Sold-To Party

(e.g. excavation)

Total Length

(e.g. 100 m)

Service Product

e.g. Install service connection

Division

(e.g. electricity)

Connection Capacity

(e.g. 100 A)

Cable Quality

(e.g. cable type A)

Type of Connection

(e.g. underground cable, overhead line)

Soil Condition

(e.g. normal soil)

Characteristics and Characteristic Values

The service product, such as Install Service Connection, can be described precisely with various characteristics.

Characteristic values represent specific instances of characteristics. You assign the characteristics to the material master record of the service product using the SAP

classification system.


4.10

SAP AG 1999

Service ProductInstall service

connection

Configuration Profile

Class 1(e.g. technical properties)

Class 2(e.g. properties describing

the service activity)

Characteristic 1(e.g. connection capacity)

Characteristic 2(e.g. connection type)

Characteristic 3(e.g. soil condition)

Characteristic 4(e.g. work by sold-to party)

Class and Configuration Profile

A class is a group of objects sharing the same or similar properties. Each class contains characteristics that describe these properties. Allowed characteristic values can be

defined for each characteristic. The configuration profile determines which classes and therefore which characteristics can be used to

describe a particular object to be classified. In the example, two different classes were created: Class 1 contains the technical properties of the

service product and Class 2 contains properties that describe the service activity. Allocating characteristics to different classes like this is particularly useful when it comes to modeling the service connection as equipment in PM: you can specify just the technical characteristics in the equipment data while using the service-related characteristics for costing and pricing in the quotation.


4.11

SAP AG 1999

Configuration of Service Products

Configuration is the assignment of characteristic values

The configuration of the service product controls:

The derivation of operations and components (that is, materials and production resources) for automatic creation of the PM or SM order

Costing and pricing in SD

Configuration of the related equipment


4.12

SAP AG 1999

Variant Configuration Basics


4.13

SAP AG 1999

Components of the Knowledge Base

Object dependencies describe dependencies between characteristics, characteristic values, and objects

Types of object dependencies

Precondition

Selection condition

Action

Procedure

Constraint

The following are called up in the configuration:

Characteristics

Task lists

Materials

The information that is called up during the configuration of a material represents the knowledge base of a configuration.


4.14

SAP AG 1999

Determines whether a characteristic or characteristic value

can be included in the configuration

Determines whether a characteristic or characteristic value

can be included in the configuration

Precondition for a Characteristic Value

Characteristic Characteristic Value Precondition

Connection box Type AType B

Max. elec. 40 A60 A100 A Connection box = Type B

Precondition for a Characteristic

Characteristic Characteristic Value Precondition


Flush-type? Connection box = Type B

Precondition


4.15

SAP AG 1999

Determines whether a characteristic, a task list operation, or

a BOM item must be included in the configuration

Determines whether a characteristic, a task list operation, or

a BOM item must be included in the configuration

Selection Condition for a Characteristic

Operation Description Selection Condition

0010 Excavation Loose Soil Soil condition = light0020 Excavation Normal Soil Soil condition = normal0030 Excavation Heavy Soil Soil condition = heavy

Selection Condition for a Task List Operation

Characteristic Characteristic Value Selection Condition


Flush-type? Yes Connection box = Type BNo

Selection Condition

Selection Condition for a Characteristic: The "flush-type" characteristic must be valuated if type B has been chosen as the connection box. The syntax for this selection condition for the characteristic is: Connection box eq 'B'.

Selection Condition for a Task List Operation: Depending on the valuation of the soil, one of the possible operations (10, 20, or 30) is copied to the

service order. The syntax for this selection condition for the operation is: Connection box eq 'B'.


4.16

SAP AG 1999

Sets characteristic values

Activities can be assigned to characteristics,

characteristic values, and configuration profiles

Sets characteristic values

Activities can be assigned to characteristics,

characteristic values, and configuration profiles

Assignment to Characteristic Value Type B:

Max. elec. = 100 A

Assignment to the Characteristic Connection Boxor to the Configuration Profile Install Service Connection:

Max. elec. = 100 A if connection box = type B

Characteristic Characteristic Value Action

Connection box Type AType B Max. elec. = 100 A

Max. elec. 40 A60 A

100 A

Action

If type B is chosen as the connection box, the maximum electricity will always be 100A. With type A, 40, 60, or 100A are possible.

The condition can be defined in three different places: In the characteristic value "B". The syntax is then: $SELF.MAXELECTRICITY = 100. In the characteristic "Connection box" or in the configuration profile for the service product "Install

service connection". The syntax is then: $SELF.MAXELECTRICITY = 100 if connection box = `B`. If a value is derived for a characteristic, this characteristic is flagged in an action with $SELF.


4.17

SAP AG 1999

Procedure

Sets characteristic values that can either be changed by other

procedures or changed again manually

Several procedures for an object can be organized into an

evaluation sequence

Procedure

Sets characteristic values that can either be changed by other

procedures or changed again manually

Several procedures for an object can be organized into an

evaluation sequence

Constraint

Describes dependencies between several objects and their

characteristics

Monitors the consistency of configurations

Is assigned to the configuration profile

Constraint

Describes dependencies between several objects and their

characteristics

Monitors the consistency of configurations

Is assigned to the configuration profile

Procedure and Constraint


4.18

SAP AG 1999

Reference Characteristics

Reference characteristics refer to table fields

The data from the field (format, length) is copied

The field contents can be changed in actions or procedures with reference to reference characteristics

Example:

The work effort for the excavations is to be calculated from thelength of the service connection

Setting the execution factor: Work effort and material quantity are calculated simultaneously from the length

Price determination

Calculating the work effort for an excavation: Define a reference characteristic WORK EFFORT with reference to the ARBEI field in the PLPO

table. This field is used in the operations of the task lists. For the operation of the "Perform excavations" task list, the following action is defined:

$SELF.WORK EFFORT = LENGTH. The execution factor (field AUFKT in the PLPO table) can be influenced in the same way. This factor

does not only influence the work effort but also the required material quantity. If the price depends on the configuration, you need a reference characteristic with reference to the

VKOND field in the SDCOM table.


4.19

SAP AG 1999

Configurable Service Products


4.20

SAP AG 1999

Configuration profilewith control parameters

Configuration profilewith control parameters

Object dependenciesObject dependencies

Service productService product

Variant class(es)Variant class(es)

Suitable characteristicsSuitable characteristics

Super BOM with all possible items

Super BOM with all possible items

Super task listwith all possible operations

Super task listwith all possible operations

Object dependenciesfor BOM items

Object dependenciesfor BOM items

Object dependencies forelements of the task list

Object dependencies forelements of the task list

Configurablematerial

Configurablematerial

Defining a Configurable Service Product

You need to perform various individual steps when setting up the knowledge base for a service product. You need the characteristics that describe the material as a basis. You use the characteristics in a class

defined for variant configuration. You maintain object dependencies for the characteristics and characteristic values so that only allowed values can be chosen.

You also maintain the settings required for the configurable material in the material master. You create a configuration profile for the material by defining the configuration parameters and assigning the material to the class with the descriptive characteristics.

The components and operations for a configurable material are defined in a super BOM and super task list. You maintain object dependencies for the operations and components that can only be chosen for certain variants.

Before you use the configuration of a material productively, you should perform a simulation of the configuration to check whether all the data has been maintained correctly.


4.21

SAP AG 1999

IF Soil condition = looseIF Soil condition = normalIF Soil condition = hard

IF Soil condition = looseIF Soil condition = normalIF Soil condition = hard

Super Task List0010 Excavation (loose soil)0020 Excavation (normal soil)0030 Excavation (hard soil)

0040 Lay cableCable type ACable type B

0050 Install connection box type AConnection box type A

0060 Install connection box type BConnection box type B

Super Task List0010 Excavation (loose soil)0020 Excavation (normal soil)0030 Excavation (hard soil)

0040 Lay cableCable type ACable type B


0060 Install connection box type BConnection box type B

Configuration of theService Product:

Soil condition = normalConnection type = A

Configuration of theService Product:

Soil condition = normalConnection type = A

Task List in the Generated Service

Order

0020 Excavation (normal soil)

0040 Lay cable cable type A


Object Dependencies

Configurable Task Lists

Task lists can be configured.

The configuration data is used to determine the required operations and components automatically.

You use object dependencies for the characteristics in question.

You only have to create the super task list.

A configurable task list enables you to create frequently recurring work orders (such as installation of a service connection) easily and flexibly. To do this, a full specification of the task list must first be defined. Among other things, the task list contains a list of operations, a list of the required materials and production resources/tools and planned times for the operations.

Once the task list is configured, it is included in the generated service order. The operations that are determined using the current configuration data are taken from the super task list using object dependencies.


4.22

SAP AG 1999

Service Product Install Service Connection 3000• Length up to 10m• Connection box type A• Not work by sold-to party

Service Product Install Service Connection 3000• Length up to 10m• Connection box type A• Not work by sold-to party

Quotation, sales orderQuotation, sales order

Condition Records:

• Extra charge for extra length 250

• Discount for work by sold-to party 10%

• Extra charge for connection boxes type B 300

Condition Records:

• Extra charge for extra length 250

• Discount for work by sold-to party 10%

• Extra charge for connection boxes type B 300

SD Pricing Total PriceSD Pricing Total Price

Characteristics of Service Product:• Extra length?• Connection box• Work by sold-to party?

Characteristics of Service Product:• Extra length?• Connection box• Work by sold-to party?

Configuration and Pricing

You can define a base price for a configurable material. The price also depends on the properties resulting from the characteristic value assignment.

You can define surcharges and discounts using characteristics and characteristic values in conjunction with condition records.

Information identifying the condition records to be considered for pricing is sent to SD.


4.23

SAP AG 1999

Defining Pricing

Create a reference characteristic with reference to field VKOND in table SDCOM.

Define condition records for condition type VA00 (absolute amounts) or VA01 (percentage amounts).

The pricing procedure in SD must consider VA00 or VA01.

Two possible links to the service product:

Link the condition record to the characteristic value.

Create object dependencies with condition records to valuate thereference characteristic and assign them.

For the surcharges and discounts, you define variant conditions in table SDCOM. For variant conditions, there are the condition types VA00 (absolute amounts) and VA01 (percentage amounts). You create variant conditions with reference to a material, a distribution channel, and a sales organization. Either VA01 or VA00 can be used in pricing. You can choose the any keys you want for the condition records (note: the difference between lower and upper-case spelling).

You control when a surcharge or discount will take place by assigning characteristic values or using object dependencies. You call up the condition table in the object dependencies using a reference characteristic that refers to table SDCOM and field VKOND.

You have two options for determining when a surcharge or discount will take place: From the link between the characteristic values and the keys of the condition records From object dependencies: the valuation is performed using the reference characteristic with the keys

of the condition records. In the object dependencies (actions, procedures), the reference characteristic (here "surcharge") is

valuated with the keys of condition records in certain circumstances. $SELF.<Reference characteristic> = `Key of the condition record´ if <condition>Example: $SELF.SURCHARGE = `Extra charge_xyz´ if CONNECTION BOXES eq `TypeB´


4.24

SAP AG 1999

ServiceproductServiceproduct

Modelwork order

Modelwork order

Settlementrules

Settlementrules

Create a work order in combination with the service product

Refers to

Contains

Copy of thesettlement rules

Settlementrules

Settlementrules

Work orderWork order

Contains

Copy of the Settlement Rules

In PM, the settlement rules are usually set in line with the reference object and Customizing. Improvement in IS-U Work Management

Presetting the settlement rules of the service product The service product refers to a work order that contains the settlement rules for this service product

The presetting based on the service products enables the settlement rules to depend on The service The regional structure


4.25

SAP AG 1999

The service product may refer to a technical object.

The following reference types are possible:

No reference (e.g. energy consulting)

Object can be specified

Object must be specified (e.g. repairs, service connection amplification)

Object is automatically specified (e.g. create service connection)

The following reference object types are possible:

Functional location

Equipment master record

Material in combination with a serial number

The reference object provides a basis for the service order. It can fill the characteristics of the service product with values from the internal configuration or classification.

Technical Reference Object for a Service Product


4.26

SAP AG 1999

Newtechnical

object

Configuration

Char. 01

Char. 02

Char. 03

Char. 01

Char. 02

Creating a new technical object (such as a new service connection)

Values are copied for characteristicswith the same name

Technicalreference

object

Configuration

Serviceproduct

Configuration

Char. 01

Char. 02

Char. 03

Char. 01

Char. 02

Using a service product with reference to an existing technical object (such as service connection amplification)

Serviceproduct

Configuration

Values are copied for characteristicswith the same name

A)

B)

Characteristic Inheritance

When a service connection is installed, a new technical object (the connection as equipment) is generated. This can be performed together with creating the service order. If this piece of equipment is configurable, the technical data from the configuration of the service product can be transferred automatically to the equipment configuration.

When an existing service connection is changed (with a connection amplification, for example), the appropriate equipment can be copied from the work order as a reference object.

In Customizing, you can define whether a reference object must or can be specified for automatic creation of a work order by an SD document. If a reference object has to be specified, the clerk must specify the relevant piece of equipment (the existing connection) when creating the SD document (quotation or order). The technical data from the equipment configuration is transferred to the configuration of the service product as a set of default values. Once the technical data in the configuration of the service product is adjusted, a service order is generated automatically, and the piece of equipment is transferred to the service order as a reference object. Once the work has been performed, the technical data in the equipment configuration can be updated.


4.27

SAP AG 1999

Task list

Task list

QuotationQuotation Sales orderSales order Billing document

Billing document

Serviceorder

Serviceorder

Example: Repair work to a service connectionExample: Repair work to a service connection

ServiceproductServiceServiceproductproduct

Technical object

Technical Technical objectobject

Configu-ration

ConfiguConfigu--rationration

Configu-ration


ServiceproductServiceServiceproductproduct

Technical object

Technical Technical objectobject

Configu-ration


Configu-ration


Copying the Configuration


4.28

SAP AG 1999

Multi-Level Structure of Service Objects


4.29

SAP AG 1999

Service objectMainline extension

Task List

Service objectService object

Operation 10: ExcavateOperation 10: Excavate

Operation 20: Set up mastOperation 20: Set up mast

Operation 30: CableOperation 30: Cable

Operation 40 : Set transformerOperation 40 : Set transformer Service objectService object

Service objectInstall a

transformer

Task List

Operation 10: Prepare base Operation 10: Prepare base

Operation 20: Prepare mastOperation 20: Prepare mast

Operation 30: InstallOperation 30: Install

Operation 40: ConnectOperation 40: Connect

Multi-Level Service Objects


4.30

SAP AG 1999

Service object 1000Service object 1000 Config. for 1000Config. for 1000



Service object 1200Service object 1200 No config.No config.


Service object 1110Service object 1110


Config. for 1110Config. for 1110

No config.No config.



Config. for 1210Config. for 1210

No config.No config.


Configuration in a Multi-Level Structure


4.31

SAP AG 1999

SD documentSD document

Item 10Item 10 Service productService product


Work orderWork orderItem 20Item 20

Item 30Item 30




Work orderWork orderService productService product


Service products with

multi-level structures

Work order hierarchy according to the multi-level structure of the

service product

Multi-Level Order Structure



4.32

SAP AG 1999

Further Functions of Variant Configuration


4.33

SAP AG 1999

Variant Tables and Object Dependencies

Variant tables describe combinations of characteristic values

To represent allowed combinations

To calculate or derive characteristic values

A table can represent dependencies between many characteristics

One table instead of several dependencies

Clearer overview

Simpler representation of the object dependencies

In selection conditions, preconditions, constraints, and in the condition part of actions and procedures, your role is to check the consistency of the values. Preconditions can also be used as input help.

With actions, procedures, and constraints, tables can be used to derive values.


4.34

SAP AG 1999

Model Box Length Soil Electricity Work by sold-to party

Standard Type A < 10 m normal 60A

Service+ Type B < 10 m normal 100A

Handyman Type A > 10 m heavy 40A X

Further values can be derived in an action from the key field "Model"

The table access must be unique

"Service Connection" Table

Example: Table with Service Connection

The syntax for using the table in an action: TABLE SERVICE CONNECTION (MODEL = MODEL, BOX = $SELF.BOX, LENGTH =

$SELF.LENGTH etc.) You can link this action to the configuration profile.


4.35

SAP AG 1999

Functions

You can use ABAP programs and external routines for the configuration.

Procedure:

Write an ABAP program.

Create a function in variant configuration that calls up the ABAP program.

In each object dependencies, you can refer to the function.

Key word: function

Same reference (syntax) as for tables

You can use data from external systems for the characteristic definition.

An example of using external data for defining characteristics is as follows: In an external system, data regarding location, type and dimensions of lawns are maintained. In SAP, there are characteristics defined that correspond to the types of operations and resources

required based on the data identified in the external system. Depending on the location, type and dimensions of the lawn, a different operation of the service order will be saved.


4.36

SAP AG 1999

ConfigurableTask List

ConfigurableTask List

Excavation loose soil

Excavation normal soil

Excavation hard soil

Work center 01 Work center 02

Lay cable

Restore surface

Install connection box A

Install connection box B

Operation summary work center 01

Operation summary work center 02

Function : sum_time_01

Function : sum_time_02

Function : store_time_01

Function : store_time_02

Example: Summary of Operations

Objective:

Summary of operations of a work center in a work order

Estimation, scheduling, and confirmation are only performed for summarized operations


4.37

SAP AG 1999 SAP AG

Service products and service objects standardize the processes involved in creating maintenance and service orders.

Service products describe a service offered to the customer.

Service products contain the following information:

SD view (description of the service, price information, sales BOM)

Internal view (task list, internal and external resource requirements)

Characteristics for precise description

You can also create a multi-level hierarchy with service products

Summary (1)


4.38

SAP AG 1999 SAP AG

The characteristics and service products are valuated in the configuration.

Characteristics are grouped into classes and in the configuration profile.

Various objects can be linked in the configuration using object dependencies.

Object dependencies also influence configurable task lists and pricing.

You can also use tables, ABAP programs, and external routines for the configuration.

Summary (2)


4.39Service Products: Exercises

Unit: Service Products

Topic: The Service Product Concept


Describe what the configuration of the service product controls

Understand the terms class, characteristics and configuration profile

Provide examples of characteristics and characteristic values for the service product

Create a service product and links to the classes and characteristics

The scenario involves viewing classes already set up in the training system. Once you understand classes, you create a new configurable material for the installation of a service connection. After this is set up, you link the service product to the characteristics of the classes already set up in the system.

1-1 True or False?

A service product consists of a service material, configuration and task list.

1-2 What does the configuration of the service product control?

________________________________________________________________

________________________________________________________________

________________________________________________________________

1-3 True or False?

1-3-1 Service product configuration is accomplished using classes, characteristics and the configuration profile.

1-3-2 A class is a group of objects sharing the same or similar properties.

1-3-3 Characteristics contain classes that describe properties. Characteristic values can be defined for each characteristic.

1-3-4 The configuration profile determines the operations and components, as well as the characteristics, that can be used to describe a particular object to be classified.

1-4 Display the classes TECH and SERVICE.


Enter the class TECH, the class type 300 (variants), and choose Enter.

1-4-1 Which characteristics does the class TECH contain?

1-4-2 Which value set exists for the characteristic CONNECTION_TYPE?

1-4-3 Which characteristics are contained in the class SERVICE?

1-4-4 Which value set exists for the characteristic SOIL_CONDITION?

1-5 Create a new configurable material for the installation of a service connection. Use the material TE_CONN_SERVICE as a reference.

1-5-1 Create a new configurable material PE0402A### for the utilities industry with the following default values for the organizational levels of the material to be created and the reference material:

Field Entry

Plant U003

Sales organization U300

Distribution channel U3

Use the table below to enter data in the views of the material.

View Field Entry

Basic data 1 Material

Base unit of measureDivisionWeight unit

Service Product Group ##

ST01KG

Basic data 2 Indicator Material is configurable

X

Sales:sales org. 1

Delivering plantTax classification for VAT

U0031

Sales:sales org. 2

Matl statistics grpAccount assignment groupItem category group

102LEIC

Sales:general/plant

Availability checkTransp. grpLoadingGrp

KP00010001

MRP 1 MRP type ND


MRP 3 Period indicatorStrategy group

M84

Costing 2 Valuation classPrice controlPrice unitStandard price

7900S12500

1-5-2 Specify a price (UNI 3000) for your service product.

Enter the sales organization U300 and the distribution channel U3.

The price should be valid indefinitely from today’s date.

In the table of conditions, enter PE0402A### in the Material field, 3000 in the Amount field and UNI in the Unit field.

1-5-3 Define the material as a service product. Use the maintenance planning plant U003 and the work center 16/3. Do not assign a general maintenance task list or a reference object at this stage.

Choose New entries, and enter your service product as follows:

Plnt (planning plant) U003ServiceProduct PE0402A###Work ctr (work center) 16/3Plnt U003You can leave the other fields empty.

1-6 Link your service product (PE0402A###) with the characteristics of the classes TECH and SERVICE.

1-6-1 Create the new configuration profile PE0402A### for your service product. Use the class type 300.

1-6-2 Allocate the classes TECH and SERVICE.


Exercises


Topic: Configurable Task List


Understand the purpose of the configurable task list

Describe the link between the configurable service product and task list

Create a configurable task list and create an object dependency to operations in the list using a selection condition and an action.

Create a configuration profile for the task list

Create a maintenance order using the task list and influence the operations in the task list using the characteristic values

The utilities company wants to use characteristic values to influence the operation list that describes the work to be performed for a standard service connection. This includes selecting the operations to be included in the list as well as determining parameters, such as the work required.

2-1 True or False?

2-1-1 A configurable general maintenance task list (PM task list) enables you to create frequently recurring work orders (such as installation of a service connection) easily and flexibly. A task list contains a list of operations, a list of the required materials and production resource/tools, and planned times for the operations.

2-1-2 There is no link between the configurable service product and the configurable task list.

2-2 Create the task list TE_### and a configuration profile for the task list with the classes TECH and SERVICE.

2-2-1 Create the task list TE_###. Use the existing task list CO_TEMP as a reference. Set the status for the task list in the task list header to 4 (Released (general)) and enter the description Standard Service Connection Group ###.

2-2-2 What are the names of the operations contained in the task list?

2-2-3 Create a configuration profile with the classes TECH and SERVICE for task list TE_###. Assign the name Standard Service Connection ### to the profile.


2-3 Create an object dependency for the operations in the task list TE_### using the characteristics in TECH and SERVICE.

2-3-1 Create a selection condition for operation 0020 Extra work: protect trench. The operation is only to be executed if the following condition applies: Soil Condition = 1.

2-3-2 Display the reference characteristic PLPO_ARBEI. Which database field is used as a template for this field?

2-3-3 The PLPO_ARBEI characteristic can be used to influence the value of the database field for the work of the operation. Create an object dependency to set the value of the work of operation 0040 to 0.2 x connection length.

Create the object dependency with the following syntax: $self.plpo_arbei = length * 0.2

2-4 Create a maintenance order. The operations for the order are to be copied from the task list TE_###. Use the characteristic values to influence the operations in the task list.

2-4-1 Create a maintenance order of type PM01. Enter the following values in the order header:

Field Name or Data Category Values

Plannergroup

100/ U003

Mn.wk.ctr 13/3 Electricity Workshop

Basic start Today’s date

Short text Maintenance Order with Task List TE_###

2-4-2 Copy the operation list from the general maintenance task list TE_###. Use the following values for the characteristics:


Soil Condition 2 (Normal soil)

Extra Length No entry

Work by Sold-to Party No entry

Connection Type Connection type A

Connection length 10 m


Can you see the operation 0020 Extra work: protect trench here? Explain why.

________________________________________________________

________________________________________________________

________________________________________________________

What is the value for the work of operation 0040? Explain how this value is determined.

________________________________________________________

________________________________________________________

________________________________________________________

2-4-3 Copy the operation list from task list TE_### and change the characteristic values as follows:


Soil Condition 1 (Loose soil)



Connection Type Connection Type B



________________________________________________________

________________________________________________________

________________________________________________________


________________________________________________________

________________________________________________________

________________________________________________________

Save your entries and make a note of the order number ._______________________


Exercises


Topic: Copying the Configuration from the Order to the Equipment

3-1 (Optional) Create a sales order, a service order, and a service connection.

3-1-1 Create a sales order with the material CREATE_CONNECTION for customer TE0301A0##. Use the data from the following table to do so. Configure the service connection.

Order Type OR



Division 01

3-1-2 Display the sales order and the related service order. Has a piece of equipment already been entered in the service order?

3-1-3 Release and close the service order.

3-1-4 Display the equipment that was created with the service order. Which characteristics have been copied to the configuration? Why were these characteristics copied?


4.40Service Products: Solutions


Topic: The Service Product Concept

1-1 True or False?A service product consists of a service material, configuration and task list.

True. Service products describe a service offered to the customer, for example, install service connection. In addition to the service product, you define a configurable service material, which describes the service and also contains price information. Since the service must be performed internally or by third parties, a configurable task list is allocated to the service material.

1-2 What does the configuration of the service product control?

Costing and pricing in SD

The derivation of operations and components (that is, materials and production resources) for automatic creation of the PM order

Equipment configuration (technical data for the service connection is stored in the piece of equipment)

1-3 True or False?

1-3-1 Service product configuration is accomplished using classes, characteristics and the configuration profile.

True

1-3-2 A class is a group of objects sharing the same or similar properties.

True

1-3-3 Characteristics contain classes that describe properties. Characteristic values can be defined for each characteristic.

False. Each class contains characteristics that describe these properties. Characteristic values can be defined for each characteristic.


1-3-4 The configuration profile determines the operations and components, as well as the characteristics, that can be used to describe a particular object to be classified.

False. The configuration profile determines the classes, as well as the characteristics, that can be used to describe a particular object to be classified.

1-4 Display the classes TECH and SERVICE.

Choose Work Management Master Data Classification System Classes

Enter the class TECH, the class type 300 (variants), and choose Enter.

1-4-1 Which characteristics does the class TECH contain?

Choose Characteristics. An overview appears of the allocated characteristics. The characteristics in this case are CONNECTION_TYPE and CONNECTION_LENGTH.

1-4-2 Which value set exists for the characteristic CONNECTION_TYPE?

You determine the value set for the characteristic CONNECTION_TYPE by placing the cursor on the line for the characteristic and choosing Display values. The allowed characteristic values for the characteristic CONNECTION_TYPE are A and B.

1-4-3 Which characteristics are contained in the class SERVICE?

Choose Other object and enter SERVICE in the Class field

The class SERVICE contains the characteristics SOIL_CONDITION, EXTRA_LENGTH and WORK_BY_SOLD_TO_PARTY.

1-4-4 Which value set exists for the characteristic SOIL_CONDITION?

The procedure is described above. The allowed characteristic values for the characteristic SOIL_CONDITION are 1 (loose soil), 2 (normal soil) and 3 (heavy soil).

1-5 Create a new configurable material for the installation of a service connection. Use the material TE_CONN_SERVICE as a reference.

1-5-1 Create a new configurable material PE0402A### for the utilities industry.

Choose Work Management Master Data Service Product Create Configurable Material

In the Material field, enter PE0402A### and enter Utilities in the Industry sector field. Enter the Material TE_CONN_SERVICE as the reference material.

Choose Select view(s). A dialog box appears. Choose the views specified in the table below.


Enter the following data in the dialog box that appears. Enter the same values in the Copy from column. (You can leave the organizational level Storage location blank.).

Field Entry

Plant U003



Choose Enter.

Use the table below to enter data in the views. Most of the data has already been copied from the reference.

You can confirm the message “You have not yet created an EAN” with Enter.

Once the specifications are entered, save the material.

View Field Entry

Basic data 1 Material

Base unit of measureDivisionWeight unit

Service Product Group ##

ST01KG

Basic data 2 Indicator Material is configurable

X

Sales:sales org. 1

Delivering plantTax classification for VAT

U0031

Sales:sales org. 2

Matl statistics grpAccount assignment groupItem category group

102LEIC

Sales:general/plant

Availability checkTransp. grpLoadingGrp

KP00010001

MRP 1 MRP type ND

MRP 3 Period indicatorStrategy group

M84

Costing 2 Valuation classPrice controlPrice unitStandard price

7900S12500



1-5-2 Specify a price (UNI 3000) for your service product (valid from today’s date).

Choose Logistics Sales and Distribution Master Data Conditions Create. Then choose Prices Material Price.

Choose Create.

Enter the sales organization U300 and the distribution channel U3.

Enter PR00 in the Condition type field, PE0402A### in the Material field, 3000 in the Rate field, UNI in the Unit field, and today's date in the Valid on field.

Choose Enter to confirm and then save your work.

1-5-3 Define the material as a service product. Use the maintenance planning plant U003 and the work center 16/3. Do not assign a general maintenance task list or a reference object at this stage.

Choose Work Management Master Data Service Product Maintain Service Product

Choose New entries, and enter your service product as follows:

Plnt (planning plant)U003ServiceProduct PE0402A###Work ctr (work center) 16/3Plnt U003You can leave the other fields empty.

Save the entry.

1-6 Link your service product (PE0402A###) with the characteristics of the classes TECH and SERVICE.

Choose Work Management Master Data Configuration Profile Create.

1-6-1 Create the new configuration profile PE0402A### for your service product. Use the class type 300.

In the dialog box, select Material, if necessary. Enter the material number of the service product (PE0402A###) in the field Material. Enter today's data in the Valid from field. Choose Enter.

Choose Profile overview. In the Profile name field in the table, enter PE0402A### and for the Class type field select 300 (variants).

Choose Enter.

1-6-2 Allocate the classes TECH and SERVICE.

Choose Class assignments and assign the two classes to the configuration profile.

Save the entry.


Solutions


Topic: Configurable Task List

2-1 True or False?

2-1-1 A configurable general maintenance task list (PM task list) enables you to create frequently recurring work orders (such as installation of a service connection) easily and flexibly. A task list contains a list of operations, a list of the required materials and production resource/tools, and planned times for the operations.

True

2-1-2 There is no link between the configurable service product and the configurable task list.

False. A link is created between the configurable service product and the configurable task list when the service products are defined.

2-2 Create the task list TE_### and a configuration profile for the task list with the classes TECH and SERVICE.

2-2-1 Create the task list TE_###. Use the existing task list CO_TEMP as a reference. Set the status for the task list in the task list header to 4 (Released (general)) and enter the description Standard Service Connection Group ###.

Choose Work Management Master Data General Task List Create.

In the Group field, enter TE_###. Choose Copy reference. Choose General maintenance task list in the dialog box that appears and then Continue. In the Group field, enter the reference HA_STAND and choose Continue to create the task list.

In the status field of the task list header, enter 4 (Released (general)). Enter the description Standard Service Connection Group ###. Choose Copy to copy the operations from the reference and save your data.

2-2-2 What are the names of the operations contained in the task list?

Perform excavation

Extra work: protect trench

Lay cable

Refill trench

Save the entries.


2-2-3 Create a configuration profile with the classes TECH and SERVICE for task list TE_###. Assign the name Standard Service Connection ### to the profile.

Choose Work Management Master Data Configuration Profile Create.

If a material-based configuration profile from one of the previous exercises is specified in the screen, choose Change configurable object General maintenance task list. Confirm your entries.

Choose General maintenance object as the configurable object. Enter the group number TE_### and 01 and choose Enter.

Enter the standard service connection ## in the Profile name field and 300 in the Class type field.

Choose Class assignments to assign the classes TECH and SERVICE. Enter TECH and SERVICE in the class list and display the characteristics by clicking Enter.

Save the configuration profile.

2-3 Create an object dependency for the operations in the task list TE_### using the characteristics in TECH and SERVICE.

2-3-1 Create a selection condition for operation 0020 Extra work: protect trench. The operation is only to be executed if the following condition applies: Soil Condition = 1.

Choose Work Management Master Data General Task List Change.

Enter TE_### in the Group field and choose Enter to call up the task list in change mode.

Select the operation 0020 Extra work: protect trench and choose Extras Object dependencies Editor.

Choose Selection condition and Enter. In line 0010 of the Edit Dependency screen, enter the text Soil Condition = 1 and save your data.

2-3-2 Display the reference characteristic PLPO_ARBEI. Which database field is used as a template for this field?

Choose Work Management Master Data Classification System Characteristics

Enter PLPO_ARBEI in the Characteristic field and choose Enter.

Choose Additional data. This data shows that the characteristic is based on the ARBEI field in the PLPO table.

2-3-3 The PLPO_ARBEI characteristic can be used to influence the value of the database field for the work of the operation. Create an object dependency to set the value of the work of operation 0040 to 0.2 x connection length.


Create the object dependency with the following syntax: $self.plpo_arbei = length * 0.2

Choose Work Management Master Data General Task List Change.

Enter TE_### in the Group field and choose Enter to call up the task list in change mode.

Select the operation 0040 Refill trench and choose Extras Object dependencies Editor.

Choose Action and Enter. In line 0010 of the Edit Dependency screen, enter the text $self.plpo_arbei = connection_length * 0.2 and save your data.

2-4 Create a maintenance order. The operations for the order are to be copied from the task list TE_###. Use the characteristic values to influence the operations in the task list.

2-4-1 Create a maintenance order of type PM01. Enter the following values in the order header:


Plannergroup

100/ U003

Mn.wk.ctr 13/3 Electricity Workshop

Basic start Today’s date

Short text Maintenance Order with Task List TE_###

Choose Work Management Processing Maintenance Processing Order Create (General).

Enter PM01 in the Order type field and U003 in the Plng plant field. Choose Enter to create the order.

Enter the data listed above in the order header.

2-4-2 Copy the operation list from the general maintenance task list TE_###. Use the following values for the characteristics:


Soil Condition 2 (Normal soil)






To copy the operation list from the task list, choose Extras Task list selection Direct entry.

In the Task List Direct Input dialog box, enter TE_### in the Task List Group field.

If a dialog box appears with the question "Should operations be deleted?", choose Yes to overwrite the values assigned before the characteristics and the operations copied to the operation list.

Enter the characteristic values as specified above.

Choose Back and then Operations to display the operation list.


Operation 0020 Extra work: protect trench is not contained here since the selection condition for operation 0020 stipulates that the operation is only included if the soil condition = 1.


The value for the work of operation 0040 is 2.0h. It is determined using the action dependency plpo_arbei = connection_length * 0.2.

2-4-3 Copy the operation list from task list TE_### and change the characteristic values as follows:





Connection Type Connection Type B

Connection Length 20 m

To copy the operation list from the task list, choose Extras Task list selection Direct entry.

In the Task List Direct Input dialog box, enter TE_### in the Task List Group field.

Enter the characteristic values as specified above.


Choose Next screen to validate the values and then Operations to display the operation list.


Operation 0020 Extra work: protect trench should now be contained here since the selection condition for operation 0020 Soil condition = 1 is now met.


The work for operation 0040 is 4.0 h. The value is determined using the action dependency plpo_arbei = connection_length * 0.2.

Save your entries and make a note of the order number.

_____________________.


Solutions


Topic: Copying the Configuration from the Order to the Equipment

3-1 (Optional) Create a sales order, a service order, and a service connection.

3-1-1 Create a sales order with the material CREATE_CONNECTION for customer TE0301A0##. Use the data from the following table to do so. Configure the service connection.

Order Type OR



Division 01

Choose Work Management Processing Service Processing Order Sales Order Create.

Enter the data from the table.

Enter the sold-to party, the purchase order number, the material, and the order quantity.

Confirm the message that appears by choosing Enter.

Configure the service connection with values of your choice and choose Next screen.

Save the entries.

3-1-2 Display the sales order and the related service order. Has a piece of equipment already been entered in the service order?

Choose Work Management Processing Service Processing Order Sales Order Display.

Select the item and choose Schedule lines for item.

Choose Service order.

The equipment has already been entered in the service order as a reference object.

3-1-3 Release and close the service order.


Choose Work Management Processing Service Processing Order Service Order Change.

Choose Release and Complete (technically).

Confirm the messages output by the system.

3-1-4 Display the equipment that was created with the service order. Which characteristics have been copied to the configuration? Why were these characteristics copied?

Choose Work Management Processing Service Processing Order Service Order Display.

Double-click the equipment that is the reference object in the service order.

Choose the Configuration data tab page and Display.

The characteristics connection type and connection length have been copied.

These two characteristics have been copied because the service product CREATE_CONNECTION is linked to the reference equipment CONN-CONFIG. You can display this information by choosing Work Management Master Data Service Product Create Service Product.

The reference equipment CONN-CONFIG contains material CONN_TECH in the configuration, which contains the two copied characteristics. You can display this information by choosing Logistics Plant Maintenance Management of Technical Objects Equipment Display. Material CONN_TECH is on the Configuration data tab page.


5

SAP AG 1999

Contents:

The workflow "Install Service Connection"

Link between SD and CS


(C) SAP AG IUT221 1

5.2

SAP AG 1999


Execute the workflow "Install Service Connection"

Describe the link between SD and PM

Installation Services: Unit Objectives

(C) SAP AG IUT221 2

5.3

SAP AG 1999

Installation Services: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

5.4

SAP AG 1999 SAP AG

Installing a service connection is a process that lasts a few days and involves several employees from IDES Energy Inc. This process will, therefore, be controlled by a workflow that monitors the entire process and sends the required information automatically to all the employees involved.

The process starts with a quotation for the customer - a configurable service product is used here - and ends with invoice creation.

Installation Services: Business Scenario

(C) SAP AG IUT221 4

5.5

SAP AG 1999

The Workflow "Install Service Connection"

(C) SAP AG IUT221 5

5.6

SAP AG 1999

SD

CS

Customer inquiry

Service order

Customer

Workflow

1

2

3

6

Quotation Processing

IS-UFront office

Quotation

Event: a customer requests a quotation for the installation of a service connection. Steps:

The clerk identifies the customer using the front office (1) or (in the case of customers not yet defined in the system) creates a master record for the customer.

The clerk creates an SD customer quotation (2), which may relate to an SD inquiry. The quoted service (for example, the service product Install_Service_Connection) is entered as an

item in the quotation. The clerk has to specify the characteristics of the service here. A quotation notification is created and sent to the customer (3). A service order can be created automatically in the background, parallel to the quotation (in

CS) (6). The service connection processing costs can be calculated on the basis of certain characteristics of the

service (such as technical conditions, or service-related criteria), or the flat rate is calculated in the SD quotation.

(C) SAP AG IUT221 6

5.7

SAP AG 1999

SD

CS

Customer inquiry

Service order

Customer

Salesorder

Workflow

4

5

6

Order Processing

IS-UFront office

Quotation

Event: the customer accepts the quotation (4). Steps:

If it is necessary, the clerk requests a down payment from the customer. An SD order is created (5); the order item(s) can be transferred automatically from the SD

quotation. A service order is created automatically in the background (in CS) (6), if it was not created

when the quotation was created. The service order is put in process, and the documents required by the technician to carry out the

connection (known in PM as "shop papers") are printed. The service order contains a description of the operations to be performed and also of materials required.

When operations are assigned externally, the external service can be purchased using the purchasing component from the Materials Management (MM) component. The required materials can be provided internally using a reservation or externally using a purchase order. Both functions are processed in MM.

In the service order, all planned costs and all costs actually incurred (after order closing) are managed.

(C) SAP AG IUT221 7

5.8

S A P A G 1 9 9 9

S D

C S

C u s t o m e r i n q u i r y

Q u o t a t i o n S a l e s o r d e r

F I - C A

D o c u m e n t

W o r k o r d e r

A l t e r n a t i v e

I S - U

W o r k f l o w

I n v o i c i n g

B i l l i n g r e q u e s t

I n v o i c e

8

9

7

1 1

1 0

O r d e r C l o s i n g a n d B i l l i n g

C u s t o m e r

B i l l i n g

F r o n t o f f i c e I S - U

Event: the connection is installed on site (7). Steps:

The service order is returned and completed. In the case of resource-related settlement of the service, an SD billing request is created from the

service order (8). The costs of the service order actually incurred are taken as a basis for this. SD billing is initiated (9) and posted. If the service is to be billed according to actual costs, then the

resource-related billing document is used on the basis of the billing request. In the case of flat-rate settlement of the service, the SD order forms the basis for billing.

A debit position can be provided for the billed amount in FI-CA (10). Down payments can also be entered in FI-CA.

As an alternative to billing in SD, the service can be invoiced in IS-U. In this case, you can either print out the invoice immediately or consider the invoiced amount from the service connection processing in the first consumption billing run.

(C) SAP AG IUT221 8

5.9

S A P A G 1 9 9 9

A c c e p t Q u o t a t i o n

C r e a t e Q u o t a t i o n

C r e a t e S e r v i c e O r d e r

I n s t a l l S e r v i c e C o n n e c t i o n

C r e a t e S a l e s O r d e r

I n s t a l l s e r v i c e +c o n n e c t i o n o b j e c t

P a y I n v o i c e

C r e a t e I n v o i c e

W o r k f l o w S t r u c t u r e

R e q u e s t s e r v i c e c o n n e c t i o n

C o n f i r m S e r v i c e O r d e r

R e q u e s t D o w n P a y m e n t

P a y D o w n P a y m e n t

(C) SAP AG IUT221 9

5.10

SAP AG 1999

Workflows for Service Connection Processing

Service Connection with

Quotation

Process SM Order

Monitor Completion of SM Order

Confirm Service Order

Customer Decision Regarding Quotation

ServiceConnection

Order Processing

Create and Install Service Connection

Work Management provides a series of workflows that you can use for order processing of service connections; The workflow ISUNewConQuo (service connection with quotation) enables full, end-to-end service

connection processing from SD quotation processing using SD order creation to service order processing and finally SD billing. This workflow makes use of further workflows to perform the individual functions just mentioned.

The workflow ISUQuoDecisi (customer decision regarding quotation) enables the customer's reaction to an SD quotation for a service to be entered in the system.

The workflow ISUNewConOrd (service connection order processing) enables service connection processing from SD order creation using service order processing to SD billing. The SD order can be created with reference to an existing SD quotation. This workflow makes use of the workflow ISUProcSMOrd to perform the individual functions just mentioned.

The workflow ISUProcSMOrd (process SM order) enables processing of the service orders that are determined from the SD orders. If order monitoring is necessary, the following workflow can be used.

The workflow ISUSupCSMOrd (monitor completion of SM order) enables the service order to be closed if SD billing is brought forward.

The workflow ISUCompSMOrd (start final confirmation of SM order) can be used to confirm a service order.

The workflow ISUConCreIns (create and install service connection) is used to create the new service connection in the system and to install it in an existing or newly created connection object.



5.11

SAP AG 1999

End workflow

Front office Manual

Specify service product

Create customer quotation

Wait for customer response

Down payment processing

WF: Service connection

order processing

Resubmission

End

Quotation rejected

Quotation accepted No response

WF: Customer decisionregarding quotation

Front office Manual

Workflow: Service Connection with Customer Quotation

The workflow Service connection with customer quotation can be started either from the front office or manually from the workflow environment.

Once the service product has been defined and the customer quotation created, the workflow waits for the customer to respond to the quotation. The workflow is informed of this reaction by the Customer decision regarding quotation workflow: If the customer rejects the quotation, the entire workflow is ended. If there is no reaction, the work item can be resubmitted. (You can use scheduling parameters in the

workflow to determine which interval is to have passed before the work item is resubmitted.) If the customer accepts the quotation, down payments can be processed before the start of the Service

connection order processing workflow. In down payment processing, the clerk can decide whether the service can only be provided if a down

payment is made first. If the clerk decides that this is the case, a down payment request is created and posted in FI-CA. The order is not processed any further until the down payment is made.

If the down payment request is cancelled, the clerk can then decide whether the order should be processed anyway or whether the quotation should be withdrawn.



5.12

SAP AG 1999

Workflow: Service Connection Order Processing

Specify service product

End

WF: Process SM order

WF: Service connection with customer quotation

Determine SM ordersfor SD order

Create SD order withoutquotation reference

Create SD order withquotation reference

Front office Manual

Invoice creation

The workflow Service connection order processing can be started either automatically by the workflow Service connection with quotation or manually from the front office or the workflow environment. If it is started from the front office or the workflow environment, the order cannot be created with reference to an existing quotation. As, in this case, service processing is to be carried out without reference to a quotation, you must define a service product. If this workflow is started automatically by the workflow Service connection with quotation, the quotation that has already been created in the workflow is used as the basis for further processing.

After the sales order has been created, the service orders are defined. One SM service order is determined per SD item.

SM service order processing takes place in the workflow Process SM order. Once service order processing is completed, the service is invoiced.


5.13

SAP AG 1999

Workflow: Process SM Order

Manual

End

Front office Manual

WF: Start finalconfirmation of

SM order

Put SM order "in processing"

Wait for completion confirmation

Close SM order technically

Yes

No

Yes

WF:Monitor Completion

of SM Order

WF:Service connectionOrder processing

WF:Create a service

connection and install it in a connection object.

Invoice creation withoutorder closing?

The workflow Process SM order is started automatically from the workflow Service connection order processing.

Once the SM order is put in process, parallel processing is initiated. The workflow waits for completion confirmation of the SM order and, at the same time, allows the clerk to initiate invoice creation without order closing as soon as the period specified in the workflow has passed.

Completion confirmation can be initiated by the workflow Start final confirmation of SM order, which can be started either from the front office or manually (from the workflow environment). In this workflow the planned data of the order (times, materials) can currently only be copied to actual data, without the clerk being able to adjust the values. For this reason, it is more appropriate for the SM order to be confirmed completely using the original transaction. After completion confirmation, the SM order can be closed technically.

If the clerk opts for early invoice creation without order closing, the workflow Monitor completion of SM order is initiated automatically. This ensures that the closing of the SM order can still be monitored even though billing takes place early. If the clerk does not opt for early invoice creation, workflow control returns again to the beginning of the loop.

The workflow Create and install service connection is used to create the new service connection in the system and to install it in an existing or newly created connection object.



5.14

SAP AG 1999

Link Between SD and CS


5.15

SAP AG 1999

Interaction Between SD and CS

Customer(External) View

Company(Internal) View

CSCSSDSD Work Management

InquiriesInquiries

QuotationsQuotations

Sales ordersService Products

Sales ordersService Products

Technical objects

Service orders

InvoicesInvoices

Service order type

The standard processes from the Plant Maintenance (PM), Customer Service (CS), and Sales and Distribution (SD) application components and their links to each other offer a range of options for modeling typical process chains.

In particular, the links between the sales order (SD order) and the service order (SM order) makes processing of these business transactions considerably easier. You enter the relevant data, such as the business partner, the service object, and the precise specification of the service, once only, and this data is then transferred automatically to the relevant processing steps.


5.16

SAP AG 1999

Basic Data

Sales Org.Data

ForeignTrade

SalesText

Purchasing Accounting

MRP 1

MRP 2

MRP 3

MRP 4

Strategy Group

Mai

ntain

ed in

Values provided by SAP:

Strategy 84

Requirements type SERA

Requirements class 203

Order type SM01

Strategy

Requirements type

Requirements class

Order type

Derivation of the Service Order Type (1)

MaterialMasterRecordViews

If you are creating a service order on the basis of a sales order, the system determines the service order type using the strategy group that you have maintained in the MRP 3 view of the material master. The order type is not allocated to the strategy group directly, but via the strategy, the requirements type, and the requirements class.


5.17

SAP AG 1999

Strategy Group

Requirements type (Transaction OPPS)

Requirements class (Transaction OVZH)

Order type (Transaction OVZG)

Strategy (Transaction OPPT)

Derivation of the Service Order Type (2)

The steps to be performed in the Implementation Guide (IMG) to derive the service order type can be found at various places in the IMG. It is, therefore, simpler to enter the transaction directly.


5.18

SAP AG 1999

Several Order Types

Procedure for creating several order types:

Copy requirements class "203" to "Z03" and assign order type XXXX (e.g. SM02) accordingly (OVZG).

Copy requirements class "SERA" to "ZERA" and assign requirement class "Z03" (OVZH).

Copy strategy "84" to strategy "Z4" and assign requirements class "ZERA" (OPPS).

Copy strategy group "84" to strategy "Z4" and assign strategy "Z4" (OPPT).

Maintain the strategy group in the service material (view MRP 3)in line with the customer requirements (MM02).


5.19

SAP AG 1999

Quotation/Sales Order

Work order

Planned costs UNI 1000.00

Conditions used

EK02: Planned costsEK01: Actual costs

10 Item

Calculation schema

order

Actual costs UNI 920.00

Transfer costs for each total

10 Item20 Item

Create work

Actual costs

Planned costs

Transferring Costs from Work Orders

Costs are not included on the SD order until they are determined using a calculation schema on the planned costs in the PM order.


5.20

SAP AG 1999 SAP AG

Functions from SD, CS and IS-U/CCS are used for the installation of service connections.

The entire process is implemented as workflow in Work Management. It contains quotation processing, order processing, order closing, and billing.

The sales order and service order can be linked by means of service products. This enables planned and actual costs to be transferred from the service order to the sales order, for example.

Installation Services: Summary


5.21Installation Services: Exercises

Unit: Installation Services

Topic: The Service Connection Workflow


Use the service connection workflow

In the following exercise you are going to execute the entire business process of installing a service connection using the workflow provided by SAP.First, a quotation is created, which the customer accepts after a certain period of time. The next work item is to determine whether a down payment is required from the customer. The SD and CS orders will then be processed and billing will be performed in SD.

1-1 Start the business process "Service connection with quotation".

1-1-1 In CIC, start the workflow Service Connection with Quotation for the business partner TE0501A###. Choose sales organization U300, distribution channel U3, division 01, and regional grouping 0001.

1-1-2 Choose the service product CONN_CREATE and configure it with the following values:



Connection length 10

1-1-3 Display the sales order. How much does the service connection cost? Complete the workflow step.

1-1-4 Save the customer contact.

1-1-5 Obtain an overview of the active workflows of your business partner. Display the progress of the workflow you have just started.

1-2 The customer has informed you that he/she is accepting the quotation for the installation of a service connection.

1-2-1 Start the workflow for accepting/rejecting the quotation for the business partner TE0501A###.

1-3 In the next step, you decide that a down payment is unnecessary.


1-3-1 Execute the corresponding work item Is down payment request required for quotation ######## in the integrated inbox.

1-4 The sales order and service order are now created. In the next step, you will confirm the service order, technically complete the order, and enter the new master data in the system.

1-4-1 Confirm the service order

1-4-2 Enter a storage location from which the materials have been taken.

1-4-3 Perform the final confirmation.

1-4-4 Close your service order technically by executing the corresponding work item in the integrated inbox.

1-4-5 Create a new connection object in Oak Tree Road ## in Washington D.C.

1-5 Create the invoice for installing the service connection

1-5-1 Create an invoice for your sales order by executing the corresponding work item in the inbox.

1-5-2 What is the status of the workflow?

1-5-3 Take a look at your customer's account. Has the amount for the service connection already been recorded?

1-5-4 Take a look at the document flows of service order and sales order.

1-6 In the data environment of the new connection object, check that the service connection has been installed.


5.22Installation Services: Solutions

Unit: Installation Services

Topic: The Service Connection Workflow

1-1 Start the business process "Service connection with quotation".

1-1-1 In CIC, start the workflow Service Connection with Quotation for the business partner TE0501A###. Choose sales organization U300, distribution channel U3, division 01, and regional grouping 0001.


Enter the business partner (TE0501A###) in the search criteria: The Tech. table contains the corresponding workflow. Start the workflow and use the organizational data specified above.

Specify the period for which the quotation is to be valid.

Choose Execute.

1-1-2 Choose the service product CONN_CREATE and configure it with the following values:



Connection length 10

In the dialog box, choose the service product CONN_CREATE and choose Enter.

Configure the service product with the specified values.

Once you have entered all the data on the characteristics, choose Next Screen. The screen Should the sales order be revised? appears.

1-1-3 Display the sales order. How much does the service connection cost? Complete the workflow step.

1-1-4 Save the customer contact.

A contact is created automatically. You can return to the front office by saving the customer contact.

1-1-5 Obtain an overview of the active workflows of your business partner. Display the progress of the workflow you have just started.

The active workflows for your business partner are contained in the action box under Info.


By double-clicking the active workflow Service Connection with Customer Quotation, you branch to the step log, where you can view the progress of your workflow.

1-2 The customer has informed you that he/she is accepting the quotation for the installation of a service connection.

1-2-1 Start the workflow for accepting/rejecting the quotation for the business partner TE0501A###.

In the navigation area, call up the documents and choose Refresh.

You can find the quotation you just generated under sales quotations. You can call up the menu with the right mouse button and then accept or reject the quotation.

Review the quotation information and choose Accept.

Save the customer contact.

1-3 In the next step, you decide that a down payment is unnecessary.

1-3-1 Execute the corresponding work item Is down payment request required for quotation ######## in the integrated inbox.

Go to your integrated inbox in the application area and refresh. The new work item Is down payment request required for quotation ######## is in the integrated inbox.

Choose the work item. Choose Execute.

Choose Down payment request is not required.

1-4 The sales order and service order are now created. In the next step, you will confirm the service order, technically complete the order, and enter the new master data in the system.

1-4-1 Confirm the service order

In the navigation area, call up the documents and choose Refresh.

You can find the service product you just generated under service orders. You can call up the menu with the right mouse button and then start the confirmation.

1-4-2 Enter a storage location from which the materials have been taken.

In the dialog box, choose Change.

Choose the Components tab page. Enter 0001 in the Storage location field.

Save the entries.

1-4-3 Perform the final confirmation.

In the dialog box, choose Finally confirm.

1-4-4 Close your service order technically by executing the corresponding work item in the integrated inbox.


From your integrated inbox, select work item IS-U: Complete service order ########### technically.

1-4-5 Create a new connection object in Oak Tree Road ## in Washington D.C.

Select Create connection object.

Enter a description.

Search for Oak Tree Road in Washington D.C. and enter the house number.

Enter the maintenance plant U003.

Save the entries.

1-5 Create the invoice for installing the service connection

1-5-1 Create an invoice for your sales order by executing the corresponding work item in the inbox.

Go to your integrated inbox and choose Refresh. Your inbox contains a new work item: IS-U: Create invoice for sales order ##########. Choose Execute.

1-5-2 What is the status of the workflow?

The (sub-) workflow Order processing of service connection processing has also ended, as has the entire workflow Service connection with customer quotation. If you now display the active workflows for your business partner from Front Office, no more entries exist.

1-5-3 Take a look at your customer's account. Has the amount for the service connection already been recorded?

Start the account overview in the data environment at contract account level.

1-5-4 Take a look at the document flows of service order and sales order.

In the customer overview, click the service product.

Choose Document flow.

Choose the sales order and Document flow.

1-6 In the data environment of the new connection object, check that the service connection has been installed.

In the action box in the Info area, choose the process Connobject Environme.

Under Technical data, enter Oak Tree Road ## and choose Find. The data environment for the connection object is displayed together with the service connection.


6

SAP AG 1999

Contents:

Codes for orders and notifications

Orders and notifications in processes

Inspections

Disaggregation

Governing body electrical inspections


(C) SAP AG IUT221 1

6.2

SAP AG 1999


Create work orders and notifications using order and notification codes in various processes, such as in

Disconnections and reconnections

Aperiodic meter readings

Periodic replacements

Device repairs

Inspections

Describe how services can run in deregulated companies

Processes in the Utilities Industry: Unit Objectives

(C) SAP AG IUT221 2

6.3

SAP AG 1999

Processes in the Utilities Industry: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

6.4

SAP AG 1999

Utilities Industry Processes: Business Scenario

IDES Energy Inc. has to provide various services for their customers. It wants to standardize these services by means of service products and objects. These services include:

Aperiodic meter readings

Disconnections and reconnections

Periodic replacements

Device repairs

Inspections

(C) SAP AG IUT221 4

6.5

SAP AG 1999

Codes for Orders and Notifications

(C) SAP AG IUT221 5

6.6

SAP AG 1999

PM/SM orderPM/SM order

Order code

Order code

IS-U processFront office


ServiceproductServiceproduct

Service order (connected to the sales order)

Service order (connected to the sales order)

Sales orderSales order

Service object

Service object

NotificationNotification

Notification code

Notification code

Notification profile

Notification profile



Creating Orders and Notifications

(C) SAP AG IUT221 6

6.7

SAP AG 1999

• Order type• Maintenance activity type• Main work center• Business area• Task list group

Default ValuesDefault Values

• Disconnection order• Reconnection order• Device installation order• Order for periodic

replacement• Order for aperiodic meter

reading• Repair order• etc.

Order CodeOrder Code Service ObjectService Object

• Disconnection• Reconnection• Installation• Replacement• Aperiodic meter

reading• Device repair• etc.

Technical Reference ObjectTechnical Reference Object

Settlement RuleSettlement Rule

Service objects can be grouped into set levelsExample:

• Consulting• Service

Order Code

(C) SAP AG IUT221 7

6.8

SAP AG 1999

• Maintenance planning plant• Notification type• Priority• Business area• Work center/plant• Maintenance activity type• Activity schema

Default ValuesDefault ValuesNotification CodeNotification Code Notification ProfileNotification Profile

• Disconnection• Reconnection• Periodic replacement

notification• Notification for aperiodic

meter reading• etc.

• Disconnection• Reconnection• Replacement• Aperiodic meter

reading• etc.

The activity schema corresponds to the service order task list

Notification Code

(C) SAP AG IUT221 8

6.9

SAP AG 1999

Selecting a Code

Integration in front office processes or workflows

Using the method Create with order code

Using the method Create with notification code

e.g. with a repair order or malfunction report

Calling a code up in a process, such as

Aperiodic meter reading order

Periodic replacement

Calling up a code in the structure list of the technical objects

Creating an order via service objects for equipment and functional locations

Configuration and multi-level service objects are also possible here

(C) SAP AG IUT221 9

6.10

SAP AG 1999

Plant and Work Center Determination

The main maintenance planning plant for a work order depends on the

Service Object

Regional Structure Area

The main work center of a work order depends on the

Service Object

Regional Structure Group

The main maintenance planning plant for a notification depends on the

Notification Profile

Regional Structure Area


6.11

SAP AG 1999

Regional Structure Area 0005

Maintenance Planning Plant BMaintenance Planning Plant A



Regional Structure Group 0011

WorkWorkcentercenter1010







Regional Structure Group 0011

Example of Plant and Work Center Determination


6.12

SAP AG 1999

Orders and Notifications in Processes


6.13

SAP AG 1999

Aperiodic Meter Reading

Manual creation of a meter reading order, for example, for:

An interim meter reading with or without settlement

A control reading

Automatic creation of a meter reading order on the basis of an operation, for example, for:

Move-Out, Move-In

In Customizing, you can define

Whether a service order or a notification (or neither of the two) is to be created for the meter reading order

The level on which (device, device location, connection object) the service order or notification is generated

If you are creating a meter reading order manually, a service order is generated automatically (if Customizing has been set accordingly). This may, however, be prevented by setting an indicator in order creation.

For aperiodic meter reading, the system contains the order or notification codes SMRO, SMR1, and SMR2 for meter readings at device, device location, and connection object level.

You can define some codes in Customizing and use them via the SAP enhancement EXIT_SAPLEL01_001 when generating service orders.


6.14

S A P A G 1 9 9 9

E n t e r R e c o n n e c t i o n

D a t a

C r e a t e D i s c o n n e c t i o n

O r d e r

T e c h n i c i a nT e c h n i c i a n

P e r f o r m R e c o n n e c t i o n

C r e a t e D i s c o n n e c t i o n

D o c u m e n t

C r e a t e R e c o n n e c t i o n

O r d e r

T e c h n i c i a nT e c h n i c i a n

P e r f o r m D i s c o n n e c t i o n

C l e r kC l e r k

C o n f i r m R e c o n n e c t i o n

O r d e r

E n t e r D i s c o n n e c t i o n

D a t a

C l e r kC l e r k

C o n f i r m D i s c o n n e c t i o n

O r d e r

C l e r ko r S y s t e m


T r i g g e r R e c o n n e c t i o n







D i s c o n n e c t i o n a n d R e c o n n e c t i o n

Disconnection is triggered either manually by a clerk (if the customer has requested the disconnection, for example) or by the system (if, for example, the disconnection dunning level has been reached in the dunning run). The system then generates a disconnection document. Disconnection documents can also be created manually by clerks.

The system generates a disconnection order, complete with all the documents the technician needs to disconnect the installation.

The technician carries out the disconnection using the documents. The disconnection is performed in the system: the disconnection order is confirmed and disconnection

data is entered. The confirmation status indicates whether or not the disconnection was successful (for example, disconnection performed, entry not possible).

Reconnection is triggered either manually by a clerk (if the customer requested the original disconnection, for example) or by the system (if, for example, payment has been received since the disconnection dunning level was reached in the dunning run).

The system generates a reconnection order, complete with all the documents the technician needs to reconnect the installation.

The technician carries out the reconnection. The reconnection is performed in the system: The reconnection order is confirmed and reconnection data

is entered. The confirmation status indicates whether the reconnection was successful (disconnection performed, entry not possible, for example).



6.15

SAP AG 1999

Customizing Disconnections/Reconnections

In the Customizing settings, you define

Whether service orders or notifications are to be created

Which order or notification codes are used for disconnections and reconnections. The codes depend on the processing variant.

Examples of processing variants:

Disconnection order from dunning run

Customer request

Technical reasons

Holiday home left empty for six months


6.16

SAP AG 1999

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

Periodic replacement list4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders Replacement

orders for all devices

Replacement orders for sample devices and spare sample devices

Sample4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

4567,8

Siemens

Owner no.

Repl acement Orders

DeviceCat.

B

Device Cat.

A

Overview of Device Inspection


6.17

SAP AG 1999

Selecting Devices for Work Orders

Selecting devices from sample lots

Selecting devices from the periodic replacement list, for example, according to

Periodic replacement year

Device category

Function class and/or construction class

Regional structure (country, city, street, house number)

Additional orders for all devices that are installed in the samedevice locations as the selected devices (can be differentiated by division)

Checking whether there is a scheduling conflict with other meter readings

The work orders can be created using a background job.


6.18

SAP AG 1999

In the Customizing settings, you define

Whether a service order is to be generated for the device replacement

The level on which (device, device location, connection object) the service order is generated

Whether a service order is also to be generated for uninstalled units to be tested and whether bundling per warehouse takes place

Whether notifications are to be created instead of service orders

At device and device category level, you can define an overriding order or notification code.

Customizing the Device Inspection

For the periodic replacement, the system contains the order or notification codes PREP, PRE1, and PRE2 for replacement at device, device location, and connection object level.

For the samples lots, the system contains the order or notification codes SAMP, SAM1 and SAM2 for replacement at device, device location, and connection object level.

For units not to be tested, the system contains the order or notification codes PHOL and PLAG for individual devices in a warehouse or for the bundling of devices per warehouse

You can override the default code by entering an order or notification code at device or device category level, if the installed device has to be certified.


6.19

SAP AG 1999

Customer complainsabout faulty device

Clerk chooses front office process

Service order is sent to thetechnician responsible

Front office process refers to order code

Device Repairs

Using the Front Office, you can trigger the generation of a repair order by first selecting the affected customer and the starting the Front Office process SREP.


6.20

SAP AG 1999

Example: Initial Data Creation for a Front Office Process

The front office process Initial data creationcreates:

Connection object

Premise

Device location

Installation

Service order for a device installation

The front office process initial data creation represents an example that can be adjusted to the requirements of the utilities company.


6.21

SAP AG 1999

Inspections


6.22

SAP AG 1999

Subdivision of Inspections

Inspections are subdivided into

Periodic and aperiodic inspections

Scheduled and unscheduled inspections

Aperiodic inspections are processed by means of CIC processes

Initial inspections

Advance inspections

Unscheduled inspections

Periodic inspections are managed in the inspection list

Initial inspection: A technical installation is created, checked for the first time, and is assigned the date of the last inspection. An initial inspection is always a scheduled inspection.

Advance inspection: The work scheduler knows that, at a certain point in time, the service technician will be working close to a technical installation that has to be inspected in the near future. To avoid the technician having to return to the same object again, the work scheduler decides to schedule the inspection to be performed at the same time as the other work required and creates an advance inspection order. This form of advance inspection is a scheduled inspection.

Unscheduled inspection: A service technician is performing work for a customer and decides to inspect the technical installation of the customer at the same time even though this inspection is not actually due. This form of inspection is an unscheduled inspection.


6.23

SAP AG 1999

ConnectionObject

ConnectionObject ConnectionConnection

Device LocationDevice

Location

PremisePremise

MeterMeter

TechnicalInstallation Technical

Installation AdditionalEquipmente.g. Riser

AdditionalEquipmente.g. Riser

AdditionalEquipment

e.g. Refrigerator

AdditionalEquipment

e.g. Refrigerator

Selection for inclusion inan inspection listSelection for inclusion inan inspection list

Selecting Technical Objects

Technical installations are mapped in the system as equipment. You can, however, also inspect "just" items of equipment. This equipment must just be installed in a connection object or in a device location. This also enables you to process connections or IS-U devices (counters) with the inspections.

The date of the last inspection is stored for the equipment or for the technical installation.


6.24

SAP AG 1999

Advanceinspection

UnscheduledUnscheduledinspectioninspection

Process

Initialinspection

Create Close


installations

Inspect.order

Inspect.order

TechnicalinstallationTechnicalinstallation

Inspect.order

Inspect.order

TechnicalinstallationTechnicalinstallation

Inspect.order

Inspect.order


installations

Inspect.order

Inspect.order

TechnicalinstallationTechnicalTechnicalinstallationinstallation

Date of last inspectionDate of last inspection

Date of last inspectionDate of last inspection

Date of last inspectionDate of last Date of last inspectioninspection

Can be

Transferred

to Inspection

Lists

for

Periodic

Inspections

CIC Processes for Aperiodic Inspections

The following CIC processes for aperiodic inspections are available: Create initial inspection: A customer reports a new technical installation for a particular division.

The front office employee creates the technical installation and the initial inspection order required. Create advance inspection: A work scheduler schedules work in a building or area that contains a

technical installation that needs to be inspected. To optimize travel costs, the inspections for these technical installations are scheduled at the same time, in other words, the work scheduler creates the corresponding inspection orders.

Complete scheduled inspection: An initial inspection or an advance inspection has been performed by a service technician and can then be completed in the R/3 System. The order is technically completed here.

Complete unscheduled inspection: While working on a customer's premises, a service technician decides to inspect a technical installation although this was not planned beforehand by an inspection order. Once the inspection has been completed, it must be entered in the R/3 System. No inspection order is created.

When an aperiodic inspection is completed, the date of the last inspection is always set. This includes the technical installations/equipment automatically in the processing of the periodic inspections.


6.25

SAP AG 1999

Selection ofequipment

Create/maintaininspection list

Complete the inspection

Performthe inspection

Additionalequipment

Additionalequipment

Technicalinstallation




Additionalequipment

Additionalequipment

Additionalequipment

AdditionalequipmentAdditional

equipment

Additionalequipment







Additionalequipment

Additionalequipment




TechnicalinstallationAdditional

equipment

Additionalequipment



Campaign A

Campaign B

08/15/200008/15/2000

08/12/200008/12/2000

05/25/200005/25/2000

08/17/200008/17/2000

08/10/200008/10/2000

08/11/200008/11/2000

05/15/200005/15/2000

05/20/200005/20/2000

05/10/200005/10/2000

OrdersOrders

Notifications

or

Periodic creation

Periodic creation

Overview of Periodic Inspections

Campaigns always have a fixed validity period that can no longer be changed once they have been created. When a campaign is created, you can either include technical installations or equipment. You can, however, enhance the campaigns at a later stage to include further technical installations/pieces of equipment.

Entries of a campaign can be deleted provided that no orders or notifications have been created. A campaign can be enhanced at any time.

The enhancement EWMHI001 contains the user exit EXIT_RE_INSP_LIST_CREATE_001 and the associated CI include CI_EWMINSP. When the inspection list is created, individual fields can be saved for each entry. These fields are then available for changing/displaying the inspection list and for creating orders/notifications as selection criteria.


6.26

SAP AG 1999

Campaign

1Q 2000 US GAS

1Q 2000 US ELEC.

2Q 2000 US GAS

Equipment Division Last insp. Next insp. Order ...

10003456 Gas 02/09/1990 02/09/2000 - ...

10007558 Electricity 02/12/1990 02/12/2000 900786 ...

10007832 Electricity 02/18/1990 02/18/2000 900787 ...

10008625 Electricity 02/25/1990 02/25/2000 900788 ...

10009667 Electricity 03/29/1990 03/29/2000 900788 ...

10002499 Gas 04/02/1990 04/02/2000 900805 ...

Start

01/01/2000

End

03/31/2000

01/01/2000 03/31/2000

04/01/2000 06/30/2000

Details of Inspection List (Equipment / Technical Installations)

Header of Inspection List (Campaigns)

Periodic Inspections

A piece of equipment (or a technical inspection) can only be contained once in the inspection list, in other words, only in one campaign. This avoids inconsistencies. After all the inspections of a campaign have been performed, the complete campaign should either be archived or deleted.


6.27

SAP AG 1999

Selection Options for Inspections

Selection options for inspections:

Division

Type of premises and meter reading unit (for TI)

Equipment type (for equipment)

Inspection period

Regional selections (regional group, address)

Inspection data

Individual technical installations and pieces of equipment

Free selection of individual fields (only available after the inspection list has been created)


6.28

SAP AG 1999

Bundling Inspections

Bundling possible at

Equipment level

+ Unique assignment of inspection order / notification

+ Partner can be transferred to order / notification

- No optimization with multiple inspections

Connection object level

+ Summary of all inspections for the CO

- Partner cannot be transferred

The most important decision criteria for the bundling is the partner. If the partner is to be transferred to the order or notification, you need to bundle the inspections at equipment level.

When inspections are bundled at connection object level, the technical installations or pieces of equipment affected are referenced as follows: All the pieces of equipment/TIs in the order are stored in the object list. The pieces of equipment/TIs

are also attached to the order using object links. In the notification, all the pieces of equipment/TIs affected are just stored using the object link, since

the notification does not contain an object list.


6.29

SAP AG 1999

Example: Switzerland and Spain

In Switzerland, legal requirements stipulate that the electricalinstallations must be inspected (home installation check). This includes

Initial check (aperiodic initial inspection)

Periodic check (periodic inspection)

The control interval depends on the type of premise (living space, office, commercial room, doctor's practice,... )

In Spain, the gas installations have to be checked every four years. This includes

Checking the risers that lead from the grid to the premise (IRC)

The installation within the premise (IRI)


6.30

SAP AG 1999

Disaggregation


6.31

SAP AG 1999

Regulated Company

Generation

Distribution

Trans-mission

Internal processes

Deregulated Company

Outsourcing

Service quotation

Serv

ice

External processes

Deregulated Market

Services between the "new", independent companies are provided on the basis of the disaggregation of companies

This produces "service chains" between the companies


6.32

SAP AG 1999

Distribution companyDistribution company

Residential customers

Commercial customers

Service:Energy supply

Service connections

Service companyService company

Customer:Distribution company

Service:Installation service

Ext. service providerExt. service provider

Customer:Service company

Service:Groundwork

.....

Installation

Service connection

Outsourcing

Groundwork

Service

entry sheet

Outsourcing

Long-term agreements

Outline agreement

Outline agreement

Service contract

Service contract

Business documents

Sales order

Purchase order

Work order

Sales order

service

Service Chains

One of the distribution company's customers orders a new service connection. A sales order is created. Distribution companies and service companies have settled an outline agreement. This means that the

service company will not create a sales order but will create a work order straight away. The service company now purchases the groundwork from a different service provider. The service

provider creates a sales order for this purpose. An outline agreement can also be settled for these purchase orders.


6.33

SAP AG 1999

Maintenance ofequipment

Operation of power plants

Maintenance ofequipment

Operation of power plants

Typical services for customers and companies involved in ...

Transmission servicesTransmission services

Energy supply

Installation services

Meter reading services

Energy supply

Installation services

Meter reading services

GenerationGeneration TransmissionTransmission DistributionDistribution

Services in the Utilities Industry

Define the service as a configurable service product


6.34

SAP AG 1999

IS-U/CCS

SDCustomer

inquiryCustomer

inquiry QuotationQuotation OrderOrderDebit memoInstallation

services

Debit memoInstallation

services

FI-CAFI-CA

DocumentDocumentCustomerCustomer

INVOICE #:

LOGO

CSService

orderService

order

InvoiceInstallation

service

InvoiceInstallation

service

Front officeFront office

Qty Ordered

TotalSALESPERSONData

Sales Tax

Subt otal

TotalPrice

DescriptionQty Shipped

P.O. #:

PremiseCustomer

UTILITY BILL

W o r k f l o w M a n a g e m e n tW o r k f l o w M a n a g e m e n t

Sys

tem

1 o

r c

om

pa

ny

AS

yste

m 2

or

Sys

tem

2 o

r c

om

pa

ny

Bc

om

pa

ny

B

Disaggregation IDocs

Confir-mation

Invoice

Example: Installation Service

A business process (creating a new service connection, for example) is distributed to two R/3 Systems or to two company codes in an R/3 System.

The customer-related sub-steps have to be performed in an R/3 System that contains the IS-U system and the standard R/3 System. For the sub-steps related to logistics, only the standard R/3 System is required.

The communication between the two systems is processed using the following IDocs: ISU_SDSM_ORDER: Transfers the data of a sales order and creates a service order. ISU_SDSM_COMP: Indicates the technical completion of the service order. The billing block on the

sales order is deleted. You can give every position of the sales order a different schedule line date that can be used for service

order scheduling of the service order In the sales order, you can enter a different partner as the sold-to party whose address can be used in the

service order The following functions are also in the standard system:

Address check before service orders are created Enhancing EWMSM001 for determining CpD-customers Enhancing EWMSM003 to set an application standard for the service order



6.35

SAP AG 1999

Governing Body Electrical Inspections


6.36

SAP AG 1999

Permit required?Permit required?

Yes No

Create order without permit

Create order without permit

Create order with permitCreate order with permit

Order is blocked

Permit ok

Process order

Process order

Governing Body Electrical Inspections (US Only)

For some areas of the US, before mobile homes can be located at a site, the customer must first receive permission from the local governing body.

Permits are handled as approvals in PM.


6.37

SAP AG 1999

Type of service:Gas reconnection

Regional areas:Alexandria AArlington BWashington DC C

Alexandria

Arlington

Washington DC

Permit type 001Permit type 002Permit type 003

A003

Example of Permit Determination


6.38

SAP AG 1999

PermitService Object

Regional StructureArea 0001

Gas Reconnection

Permit Determination


6.39

SAP AG 1999 SAP AG

Processes in the Utilities Industry: Summary

Orders and notifications in many utilities-specific processes can be generated automatically using codes. The codes provide the necessary parameters and control plant and work center determination.

These processes include aperiodic meter readings, disconnections, device replacements, and so on.

The creation of orders and notifications for regular inspections is supported further by inspection lists.

If various companies are involved in these processes, data can be exchanged with IDocs and BAPIs.


6.40Processes in the Utilities Industry: Exercises

Unit: Processes in the Utilities Industry

Topic: Service Object and Order Code


Explain the purpose of order codes and notification codes

Make the most important Customizing settings for creating and assigning order codes

In a utilities company, there are lots of processes for which service orders are generated automatically in the background. With meter reading orders, a service order is required if it is an aperiodic meter reading, such as a repair or control reading.

1-1 Create a service object and assign it to an order code.

1-1-1 Define a service object Group ##.

Use planning plant U003, order type SM01, and main work center 16/3.

1-1-2 Define the order code GR## in the IMG.

1-1-3 Assign the order code to the service object.


Exercises


Topic: Aperiodic Meter Readings


Create aperiodic meter reading orders and connected service orders.

In this exercise, you will create meter reading orders for aperiodic meter readings. You will generate a service order that is displayed and processed.

2-1 Create an aperiodic meter reading order with an assigned service order. Display the meter reading order and put the service order in process.

2-1-1 Create an aperiodic meter reading order with an assigned service order. Use the MR reason 09 (Interim meter reading without billing) for installation TE0601G###.

2-1-2 Display the aperiodic meter reading order you just created and make a note of the number of the associated service order.

2-1-3 Set the service order to put in process and display the corresponding shop paper.


Exercises

Unit: Inspections

Topic: Aperiodic Inspections


Explain and use the front office processes delivered by SAP for aperiodic inspections.

3-1 Create a new technical installation and the related inspection order as part of an initial inspection.

3-1-1 Start the Customer Interaction Center and choose the business partner TE0601A###. Navigate to the premise TE0601E### and display the technical installations.

3-1-2 Start the process Create initial inspection for the premises. Choose division 06 and a description for the new technical installation.

3-1-3 Display your documents for your business partner. Check the initial inspection order you just created for the reference object, the long text you specified, and the data on the sold-to party. Release the order and save the release.

3-1-4 Display the technical installations for the premise again. The technical installation you created should be the last inspection without a date.

3-2 Complete the initial inspection you just created.

3-2-1 Start the function Complete scheduled inspection for the initial inspection order you just created. Enter today's date as the inspection date.

3-2-2 Check the technical installation for the premise again. The date of the last inspection and the next inspection date should now be set.

3-2-3 Check the initial inspection order. This should be technically completed (status TECO).

3-3 Create an order for an advance inspection.

3-3-1 Start the process Create advance inspection for the premise TE0601E### of your business partner. Choose the technical installation you just created.

3-3-2 Start the Change function for the advance inspection order you just created. Check the order for the defined reference object, the long text you specified, and the data on the sold-to party. Release the order and save the release.


3-4 Close the advance inspection you just created.

3-4-1 Start the function Complete scheduled inspection for the advance inspection order. Enter today's date as the inspection date.

3-5 Complete an unscheduled inspection.

3-5-1 Start the process Complete unscheduled inspection for the premise TE0601E### of your business partner. Choose the technical installation you just created. Enter a date in the future.

Check the technical installation for the premise again. The date of the last inspection for the technical installation you chose should now be set in line with the data you specified. Check the calculation of the date of the next inspection once again.


Exercises

Unit: Inspections

Topic: Periodic Inspections


Explain and use the concept of periodic inspections

4-1 Display the Apartments campaign using various selection criteria.

4-1-1 Display the complete Apartments campaign.

4-1-2 Restrict the display to 1-room apartments in Maple Leaf Road in Washington D.C.

4-1-3 Display only the apartments for which there are not yet any orders.

4-1-4 What is the simplest way of completing existing orders?


6.41Processes in the Utilities Industry: Solutions


Topic: Service Object and Order Code

1-1 Create a service object and assign it to an order code.

1-1-1 Define a service object Group ##.

Tools AcceleratedSAP Customizing Edit Project SAP Reference IMG SAP Utilities Work Management Master Data Define Service Objects.

Choose New entries.

Enter U003 in the Planning plant field and 00 in the Service object ID field.

Choose Enter.

In the Service object field, enter Group ##.

In the Order type field, enter SM01. Enter 16/3 in the Main WorkCenter field and specify plant U003.

Save the entry.

1-1-2 Define the order code in the IMG.

Work Management Processing Orders Define Order Codes.

Choose New entries.

Enter order code GR## and the short text Service object Gr. ##.

Save the entry.

1-1-3 Assign the order code to the service object.

Work Management Processing Orders Allocate Service Objects to Order Codes.

Choose New entries.

Enter order code GR##, a short text, the service object ID 01, and the Service object Group##.

Save the entry.


Solutions


Topic: Aperiodic Meter Readings

2-1 Create an aperiodic meter reading order with an assigned service order. Display the meter reading order and put the service order in process.

2-1-1 Create an aperiodic meter reading order with an assigned service order. Use the MR reason 09 (Interim meter reading without billing).

Choose Utilities Industry Device Management Meter reading Order Creation Individual Order.

Select Installation and enter TE0601G###. Select 09 as the meter reading reason.

In the Scheduled MRD field under Scheduling, enter the last day of the current month.

Execute. The message Meter reading orders and/or billing orders created for installation appears.

2-1-2 Display the aperiodic meter reading order you just created and make a note of the number of the associated service order.

Choose Meter reading Monitoring Manual.

Select Installation and enter installation TE0601G###. Choose Meter reading order and enter the meter reading reason 09. Choose Execute.

The header data of the meter reading order is displayed. Make a note of the order number in the Service order field.

2-1-3 Set the service order to put in process and display the corresponding shop paper.

Choose Work Management Processing Service Processing Order Service Order Change. Enter the order number ######.

Choose Put in process.

In the dialog box, choose Print with online window.

Select shop paper E090 for the display.

Enter A000 as the output device (not a printer).

Choose Print preview. The shop paper contains the data relevant to the meter reading.


Solutions

Unit: Inspections

Topic: Aperiodic Inspections


Explain and use the front office processes delivered by SAP for aperiodic inspections.

3-1 Create a new technical installation and the related inspection order as part of an initial inspection.

3-1-1 Start the Customer Interaction Center and choose the business partner TE0601A###. Navigate to the premise and display the technical installations.

Identify the business partner.

Click the premise with the right mouse button and choose Display.

Choose Create initial inspection.

3-1-2 Start the process Create initial inspection for the premises. Choose division 06 and a description for the new technical installation.

Click the premise with the right mouse button and choose Create initial inspection.

Enter the division and a description.

Choose Step forward.

3-1-3 Display your documents for your business partner. Check the initial inspection order you just created for the reference object, the long text you specified, and the data on the sold-to party. Release the order and save the release.

In the navigation area, choose the Documents tab page.

Choose Refresh.

Display the service orders and choose Change for the initial inspection order.

Check the data and then choose Release.

Save the order.

3-1-4 Display the technical installations for the premise again. The technical installation you created should be the last inspection without a date.


3-2 Complete the initial inspection you just created.

3-2-1 Start the function Complete scheduled inspection for the initial inspection order you just created. Enter today's date as the inspection date.

Choose Complete scheduled inspection for the initial inspection order.

Enter today's date as the inspection date.


3-2-2 Check the technical installation for the premise again. The date of the last inspection and the next inspection date should now be set.

3-2-3 Check the initial inspection order. This should be technically completed (status TECO).

3-3 Create an order for an advance inspection.

3-3-1 Start the process Create advance inspection for the premise TE0601E### of your business partner. Choose the technical installation you just created.

Click the premise with the right mouse button and choose Create advance inspection.

Choose the technical installation.


3-3-2 Start the Change function for the advance inspection order you just created. Check the order for the defined reference object, the long text you specified, and the data on the sold-to party. Release the order and save the release.


Choose Refresh.

Display the service orders and choose Change for the advance inspection order.

Check the data and then choose Release.

Save the order.


3-4 Close the advance inspection you just created.

3-4-1 Start the function Complete scheduled inspection for the advance inspection order. Enter today's date as the inspection date.

Choose Complete scheduled inspection for the advance inspection order.

Enter today's date as the inspection date.


3-5 Complete an unscheduled inspection.

3-5-1 Start the process Complete unscheduled inspection for the premise TE0601E### of your business partner. Choose the technical installation you just created. Enter a date in the future.

Click the premise with the right mouse button and choose Complete unscheduled inspection.

Enter the inspection date and choose Execute.

Choose the technical installation.


3-5-2 Check the technical installation for the premise again. The date of the last inspection for the technical installation you chose should now be set in line with the data you specified. Check the calculation of the date of the next inspection once again.


Solutions

Unit: Inspections

Topic: Periodic Inspections


Explain and use the concept of periodic inspections

4-1 Display the Apartments campaign using various selection criteria.

4-1-1 Display the complete Apartments campaign.

Choose Work Management Processing Inspections Display Inspection List.

Choose the campaign Apartments.

Execute.

4-1-2 Restrict the display to 1-room apartments in Maple Leaf Road in Washington D.C.

Choose Work Management Processing Inspections Display Inspection List.

In the selections for the technical installations, enter the type of premise 0004 and Maple Leaf Road in the Regional selections.

Execute.

4-1-3 Display only the apartments for which there are not yet any orders.

Delete the selection criteria you just entered and choose Only select entries without order/notification under Restrictions.

Execute.

4-1-4 What is the simplest way of completing existing orders?

Choose Work Management Processing Inspections Change Inspection List.

Choose the Apartments campaign again and restrict the selection to Only select entries with order/notification.

Execute.

You can complete the orders by choosing Complete.



7

SAP AG 1999

Contents:

Integration of complementary software (CSP)

The GIS Business Connector

Further interfaces to external systems


(C) SAP AG IUT221 1

7.2

SAP AG 1999


Explain how to integrate complementary software (CSP)

Outline how CSPs communicate with the R/3 System

Describe the CSPs that you can integrate with the R/3 System

Describe the GIS Business Connector

Interfaces to External Systems: Unit Objectives

(C) SAP AG IUT221 2

7.3

SAP AG 1999

Interfaces to External Systems: Course Overview Diagram




Service

Service Products




(C) SAP AG IUT221 3

7.4

SAP AG 1999

Interfaces to External Systems: Business Scenario

IDES Energy Inc. wants to link various systems to the Work Management system:

Work orders will be created on the basis of notifications from the OMS and the SCADA system.

Processes such as grid extensions or marketing tasks will use the SAP system and the GIS simultaneously.

The field sales representatives will be able to upload unplanned data to the Work Management system.

The aim of using a CADS system is to extend the possibilities of scheduling and dispatching in the SAP system even further.

(C) SAP AG IUT221 4

7.5

SAP AG 1999

Integration of Complementary Software (CSP)

(C) SAP AG IUT221 5

7.6

SAP AG 1999

SCADA

GISAM/FM

CADS

OMS

IS-U/CCSWork ManagementPMCS...... Service orders

Completion confirmations

Outagenotificationsand orders

Outages atsubstations

Connectivity information

Monitoring of the situation

Geographical data

Mobile DevicesService orders

Completion confirmations

MDI

Integration of External Systems

GB

C

The GIS Business Connector MDI = Mobile Data Interface CADS = Computer-aided Dispatch System OMS = Outage Management System SCADA = Supervisory Control and Data Acquisition AM/FM = Asset Management/Facility Management

(C) SAP AG IUT221 6

7.7

SAP AG 1999

How to Integrate a CSP (1)

Set up a model for the business processes (for example, as an event process chain)

Assign process owners to the steps of the chain (SAP and/or CSP)

Derive a detailed description of the interfaces (data exchange):

Define sender/receiver/owner of the data

Describe type of interface (online, batch, real time and so on)

Push or pull principle, ....

Identify/define business objects and methods to handle the input/output at the interfaces

Certify the interface/CSP

(C) SAP AG IUT221 7

7.8

SAP AG 1999

Business Process ProcessOwner

SAP

SAP

SAP

CSP

Data Exchange

Details for Interface

Fields,objects

Fields,objects

B O R

Businessobjects,methods

Businessobjects,methods

How to Integrate a CSP (2)

(C) SAP AG IUT221 8

7.9

SAP AG 1999

IDoc interfaces for uploading/downloading

Outage notification, notification of the end of the outage

Orders for device replacement, installation, or removal

Collection/disconnection orders

Confirmation of work orders

Mobile data information

BAPI interfaces for

Creating service orders

Creating notifications

Updating the status of service orders and notifications

Setting the dates and times of notifications

Interfaces for Work Management

The following IDocs (Intermediate Document) transfer data to external systems (outbound processing): ISU_OMS_ORDER: download of outage order ISU_RPL_ORDER: download of replacement order (meter reading) ISU_COL_ORDER: download of collection/disconnection order ISU_DL_ORDER: download of order created for a device location ISU_OMS_NOTIF: download of outage notification

The following IDocs copy data from external systems (inbound processing): ISU_DEVICE_CHANGE: upload of device replacement/installation/removal ISU_MDI_UPLOAD: upload of mobile data information ISU_OMS_END: end of outage

BAPIs The Business Object Repository (BOR) contains the following business application programming interfaces (BAPIs) for work management: UtilServiceOrder.CreateMultiple: create service orders UtilServNotification.CreateMultiple: create notifications UtilServiceOrder.SetStatusTechnCompleted: set the status of order to technically completed UtilServNotification.SetDateTime: set the dates and times of notifications UtilServNotification.SetCompleted: set status of service notification to completed

(C) SAP AG IUT221 9


7.10

SAP AG 1999

Work OrderWork Order IDocIDoc tRFCtRFC

Work Manag.

ALE

• Process work orders

• Preparethe IDoc

• Recipient determination

• Generate the IDocs

• Link to application objects

• Communic-ation setup

• Send the message

C ProgramC Program ApplicationApplication

• Data input • Data processing

SAP System External System

Comm-unication

Outbound Processing with ALE

Abbreviations: ALE = Application Link Enabling tRFC = transactional Remote Function Call


7.11

SAP AG 1999

tRFCtRFC IDocIDoc Work OrderWork Order

Comm-unication

ALE Work Manag.

• Receive the IDoc

• IDoc in the data-base

• Call up the application

• Process the IDoc

SAP System

External System

External System IDocIDoc

• Data prepara-tion

• Send an IDoc

External System

Inbound Processing with ALE


7.12

SAP AG 1999

Function Module(RFC-capable)


Function Builder

R/3





Business Object Repository

Business ObjectWork Order

Business ObjectWork Order

BAPIBAPI

BAPIBAPI

BAPIBAPI

Object-oriented accessObject-oriented access RFC accessRFC access

Business Objects, BAPIs, Function Modules

BAPIs are defined as methods of SAP Business Objects in the Business Object Repository (BOR) and implemented in the R/3 System as function modules.

The SAP Business Objects meet the guidelines set up by the OAG (Open Application Group) and other committees.

The BAPIs enable access to data and processes from external systems. External programs just have to call up the BAPIs to access the data and processes.

Object-oriented access to a BAPI can be performed using various programming platforms, such as Windows NT, Win9x, DCOM/COM.

You can also execute direct RFC calls to the function module on which the BAPI is based. Either using ABAP or from external development platforms by using the RFC class library of C/C++, for example.

Stability and compatibility: A BAPI interface certified by SAP remains stable with regard to the interface definition

(input/output parameters). Enhancements to existing BAPIs are only permitted with additional optional parameters. This ensures

the stability of the existing applications while also providing the option of making new functions accessible.


7.13

SAP AG 1999

The GIS Business Connector


7.14

SAP AG 1999

Advantages of an Integrated Interface

Using central objects in GIS and IS-U:

Service connection

Equipment for energy distribution, lines, transformer stations

Access to technical and business data in both systems

"Cross-application" processes, such as

Installation service for service connections

Cost analyses on the basis of geographical selection

Marketing campaign for customers that are not yet being supplied

A link to a geographical information system (GIS) enables you to model technical objects of the Work Management (IS-U-WM) component, such as grids, cables, stations or service connections, in a geographical framework. While the logical relationships between the objects are modeled in work management, you can view the spatial relationships in the GIS.

Central objects are objects that are required in both systems and are often stored redundantly. "Cross-application processes" enable a new view of the data:

Business data can be accessed from the GIS and can be evaluated with graphical selections, for example.

Planning in SAP can also access data from the GIS, for example.


7.15

SAP AG 1999

GeographicalCoordinates

Connections

GraphicalDisplay

GIS

Data Distribution

Cost Center

Company Code

Work Orders

Maint. Planning Plant

SAP/ IS- U

Divisions

Addresses

TechnicalData

The data that is required in both systems and often is stored redundantly is critical for an interface. An interface must, as far as possible, avoid redundant data or at least ensure this data is kept consistent.


7.16

SAP AG 1999

Connection obj. 10

Connection 4711

Connection obj. 20

Connection 4712

Connection obj. 30

Connection 4713

IS-UGIS

Transformer 12

Objectlinks

Functional location

Equipment

3-D objects

Intersection

Logical ObjectsGraphical Objects

GIS Interface: Example

If your service territory is large, SAP recommends that you maintain only the objects of the distribution grid in the GIS.

If your service territory is small, you can manage objects down to service connection level. Here, the GIS enables you to map the connection between the supply grid and the customer objects of IS-U. However, this is recommended only if the grid structures are relatively static.


7.17

SAP AG 1999

Database Database

Exchangeof

data fields

Applications

Applications

GIS SystemGIS System SAP SystemSAP System

SAPtransaction

calls

SAPprogram

calls

Interface only works synchronously SAP system does not support industry-specific

functions No GIS information is available in the SAP system

The CAD Interface

Historically speaking, the CAD (computer aided drafting) interface originated from the areas of design and engineering. It enables documents from an external system to be linked to an SAP material master, for example.

Some functions of the CAD interface from plant maintenance are used to implement a GIS link. Communication is performed via Remote Function Calls (RFC), which are based on the TCP/IP

protocol. A disadvantage is the lack of topological data in SAP. Examples:

Which service connections are supplied by which transformer station? Which customers have to be informed if the supply has to be interrupted?

You can find a list of authorized GIS systems in SAPNet.


7.18

SAP AG 1999

Methods

Methods

Middleware

GBCGBC

Applications

GISGIS

Business Objects

SAPSAP

Applications

Business ObjectsEnhanced

applications

Enhanced applications

The Principle of the GIS Business Connector

For each business process in the SAP system that affects data that is important in GIS, a method is called up in GBC: The GBC then tests whether the GIS is available. If the GIS is available, the GBC identifies the data

objects in the GIS and calls up the appropriate method. If the GIS is unavailable or if information on the required data objects is missing, the GBC buffers the

worksteps that are yet to be executed. When a user logs onto the GIS, the GIS starts a connection to the GBC and instructs the GBC to execute the waiting worksteps.

The procedure is the same for business processes in the GIS.


7.19

SAP AG 1999

Properties of the GBC

Used as a mapping tool for:

Business objects of SAP and GIS applications

Methods of the business objects

Data fields for identifying technical objects

Enables synchronous and asynchronous method calls

Backlog and error handling

Is not an active driver of the business process (pull principle of the SAP or GIS application)

The GIS Business Connector has a flexible design. If a GIS offers business objects and methods to access the data, it can be used with the GIS Business Connector.

The interface for communicating with the GBC is implemented as a BOR object (objet type ISUGBCIF).


7.20

SAP AG 1999

GISSAP

Actional Control Broker

Actional Control Broker

ObjectRepository

ObjectRepository(BOR)

IS-U GBC

ObjectRepository(BOR)

CALL GBC.method()

Events

CALL GBC.method()

System Architecture of the GBC

The Control Broker from the company Actional is used as a generic tool for communication between GBC and GIS. This enables the GBC to communicate with various object models (COM/DCOM and CORBA, for example).


7.21

SAP AG 1999

Customizing the GBC

Create object relationships and maintain method repositories

Set relationships between BOR and GIS

Store GIS object methods in the repository

Define tasks and assign methods

All objects are assigned to a particular object relationship

Assign fields and values

Transferring data to the methods via

Field assignment: Fixed values or user a defined function

Default Values

Define key allocation for every task


7.22

SAP AG 1999

Create New Service Connection (I)

Equipment

- Create

- Change

- .....

Equipment

- Create

- Change

- .....

Connection

- Create

- Read

- .....

Connection

- Create

- Read

- .....

Object relationship

Create object relationsips and maintain method repositories:

Determine relationships between BOR and GIS

Store GIS object methods in the repository

GIS ObjectsBOR


7.23

SAP AG 1999

Create New Service Connection (II)

Define tasks and assign methods

All objects are assigned to a particular object relationship

GBC task of creating the object relationship between SAP equipment and the GIS connection:

Read the service connection in the GIS

Connection READ

Create the service connection in SAP

Equipment CREATE


7.24

SAP AG 1999

Create New Service Connection (III)

Assign fields and values

Define key allocation

1. Task is called

GIS service connection key is put in the data container

2. Read the service connection data in the GIS

Input: GIS key

Output: service connection data

3. Create the service connection in SAP

Input: service connection data

Output: SAP key

4. Assign GIS and SAP keys


7.25

SAP AG 1999

GISGISSAPSAP GBCGBCGBC

Object Attribute Method

Company Code

Division

SAP_HC.CREATE

ConnectionEquipment 4711

Division

XY Coordinates

GIS_HC.CREATE

ConnectionObject 0815

4711 0815<=>

GBC_HC.CREATEGBC_HC.CREATE

Company Code

Division

XY Coordinates

GBC ObjectGBC ObjectHCHC

call method....

call method.... call method....

call method....

Example: New Service Connection

A service connection is created in the R/3 System. The SAP system calls up a method in GBC and supplies data at once. The GBC ensures that the method for creating a service connection is also called up in the GIS.

If the process for creating the connection begins in the GIS, it is reversed.


7.26

SAP AG 1999

SAPGIS

The Grid Extension Project

Start of the project forextending a grid

Start of the project forextending a grid

Plan the new line and the required resources

Plan the new line and the required resources

Detailed resource planning (service objects)Cost estimation

Detailed resource planning (service objects)Cost estimation

Plan alternatives Optimization

Display the results

Plan alternatives Optimization

Display the resultsSelect the final version

Budget approvalSelect the final version

Budget approval

Create the work orders and release the resources

Create the work orders and release the resources

Monitor the progress of the work

Monitor the progress of the work

Change the final version Confirm and activate the

installed version

Change the final version Confirm and activate the

installed versionComplete work orders / projects

Create the asset register

Complete work orders / projects

Create the asset register

Confirm the work ordersTechnical completion

Confirm the work ordersTechnical completion

Interactive Link Between SAP and GBC


7.27

SAP AG 1999

GIS Integration: Further Examples

The utilities company informs its customers of an impending power cut due to maintenance work at a transformer station:

The low-voltage grid is stored in the GIS: network trace from the transformer station to the affected service connections

Service connections are assigned to customers in the SAP system

Customer reports malfunction

The GIS determines the whole outage region

A work order for a crew is created in the SAP System

The GPS locates the crew nearest the outage region


7.28

SAP AG 1999

Interfaces to Further External Systems

Outage Management Systems (OMS)

Computer-Aided Dispatch and Scheduling Systems (CADS)

SCADA Systems

Mobile Data Interface (MDInt)


7.29

SAP AG 1999

Customer reports malfunction

Notification is sent to the outage management system as an IDoc

Clerk chooses service objectin the front office

2

1

3

OMS: Outage Notification (1)

An outage management system analyzes faults in the supply grid reported by customers. If the number of faults accumulates in a particular section of the grid, it determines whether the cause is a central fault (such as a transformer failure). The R/3 System can manage the correction of the fault and determine which customers are affected. It does this using "connectivity," which informs it whether the supply medium is being transferred between two nodes.

Prerequisites A geographical information system (GIS) or a network information system (NIS) is installed to enable

connectivity information to be called up. The technical objects (such as equipment) and the basic customer information are available in the

outage management system. Step 1: Customer reports outage to utility company Step 2: A clerk creates a notification (or a work order) in IS-U/CCS Step 3: The notification is sent to the outage management system (OMS) as an IDoc via Electronic Data

Interchange (EDI)


7.30

SAP AG 1999

OMS

SCADA

GIS

Connectivityinformation

Outage notification (IDoc)

Completion confirmation

Repair order

Complete orders

Confirm work

SAPWM Current status

3

4

CADS

4

Compare data

5

6

Bundle notifications for an order

4

OMS: Outage Notification (2)

Step 4: The Geographical Information System (GIS) localizes problems reported in notification and reports coordinates to OMS. At the same time, the Supervisory Control and Data Acquisition (SCADA) system reports the current state of the network system. The PM component also matches the equipment data to the current state of the network report from SCADA.

Step 5: OMS sends an answer to the R/3 System. Step 6: The R/3 System creates one service order based on several customer notifications. If work orders are created instead of notifications, you can specify one of the orders as the superior order

for further processing. All of the corresponding orders are then completed collectively.


7.31

SAP AG 1999

Scheduling and Dispatching with SAP and CADS

Functionality within the SAP R/3 System:

Assignment of individual persons in workforce planning

Direct assignment of persons in work orders

Planning board

Possible additional functions of a Computer-Aided Dispatch System (CADS):

Automatic scheduling

Use of mobile means of communication

Geographical interfaces

A scheduling and dispatching system is used if a variety of orders are to be scheduled automatically and assigned to work groups or service technicians. This is suitable for orders that do not take long to process and that cover mainly standardized activities. The orders that are to be scheduled automatically are either generated in the Work Management (IS-U-WM) component directly or result from IS-U processes.

Examples from the IS-U: Orders for aperiodic meter reading Orders for disconnection and reconnection Meter replacement Periodic replacement

Some systems also enable you to transfer the data for the work groups to mobile devices (such as laptops, pagers, or hand-held devices).


7.32

SAP AG 1999

CADSCADSSAPWM

Meter reading ordersMeter reading information

Labor confirmation

Data (such as meter reading results)

Collection ordersAccount info, Contract info

Update order status

12

3

4

5

6

7

Create the orders

Assign work groups

Complete the orders

Data Exchange Between SAP and CADS

Prerequisite: Orders have been entered and scheduled in the R/3 System (1) Process flow:

The orders are transferred to the scheduling and dispatching system (2). This system schedules the orders and allocates them to the work groups (3). This process is influenced by criteria such as:

Required qualificationGeographical conditions (such as distance, journey time)PrioritiesFixed dates

While the order is being processed, information on its status is supplied (4). After the work has been carried out, the data for the resources used (such as personnel or materials) is

transferred from the scheduling and dispatching system to IS-U-WM (5). If IS-U processes are affected, the corresponding data (such as the meter reading results from removed or installed meters) is transferred from the scheduling and dispatching system to IS-U-WM (6).

Result: The order and the accompanying IS-U processes are completed (7).



7.33

SAP AG 1999

Field BUS

Process control system

Process control

SCADA

Supervisory Control & Data Acquisition

Measuring and ruling

devices

SAP R/3 PM

Business objects

and methods

Mea

su

re

Ru

le

Transmission and triggering of plant maintenance activities

Business applications

SCADA connects the process control with business applications

Process and installation monitoring

SCADA Systems: Principle of the Interface


7.34

SAP AG 1999

What are interface scenarios?

SCADA Systems: Interface Scenarios

Condition-based monitoring:

Predefined events trigger maintenance notifications in SAP R/3 PM

Preventive maintenance:

Wear and tear is forwarded to R/3 PM (meter reading, measurement readings)

Scheduling of activity-dependent maintenance plans generates preventive maintenance activities


7.35

SAP AG 1999

SCADA SystemSAP R/3 PM Application

Store values for weekly consumption

Create measurement document for this measuring point

Store values for weekly consumption


Measurement reading lies above threshold value


Set trigger for counter-based maintenance plan

Measurement reading lies above threshold value


Set trigger for counter-based maintenance plan

Frequency spectrum for drive shaft

Crack in shaft discovered

Generate malfunction report to repair wave

Frequency spectrum for drive shaft

Crack in shaft discovered

Generate malfunction report to repair wave

SCADA Systems: Scenario for a Gas Station


7.36

SAP AG 1999

Mobile Data Interface

Decentralized CCS functionality ("front office on site")

Variable feedback information

Structured and unstructured information

Execute unplanned actions

Perform only a few checks on site

Perform extensive checks in IS-U/CCS

Interface must be adjusted for individual requirements

Enhance IDoc to include the required data

Create include

Create function module that transports data from the IDoc to theinclude

The IDoc ISU_MDI_UPLOAD for the data upload is defined and shipped by IS-U. It contains segments for the creation of the notification.

SAP cannot define the processes for all customers because every customer has different requirements and different processes. That is why you have to define a customer extension segment based on the segment E1ISU_MDI_NOT_TASK_DATA. This segment should contain all data to be passed to IS-U/CCS. In addition, you have to define the customer-include CI_MDI_DATA. This customer-include has to be defined containing the same fields than the customer-segment of the IDoc. The data transport between the fields of the customer extension segment and the fields of the customer include has to be done in the user-exit function module EXIT_SAPLEEWM_IF_MDI_1_001.

The customer-defined function module does not have to contain any parameters. It can get the necessary data from the IDoc by calling the IS-U function module ISU_READ_FOLLOW_UP_ACTION_DATA. This function module reads the global data of the IDoc inbound process. This means that it returns a structure containing the customer-include.


7.37

SAP AG 1999

IS-U

CCS

IS-U

CCS

Notifications- Activities

- TasksPM/SM

Notifications- Activities

- TasksPM/SM

Customer action

Customer action

13

4

IDoc frommobile device

IDoc frommobile device

2

5

6

Inbound processing

Create notification

Read the additional data

Call follow-upactions

e.g. change bankdata of customer

Additional customer-defined data

Mobile Data Interface (Example)

In our business process example the customer function module can call the IS-U function module to change the bank details of the utility's customer. Now the function module of the customer has all the data it needs to execute the required IS-U

function modules (1+2). Within IS-U, there is a function module which processes the incoming IDoc. This function module

creates a notification with activities and tasks depending on the IDoc data (3). In Customizing for the standard components PM/CS, the customer can define a follow-up action for

each task. This follow-up action is the call of a function module. When the notification is created all follow-up actions to tasks are executed (4-6).


7.38

SAP AG 1999 SAP AG

CSPs are integrated in the R/3 System via IDocs and

BAPIs.

The GIS Business Connector enables GIS and Work

Management to be integrated and the two systems to

be linked interactively in various business

processes.

Work Management also works together with OMS,

CADS, and SCADA systems.

The mobile data interface (MDI) allows for flexible

feedback information from the field.

Interfaces to External Systems: Summary


7.39Interfaces to External Systems: Exercises

Unit: Interfaces to External Systems

Topic: All Topics


Understand the GIS concept and the connections between it and the Work Management system

Describe the purpose and functions of the Outage Management system

Describe the purpose and functions of the Scheduling and Dispatching system

1-1 True or False?

1-1-1 A link to the SAP document management system enables you to model technical objects of the Work Management (IS-U-WM) component, such as grids, cables, stations or service connections, in a geographical framework. For example, while the logical relationships between the objects are modeled in work management, you can view the spatial relationships in document management.

1-1-2 An outage management system analyzes outage data from the work management system reported by customers.

1-1-3 Prerequisites for an outage management system are (1) geographical information system (GIS) or a network information system (NIS) installed so that the connectivity can be called and (2) in the outage management system the technical objects (such as pieces of equipment) and, if applicable, basic customer information are available.

1-1-4 A scheduling and dispatching system is used if a variety of orders are to be scheduled automatically and assigned to work groups or service technicians. This is suitable for orders that do not take long to process and that cover mainly standardized activities. The orders that are to be scheduled automatically are either generated in the Work Management (IS-U-WM) component directly or result from IS-U processes.

2-1 Create an outage notification and the corresponding IDoc that can be sent to an outage management system.

2-1-1 Create an outage notification for the device of customer TE0501A0##.

2-1-2 Display the outage message.

2-1-3 Display the IDoc that was created at the same time. Which status records have been generated?

2-1-4 Which segment of the data record contains the street name?


2-1-5 What is the name of the basic type of the IDoc created? Display the documentation for this basic type.


7.40Interfaces to External Systems: Solutions

Unit: Interfaces to External Systems

Topic: All Topics

1-1 True or False?

1-1-1 A link to the SAP document management system enables you to model technical objects of the Work Management (IS-U-WM) component, such as grids, cables, stations or service connections, in a geographical framework. For example, while the logical relationships between the objects are modeled in work management, you can view the spatial relationships in document management.

False. A link to a geographical information system (GIS) enables you to model technical objects of the Work Management (IS-U-WM) component, such as grids, cables, stations or service connections, in a geographical framework. For example, while the logical relationships between the objects are modeled in work management, you can view the spatial relationships in the GIS.

1-1-2 An outage management system analyzes outage data from the work management system reported by customers.

False. An outage management system analyzes faults in the supply grid reported by customers. If the number of faults accumulates in a particular section of the grid, it determines whether the cause is a central fault (such as a transformer failure). The R/3 System can manage the correction of the fault and determine which customers are affected. It does this using "connectivity," which informs it whether the supply medium is being transferred between two nodes.

1-1-3 Prerequisites for an outage management system are (1) geographical information system (GIS) or a network information system (NIS) installed so that the connectivity can be called and (2) in the outage management system the technical objects (such as pieces of equipment) and, if applicable, basic customer information are available.

True

1-1-4 A scheduling and dispatching system is used if a variety of orders are to be scheduled automatically and assigned to work groups or service technicians. This is suitable for orders that do not take long to process and that cover mainly standardized activities. The orders that are to be scheduled automatically are either generated in the Work Management (IS-U-WM) component directly or result from IS-U processes.

True


2-1 Create an outage notification and the corresponding IDoc that can be sent to an outage management system.

2-1-1 Create an outage notification for the device of customer TE0501A0##.


Identify the business partner and start the process Create outage message at device level in the navigation area.

Enter a value in the Problem field and a long text if you wish.

Choose Step forward and save the customer contact.

2-1-2 Display the outage message.


Choose Refresh.

Display the outage message under Service notifications.

2-1-3 Display the IDoc that was created at the same time. Which status records have been generated?

Choose Utilities Industry Work Management Interfaces IDoc and EDI Basis IDoc Display IDoc.

Choose Execute.

Choose one of the IDocs by double-clicking the line. The data records and status records of the IDoc are displayed.

2-1-4 Which segment of the data record contains the street name?

You can display the contents of the segments, in other words, the field names and field contents, by clicking the individual segments.

2-1-5 What is the name of the basic type of the IDoc created? Display the documentation for this basic type.

The basic type of the IDoc is called ISU_OMS_NOTIF.

You can display documentation on the basic type and its segments by choosing Work Management Interfaces IDoc and EDI Basis Documentation IDoc Types.
