Domain: SU Management Accounting

Responsibility area: Maintain Costing Master Data

1. Objective and Scope

1.1. Objective of this Operation

The purpose of this document is to describe the process of creating a WBS (OPEX/Expense).

1.2. Scope

This document applies to all the processes of creating a WBS to process expense costs (non capitalized).

2. Definitions

See Finance Glossary

3. Tasks description

3.1. I receive the request to create a WBS

I receive a request to create a WBS, some mandatory fields are necessary such as:

WBS Code
Description
Cost Center
SRM7 Code (Position of person approving shopping carts)

3.2. I search an existing Project

After the project code is provided and details to introduce into the WBS we can enter the project using CJ02 or CJ20N, in this case we will use "RR.DSXXDI" and T-Code CJ20N.

The Project Structure has Project RR.DSXXDI in first line, WBS level 1 RR.DSXXDI in second line and WBS level 2 RR.DSXXDI.101 in third line.

3.3. I create the WBS element

In this case we will create a new WBS Element (level 2) RR.DSXXDI.146 inside Level 1 WBS RR.DSXXDI.
By selecting WBS Level 1, right click mouse to view options and select Create > WBS Element.

The new line in the project was now created but with several empty fields in tab Basic data that will need to be edited:

WBS Element Code: RR.DSXXDI.146
WBS Element Description: Energy CO2 Operations
Proj. Type (Expense): Internal Operations for Regular Family Projects and Innovation Project for R&I Family Projects.
System Status: (REL) - Released and SETC (Settlement Rule Created) - Read 3.3. Paragraph
Person Responsible No.: Code managed in T-Code OPS06 to identify who is in charge of the project.
Account Assignment Element: X (Should be selected in order to receive costs).
Responsible Cost Center: Cost Center that the costs will go trough.
Required Cost Center: Cost Center that the costs will go trough.
Required Company Code: Automatically populated after Cost Center are inserted.

Next tab to be maintained is Assignments:

The fields will be automatically populated using the same information provided in the Project Master data.
For Expense Projects the Object Class: Overhead should be selected. All remaining information should be according to request.

Next tab to be maintained is User fields:

Only some GBU's use field Code of Group, in order to aggregate projects by groups created in T-Code ZWPST004.

Checkboxes: X Replicon (If the WBS is used to track and charge hours of labor by engineer's or laboratory employees)

Next tab to be maintained is Cust. Enhancement:

The majority of the information related to Cust. Enhancement is to identify the market that is related the WBS and Invoicing information.

First Fields are related to the GBU/Business Unit, that should be filled in according to request.

Fill in next fields related to WBS Family, and Position Code (SMR7 Approver) provided by the requester.

Specifically for R&I Projects the WEGO Number and Category can be requested:

3.4. I create the settlement rule

The Settlement Rule and Settlement Parameters define how the costs will be processed for expense costs we can have the following cost objects available:

Cost Center
WBS
Order
GL Accounts

Edit -> Costs -> Settlement Rule-> Go To-> Settlement Parameters:

Options Available will change according to what is defined in the Settlement Rule Parameters:

For R&I PF1 example, to allocate costs to a CC in the Settlement Parameters should be the Settlement Profile: ZPS10 and Allocation Structure: SJ.

There are several different combinations possible in order to reflect the costs with different accounts in the receiver cost object.

Table of contents

Scope

ERP

Frequency

References

Forms

Attachments