operation account assignment in sap pm

Welcome, Login to your account.

Recover your password.

A password will be e-mailed to you.

Operation Level Costing – Part 1

Hey there…!!! This is Harikrishna Anumandla. Am working as an EAM Consultant. I want to share my recent experience on Operation Level Costing for the community. Purpose of this blog is to leverage operation level costing insights to drive innovative new business models.

This Functionality is primarily used to track the costs at Operation Level. Earlier to this, there used to be a single Accounting Structure for the whole Order which would result in exponential growth of Maintenance Orders. Most of the times, we may create a separate order for maintenance work just due to the fact that work order need to be settled to a single costing object.

Therefore, by activating OLC Business Function( LOG_EAM_OLC ) you can assign more than one Technical Objects for every operation. Each Operation can possibly have different Account Assignments, Settlement Rules which could eliminate creating multiple work orders.Further Total costs of the work order can breakdown to granular level.

This Functionality is available from SAP ECC 6.0 EHP 5. Operation Level Costing can be activated per Order Type and Plant. However, this functionality cannot be supported for Refurbishment and Investment orders.

Plant Maintenance and Customer Service – Maintenance and Service Orders – Functions and Setting for Order Types – Costs at Operation Level

Once you activate OLC to any order type, and create a new order then System Status “ACAS” Activity Account assignment is defaulted. With the Order Operation Account Assignment function, following account assignment information is available at each operation.

• Costing Sheet
• Overhead key
• Profit Center
• Maintenance Activity Type &
• WBS Elements.
• Functional Area (This field is used when Funds Management is Active)

For Order Confirmations, system updates the actual costs to the cost objects of the order operations.

There can be a possibility of integrating PM with PS by tying operation to a WBS Element. .System can consider order operations as the account assignment objects for the posting of Finance, Controlling and Material Management. While posting orders as account assignments in MM, FI & CO, the order number & operation number in the coding block become Active.

With OLC Activation, Settlement Rule is no more active on Order Header Level. So, you have Settlement Rule for each operation. We have two options for the Settlement Rules.

• With Default
• Without Default

System determines the Plan costs and Actual Costs at the header level from the total costs for all operations.

IW40N Report –

You can use this report to display a cost summary for each operation for one or more maintenance order(s). Beside displaying costs for Operation Level Costed orders, the report can also display costs of Header Costed orders.

Please share your comments or thoughts for further improvement.

Thanks for passing through my blog.

Would you like to access Full Article?

If you are already a member in this website, Please Click here to login If you are not yet a member, Please Click here to Sign up

New NetWeaver Information at SAP.com

Very helpfull.

User Rating: Be the first one !

SAP WM- Process, Functionality, Scope, Benefits, Advantages, Disadvantage-Complete Reference-Part 4

SAP TechEd Las Vegas – Day Three (Goat Day)

Operation wise cost in Work Order – Without LOG_EAM_OLC

SAP EAM – FICO Integration

AMC Process in Plant Maintenance

LSMW for Master Data upload Simple Explanation (Part – 3)

Your email address will not be published.

Save my name, email, and website in this browser for the next time I comment.

Configuring Orders and Work Packs

After completing this lesson, you will be able to:

• Configure general order parameters
• Configure procurement objects
• Configure workflows
• Configure phase model maintenance settings
• Configure work packs

Maintenance Order & Work Packs Overview

Maintenance Orders

The Maintenance order is used to plan, execute, and control maintenance on technical assets (such as functional locations and equipments). The maintenance order is created either as a result of a malfunction on a technical asset or to carry out preventive maintenance (planned maintenance).

Orders form an important part of the detailed planning of tasks and their accompanying documentation in Maintenance Management. The technician on site must execute tasks at a technical object. For this, materials, utilities and staff must be planned and costs estimated. The order supports you with these tasks, since it primarily contains data for planning and executing tasks that must be performed at the technical object in question.

Maintenance Order Type

Maintenance orders are classified by their order type. The order type represents a specific business process because it determines the realization and subsequent processing options of individual orders. This is also why you cannot change the order type of the maintenance order retrospectively.

A key differentiators between the available maintenance processes is the phase model, which structures the end-to-end maintenance process into individual phases and sub-phases. Only some order types support processing according to phases. In the other business processes, the system status of the maintenance order describes its current process step.

• Reactive Maintenance
• Proactive Maintenance
• Improvement Maintenance
• Operational/Overhead Maintenance

During the execution of scheduled maintenance work, the maintenance supervisor needs to plan and print job relevant output forms for one or more maintenance orders that need to be executed. These forms need to be handed over to the maintenance technicians for execution of the job. A work pack is created by the Maintenance Planner or Maintenance Supervisor to club these orders into one package based on grouping criterion.

For work pack to be successfully created for maintenance order operations with an active phase model, the system status must be DSPT (Dispatched), for maintenance order operations without the phase model, the system status must be REL (Released)

Some work pack grouping criteria are delivered by default. You can use the following work pack configurations:

Define Grouping Criteria for Work packs: You can create grouping criteria for generating job packs in a work pack and for managing the output based on work packs.

Assign Grouping Criteria to Work Pack Type: You have the option to choose and assign grouping criteria to work pack types.

Maintenance Activity Type Configuration

Using this configuration activity, you can define maintenance activity types to classify maintenance order. In this step, you determine the allowed maintenance activity types. Check the maintenance activities of the standard system and define new ones, if necessary.

Recommendation

In collaboration with your maintenance controlling, define the level of detail of your maintenance tasks from the point of view of task processing and from the point of view of cost follow-up for the maintenance history. The maintenance activity types are stored in the header of each maintenance order. The maintenance activity types are used in the PM Information System as a grouping element for maintenance orders. For example, cost evaluations in the PM Information System can be performed using maintenance activity types. The maintenance activity types must not be confused with activities in the CO system.

It is optional to configure this activity.

Default Values for Maintenance Activity Type for Each Order Type

Using this configuration activity, you can assign a default maintenance activity type to an order type. The activity is then proposed during order processing.

It is Optional to configure this

Assign Valid Maintenance Activity Types to Maintenance Order Types

Using this configuration activity, you assign a maintenance activity type to a maintenance order type. You can allocate the corresponding maintenance activities to the PM and CS order types.

For example, if you have created an order type for modification tasks, in this step you can now define that only the maintenance activity type MODIFICATION are allowed for modification tasks. All other activity types must not be allowed for this special order type.

It is Optional to configure this.

Order Parameter Control Configuation

Maintain value categories.

In this step, you define value categories. Value categories are intervals for cost elements and are required to update the Plant Maintenance Information System and the Customer Service Information System.

For performance reasons, it is advisable to group together cost elements into value categories. This reduces the volume of data. If you still want to create value categories according to the cost elements, then you can generate the value categories automatically.

Quantities are only updated in the order if you have assigned a unit of measure to the value category.

• Define a key and description for the value category.
• If you want to evaluate quantities in the order, assign a unit of measure to the value category.

Assign Cost Elements to Value Categories

In this section, you define a cost element group as a value category.

If you subsequently change value categories, you have to restructure the files PMCO and PMCOQT . For restructuring, you use the program RIPMCO00 . It is also possible to change the value categories if records have already been placed in the files.

In addition, you must restructure the info structures in the Plant Maintenance Information System if you are updating cost and quantity key figures based on value categories.

You can restructure the information structures using report RIPMS001 .

• Choose a value category and call up the detail screen.
• Define a cost element group as a value category.

Define Default Values for Value Categories

Allows you to define default values for the value categories for the entry of costs.

In this step, you can define default values for the value categories for the entry of costs.

This setting applies to the creation of cost estimates in orders.

To ensure the comparability of the cost structures, you should use the same cost structures (value categories) as for orders performed in the SAP System.

Order Parameter Configuration

Define change documents, collective purchase requisition, mrp relevance.

In this activity, you can define:

• Whether just one purchase requisition (collective purchase requisition) should be generated for external material and operations for each order.
• Whether reservations or purchase requisitions relevant to materials planning should be generated when an order is created or only when the order is released.
• If you do not flag the CollctveRequstn (collective purchase requisition) field, an internal purchase requisition with an item is generated for each external operation and external material.
• You do not select the field Reservation/Purchase Requisition. As a result, purchase requisitions are only generated when the order is released, and reservations only become relevant to materials planning once the order has been released.

It is Optional to configure this activity

Define Order Parameters for Rework Analysis

The Order History time frame can be configured in the activity for rework analysis. You can maintain this time frame less than or equal to 30 days. In this configuration step you can additionally maintain the Order types and Maintenance Activity types as a criteria to determine rework orders.

The rework analysis further considers the following criteria:

Matching technical object between orders

Matching scope items specified in the planning bucket

Previous matching orders are technically complete

Default Value Profiles for External Procurement

Using this activity you can define a profile for external service and material procurement. Use default values such as purchasing organization, purchasing group, cost element, and material group.

In this step, you define the profiles for external procurement of services and materials. In the external processing profile, you can store default values to generate purchase requisitions from maintenance or service orders. In each profile, you can store a default value for the following values:

Cost element account

Purchasing organization

Purchasing group

Material group

During external processing, a distinction is made between the external procurement of materials and the allocation of complete order operations to vendors. Both of these procurement processes generally require different data for purchasing: for example, different purchasing groups or different cost element accounts. Therefore, you must also define different profiles for them. For example:

External processing or external assignment of complete order operations.

Procurement of materials (material profile) In a further step, you can assign two profiles to each user.

It is Recommended to configure this activity.

Service Entry Sheets Use Configuration

Approval for service entry sheet.

When setting up the system for the overall business process with regards to the approval of a service entry sheet, a BPC expert can configure the following settings:

• Configure the type of the message which will be raised in the case that the responsible person has not been entered into the maintenance order
• Introduce a workflow for the approval of the service entry sheet which has been initiated from the planned work of the maintenance order, i.e. a lean service has been entered into a maintenance order operation.

A user assigned to the role SAP_BR_BPC_EXPERT is authorized to launch application Manager Your Solution .

In order to determine the appropriated message type, please launch the following configuration item:

• Application Area: Asset Management
• Sub Application: Maintenance Management
• Message Control

By default, a warning message would be raised if an operation including a lean service is going to be dispatched, but the responsible person has not been entered into the maintenance order header.

You might consider changing this message type to E so that an error would be raised in the case that the responsible person in the maintenance order has not been entered yet.

Finally, when the service entry sheet has been submitted for approval, the responsible person should be determined in the maintenance order. To prevent the missing information in the maintenance order, the blue print of your business process could define raising an error message.

The following configurations are required so that the responsible person in the maintenance order will receive the approval request:

• Assign Account Assignment Category e.g. Maintenance Order
• Assign Role e.g. Person Responsible for Maintenance Order

Introducing both configuration options are the main enhancements to enable the maintenance management process flow into the approval process of a submitted service entry sheet.

Maintenance Order Workflow Activation

Using this activity you can activate the flexible workflow for maintenance orders.

The flexible workflow allows you to use either the automatic one-step or even, multi-step approval. You can use the app Manage Workflows for Maintenance Orders to define start conditions such as the planning plant, planner group, activity type, or the order type of the maintenance order. This app also provides several options for determining the approver, such as the approval by the manager, or approval by the responsible cost center. Alternatively, you can enter a specific user as the approver.

If you have defined several workflows, the start conditions are checked in the order you have defined in the app Manage Workflows for Maintenance Orders . As soon as the start conditions for a workflow are met, this workflow is used. This ensures that only one workflow in the list of your defined workflows is started, even if several workflows have matching start conditions.

To configure the flexible workflow, follow these steps:

• Using this activity you can activate flexible workflow for a combination of maintenance order type and planning plant. If the flexible workflow is not activated for a combination of order type and planning plant, you can release the work order without triggering any workflow.
• Set up the flexible workflow rules using the app Manage Workflows for Maintenance Orders .

Set Up Flexible Workflow Rules

To set up the flexible workflow rule, follow these steps:

In the launchpad, open the app Manage Workflows for Maintenance Orders .

Choose Add to add a new workflow.

You must enter a name for the new workflow. In addition, you can provide a description.

In the section Preconditions , you can define the start conditions for your workflow, for example, in the following way:

In the section Preconditions , select Maintenance order type is from the drop-down list in the app, and enter YA01 .

From the drop-down list, select Maintenance plant of the maintenance order is and enter the required value.

From the drop-down list, select Total planned cost is greater than or equal to and add the desired values for New Value and Currency .

In the section Step Sequence , choose Add . In the drop-down list of the field Type , choose Approve Maintenance Order to define the approver of the workflow.

In the section Recipients , you can choose the desired agent determination rule or you can add the user ID of a specific user.

Choose Add to add these entries and return to the workflow definition screen.

Choose Save to add this workflow to the list of available workflows.

In the list of workflows, ensure that this workflow has the status Active .

Phase Model Maintenance Configuration

Define phase control code for maintenance orders.

Allows you to define phase control codes for maintenance orders. You always configure phase control codes for a combination of order type and entity. This means that you can define phase control codes differently for the order header and order operation of the same order type.

Phase control code allows you to control the transition of phases. If you activate a phase control code to block a phase for a maintenance order, the system will not allow you to transition to this phase until you have deactivated the phase control code. Phase control codes can be activated for order headers and operations.

Configure Phase Control Codes

To configure phase control codes, follow these steps:

• Select the entity (order header or order operation) for which you plan to define the phase control code
• Select the order type and define the phase control code. For each phase control code, you can indicate whether the phase control code has to be activated automatically when an order is created. You can also set the authentication key. Only the users with the authentication key can activate or deactivate a phase control code.

You can indicate whether the phase control code is still valid (Valid), Will no longer be used in future (Deprecated) or is an invalid entry No longer valid

• A valid phase control code can be used without any restrictions
• A deprecated phase control code is still displayed in the value help and still can be activated and deactivated. If the user selects this phase control code and wants to activate it, the system issues a warning message
• A phase control code that is no longer valid cannot be activated. This means that the user cannot select invalid phase control codes from the value help in any apps that allow the activation of phase control codes (for example, in the Change Maintenance Order app). However, an invalid phase control code can still be deactivated. Note that invalid phase control codes can be selected from the value help and displayed in apps that provide a list view. This allows you to use invalid phase control codes as a search and filter criterion
• For a phase control code, you can define the phase and sub-phase that needs to be blocked. This will block the maintenance order or operation from moving to the phase and sub-phase when the phase control code is activated. If the phase control code is not activated automatically at the order creation, you can also define the phase where the phase control code should be automatically activated.
• Depending on the phase control key, phase, and sub-phase that you selected for a phase control code, all the system statuses derived by the system are shown as references. If the check-box is selected, it indicates that the system status was automatically created. Additionally, you can also add or remove a system status. This helps you to adjust the system status for a phase control code

Define Authorization Keys

Authorization Keys can be configured to define users are allowed/authorized to change and adjust the phase control codes.

Authorization Keys need to be defined before they can be added to a Phase Control Code in the definition of the Phase Control Codes.

Assign Entities to Order Types

Select the node Assign Entities to Order Types .

Click on New Entries .

Select the Order Type for which you want to define phase control code.

Select the Entity – ORI (Order Header) or OVG (Order Operation).

Define Phase Control Codes

Select the node Define Phase Control Codes and click on New Entries .

Define a Phase Control Code .

Set the Auto flag to Yes if you want to apply the phase control code automatically when the order is created.

Defined Authorization Keys can be added to the Phase Control Codes.

Save the entries.

Define Phase Controls

Select the node Define Phase Controls .

Choose Control Key Block .

Choose the phase and subphase you want to block.

Adjust System Status

System Statuses can be configured to control the changes of System Statuses. The System Status can be configured so that no transaction can be executed which would result in a change of System Status.

Phase control codes - enhancements

The processing of an order header or operation can be influenced by activating a phase control code so that the transition into the next subphase is blocked. From a technical perspective, a business transaction such as technical completion is triggered against the order header. An active phase control code would block the execution of the appropriated business transaction that would lead to the technical completion. Since the technical completion system status could not be set, the order header remains in the current subphase and will not enter the subphase for technical completion.

Not all phase control codes have been configured to block a business transaction so that those phase control codes will not control the processing of an order header or operation at all. Instead, those phase control codes are just used as a flag to highlight a custom specific information.

A new authorization object has been introduced to control the processing of phase control codes. When configuring a new role, an administrator can issue the appropriated permissions.

For BAdI implementation in the context of releasing a reactive maintenance order consider the following topics:

• The standard reactive maintenance order has been introduced with CE 2011 and this order covers the regular reactive maintenance work. Following the standard process, each reactive maintenance order has to be submitted for approval and the approval has to be issued before releasing this order.
• In the case of an emergency, an order of type reactive maintenance order is generated automatically, but this order will skip certain phases such as the approval phase and the release of this order is triggered automatically.
• In the case that an emergency order cannot be released at all, the entire business process of the emergency case will not be initiated. Hence, the corresponding reactive notification and order will be generated due to a failure message that is shown to the user who would like to initiate this process.
• The custom BAdI implementation should be used to activate a phase control code for the standard reactive maintenance order that will block the order release.

Here are some examples of customers use cases that can be fulfilled by a BAdI implementation:

• For certain technical objects, a permit to work needs to be introduced to prevent the uncontrolled execution of work
• An approval needs to be issued for emergency orders to enable maintenance planner to trigger technical completion of those orders
• Once a maintenance order has been released, the business completion of an order could be triggered before this order has been technically completed.

Consider the following issues regarding OData APIs:

• Starting with CE 2111, an OData API was provided to create an update a maintenance order
• Starting with CE 2202, an OData API is provided to read, activate or deactivate phase control codes on order header or operation.

Define Approval Settings for Maintenance Orders

Allows you to define a combination of maintenance order type and planning plant for approval of maintenance orders.

In this configuration step, you can define if approval is required for a combination of maintenance order type and planning plant. This allows you to release a maintenance order after approval or without approval depending on your requirement.

This is an Optional configuration activity

The flexible workflow allows you to use either the automatic one-step or even, multi-step approval. You can use the App Manage Workflows for Maintenance Orders to define start conditions such as the planning plant, planner group, activity type, or the order type of the maintenance order. This app also provides several options for determining the Approver, such as the approval by the manager, or approval by the responsible cost center. Alternatively, you can enter a specific user as the Approver.

If you have defined several workflows, the start conditions are checked in the order you have defined in the App Manage Workflows for Maintenance Orders . As soon as the start conditions for a workflow are met, this workflow is used. This ensures that only one workflow in the list of your defined workflows is started, even if several workflows have matching start conditions.

Define Assignment Rules for Procurement Milestones

Define custom rules for monitoring procurement milestones and change the default warning period for the milestone due date.

In this activity, you can change the default settings that determine how the system monitors procurement milestones in the relevant SAP Fiori apps for Maintenance Management:

• You can define custom rules to determine which procurement milestones are monitored for a combination of maintenance order type, procurement demand category, maintenance plant, maintenance planning plant, and material group
• You can change the default warning period for the milestone due date. The warning period specifies the time period between the date on which a milestone becomes due and the date on which the system starts to display the procurement status as a warning. By default, the warning period is two days before the milestone due date

Standard Settings

By default, the table in this activity is empty and the system is pre-configured to monitor the following procurement milestones for all maintenance order types, maintenance planning plants, maintenance plants, and material groups:

Milestone Monitoring

This is an Optional activity

Work Pack Configuration

A work pack consists of a list of job packs in which the system can output together and the work order operations (jobs) belonging to the corresponding job packs. Work packs allow you to include multiple output types and leverage support for print and email channels for the output. When you create a work pack, you can select the work pack type and grouping criteria for the work pack and decide whether you want to include operations that are already included in other work pack

Define Grouping Criteria for Work Packs

Create grouping criteria for work packs and work pack items for the purposes of work pack output management.

To create new grouping criteria:

• Choose New Entries
• Enter the ID (four alphanumeric symbols) and the name of the new grouping criteria
• In the tab Work Pack Grouping Attributes, choose the attribute of the new criteria from the list available in the value help.
• After you create a grouping criteria in this step, you can assign this grouping criteria to the work pack type in the relevant configuration step Assign Grouping Criteria to Work Pack Type.

Assign Grouping Criteria to Work Pack Type

In this step, you can choose and assign grouping criteria for work pack types.

You can assign more than one grouping criteria per work pack type. You can select from the predefined list or create  new grouping criteria in the relevant configuration step Define Grouping Criteria for Work Packs.

• output Immediately: Select this option to configure only a single combination of work pack type and grouping criteria.
• Default Grouping Criteria: Select this option to make one of the available grouping criteria as a default.
• Include Operation: Select this option to include work pack operations that are part of other work packs in the new work pack.

Log in to track your progress & complete quizzes

Blog about all things SAP

ERProof » SAP PM » SAP PM Training » SAP Maintenance Order

SAP Maintenance Order

SAP PM is divided in two areas:

• Basic maintenance: equipment is structured and the repair is documented.
• Preventive maintenance: automatic generation of planned orders due to maintenance plans.

This tutorial covers the handling of orders for basic maintenance. Only the steps below the line shown on the picture are covered.

SAP PM orders play a central role in maintenance processing. They are the cost collectors and the initiators to get work performed.

SAP PM notification cannot collect cost, only information. If it is required to have detailed reporting on e.g. reason codes, we must have the notification to collect this kind of information. The notification can also be used as a request for maintenance before SAP maintenance order is created.

Since it’s optional to use the notification, creation of a maintenance notification is described in a separate tutorial and is not covered here.

SAP Maintenance Order Lifecycle

Through different steps in order processing the order will get different statuses. Each status represents a step in the orders lifecycle and different functions are related to the status.

In the diagram below, you will find steps from the basic maintenance process flow and the statuses related to the steps. On the right side you can see each function available with the status.

From the diagram, it can also be seen that you can’t reverse the statuses DLFL and REL (marked with red arrows in the below diagram). Status CLSD can only be reversed to status TECO.

SAP Maintenance Order (SAP PM Order)

Orders form an important part in SAP Plant Maintenance. Orders are cost collectors and you cannot do any maintenance without an order. Orders store the actual time spend on maintenance tasks, the consumption of spare parts, and if an outside vendor has done some repair, the invoice finds a place in the PM order too.

You can supplement orders with notifications. However, it is not necessary to use notifications in order to use SAP PM orders.

SAP Maintenance Order Types Configuration

When you create an order it is very important that you choose the correct order type because almost all the reporting is done by order type. In reporting, you can compare costs for breakdown, planned repair and preventive maintenance only if you use the order types correctly. We do have some mandatory configuration for order types which is shown below.

SPRO>>Plant Maintenance and Customer Service>>Maintenance and Service Processing>>Maintenance and Service orders>>Functions and Setting for Order type>>Configure order type

Order Number Range

We define number ranges for the order type in this step. There can be different ranges based on business reporting levels. Number range is a transportable object but it is recommended to do number range maintenance at the client level.

SPRO>>Plant Maintenance and Customer Service>>Maintenance and Service Processing>>Maintenance and Service orders>>Functions and Setting for Order type>>Configure number range

Assign Order Type to Maintenance Plant

We link the order type to a maintenance plant in this step of configuration.

SPRO>>Plant Maintenance and Customer Service>>Maintenance and Service Processing>>Maintenance and Service orders>>Functions and Setting for Order type>>Assign order type to maintenance plant

Set Scheduling Parameter for Order Type

We need to define scheduling parameters for the order type in relation with a plant. We can set the following scheduling parameters for every maintenance plant:

• Automatic scheduling
• Display scheduling log automatically after scheduling
• Maximum number of days for start in the past
• Automatic adjustment of the start/finish dates
• Shift order indicator
• Scheduling to incorporate breaks (breaks at the work center are taken into account when scheduling is created)

SPRO>>Plant Maintenance and Customer Service>>Maintenance and Service Processing>>Maintenance and Service orders>>Scheduling>>Set Scheduling parameters

Operations with SAP Maintenance Order

Order creation is very quick and is easy to do. For most of the order types the order creation follows the same procedure except refurbishment process, which is not defined in this tutorial as it mainly deals with basic maintenance.

Create Order

On the initial screen of IW31 transaction do the following:

• Insert order type
• Choose a priority
• Insert the equipment or functional location

Next, click Enter button on the keyboard.

On the next screen, you should enter the following information:

• Enter a short description of the problem.
• Main work center defaulted from the equipment.
• Dates are calculated or can be defined.
• Functional location, defaulted from the equipment else functional location can be defined.
• Work center for operation. Defaulted – the same as main work center.
• Control key, defaulted from the work center.
• Activity type, defaulted from the work center.
• To put in process, click release the maintenance order.
• Please use long text if details need to be defined for maintenance planner/technician.

Operation tab contains details related to operations which will be performed during maintenance processing. Operation contains planned required time which will be the basis of planned cost calculation based on activity type and cost center defined in the work center . It is defaulted from equipment or functional location task list. It is also possible to adopt general task list in PM order.

Components tab contains spare part information which will be required during maintenance processing. On release of the order, spare parts can be consumed against reservation in planned way. Consumption of spare part will update actual cost in the maintenance order.

The order can be saved now for further processing.

Change Order

This transaction is used if any changes related to operations (addition or deletion), more or less spare parts are required during processing, shop floor paper prints are required.

Change mode can also be used to release order if it is not done during the initial creation. It is updated with the status REL.

Shop floor papers are printed on order release.

Make Extra Order Prints

On the initial screen of IW3D transaction enter the order number and click Enter button on the keyboard.

Display Order

On the initial screen of IW33 transaction enter the order number and click Enter button on the keyboard.

All header data is displayed and you can navigate through to display different data on different tabs.

Next, click on Costs tab.

Planned costs consist of planned activity cost, spare parts cost as planned along with other miscellaneous overhead costs. If activity confirmation and spare part consumption has been taken place, then actual consumption value will also be reflected.

There are different other navigation options to get details of different cost center details.

Completion Confirmation

Confirmation on an order has to be made for each operation, which means each work center. As soon as an order has been released and the work has begun, the employees involved can enter completion conformation in the system.

It can be either a partial or a final confirmation:

• Partial – some work has been done, but there are still work left.
• Final – all work is finished.

On the initial screen of IW41 transaction, enter the order number and press Enter on the keyboard.

On the next screen, select the operation for which confirmation will be done and click on Actual Data button.

Here, actual work along with work start and work finish details are provided. If last confirmation is being made for this operation, then it is recommended to check Final Confirmation checkbox.

It is also possible to link the order confirmation with an employee personal number (from SAP HR module ). If there are any deviation from planned values, then a reason code should be selected.

Also, insert a confirmation text to describe in very short terms what have been done. Next, click on Goods Movements tab if spare parts are backflushed (goods issue along with confirmation).

Now, we can save the document and it will do the operation confirmation along with goods issue if any.

It will change the order status to PCNF, and if the final confirmation is done, then the status will be CNF.

Did you like this tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP PM tutorials.

Navigation Links

Go to next lesson:  SAP Corrective Maintenance Process

Go to previous lesson:  SAP Breakdown Maintenance Process

Go to overview of the course: SAP PM Training

16 thoughts on “SAP Maintenance Order”

helpfull to understand the complete work flow one question I have? is an report available to see all orders was TECO for one day? and also an report which show me the Action log from an order?

There is no standard report available for action log of PM orders however if you want to know how many orders have status TECO for a period of time then T/code IW38 can be used. Status TECO needs to be put in field “Status inclusive”

How to assign different the schedule Start Date and Basic Start date in custom FM of PM_ORDER_EXTERN_SCHED_DEFAULT

You need help of an ABAP developer with this.

It is not possible for FM suggested. Please use ALM_ME_ORDER_CREATE

Is there any T code to get the List of Tasklist’s , Activity type i.e man power utilisation , Component’s , spares &PRT along with notification date in single report

Good document.

How there is no notification to input malfunction type, cause codes etc?

how to change the default printer of maintenance order to another new printer ?

type Tcode su0 enter then go to defaults tab spool control then change your printer make sure the print now & delete after output are flagged

thanks for your technical support!

How to Close Work Order in SAP (user status as CLSD)

Is there a way to stop the order description from populating the text field of the first operation?

Hi, During order confirmation via IW41. is there any possibility to attach defect photos before Vs after to have equipment history.

After time confirmation, final settlement of order to be done using K088.

But I can reverse DLFL status in work order I have tested it. Can you please tell me why it is mention here as DLFL is not reverted?

Leave a Reply Cancel reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM !

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

2946904 - Operation field for Maintenance Order in SRM Shopping Cart

• When create a SC in SRM with account assignment for PM order, there is an error "Order &&& requires assignment to an operation number" (ERP_CO_OLC_E 003).
• There is no option to enter Operation against the Order.
• The Operation fields are not available in Customizing path: SPRO -> SAP IMG -> SRM Server -> Cross Application Basic Settings -> Account Assignment -> Define Account Assignment Categories.

Environment

• SAP Supplier Relationship Management (SRM) 7.0 and higher
• SAP enhancement package for SAP Supplier Relationship Management

EBP, ACC, BBP4X_CODINGBLOCK_CHECK_47A , CO_SF_NETWORKACTIVITY_CHECK, network, activity, AFVC -VORNR ,AFVC , VORNR , KBA , SRM-EBP-CA-ACC , Account Assignment , PM-WOC-MO-OLC , Operation Level Costing , Problem

About this page

Search for additional results.

Visit SAP Support Portal's SAP Notes and KBA Search .

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark