AFS 107 BB Config

BB Installation Guide

SAP ECC 6.0 EhP3

August 2008

English REF DokSprache \* MERGEFORMAT English

Sales Processing using Third Party (w. Shipping Notification) (107)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

Copyright

Copyright 2008 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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, xApps, xApp, 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 in several other countries all over the world. 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

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.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Contents

51Purpose

52Preparation

52.1Prerequisites

53Configuration

53.1Sales: General

53.1.1Defining Item Category

63.1.2Assigning Item Category

73.1.3Maintaining Copy Control for Sales Documents (Item)

83.2Transfer of Requirements

83.2.1Defining Requirement Classes

93.2.2Defining Requirement Types

103.2.3Determining Requirement Types using Transaction

113.3Schedule Lines

113.3.1Assigning Schedule Line Categories

123.4Billing

123.4.1Copy Control on Item Level

Sales Processing using Third Party (w. Shipping Notification)

1 Purpose

This 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 Preparation2.1 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_IN.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_IN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\BBLibrary\General\.

3 Configuration3.1 Sales: General3.1.1 Defining Item CategoryUse

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 TAS Third Party Item and choose Copy As.

3. On the Change View Maintain Item Categories: Details of Selected Set screen, make the following entries for YB1:

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 Billing relevance field should be changed to B. Choose Back and then choose Save.

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

5. Choose Save.

6. Choose Back (F3).

Result

The item category YB1 has been created.

3.1.2 Assigning Item CategoryUse

Item categories which have been created in the previous step should be assigned to order (OR) type. 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.

Prerequisites

The item category group YBNA has been maintained.

Procedure


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, make the following entries:

Field name

Description


Note

Sales Doc. Type

OR

Item ca.group

YBNA

M Item category

YB1

Dfitc

YB2

M Item category

TAS

M Item category

TAN

4. Choose Save.


Result

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

3.1.3 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


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 order (OR) in both SalesDoc Type input fields in the Another entry dialog box.

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.


Field name

Description


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

Pricing type

A

Copy quantity

A

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

9. Choose Save.


Result

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

3.2 Transfer of Requirements3.2.1 Defining Requirement ClassesUse

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


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, make the following entries:

Field name

Description


Note

Reqmts. Class

3rd Party with SN

YB1

Availability

X

Req. transfer

X

Configuration

*

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

4. Choose Save.


Result

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

3.2.2 Defining Requirement TypesUse

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

Prerequisites

Requirement class YB1 has been created.

Procedure


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, make the following entries:

Field name

Description


Note

RgTy

YB1

Requirements type

3rd Party with SN

ReqCl

YB1

4. Choose Save.


Result

The requirement type YB1 is created.

3.2.3 Determining Requirement Types using TransactionUse

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


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.


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

Field name

Description


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.


Result

The item category has been assigned to the requirements type.

3.3 Schedule Lines3.3.1 Assigning Schedule Line CategoriesUse

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

Procedure


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.


Field name

Description


Note

Item category

YB1

PropSchdLneCat.

CS

4. Choose Save.


Result

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

3.4 Billing3.4.1 Copy Control on Item LevelUse

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


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 Billing Type input field and OR in the SalesDoc Type input field in the Another entry dialog box.


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


Note

Target Bill Type

Invoice

F2

From Sale Doc. Type

Standard Order

OR

Item Category

3rd Party with SN

YB1


Ord.rel 3rd pty item

012

Billing quantity

F

Pos./neg. quantity

+

Pricing Type

G

If the entry does not exist, choose New Entries.

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

Field name

Description


Note

Target Bill Type

Invoice

F2

From Sale Doc. Type

Standard Order

OR

Item Category

YB1


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 Billing quantity field to E, which ensures that the quantity to be invoiced is GR quantity, which is less invoiced quantity.

8. Choose Save.


Result

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

_1118216528.bin