212 bb config_guide_en_uk

507 views
421 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
507
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

212 bb config_guide_en_uk

  1. 1. EHP4 for SAP ERP6.0March 2010EnglishSales of Planned Services(212)SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block Configuration Guide
  2. 2. SAP Best Practices Sales of Planned Services (212): Configuration GuideCopyright© 2010 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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, 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, SystemStorage, 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 trademarksof 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 trademarksof 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 trademarksor registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C 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.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjectsExplorer, and other SAP products and services mentioned herein as well as their respective logos aretrademarks 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 wellas their respective logos are trademarks or registered trademarks of SAP France in the United Statesand in other countries.All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications mayvary.These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warrantyof any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. Theonly warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should beconstrued as constituting an additional warranty.© SAP AG Page 2 of 15
  3. 3. SAP Best Practices Sales of Planned Services (212): Configuration GuideIconsIcon MeaningCautionExampleNote or TipRecommendationSyntaxTypographic ConventionsType Style DescriptionExample 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, forexample, 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 theENTER 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.© SAP AG Page 3 of 15
  4. 4. SAP Best Practices Sales of Planned Services (212): Configuration GuideContentSales of Planned Services.......................................................................................................51 Purpose..................................................................................................................................52 Preparation............................................................................................................................52.1 Prerequisites...................................................................................................................53 Configuration..........................................................................................................................53.1 SD Settings.....................................................................................................................53.1.1 Define Item Categories.............................................................................................53.1.1.1 Define Sales Document Item Categories............................................................53.1.1.2 Assign Item Categories......................................................................................63.1.2 Schedule Line Categories.........................................................................................73.1.2.1 Define Schedule Line Categories.......................................................................73.1.2.2 Assign Schedule Line Categories.......................................................................73.1.3 Availability Check and Transfer of Requirements.....................................................83.1.3.1 Define Requirement Classes..............................................................................83.1.3.2 Check Requirement Class (CO).........................................................................93.1.3.3 Define Requirement Types.................................................................................93.1.3.4 Determination of Requirements Types Using Transaction...............................103.1.4 Set Up Copy Controls for Sales and Billing Documents..........................................103.1.4.1 Maintain Copy Control for Sales Documents....................................................103.1.4.2 Maintain Copy Control for Billing Documents...................................................123.2 CS Settings...................................................................................................................133.2.1 Maintain Plan Number............................................................................................133.3 Master Data...................................................................................................................143.3.1 Create Service Product for Maintenance Plan........................................................14© SAP AG Page 4 of 15
  5. 5. SAP Best Practices Sales of Planned Services (212): Configuration GuideSales of Planned Services1 PurposeThis configuration guide provides the information you need to set up the configuration of thisbuilding block manually.If you do not want to configure manually and prefer an automated installation process usingBC Sets and other tools, refer to the installation guide of this building block.2 Preparation2.1 PrerequisitesBefore you start installing this scenario, you must install prerequisite building blocks. For moreinformation, see the Building Block Prerequisites Matrix for SAP Best Practices BaselinePackage.3 Configuration3.1 SD Settings3.1.1 Define Item Categories3.1.1.1 Define Sales Document Item CategoriesUseIn this menu option, you define item categories for sales documents. The item categories thatare contained in the standard SAP system together with the sales document types representthe usual business transactions. We assign in this step the Billing Form and the DIP Profile.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Sales → Sales Document Item →Define Item CategoriesTransaction Code SPRO2. Activities; create the item category YBC1 with the following settings:© SAP AG Page 5 of 15
  6. 6. SAP Best Practices Sales of Planned Services (212): Configuration GuideFields YBC1Description SP: Contract ItemBusiness DataCompletion Rule CPricing XBusiness Item checkedWght/Vol.Relevant checkedDetermine Cost checkedTransaction FlowScreen Seq.Grp NPartnerDetermProced TTextDetermProcedure 01Item Cat.Stats.GroupControl of Resource-related Billing andCreation ofQuotationsBilling Form 02DIP Prof. YBR00099ResultThe Item Category YBC1 was created.3.1.1.2 Assign Item CategoriesUseIn this menu option, you can specify which item categories the system proposes duringdocument processing for each sales document type and item category group. At the sametime, you can specify additional item categories with which the system default can beoverwritten. There is a maximum of three possible alternative item categories.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Sales → Sales Documents → SalesDocument Item → Assign Item CategoriesTransaction Code VOV42. Assign Item Categories as shown in the table below:Sales Document Type Item Category Group Usage Default Item CategoryYBC1 YBLE YBC1YBDR YBLE SEIN L2N© SAP AG Page 6 of 15
  7. 7. SAP Best Practices Sales of Planned Services (212): Configuration GuideResultThe Item Category Assignment is finished.3.1.2 Schedule Line Categories3.1.2.1Define Schedule Line CategoriesUseIn this customizing activity we have to define schedule line categories for item categories.This allocation of schedule line categories is carried out depending on the MRP type that isspecified in the material master record for a material.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Sales → Schedule Lines → DefineSchedule Line categoriesTransaction Code SPRO2. On the Change View ‘Maintain Schedule Line Categories: Overview’ screen make thefollowing entries.SLCa DescriptionY9 SP: Contract Sched LResultThe definition of the schedule line category is done.3.1.2.2Assign Schedule Line CategoriesUseIn this customizing activity we have to assign schedule line categories to item categories. Thisallocation of schedule line categories is carried out depending on the MRP type that isspecified in the material master record for a material.PrerequisitesThe schedule line category Y9 has been created.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Sales → Schedule Lines → AssignSchedule Line categoriesTransaction Code SPRO2. On the Change View ‘Assign Schedule Line Categories: Overview’ screen make thefollowing entries.© SAP AG Page 7 of 15
  8. 8. SAP Best Practices Sales of Planned Services (212): Configuration GuideItCa Typ SchLCYBC1 Y9ResultThe assignment of the schedule line category Y9 to the item category YBC1 is done.3.1.3 Availability Check and Transfer of Requirements3.1.3.1Define Requirement ClassesUseRequirements class YB9 is primarily intended to allow sales documents to be linked to serviceorders. However, it also contains the default values for costing method, costing variant,settlement profile, and results analysis keys. These values all default into the sales order andfacilitate unit cost estimates, results analysis, and settlement.PrerequisitesThe settlement profile YBSV02 and results analysis key YBSV02 have been created.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Basic Functions → Availability Checkand Transfer of Requirements → Transfer of Requirements →Define Requirement ClassesTransaction Code OVZG2. Create requirement class YB9 as shown in the table below:CostingCosting Variant PC04Reqmts class YB9Description SP: w/o Serv Ord, RRAssemblySpecial Stock EOrder TypeAccount assignmentAcct Assign. Category ESettlmt. Profile YBSV02RA Key YBSV02Consumption EResultThe requirement class as a basic setting in SD was created.© SAP AG Page 8 of 15
  9. 9. SAP Best Practices Sales of Planned Services (212): Configuration Guide3.1.3.2 Check Requirement Class (CO)UseIn this step you check the requirements classes to make sure that they meet the requirementsof Cost Object Controlling.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Basic Functions → AccountAssignment/Costing → Maintain Requirements Classes ForCosting/Account AssignmentTransaction Code SPRO2. Select the Requirement Class YB9 and maintain them as shown in the table below:Requirement Class YB9Description SP: w/o Serv Ord, RRCostingCosting Variant PC04Account assignmentAccount assignment category ESettlement profile YBSV02Results Analysis Key YBSV02ResultIn this step you added the parameters in the requirements class that are relevant to costaccounting.3.1.3.3 Define Requirement TypesUseIn this activity you change or define requirements types which identify the differentrequirements, such as sales order requirements, delivery requirements or individual customerrequirements. The requirements types can be changed, for example, in order to representcustomer-specific terms.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Basic Functions → AvailabilityCheck and Transfer of Requirements → Transfer ofRequirements → Define Requirement TypesTransaction Code OVZH2. Create Requirement Type YBA and assign them to the Requirement Class as shown inthe table below:© SAP AG Page 9 of 15
  10. 10. SAP Best Practices Sales of Planned Services (212): Configuration GuideRqTy YB9Requirements type SP: w/o Serv Ord, RRRequirements class YB9Description SP: w/o Serv Ord, RRResultThe requirement type was created and assigned to the requirement class.3.1.3.4 Determination of Requirements Types UsingTransactionUseIn this activity you assign the item categories and MRP type to the requirements types.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Basic Functions → AvailabilityCheck and Transfer of Requirements → Transfer ofRequirements → Determination of Requirement TypesUsing TransactionTransaction Code OVZI2. Assign Requirements Types YBA to item categories as shown in the table below:Item Category Type Requirement Type Origin requirement typeYBC1 YB9 0 (Item type strategy)ResultThe requirement type YB9 was assigned to the item category YBC1.3.1.4 Set Up Copy Controls for Sales and BillingDocuments3.1.4.1 Maintain Copy Control for Sales DocumentsProcedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Sales → Maintain Copy Controlfor Sales DocumentsTransaction Code VTAA2. Double-click on copying control: Sales document to sales document if you are using theordinary IMG path. Otherwise use the transaction code VTAA to access the functionalitydirectly.© SAP AG Page 10 of 15
  11. 11. SAP Best Practices Sales of Planned Services (212): Configuration Guide3. Create copy controls for source document YBC1 to target document YBC1 copyingsettings for OR to OR. Include copy control for source item category YBC1.Header:Target Sales Doc.Type YBC1 (SP: SD-Contract)From Sales Doc.Type YBC1 (SP: SD-Contract)Copying req. for data transfer VBAK 051 (General header data)Copying req. for transferring business data 101 (Header business data)Copying req. for partner data VBPA 001 (Partner header)Copying requirements 002 (Header-diff.customer)VEDA 000Copy item number Not checkedComplete reference Not checkedItem:Target Sales Doc.Type YBC1 (SP: SD-Contract)From Sales Doc.Type YBC1 (SP: SD-Contract)Item Category YBC1 (SP: Contract Item)Copying req. for data transfer VBAP 151 (General item data)Copying req. for transferring business data 102 (Bus.data/item compl.)Copying req. for partner data VBPA 002 (Partner item)VEDA 000Copying req. for data transfer FPLA 251 (Conditions)Copying requirements 301Pricing type ACopy schedule lines CheckedUpdate document flow CheckedSchedule line:Target Sales Doc.Type YBC1 (SP: SD-Contract)From Sales Doc.Type YBC1 (SP: SD-Contract)SchdLneCatProposal Y9 (SP: Contract Sched L)Sched. Line Cat. Y9 (SP: Contract Sched L)DataT 201 (Gen.sched.line data)Copying requirements 501 (Scheduled qty > 0)4. Create copy controls for source document YBC1 to target document YBC1 copyingsettings for OR to OR. Include copy control for source item category YBC1.Header:Target Sales Doc.Type YBDR (SP: Debit Memo Req)From Sales Doc.Type YBC1 (SP: SD-Contract)Copying req. for data transfer VBAK 051 (General header data)Copying req. for transferring business data 101 (Header business data)Copying req. for partner data VBPA 001 (Partner header)Copying requirements 001 (Header-same customer)© SAP AG Page 11 of 15
  12. 12. SAP Best Practices Sales of Planned Services (212): Configuration GuideCopy item number checkedComplete reference Not checkedItem:Target Sales Doc.Type YBC1 (SP: SD-Contract)From Sales Doc.Type YBC1 (SP: SD-Contract)Item Category YBC1 (SP: Contract Item)Copying req. for data transfer VBAP 151 (General item data)Copying req. for transferring business data 102 (Bus.data/item compl.)Copying req. for partner data VBPA 002 (Partner item)Copying req. for data transfer FPLA 251 (Conditions)Copying requirements 303Pricing type GCopy schedule lines Not checkedUpdate document flow checkedSchedule line: no schedule line is needed for copying control from YBC1 to YBDR.ResultThe copy control for the sales documents YBC1 and YBDR has been accomplished.3.1.4.2 Maintain Copy Control for Billing DocumentsUseUsing requirements in copying control, you can specify how a sales document is to be billedwith regard to requirements.Procedure1. Access the activity using one of the following navigation options:IMG Menu Sales and Distribution → Billing → Billing Documents →Maintain Copying Control for Billing DocumentsTransaction Code VTFA2. Double-click on Copying control: Sales document to billing document, if you are using theordinary IMG path. Otherwise use the transaction code VTFA to access the functionalitydirectly.3. Define copy controls for source sales document YBDR to target billing document L2 bycopying settings for DR (debit memo request) to L2 (debit memo). Include copy controlsfor source item categories L2W, L2N and YBC1.Header:Target Billing Type L2 (Debit Memo)Source Sales Doc.Type YBDR (SP: Debit Memo Req)© SAP AG Page 12 of 15
  13. 13. SAP Best Practices Sales of Planned Services (212): Configuration GuideCopying requirements 001 (Header/order-related)Copy item number checkedItems:Target Billing Type L2 (Debit Memo)Source Sales Doc.Type YBDR (SP: Debit Memo Req)Item Category YBC1 (SP: Contract Item), L2N(Request), L2W (Request)Copying requirements 002 (Item/order-related)Data transfer VBRK/VBRP 002 (Ord-rel.credit memo)Billing quantity APos./neg. quantity +Pricing type D4. Define copy controls for source sales document YBC1 to target billing document L2 bycopying settings for DR (debit memo request) to L2 (debit memo). Include copy controlsfor source item categories L2W, L2N and YBC1.Header:Target Billing Type L2 (Debit Memo)Source Sales Doc.Type YBC1 (SP: SD-Contract)Copying requirements 001 (Header/order-related)Copy item number checkedItems:Target Billing Type L2 (Debit Memo)Source Sales Doc.Type YBC1 (SP: SD-Contract)Item Category YBC1 (SP: Contract ItemCopying requirements 002 (Item/order-related)Data transfer VBRK/VBRP 001 (Inv.split (sample))Billing quantity APos./neg. quantity +Pricing type DResultThe copy control for the sales documents YBDR and YBC1 to the billing document L2 hasbeen accomplished.3.2 CS Settings3.2.1 Maintain Plan NumberUseIn the following process you assign number range groups for maintenance plan. This processis needed to create a maintenance plan.© SAP AG Page 13 of 15
  14. 14. SAP Best Practices Sales of Planned Services (212): Configuration GuidePrerequisitesMaintenance plan type is available.Procedure1. Access the activity using one of the following navigation options:IMG Menu Plant Maintenance and Customer Service → MaintenancePlans, Work Centers, Task Lists and PRTs → MaintenancePlans → Define Number Ranges for Maintenance PlansTransaction Code SPRO1. Choose .2. Select Maintenance Plan Number.3. Position your cursor on the maintenance plan you want to assign (OC) in the NotAssigned area on the lower section of the screen.4. Choose (Select Element (F2)).5. Choose .6. Choose to save your entries.7. Confirm the dialog box Transport number range intervals with Continue (Enter).ResultMaintenance plan category is assigned.3.3 Master Data3.3.1 Create Service Product for Maintenance PlanUseIn this activity, you create the service product for use in the Maintenance plan. The serviceproduct is required to create the service order.Procedure1. Access the transaction using one of the following maintenance options:SAP ECC menu Logistics → Customer Service → Service Agreements →Environment → Sales and Distribution → Service Products forMaintenance PlansTransaction code OISF2. On the Create /process Service Products: Initial Screen choose New Entries and enterthe following data.© SAP AG Page 14 of 15
  15. 15. SAP Best Practices Sales of Planned Services (212): Configuration GuidePlPL ServiceProductType Mn.wk.ctr Plant M BusA Group GrC TLType1000 D102 SERV01 1000 1000 100000 2 A3. Save your settings.4. Choose Back.© SAP AG Page 15 of 15

×