154_BPP_FM_EN_US

EHP4 for SAP ERP 6.0

June 2010

English

Prerequisite Process Steps (154_FM)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Prerequisite Process Steps (154_FM): BPD

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.

© SAP AGPage 2 of 29


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....................................................................................................................................... 62 Prerequisites................................................................................................................................ 6

2.1 Master Data and Organizational Data..................................................................................62.2 Business Conditions............................................................................................................72.3 Preliminary Steps................................................................................................................. 72.4 Roles.................................................................................................................................... 7

3 Process Overview Table..............................................................................................................84 Process Steps.............................................................................................................................. 9

4.1 Roll MM Period to Current Period........................................................................................94.2 Product Costing: Costing Run............................................................................................104.3 Product Costing: Costing Run for Configured Materials.....................................................124.4 Create Product Cost Collectors..........................................................................................144.5 Preliminary Cost for the Product Cost Collector.................................................................154.6 Set Up Planning File Entry.................................................................................................164.7 Routings: Material Update.................................................................................................174.8 Run Materials Requirements Planning (MRP)...................................................................184.9 Prepare Assets for Manufacturing Cost Centers................................................................194.10 Create Missing Parts Index................................................................................................214.11 Define Release Procedure for Purchase Orders................................................................224.12 Define Tolerance Groups for Employees...........................................................................234.13 Additional Activities for DIMP Activation............................................................................244.14 Valuation and Account Assignment (DIMP system ONLY)................................................254.15 Creating SD Routine 600 for Condition Value Profit margin % and assign to Pricing Procedure (Optional Step).............................................................................................................26

5 Appendix.................................................................................................................................... 285.1 Reversal of Process Steps.................................................................................................285.2 Costing Error...................................................................................................................... 29



Prerequisite Process Steps

1 PurposeThis Business Process Documentation contains process steps that have to be done as prerequisite before you can start to work through the standard Business Process Documentation of selected logistics scenarios.

2 Prerequisites2.1 Master Data and Organizational Data

Default ValuesEssential master data (that suits its operational focus, for example, master data for materials, vendors, and customers) and organizational data (such as the data that reflects the organizational structure of your company) are created in your ERP system in the implementation phase..The business process is enabled with this organization-specific master data, examples are provided in the next section.

Additional Default ValuesYou can test the scenario with other SAP Best Practices default values that have the same characteristics.Check your SAP ERP system to find out which other material master data exists.

Using Your Own Master DataYou can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Service

Manufacturing Area / Trading Area



Master data Value Master data details

Comments

Material * Material Type ROH, HALB, FERT

Costing Run only for these Material Types in Plant 1000

* means all possible values.

2.2 Business Conditions This building block is required for the use of SAP Best Practices scenarios in a demo environment. This data is required for the scenarios and do not exist directly after activation. The following process steps describe all necessary steps required for creating the required transactional data.

This scenario is not relevant for usual business operations,

2.3 Preliminary Steps

2.4 RolesUseThe 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.

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

Business role Technical name Process step

Employee (Professional User)

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

General Ledger Accountant

SAP_NBPR_FINACC-S Roll MM Period to Current Period (MMPV)

Product Cost Controller

SAP_NBPR_PRDCOST_CONTRLR-S

Costing Run (CK40N)

Costing Run for Configured Materials (CK40N)

Create Product Cost Collectors (KKF6M)

Preliminary Cost for Product Cost Collectors (MF30)

Production Planner SAP_NBPR_PRODPLANNER-S Set Up Planning File Entry



Business role Technical name Process step

(MDAB)

MRP Run in Batch (MDBT)

Engineering Specialist

SAP_NBPR_ENGINEER-S Routings: Material Update

Assets Accountant SAP_NBPR_ASSET-S Create Asset Master Data

Asset: Acquisition with Automatic Offsetting Entry

IT Administrator(Professional User)

SAP_NBPR_IT_ADMIN-S Create Missing Parts Index

3 Process Overview Table

Process step External process reference

Business condition

Business role Trans-action code

Expected results

Roll MM Period to Current Period

General Ledger Accountant

MMPV

Product Costing: Costing Run


CK40N

Product Costing: Costing Run for Configured Materials


CK40N

Create Product Cost Collectors


KKF6M

Preliminary Cost for the Product Cost Collector


MF30

Set Up Planning File Entry

Production Planner

MDAB

Routings: Material Update

Engineering Specialist

CA97

Run Materials Requirements Planning (MRP)

Production Planner

MDBT

Asset: Create Asset Master

Assets Accountant

AS01

Asset: Acquisition with Automatic

Assets ABZON



Process step External process reference

Business condition

Business role Trans-action code

Expected results

Offsetting Entry Accountant

4 Process Steps4.1 Roll MM Period to Current PeriodUse

Perform this activity only if the MM period in the system is not set to the current period. This activity has to be done monthly.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP System Menu Logistics Materials Management Material Master Other Close Period

Transaction Code MMPV

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role General Ledger Accountant(SAP_NBPR_FINACC-S)

Business role menu General Ledger Periodic Processing Closing Periods Close Period for Material Master

2. On the Close Period for Material Master Records screen, make the following entries:

Field name Description User action and values Comment

From company code

Enter the company code.

1000 (for example)

Period Enter the current period.

<current month>

Fiscal year Enter the current fiscal year.

<current fiscal year>



2. Choose Execute.

4.2 Product Costing: Costing RunUseThe purpose of this activity is to perform product costing.

This step can only be executed if product cost planning is activated.

IMG (SPRO) Controlling Product Cost Controlling Product Cost Planning Basic Settings for Material Costing Define Cost Component Structure

Transaction Code OKTZ

Check, that the cost component structure Y1 (BP Cost Component Layout) exists.

Procedure Plant 10001. Access the activity using one of the following navigation options:


SAP System Menu Logistics Production Product Cost Planning Material Costing Costing Run Edit Costing Run

Transaction Code CK40N


Business role Product Cost Controller (SAP_NBPR_PRDCOST_CONTRLR-S)

Business role menu Product Cost Controlling Product Cost Planning Edit Costing Run

2. On the Edit Costing Run screen, in the Costing Run field, enter NT001. 3. Enter the Costing Run Date.

4. Choose Create.5. Enter a description.6. On the Costing Data tab page, enter the following data and choose Enter:

Field name User action and values

Costing variant YPC1

Costing Version 01

Controlling Area 1000

Company Code 1000



7. On the Dates tab page, enter the following:


Costing Date from Today's date

Costing Date to 12/31/<current year>

Valuation Date Today's date

Qty Structure Date Today's date

8. Choose Save.9. In the Create Cost Estimate table, for each row, there is a Change Parameter button in the

Parameters column. Choose the one in the Selection row and enter the following data:


Material Type ROH, HALB, FERT

Plant 1000

Background Processing Deselect

10. Choose Save and then choose Back.

11. Choose Execute that appears in the Parameter column and the status light for this row would turn green.

12. For the Struct. Explosion row, choose the Change Parameter button. Deselect Background Processing and choose Save. Choose Back.


14. Repeat these steps for the Costing row.15. Choose Costing Results.16. If you get error in some material, refer to section 5.2 of the Appendix for explanation 17. If the status light for this row is not Green then review the Costing levels report. and correct

errors in the report. Rerun the Costing if necessary.

18. On the Row Analysis screen, choose SAP&11 for the parameter setting then choose Execute.

19. On the row with Marking, choose Lock.20. On the Price Update: Organizational Measure screen, select the row with company code 1000.21. On the dialog box, enter the Costing variant YPC1 and the Costing version of 1, and then choose

Enter. The status light of the row would turn green.

22. Choose Save.

23. Choose Back.24. Choose Change Parameter and deselect Test Run and Background Processing.

25. Choose Save.

26. Choose Back and then choose Execute.27. Repeat steps 23 to 25 for the Release row.

Procedure Plant 11001. Repeat above steps for plant 1000 with following selection and costing run name NT010:




Material Type FERT

Plant 1100


4.3 Product Costing: Costing Run for Configured MaterialsUse

You only have to execute this activity if you have the following scenario in scope: MTO-Order Processing with Variant Configuration (147) or Make-to-Order (Multilevel Production) with Variant Configuration and Sales Order Costing (357)




PrerequisitesCheck that the cost component structure Y1 (BP Cost Component Layout) exists.

Procedure Plant 10001. Access the activity using one of the following navigation options:


SAP System Menu Logistics Production Product Cost Planning Material Costing Costing Run Edit Costing Run

Transaction Code CK40N


Business role Product Cost Controller (SAP_BPR_PRDCOST_CONTROLLER-K)


2. On the Edit Costing Run screen, in the Costing Run field, enter NT002.

3. Enter the Costing Run Date.



4. Choose Create.5. Enter a description.

6. On the Costing Data tab page, enter the following data:


Costing variant YPC1

Costing Version 1

Controlling Area 1000

Company Code 1000

7. On the Dates tab page, enter entries in the following fields:


Costing Date from Today's date

Costing Date to 12/31/<current year>

Valuation Date Today's date

Qty Structure Date Today's date

8. Choose Save.

9. In the Create Cost Estimate table, for each row there is a Change Parameter button in the Parameters column. Choose the one in the Selection row and enter the following data:


Material Type ROH, HALB, HAWA, FERT

Plant 1000

Select configured materials only Selected

Background Processing Deselected

10. Choose Save, and then choose Back.


12. For the Struct. Explosion row, choose Change Parameter. Deselect Background Processing then choose Save, and then choose Back.


14. Repeat steps for the Costing row.15. Choose Costing Results.16. If the status light for this row is not Red then review the Costing levels report. and correct errors

in the report. Rerun the Costing if necessary.

17. On the Row Analysis choose SAP&11 for the parameter setting then choose Execute.18. On the row with Marking, choose Lock.19. On the Price Update: Organizational Measure screen, select the row with company code 1000.20. In the dialog box, enter the Costing variant of YPC1 and the Costing version of 1, and then



choose Enter. The status light of the row will turn green.

21. Choose Save.

22. Choose Back.23. Choose Change Parameter and de-select Test Run and Background Processing.

24. Choose Save.

25. Choose Back, then choose Execute.26. Repeat steps 23 to 25 for the Release row.

Procedure Plant 11001. Repeat above steps for plant 1000 with following selection and costing run name NT011:


Material Type FERT

Plant 1100


4.4 Create Product Cost CollectorsUseIn this step, you create the product cost collector.

You only have to execute this activity if you have the following scenario in scope: Repetitive Manufacturing (149)





Procedure 1. Access the transaction choosing the following navigation option:


SAP System Menu Logistics Production Repetitive Manufacturing Master



Data Product Cost Collector Collective Entry

Transaction Code KKF6M



Business role menu Product Cost Controlling Product Cost Planning Create Multiple Product Cost Collectors for Production Versions

2. On the Create Multiple Cost Collectors for Production Versions screen, enter the following values:


Plant 1000

Order type YBMR

Only Repetitive Mfg Mat'

Select

3. Choose Execute.

4. Choose Exit.

4.5 Preliminary Cost for the Product Cost CollectorUseIn this step, you create preliminary cost for the product cost collector.

You only have to execute this activity if you have the following scenario in scope: Repetitive Manufacturing (149)





Procedure



1. Access the transaction choosing the following navigation option:Option 1: SAP Graphical User Interface (SAP GUI)

SAP Menu Accounting Controlling Product Cost Controlling Cost Object Controlling Product Cost by Period Planning Preliminary Costing for Product Cost Collector

Transaction code MF30



Business role menu Product Cost Controlling Product Cost Planning Creation of Preliminary Cost Estimates for Product Cost Collectors

2. On the Creation of Preliminary Cost Estimates for product Cost Collectors screen, make the following entries:


Costing Date Enter today’s date. <current date> Example

Plant 1000

3. Choose Execute.

4.6 Set Up Planning File EntryUse

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


SAP System Menu Logistics Production MRP Planning Total Planning As Background JoborLogistics Materials Management Material Requirements Planning (MRP) MRP Planning Planning File Entry Set Up in Background

Transaction Code MDAB


Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production Job Planning Planning File - Set Up BATCH



2. On the Set Up planning file entry: Variants screen, choose Variant.3. On the ABAP: Variants dialog box, in the Create Variant field, enter Y1000 and choose Create.4. On the Variants: Change Screen Assignment screen, select the Full screen row, then choose

Continue.5. On the Maintain Variant screen, enter the following information:

Field Value

Plant 1000

6. Choose Attributes.7. On the Variant Attributes screen, in the Meaning field, enter MRP Plant 1000. 8. Choose Save.9. Choose Back.10. On the Set Up planning file entry: Variants screen, choose the Start immediately.

To check the results, choose Display Scheduling. Select an entry and choose Result and then display the content of the spool request.

11. Repeat the above steps for plant 1100 to create variant Y1100.

4.7 Routings: Material UpdateUseThe purpose of this activity is to update lot size dependent scheduling data in the material master record (mass processing)

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


SAP ECC Menu Logistics Production Master Data Routings Extras Material Master Schedule Material Master

Transaction code CA97

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

Business role (Name) Engineering Specialist (SAP_NBPR_ENGINEER-S)

Business role Menu Engineering Master Data Material Master Update Material Master

2. On the Initial Screen, enter plant 1000 and select Update material master directly checkbox.

On the initial screen, enter either a material number or a production scheduler. Entering the production scheduler without a material would allow you to update all materials for a given scheduler at the same time.

3. Choose Enter. The materials would be updated in the background.



ResultMaterial master work scheduling data is updated with routing information.

4.8 Run Materials Requirements Planning (MRP)UseThe purpose of this activity is to create and schedule a job for a periodic MRP run.



SAP System Menu Logistics Production MRP Planning Total Planning As Background Jobor Logistics Materials Management Material Requirements Planning (MRP) MRP Planning Total Planning As Background Job

Transaction Code MDBT


Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production Job Planning MRP Run In Batch

2. On the Total Planning: Variants screen, choose Variant.3. On the ABAP: Variants dialog box, in the Create Variant field, enter Y1000 and choose Create.4. On the Variants: Change Screen Assignment screen, select the Full screen row, then choose

Continue.5. On the Maintain Variant screen, enter the following information:

Field Value

Processing Key NEUPL

Plant 1000

Create purchase req. 1

Schedule lines 3

Create MRP List 1

Planning Mode 3

Scheduling 2

Planning date <current date>



Field Value

Display material list Selected

Parallel processing Selected (this needs to be selected only if you do parallel MRP processing)

6. Choose Attributes.7. On the Variant Attributes screen, in the Meaning field, enter MRP Plant 1000. 8. On the Object for selection screen - planning date row, choose selection variable D by using F4-

help and Name of variable Current date by using F4-help 9. Choose Save.10. Choose Back.11. On the Total Planning: Variants screen, select the variant and then choose Schedule Job.12. On the Total Planning Scheduling: Start Time screen, choose Schedule Periodically.13. On the Period Duration dialog box, select weeks and choose Create.14. Repeat the above steps for plant 1100 to create variant Y1100.

ResultYou have created and scheduled a job for an MRP run.

Instead of creating job for each plant it is possible to create one job for all plants. In this case, use scope of planning YB01 and leave the field plant empty.

4.9 Prepare Assets for Manufacturing Cost CentersUseAssets are created for manufacturing cost centers. The assets are needed for scenarios located in the library.

This step can only be executed if the manufacturing cost centers exist. Execute transaction KS02 and check that cost center 1301 exists.

Prerequisites Cost Center 1301 exists (transaction KS02).

4.9.1 Create Asset Master Data



SAP System Menu

Accounting Financial Accounting Fixed Assets Asset Create Asset

Transaction code

AS01



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

Business role (Name)

Assets Accountant (SAP_NBPR_ASSET-S)

Business role Menu

Asset Accounting Master Data Assets Create Asset Master Record

2. On the Create Asset: Initial screen, provide the necessary data and select Master Data:


Asset class Number of the asset class 2000

Company Code #1000

3. On the Create Asset: Master Data screen, make the following sets of entries on register tab General and register tab Time-Dependent and save:

Asset num. Asset class

Description asset class

Description Cost center

Register tab General Register tab Time-dependent

<internal number>

2000 Machinery Hammer drill device Hilti 22 XL

1301

<internal number>

2000 Machinery Compressed air - screwdriver 262

1301

80000 5000 Low-value assets Machinery

Floor cleaning machine 234

1301

Result The asset master record has been created under the number you specified in company code #1000.

4.9.2 Acquisition with Automatic Offsetting Entry

UseWith this transaction the asset can be posted automatically against the Clearing account fixed asset acquisition.



SAP system menu

Accounting Financial Accounting Fixed Assets Posting Acquisition External Acquisition Acquis. w/Autom. Offsetting Entry

Transaction code

ABZON




Business role Assets Accountant (SAP_NBPR_ASSET-S)

Business role menu

Asset Accounting Postings Day to Day Acquis. w/Autom. Offsetting Entry

2. On the Enter Asset Transaction: Acquis. w/Autom. Offsetting Entry screen, make the following entries for all assets created with previous step:

Field name Description User action and values

Comment

Existing Asset

<no. of the asset>

Number of the asset created with the previous step

Document Date

<document date>

for example, today

Amount Posted

<amount> for example, 1000 For Asset Class 5000 (low value asset) example amount in 500

Quantity <Quantity> Caution:The Quantity is necessary for the asset classes 2000for example, 1

Base Unit Base Unit of Measure

<Base Unit> Caution:The Base Unit is necessary for the asset classes 20000for example, EA

3. Post the document.

Result The asset has been capitalized with the amount specified. In the asset master record, the capitalization and depreciation start dates were set when the first acquisition was posted.

4.10 Create Missing Parts IndexUseThis report creates the missing parts index based on reservations and dependent requirements. The report is only necessary for using the Missing Parts Information System (transaction CO24).


SAP Graphical User Interface (SAP GUI)

SAP Menu Tools → ABAP Workbench → Development → ABAP Editor

Transaction code SE38




Business role IT Administrator (Professional User) (SAP_NBPR_IT_ADMIN-S)

NWBC Menu IT Administration Administration ABAP Workbench ABAP Editor

2. Enter program PPCOXPR1 and choose Execute (F8).

ResultThe index is created and the log is displayed. If the report was already executed there is an information message within the log.

4.11 Define Release Procedure for Purchase OrdersUseIn this activity you confirm the release procedure for purchase orders.

Procedure1. Access the transaction using one of the following methods:

IMG menu Material Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders

Transaction code

SPRO

2. Double-click Release Strategies.3. Select Release Prerequisites, and choose the Continue button.4. Select Release Statuses, and choose the Continue button.5. Choose Classification.6. On the Change View ”Release Strategies”: Classification screen, ensure the following entries

exists:

Field User Action or Values

Order type (Purchasing) Framework order

Standard PO

Stock Transfer Order

Total net order value > 500.00 USD

Purchasing Group Purchasing group 100

Purchasing group 101



7. Choose Back.8. Save your entries.



9. Choose Release Simulation.10. Choose Simulate Release.11. Choose Back.12. Choose Save, and then Exit.

ResultThe release procedure for purchase orders is defined.

4.12 Define Tolerance Groups for EmployeesUseIn this activity, you predefine various amount limits for your employees with which you determine:1. the maximum document amount the employee is authorized to post2. the maximum amount the employee can enter as a line item in a customer or vendor account3. the maximum cash discount percentage the employee can grant in a line item4. the maximum acceptable

Procedure1. Access the transaction using one of the following methods:

IMG menu Financial Accounting (New) Financial Accounting Global Settings (New) Document Tolerance Groups Define Tolerance Groups for Employees

Transaction code

SPRO

2. Double-click Company code #1000.3. On the Change View ”FI Tolerance Groups for Users”: Details screen, ensure the following

entries exists (you can also set the tolerance limits as required):

Field User Action or Values

Amount per document 9,999,999,999.00

Amount per open item account item 9,999,999,999.00

Cash discount per line item 5,000

Revenue (Amount) 5.00

Revenue (Percent) 2.0

Expense (Amount) 5.00

Expense (Percent) 2.0

4. Save your entries.5. Repeat the above steps for company code 1010 if you have activated Building block 216

Enterprise Structure extension.6. Choose Back.



4.13 Additional Activities for DIMP ActivationWhen your system is set up with the business function set for DIMP, the screen sequence used in transaction MM01 and MM02 changes from 21 to DI.To avoid problems with the eCATT of SAP Best Practices, the screen sequence control has temporarily been set to the value of SAP standard system: 21.Now you need to set this setting back to DI.

Only execute this step on a system where the business function set for DIMP has been activated. You can check this in transaction SWF5.

4.13.1 Change Screen Sequence Control

UseFor DIMP systems, you need to set the screen sequence to value DI.

Procedure1. Before you start the installation of SAP Best Practices, access the following IMG activity:

SAP IMG Logistics - General Material Master Configuring the Material Master Assign Screen Sequences to User/Material Type/Transaction/Industry Sector

Transaction Code OMT3E

2. On the Dialog structure, choose Screen Sequence Control. 3. In the Change view "Screen sequence control": Overview screen, maintain the following

entries:

Field name Description R/O/C User action and values

SRef: trans. Screen reference depending on the transaction R 01

SRef: user Screen reference depending on the user R *

SRef: matl type Screen reference depending on the material type R *

SRef: industry Screen reference depending on the industry sector R *

SRef: SSq Screen Sequence Number R DI

4. Choose Save.

ResultThe screen sequence control is set back to the value DI, which is the required value for DIMP systems.

Defining Number Range for Reprocessing Records (ONLY REQUIRED FOR DIMP SYSTEM)

Use



Create Number Range for Reprocessing Records.If you want to install and test baseline scenario 120 Returnables Processing


IMG menu Materials Management Returnable Packaging Logistics Number Ranges Define Number Ranges for Reprocessing Records

Transaction code ORLNR

2. On the Internal Number of Reprocessing Records screen, choose Change Intervals.3. On the Maintain Number Range Intervals screen, choose Insert interval (SHIFT+F1).4. On the Insert Interval screen, make the following entry:

Field name Description User action and values Note

No 01

From number 000000000001

To number 999999999999

Ext Blank

5. Choose Insert (Enter).6. Choose Save.

4.14 Valuation and Account Assignment (DIMP system ONLY)

UseIn DIMP system Account category reference for material type LEIH is incorrectly assigned as 0007 Ref. for nonvaluated material and should be changed to 0004 Reference for packagingThis change is taken care in BB 100 but this is just for reference

4.14.1 Define Valuation Classes

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

IMG Menu Materials Management Valuation and Account Assignment - Account Determination - Account Determination Without Wizard - Define Valuation Classes

Transaction Code OMSK

2. On the Account Category Reference/Valuation Classes screen, choose Valuation Class.3. On the Change View: "Account Category Reference/Material type": Overview, make the

following changes:

MTyp Aref Description

LEIH 0004 Reference for packaging



4.15 Creating SD Routine 600 for Condition Value Profit margin % and assign to Pricing Procedure (Optional Step)

UseThis is an optional step to display Profit Margin in Percentage (%) in SD Pricing procedure, perform following steps.

Procedure 4.15.1 Creating Routine 600

IMG menu Sales and Distribution System Modifications Routines Define Formulas For Pricing

Transaction code VOFM

Note that you can choose any number between 600 and 699 to create the routine as per your choice. When the routine is generated, the program names will also change with the routine name in the suffix..

1. Select Formulas- Condition Values2. On Maintain: Formulas Condition value enter value as follow:

Routine number: 600Description: Profit margin %

3. Enter twice and ignore any information message4. In Prompt for transportation workbench request provide your request number and enter5. Select new created routine number 600 and select Source code (F5)6. On ABAP Editor: Change Include RV64A600 enter code as following:

FORM FRM_KONDI_WERT_600.* Profit margin%* xkwert = ( ( komp-netwr - komp-wavwr ) / komp-netwr ) * 100. DATA: MARGIN(16) TYPE p DECIMALS 2. XKWERT = KOMP-NETWR - KOMP-WAVWR. XKOMV-KRECH = 'A'. MARGIN = XKWERT * 100000 / KOMP-NETWR. XKOMV-KBETR = MARGIN.ENDFORM.

7. Choose Check (Ctrl+F2)8. Choose Program -Generate and if you get any message select yes9. Select Activate (Ctrl+F3)and go back10. On Maintain: Formulas Condition Value select routine number 60011. Choose Edit-Activate and enter Workbench Request on Prompt



Go to Transaction SE381. On Screen ABAP Editor: Initial Screen enter Program FV64A352 and select Change2. Ignore any information message3. On Screen ABAP Editor: Change Include FV64A352 select Program - Generate4. Now Select button Activate (Ctrl+F3) and go back

4.15.2 Assign Routine 600 to Pricing Procedure

IMG menu Sales and Distribution Basic Functions Pricing Pricing Control Define and assign Pricing Procedure

Transaction code SPRO

1. On Choose Activity select Maintain pricing procedures2. On Change View "Procedures": Overview select Procedure YMNFCH and double click on

Control data3. Select New Entries and enter as follow:

Step : 960Counter: 0Description: Profit Margin %CalType : 600 and choose enter and back

Save your entry

Note: If you want to view Profit margin in %, this routine can be used in other Pricing Procedures



5 Appendix5.1 Reversal of Process Steps

Create costing run Transaction code ( SAP GUI) CK44

Reversal: Delete Costing Run

Transaction code ( SAP GUI) CK44


Business role menu Product Cost Controlling Product Cost Planning Delete Costing Run

Comment Important: Only delete a costing run if the calculations are not needed.

Release standard cost estimate and revalue stock at start of new fiscal yearTransaction code ( SAP GUI) CK40N

Reversal: N/A

Transaction code ( SAP GUI) N/A



Comment Once a standard price is released, the stocks are revaluated and it is almost impossible to change it. You would have to delete the standard cost estimate, create a new cost estimate, select, and release it.



Change Material Master - Routings: Material UpdateTransaction code ( SAP GUI) MM02

Reversal: Change Material

Transaction code ( SAP GUI) MM02

Business role Engineering Specialist

Business role menu Engineering Material Master Change Material

Comment Transaction CA97 updates lot size dependent scheduling data on the work scheduling view and removes the lot size independent scheduling data (field: In-house production) You can change the data and change back if required

5.2 Costing Error

Material Reason

S24Material is created in BB 143 which is part of solution but BOM and routing are created in 146 which is not in scope

F29Material is created in BB 143 which is part of solution but BOM and routing are created in 146 which is not in scope

S240-1Material is created in BB 243 which is part of solution but BOM and routing are created in 232 which is not in scope

YM2000-999YM2000-999 is second class material required in QM and does not have BOM and routing

F235-1

Material is created in 243 which is in scope but Cost apportionment or Equivalence Numbers for coproduct is created in BB 235 which is not in scope

F235-2

Material is created in 243 which is in scope but Cost apportionment or Equivalence Numbers for coproduct is created in BB 235 which is not in scope


Date post:	25-May-2017
Category:	Documents
Upload:	chrisvyas125
View:	237 times
Download:	9 times

154_BPP_FM_EN_US

Documents