J21_BB_ConfigGuide_EN_DE

8/6/2019 J21_BB_ConfigGuide_EN_DE

http://slidepdf.com/reader/full/j21bbconfigguideende 1/16

SAP R/3 4.7

March 2004

English

Cost Object Controlling -

Make-to-Stock (J21)

SAP AGNeurottstr. 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices Cost Object Controlling - Make-to-Stock (J21): Configuration Guide

Copyright

© Copyright 2004 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 softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®,OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,

Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USAand/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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 technologyinvented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves information purposesonly. National product specifications may vary.

© SAP AG Page 2 of 16




Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

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

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 keywords 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 asnames 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 thesystem exactly as they appear in the documentation.

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







Cost Object Controlling - Make-to-Stock:Configuration Guide

1 Purpose

This configuration guide provides the information that you need to manually set upconfiguration of this building block.

If you do not want to configure manually and prefer to use an automated installation processusing BC sets and other tools, refer to the installation guide for this building block.

2 Preparation.2.1 Prerequisites

If you want to use this building block, you must first install the following building blocks:

Building Block # Description

B32 Settings for Best Practices Installation

J02 Organizational Structure

B29 External Accounting - Central FI

B30 Cost and Profit Center Accounting

J05 Materials Management

J04 Sales and Distribution

J18 Product Cost Planning

J17 Profitability Analysis (optional)

3 Configuration.3.1 Cost Object Controlling

Cost Object Controlling calculates the costs that incur during a concrete manufacturingsituation. It consists of preliminary costing, simultaneous costing and period-end closing.Preliminary Costing calculates the target costs of the order. Simultaneous costing provides anoverview over the actual costs incurred on the order so far and compares them to the targetcosts. Period-end closing deals with allocation of overhead costs, reconciliation betweenControlling and Financial Accounting, variance calculation and settlement.





3.1.1 Create Valuation Variant for Manufacturing Orders

Use

The Valuation Variant controls various parameters regarding the valuation of input items for the object for which costs are being determined.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3

Role Menu

Check Valuation Variants for Manufacturing Orders

Transaction Code OPN2

IMG Menu Controlling Product Cost Controlling Cost Object

Contolling Manufacturing Orders Check ValuationVariants for Manufacturing Orders

2. Click button New Entries and enter header data. Then for each new entry chooseDetails and enter remaining data.

3. Overview of data records:

Valuation Variant Name

Y01 SMB Planned Valuation

Material Value

Prio Strategy sequence incl add co

Y01 1 Planned Price 1Y01 2 Standard Price

Y01 3 Moving Average Price

Activity Types/processes

Prio Strategy sequence P/A Version

Y01 1 Plan price as average of all fiscal year periods 0

Subcontracting: quotation in purchasing

Y01 Net Quotation Price Quot. in purchasing : Actual Quota Arrangement

External processing

Prio Strategy sequence

Y01 1 Price from Operation

Y01 2 Net quotation price

Overhead

Materials Components OH on subc. Mat.

Y01 Baseline Costing Sheet Not set





3.1.2 Create Costing Variant for Manufacturing Orders

Use

The Costing Variant controls various parameters when costs for a cost object or a materialare being determined, such as the costing type or the valuation variant used.

Procedure


SAP R/3

Role Menu

Check Costing Variants for Manufacturing Orders

Transaction Code OPL1


Controlling Manufacturing Orders Check Costing Variants for Manufacturing Orders



Costing Variant Name

YGP1 SMB CP Prod. order Plan

YGP2 SMB CP Prod. order Actual

Control

Costing Type Valuation variant

YGP1 06 Y01

YGP2 07 Y01

Miscellaneous

Costing Variant Gen. costs activity Network component

YGP1

YGP2

3.1.3 Define Goods Received Valuation for Order Delivery

Use

This activity determines how the material that is transferred to stock from a production order isvaluated.

Procedure


SAP R/3Role Menu

Define Goods Received Valuation for Order Delivery





Transaction Code SPRO

IMG Menu Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Order -> Define GoodsReceived Valuation for Order Delivery

2. Make the following entries:

Valuation Area BP01 BP02 BP03 BP0X

Valuation Variant Y01 Y01 Y01 Y01

3.1.4 Period End Closing

Period end closing consists of several steps. Overhead surcharge allocates overhead costs tothe order as specified in the costing sheet assigned to the order. WIP calculation reconciliatesControlling and Financial Accounting by valuating and then capitalizing goods that have beenproduced but not transferred to stock yet. Variance Calculation determines variances betweenthe actual costs incurred on the order and the standard costs of the material produced.Settlement transfers the variances to CO-PA.

.3.1.4.1 Work in Process (WIP Calculation)

WIP calculation is used to valuate order inventories in period-end closing. The computedorder inventories are then transferred to Financial Accounting, whereby a reconciliation

between Controlling and Financial Accounting is achieved.

.3.1.4.1.1 Define Results Analysis Key

Use

The RA key is a key field in most customizing tables for results analysis. It is useddifferentiate different types of results analysis / WIP calculation and to assign them to theorders.

Procedure


SAP R/3

Role Menu

Define Results Analysis Keys

Transaction Code OKG1


Controlling Product Cost by Order Period-End

Closing Work in Process Define Results AnalysisKeys

2. Click button New Entries and provide data.





3. Overview of data records

RA Key Text

YG0001 BP WIP Calculation at Actual Costs

.3.1.4.1.2 Define Results Analysis Version

Use

The RA Version controls various settings related to WIP calculation.

Procedure


SAP R/3

Role Menu

Define Results Analysis Versions




Closing Work in Process Define Results AnalysisVersions

2. Choose button New Entries and provide general data. Choose Details and provideremaining data.


CoArea RA Version Text

BP01 0 BP WIP/Results Analysis (Standard)

Actual Results Analysis / WIP Calculation

Version relevant to settlement X

Transfer to Financial Accounting X

Multiple Valuation Legal Valuation

Extended control

Assignment/RA Key X

Update/RA Key X

Update Plan Values X

Status control A

Cutoff period for actual 1.1900

Actual RA X

Planned Results Analysis

Cutoff period for planned RA 0

Cost Elements

Technical RA cost Element 931000





.3.1.4.1.3 Define Valuation Method (Actual Costs)

Use

The valuation method controls various parameters related to WIP calculation.

Prerequisites

RA Version, RA Key

Procedure


SAP R/3

Role Menu

Define Valuation Method (Actual Costs)

Transaction Code OKGC

IMG Menu Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Order -> Period End Closing -> Work in Process -> Define Valuation Method (Actual Costs)

2. Choose New Entries, then choose WIP method.

3. On New Creation WIP Valuation screen, enter remaining data and choose Enter .

Data records:

WIP Method COAr RA-Version RA key

Actual Costs BP01 0 YG0001

.3.1.4.1.4 Define Line ID’s

Use

Cost Elements are grouped to line ID’s in WIP calculation. Further processing then is definedseparately for each line ID.

Procedure


SAP R/3

Role Menu

Define Line IDs




Closing Work in Process Define Line IDs

2. Choose button New Entries and provide data.






CoArea Line ID Name

BP01 COP Primary Costs

BP01 COS Secondary Costs

BP01 REV Revenues

BP01 SET Settled Costs

.3.1.4.1.5 Define Assignment for Results Analysis

Use

Cost Elements and Cost Element intervals are assigned to line ID’s.

Prerequisites

Cost elements, RA Version, Line IDs

Procedure


SAP R/3

Role Menu

Define assignment

Transaction Code OKGB

IMG Menu Controlling Product Cost Controlling Cost Object Controlling Product Cost by Order Period-End

Closing Work in Process Define assignment

2. Choose the New Entries button and provide the following data:

Overview of data records:

Co-Area BP01 BP01 BP01 BP01

RA Version 0 0 0 0

RA Key YG0001 YG0001 YG0001 YG0001

Masked CoEl 0000521000 000060++++ 00009+++++ 0000523000

Origin ++++ ++++ ++++ ++++

Masked CC ++++++++++

Masked AT ++++++

Bus Proc.

C/D ind. + + + +

Vble/Fix ind. + + + +

App. Reason

Acc ind. ++ ++ ++ ++





Val-from Per. 001.2000 001.2000 001.2000 001.2000

RecToCap COP COP COS SET

.3.1.4.1.6 Define Update for Results Analysis

Use

For each line ID a cost element, under which RA is performed, is assigned.

Prerequisites

RA Versions, Cost Elements, Line IDs

Procedure1. Access the activity using one of the following navigation options:

SAP R/3

Role Menu

Define Update

Transaction Code OKGA



Closing Work in Process Define Update

2. Click button New Entries and enter data.


CoAr Vers RA Key LID CatCreation

UMWIP Reserves

BP01 0 YG0001 COP

K 931110 931120

BP01 0 YG0001 COS

K 931130 931140

BP01 0 YG0001 REV N

BP01 0 YG0001 SET A

.3.1.4.1.7 Define Posting Rules for Settling Work in Process

Use

For each RA Category a P/L- and a balance sheet account is defined where the calculatedWIP is posted to when WIP is transferred to Financial Accounting,

Procedure






SAP R/3

Role Menu

Define Posting Rules for Settling WIP



Controlling Product Cost by Order Period-End Closing Work in Process Define Posting Rules for Settling WIP

2. Select “New entries” and enter the following values:

COArea CompanyCode

RAversion

RAcategory

Recnumber

P/L Acct BalSheetAcct

BP01 BP01 0 WIPR 0 521500 215000

BP01 BP01 0 RUCR 0 548500 390000

3. Save your entries.

.3.1.4.2 Variances & Settlement

Variance Calculation determines differences between the actual costs incurred on aproduction order and the standard costs of the material produced. Variances are calculatednot at once, but for different variance categories. The variances computed are thentransferred to CO-PA.

.3.1.4.2.1 Define Default Variance Keys for Plants

Use

The Variance Key is part of the order header and controls variance calculation. The systemselects the value set by this step as default value when a material master is created. From thematerial master the variance key then is transferred to the order when an order for thematerial is created.

Procedure


SAP R/3

Role Menu

Define Default Variance Keys for Plants

Transaction Code OKVW

IMG Menu Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Order -> Period End Closing -> Variance Calculation -> Define Default Variance Keys for Plants

2. Make the following entries:

Plant Variance Key

BP01 000001

BP02 000001





BP03 000001

BP0X 000001

.3.1.4.2.2 Define Target Cost Versions

Use

The target cost version controls various parameters related to calculation of target costs invariance calculation. In variance calculation, target costs are needed as a comparison to theactual costs incurred.

Procedure


SAP R/3

Role Menu

Define Target Cost Versions

Transaction Code OKV6

IMG Menu Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Order -> Period End Closing -> Variance Calculation -> Define Target Cost Versions

2. Select “New entries” and enter the following values or copy from default settings of CoArea 0001 to BP01:

CoArea TgtCostVsn Text Variance Variant

BP01 0 Target Costs for Total Variances 001

BP01 1 Target costs for productionvariances

001

BP01 2 Target costs for planning variances 001

3. Leave the other entries as they are suggested (Control costs: Actual Costs, Target costs:Current std cost est) and save your entries.

.3.1.4.2.3 Create Settlement Profile

Use

The settlement profile controls various parameters related to settlement.

Prerequisites

Allocation Structure, PA Transfer Structure

Procedure


SAP R/3Role Menu

Create Settlement Profile







Controlling Product Cost by Sales Order Period-

End Closing Create Settlement Profile



Profile Text

YREM00 BP Repetitive Manufacturing

YREM

Actual costs/costs of sales

To be settled in full X

Can be settled

Not for settlement

Default Values

Allocation Structure A1

PA Transfer Struct. A1

Default object Type

Source Structure

Indicators

100% Validation X

%-Settlement X

Equivalence No’s X

Amount Settlement

Var. to co. bsd. PA

Valid receivers

G/L account N

Cost center O

Order O

WBS Element O

Fixed asset N

Material O

Network N

Profit. Segment N

Sales order O

Cost objects O

Order item O

Business proc. N





Real est. object N

Other parameters

Document type SA

Max.no.dist.rls 3

Residence time 3


Documents

J21_BB_ConfigGuide_EN_DE