Linear Asset Management Operation Account Assignment Fitt Morrow RKT LES 21June2010
description
Transcript of Linear Asset Management Operation Account Assignment Fitt Morrow RKT LES 21June2010
SAP ERP 6.0 Enhancement Package5 - RKT ProjectLinear Asset Management (LAM)Operation Account Assignment (OAA)
Dean FittSolution ManagerIBU Oil and Gas
Kevin MorrowSolution ManagerIBU Utilities
© SAP AG 2009. All rights reserved. / Page 2
Disclaimer
“This presentation outlines our general product direction and should not be relied on inmaking a purchase decision. This presentation is not subject to your license agreementor any other agreement with SAP. SAP has no obligation to pursue any course ofbusiness outlined in this presentation or to develop or release any functionalitymentioned in this presentation.
This presentation and SAP's strategy and possible future developments are subject tochange and may be changed by SAP at any time for any reason without notice.
This document is provided without a warranty of any kind, either express or implied,including but not limited to, the implied warranties of merchantability, fitness for aparticular purpose, or non-infringement. SAP assumes no responsibility for errors oromissions in this document, except if such damages were caused by SAP intentionallyor grossly negligent.”
© SAP AG 2009. All rights reserved. / Page 3
Agenda
1. Linear Asset Management2. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 4
Agenda
1. Linear Asset ManagementIntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
2. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 5
Challenges of Linear Assets
The location information can vary depending on the asset type e.g.Roads – Markers e.g. mileposts/kilometerposts, lane, direction, offsets, bridges, tunnels,signs etc.Rail – Mile or chain markers, track number, offset, switch, crossings, signals etc.Pipeline – Kilometer Point, compressor stations, valves, pig stations etc.
The linear aspect has to be reflected in:InspectionsConditionMaintenance and Repair
Linear Assets need to managed as a continuous asset with dynamic segmentation
© SAP AG 2009. All rights reserved. / Page 6
Typical Attributes of a Linear Asset
A special type of asset which has an associated length dimension; this dimensionis represented by means of start points and end points or by specifying the assetlengthConfiguration has the complexity that components (or features) can be “installed”along its lengthAttributes can change frequently along its lengthTypically connected with other linear assets to represent an infrastructure networkor routeSubject to dynamic segmentation; multiple sets of attributes can be associatedwith any portion of an existing linear feature independently of where it begins orendsRequire a linear referencing method as a mean to describe and locate a positionalong its lengthPermanent referencing locations (markers or referencing locations) plus offsets areused as reference to describe the exact position along the linear asset
© SAP AG 2009. All rights reserved. / Page 7
Linear Asset Management – Overall Concept
0,00km 529,8km
Func. Loc. A-A9
Equip. S02519
Equip. S02656
Char: surface concrete
Char: surface bitumen
Char: speed limit 120 km/h
Work order: 901961
Operation 0010
Operation 0020
Work order: 901989
Notification 1007423
Item 001 : onsite inspection
Item 002: surface damaged
Meas. Point: roughness
Meas. Doc: 1 µmm
Meas. Doc: 0,87µmm
Operation 0020
Operation 0020
© SAP AG 2009. All rights reserved. / Page 8 Customer
Check Enterprise BusinessLOG_EAM_LINEAR_1 Function is Active
First Node of IMG or Transaction SFW5
© SAP AG 2009. All rights reserved. / Page 9
Agenda
1. Linear Asset ManagementIntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
2. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 10
Linear Data Fields
Field Description Values RemarksLinear Reference Pattern (LRP) Marker Schema LRP ID Only valid for Functional Location
and Equipment
Start Point Start point of Linear Asset Distance Value in UOM For point locations, the positionalong the Linear Asset is indicatedin this field
End Point End point of 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 etc.
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 OffsetDistances
Yards, Meters
Offset 1 Perpendicular Reference center lineright marginleft margin
Typically Perpendicular Offset e.g.right angles to center line
Unit of Measure (UOM) Unit of measure of the offset Yards, Meters; Degrees
Offset 2 Vertical Reference center lineground leveltunnel roof
Typically Vertical Offset
Unit of Measure (UOM) Unit of measure of the offset Yards, Meters
© SAP AG 2009. All rights reserved. / Page 12
Linear Assets – Technical ObjectsLinear Data Fields applied to Functional Locations and Equipment
TEA-21 Empire Corridor, ……..
Linear Data Fields contenttraditional EAM content
start end length
TEA-21-3 Track 1, …..
TEA-21-2 Track 2, …..
0.000 460.000 460.000
0.000 460.000 460.000
0.000 150.000 150.000
Offset
0.000
0.000
0.000
TEA-21-2-T21 Turnout 21 Track 2, ….. 52.250 0.000
Ref
center
center
center
center
UoM
Mile
Mile
Mile
Mile
TEA-21-2-S03 Croton-Harmon Siding, ….. 50.300 52.250 2.200 0.500 centerMile
Sup. FL
TEA-21
TEA-21
TEA-21-3
TEA-21-2
UoM
yds
yds
yds
yds
yds
( functional location )equipment
850001 115 Lb/Yd AREA Rail, ….
850003 Concrete Tie, ....
850002 136 Lb/Yd AREA Rail, ….
850004 Concrete Tie 7x7x9, ....
0.000 52.250 52.250 0.000 centerMileTEA-21-3 yds
52.250 125.500 73.250 0.000 centerMileTEA-21-3 yds
0.000 460.000 460.000 0.000 centerMileTEA-21-3 yds
0.000 460.000 460.000 0.000 centerMileTEA-21-3 yds
yds52.250 2
yds52.250 0.000
center
center
Mile
Mile
850005 Switch Stand, …
850006 Switch Frog, …
TEA-21-2-T21
TEA-21-2-T21
850010 115 Lb/Yd AREA Rail, ….
850012 HW 7x7x9, ....
0.000 150.000 150.000 0.000 centerMileTEA-21-2 yds
53.250 90.000 36.750 0.000 centerMileTEA-21-2 yds
850011 Concrete Tie, .... 0.000 53.250 53.250 0.000 centerMileTEA-21-2 yds
Offset 2
0.000
0.000
0.000
0.000
Ref
ground
ground
ground
ground
0.500 ground
UoM
yds
yds
yds
yds
yds
0.000 ground yds
0.000 ground yds
0.000 ground yds
0.000 ground yds
yds0.000
yds0.000
ground
ground
0.000 ground yds
0.000 ground yds0.000 ground yds
© SAP AG 2009. All rights reserved. / Page 13
Linear Data Fields Based on Technical Object(Functional Location) Category Customizing
© SAP AG 2009. All rights reserved. / Page 14
4,75m
2,15m
4,62m
4,60 km
0,80 km
Linear Data - Offsets
Offsets are used to define an exact location
© SAP AG 2009. All rights reserved. / Page 16
The Linear Data Fields in Classes andCharacteristics
For linear assets the valuation of characteristics has been enhanced with the LinearData Fields. The characteristic allows a multiple valuation so that each value can belimited in location and extension.
Examples:
Speed limit: t1 from x1 to y1t2 from x2 to y2
Surface: h3 from x3 to y3h4 from x4 to y4
© SAP AG 2009. All rights reserved. / Page 17
Linear Referencing Pattern (LRP)Offsets can used to define location
MP1
MP4
MP5
MP6
MP7
MP8
MP9
MP3
MP2
Six Types of Markers
1. Classic Marker e.g. Milepost
2. Functional Location e.g. Bridge
3. Equipment e.g. Sign Gantry
4. Well Known Location e.g. Service Station
5. Well-known Functional Location
6. Well-known Equipment
© SAP AG 2009. All rights reserved. / Page 19
Relative Referencing – Use of Markers
Field Description Values Remarks
St.Marker Marker point or Well Know Location Mile Post, 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 theclosest “down” Marker.
UoM Unit of Measure for Offset
End Marker Marker point or Well Known Location Mile Post, 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 theclosest “down” Marker.
Fields for Relative Referencing will be enabled through F4-Help in the Start and End Point aswell as Marker fields.
© SAP AG 2009. All rights reserved. / Page 20
Mass Changes for Technical ObjectsFunctional Locations (also available for Equipment)
© SAP AG 2009. All rights reserved. / Page 21
Agenda
1. Introduction2. Linear Asset Management
IntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
3. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 22
Work Order: Header DataLinear data is assigned to the location tab
© SAP AG 2009. All rights reserved. / Page 23
Linear Data Fields Fields in OperationsAvailable in Tabular and Detail View
© SAP AG 2009. All rights reserved. / Page 24 Customer
Default Rules - 1Order Operations
Define default settings in the Customizing activity Define Change Docs, Collective Purc. Req.Indicator, Operation No. Interval by choosing Plant Maintenance and Customer Service ->Maintenance and Service Processing -> Maintenance and Service Orders -> Functions andSettings for Order Types -> Define Change Docs, Collective Purc. Req. Indicator, Operation No.Interval
© SAP AG 2009. All rights reserved. / Page 25
Linear Data – Simplified/Basic OrderExample - simplified with one tab; direct access to linear data fields
© SAP AG 2009. All rights reserved. / Page 28
Agenda
1. Introduction2. Linear Asset Management
IntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
3. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 30
Notification Item with Linear Data InformationTechnical Object and Linear Data Fields can be assigned
© SAP AG 2009. All rights reserved. / Page 31 Customer
Default Rules - 2Assign Default Rule to Notification Type
Define default settings in the Customizing activity Define Default Rules for Linear Data inNotification Items by choosing Plant Maintenance and Customer Service -> Maintenance andService Processing -> Maintenance and Service Notifications -> Notification Processing ->Additional Functions -> Define Default Rules for Linear Data in Notification Items
© SAP AG 2009. All rights reserved. / Page 34
Agenda
1. Introduction2. Linear Asset Management
IntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
3. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 35
SOA Enterprise Services
Enterprise Services allow external systems e.g. Geographical Information Systems(GIS) to communicate with the SAP ERP system.
The following existing SOA Enterprise Services have been be enhanced with theLinear Data Fields* :
Create, Change, Display Functional Location (Installation Point)InstallationPointERPCreateCheckQueryResponse_In_V1InstallationPointERPCreateRequestConfirmation_In_V1InstallationPointERPChangeCheckQueryResponse_In_V1InstallationPointERPChangeRequestConfirmation_In_V1InstallationPointERPByIDQueryResponse_In_V1
Create, Change, Display Equipment (Individual Material)IndividualMaterialByIDQueryResponse_In_V1IndividualMaterialERPCreateRequestConfirmation_In_V1IndividualMaterialERPCreateCheckQueryResponse_In_V1IndividualMaterialERPChangeRequestConfirmation_In_V1
*only start/end point, length and UoM and offsets
© SAP AG 2009. All rights reserved. / Page 36
Agenda
1. Introduction2. Linear Asset Management
IntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
3. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 37
Reports Enhanced with Linear DataInformation
The following reports have been enhanced with the Linear Data InformationList Reports
Functional Locations, Equipment, Notifications, Orders, Confirmations,Measuring Points, Measuring Documents, Maintenance Plan Items,
Multi-Level List ReportsFunctional Locations, Equipment, Notifications, Orders
Structure List ReportsFunctional Location, Equipment
© SAP AG 2009. All rights reserved. / Page 38
List Reports - Selection Parameters
There are various selection parameters available to search for objects with linear dataincluding range or segment, LRP ID, Start and/or End Point etc. These selection parametersare consistent across all the list reports.
© SAP AG 2009. All rights reserved. / Page 39
List Report – Output with Linear DataInformation
The fields displayed in thelist are subject to how thelayout has been set up.As well as the data fieldsshown, additional lineardata fields can beincluded by including themin the layout
© SAP AG 2009. All rights reserved. / Page 40
Functional Location Structure List with LinearData Information
© SAP AG 2009. All rights reserved. / Page 42
Multi-Level List Report in Graphical LayoutSelectable from list output display
© SAP AG 2009. All rights reserved. / Page 43
Agenda
1. Introduction2. Linear Asset Management
IntroductionLinear Data ModelingWork ManagementInspection and Condition MonitoringSOA Enterprise ServicesReportingBAdI‘s
3. Operation Account Assignment
© SAP AG 2009. All rights reserved. / Page 44
Business Add-Ins (BAdI’s)
Four Business Add-Ins (BAdI’s) have beenprovided for Linear Asset Management:
1. Adjustment of Linear PointDetermination
2. Adjustment of Linear Data Display3. Enhancement of Linear Data Screen –
example shown4. Checking of Linear Data
© SAP AG 2009. All rights reserved. / Page 45
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 46
There has always been a need to cost out individual tasks duringmaintenance 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 arenot part of the companies’ overall business strategy.
The Operation Account Assignment (OAA) solution allows for a singleorder with cost objects at the operation level. Each of the processesavailable for the header are now available at the operation.
An order must be header based or operation based costing. There is noability to have mixed mode costing.
The need for detailed costing
© SAP AG 2009. All rights reserved. / Page 47
Budgeting
Cost Estimation
ResourceRelatedQuotation
Confirmation
Procurement
SRM Integration
G/L Postings
ResourceRelated Billing
Settlement
OLTP CostReporting
OLTP RevenueReporting
BI(Header totals)
Inventory
Planning Execution Closure Analytics
Solution overview
Master Data
Technical ObjectIntegration
Financial AssetIntegration
InvestmentManagement
Operation Account AssignmentTarget Areas of Functional Improvements
The OAA enhancement touches many parts of the EAM work process.
Operation level SRM and BI integration is “planned” for EhP6.
© SAP AG 2009. All rights reserved. / Page 48
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 49
Check Enterprise Business FunctionLOG_EAM_OLC is Active
First Node of IMG or Transaction SFW5
Information accessible from here includes:DocumentationRelease NotesTest Catalog
© SAP AG 2009. All rights reserved. / Page 50
Define Cost Settings for Costs at theOperation Level
Define cost settings in the Customizing activity Define Cost Settings by choosing PlantMaintenance and Customer Service -> Maintenance and Service Processing -> Maintenanceand Service Orders -> Functions and Settings for Order Types -> Costs at Operation Level - >Define Cost Settings
The Costs at Operation Level are defined by order type within each plant.
Refurbishment and Investment orders may not be configured for operationaccount assignment.
© SAP AG 2009. All rights reserved. / Page 51
Configure Order Types for Customer Billing
Configure Customer Service Orders for Billing in the Customizing activity Configure Order Typesby choosing Plant Maintenance and Customer Service -> Maintenance and Service Processing-> Maintenance and Service Orders -> Functions and Settings for Order Types -> ConfigureOrder Types
In order to run the Resource Related Billingfunctions for an operation account assignmentorder the “Revenue postings” flag must be set.Transaction DP80 for QuotationsTransaction DP90 for Debit Memo Requests
The operation cannot be used as a revenueobject and the “true” revenue object must bedetermined when generating the billing document.
BAdI “BADI_SD_BILLING“ can be used forcustomer defined billing object derivation.
© SAP AG 2009. All rights reserved. / Page 52
List Editing – Goods Movements for OrdersDefine Field Selection for Goods Movement for Orders
Define field selection for the Operation field in Goods Movement Editing lists in the Customizingactivity Set List Editing for Goods Movements of Orders by choosing Plant Maintenance andCustomer Service -> Maintenance and Service Processing -> Maintenance and Service Orders-> Functions and Settings for Order Types -> Goods Movements for Order -> Set List Editing forGoods Movements of Orders
Enables display and grouping by operation ofgoods movements within an order
© SAP AG 2009. All rights reserved. / Page 53
BAdI: Maintenance/Service Order: SettlementRule for Operation
Execute the Business Add-In BAdI: Maintenance/Service Order: Settlement Rule for Operation,in the Customizing activity by choosing Plant Maintenance and Customer Service -> SystemEnhancements and Data Transfer -> Business Add-Ins -> Operation Account Assignment ->BAdI: Maintenance/Service Order: Settlement Rule for Operation
You can use this BAdI to create settlement rules for a maintenance or service order at operationlevel.
A default implementation, BADI_OLC_SETTL_RULE_DET_OPR is used to provide the standardlogic for default rule creation. Customers may provide their own implementation to change thebehavior of the settlement rule creation.
© SAP AG 2009. All rights reserved. / Page 54
BAdI: Define Default Values for OperationAccount Assignment
Execute the Business Add-In BAdI: Define Default Values for Operation Account Assignment, inthe Customizing activity by choosing Plant Maintenance and Customer Service -> SystemEnhancements and Data Transfer -> Business Add-Ins -> Operation Account Assignment ->BAdI: Define Default Values for Operation Account Assignment
By default account assignment values are inherited from the order header. The BAdIES_EAM_OAA_DEFAULT enables you to populate certain fields with default values for amaintenance and service order in the case of account assignment at operation level.
Methods in this BAdI enable you to default values for:1. Costing Sheet, Overhead Key and Profit Center2. Tax Jurisdiction Code.3. Project WBS element.
© SAP AG 2009. All rights reserved. / Page 55
BAdI: IS-U/FERC: Extension for RegulatorReporting
Execute the Business Add-In BAdI: IS-U/FERC: Extension for Regulator Reporting, in theCustomizing activity by choosing Plant Maintenance and Customer Service -> SystemEnhancements and Data Transfer -> Business Add-Ins -> Operation Account Assignment ->BAdI: IS-U/FERC: Extension for Regulator Reporting
The BAdI ES_EAM_FERC_DEFAULT enables you to populate the Utilities FERC indicator fieldwith a default value for a maintenance and service order in the case of account assignment atoperation level.
© SAP AG 2009. All rights reserved. / Page 56
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 57
OAA OrderIndication using System Status
The system status I0053 (ACAS in English) is displayed when theorder operation is the account assignment object. This is the sameindicator as for a PS network with activity level costing.
© SAP AG 2009. All rights reserved. / Page 58
OAA OrderAccount assignment details and operation costs
The account assignmentdetails for an operation areshown on the AccountAssignment tab of theoperation detail view.
Sub-operation accountassignment values areinherited from the superioroperation.
The FERC indicator field isonly available whenBusiness Function EA-FRCis active.
The costs are displayed inthe cost tabs on the lowerpanel.
© SAP AG 2009. All rights reserved. / Page 59
Order header
Profit Center
Defaulting for operation takes placewhen a new operation is created.
Order operation
Functional Area
PM Activity Type
Costing Sheet
Overhead Key
Object Class
Business Area
Tax Jurisdiction Code
FERC Indicator
WBS Element
Profit Center
Functional Area
PM Activity Type
Costing Sheet
Overhead Key
Object Class
Business Area
Tax Jurisdiction Code
FERC Indicator
WBS Element
BADI
Overwritedefaultvalueswith
customerlogic
Defaultvalues
Headervalue
=Operation
value
BADIWith customerimplementation
Account Assignment DetailsDefaulting account assignment information
© SAP AG 2009. All rights reserved. / Page 60
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
ORnnnn………
Reporting / Transactions / Extraction
Transformation ofcosts (plan/actual)according to value
categories
OVnnnnOVnnnnOVnnnn…………
Stored in database as
Dynamic summationfor header values
Operation costsUpdate of Plant Maintenance Cost View
OAA order costs are only stored for the operation objects. Header totals are dynamicallysummed as required. No costs are stored on the database for the OAA Order object.
© SAP AG 2009. All rights reserved. / Page 61
Operation costsCost Display
The cost overview of the operationdisplays individual sub-operationplanned costs if allocated.
The operation costs are thesum of the operation and anysub-operations.
The individual sub-operationplanned costs can be seen onthe overview tab.
Operation relevant quantitiesare calculated in the samemanner as header relevantquantities.
© SAP AG 2009. All rights reserved. / Page 62
Operation costsSub-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 beseen.
Actual costs cannot be posted to a sub-operation.
© SAP AG 2009. All rights reserved. / Page 63
Copy Estimated Costs from Planned CostsCopy Function
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 toallow automatic copy at order release.
For OAA orders manual entry of estimatedcosts is only at the operation level with theheader displaying the sum of the operations.
For ease of use the estimated costs may becopied from the planned costs at any pointuntil order release using the copy estimatedcost button.
The copy function also works with regularheader costed orders.
This copied version may for example beutilized to ‘freeze” the planned costs at time oforder release.
© SAP AG 2009. All rights reserved. / Page 64
settlementrules
Settlement RulesDefaulting settlement rules
existing header costed orders operation level costing
header
operation
operation
operation
header
operation
operation
operation
Order header
Existingdefault engine
settlementrules
settlementrules
settlementrules
BADI tomodify
defaults BADI tomodify
defaultsalreadyexisting
BADI newBADI
A default implementation is used to provide header like default rule logic. If a technical object is assigned tothe operation it will be used to derive default rule. If no technical object is allocated the header technicalobject will be used to attempt a default rule derivation. Settlement rule requirement settings in customizingwill only pass when all operations meet the set condition.
© SAP AG 2009. All rights reserved. / Page 65
Settlement RulesSettlement rule status
The generation of defaultsettlement rules may betriggered manually foroperations selected in theoperation overview screen.
To facilitate easy viewing ofsettlement rule status it issuggested that the defaultoperation overview list layoutinclude the System Statusfield.
Operations with settlementrules will have status I0028which is “SETC” in English.
Transaction “KOSRLIST_OR” may be used to list settlement rules for all operations of an order.
© SAP AG 2009. All rights reserved. / Page 66
New LogsOperation settlement rule and account assignment
Two new logs are introduced.
The Operation Account Assignmentmenu is only available when there isan active BAdI implementation.
The settlement rule log displays information from the default rule creation and customermessages returned from implementations of the BAdI BADI_OLC_SETTL_RULE_DET_OPR.
The Operation Account Assignment log displays customer messages returned fromimplementations of the account assignment BAdI ES_EAM_OAA_DEFAULT.
© SAP AG 2009. All rights reserved. / Page 67
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 68
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
orde
r no.
orde
r no.
+ o
pera
tion
no.
Timeconfirmation
Inventorymanagement
Procurement(material+services)
G/Lpostings
Sub-operationcosts:plan
TimeConfirmation
only
Postings during Work Management Execution
Generally planned and actual costs are posted at the operation level. The exception isthat sub-operations will only ever have planned costs for activity postings. Actual costs forsub-operation postings will post to the superior operation.
© SAP AG 2009. All rights reserved. / Page 69
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
Availabilty check
(tolerances,transactions, ..)
Budget
Order BudgetingAvailability Check
Individual order budgets may be set at the orderheader level.
The availability check for postings to theoperation will be against the total of alloperations in the order (Dynamic header total).
© SAP AG 2009. All rights reserved. / Page 70
Completion ConfirmationIW42 Constraints
When an OAA order is entered in IW42 the entry profile is checked for inclusion of material or servicesub-screens. If these sub-screens do not exist in the profile all operations may be confirmed else an errormessage 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 defaultedfor entry.
© SAP AG 2009. All rights reserved. / Page 71
PurchasingPurchase Requisition/Order
The operation account assignment from thepurchase requisition is automaticallytransferred to the purchase order.
Manual account assignment to the operation isalso possible.
Purchase requisitions created from OAA orders willhave the originating operation as the defaultaccount assignment object for the item.
A new field VORNR_AUF has been added topurchasing account assignment screens. This fieldis used to enter the order operation field for OAAOrders.
© SAP AG 2009. All rights reserved. / Page 72
Goods MovementGoods Issue/Receipt
Material reservations for an OAA order default the originating operation as the account assignmentobject.
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 accountassignment object.
© SAP AG 2009. All rights reserved. / Page 73
Financial DocumentsDocument List and Line Item Detail
For financial document detailed accountassignment (Coding Block) views the fieldVORNR_AUF has been added.
Layouts for financial document details mayinclude the order operation as shown in thetransaction FB03 example.
© SAP AG 2009. All rights reserved. / Page 74
Project System IntegrationAssignment to WBS Elements
operation level costingorder
header
operation
operation
operation
costs:plan/actual
costs:plan/actual
costs:plan/actual
WBS A
WBS B
WBS A-1
Cost reportingbudgeting Scheduling
Revenue targetdetermination
BAdI
BAdI
BAdI
BAdI
as for orderheadercosting
notapplicable
notapplicable
notapplicable
notapplicable
YES,if WBS
maintained
YES,if WBS
maintained
YES,if WBS
maintained
Functional areas in which theWBS assignment can be used
Operations can individually be assigned to “released” WBSelements.
Header assignment to OAA orders is for scheduling purposesonly.
© SAP AG 2009. All rights reserved. / Page 75
Project System IntegrationPS Functions Impacting Operations
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
Overheadcalculation
Single and mass processing(e.g. along WBS or project hierarchy )
Interestcalculation
Copy of planversions
(plan / plan)
Creation ofsimulationversions
Settlement
Operations assigned to WBSelements can be included inthe Project structureprocessing functions.
© SAP AG 2009. All rights reserved. / Page 76
Project System IntegrationProject Structure
Operations allocated to WBS elements are displayed under the assigned WBS in thestructure.
The unassigned operations are displayed under their order outside of the projectstructure.
© SAP AG 2009. All rights reserved. / Page 77
Project System IntegrationCost Reporting
As with the structure views, any unassigned operations from orders with assignedoperations are displayed under their order outside of the project structure.
© SAP AG 2009. All rights reserved. / Page 78
OAA Order BillingResource related Quotation and Billing
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
BillingDocument
Debit memoRequest (DR)
Resource relatedquotation (AE)
DP80
DP90
planned costs
actual costs
DP80
DP90
VA22
VA02
Revenue postings toheader costed orderpossible / allowed
order + operation no.removed in billing items
Revenue postings tocost objects allowed to
carry revenues
© SAP AG 2009. All rights reserved. / Page 79
OAA Order BillingConstraints
With the standard header costed service order, the order itself can be the final revenueobject.
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 Billingprocess the internal representation of the originating operation is stored in the fieldsAUFPL_OAA/APLZL_OAA for reference purposes.
When the subsequent billing document is created from the sales document the profitcenter from the operation is defaulted as the revenue object and the referenceoperation details are cleared.
If the customer wishes to change this behavior the BAdI “BADI_SD_BILLING” may beused to determine the correct revenue object.
It is suggested for larger jobs that the Project System be used and that WBS elementsassigned to the operations be used as the final revenue objects. The appropriate WBSelement can be read from the originating operation record. This allows for easycombination of different orders into the billing process.
© SAP AG 2009. All rights reserved. / Page 80
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 81
Period End ProcessingOverhead Calculation and Settlement
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actualOverhead
calculation
Single and mass processing
Settlement
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 “Withorders” option is specified in the settlement selection parameters.
© SAP AG 2009. All rights reserved. / Page 82
settlementrules
settlementrules
settlementrules
settlementrules
Order SettlementSettlement Options
existing header costed orders operation level costing
header
operation
operation
operation
costs:plan/actual header
operation
operation
operationcosts:plan/actual
costs:plan/actual
costs:plan/actual
Order
Cost center
Fixed asset
WBS element
G/L account
……………..
Order operation
Settlement receivers
Single and mass processing
Settlement rules cannot be maintained at the header level for OAA orders.
The operation cannot be a settlement receiver.
© SAP AG 2009. All rights reserved. / Page 83
Order SettlementSettlement Options
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 isspecified in the settlement selection parameters.
© SAP AG 2009. All rights reserved. / Page 84
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 85
ReportingOperation 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.
© SAP AG 2009. All rights reserved. / Page 86
ReportingOrder document flow
Each posted document is created under the originating operation.
© SAP AG 2009. All rights reserved. / Page 87
OAA Orders as sub-ordersHierarchical operation cost report
Each value column is summed to the respective superior node.
Node summation functions can display total, average, maximum andminimum values.
OAA Orders may becreated as sub-orders.
A new hierarchy costreport displays the costsof all order header totalsas well as the individualoperation costs for OAAorders.
This report may be run astransaction IW40N withmultiple order selection.
© SAP AG 2009. All rights reserved. / Page 88
ReportingCO Reports
The CO Report Writerhas been adjusted toread the operation costobjects.
CO cost reports are available at theoperation and header level. Theheader reports select data from alloperations for the order.
Individual operation details areavailable in the line item reports.
© SAP AG 2009. All rights reserved. / Page 89
Operation list edit with cost display(IW37/IW49/IW37N/IW49N)
Similar to the order list reportsthe operation lists have thecost fields available fordisplay.
© SAP AG 2009. All rights reserved. / Page 90
Order PM/CS Cost Rebuild(OLI5N)
Occasionally it is necessary torebuild the Plant Maintenanceview of the order costs in thecase they become out of syncwith the CO values.
The new transaction OLI5N,which calls report RIPMCO01,will rebuild the order headerlevel and operation level costsat the same time.
© SAP AG 2009. All rights reserved. / Page 91
Agenda
1. Linear Asset Management
2. Operation Account AssignmentBusiness BackgroundCustomizingMaintenance and Service OrderWork ExecutionPeriod End ProcessingReportingSummary
© SAP AG 2009. All rights reserved. / Page 92
Summary
No business processes have been changed. The only difference is the granularityof the order cost collection.The order operation screens have been enhanced to include account assignmentdata and maintain/display operation costs.PM/CS and FI/CO reports have been adjusted to display the originating operationcosts.Logistics transactions have been enhanced to allow the operation as an accountassignment object.Controlling and financial transactions have been enhanced to allow the operationas an account assignment object.The operation may be assigned to a WBS element and becomes integrated into thePS project structure and period end processing transactions.Applicable BAPI’s have been enhanced to understand the order operation as anaccount assignment object.
Dean FittSAP AG
Kevin MorrowSAP Labs LLC
© SAP AG 2009. All rights reserved. / Page 95
Procurement
Maintenance
Engineering
OperationsBusinessPlanning &Budgeting
DemandPlanning &Creation
Optimized Asset Operations and Maintenance
Service Provider Service Entry
MaintenanceCostBudgeting
TechnicalAssetManagement
DocumentManagement
AssetPerformanceManagement
MaintenancePlanning &Scheduling
Sub-contracting
OperationalSourcing
OrderCollaboration
Operations andMaintenance
ServiceProcurement
Asset Planning
Scheduling
Asset PlanningandScheduling
Engineering
COO
Spare PartsManagement
ProcurementMaintenance Operations
InvoiceCollaboration
CatalogManagement
PartsProcurement
InitiatingMaintenance
Asset andMaintenanceReporting
InventoryManagement
Master DataManagement
Preventive &CorrectiveMaintenance
ServiceDeliveryCon-firmation
Refurbish-mentProcessing
ConsumptionDrivenPlanning
OperationalProcurement
ProductionPlanning
WorkClearanceManagement
ShutdownManagement
Optimized Asset Operations and Maintenance connects processes across departmentsto ensure asset availability at lowest cost.
© SAP AG 2009. All rights reserved. / Page 96
Key BenefitsSolution Enhancements
Manage continuous assetswith dynamic segmentation.
Identify maintenancelocations (where to work), bylinear attributes likestart/end point, length andoffsets.
Increase assets capabilityand availability as lowperformance in any linearsection can have big impacton overall throughput.
Ability to report on ordercosts at operation level
Linear Asset Management – One Page Summary
Linear Asset ManagementLinear Asset Management is functionality
within the Plant Maintenance (PM) modulewhich is especially designed to meet therequirements of linear asset maintenance.
In Asset Intensive Industries like Oil &Gas, Railways, Utilities and Public Sectorthe utilization of traditional hierarchicalstructure of assets to represent theirproduction or infrastructure networks is acomplex and difficult process.
The need to represent and model assetswhich extend for several kilometers (ormiles) with changing characteristics andconditions requires modeling andmanagement tools to provide the specificcapabilities to support and manage thesecomplex assets.
Linear referencing functions e.g.schema for markers.Linear data modeling -Enhancement of technicalobjects functions (functionallocation and equipment) andclassification system to supportthe definition of a linear asset.Linear asset work management -Enhancement of work orderprocessing to support linear workdefinition including work orders,confirmations and maintenanceplans.Inspection and conditionmonitoring - Enhancement ofnotifications, measurementpoints/Counters andmeasurement documents tosupport linear information.Reports for all of the above.
Engineering
COO
ProcurementMaintenance Operations
© SAP AG 2009. All rights reserved. / Page 97
The Linear Data Fields in Technical AssetMaster Data
Both functional locations and equipment can be linear assets. The customizing ofthe category will indicate that functional locations and equipments are linear assets.
For these LAM categories the Linear Data Fields can be maintained in the masterdata in a separate tab (subject to customizing).
If point-oriented (discrete) assets are managed within LAM e.g. posts, road signs itis only necessary to maintain the start point.
For linear objects the length maintained is not checked against the differencebetween starting and end point. There are several cases that this data does notcoincide e.g. so called “short miles”
© SAP AG 2009. All rights reserved. / Page 98
Linear Data Fields Based on Technical Object(Equipment) Category Customizing
© SAP AG 2009. All rights reserved. / Page 100
Asset Viewer Web DynproPart of Maintenance Worker Role
© SAP AG 2009. All rights reserved. / Page 101
All Screens Available as Web DynproExample for Technical Object
© SAP AG 2009. All rights reserved. / Page 102
Linear Referencing Pattern (LRP)
The LRP is assigned to linear asset elements to use them as reference points whenevents or locations have to be described.
Patterns are used to indicate the distance from the starting point to the location wherethe marker is placed.
LinearElement
MP1 MP2
10 Miles
MP3 MP4 MP5 MP6 MP7 MP8 MP9
XLinearElement
Mile Post
ReferencePost
ReferenceLocation
2.5 miles
MP1 MP2
1.0 1.0 0.5
RP1 RP2
©
MilePoint
10 Miles
2.5 Miles
4 KmMeterPoint
MP2+0.5 Miles
RP2+0.400 Miles
©+1.8 Miles
© SAP AG 2009. All rights reserved. / Page 103
Linear Referencing Pattern (LRP)
Marker Location UOM Length UOM
MP1 1 Mile 1 Mile
MP2 2 Mile 1 Mile
MP3 2.95 Mile 0.95 Mile
MP4 3.90 Mile 0.95 Mile
MP5 4.90 Mile 1 Mile
MP6 5.90 Mile 1 Mile
MP7 6.90 Mile 1 Mile
MP8 7.90 Mile 1.2 Mile
MP9 9.1 Mile 1 Mile
Patterns are usually distributed uniformly along the linear element to representhomogeneous distance segments (in some exceptional cases some markers havedifferent lengths).
The patterns are indicated in the same unit of measure used to define the linearasset element (Miles, Kilometers, Meters, etc.).
© SAP AG 2009. All rights reserved. / Page 104
The Linear Data Fields in Work Management
In Work Orders the Linear Data Fields are on the level of the header and on the level of theoperations.On the header level the Linear Data Fields allows to define for the reference object whereexactly the work has to start and/or end and what is the extension/length of the work. Thisallows also to get information about the costs (planned/actual) per unit of length.On the level of operations the Linear Data Fields allows (in addition to the information onheader level) to describe in more detail where each of the activities has to be performed.If the work order is performed for several assets they will be listed in the object list on theheader level. If work is performed especially for one of these assets this one can be assignedto an operation. In this case the Linear Data Fields allows to specify the worklocation/extension particular for this assigned asset on operation level.
The following objects have been enhanced with the Linear Data Fields.Work Order HeaderWork Order OperationWork Order ConfirmationsMaintenance Plan ItemRelevant List Reports
© SAP AG 2009. All rights reserved. / Page 105
Summary - Linear Data Fields and TechnicalObjects in Orders
Work orderheader
operation
operation
operation
technical object
technical object
technical object
technical object
Linear Data Fields
Linear Data Fields
Linear Data Fields
Linear Data Fields
new with LAM
new with LAM
new with LAM
new with LAM
existing
ECC6 EHP4
ECC6 EHP4
ECC6 EHP4
Work Order processing
Note: this is a simplified view on the order and notification structure. It shows only those objects whereLinear Data Fields are assigned. Others like object list, components, settlement rules (in the order) or tasks
and activities (in the notification) are not shown here for simplicity reasons.
© SAP AG 2009. All rights reserved. / Page 106
Inspection and Condition Monitoring
For condition monitoring and inspections information of different characteristics andformats can be entered.This information can be a stream of measured samples for one or several LinearAssets or by capturing specific events that are found during physical inspection.Linear Asset Condition information can be obtained through the use of DiagnosticEquipment or through activities like walkdowns or helicopter surveys where a visualsurvey is carried out and where exceptions are recorded.For Inspection and Condition Monitoring processes the following objects have beenenhanced with the Linear Data Fields:
Notification HeaderNotification ItemMeasurement Point / CounterMeasurement Document
© SAP AG 2009. All rights reserved. / Page 107
Summary - Linear Data Fields and TechnicalObjects in Notifications
Notificationheader
item
item
item
technical object
technical object
technical object
technical object
Linear Data Fields
Linear Data Fields
Linear Data Fields
Linear Data Fields
new with LAM
new with LAM
new with LAM
new with LAM
existing
new with LAM
new with LAM
new with LAM
Notification processing
Note: this is a simplified view on the order and notification structure. It shows only those objects whereLinear Data Fields are assigned. Others like object list, components, settlement rules (in the order) or tasks
and activities (in the notification) are not shown here for simplicity reasons.