EHP3 for SAP ERP 6.0 June 2009 EnglishEnglish
	Sales Processing using Third Party (w. Shipping Notification) (107)
SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf Germany	Building Block Configuration Guide

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 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, SAP Business ByDesign, 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 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 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.

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

Sales Processing using Third Party (w. Shipping Notification)

• Purpose

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

If you prefer an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide.

• Prerequisites

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_PL.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_PL.xls). This document can be found on the SAP Best Practices documentation DVD in the folder: ..\BBLibrary\General\.

• Configuration

1. Sales: General

1. Defining Item Category

Use

The item category YB1 is used for third-party order with shipping notification. The item categories that are contained in the standard SAP system together with the sales document types represent the usual business transactions.

Procedure

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

Transaction code	SPRO
IMG menu	Sales and Distribution  Sales  Sales Documents  Sales Document Item  Define Item Categories

2. On the Change View Maintain Item Categories: Overview screen, choose the entry TAS Third Party Item and choose Copy As.

3. On the Change View Maintain Item Categories: Details of Selected Set screen, maintain the entries for YB1 as below:

Field name	Description	User action and values	Note
Item category	3rd party w SN	YB1
Billing relevance		B
Pricing		X
Business Item		X
SchedLine Allowed		X
Wght/Vol Relevant		X
Credit Active		X
Determine Cost		X
Incompletion Proc.		28
Partner DetermProced.		T
TextDetermProced.		01
Screen Seq. Grp		N




YB1 can be copied from TAS.

The field Relevant for billing should be changed to B.

4. Choose Back and then choose Save.

5. Choose Enter and confirm the Dependent entries for copy control dialog box.

6. Choose Save.

7. Choose Back (F3).

Result

The item category YB1 has been created.

1. Assigning Item Category

Use

Item categories that have been created in the previous step should be assigned to order type OR. It is possible to define a default item category that is 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.

Prerequisites

The item category group YBNA has been maintained.

Procedure

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

Transaction code	SPRO
IMG menu	Sales and Distribution ! Sales ! Sales Documents ! Sales Document Item ! Assign Item categories

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

3. On the New Entries: Details of Added Entries screen, enter the values shown below.

Field name	Description	User action and values	Note
Sales Doc. Type		OR
Item ca.group		YBNA
Item category		YB1	MitCa (Manual Item Category entry)

4. Choose Save.

5. Choose Back (F3).

Result

The assignment of the item category YB1 to the sales order OR is done for the item category group YBNA.

1. Maintaining Copy Control for Sales Documents (Item)

Use

Copy control should be maintained at Item level to ensure that the reference to another third-party order (OR) works.

Procedure

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

Transaction code	VTAA
IMG menu	Sales and Distribution  Sales  Sales Documents  Maintain Copy control for Sales Documents  Copying Control: Sales Document to Sales Document

2. On the Display View Header Overview screen, choose Display ! Change (Ctrl+F1).

3. On the Change View Header Overview screen, choose Position.

4. Enter OR in both SalesDoc Type input fields in the dialog box Another entry.

5. Choose Continue (Enter).

6. On the Change View Header Overview screen, mark the line of your selected sales document types and double-click Item in the Dialog Structure.

7. On the Change View: Item Overview screen, choose New Entries.

8. On the New Entries: Details of Added Entries screen, enter the values shown below.

Field name	Description	User action and values	Note
Target Sales Doc Type	Standard Order	OR
From Sale Doc. Type	Standard Order	OR
Item Cat Proposal		YB1
Item Category		YB1
DataT		151
DataT		102
DataT		002
FPLA		251
Copying requirements		303
Copy schedule lines		X
Do not copy batch		X
Configuration		A
Copy quantity		A
Pricing type		A




The copy control for YB1 should have been set up if you confirmed copy control when you created the item category YB1. You still need to change the fields Item type proposal and Configuration as per the above table.

9. Choose Save.

10. Choose Back (F3).

Result

The copy control for order type OR and item category YB1 has been created.

1. Transfer of Requirements

1. Defining Requirement Classes

Use

The purpose of this activity is to define a new requirement class YB1. With the requirement class you control all functions relevant to requirements in third-party processing.

Procedure

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

Transaction code	OVZG
IMG menu	Sales and Distribution ! Basic Functions ! Availability Check and Transfer of Requirements ! Transfer of Requirements ! Define Requirements Classes

2. On the Change View Requirements Classes: Overview screen, choose New Entries.

3. On the Change View Requirements Classes: Details of Selected Set screen, enter the values shown below.

Field name	Description	User action and values	Note
Reqmts. Class	3rd Party with SN	YB1
Availability		X
Req. transfer		X
Configuration		*




The indicator Configuration = * is set so that the configuration of materials can be entered in the sales order.

4. Choose Save.

5. Choose Back (F3).

Result

The requirement class YB1 can be used for third-party business.

1. Defining Requirement Types

Use

The purpose of this activity is to create the requirement type YB1. A requirement type YB1 with assignment to requirements class YB1 is used for third-party business.

Prerequisites

Requirements class YB1 has been created.

Procedure

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

Transaction code	OVZH
IMG menu	Sales and Distribution ! Basic Functions ! Availability Check and Transfer of Requirements ! Transfer of Requirements ! Define Requirements Types

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

3. On the New Entries: Overview of Added Entries screen, enter the values shown below.

Field name	Description	User action and values	Note
RgTy		YB1
Requirements type		3rd Party with SN
ReqCl		YB1

4. Choose Save.

5. Choose Back (F3).

Result

The requirement type YB1 is created.

1. Determining Requirement Types using Transaction

Use

The purpose of this activity is to assign the item category (=business transaction) to the requirements type, and thus also to the requirements class.

Procedure

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

Transaction code	SPRO
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 YB1 in the Item Category input field in the Another entry dialog box.

4. Choose Continue (Enter).

5. On the Change View Assignment of Requirement Types to Transaction: Overview screen, enter the values shown below.

Field name	Description	User action and values	Note
ItCa		YB1
RgTy		YB1
Q		1
Requirements and description		3rd Party




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 is used for different business transactions (depending on the item category). The above assignments have to be maintained.

6. Choose Save.

7. Choose Back (F3).

Result

The item category has been assigned to the requirements type.

1. Schedule Lines

1. Assigning Schedule Line Categories

Use

The purpose of this activity is to assign the schedule line category CS to the item category YB1.

Procedure

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

Transaction code	SPRO
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.

3. On the New Entries: Details of Added Entries screen, enter the values shown below:

Field name	Description	User action and values	Note
Item category		YB1
PropSchdLneCat.		CS

4. Choose Save.

5. Choose Back (F3).

Result

The new schedule line category YB1 has been assigned to the item category CS.

1. Billing

1. Copy Control on Item Level

Use

For the order-related billing of a third-party order, the new order item category YB1 must be integrated in the copy control for the order types OR ! F2.

Procedure

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

Transaction code	VTFA
IMG menu	Sales and Distribution ! Billing ! Billing Documents ! Maintain Copy control For Billing Documents ! Copy control: Sales Document to Billing Document

2. On the Display View Header: Overview screen, choose Display ! Change (Ctrl+F1).

3. On the Change View Header: Overview screen, choose Position.

4. Enter F2 in the input field Billing Type and OR in the input field SalesDoc Type in the Another entry dialog box.

5. Choose Continue (Enter).

6. Mark the line of Tgt F2 and Source OR and double-click Item in the Dialog Structure.

7. On the Change View: Item Overview screen, check whether the entry YB1 exists:

• If the entry is available on the Item sub-screen, mark the respective line and choose Details (Ctrl+Shift+F2).

• Check the existing settings on the Change View: Item Details screen and, if necessary, correct them according to the values shown below.

Field name	Description	User action and values	Note
Target Bill Type	Invoice	F2
From Sale Doc. Type	Standard Order	OR
Item Category	3rd Party with SN	YB1
Copying requirements	Ord.rel 3rd pty item	012
Billing quantity		F
Pos./neg. quantity		+
Pricing Type		G




If you created the item category YB1 manually as a copy of a standard item category and chose copy dependent entries, the copy control from OR to F2 should already be available. If so, you still need to change the field Billing quantity to E, which ensures that the quantity to be invoiced is GR quantity less invoiced quantity.

8. Choose Save.

9. Choose Back (F3).

Result

The copy control has been set up for sales document to billing document level.




SAP Best Practices
Sales Processing using Third Party (w. Shipping Notification) (107): Configuration Guide


© SAP AG Page 2 of 12

---