Linear Asset Management - Operation Level Costing - Pipe Version

Linear Asset Management and Operation Account
Assignment
Linear Asset Management – One Page Summary
Linear asset management Solution enhancements Key benefits

 Linear asset management is functionality within the plant
maintenance (PM) module which is especially designed to  Linear referencing functions, for  Manage continuous assets with
meet the requirements of linear asset maintenance. example, schema for markers dynamic segmentation
 In asset intensive industries like oil & gas, railways,  Linear data modeling – enhancement  Identify maintenance locations
utilities, and public sector the utilization of traditional of technical objects functions (where to work), by linear attributes
hierarchical structure of assets to represent their (functional location and equipment) like start point and end point,
and classification system to support length, and offsets
production or infrastructure networks is a complex and
the definition of a linear asset
difficult process.  Increase assets capability and
 The need to represent and model assets which extend for  Linear asset work management – availability as low performance in
enhancement of work order any linear section can have big
several kilometers (or miles) with changing characteristics
processing to support linear work impact on overall throughput
and conditions requires modeling and management tools
definition including work orders,
to provide the specific capabilities to support and manage confirmations, and maintenance plans.  Ability to report on order costs at
these complex assets. operation level
 Inspection and condition monitoring –
enhancement of notifications,
measurement points and counters, and
measurement documents to support
linear information
 Reports for all of the above
COO
 
Engineering Maintenance Procurement Operations
© 2010 SAP AG. All rights reserved. / Page 3

AGENDA
1. Linear Asset Management
2. Operation Account Assignment

Linear Asset Management
AGENDA

 Introduction
 Linear Data Modeling
 Work Management
 Inspection and Condition Monitoring
 SOA Enterprise Services
 Reporting
 Business Add-Ins (BAdIs)

Challenges of Linear Assets
 Linear asset types:

 Road – Markers, for example, mileposts or kilometer posts, lane, direction, offsets, bridges, tunnels, signs, and so on
 Rail – Mile or chain markers, track number, offset, switch, crossings, signals, and so on
 Pipe – Kilometer point, compressor stations, valves, pig stations, and so on
 The linear aspect has to be reflected in:
 Master data
 Inspections
 Condition recording
 Maintenance and repair
 Linear assets need to managed as a continuous asset with dynamic segmentation

Typical Attributes of a Linear Asset
 A special type of asset which has an associated length dimension; this dimension is represented by
means of start points and end points or by specifying the asset length
 Configuration has the complexity that components (or features) can be “installed” along its length
 Attributes can change frequently along its length
 Typically connected with other linear assets to represent an infrastructure network or route
 Subject to dynamic segmentation; multiple sets of attributes can be associated with any portion of
an existing linear feature independently of where it begins or ends
 Require a linear referencing method as a mean to describe and locate a position along its length
 Permanent referencing locations (markers or referencing locations) plus offsets are used as
reference to describe the exact position along the linear asset

AGENDA

 Introduction
 Work Management
 Reporting

Linear Data Fields
Field Description Values Remarks
Linear Reference Pattern (LRP) Marker schema LRP ID Only valid for functional location and equipment
Start Point Start point of the linear asset Distance value in UOM For point locations, the position along the linear
asset is indicated in this field
End Point End point of the linear asset Distance value in UOM
Length Length of the linear asset Length of linear asset in UOM
Unit of Measure (UOM) Unit of measure of the linear asset Miles, kilometers, and so on
Start Marker Milepost
End Marker Milepost
Distance From Start Marker Offset from start marker Distance value in UOM
Distance From End Marker Offset from end marker Distance value in UOM
Unit of Measure (UOM) Unit of measure for marker offset distances Yards, meters
Offset 1 Perpendicular reference center line Typically perpendicular offset, for example, right
right margin angles to center line
left margin
Unit of Measure (UOM) Unit of measure of the offset Yards, meters; degrees
Offset 2 Vertical reference center line Typically vertical offset
ground level
tunnel roof
Unit of Measure (UOM) Unit of measure of the offset Yards, meters

Linear Data Fields – Screen Layout

Linear Data Fields Based on Technical Object (Functional
Location) Category Customizing

Linear Data - Offsets
Offsets are used to define an exact location
4,75m
2,15m
4,60 km

Linear Data Fields in Functional Location

Linear Asset Attributes
Modeled using classification and characteristics

For linear assets, the valuation of characteristics has been enhanced with the linear
data aspects.
Examples:
Material
S1 from x1 to y1 S2 from x2 to y2
Diameter
D1 from x3 to y3 D2 from x4 to y4

Linear Reference Pattern (LRP)
MP9
Can be used to define a set of markers

MP8
6 types of markers
MP7
1. Classic marker, for example, milepost

2. Functional location, for example, bridge MP6
3. Equipment, for example, sign gantry MP5
4. Well-known location, for example, service station

MP4
5. Well-known functional location

6. Well-known equipment MP3
MP2
MP1

Linear Reference Pattern (LRP) Table

Use of Markers
The markers (LRP) are available via an F4-Help on the Start Point and End Point
as well as marker fields.
Field Description Values Remarks

St.Marker Marker point or well-known location Milepost, mile point, meter post, reference point
Dist.St.M. Distance from start marker Numeric value - : negative number is distance form closest “up”
marker
+ : positive number is distance from the closest

“down” marker
Unit of Measure Unit of measure for offset
End Marker Marker point or well-known location Milepost, mile point, meter post, reference location
Dist End Marker Distance from end marker Numeric value - : negative number is distance form closest “up”
marker
+ : positive number is distance from the closest

“down” marker

Mass Changes for Technical Objects
Functional Locations (also available for equipment)

Asset Viewer

Technical Object (Web Dynpro)

Network – Tabular View

Network – Graphical Viewer

AGENDA

 Introduction
 Work Management
 Reporting

Work Order: Header Data
Linear data is assigned to the location tab

Linear Data Fields Fields in Operations
Available in tabular and detail view

Linear Data – Simplified and Basic Order
Example - simplified with one tab; direct access to linear data fields

Work Order Confirmation – Individual

Maintenance Plan Item with Linear Data Information

AGENDA

 Introduction
 Work Management
 Reporting

Notification Header with Linear Data Information

Notification Item with Linear Data Information
Technical object and linear data fields can be assigned

The Linear Data Fields in Measuring Points

The Linear Data Fields in Measurement Documents

AGENDA

 Introduction
 Work Management
 Reporting

Service-Oriented Architecture (SOA) Enterprise Services
Enterprise Services allow external applications, for example, geographical information systems (GIS)
or mobile to communicate with the SAP ERP application.
The following existing SOA Enterprise Services have been be enhanced with the linear data fields*:
 Create, Change, Display Functional Location (Installation Point)
 InstallationPointERPCreateCheckQueryResponse_In_V1
 InstallationPointERPCreateRequestConfirmation_In_V1
 InstallationPointERPChangeCheckQueryResponse_In_V1
 InstallationPointERPChangeRequestConfirmation_In_V1
 InstallationPointERPByIDQueryResponse_In_V1
 Create, Change, Display Equipment (Individual Material)

 IndividualMaterialByIDQueryResponse_In_V1
 IndividualMaterialERPCreateRequestConfirmation_In_V1
 IndividualMaterialERPCreateCheckQueryResponse_In_V1
 IndividualMaterialERPChangeRequestConfirmation_In_V1
*only start point, end point, length, UoM, and offsets

AGENDA

 Introduction
 Work Management
 Reporting

Reports Enhanced with Linear Data Information
The following list reports have been enhanced with the linear data information
 List reports
 Functional locations, equipment, notifications, orders, confirmations, measuring points,
measuring documents, maintenance plan items
 Multi-level list reports
 Functional locations, equipment, notifications, orders
 Structure list reports
 Functional locations, equipment

List Reports – Selection Parameters
There are various selection parameters available to search for objects with linear data, including range or
segment, LRP ID, Start Point, End Point, and so on. These selection parameters are consistent across all the list
reports.

List Report – Output with Linear Data Information
 The fields displayed in the list are

subject to how the layout has been
set up. As well as the data fields
shown, additional linear data fields
can be included by including them in
the layout.

Functional Location Structure List with Linear Data
Information

Dynamic Segmentation Analysis
Func. Loc. PIPE2
Equip. S02519
Equip. S02656
Char: pipe material
Char: pipe diameter
Char: pipe coating
Work order: 901961
Operation 0010
Operation 0020
Work order: 901989
Operation 0020
Operation 0020
Notification 1007423
Item 001 : onsite inspection
Item 002: surface damaged
Meas. Point: wall thickness
Meas. Doc: 1 µmm
Meas. Doc: 0,87µmm
0,00km 1000,00km

Multi-Level List for Functional Locations
Selection options
Dynamic segment
Select data to be
shown in analysis

Multi-Level List Report with Linear Data Information

Multi-Level List Report in Graphical Layout
Drill-down to business object possible

AGENDA

 Introduction
 Work Management
 Reporting

Business Add-Ins (BAdIs)
4 BAdIs have been provided for linear asset management:

 Adjustment of linear point determination
 Adjustment of linear data display
 Enhancement of linear data screen – example shown below
 Checking of linear data

Operation Account Assignment
AGENDA

 Business Background
 Maintenance and Service Order
 Work Execution
 Period End Processing
 Reporting
 Summary

The Need for Detailed Costing
 There has always been a need to cost out individual tasks during
maintenance while keeping the aggregated total for the entire job,
especially in service industries.
 There is also a need from external bodies (regulators, legal

requirements) to capture costs on a detailed level and report them
in categories that are not part of the companies‟ overall business
strategy.
 The Operation Account Assignment (OAA) solution allows for a

single order with cost objects at the operation level. Each of the
processes available for the header are now available at the
operation.
 An order must be header-based or operation-based costing.

There is no ability to have mixed mode costing.

Operation Account Assignment
Target areas of functional improvements
Solution overview
Master data Planning Execution Closure Analytics
Technical object Resource-related

Cost estimation Confirmation OLTP cost reporting
integration billing
Financial asset Resource-related OLTP revenue

Inventory Settlement
integration quotation reporting
BI
Budgeting Procurement
(Header totals)
Investment
G/L postings
management
SRM integration
 The OAA enhancement touches many parts of the enterprise asset management
work process.
 Operation-level SRM and BI integration is “planned” for EhP6.
AGENDA

 Work Execution
 Reporting
 Summary

Operation Account Assignment (OAA) Order
Indication using system status
The system status I0053 (ACAS in English) is displayed when the order operation is the
account assignment object. This is the same indicator as for a PS network with activity
level costing.

OAA Order
Account assignment details and operation costs
The account assignment details for
an operation are shown on the
Account Assignment tab of the
operation detail view.
Sub-operation account assignment

values are inherited from the
superior operation.
The FERC indicator field is only

available when Business Function
EA-FRC is active.
The costs are displayed in the cost

tabs on the lower panel.

Account Assignment Details
Defaulting account assignment information
Order header Order operation
Profit center Profit center
Functional area Functional area
Default values BAdI PM activity type
PM activity type
Costing sheet Header value Overwrite Costing sheet
= default values
Overhead key with customer Overhead key
Operation
Object class value logic Object class
Business area Business area
Tax jurisdiction code Tax jurisdiction code
FERC Indicator FERC indicator
BAdI
WBS element with customer WBS element
implementation
Defaulting for operation takes place when a

new operation is created.

Operation Costs
Update of plant maintenance cost view
existing header for costed orders Operation-level costing
Reporting / Transactions / Extraction
Dynamic summation for

header values
costs:
header plan/actual header
OVnnnn
ORnnnn OVnnnn
……… OVnnnn costs:
operation plan/actual operation
…………
Stored in database as
costs:
operation operation
plan/actual
Transformation of costs
(plan/actual) according to
costs:
operation value categories plan/actual operation
OAA order costs are only stored for the operation objects. Header totals are dynamically summed as
required. No costs are stored on the database for the OAA order object.
Operation Costs
Cost display
The cost overview of the operation displays

individual sub-operation planned costs if
allocated.
The operation costs are the sum of the

operation and any sub-operations.
The individual sub-operation planned
costs can be seen on the overview tab.
Operation relevant quantities are

calculated in the same manner as
header relevant quantities.

Operation Costs
Sub-operation
The sub-operation inherits account assignment information from the superior operation.
As sub-operations are primarily intended for allocating extra work centers to an operation, the sub-operation
displays the total costs of the superior operation and any sub-operations. In the cost overview of the operation
the individual sub-operation planned costs may be seen.
Actual costs cannot be posted to a sub-operation.
Copy Estimated Costs from Planned Costs
Copy function
For OAA orders, manual entry of estimated costs is only

at the operation level with the header displaying the sum
of the operations.
For ease of use, the estimated costs may be copied from
the planned costs at any point until order release using
the copy estimated cost button.
The copy function also works with regular header costed
orders.
This copied version may for example be utilized to
„freeze” the planned costs at time of order release.
After copy, the status SKKP is set and manual input of estimated values is no longer possible.
The values may be recopied and overwritten as many times as required during the planning phase.
If the compatible units functionality is active (Business Function/ CUM/ MAIN) customizing may be set to allow
automatic copy at order release.
Settlement Rules
Defaulting settlement rules
Existing header costed orders Operation-level costing
header Order header header
settlement
rules Existing
default engine
operation operation
settlement
rules
operation operation
BAdI to
modify settlement
rules
defaults BAdI to
modify
operation operation
already defaults
existing settlement
BAdI rules
new
BAdI
A default implementation is used to provide header-like default rule logic. If a technical object is assigned to the operation it will
be used to derive default rule. If no technical object is allocated the header, technical object will be used to attempt a default
rule derivation. Settlement rule requirement settings in customizing will only pass when all operations meet the set condition.

Settlement Rules
Settlement rule status
The generation of default settlement rules

may be triggered manually for operations
selected in the operation overview
screen.
To facilitate easy viewing of settlement
rule status, it is suggested that the default
operation overview list layout include the
system status field.
Operations with settlement rules will have
status I0028 which is “SETC” in English.
Transaction “KOSRLIST_OR” may be used to list settlement rules for all operations of an order.

New Logs
Operation settlement rule and account assignment
Two new logs are introduced.

The Operation Account Assignment menu is only
available when there is an active BAdI implementation.
The settlement rule log displays information from the default rule creation and customer messages returned from
implementations of the BAdI BADI_OLC_SETTL_RULE_DET_OPR.
The Operation Account Assignment log displays customer messages returned from implementations of the account assignment
BAdI ES_EAM_OAA_DEFAULT.
AGENDA

 Work Execution
 Reporting
 Summary

Postings During Work Management Execution
costs:
Inventory
management
costs:
operation Procurement operation
order no. + operation no.

plan/actual
(material+services)
order no.
costs:
operation G/L plan/actual
operation
postings
costs:
operation Time plan/actual operation
confirmation
costs: Time
plan
confirmation Sub-operation
only
Generally planned and actual costs are posted at the operation level. The exception is that sub-operations
will only ever have planned costs for activity postings. Actual costs for sub-operation postings will post to the
superior operation.
Order Budgeting
Availability check
Budget
costs:
Availabilty check
operation
(tolerances, transactions, ..) costs:
operation
plan/actual
costs:
operation operation
plan/actual
Individual order budgets may be set at the order header level.
The availability check for postings to the operation will be against costs:
operation the total of all operations in the order (dynamic header total). plan/actual operation

Completion Confirmation
IW42 constraints
When an OAA order is entered in IW42, the entry profile is checked for inclusion of material or service sub-screens. If these sub-
screens do not exist in the profile, all operations may be confirmed else an error message will notify that entry of an operation is
also required.
When a single operation is entered, any materials or internal services for the operation will be defaulted for entry.
Purchasing
Purchase requisition and order
Purchase requisitions created from OAA orders will have the
originating operation as the default account assignment
object for the item.
A new field, VORNR_AUF, has been added to purchasing
account assignment screens. This field is used to enter the
order operation field for OAA Orders.
The operation account assignment from the purchase

requisition is automatically transferred to the purchase
order.
Manual account assignment to the operation is also
possible.

Goods Movement
Goods issue and receipt
Material reservations for an OAA order default the originating operation as the account assignment object.
The goods issue for the reservation retains this operation as the default account assignment object.
Unplanned goods movements may have manual operation account assignment.
The goods receipt for a purchase order maintains the originating operation as the account assignment object.
Financial Documents
Document list and line item detail
For financial document detailed account assignment

(Coding Block) views, the field VORNR_AUF has been
added.
Layouts for financial document details may include the order
operation as shown in the transaction FB03 example.

Project System Integration
Assignment to WBS elements
existing header costed orders
Cost reporting Scheduling Revenue target

header WBS A budgeting determination
Not applicable As for order header BAdI

costing
YES, Not applicable BAdI
operation WBS B if WBS
maintained
costs:
plan/actual
YES, Not applicable BAdI
operation if WBS
maintained
costs:
plan/actual YES, Not applicable BAdI
if WBS
operation WBS A-1 maintained
costs:
plan/actual Functional areas in which the
WBS assignment can be used
Operations can individually be assigned to “released” WBS elements.
Header assignment to OAA orders is for scheduling purposes only.

PS functions impacting operations
Overhead
costs: calculation
Interest
calculation
costs:
Copy of plan versions
(plan / plan)
costs:
operation operation
plan/actual
Creation of simulation
versions
costs:
Settlement
Operations assigned to WBS elements

can be included in the project structure
processing functions. Single and mass processing
(for example, along WBS or project hierarchy )

Project structure
Operations allocated to WBS elements are displayed under the assigned WBS in the structure.
The unassigned operations are displayed under their order outside of the project structure.

Cost reporting
As with the structure views, any unassigned operations from orders with assigned operations are displayed
under their order outside of the project structure.

OAA Order Billing
Resource-related quotation and billing
Revenue postings to header Revenue postings to
costed order possible and cost objects allowed to carry
allowed revenues
costs:
order + operation no.
removed in billing items
costs:
Billing DP90
document
costs:
operation VA02 operation
plan/actual
DP90 Debit memo

actual costs request (DR) costs:
VA22
DP80 Resource related DP80

planned costs quotation (AE)

OAA Order Billing
Constraints
With the standard header costed service order, the order itself can be the final revenue object.
As the operation will not be a revenue object, OAA order takes a different approach.
During the generation of the sales documents from the resource-related billing process, the internal
representation of the originating operation is stored in the fields AUFPL_OAA/APLZL_OAA for
reference purposes.
When the subsequent billing document is created from the sales document, the profit center from the
operation is defaulted as the revenue object and the reference operation details are cleared.
If the customer wishes to change this behavior the BAdI “BADI_SD_BILLING” may be used to
determine the correct revenue object.
It is suggested for larger jobs that the project system be used and that WBS elements assigned to the
operations be used as the final revenue objects. The appropriate WBS element can be read from the
originating operation record. This allows for easy combination of different orders into the billing
process.

AGENDA

 Work Execution
 Reporting
 Summary

Period End Processing
Overhead calculation and settlement
costs:
costs:
operation Overhead plan/actual operation
calculation
costs:
operation operation
plan/actual
Settlement
costs:
Single and mass processing

Overhead and settlement processing for OAA orders is performed at the individual operation level.
An OAA order will be settled for all operations if none is specified, or for individually entered operations.
Mass processing has the same selection options.
Operations allocated to WBS elements may be settled during project system settlement if the “With orders”
option is specified in the settlement selection parameters.
Order Settlement
Settlement options
costs: Settlement receivers

settlement
rules Order
Cost center costs:

Fixed asset settlement
rules
WBS element
costs:
operation operation
plan/actual
G/L account
settlement
rules
……………..
costs:
settlement
Order operation rules
Single and mass processing
Settlement rules cannot be maintained at the header level for OAA orders.
The operation cannot be a settlement receiver.
AGENDA

 Work Execution
 Reporting
 Summary

Reporting
Operation overview report
The operation cost overview report shows costs for all operations by value category.
The report can be run as a transaction IW40N and include sub-orders.
Reporting
Order document flow
Each posted document is created under the originating operation.

OAA Orders as Sub-Orders
Hierarchical operation cost report
OAA orders may be created as sub-orders.

A new hierarchy cost report displays the
costs of all order header totals as well as the
individual operation costs for OAA orders.
This report may be run as transaction IW40N
with multiple order selection.
Each value column is summed to the respective superior node.

Node summation functions can display total, average, maximum, and minimum values.
Reporting
CO reports
The CO report writer has been

adjusted to read the operation cost
objects.
CO cost reports are available at the operation

and header level. The header reports select
data from all operations for the order.
Individual operation details are available in
the line item reports.

Operation List Edit with Cost Display
(IW37/IW49)
 Similar to the order list reports,
the operation lists have the cost
fields available for display.
 The list reports IW37N and
IW49N have not been adjusted
and are planned for inclusion in
EhP6.

AGENDA

 Work Execution
 Reporting
 Summary

Summary
 No business processes have been changed. The only difference is the granularity of the
order cost collection.
 The order operation screens have been enhanced to include account assignment data and
maintain and display operation costs.
 PM/CS and FI/CO reports have been adjusted to display the originating operation costs.
 Logistics transactions have been enhanced to allow the operation as an account
assignment object.
 Controlling and financial transactions have been enhanced to allow the operation as an
account assignment object.
 The operation may be assigned to a WBS element and become integrated into the PS
project structure and period end processing transactions.
 Applicable BAPIs have been enhanced to understand the order operation as an account
assignment object.

Thank You!

Linear Asset Management - Operation Level Costing - Pipe Version

Uploaded by

Copyright:

Available Formats

You might also like

Linear Asset Management - Operation Level Costing - Pipe Version

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Linear Asset Management - Operation Level Costing - Pipe Version

Uploaded by

Copyright:

Available Formats

Linear Asset Management and Operation Account

Linear asset management Solution enhancements Key benefits

 Reports for all of the above

© 2010 SAP AG. All rights reserved. / Page 3

1. Linear Asset Management

2. Operation Account Assignment

© 2010 SAP AG. All rights reserved. / Page 4

1. Linear Asset Management

© 2010 SAP AG. All rights reserved. / Page 6

 Linear asset types:

© 2010 SAP AG. All rights reserved. / Page 7

© 2010 SAP AG. All rights reserved. / Page 8

1. Linear Asset Management

© 2010 SAP AG. All rights reserved. / Page 9

Length Length of the linear asset Length of linear asset in UOM

Start Marker Milepost

End Marker Milepost

© 2010 SAP AG. All rights reserved. / Page 10

© 2010 SAP AG. All rights reserved. / Page 11

© 2010 SAP AG. All rights reserved. / Page 12

© 2010 SAP AG. All rights reserved. / Page 13

© 2010 SAP AG. All rights reserved. / Page 14

Modeled using classification and characteristics

© 2010 SAP AG. All rights reserved. / Page 15

Can be used to define a set of markers

1. Classic marker, for example, milepost

3. Equipment, for example, sign gantry MP5

4. Well-known location, for example, service station

5. Well-known functional location

© 2010 SAP AG. All rights reserved. / Page 16

© 2010 SAP AG. All rights reserved. / Page 17

Field Description Values Remarks

+ : positive number is distance from the closest

Unit of Measure Unit of measure for offset

+ : positive number is distance from the closest

© 2010 SAP AG. All rights reserved. / Page 18

© 2010 SAP AG. All rights reserved. / Page 19

© 2010 SAP AG. All rights reserved. / Page 20

© 2010 SAP AG. All rights reserved. / Page 21

© 2010 SAP AG. All rights reserved. / Page 22

© 2010 SAP AG. All rights reserved. / Page 23

1. Linear Asset Management

© 2010 SAP AG. All rights reserved. / Page 24

© 2010 SAP AG. All rights reserved. / Page 25

© 2010 SAP AG. All rights reserved. / Page 26

© 2010 SAP AG. All rights reserved. / Page 27

© 2010 SAP AG. All rights reserved. / Page 28

© 2010 SAP AG. All rights reserved. / Page 29

1. Linear Asset Management

© 2010 SAP AG. All rights reserved. / Page 30

© 2010 SAP AG. All rights reserved. / Page 31

© 2010 SAP AG. All rights reserved. / Page 32

© 2010 SAP AG. All rights reserved. / Page 33

© 2010 SAP AG. All rights reserved. / Page 34

1. Linear Asset Management

© 2010 SAP AG. All rights reserved. / Page 35

 Create, Change, Display Equipment (Individual Material)

*only start point, end point, length, UoM, and offsets