You are on page 1of 15

EHP7 for SAP ERP 6.

0
September 2013
English

Sales of Nonstock Item
with Order Specific
Procurement (115)
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. All rights reserved. which speak only as of their dates. or to develop or release any functionality mentioned therein. products. and they should not be relied upon in making purchasing decisions. © SAP SE Page 3 of 8 . or any related presentation. Please see http://global. without representation or warranty of any kind. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only. code. Readers are cautioned not to place undue reliance on these forward-looking statements. and SAP SE’s or its affiliated companies’ strategy and possible future developments. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. or legal obligation to deliver any material. The information in this document is not a commitment. This document. and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. Nothing herein should be construed as constituting an additional warranty.sap. if any.com/corporate-en/legal/copyright/index. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries.epx#trademark for additional trademark information and notices. In particular. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. or functionality. and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. promise.SAP Best Practices Sales of Nonstock Item with Order Specific Procurement (115): Configuration Guide Copyright © 2014 SAP SE or an SAP affiliate company. SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services.

These include field names. EXAMPLE TEXT Keys on the keyboard. Pointed brackets indicate that you replace these words and characters with appropriate entries. function keys (such as ENTER key. These are words or characters that you enter in the system exactly as they appear in the documentation. upgrade and database tools. table names. SELECT and INCLUDE. screen titles. These include report names. titles of graphics and tables. for example. and individual key words of a programming language. source code. <Example text> Variable user entry. for example. Cross-references to other documentation. Example text Emphasized words or phrases in body text. © SAP SE F2) or the Page 3 of 8 . when surrounded by body text. This includes file and directory names and their paths.SAP Best Practices Sales of Nonstock Item with Order Specific Procurement (115): Configuration Guide 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. Example text Exact user entry. program names. transaction codes. messages. pushbuttons as well as menu names. Example text Screen output. paths and options. names of variables and parameters as well as names of installation. EXAMPLE TEXT Names of elements in the system.

......................14 © SAP SE Page 6 of 8 ............3............................................. Types Using Transaction.....2 Maintaining Copy Control for Sales Documents (Header and Item)............................................. to Billing Doc................1 Creating Requirement Classes........................6 3..........................................................................................................4................3 Defining Requirements Types........................................8 3...1 Defining Item Categories for Deliveries.................... 7 3.... 5 2 Prerequisites.............................................................................................................3...................................................1...................................................................4.............7 Transfer of Requirements.....SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement Contents Sales of Nonstock Item with Order Specific Procurement...2 Maintaining Requirements Classes for Costing/Account Assignment.............................................................1 Sales: General..3 Assigning Schedule Line Categories.........................2 Schedule Lines.............2.................4........10 3................4...................................10 3............. 5 3 Configuration..............................................................4 Determining Req......12 3..............1.................................. 10 3..............................................................1 Assigning Item Categories........................4 Delivery..........................7 3..3..........................3 Specifying Copy Control for Deliveries ..................................................... 5 3..........................................5 1 Purpose............................................5 3.11 3...........................9 3...................4 Maintaining Copying Control for Billing Doc...........................................................12 3......................... 7 3..5 Maintaining Copying Control: Billing Doc.1 3.... 5 3........4............................2 Defining Item Category Determination in Deliveries............3.............................................................................................................................Item.........

SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement Sales of Nonstock Item with Order Specific Procurement 1 Purpose This configuration guide provides the information that you need to manually set up configuration of this building block.1 Assigning Item Categories Use The purpose of this activity is to assign the item categories to the sales order type OR.xls. refer to the SAP Best Practices Quick Guide. [yy] depends on the language version. In the sales order. the placeholder [xx] depends on the SAP Best Practices version you use. On the New Entries: Details of Added Entries screen make the following entries: © SAP SE Page 6 of 8 . for example. see the Building Block Prerequisite Matrix (Prerequisites_Matrix_[xx]_[yy]_ [zz]. 2 Prerequisites Before you start installing this building block.. Access the activity using the following navigation option: Transaction code VOV4 IMG menu Sales and DistributionSalesSales DocumentsSales Document ItemAssign Item Categories 2. 3 Configuration 3. Alternatively up to three further item categories can be assigned. ([xx] depends on the SAP Best Practices version and [zz] depends on the country version). choose New Entries.\ [xx]_[zz]\Documentation\. PK for Pakistan: Prerequisites_Matrix_BL_EN_PK. For more information. for example. 3. the default item category can be replaced manually by the alternative item categories.xls).1. EN for English language. for example. and [zz] depends on the country version. On the Change View “Item Category Assignment”: Overview screen. BL refers to the SAP Best Practices Baseline Package. It is possible to define a default item category that will be determined automatically in the sales order (depending on the item category of the material). Procedure 1. If you do not want to configure manually and prefer to use an automated installation process using BC Sets and other tools. you must install prerequisite building blocks.1 Sales: General 3. This document can be found in the SAP Best Practices documentation package in the folder .

SAP Best Practices Configuration Guide Field name Sales of Nonstock Item with Order Specific Procurement Description User action and values Sales Doc. Mark the line of your selected sales document types. Enter OR in both input fields SalesDocType in the Another entry dialog box. choose Copy Control: Sales Document to Sales Document. There is a maximum of three possible alternative item categories. On the Choose Activity selection screen.1. and double-click Item in the Dialog Structure. Choose Continue (Enter). 9. 4. 3. choose Position. Result The assignment of the item category YBAB to the sales order OR is done for the item category group YBUK. 8. 4. Procedure 1. 5. choose Display  Change (Ctrl + F1).2 Maintaining Copy Control for Sales Documents (Header and Item) Use The purpose of this activity is to ensure that the reference between document types OR works. 7. On the Change View “Header”: Overview screen. choose New Entries. On the Change View “Item”: Overview screen. Type OR Item cat. Access the activity using the following navigation option: Transaction code VTAA IMG menu Sales and DistributionSalesMaintain Copy Control for Sales Documents 2. 3. On the New Entries: Details of Added Entries screen make the following entries: Field name User action and values Comment Target SalesDoc Typ OR Standard Order From SalesDoc Type OR Standard Order ItemCat Propsal YBAB Bought-In Item © SAP SE Description Page 6 of 8 . Choose Save. group YBUK Item category YBAB Manual item cat DSI Comment You can also specify additional item categories to change the system default manually in the sales order. On the Display View “Header”: Overview screen. 6.

Choose Save. Access the activity using the following navigation option: Transaction code VOV5 IMG menu Sales and DistributionSalesSales DocumentsSchedule LinesAssign Schedule Line Categories 2. Result The item category YBAB can be used for copying from sales order type OR to sales order type OR. © SAP SE Page 6 of 8 . 3. 3.1 Assigning Schedule Line Categories Use The default schedule line category CB is used for bought-in scenarios. However. Choose Save. the default schedule line category CB will be used.data/item compl. it has to be assigned to the corresponding item category.2 Schedule Lines 3. On the New Entries: Details of Added Entries screen make the following entries: Field name Description User action and values Item category YBAB PropSchdLneCat. CB Comment 4. Procedure 1. On the Change View “Assign Schedule Line Categories”: Overview screen. 11. DataT 002 Partner item FPLA 251 Conditions Copying requirements 303 Copy schedule lines X Do not copy batch X Configuration A Pricing type A 10. Result When using the item category YBAB. choose New Entries. Confirm your entries by choosing Enter.2.SAP Best Practices Configuration Guide Field name Sales of Nonstock Item with Order Specific Procurement Description User action and values Comment Item Category YBAB Bought-In Item DataT 151 General item data DataT 102 Bus.

Access the activity using the following navigation option: Transaction code OVZG IMG menu Sales and DistributionBasic FunctionsAvailability Check and Transfer of RequirementsTransfer of Requirements Define Requirements Classes 2. 3. Procedure 1. 3.3 Transfer of Requirements 3.3. Result The requirement class YB4 has been created.3. On the Change View “Requirements Classes”: Overview screen. On the New Entries: Details of Added Entries screen make the following entries: Field name Description User action and values Comment Reqmts class YB4 Bought-In Availability X Req.SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement 3. choose New Entries. Procedure 1. It can also be used for configurable material (configuration = * for options).2 Maintaining Requirements Classes for Costing/Account Assignment Use The purpose of this activity is to add some parameters to meet the requirements of cost object controlling. transfer X Configureation * Special Stock E The indicator Configuration = * is required when you want to use configurable materials within this scenario. 4.1 Creating Requirement Classes Use The purpose of this activity is to create the requirement classes YB4 for the bought-in scenario. Access the activity using the following navigation option: Transaction code SPRO IMG menu Sales and DistributionBasic FunctionsAccount Assignment/CostingMaintain Requirements Classes For © SAP SE Page 6 of 8 . Choose Save.

Access the activity using the following navigation option: Transaction code OVZH IMG menu Sales and DistributionBasic FunctionsAvailability Check and Transfer of RequirementsTransfer of Requirements Define Requirements Types © SAP SE Page 6 of 8 .3. to use valuated sales order stock without a Costing object. 5. 7. change the field Account assignment category to E. On the Change View “Requirements Class for Costing and Account Assignment”: D screen make the following entries: Field name Description User action and values Reqmts class YB4 Assembly type 0 Acct Assignment Cat. On the Change View “Requirements Class for Costing and Account Assignment”: O screen. M Valuation M Settlement profile SD1 Results Analysis Key 000004 Comment In this case. Choose Continue (Enter). choose Position. Prerequisites Requirements class YB4 has been created.SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement Costing/Account Assignment 2. the account assignment category is M. 3.3 Defining Requirements Types Use The purpose of this activity is to create the requirement type YB4 and to assign it to requirement class YB4. Enter YB4 in the field Reqmts class in the Another entry dialog box. 4. Result The requirements class YB4 for costing/account assignment is created. 6. Procedure 1. On the Change View “Requirements Class for Costing and Account Assignment”: O screen. double-click the marked requirement class YB4. Choose Save. If you want to use the non-valuated sales stock (the field Valuation is blank) or to use sales order item to collect costs and revenues. 3.

Access the activity using the following navigation option: Transaction code OVZI IMG menu Sales and DistributionBasic FunctionsAvailability Check and Transfer of RequirementsTransfer of RequirementsDetermination Of Requirement Types Using Transaction 2. mark the line of item category YBAB. 4. On the New Entries: Overview of Added Entries screen make the following entries: RgTy Requirements type RegCl YB4 Bought-In YB4 4. 6. and choose Details (Ctrl + Shift + F2). 7. choose Position. 3. since determination using the strategy in the material master is not possible.4 Delivery © SAP SE Page 6 of 8 . Result The requirement type YB4 is assigned to item category YBAB.3. 8.4 Determining Req. 3. 3. On the Change View “Assignment of Requirement Types to Transaction”: Details screen make the following entries: Item Category Reqmts type YBAB YB4 Source 1 Reqmts class Availability Requirements YB4 X X The requirements type is determined using the strategy supply source = 1 (item category and MRP type strategy). Choose Save. 3.SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement 2. On the Change View “Requirements Types”: Overview screen. On the Change View “Assignment of Requirement Types to Transaction”: Overview screen. Types Using Transaction Use This is where you assign the item category (=business transaction) to the requirement type. Procedure 1. Choose Continue (Enter). Result The requirement type YB4 is created with relation to the requirement class YB4. 5. Choose Back (F3) twice. Enter YBAB in the field Item category in the Another entry dialog box. Choose Save. because the same material might be used for different business transactions (depending on the item category). and thus also to the requirements class. choose New Entries. On the Change View “Assignment of Requirement Types to Transaction”: Overview: screen.

choose New Entries.1 Defining Item Categories for Deliveries Use Due to the new item category YBAB in order processing. Choose Save. 3. the item category YBAB should be determined. J Mat no. 3. On the New Entries: Overview of Added Entries screen make the following entries: DlvT © SAP SE ItCG Usg. create the following delivery item category YBAB. Access the activity using the following navigation option: Transaction code SPRO IMG menu Logistics ExecutionShippingDeliveriesDefine Item Categories for Deliveries 2. choose New Entries. On the Change View “Delivery item category determination”: Overview screen. 3.4. On the Change View “Delivery item categories”: Overview screen.SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement 3. On the New Entries: Details of Added Entries screen make the following entries: Field name Description User action and values Item Category YBAB Document cat. Procedure 1.2 Defining Item Category Determination in Deliveries Use For the item category group YBUK.4. ItmC ItmC Page 6 of 8 . Result The delivery item category YBAB is created. Procedure 1. Access the activity using the following navigation option: Transaction code 0184 IMG menu Logistics ExecutionShippingDeliveriesDefine Item Category Determination in Deliveries 2. ’0’ allowed X Check quantity 0 A Check minimum qty A Relevant for picking X StLocation required X Determine SLoc X AutoBatchDeterm X Comment 4.

3. 4. Type LF Delivery Sales doc. Procedure 1. Choose Save. 6. Type OR Standard Order Item category YBAB Bought-In Item Order requirements 101 Item Item data 101 Item Business data 2 Business Data Update document flow X Pos. It is determined for the standard item and also for batch split items. © SAP SE Page 6 of 8 .SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement LF YBUK LF YBUK YBAB CHSP YBAB YBAB 4. Enter LF in the Delivery type input field and OR in the SalesDoc Type input field. choose Display  Change (Ctrl + F1). if batch managed materials should be used. 5. 3. quantity + 9. Access the activity using the following navigation option: Transaction code VTLA IMG menu Logistics ExecutionShippingCopy ControlSpecify Copy Control for Deliveries 2. choose Position. mark the first line. and double-click Item in the Dialog Structure. Result The copy control for deliveries has been defined. choose New Entries. On the Change View “Header”: Overview screen. On the Change View “Header”: Overview screen.3 Specifying Copy Control for Deliveries . Result The item category YBAB is determined for all materials with the item category group YBUK. 7. in the Another entry dialog box./neg. Choose Save.Item Use The purpose of this activity is to define the copy control for deliveries on item level. On the New Entries: Details of Added Entries screen make the following entries: Field name Description User action and values Comment Tgt Del. On the Change View “Item”: Overview screen.4. On the Display View “Header”: Overview screen. Choose Continue (Enter). 8.

Choose Save. 3. 11. choose Display  Change (Ctrl + F1). On the Change View “Header”: Overview screen. Use The new item category YBAB is integrated in the copy control from LF to F2/F8 on item level. On the Change View “Item”: Overview screen. quantity + Pricing Type G Note that the Billing quantity is set to G (Cumulative batch quantity minus invoiced quantity) to allow the billing of batch split items. 8. 4. Choose Copy control: Delivery document to billing document in the Choose Activity dialog box. choose New Entries.4 Sales of Nonstock Item with Order Specific Procurement Maintaining Copying Control for Billing Doc. On the New Entries: Details of Added Entries screen make the following entries: Field name Description User action and values Comment Target Bill. On the Change View “Item”: Overview screen. On the New Entries: Details of Added Entries screen make the following entries: Field name User action and values Comment Target Bill. 13.4. Back to the Change View “Header”: Overview screen. Double-click Item in the Dialog Structure. mark the line with billing type F8 (Tgt). mark the line with billing type F2 (Tgt). and delivery type (Source) LF in the Header dialog box. 12. 6. On the Display View “Header”: Overview screen. 9. 10. and delivery type (Source) LF in the dialog box Header.SAP Best Practices Configuration Guide 3. Type F2 Invoice From Delivery Type LF Delivery Item Category YBAB Bought-In Item Copying requirements 004 Deliv-related item Data VBRK/VBRP 001 Inv. 7. choose New Entries. Procedure 1. Double-click Item in the Dialog Structure. Access the activity using the following navigation option: Transaction code VTFL IMG menu Sales and DistributionBillingBilling DocumentsMaintain Copy Control For Billing Documents 2. 5. Type F8 Pro Forma Inv f Dlv From Delivery Type LF Delivery © SAP SE Description Page 6 of 8 . On the Change View “Header”: Overview screen.split (sample) Billing quantity G Pos/neg.

On the Change View: “Header”: Overview screen. mark the line with billing type F8 (Tgt) and delivery type (Source) LF in the dialog box Header. Save your settings. On the Change View: “Header”: Overview screen. On the Change View “Item”: Overview screen. 4. quantity Pricing Type G 14. choose New Entries. Choose Back (F3).SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement Item Category YBAB Bought-In Item Copying requirements 010 DlvRel. Double-click Item in the Dialog Structure. 3. 5.5 Maintaining Copying Control: Billing Doc. Procedure Carry out the following steps: 1. Choose Copying control: Billing document to billing document in the dialog box Choose Activity.4.pro forma itm Data VBRK/VBRP Billing Quantity D Pos./neg. Choose Save. mark the line with billing type G2 (Tgt) and delivery type (Source) F2 in the dialog box Header. 8. Result The Customizing settings for specifying the copy control of delivery documents to billing documents is maintained. Access the activity using one of the following navigation options: Transaction code VTFF IMG menu Sales and DistributionBillingBilling DocumentsMaintain Copying Control For Billing Documents 2. Field name Description User action and values Target Bill Type Credit Memo G2 Source Bill Type Invoice F2 Item Category YBAB Copying requirements 027 Pricing Type G Comment 6. to Billing Doc Use Integrate the new item category YBAB in the copy control from OR to L2/G2 in the item level so that the debit /credit memo processing can work. © SAP SE Page 6 of 8 . 3. 7.

Save your settings. choose New Entries.SAP Best Practices Configuration Guide Sales of Nonstock Item with Order Specific Procurement 9. Field name Description User action and values Target Bill Type Debt Memo L2 Source Bill Type Invoice F2 Item Category YBAB Copying requirements 027 Pricing Type G Comment 11. 12. Choose Back (F3) twice. 10. Double-click Item in the Dialog Structure. © SAP SE Page 6 of 8 . On the Change View “Item”: Overview screen.