107 bb configguide en us

7/28/2019 107 BB ConfigGuide en US

http://slidepdf.com/reader/full/107-bb-configguide-en-us 1/12

EHP4 for SAP ERP 6.0

June 2010

English

Sales Processing Using

Third Party (with ShippingNotification) (107)

SAP AGDietmar-Hopp-Allee 16D-69190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices Sales Processing Using Third Party (with Shipping Notification) (107): Configuration Guide

Copyright

© 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 componentsof 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 trademarks of IBMCorporation.

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 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 technology inventedand implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, 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 andin other countries. Business Objects is an SAP company.

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 may vary.

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 warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

© SAP AG of 12




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.

Exampletext

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLETEXT

Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example, SELECTand 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 namesof installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Exampletext

Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

<Example

text>

Variable user entry. Pointed brackets indicate that you replace these words and

characters with appropriate entries.

© SAP AG of 12




Contents

Sales Processing Using Third Party (with Shipping Notification)............................................... ....5

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

2 Preparation................................................................................................................................. . 5

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

© SAP AG of 12




Sales Processing Using Third Party (withShipping Notification)

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

If you do not want to configure manually and prefer an automated installation process using BCSets and other tools, refer to the SAP Best Practices Quick Guide, located on the SAP Note.

2 Preparation

2.1 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 Excelfile) is linked on the solution's DVD/website in one of the following two locations:

• Content Library

• Site Map

3 Configuration

3.1 Sales: General3.1.1 Define Item Category

Use

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

Procedure

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

IMG Menu Sales and Distribution → Sales→ Sales Documents → SalesDocument Item → Define Item Categories

Transaction Code VOV7

2. On the Change View ”Maintain Item Categories”: Overview screen, select the entry TASThird Party Item and choose Copy As.

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

© SAP AG of 12




Field name Description User action and values

Item category 3rd Party with 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.Choose Back and then choose Save.

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

5. Save your settings.

6. Choose Back (F3).

Result

The item category YB1 has been created.

3.1.2 Assigning Item Category

Use

Item categories which have been created in the previous step must be assigned to order typeOR. It is possible to define a default item category that will be determined automatically in thesales order (depending on the item category of the material). Alternatively, up to three further itemcategories can be assigned. In the sales order, the default item category can be replacedmanually by the alternative item categories.

PrerequisitesThe item category group YBNA has been maintained.

Procedure


IMG Menu Sales and Distribution → Sales→ Sales Documents → Sales

Document Item → Assign Item categories

© SAP AG of 12




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 User action and values

Sales Doc. Type OR

Item ca.group YBNA

Default item category for the document YB2

Manual entries allowed for item category in the document YB1 / TAS / TAN

4. Save your entries.


Result

The assignment of the item category YB1 to the sales order OR is done for the item categorygroup 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-partyorder (OR) works.

Procedure


IMG Menu Sales and Distribution → Sales→ Sales Documents →

Maintain Copy control for Sales Documents → Copying Control: Sales Document to Sales Document

Transaction Code VTAA

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, select the line of your selected salesdocument types and double-click on 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.


Target Sales Doc Type Standard Order OR

From Sale Doc. Type Standard Order OR

Item Cat Proposal YB1

© SAP AG of 12





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 controlwhen you created the item category YB1. You still need to change the fields Itemtype proposal and Configuration as per the above table.



Result

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

3.2 Transfer of Requirements

3.2.1 Defining Requirement Classes

Use

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

Procedure

1. Access the activity using one of the following navigation 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 ”Requirements Classes”: Overview screen, choose New Entries.

© SAP AG of 12




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


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 beentered in the sales order.



Result

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

3.2.2 Defining Requirement Types

Use

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

Prerequisites

Requirements class YB1 has been created.

Procedure


IMG Menu IMG → 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, enter the values shown below.Field name Description User action and values

RgTy YB1

Requirements type 3rd Party with SN

ReqCl YB1


© SAP AG of 12





Result

The requirement type YB1 is created.

3.2.3 Determining Requirement Types Using Transaction

Use

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

Procedure


IMG Menu Sales and Distribution → Basic Functions → Availability Check

and Transfer of Requirements→

Transfer of Requirements→

Determination of Requirement Types using Transaction

Transaction Code OVZI

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

3. Enter YB1 in the input field Item Category in the Another entry dialog box.


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


ItCa YB1

RgTy YB1

Q 1

Requirements and description 3rd Party with SN

The requirements type is generally determined using the strategy Supply source = 1(item category and MRP type strategy), since determination using the strategy in thematerial master is not possible, because the same material is used for differentbusiness transactions (depending on the item category). The above assignmentshave to be maintained.



Result

The item category has been assigned to the requirements type.

© SAP AG of 12




3.3 Schedule Lines

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


IMG Menu Sales and Distribution → Sales→ Sales Documents →

Schedule Lines → Assign Schedule Line Categories

Transaction Code VOV5

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


Item category YB1

PropSchdLneCat. CS



Result

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

3.4 Billing

3.4.1 Copy Control on Item Level

Use

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

Procedure


IMG Menu Sales and Distribution → Billing → Billing Documents →

Maintain Copy control For Billing Documents→ Copy control:

Sales Document to Billing Document

Transaction Code VTFA

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

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

© SAP AG of 12




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


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

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

- If the entry is available in the Item sub-screen, mark the respective line and chooseDetails (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.


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 the entry does not exist, choose New Entries.

- On the New Entries: Overview of Added Entries screen, enter the data shown below.


Target Bill Type Invoice F2

From Sale Doc. Type Standard Order OR Item Category YB1

Copying requirements 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 categoryand 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 ensuresthat the quantity to be invoiced is GR quantity less invoiced quantity.



Result

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

© SAP AG of 12