Overhead Cost Accounting - Actual (184)uacnlinks.org/.../2016/03/PERTS_184_-Overhead-Cost-Accounting-Actual.pdf · EHP4 for SAP ERP 6.0 March 2010 English Overhead Cost Accounting

EHP4 for SAP ERP 6.0

March 2010

English

Overhead Cost Accounting - Actual (184)

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Business Process Documentation

SAP Best Practices Overhead Cost Accounting – Actual (184): BPD

© SAP AG Page 2 of 22

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint

are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects

Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose ................................................................................................................................... 5

2 Prerequisites............................................................................................................................ 5

2.1 Master Data ...................................................................................................................... 5

2.2 Roles ................................................................................................................................ 5

2.3 Preliminary Steps ............................................................................................................. 6

2.3.1 Setting Controlling Area ............................................................................................ 6

3 Process Overview Table ......................................................................................................... 7

4 Process Steps ......................................................................................................................... 8

4.1 Actual Postings in Overhead Cost Controlling ................................................................. 8

4.1.1 Entering G/L Account Documents ............................................................................ 8

4.1.2 Reposting of Primary Costs .................................................................................... 10

4.1.3 Reposting of Line Items .......................................................................................... 11

4.1.4 Recording of Statistical Key Figures ....................................................................... 13

4.1.5 Reporting ................................................................................................................ 14

4.2 Period-End Closing in Overhead Cost Controlling ......................................................... 15

4.2.1 Assessment of Shared Expenses ........................................................................... 15

4.2.2 Accrual Calculation ................................................................................................. 17

4.2.3 Controlling Maintain Versions ................................................................................. 18

4.2.4 Period Lock ............................................................................................................. 20

5 Appendix ................................................................................................................................ 21

5.1 Reversal of Process Steps ............................................................................................. 21



Overhead Cost Accounting - Actual

1 Purpose This part of the document describes the transaction-based actual postings that are normally used in Overhead Cost Controlling.

For an explanation of the activities that are generally performed at the end of the period, refer to the chapter Period-End Closing.

2 Prerequisites

2.1 Master Data

A description of all CO Master Data can be found in the document of CO_MasterData_Overview.xls.

Common Master Data provided for all Areas

Master Data Value Selection Comment

Cost Center

Cost Center Group 100 and all groups assigned to group 100

Cost Elements *

Service Area


Cost Center

Manufacturing Area / Trading Area


Cost Center

2.2 Roles

Use

The following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

Prerequisites

The business roles have been assigned to the user who is testing this scenario.



Business Role Details Transaction

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality.

General Ledger Accountant

SAP_NBPR_FINACC-S FB50 (FB50L)

Enterprise Controller

SAP_NBPR_CONTROLLER-M KB11N

KB61

KB31N

S_ALR_87013611

KSU5

KSA3

S_ALR_87005830

OKP1

2.3 Preliminary Steps

2.3.1 Setting Controlling Area

Use

The controlling area is to be set before you carry out the first steps in controlling.

If the controlling area is already assigned in the user parameters (see the Quick Guide), this step is no longer necessary and can be omitted.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Controlling Cost Element Accounting

Environment Set Controlling Area

Transaction code OKKS

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Enterprise Controller

(SAP_NBPR_CONTROLLER-M)

Business role menu Overhead Cost Controlling Actual Postings Actual

Posting Preparation Set Controlling Area



2. On the Set Controlling Area screen, enter Controlling area 1000.

3. Save your entry as a user parameter.

3 Process Overview Table There is generally no required sequence for transaction-based actual postings in Overhead Cost Controlling. For simplicity’s sake, the activities are described below in the order in which they appear in the SAP Easy Access menu:

Process step External process reference

Business condition

Business role

Transaction code

Expected results

Enter G/L Account Document

Primary cost element posting to cost center

General Ledger Accountant

FB50 (FB50L) Actual costs are posted to cost centers

Reposting Primary Costs

Correction of Primary Cost Values


KB11N Updating Cost Centers while Generating Line Item.

Reposting Line Items

Line Item Repostings


KB61 Displays Line Items reposted

Recording of Statistical Key Figures

statistical key figures as transaction-based actual postings


KB31N postings for statistical key figures and reverse them if necessary

Reporting periodically Enterprise Controller

S_ALR_87013611 shows the actual and plan costs, as well as the resulting variances in absolute values and percentages

Assessment of shared expenses

Periodically Enterprise Controller

KSU5 Allocates primary and secondary costs to the receiving cost center(s) in an assessment cost element.

Accrual calculation

Periodically Enterprise Controller

KSA3 Post accruals for payroll fringe costs on a monthly basis

Maintain Versions

Year end Enterprise Controller

S_ALR_87005830

Period Lock Year end Enterprise Controller

OKP1



4 Process Steps

4.1 Actual Postings in Overhead Cost Controlling

4.1.1 Entering G/L Account Documents

Use

Entering G/L Account Documents is an activity belonging to the FI application. For each data record that you enter a CO-object has to be provided. By doing so, the CO objects are charged with the corresponding amount of costs.

Procedure



SAP ECC menu Accounting Financial Accounting General Ledger Posting

Enter G/L Account Document for Ledger Group

Transaction code FB50 (FB50L)


Business role General Ledger Accountant

(SAP_NBPR_FINACC-S)

Business role menu General Ledger Posting Posting Post G/L Account Document

2. On the Enter G/L Account Document for Ledger Group screen, make the following entries:

Field name Description User action and values Comment

Company Code <company code>

CORPRATE CENTER

1000

UNICO

2000

CAP

3000

UFL

4000

SWAN

4010

GCL

5000



Document date

<Current date> Example

Posting date <Current date> Example

Currency NGN

G/L account <Any account which

is a cost element> Example: 500040

D/C Debit

Amount in doc. curr.

<Any value> Example: 10000

Tax code * Example, V1 (domestic input tax)

Calculate tax X On Details tab

Cost center <Any cost center>

CORPRATE CENTER

Cost center 1002

CHIEF FINANCIAL OFFICER

UNICO

Cost center 2002 COMMERCIAL

CAP

Cost center 3010 FINANCE/IT

UFL

Cost center 4010

PROCUREMENT – HEAD OFFICE

SWAN

Cost center

4120

PROCUREMENT – HEAD OFFICE

GCL

Cost center 5177 Quality Assurance

G/L account <Any account> Example: 161613

D/C Credit

Amount * Example: 10000

Value date <Current date> Double click on line item to enter the date

Choose Post

3. Enter further G/L account postings as shown above using different accounts and cost centers.

Result

Primary costs are posted.



4.1.2 Reposting of Primary Costs

Use

In transaction-based reposting, you can post an existing cost element from one cost center to another (or to a different CO object). This function is used primarily to correct postings in Controlling that were incorrectly posted in the upstream user departments.

Prerequisites

Primary costs are already posting to CO object. The CO object has to be corrected.

Procedure



SAP ECC menu Accounting Controlling Cost Center Accounting Actual

Postings Manual Reposting of Costs Enter

Transaction code KB11N




Business role menu Overhead Cost Controlling Actual Postings Actual Postings Enter Manual Repostings of Costs

2. On the Enter Manual Repostings of Primary Costs screen, make the following entries:


Document date



Period Proposed automatically Example

Document text

CCtrr (old) Cost center (old) <select cost center>

Cost elem. Cost element * For example, 500100

Amount * For example, 4000

CCtrr (new) Cost center (new) * Choose a different cost center

Text * For example, Correction cost center

Post

Result



Once you have entered the transaction-based posting, it is effective immediately and updated in the cost centers involved. Line items are always generated to help you trace the entered documents.

4.1.3 Reposting of Line Items

Use

The reposting of line items in Controlling is normally used to correct postings that were posted incorrectly in the upstream user departments.

Prerequisites

Primary costs are already posting to CO object.

Procedure



SAP ECC menu Accounting Financial Accounting General Ledger Posting

Enter G/L Account Document for Ledger Group

Transaction code FB50 (FB50L)



(SAP_NBPR_FINACC-S)

Business role menu General Ledger Posting Posting Post G/L Account Document

2. On the Enter G/L Account Document for Ledger Group screen, make the following entries:


Company Code

<select company

code> 1000, 2000, 3000, 4000, 4010 or 5000

Document date



Currency NGN

G/L account <Any account which

is a cost element> Example: 500020

D/C Debit

Amount in doc. curr.

* For example, 10000

Tax code * For example, V1 (domestic input tax)

Calculate tax X

Cost center <select cost center>

G/L account * For example, 161613



D/C Credit

Amount * For example, 10000

Value date <Current date> Example

Post

Write down the document number for the subsequent transactions.

3. Repost the line items. Access the transaction choosing one of the following navigation options:



Postings Repost Line Items Enter

Transaction code KB61




Business role menu Overhead Cost Controlling Actual Postings Actual Postings Enter Reposting of CO Line Items

4. On the Enter Line Item Repostings screen, make the following entries:

Field name Description User actions and values Comment

Document number

<Document number

from the above

posting>

Company code <select company

code> 1000, 2000, 3000, 4000, 4010 or 5000

Fiscal year <Current fiscal

year> Example

Execute

Value TranCurr * For example, 5000

Object type CTR Cost center

Account assignment 1

<select cost center>

Text

Enter

Value TranCurr * For example, 2000




Text

Enter



Value TranCurr * For example, 1403.36




Text

Choose Post

Result You can display the reposted line items at any time.

4.1.4 Recording of Statistical Key Figures

Use

You enter the statistical key figures as transaction-based actual postings. They are used to calculate key figures for reporting and also as the basis for periodic allocation.

Prerequisites When you define a statistical key figure, you have to define its characteristic values. You can define a statistical key figure as:

A fixed value: Fixed values are carried forward from the current posting period to all subsequent posting periods.

A totals value: Totals values are only posted in the current posting period.

Procedure




Postings Statistical Key Figures Enter

Transaction code KB31N




Business role menu Overhead Cost Controlling Actual Postings Actual Postings Enter Statistical Key Figures

2. On the Enter Statistical Key Figures screen, make the following entries:


Document date



Document text




Receiver cost center

<select cost center> Manufacturing cost center

Statistical key figure

* For example, 1002

Total quantity

* For example, 4

Text

Choose Post

Result

Like in the preceding activities involving actual postings, you can also display the postings for statistical key figures and reverse them if necessary.

4.1.5 Reporting

Use Reports predefined by SAP are available for Cost Center Accounting. The predefined reports are arranged in a standard report tree. The reports enable you to evaluate the posted data according to various criteria. A variety of analysis functions is also available.

Prerequisites Postings are done.

Procedure



SAP ECC menu Accounting Controlling Cost Center Accounting Information

System Reports for Cost Center Accounting Plan/Actual

Comparisons Cost Centers: Actual/Plan/Variance

Transaction code S_ALR_87013611




Business role menu Overhead Cost Controlling Reporting Cost Centers Cost Centers: Actual/Plan/Variance

2. On the Cost Centers: Actual/Plan/Variance: Selection screen, make the following entries:


Controlling area

1000


year> Current year

From period 1 January



To period 12 December

Plan version 0 Plan/actual version

Cost center group

Or value(s) (cost centers)

Cost element group

Or value(s) (cost elements)

Choose Execute

Result

The report shows the actual and plan costs, as well as the resulting variances in absolute values and percentages. You can display the plan and actual costs at both cost center and cost element level.

4.2 Period-End Closing in Overhead Cost Controlling

Purpose The purpose of Cost Center Accounting is to take the costs incurred in a company and allocate them to the actual sub-areas that caused them. During the period-end closing, these costs are distributed to the cost centers through automatic allocation. By allocating the cost elements to cost centers in Overhead Cost Controlling, you can control your costs and compare plan and actual costs. The plan/actual comparison at the end of the period help you to plan, control and monitor cost behavior. It also supports various analyses of variances, such as volume variance, price variance, input variance and quantity variance. Overhead Cost Controlling is also a prerequisite for further allocating overhead costs to cost objects (CO-PC), which enables you to conduct a period-specific profitability analysis.

4.2.1 Assessment of Shared Expenses

Use

Assessment is an activity that you perform periodically, during the period-end closing in Overhead Cost Controlling (CO-OM), in which primary and secondary overhead costs are assessed from one or more sender objects to one or more receiver objects.

Assessment means that the sending cost center is credited and the receiving cost center is charged under a freely definable secondary cost element. The original cost elements that were charged by the sender cost center are lost, and are converted to one or more assessment cost elements (secondary cost elements).

Assessment groups together the posted primary and secondary costs and allocates them to the receiving cost center(s) in an assessment cost element.

For example, you could assess the cost from the reception cost center to the other cost centers based on the headcount managed in those cost centers.

Prerequisites

One or more assessment cycles have to be configured.



You have to start the defined cycles for assessment for the corresponding periods. The postings are generated automatically. A log is generated. You can start a simulation before you perform the actual assessment. The simulation displays the individual posting records without actually posting them.

The following cycle has been defined for the actual assessment:

Cycle Segment Sender CC Tracing Factor Receiver

Y_A020

Ass. shared facility (plan) DE

buildings & maintenance cost

Buildings and maintenance

For example, stat. key figure 1002 (plan)

Area in sq. footage

Cost center

group

Statistical key figures must be entered for some of the receiver cost centers. You can do so using transaction KB31N. For the assessment described above, for more detailed instructions, refer to the information in step “posting statistical key figures” of this document.

Procedure



SAP ECC menu Accounting Controlling Cost Center Accounting Period-End

Closing Single Functions Allocations Assessment

Transaction code KSU5




Business role menu Overhead Cost Controlling Period End Closing Execute Actual Assessment Cycle for Cost Centers

2. On the Execute Actual Assessment screen, make the following entries:


Period <Current period> Example


year> Example

Test run X Until the run is error-free

Detailed lists X

Cycle Y_A020 Actual assessment

Execute

Test run Deselect for production run

Execute

Result

Assessment is started at the end of the period. Line items (posting records) are written for the individual postings. These postings are generated automatically.



You can start a simulation before you perform the actual assessment. The simulation displays the individual posting records without actually posting them. You can reverse the assessment if necessary.

4.2.2 Accrual Calculation

Use In Cost Accounting, it is often necessary to impute costs (for planning reasons) that have a different equivalent – or none at all – in Financial Accounting. Such costs are called accrued costs. They are divided into valuation differences and additional costs. The SAP system uses accrual calculation in order to model both cases automatically. In accrual calculation, costs that are posted irregularly in the individual periods in Financial Accounting are distributed among the individual periods according to cause (on an accrued basis). One example of such accrued costs is the holiday bonus. In Controlling, the holiday bonus is distributed among the 12 months of the year, in order to charge all the months equally. If you did not distribute the holiday bonus among all the periods, you would have an intolerable cost fluctuation for the month of December, which would distort the operating profit for that period. To avoid such fluctuations, the costs are posted on an accrual basis in Controlling, which distributes the costs in a manner that is both according to cause and pertinent for the period.

Prerequisites In order to determine the actual accruals, a costing sheet with valid overhead rates must be defined in Customizing. The structure of the costing sheet is taken from the planned accrual. An order serves as the accrual object. This accrual order corresponds to the one used in the plan, which enables you to compare and contrast the plan and actual costs.

You have to enter postings in Financial Accounting in order to create values in the system as a basis for the accrual calculation. For demo purpose you could enter a G/L account posting for salaries for account 630000 and cost center 1101(offsetting entry to bank account 280000 in credit), for example. For more detailed information about G/L account postings, refer to the information on reposting line items in the Actual Postings document.

Procedure



SAP ECC menu Accounting Controlling Cost Center Accounting Period-End

Closing Single Functions Accrual Calculation

Transaction code KSA3




Business role menu Overhead Cost Controlling Period End Closing Actual Accrual for Cost Centers

2. On the Actual Accrual Calculation for Cost Centers screen, make the following entries:


Cost center group

1000 Cost center group (BP UK)



Period <Current period> Example


year> Example

Test run X Until the run is error-free

Detailed lists X

Execute

Test run Deselect for production run

Execute

If you want processing to take place in the background, set Background Processing in the Processing Options area. This is recommended for large data volumes.

You can simulate the accrual calculation for testing and forecast purposes. To do so, set Test Run on the initial screen. This function enables you to check the results of accruals calculation without making any changes to the database.

If you choose background processing, you have to enter the necessary data on the Background Processing: Job Parameters screen:


Job name <Name of background

job> Any

Planned start <Date and time> Start of background job

No start after <Date and time> Upper limit of time window

Immediate start X Job starts immediately

Check

Result Accrual calculation triggers the following postings:

The accrual order is credited

The cost center is debited

Check accrual postings in reporting. For information on how to call a cost center report, refer to section Reporting of this business process documentation Actual Postings in Overhead Cost Controlling.

4.2.3 Controlling Maintain Versions

Use

This activity is a year-end-activity, which can be executed for several years at once. In this IMG activity you edit the general version definition on the client level.

You make controlling area settings in the IMG for the Cost Center Accounting, Overhead Orders, or Activity-Based Costing components.



You make profitability segment settings in the IMG for the Profitability Analysis component.

For demo purposes Best Practices already delivered fully maintained versions. Therefore it is usually not required to adopt the versions in case of demo.

Procedure



SAP IMG menu Controlling General Controlling Organization Maintain Versions

Transaction code S_ALR_87005830




Business role menu Overhead Cost Controlling Period End Closing Maintain Version Settings

2. On the Choose Activity screen, choose Maintain Settings of Version in Controlling Area.

3. On the Determine Work Area Entry dialog box, make the following entries:


Controlling Area

1000

Version 0

4. On the General Version Definition screen, select the version 0 and choose on the Dialog Structure Settings for each fiscal year (double click).

5. Select the newest year and choose Copy As (F6). On the General Version Definition screen, select the version 0 and choose on the Dialog Structure Settings for each fiscal year.

6. On the Change View “Settings for each fiscal year”: Details of selected set screen, make the following entries:


Fiscal Year <The new fiscal year

you want to maintain>

Value Date <01.01.yyyy> yyyy = the fiscal year, you want to maintain

7. Choose Save.

Result The controlling versions are completed for the next year(s).



If transport handling is activated in the client an input for customizing request is required. Assign the customizing request you are assigned to.

4.2.4 Period Lock

Use Use the period lock to lock plan and actual business transactions for a combination of controlling area, fiscal year, and version.

You can use Actual and Plan to decide whether to lock periods in actual or plan data. You receive a list of all business transactions in actual or in planning data, with which you can lock individual transactions for specific periods.

Procedure



SAP ECC menu Accounting Controlling Cost Element Accounting

Environment Period Lock Change

Transaction code OKP1




Business role menu Overhead Cost Controlling Period End Closing Change Period Lock

2. On the Change period lock: Initial screen, make the following entries:


Controlling Area

1000

Fiscal Year <The actual fiscal

year>

Version <0> Plan and actual version

3. Choose Actual.

4. On the Change Actual Period Lock: Edit screen, select the period, you want to lock and then choose Lock Period.

5. Choose Save.

Result All CO-transactions are locked for the selected period.



5 Appendix

5.1 Reversal of Process Steps

In the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Entering G/L Account documents

Transaction code ( SAP GUI) FB50L

Reversal: Individual reversal

Transaction code ( SAP GUI) FB08


(SAP_NBPR_FINACC-S)

Business role menu General Ledger G/L Account Processing Display G/L Account Items Reverse Document

Comment

Reposting of primary costs

Transaction code ( SAP GUI) KB11N

Reversal: Reverse





Postings Reverse Manual Repostings of Costs

Comment

Reposting of line items

Transaction code ( SAP GUI) KB61

Reversal: Reverse

Transaction code ( SAP GUI) KB64




Postings Reverse Reposting of CO Line Items

Comment

Recording of statistical key figures




Reversal: Reverse





Postings Reverse Statistical Key Figures

Comment

Assessment Shared Expenses

Transaction code ( SAP GUI) KSU5

Reversal: Reverse assessment

Transaction code ( SAP GUI) KSU5



Business role menu Overhead Cost Controlling Period End Closing Execute Actual Assessment Cycle for Cost Centers

Comment Use same transaction

Accrual calculation

Transaction code ( SAP GUI) KSA3

Reversal: Reverse accrual costs

Transaction code ( SAP GUI) KSA3

Business role Enterprise Controller (SAP_NBPR_CONTROLLER-M)

Business role menu Overhead Cost Controlling Period End Closing Actual Accrual for Cost Centers

Comment Use same transaction