115_BB_ConfigGuide_EN_MX.doc

EHP5 for SAP ERP 6.0

June 2011

English

Sales of Nonstock Item with Order specific Procurement (115)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Sales of Nonstock Item with Order specific Procurement (115): Configuration Guide

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.

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.

© SAP AG Page 2 of 16


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include 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.



Content

1 Purpose..........................................................................................................................5

2 Prerequisites..................................................................................................................5

3 Configuration..................................................................................................................5

3.1 Assigning Item Categories.......................................................................................5

3.2 Copying Control: Sales Document to Sales Document (Header and Item)..............6

3.3 Assigning Schedule Line Categories.......................................................................7

3.4 Creating Requirement Classes................................................................................8

3.5 Maintaining Requirements Classes for Costing/Account Assignment......................9

3.6 Defining Requirements Types...............................................................................10

3.7 Determining Requirement Types Using Transaction.............................................10

3.8 Defining Item Categories for Deliveries.................................................................11

3.9 Defining Item Category Determination in Deliveries..............................................12

3.10 Specifying Copy Control for Deliveries..............................................................13

3.11 Maintaining Copying Control Delivery Doc. to Billing Doc.................................14

3.12 Maintaining Copying Control: Billing Doc. to Billing Doc....................................15


SAP Best Practices Sales of Nonstock Item with Order Specific Procurement (115): Configuration Guide

Sales of Nonstock Item with Order Specific Procurement

1 PurposeThis configuration guide provides the information that you need to manually set up configuration of this building block.

If you do not want to configure manually and prefer to use an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide.

2 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excel file) is linked on the solution's DVD Web site in one of the following two locations:

Content Library

Site Map

3 Configuration3.1 Assigning Item Categories

UseThe purpose of this activity is to assign the item categories to the sales order type OR.

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). Alternatively up to three further item categories can be assigned. In the sales order, the default item category can be replaced manually by the alternative item categories.

ProcedureCarry out the following steps:

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

IMG Menu Sales and Distribution Sales Sales Documents Sales Document Item Assign Item Categories

Transaction Code SPRO

2. On the Change View ”Item Category Assignment”: Overview screen, choose New Entries.

3. On the New Entries: Details of Added Entries screen, make the following entries.

Field Name Description User action and values Comment

Sales Doc. Type OR

Item cat. Group YBUK



Field Name Description User action and values Comment

Item Category YBAB

You can also specify additional item categories to change the system default manually in the sales order.There is a maximum of three possible alternative item categories.

4. Save your settings.

5. Choose Back (F3) twice.

Result The assignment of the item category YBAB to the sales order OR is done for the item category group YBUK.

3.2 Copying Control: Sales Document to Sales Document (Header and Item)

UseThe purpose of this activity is to ensure that the reference between document types OR works.



IMG Menu Sales and Distribution Sales Maintain Copy Control for Sales Documents


2. On the Choose Activity selection screen, choose Copying Control: Sales Document to Sales Document.

3. On the Display View “Header”: Overview screen, choose Display Change (Ctrl+F1) to get the change mode.

4. On the Change View “Header”: Overview screen, choose Position.

5. Enter OR in both input fields SalesDocTyp in the dialog box Another Entry.

6. Choose Continue (Enter).

7. Double click Item in the Dialog Structure.

8. On the Change View “Item”: Overview screen, choose New Entries.


Field Name Description User Action and Values Comment

Target Sales Doc Typ

Standard Order OR




From Sales Doc Type

Standard Order OR

Item Cat Proposal

YBAB

Item Category YBAB

DataT 151

DataT 102

DataT 002

FPLA 251

Copying requirements

303

Copy schedule lines

X

Do not copy batch

X

Configuration A

Pricing Type A

10. Confirm your entries choosing Enter.



ResultThe item category YBAB can be used for copying from sales order type OR to sales order type OR.

3.3 Assigning Schedule Line Categories

UseThe default schedule line category CB is used for bought-in scenarios. However, it has to be assigned to the corresponding item category.



IMG Menu Sales and Distribution Sales Sales Documents Schedule Lines Assign Schedule Line Categories


2. On the Change View “Assign Schedule Line Categories”: Overview screen, choose New Entries.





Item category YBAB

PropSchdLneCat. CB



ResultWhen using the item category YBAB, the default schedule line category CB will be used.

3.4 Creating Requirement Classes

UseThe purpose of this activity is to create the requirement classes YB4 for the bought-in scenario. It can also be used for configurable material (configuration = * for options).



IMG Menu Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Define Requirements Classes

Transaction Code OVZG

2. On the Change View “Requirement Classes”: Overview screen, choose New Entries.



Reqmts. Class Bought-In YB4

Availability X

Req. transfer X

Configuration *

Special Stock E

The indicator Configuration = * is required when you want to use configurable materials within this scenario.





ResultThe requirement class YB4 has been created.

3.5 Maintaining Requirements Classes for Costing/Account Assignment

UseThe purpose of this activity is to add some parameters to meet the requirements of cost object controlling.



IMG Menu Sales and Distribution Basic Functions Account Assignment/Costing Maintain Requirements Classes For Costing/Account Assignment


2. On the Change View “Requirement Class for Costing and Account Assignment”: Details screen, choose Position.

3. Enter YB4 in the input field Reqmts class in the dialog box Another Entry.


5. On the Change View “Requirement Class for Costing and Account Assignment”: Details screen, double click the marked ReqCl YB4.

6. On the Change View “Requirement Class for Costing and Account Assignment”: Details screen, make the following entries.


Reqmts.class Bought-in YB4

Assembly Type 0

Acct assignment cat. M

Valuation M

Settlement profile SD1

Results Analysis Key 000004

In this case, the account assignment category is M, to use valuated sales order stock without a Costing object.

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, change the field Account assignment category to E.





ResultThe requirements class YB4 for costing/account assignment is created.

3.6 Defining Requirements Types

UseThe purpose of this activity is to create the requirement type YB4 and to assign it to requirement class YB4.

PrerequisitesRequirements class YB4 has been created.



IMG Menu Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Define Requirements Types

Transaction Code OVZH

2. On the Change View “Requirement Types”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

RgTy Requirements type RegC

YB4 Bought-In YB4



ResultThe requirement type YB4 is created with relation to the requirement class YB4.

3.7 Determining Requirement Types Using Transaction

UseThis is where you assign the item category (=business transaction) to the requirement type, and thus also to the requirements class.





IMG Menu Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements Determination Of Requirement Types Using Transaction


2. On the Change View “Assignment of Requirement Types to Transaction”: Overview screen, choose Position.

3. Enter YBAB in the input field Item category in the dialog box Another entry.


5. On the Change View “Assignment of Requirement Types to Transaction”: Overview: screen, make the following entries.

ItCa RgTy Requirements and description

YBAB YB4 Bought-In

6. On the Change View “Assignment of Requirement Types to Transaction”: Overview: screen, mark the line of item category YBAB and choose Details (Ctrl+Shift+F2).

7. On the Change View “Assignment of Requirement Types to Transaction”: Overview: screen, make the following entries.

Item Category Reqmts type Source Reqmts class

YBAB YB4 1 YB4

The requirements type is generally determined using the strategy supply source = 1 (item category and MRP type strategy), since determination using the strategy in the material master is not possible, because the same material might be used for different business transactions (depending on the item category).



ResultThe customizing settings to run the scenario Bought-In item are activated.

3.8 Defining Item Categories for Deliveries

UseDue to the new item category YBAB in order processing, create the following delivery item category YBAB.



IMG Menu Logistics Execution Shipping Deliveries Define Item Categories for Deliveries



Transaction Code OVLP

2. On the Change View “Delivery Item Categories”: Overview screen, choose New Entries.



Item category YBAB

Document Cat J

Mat no. “0” allowed X

Check quantity 0 A

Check minimum qty A

Relevant for picking X

StLocation required X

Determine SLoc X

AutoBatchDeterm X


5. Choose Back (F3).

ResultThe delivery item category YBAB is created.

3.9 Defining Item Category Determination in Deliveries

UseFor the item category group YBUK, the item category YBAB should be determined.

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

IMG Menu Logistics Execution Shipping Deliveries Define Item Category Determination in Deliveries

Transaction Code 0184

2. On the Change View “Delivery item category determination”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries.

DlvT ItCG Usg ItmC ItmC

LF YBUK YBAB

LF YBUK CHSP YBAB YBAB





Result The item category YBAB is determined for all materials with the item category group YBUK. It is determined for the standard item and also for batch split items, if batch managed materials should be used.

3.10 Specifying Copy Control for Deliveries

UseThe purpose of this activity is to define the copying control for deliveries on item level.



IMG Menu Logistics Execution Shipping Copying Control Specify Copy Control for Deliveries

Transaction Code VTLA

2. On the Change View “Header”: Overview screen, choose Position.

3. Enter LF in the input field Delivery type and OR in the input field SalesDoc Type in the dialog box Another entry.


5. On the Change View “Header”: Overview screen, mark the first line and double click Item in the Dialog Structure.



Target Del Type Outbound Delivery LF

Sales doc. Type Standard order OR

Item category YBAB

Order requirements

101

Item data 101

Business data 2

Update document flow

X

Pos./neg. quantity

+



ResultThe copying control for deliveries has been defined.



3.11 Maintaining Copying Control Delivery Doc. to Billing Doc.

UseStandard billing type F2 is used.

The new item category YBAB is integrated in the copy control from LF to F2/F8 on item level.



IMG Menu Sales and Distribution Billing Billing Documents Maintain Copying Control For Billing Documents

Transaction Code VTFL

2. Choose Copying control: Delivery document to billing document in the dialog box Choose Activity.

3. On the Change View: “Header”: Overview screen, mark the line with billing type F2 (Tgt) and delivery type (Source) LF in the dialog box Header.

4. Double click on Item in the Dialog Structure.


Field Name Description User Action and Values

Comment

Target Bill Type

Invoice F2

From Delivery Type

Outbound Delivery

LF

Item Category YBAB


004

Data VBRK/VBRP

001

Billing quantity G

Pos/neg. 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.





If you want to use F8 (delivery-related), the copy control for delivery LF to billing type F8 is maintained at item level with the following steps:





Comment

Target Bill Type

Pro Forma Inv f Dlv

F8

From Delivery Type

Outbound Delivery

LF

Item Category YBAB


010

Billing Quantity D

Pricing Type G



ResultThe Customizing settings for specifying the copying control for delivery documents to billing documents are maintained.

3.12 Maintaining Copying Control: Billing Doc. to Billing Doc

UseIntegrate 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.



IMG Menu Sales and Distribution Billing Billing Documents Maintain Copying Control For Billing Documents

Transaction Code VTFF

2. Choose Copying control: Billing document to billing document in the dialog box Choose Activity.

3. On the Change View: “Header”: Overview screen, mark the line with billing type G2 (Tgt) and delivery type (Source) F2 in the dialog box Header.





Field name Description User action and values Comment

Target Bill Type

Credit Memo G2

Source Bill Type

Invoice F2

Item Category YBAB


027

Pricing Type G







Comment

Target Bill Type

Debt Memo L2

Source Bill Type

Invoice F2

Item Category YBAB


027

Pricing Type G


