Configuration MTO - Sales Order Processing with order BOM and OCM

1、Configuration MTO - Sales Order Processing with order BOM and OCM (665) EHP3 for SAP ERP 6.0June August 82000 ASK DokDatum ;Datum der Version; August 20002009EnglishEnglish Configuration MTO - Sales Order Processing with order BOM and OCM (665)SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf GermanyBuild

2、ing Block Configuration Guide IconsIconMeaningCautionExampleNoteRecommendationSyntaxTypographic ConventionsType StyleDescriptionExample textWords or characters that appear on the screen. These include Field names, screen titles, pushbuttons, as well as menu names, paths and options.Cross-references

3、to other documentation.Example textEmphasized words or phrases in body text, titles of graphics and tables.EXAMPLE TEXTNames 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 bo

4、dy text, for example, SELECT and INCLUDE.Example textScreen 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 TEXTKeys on the keyboard, for example, function ke

5、ys (such as F2) or the ENTER key.Example textExact 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 entrie

6、s. Copyright? Copyright 2009 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

7、 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 z1

8、0, 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, RETA

9、IN, 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, A

10、crobat, 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, Pro

11、gram 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

12、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, SAP Business ByDesign, and other SAP products and services mentioned herein as well

13、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 here

14、in as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this

15、 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 ki

16、nd, 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

17、constituting an additional warranty. Contents5Configuration MTO - Sales Order Processing with order BOM and OCM: Configuration Guide 51Purpose 52Preparation 52.1Prerequisites 52.1.1Building Blocks 53Configuration 53.1Product Cost Controlling 53.1.1Maintaining Settlement Profiles 73.2Sales and Distri

18、bution 73.2.1Defining Item Category Groups 73.2.2Maintaining Item Categories: All Parameters 83.2.3Defining Sales Document Types: All parameters 93.2.4Assigning Item Categories 103.2.5Assigning Schedule Line Categories 103.2.6Defining Requirements Classes 113.2.7Defining Requirement Types 123.2.8Det

19、ermining Requirement Types 123.2.9Maintaining Copying Control for Billing Documents 133.3Logistics Execution 133.3.1Defining Item Categories for Deliveries 143.3.2Defining Copy Control for Sales Documents to Delivery 153.4Shop Floor Control 153.4.1Defining Change Profile 163.4.2Defining Overall Chan

20、ge Profile 173.5Plant Maintenance/Customer Service 173.5.1Defining Serial Number Profile 193.6Production Planning 193.6.1Defining Control Key for Operations 203.6.2Defining Order Type 203.6.3Defining Order Type-Dependent Parameters 223.6.4Defining Production Scheduling Profile 223.6.5Defining Produc

21、tion Scheduler 223.6.6Defining Scheduling Parameters for Production Orders 233.6.7Defining Confirmation Parameters 243.6.8Defining Checking Control 253.7Controlling 253.7.1Assigning Costing Keys to Any Characteristics 264Master Data 264.1Creating Characteristic 374.2Creating Class 384.3Creating Mate

22、rial Master Data 524.4Creating Object Dependency 564.5Creating BOM 594.6Changing BOM: Assign Object Dependencies 614.7Creating Purchasing Info Record 624.8Creating Routing Finished Goods 654.9Assigning User Parameter CUQ 664.10Creating Configuration Profile 674.11Creating Condition Records: PR00 (Ma

23、terial) and VA00 (Variant Price) 694.12Assigning Pricing Conditions to Characteristic Values 724.13Assigning Costing Keys to Products Configuration MTO - Sales Order Processing with order BOM and OCM: Configuration GuidePurposeThis configuration guide provides the information you need to set up the

24、configuration of this building block manually.If you do not want to configure manually and prefer an automated installation process using eCATTs and BC Sets, use the SAP Best Practices Installation Assistant.PreparationPrerequisitesBuilding BlocksBefore you start installing this building block, you

25、must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_xx_EN_CN.xls; the placeholder xx depends on the SAP Best Practices version you use, e.g. IM&C refers to the SAP Best Practices IM&C Package: Prerequisites_Matrix_

26、IM&C_EN_CN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder.BBLibraryGeneral.ConfigurationProduct Cost ControllingMaintaining Settlement ProfilesUseIn the settlement profile, you define a range of control parameters for settlement. ProcedureAccess the ac

27、tivity using one of the following navigation options:Transaction codeOKO7IMG menuControlling?(?Internal Orders?(?Actual Postings?(?Settlement?(?Maintain Settlement ProfilesIf you access via IMG menu, choose Maintain Settlement Profiles on Choose Activity screen.On the Change 6View Settlement Profile

28、: Overview screen, select the settlement profile.This step and the following steps have to be repeated for each settlement profile. You can find the required entry data in the table below.Choose Details.On the Change View Settlement Profile: Details screen, make the following sets of entries:Field n

29、ameUser action / value: Settlement profile YIMT01Settlement profileYIMT01TextIM&C Production Order with CO-Actual costs cost of salesTo be settled in fullsetCan be settledNot for settlementDefault ValuesAllocation StructureY1PA Transfer str,Y1Default object typeORDIndicators100% validationset%-S

30、ettlementsetEquivalence numberssetAmount SettlementsetVar. to costing based PAsetValid ReceiversG/L accountSettlement optionalCost CenterSettlement optionalOrderSettlement optionalWBS elementSettlement optionalFixed AssetSettlement optionalMaterialSettlement optionalNetworkSettlement optionalProfit.

31、 SegmentSettlement optionalSales orderSettlement optionalCost objectsSettlement optionalOrder itemSettlement optionalBusiness proc.Settlement optionalReal Est.ObjectSettlement not allowedOther parametersDocument typeSAMax.no.dist. rls10Residence time3Choose Save and Back.ResultYou have created the s

32、ettlement profiles.Sales and DistributionDefining Item Category GroupsUseYou need the item category group to determine item categories. ProcedureAccess the activity using one of the following navigation options:Transaction codeSPROIMG menuSales and Distribution ( Sales ( Sales Documents ( Sales Docu

33、ment Item ( Define Item Category GroupsOn the Change View Maintain Item Category Groups in Material Master: Overview screen, create new item category groups by choosing New Entries. Make the following entries:Field nameUser action and valuesCommentItCGrYICG665 Item Category GrChoose Save.Maintaining

34、 Item Categories: All ParametersUseThe item categories influence price determination and the transfer of requirements, among other things. ProcedureAccess the activity using one of the following navigation options:Transaction codeSPROIMG menuSales and Distribution ( Sales ( Sales Documents ( Sales D

35、ocument Item ( Define Item CategoriesOn the Change View Maintain Item Categories: Overview screen, choose New Entries. Make the following entries:Field nameUser action and valuesCommentItem CategoryYICG665 Item Category GrBusiness ItemXYesSched. Line AllowedXYesBilling RelevanceADelivery related bil

36、ling documentWgth/Vol.relevantXYesPricingXItem is pricing relevantDetermine CostXStock value is calculated during pricingScreen Seq.GrpNConfig. Strategy01Sales Order Strategy (TAC, TAM)Structure scopeDConfiguration, poss. With BOM explosionChoose Save.Defining Sales Document Types: All parametersUse

37、In this step, you define the sales document types for scenario MTO with Sales Order BOM, Collective Orders, and OCM. Procedure Access the activity using one of the following navigation options:Transaction codeVOV8IMG menuSales and Distribution ( Sales ( Sales Documents ( Sales Document Header ( Defi

38、ne Sales Document TypesOn the Change View Maintain Sales Order Types: Overview screen, choose New Entries. Make the following entries:Field nameUser action and valuesCommentSales Document TypeYIMTStandardOrder-ConfigSD document categ.CSales orderNo. range int. assgt.01No. range ext. assg.02Item no.i

39、ncrement10Check division2ErrorsProbability100Output applicationV1SalesItem divisionXSelectRead info recordXSelectScreen sequence grp.AUSales orderTransaction group0Sales order0#ffff66Doc. pric. procedureAStandardDisplay RangeUALLAll itemsFCode for overv.scr.UER1Press ENTER to go to General OverviewP

40、rodAttr.messagesADialogDelivery typeLFOutbound deliveryDlv-rel.billing typeF2InvoiceOrder-rel.bill.typeF2InvoiceIntercomp.bill.typeIVInter company billingBilling block08Check Credit MemoCndType line itemsEK02Calculated costsBilling plan type01Milestone BillingPropose deliv. dateXSelectBilling reques

41、tDRDebit Memo RequestSubsequent Order TypeMissing other entriesChoose Save.Assigning Item CategoriesUseIn this step, you assign the item categories. The item category assigned depends on the sales document type and the item category group of the material, among other things. PrerequisitesDefinition

42、of sales document types, item categories, and item category types as described above.ProcedureAccess the activity using one of the following navigation options:Transaction codeSPROIMG menuSales and Distribution ( Sales ( Sales Documents ( Sales Document Item ( Assign Item CategoriesOn the Change Vie

43、w Item Category Assignment: Overview screen, choose New entries.Make the following entries:Field nameUser action and valuesCommentSales #ffff66Doc.TypeYIMTItem cat.groupYICGItem categoryYICGChoose Save.Assigning Schedule Line CategoriesUseIn this step, you assign schedule line categories to the defi

44、ned item categories. You do not need to define schedule line categories, since you can use the standard schedule line category CP. Prerequisites Definition of item categories as described above.Procedure Access the activity using one of the following navigation options:Transaction codeSPROIMG menuSa

45、les and Distribution ( Sales ( Sales Documents ( Schedule Lines ( Assign Schedule Line CategoriesOn the Change View Assign Schedule Line Categories: Overview screen, choose New entries. Make the following assignments:Field nameUser action and valuesCommentItem CategoryYICGPropSchdLneCat.CPMRPChoose

46、Save.Defining Requirements ClassesUseThe purpose of this activity is to define and maintain the requirement classes with which you control all functions relevant to requirements in logistics. Then you have to check the requirement classes to make sure that they meet the requirements of Cost Object C

47、ontrolling. Then in the next step you have to adapt the parameters in the requirements class that are relevant to cost accounting.Procedure Access the activity using one of the following navigation options:Transaction codeOVZGIMG menuSales and Distribution ( Basic Functions( Availability Check and T

48、ransfer of Requirements ( Transfer of Requirements( Define Requirements ClassesSelect requirement class 046 and copy it to Y46.Field nameDescriptionUser action and valuesCommentY46IM MMTO config. val.Choose Save.Check the requirements class with the following navigation options:Transaction codeSPROI

49、MG menuControlling ( Product Cost Controlling ( Cost Object Controlling ( Product Cost by Sales Order ( Control of Sales-Order-Related Production/Product Cost by Sales Order( Check Requirements ClassesOn the Change View Requirements Class for Costing and Account Assignment Overview screen, select th

50、e following entryField nameDescriptionUser action and valuesCommentY46IM MMTO config. val.Choose Details and make the following entries:Field nameDescriptionUser action and valuesCommentCostingCosting IDBDetermination Method1Costing VariantYISCCosting Sheet Blank (delete entry)Assembly/RequirementsA

51、ssembly typeNo changesAccount assignmentAcc. Assignment Cat.M (check)ValuationM (check)The remaining fields must be blank.Choose Save.Defining Requirement TypesUseThe requirements type determines the planning strategy to be used for a particular requirement. Procedure Access the activity using one of the following navigation options:Transaction codeOVZHIMG menuControlling ( Product Cost Controlling ( Cost Object Controlling ( Product Cost by Sales Order ( Control of Sales-Order