Show TOC

Component documentationEasy Cost Planning and Execution Services Locate this document in the navigation structure

 

Easy Cost Planning

Easy Cost Planning enables you to quickly calculate planned costs for:

  • Internal orders

  • WBS elements

  • Internal service requests

  • Appropriation requests

  • Ad hoc cost estimates

You establish a representation of the structure of planning objects in the system. These can then be used as planning forms by all cost planners. Easy Cost Planning is therefore particularly efficient when more than one person plans costs, or when you frequently plan costs in a similar way.

For an example of an Easy Cost Planning application that you can try out in an IDES system, see Example: Creating a Costing Model for Projects.

For more information on using Easy Cost Planning, see Use of Easy Cost Planning.

Execution Services

Execution Services enable you to trigger the following processes based on the costing results:

  • Purchase requisitions

  • Purchase orders

  • Reservations

  • Goods issues

  • Internal activity allocations with or without workflow

Integration

Cost planning for the object concerned is carried out in the corresponding component: Internal Orders (CO-OM-OPA), Project System (PS), Investment Management (IM), Product Cost Planning (CO-PC-PCP), or using the mySAP Workplace.

The following components are called up in the background. User knowledge in these areas is not required.

In order to complete the respective Execution Service, the Purchasing (MM-PUR), Inventory Management (MM-IM), Cost Center Accounting (CO-OM-CCA), and/or Activity-Based Costing (CO-OM-ABC) components are used, with or without the SAP Business Workflow.

Easy Cost Planning calculates the costs by using the unit costing function from Product Cost Planning (CO-PC-PCP), the characteristics function of the Classification System (CA-CL), and the template function from Activity-Based Costing (CO-OM-ABC).

Features

You create a costing model that contains the cost factors of a planning object and that represents the planner's point of view. You can structure the planning object. It is also possible to divide up related cost factors into separate costing models. You then merge these costing models into one large costing model at the end. This helps even large planning objects remain manageable, and enables you to reuse the smaller costing models.

The planner uses the costing model as a planning form. The use of this planning form ensures that all of the relevant cost factors are included, helping you to avoid errors.

To plan the costs, the planner quantifies the cost factors. The use of planning forms enables the costs to automatically be translated into data for unit costing: the system generates the costing items of the unit cost estimate and costs them.

The planning object can be structured whichever way the planner chooses, and the substructures that the user defines can be costed separately. Existing structures, such as those in the Project System, are included in costing.

You can define the entry screen in accordance with your individual requirements for each planning form. It is automatically generated in HTML format, and you can modify it in various ways, for example by adding your company logo or hyperlinks to additional data. You can also insert information in the form of explanatory text. The entry screen includes a field where planners can enter comments for themselves or for other users who need to analyze the cost estimate. These comments are saved together with the entries for the cost estimate.

You can adapt the display of individual screens for individual roles, for example to simplify the display for planners who only use this function occasionally and do not need all of the features.

The Execution Services function selects the costing items for the process to be triggered. You can change, delete, and add the costing items selected. From this display you can trigger the process for the selected items.

It is possible to display postings for the services selected that already exist in the system for the respective object. For example, if you want to trigger a purchase order for an internal order, you can call up the existing postings for this order to avoid a duplication of the purchase order.

This graphic is explained in the accompanying text.

Constraints

You cannot use this costing method for the following objects in unit costing:

  • Materials

  • Sales documents

  • CO production orders

  • General cost objects

  • Network activities

You cannot use Execution Services for appropriation requests.

You can only use Execution Services for an ad hoc cost estimate if you have assigned an account assignment object to the ad hoc cost estimate.