Functions and Settings for Order Types in SAP PM / Asset Management

In this section, I shall define the maintenance order types allowed and the technical dependencies for the
individual order types.

Guide Lines

When considering how many order types to define for maintaining processing, you should first use the
business significance of the maintenance order type as a reference.

It is generally best to use separate order types for different business tasks (capital spending orders, repair
orders, inspection orders, replacements and so on) since many technical controls depend on the order
type. As a result, settings dependent on the order type can be used effectively during analyses to make
commercially useful selections via the individual order types.

However, you should not set up a separate order type for every conceivable operation. The maintenance
activity types are available for the fine tuning of maintenance tasks. For each order type you can define
the maintenance activities allowed. This then provides another level on which you can differentiate
between the possible maintenance tasks.

Proceed to FIORI Launchpad as this is the UI5 which is primarily meant from Public , Private & Hybrid
environments cloud.

SPRO >> Ref. IMG

Plant Maintenance and Customer Service

Maintenance and Service Processing

Maintenance and Service Orders
Functions and Settings for Order Types

Configure Order Types

In this step, I must set up order types for Plant Maintenance and Customer Service.
In addition to the business reasons for configuring several order types, there are also technical controls
which depend on the order type and may require the creation of different order types.
The following technical controls depend on the order type:
• Number ranges
• Settlement proposal or account assignment rule
• Default values for control key
• Permitted maintenance activity types and default values
• Permitted order types for each maintenance planning plant
• Increment when assigning the operation numbers
• Costing parameters
• Residence period of the order after completion (residence time)
• Default values for the confirmation process
• Presetting for the reference object screen
• Budget profile
The budget profile enables you to define budgets for individual orders. You should also activate the funds
availability check. This allows you to monitor order-related budgets without using the project system.
The settings for budget profiles and activating funds monitoring are made in the Customizing for the cost
accounting system.

• Immediate order release

If you flag this field, the system tries to release orders generated from maintenance notifications, service
notifications, or maintenance plans immediately.
For orders which have been generated manually, the order must be released by the user.
If the system cannot release an order automatically, for example, because permits are missing, the order
automatically obtains the status Release refused.
The following checks are performed when orders are released automatically:
o Availability check of components
o Permits
o Settlement rule
o User status (whether user status allows the release)
o Customer exit
Example
You want to assign certain activities to external companies. For these activities, the account assignment
is usually the same and you use the same maintenance activity type for these tasks.
In this case, it is advisable to create a separate order type for these activities, since you can save resources
by using the layout for the standard values.
You can also simply select these orders using the order type.

Special note for service orders

Service orders for which billing is resource-related without reference to a sales document (contract, sales
order) cannot have a settlement structure that allows an account assignment to other objects as a G/L
account or as a profitability segment. Otherwise, revenue postings cannot be performed on the service
order.
When maintaining the cost accounting parameters, you can only flag the "Revenue postings" indicator for
order types which are to be used for service processing.

Presetting for the reference object screen

You can continue to choose a screen for maintaining order header data.
The screens offered contain different data fields for the reference object of the maintenance order. The
screen provided here can still be changed by the user when creating an order.
If you do not enter a value for a screen here, the system uses a standard screen, which enables the entry
of:
• Functional location
• Equipment
• Assembly
•
You can therefore define for each order type which screen should be used for the reference object. This
is always advisable if, for example, you only work with pieces of equipment, functional locations, or with
another special reference object.
However, this setting is only a default value, which each user can change using their own user-specific
settings.
The reference object can also be changed during a transaction. However, the new reference object screen
must contain the reference object fields already entered. Otherwise, you receive an error message.
By deleting the reference object fields, you can replace any reference object screen with another during
order processing.
Create a new maintenance Order type PMBQ- Maintenance order-BUHQ
CO Partner Update
In allocations within CO, a totals record is usually produced for each sender-receiver combination. In
orders, you can influence this process in the following ways:
• "Not active"
In allocations between an order and another object, no totals record is produced for the
relationship with the order.
• "Partly active"
In allocations between orders, totals records are produced for each combination.
In allocations which are not directly between two orders, such as activity allocations between cost
centers and orders), no totals record for the relationships with the order is produced in the other
object.
• "Active"
In allocations between an order and another object, a totals record is always produced for the
combination including the order.
Use
Use this indicate to reduce the number of totals records and thus the storage capacity needed in
the database.
Example
A cost center supplies services to many small orders. For those working with the cost center, the
information on which order has received how much is of little interest. If you set the partner
update in the order type for the small orders to "Not active" or "Partly active", the system
produces a cumulative totals record covering all the small orders. The partner information
remains intact in orders, if you set the CO partner update to "partially active".
Identifier "Revenue Posting Allowed"
This indicator controls whether revenues can be posted to an order.
Orders with revenues can be settled in the following way:
• Costs: Settlement to any receiver
• Revenues: Settlement to G/L account, profitability segment, sales order, billing element and other
orders with revenues.
You set the indicator in the order type. It is copied from the order type when you create new orders. Order
that already exist are not changed when you set this indicator at a later date in the order type.
Settlement Profile
This field contains the settlement profile. You can copy the settlement profile into the settlement rule to
change it, for orders from the order type, and WBS elements from the project profile.

Select settlement profile- 40

Budget Profile
The budget profile brings together the control parameters for budgeting.
Note: You should not maintain the budget profile if you use the Budget Control System (BCS).
Use
You can control budgeting with the following parameters:
• Time horizon
o Period into the past for which budgeting is possible
o Period into the future for which budgeting is possible
o Budgeting start year
o Budgeting of total/annual values
• Format
o What value is displayed as well as the budget, when you access the function
o Decimal places and scaling factor as default values
• Availability control (Project System, Funds Management)
o Of annual/total budget
o Of releases
• Currency translation
o Exchange rate type
o Value date
Dependencies
This description applies only in part for budget profiles in Cost Center Accounting (see the corresponding
documentation on the detailed screen for Cost Center Accounting).

Definition: object class

Controlling (CO)
The object class categorizes Controlling objects according to their business function and enables you to
analyze cost flows within Controlling from different business perspectives.
The following object classes are available:
 • Overhead
• Production
• Investment
• Profitability analysis and sales
While certain object types automatically belong to a particular class (for example, cost centers belong to
the "Overhead" class), others need to be explicitly assigned to an object class in their master record (this
is the case with internal orders and work breakdown structure elements, for example).
In addition to the functional area, the object class is required to determine or explain certain values in the
external accounting components.
Example
The balance of all objects in the Production class is categorized as Work in Process (WIP).
Marketing (CRM-MKT)
Groups together a marketing project and all of its tasks or elements. For example, object class CP
(consumer promotion) could contain the task CPT (consumer promotion task)

Residence Time 1 (Calendar Months)

Reorganizing an object (e.g. order, project) normally requires three steps:
1. Setting the delete flag (can be reset)
2. Setting the final deletion indicator (cannot be reset)
3. Reorganizing (writing the object to a sequential dataset and physically deleting it from the
system)
Residence time 1 determines the time interval (in calendar months) that must elapse between setting
the delete flag (step 1) and setting the deletion indicator (step 2).
Set "Release Immediately" Indicator
Orders of this order type are automatically assigned "Released" status when they are created. This status
allows nearly all business transactions.
Dependencies
You can only use the indicator for orders that use general SAP status management.
Maintenance orders and service orders are released automatically only if they are created from
maintenance calls, from a background notification, or from a sales order.
Service orders are also released immediately if they are created from a sales document item.
Scenario or Sub screen Category
Indicates which sub screen for the notification header, notification object, maintenance order, service
order or partner is involved.
Save it-Transport request generated

Now create Mintainanace PM order type PMBQ for verification

Header Data
Operations

Release Work order

Schedule work order

Save work order - Order 2000000 saved with notification 100002300

Conclusion:
• The PMBQ document type is now ready for use in the system. The final step is to ensure that all
stakeholders, such as maintenance planners and technicians, are familiar with the new
document type and its functionality.
• If necessary, adjust the maintenance order workflow to accommodate the unique characteristics
of PMBQ, ensuring the document type serves the desired purpose in maintenance operations
efficiently.
Once this configuration and testing are completed, the PMBQ document type can be used to process
maintenance orders effectively in SAP PM.

THNAK YOU