UI requirement to include asset bar code ID verification process as part of the first inspections for assets, this should

include verification of existing asset IDs or entering missing asset IDs by usage of Bar code reader or manual entry.
This process step needs to be added to "Update master data required !sset update process"
The frst time an inspection is conducted the inspector/maintainer will be presented
with a pop-up to verify the asset ID maintained on the system is the same asset ID
on the asset. If the asset does not have an ID maintained in the system the user will
have the ability to update the assets record by entering the missing asset ID using
a Bar code reader or by manual entry.
Configurable General Maintenance Task Lists
Definition
! general maintenance tas# list in $hich you, for example, group together all possible operations for
repairing different ob%ect types in a super task list. This means that you do not have to create a separate
general maintenance tas# list for each variant of a technical ob%ect, but that you configure each variant
accordingly.
&ou create object dependencies for the individual operations of the general maintenance tas# list, by
specifying, for example, that the system should only select an operation during maintenance or service
order creation $hen particular characteristic values apply. In addition, you can assign an assembly to the
general maintenance tas# list. If you have entered ob%ect dependencies for the materials in the
corresponding material B'(, the system copies the material components $ith the assigned ob%ect
dependencies into the general maintenance tas# list. This means that you are also able to configure
materials, and define that they are only selected $hen particular characteristic values apply.
Use
)hen maintaining technical ob%ects, it is sometimes the case that tas# lists for maintaining different ob%ect
types only differ from one another by additional, variant*specific operations, and that other$ise, they are
largely identical. In cases such as this, you can use configurable general maintenance tas# lists.
+or example, this may be the case if you $ant to repair production lines that only differ from one another
as regards additional operations that are based on the age or on the modernity of the system. !nother
situation $here you could use configurable general maintenance tas# lists $ould be if you have created
service contracts for ob%ect types that differ from one another based on, for example, the type of motor
concerned for example, for# lift truc# $ith electric engine, for# lift truc# $ith diesel engine".
Configurable General Maintenance Task List for Fork Lift Truck
Operation Object dependency:
elect if t!e type of engine is"""
,hec# electronics -lectric
,hec# $ear and tear of carbon brushes -lectric
,hec# tread depth of tires -lectric, Diesel
,hange hydraulics oil -lectric, Diesel
,hec# tension of lift chain -lectric, Diesel
,hange oil filter Diesel
,hange air filter Diesel
,lean fuel in%ectors Diesel

&ou can use the configurable general maintenance tas# list in .lant (aintenance .(" and ,ustomer
/ervice ,/". 'bserve the follo$ing features for the configuration profile0
Use Features
.(, maintenance order !ssign an ob%ect dependency and a configuration profile to the
general maintenance tas# list.
,/, service order $ith configurable
service product
! configuration profile is assigned to the configurable service
product. +rom this, assign ob%ect dependencies but no separate
configuration profile to the general maintenance tas# list. If,
ho$ever, you still choose to assign ob%ect dependencies, they $ill
be ignored by the system.
,/, service order $ith "normal"
service product
!ssign an ob%ect dependency and a configuration profile to the
general maintenance tas# list.
.( and ,/ !ssign an ob%ect dependency and a configuration profile to the
general maintenance tas# list.
If you assign the general maintenance tas# list in the ,ustomer
/ervice component to a service order $ith a configurable service
product, the configuration of the service product has priority over
the configuration of the general maintenance tas# list.

+or more information on the service product, see ,onfigurable /ervice .roduct.
#ntegration
The configurable general maintenance tas# list integrates the follo$ing components0
,lassification system
1ariant configuration
(aintenance orders or service orders
If you create a maintenance or service order and assign a configurable general maintenance tas# list to it,
the system recogni2es that the general maintenance tas# list is assigned to a configuration profile. It calls
up characteristic valuation and only selects the relevant operations for the order from the super tas# list,
based on the ob%ect dependencies that you specified.
Configuration $rofile
Definition
&ou maintain the configuration parameters for a configurable general maintenance tas# list in the
configuration profile.
The settings that you ma#e here also concern the B'( explosion for the piece of material. In addition, at
least one class, $hose class type allo$s variant configuration, must be assigned to each configuration
profile. The class contains the characteristics that the system proposes for characteristic evaluation $hen
you create a maintenance or service order.
Creation of Configurable General Maintenance Task
Lists
$urpose
)hen maintaining technical ob%ects, it is sometimes the case that tas# lists for maintaining different ob%ect
types only differ from one another by additional, variant*specific operations, and that other$ise, they are
largely identical. In cases such as this, you can use configurable general maintenance tas# lists.
If you create a maintenance or service order and assign a configurable general maintenance tas# list to it,
the system recogni2es that the general maintenance tas# list is assigned to a configuration profile. It calls
up characteristic valuation and only selects the relevant operations for the order from the super tas# list,
based on the ob%ect dependencies that you specified.
$rere%uisites
&ou have created a class in the class system and assigned characteristics to it, for example, the
class "+or# lift truc#" $ith the characteristics "-ngine type", ",onstruction year" and "-xtras". +or
more information, see The ,lassification /ystem.
&ou are familiar $ith the variant configuration see 3ogistics 4eneral" * 1ariant ,onfiguration".
$rocess Flo&
5. &ou create a general maintenance tas# list and enter ob%ect dependencies for the individual
operations.
6. &ou enter a configuration profile for the general maintenance tas# list and assign one or more
classes to the configuration profile.
'esult
&ou can assign the general maintenance tas# list to a maintenance or service order and then select
suitable operations for it. The classes" that you assign to the general maintenance tas# list using the
configuration profile controls" $hich characteristics the system proposes for the characteristic evaluation.
Creating Configurable General Maintenance Task
Lists
$rere%uisites
&ou have created a class in the class system and assigned characteristics to it, for example, the class
"+or# lift truc#" $ith the characteristics "-ngine type", ",onstruction year" and "-xtras". +or more
information, see The ,lassification /ystem.
$rocedure
5. ,hoose Logistics Plant maintenance Planned maintenance Maintenance task lists
Task lists General task lists Create.
The initial screen for creating general maintenance tas# lists is displayed.
+or more information about creating general maintenance tas# lists, see ,reating (aintenance
Tas# 3ists0 .rocess.
6. -nter ob%ect dependencies for the individual operations.
To do this, select the operation to $hich you $ant to assign an ob%ect dependency in the screen
Operation overview, and choose Extras Object dependencies Editor.
The dialog box appears.
7. /elect the relationship type and choose Continue.
The screen for maintaining ob%ect dependencies is displayed.
8. -nter the source text for the ob%ect dependency.
9parent.engine type eq :-lectrical:
The system should only select operations for the engine type "-lectrical"".
+or more information on ob%ect dependencies, see 3ogistics 4eneral" * 1ariant ,onfiguration.
;. /ave the general maintenance tas# list.
In the general maintenance tas# list , you cannot assign ob%ect dependencies directly to
the free material components. !n assignment of ob%ect dependencies to material
components is only possible if you assign a material of the category ssembl! to the
general maintenance tas# list in the tas# list header, and you select the material
components using component selection from the material B'(. The system copies the
ob%ect dependency that is assigned to the components in the bill of material to the
general maintenance tas# list. In this $ay, you are also able to control the configuration of
the material components, and define that the system only selects components for
particular characteristic values for example, material "!ir filter" for engine type "Diesel""
$hen you create a maintenance or service order.
+or more information on material components, see !ssignment of (aterial ,omponents.
'esult
&ou have created a general maintenance tas# list and must no$ create a configuration profile.
&ou can assign the general maintenance tas# list to a maintenance or service order and then
select suitable operations for it. The classes" that you assign to the general maintenance tas# list
using the configuration profile controls" $hich characteristics the system proposes for the
characteristic evaluation.
+or more information, see the /!. documentation PM " Maintenance Orders and PM " #ervice
Management
Creating Config" $rofile for Gen" Maint" Task List
$rere%uisites
&ou have created a general maintenance tas# list see ,reating ,onfigurable 4eneral (aintenance Tas#
3ists".
$rocedure
5. Use the menu bear sequence Logistics Plant maintenance Maintenance task lists and then
one of the follo$ing menu paths0
o Task lists General task lists Con$iguration pro$ile Create
o Environment %ariant con$iguration and then Con$ig. pro$ile Create
! dialog box is displayed, in $hich you can select the required configurable ob%ect.
5. /elect General maintenance task list and choose ,ontinue.
The intial screen for creating configuration profiles is displayed.
By choosing Extras C&ange con$ble.obj., you can change the ob%ect later if required.
7. -nter the name of the general maintenance tas# list that you $ant to create a profile for and
choose Continue.
The .rofile overvie$ screen is displayed.
8. -nter a profile name and a class type by $hich the ob%ect is to be classified, for each profile that
you $ant to create.
The class type must be admissible for the variant configuration. &ou can perform this
setting in the ,ustomi2ing function for the class system.
'. !ssign one or more classes to each profile for the general maintenance tas# list. The class must
be created for the class type that you have specified in the 'vervie$ screen. In this $ay, you
determine $hich characteristics are proposed by the system $hen you assign the configurable
general maintenance tas# list to a service or maintenance order.
To do this, choose Goto Class allocations.
The !ssignment screen for classes is displayed.
(. -nter the class that you $ant to assign to the ob%ect and return to the configuration profile.
). To determine the status of the profile, select Goto Pro$ile detail.
)hen you create the profile, the status is set to *n preparation. &ou can change the status
to +eleased once you have assigned the ob%ect to a class.
<. =eturn to the .rofile overve$ screen.
>. /ave the configuration profile.
+or more information on variant configurations and the creation of configuration profiles, see the
documentation LO " %ariant Con$iguration Guide.
'esult
&ou can assign the general maintenance tas# list to a maintenance or service order and then select
suitable operations for it. The classes" that you assign to the general maintenance tas# list using the
configuration profile, control $hich characteristics the system proposes for the characteristic evaluation.
+or more information on maintenance and service orders, see the documentation PM " Maintenance
Orders and PM " #ervice Management.
Task Lists (C)*G+$M)$'M)TL,
$urpose
(aintenance tas# lists describe a sequence of individual maintenance activities $hich must be performed
repeatedly $ithin a company. Tas# lists are used to standardi2e these recurring $or# sequences and to
plan them more effectively. (any manufacturers deliver their technical ob%ects together $ith maintenance
tas# lists? these tas# lists are, ho$ever, frequently created $ithin the company itself.
!ctivities for a technical ob%ect include for example
Inspections
(aintenance
=epairs
Tas# lists help to reduce the maintenance effort $hen standardi2ed $or# sequences change, for example
as a result of ne$ legal regulations. &ou must carry out the changes at exactly one place in the
corresponding maintenance tas# list. !ll maintenance orders and maintenance items that refer to the
maintenance tas# list automatically receive the actual status of the $or# sequences.
#ntegration
Using maintenance tas# lists, you can reduce the time required to create maintenance orders and
maintenance items as you can refer bac# to the operations and sequences already entered in the
maintenance tas# list.
(oreover, you can include inspection characteristics from the @uality (anagement module in
maintenance tas# lists and if necessary, include the tas# lists in the test equipment management function.
This is advisable, for example, if you $ant to #eep individual data for each piece of test equipment or if
you $ant to have a record of the results history. +or more information, see Test -quipment
(anagement.
Features
&ou can use maintenance tas# lists in the follo$ing areas of .lant (aintenance0
.lanned maintenance
'ngoing maintenance
(aintenance tas# lists contain important information such as the spares and tools required for the $or#
steps or the time required to perform the $or#.
$lanned Maintenance
The term ".lanned maintenance" includes all the maintenance $or# you can plan for the scope of $or#
and deadlines, that is, inspection, maintenance and planned repairs.
In the .( application component, you can also define the intervals at $hich individual $or# steps should
be executed in the tas# list for planned maintenance. &ou assign these tas# lists to a maintenance plan in
maintenance planning. This ensures that only operations in the maintenance order that have been
assigned to the maintenance pac#age due can be copied $hen scheduling $or#. The system creates
maintenance orders $hen a maintenance plan is due.
+or more information, see (aintenance .lanning
Ongoing Maintenance
!ll maintenance $or# that does not come under planned maintenance is classed under ongoing
maintenance.
Tas# lists for ongoing maintenance serve as the basis for a maintenance order and can be used based on
the results of the current inspection.
&ou can also use maintenance tas# lists as a model and aid for capturing data $hen processing
maintenance orders by assigning a tas# list to an order. This considerably reduces the amount of $or#
preparation for maintenance activities.
If, for example, you are creating a maintenance order for a tas# $hose operations have already been
described in detail in a maintenance tas# list, enter only this tas# list and the performance deadlines in the
order. The system $ill copy the individual operations from the maintenance tas# list.
+or further information, see )or# /cheduling $ith (aintenance Tas# 3ists.
&ou can copy operations from tas# lists into an order automatically. +or further information, see )or#list
for Aotifications and !ssigning a Tas# 3ist to a Aotification.
Configurable Maintenance Task Lists
It is also possible to create super tas# lists in $hich you describe all possible operations for maintenance
activities for different ob%ect types. !ccording to requirements, you can configure a suitable variant for a
technical ob%ect from the super tas# list $hich means that you do not have to create your o$n tas# list
every time.
Maintenance Task Lists
Definition
(aintenance tas# lists describe a sequence of individual maintenance activities $hich must be performed
repeatedly $ithin a company.
There are three types of maintenance tas# lists that can be distinguished from one another using
indicators0
-quipment Tas# 3ist
+unctional 3ocation Tas# 3ist
4eneral (aintenance Tas# 3ist
Use
&ou can use all three tas# list types for ongoing and planned maintenance.
If you $ant to use the general maintenance tas# list for planned maintenance you must assign the tas# list
to a maintenance plan or one or more maintenance items. The operations described in the general
maintenance tas# list are performed for all technical ob%ects that you have assigned to the maintenance
item. The operations fall due at the times calculated by the system $hile scheduling the maintenance
plan.
+or more information on maintenance plans, see the documentation .( * (aintenance .lanning.
tructure
&ou can group together all similar maintenance tas# lists for groups. The Tas# list group contains a series
of maintenance tas# lists that describe similar maintenance tas#s, for example, oil changes for cars and
truc#s.
&ou describe the maintenance tas#s to be performed in the individual elements of the maintenance tas#
list. The most important elements are0
'perations
/ub*operations
(aterial ,omponents
(aintenance .ac#ages
.roduction =esourcesBTools
=elationships
Task List Group
Definition
(aintenance tas# lists .( tas# lists" are grouped into tas# list groups. ! tas# list group includes
all maintenance tas# lists $ith similar maintenance flo$s for example, oil changes for cars and
truc#s". Tas# lists $ithin a tas# list group are identified by a group counter.
If you create a maintenance tas# list Equipment Task List, Task List for Functional Location or
General Maintenance Task List" for the first time, the system $ill automatically assign a ne$ group
and the counter C5 to your tas# list.
Use
The tas# list group has more significance for general tas# lists, as they are called up using the
tas# list group number. 4roup numbers for general tas# lists can be assigned either internally or
externally. 4roup numbers for equipment tas# lists and tas# lists for functional locations can only
be assigned internally.
The /!. /ystem treats all maintenance tas# lists $ithin a group as one unit. It is therefore
recommended that you assign general maintenance tas# lists to several small groups. This
considerably reduces the volume of data that must be processed $hen the group is accessed
and has a positive effect on the system response time.

In your company you have created t$o groups for "Inspection" and "(echanical =epairs". The
individual maintenance tas# lists $ithin the group "(echanical =epairs" are identified by the tas#
list counter numbers C5 and C6.

Operation
Definition
&ou can describe the individual maintenance tas#s to be performed in the operations. !n operation
specifies the time, $or# center and other control information required for the maintenance tas#. &ou can
describe ho$ the tas# is to be performed in the operation text.
Use
'perations have the follo$ing tas#s in the .( component0
Determination of capacity requirements
/pecification of $hether a tas# should be carried out internally internal processing" or externally
external processing"
(aintenance of status
Determination of deadlines on the operational level
/pecification of the required spare parts and resources for example, special tools"
Determination of flo$ in tas# completion through relationships bet$een operations
&ou can assign service pac#ages to both #inds of operations if this is allo$ed by the control #ey you have
entered. Using service pac#ages enables you to
.lan services in all dimensions
Dointly plan services to be performed in different dimensions
Define services uniformly
/tructure services in an unlimited number of levels
(a#e basic agreements
!gree on conditions
Use service catalogs
Better describe $or# content
Control -ey
The control #ey specifies $hich operations should be performed. &ou can specify the follo$ing, for
example0
/cheduling
,onfirmation
/ettlement
-xternal processing
.rinting
,osting
/ervice specifications maintenance
&ou define the operation type using a control #ey. The control #ey specifies0
'peration type, that is, $hether internally or externally processed
The business functions to be performed in the operation, for example, $hether a purchase order
$ill be created for the operation
Eo$ the operation is handled $hile it is being processed, for example, $hether it $ill be ta#en
into account in costing or $hether it should be printed and confirmed
+or each operation it is possible to create data for both internal and external processing.
&ou must first assign a control #ey to be able to decide $hether the operation should be processed
internally or externally. &ou can enter the control #ey in the Operation overview screen and the detail
screens for the individual operations.
#ntegration
It is possible that you are not able to over$rite certain values that the system copies into the tas# list.
These values originate from the master record of the $or# center you have entered in the tas# list, and
are mar#ed $ith a reference indicator. This indicator sho$s that these values are obligatory and cannot
be over$ritten at any point for example, in a tas# list or maintenance order" $here they refer to the $or#
center.
)'=F '=D-=0
'esults *nalysis -ey
Fey that defines the valuation of the order during period*end closing.
Use
Eo$ the results analysis key is used depends on the nature of the order.
+or orders $ith revenue internal orders, sales orders, and projects", the results analysis #ey
determines ho$ results analysis is carried out.
=esults analysis is recommended in the follo$ing situations0
o )hen you are using a non.aluated sales order stock or non.aluated project stock and
you $ant to valuate the inventories at the end of the period
o )hen you are using a .aluated sales order stock or .aluated project stock and $ant to
valuate goods that have been delivered but not yet invoiced, or $hen you $ant to create
reserves automatically
+or orders $ithout reference to a sales order item or /0 element, the results analysis #ey
determines ho$ the &ork in process is calculated.
The production type can be ma#e*to*stoc# or mass production on the basis of sales orders. The $or#
in process is calculated at the level of the production order, process order, or product cost
collector.
+or capital in.estment measures, the results analysis #ey determines ho$ the system calculates the
values to be capitali2ed.
12amples
+or orders $ith revenue, costs may be incurred before any revenue is received. If you are using a nonvaluated
sales order stoc#, results analysis enables you to report the costs as $or# in process. !fter the first revenue
has been posted, you can calculate the cost of sales. If the calculated cost of sales is greater than the actual
costs incurred to date, the system creates reser.es for unreali3ed costs in the amount of the difference.
Ao revenue is posted in ,' for orders $ithout reference to a sales order item. -ach goods receipt for these
orders is valuated. The &ork in process for these orders can be calculated $ith t$o different methods0
)or# in process at actual costs
The actual costs for production orders and process orders for $hich no delivery has ta#en place are
reported as $or# in process. !fter a partial delivery, the difference bet$een the debit of the order $ith
actual costs and the credit of the order from goods receipts is reported as $or# in process. )hen the
order is complete, this $or# in process is canceled. The difference bet$een the debit and credit of the
order is then interpreted by the system as a variance.
In $roduct Cost by Order, the $or# in process is usually valuated at actual costs.
! requirement for the valuation of $or# in process at actual costs is that the default rule $$4 full
settlement" must be specified in the order.
)or# in process at target costs
! confirmation is made for each operation or at certain reporting points. The system uses the
confirmations to determine the quantity of $or# in process. This quantity is valuated using the strategy
sequence specified in the .aluation .ariant for &ork in process and scrap.
In $roduct Cost by $eriod, the $or# in process is al$ays valuated at target costs.
! requirement for the valuation of $or# in process at target costs is that the default rule $$5 periodic
settlement" must be specified in the order.
/ee also0 C!eck default .alues for order types
Dependencies
The control parameters for results analysis, for the calculation of $or# in process, and for the calculation of the
values to be capitali2ed are selected through the results analysis #ey in the order and a results analysis
.ersion. If you have not specified a results analysis #ey in the order, the order $ill not be included in the
calculation of $or# in process during period*end closing.
The control parameters for the valuation of $or# in process in .roduct ,ost by .eriod are defined in
,ustomi2ing for Product Cost b! Period.
/ee also0 Define .aluation .ariant for /#$ and scrap (target costs,
Costing .ariant for actual costs
Fey that specifies the costing .ariant that is used to determine the actual costs.
The costing variant refers to a .aluation .ariant. The valuation variant determines
$hat activity prices are used from cost center accounting to evaluate the confirmed internal activities in
simultaneous costing
$hich costing s!eet is proposed for calculating the o.er!eads in the order production cost
collector or production order.
Costing .ariant for planned costs
Fey that specifies $hich costing .ariant is used to determine the planned costs.
The costing variant refers to a .aluation .ariant. The valuation variant
combines all the parameters for evaluating materials, internal activities and external activities in
preliminary costing
determines $hich calculation schema is proposed for determining the overheads for production* and
process orders
O.er!ead key
The overhead #ey is used to determine order*specific or material*related overhead rates.
$rocedure
Orders6 cost object #Ds and base planning objects0 To be able to calculate an overhead percentage rate
using the overhead #ey you must0
!ssign a costing sheet to your order or cost ob%ect ID or base planning ob%ect.
Use the field "'verhead #ey" in the overhead rates in the costing sheet
+or product costing6 production orders and run sc!edule !eaders0
To be able to apply overhead using the overhead #ey you must0
!ssign a costing sheet to your order or to the valuation variant for the cost estimate
Use the field "'verhead #ey" in the overhead rates in the costing sheet
!ssign the overhead #ey to an overhead group
-nter this overhead group in the master record of the material being used.
12amples
The overhead amounts depend on the plant and the overhead #ey. The overhead depends primarily on the
overhead #ey. If an overhead #ey is not maintained for the material or the order, overhead is to be determined
in relation to the plant.
Define a costing sheet that points to t$o condition tables. In the first table, the overhead amount depends on
the overhead #ey. In the second table, the overhead amount depends on the plant. !n access sequence
determines $hich conditions have priority.
Dependencies
The overhead #ey is also used as a selection criterion for the determination of the templates for !ctivity*Based
,osting. If a process template is assigned to an overhead #ey and costing sheet of an order, process costs are
determined for the order.
)hen you change the overhead #ey or the costing sheet, the system uses another process template, if
required.
Costing !eet
,ontrols the calculation of o.er!ead.
Use
&ou must store one costing s!eet for each ob%ect for $hich the =B7 /ystem is to determine overhead costs.
Dependencies
+or orders, you enter the costing sheet in the order master record.
o +or o.er!ead cost orders the costing sheet can be defaulted through a model order.
o +or CO production orders &it!out %uantity structure the costing sheet can be defaulted
through a planning profile.
o +or production orders, process orders, produc cost collectors, maintenance orders,
regular maintenance orders and ser.ice orders the costing sheet is defaulted through a
valuation variant.
The valuation variant is stored in the costing .ariant. &ou can store the costing variant as
default value per order type and plant.
+or cost centers you enter the costing sheet in the master data.
+or buiness processes you enter the costing sheet in the master data.
+or projects you enter the costing sheet in the pro%ect profile.
+or materials the =B7 /ystem selects the costing sheet through the valuation variant.
+or base ob%ect plannings, enter the costing sheet in the master data of the costing sheet.
+or cost object #Ds the costing sheet is defaulted through the cost ob%ect profile.
+or cost and revenue carrying sales document items the costing sheet is defaulted through the
requirements class.
tatus $rofile
Fey that identifies a status profile.
$riority Type
Fey that determines $hich priorities are allo$ed for a notification type.
Order Category #ndicator $lant Maintenance
.arameter used for internal control of the order
.ossible variations0 see domain fixed values
$rofile rels"7 grap!ic + General order
.rofile that provides default data for the follo$ing data groups0
Fey $ord ID
User*specific fields
,alculation #ey
4raphic data
8ote0
This profile is maintained by system administration for each entered user, plant and order type using
the ,ustomi2ing function.
12ternal procurement profile
.rofile that provides certain default data for processing the e2ternal acti.ities requested.
Dependencies
This profile is maintained by systems administration for each entered plant and order type, using the
,ustomi2ing function.
In the application you can use the user preconfigurations of the order to override this parameter for each user.