114 Erp607 Bb Configguide en Us

March 7, 2018 | Author: nerellavinay | Category: Invoice, Sap Se, Computing, Technology, Software
Share Embed Donate


Short Description

Descripción: SAP...

Description

EHP7 for SAP ERP 6.0 February 2014 English

Sales Processing Using Third Party (without Shipping Notification) (114) Building Block Configuration Guide

SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf Germany

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Copyright © 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. 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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. 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, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, 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. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

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, buttons 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.

© SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Contents Sales Processing Using Third Party (without Shipping Notification)...............................................5 1

Purpose................................................................................................................................... 5

2

Preparation.............................................................................................................................. 5 2.1

3

Prerequisites.................................................................................................................. 5

Configuration........................................................................................................................... 5 3.1

Purchasing: General...................................................................................................... 5

3.1.1

Maintaining Account Assignment Categories.............................................................5

3.1.2

Defining Combination of Item Category/Acc. Assignment Categories.......................6

3.2

Sales: General............................................................................................................... 7

3.2.1

Assigning Item Category........................................................................................... 7

3.2.2

Maintaining Copy Control for Sales Documents (Header and Item)..........................8

3.3

Transfer of Requirements.............................................................................................. 9

3.3.1

Defining Requirement Classes..................................................................................9

3.3.2

Defining Requirement Types...................................................................................10

3.3.3

Determining Requirement Types Using Transaction................................................11

3.4

Schedule Lines............................................................................................................ 12

3.4.1

Defining Schedule Line Categories.........................................................................12

3.4.2

Assign Incompletion Procedure to Schedule Line Categories.................................12

3.4.3

Assigning Schedule Line Categories.......................................................................13

3.4.4

Maintaining Copy Control in Schedule Line Level...................................................13

3.5 3.5.1

© SAP SE

Billing........................................................................................................................... 15 Copying Control on Item Level................................................................................15

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Sales Processing Using Third Party (without Shipping Notification) 1 Purpose This 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 BC Sets and other tools, refer to the SAP Best Practices Quick Guide, located on the SAP Note.

2 Preparation 2.1 Prerequisites Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix, located on the documentation package on the Technical  Content Library page.

3 Configuration 3.1 Purchasing: General 3.1.1

Maintaining Account Assignment Categories

Use The purpose of this activity is to create the account assignment category Y to define the account assignment data that is necessary for the purchase order item.

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

Material Management  Purchasing  Account Assignment  Maintain Account Assignment Categories

Transaction Code

OME9

2. On the Change View “Account Assignment Categories”: Overview screen, select the X entry and choose Copy As. 3. On the Change View “Account Assignment Categories”: Details of Selected Set screen, enter the following values or leave the other fields as copied: Field name

Description

User action and values

Acct assignment cat.

3rd Party without SN

Y

© SAP SE

Comment

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Field name

Description

User action and values

Acct. assgm changeable

X

AA Chgable at IR

X

Consumption posting

V

Acct modification

VAX

ID AcctAssgt Scrn

1

Distribution

1

Partial Invoice

2

Invoice Receipt

X

Comment

4. In the Fields section, make the following entries: Field Label

Mand. Ent.

Opt.Ent.

Display

Hidden

Asset

X

Asset Subnumber

X

Business Area

X

Business process

X

CO/PP Order

X

Commitment Item Cost Center

X X

Cost Object

X

Cost Type

X

5. Save your entries. 6. Choose Back (F3).

Result The account assignment category Y has been created or maintained to suit your requirements.

3.1.2

Defining Combination of Item Category/Acc. Assignment Categories

Use The purpose of this activity is to specify the allowed combinations of item categories and account assignment categories. Since we have created a new account assignment category, we must maintain the combinations for item category S (third party) here.

Prerequisites The account assignment category Y is created.

Procedure © SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

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

Material Management  Purchasing  Account Assignment  Define Combination of Item Categories/Account Assignment Categories

Transaction Code

OMG0

2. On the Change View “Check Item Category/Account Assignment Category”: Overview screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, make the following entries: ItmCat.

ACC

S

Y

4. Save your entries. 5. Choose Back (F3).

Result The relevant combinations have been created.

3.2 Sales: General 3.2.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: IMG Menu

Sales and Distribution  Sales  Sales Documents  Sales Document Item  Assign Item categories

Transaction Code

VOV4

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

User action and values

Sales Doc. Type

OR

Item ca.group

YBNA

Default item category for the document

YB2

© SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Field name

User action and values

Manual entries allowed for item category in the document

YB1 / TAS / TAN

4. Save your entries. 5. Choose Back (F3).

Result The assignment of the item category YB2 to the sales order OR is complete for the item category group YBNA.

3.2.2

Maintaining Copy Control for Sales Documents (Header and 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: IMG Menu

Sales and Distribution  Sales  Sales Documents  Maintain Copy control for Sales Documents 

Transaction Code

VTAA

2. If you access this transaction via the IMG menu, in the Choose Activity dialog box, doubleclick Copying Control: Sales Document to Sales Document. 3. On the Display View “Header” Overview screen, choose Display Change (Ctrl+F1). 4. On the Change View “Header” Overview screen, choose Position. 5. In the Another entry dialog box, in both SalesDoc Type input fields, enter OR. 6. Choose Continue (Enter). 7. On the Change View “Header” Overview screen, select the line of your selected sales document types and in the Dialog Structure, double-click Item. 8. On the Change View: Item Overview screen, choose New Entries. 9. On the New Entries: Details of Added Entries screen, make the following entries: Field name

Description

User action and values

Target Sales Doc Type

Standard Order

OR

From Sale Doc. Type

Standard Order

OR

Item Cat Proposal

YB2

Item Category

YB2

DataT

151

DataT

102

© SAP SE

Comment

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Field name

Description

User action and values

DataT

002

FPLA

251

Copying requirements

303

Copy schedule lines

X

Do not copy batch

X

Configuration

A

Pricing type

A

Copy quantity

A

Comment

The copy control for YB2 should have been set up if you confirmed copy control the time you created the item category YB2. You still must change the Item type proposal and Configuration fields as per the preceding table. 10. Save your entries. 11. Choose Back (F3).

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

3.3 Transfer of Requirements 3.3.1

Defining Requirement Classes

Use The purpose of this activity is to define a new requirement class Y42. 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: 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.

3.

On the Change View “Requirements Classes”: Details of Selected Set screen, make the following entries: Field name

Description

User action and values

Reqmts. Class

3rd Party MV

YB2

Availability © SAP SE

Comment

X Page 6 of 7

SAP Best Practices

Field name

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Description

User action and values

Req. transfer

X

Configuration

*

Comment

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

Save your entries.

5.

Choose Back (F3).

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

3.3.2

Defining Requirement Types

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

Prerequisites Requirements class YB2 has been created.

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 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: Field name

Description

User action and values

RgTy

YB2

Requirements type

3rd Party

ReqCl

YB2

Comment

4. Save your entries. 5. Choose Back (F3).

Result The requirement type YB2 is created.

© SAP SE

Page 6 of 7

SAP Best Practices

3.3.3

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

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

In the Another entry dialog box, in the Item Category field, enter Y1.

4. Choose Continue (Enter). 5. On the Change View “Assignment of Requirement Types to Transaction”: Overview screen, make the following entries: Field name

Description

User action and values

ItCa

YB2

RgTy

YB2

Source

1

Requirements and description

3rd Party

Comment

The requirements type is 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 preceding assignments have to be maintained. 6. Save your entries. 7. Choose Back (F3).

Result The item category has been assigned to the requirements type.

3.4 Schedule Lines 3.4.1

Defining Schedule Line Categories

Use © SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

The purpose of this activity is to create a schedule line category YT to be used for third-party processing in the standard SAP system. The new schedule line category YT is assigned to the account assignment category Z, which was defined in one of the previous steps.

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

Sales and Distribution  Sales  Sales Documents  Schedule Lines  Define Schedule Line Categories

Transaction Code

VOV6

2. On the Change View “Maintain Schedule Line Categories”: Overview screen, select CS and choose Copy As. 3. On the Change View “Maintain Schedule Line Categories”: Details of Selected Set screen, make the following entries: Field name

Description

User action and values

Sched. Line cat.

3rd Party w/o SN

YT

Order type

Purchase requisition

NB

Item category

Third-party

5

Acct.assig.cat.

All aux.acct. assgts.

Y

Comment

31

Incompl.proced. 4. Save your entries. 5. Choose Back (F3).

Result The schedule line category YT can be used for third-party processing.

3.4.2

Assign Incompletion Procedure to Schedule Line Categories

Procedure 1. Access the activity using the following navigation options: IMG Menu

Sales and Distribution  Basic Functions  Log of Incomplete Items  Assign Incompleteness Procedures

Transaction Code

VUE2

2. If you access the transaction via the IMG menu, in the Choose Activity dialog box, doubleclick Assign procedures to the schedule line categories. 3. On the Change View “Error Logs for Sales Document Schedule Line Categories” screen, make the following entries: Field name SLCa © SAP SE

Description

User action and values

Comment

YT Page 6 of 7

SAP Best Practices

Field name

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Description

Comment

31

Proc.

3.4.3

User action and values

Assigning Schedule Line Categories

Use The purpose of this activity is to assign the new schedule line category YT to the item category YB2.

Procedure 1. Access the activity using one of the following navigation options: 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, make the following entries: Field name

Description

User action and values

Item category

YB2

PropSchdLneCat.

YT

Comment

4. Save your entries. 5. Choose Back (F3).

Result The new schedule line category YT has been assigned to the item category YB2.

3.4.4

Maintaining Copy Control in Schedule Line Level

Use The purpose of this activity is to set up the copy control at schedule line level.

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

Sales and Distribution  Sales  Maintain Copy control for Sales Documents

Transaction Code

VTAA

2. If you access the transaction via the IMG menu, in the Choose Activity dialog box, doubleclick Copy control: Sales Document to sales document. 3. On the Display View “Header”: Overview screen, choose Display Change (Ctrl+F1). © SAP SE

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

4. On the Change View “Header”: Overview screen, choose Position. 5. In the Another entry dialog box, in both SalesDoc Type fields, enter OR. 6. Choose Continue (Enter). 7. On the Change View “Header”: Overview screen, select the line of the selected sales document types and in the Dialog Structure, double-click Item. 8. On the Change View “Item”: Overview screen, choose New Entries. 9. On the New Entries: Details of Added Entries screen, make the following entries: Field name

Description

User action and values

Target Sales Doc Type

Standard Order

OR

From Sale Doc. Type

Standard Order

OR

Item Cat Proposal

YB2

Item Category

YB2

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

10. Save your entries. 11. On the Change View “Item”: Overview screen, select the item category YB2. 12. In the Dialog Structure, double-click Schedule line. 13. On the Change View “Schedule Line”: Overview screen, choose New Entries. 14. On the New Entries: Details of Added Entries screen, make the following entries: Field name

Description

User action and values

Target Sales Doc Type

Standard Order

OR

From Sale Doc. Type

Standard Order

OR

SchdLneCatPropsal

YT

Sched. Line Cat.

YT

DataT

201

Copying requirements

501

© SAP SE

Comment

Page 6 of 7

SAP Best Practices

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

The copy control for YT might already be set up if you created the schedule line category manually and confirmed copy dependent parameters. If so, youchange the ProposedSchedLneCat field as in the preceding table. 15. Save your entries. 16. Choose Back (F3).

Result The copy control has been set up at schedule line level.

3.5 Billing 3.5.1

Copying Control on Item Level

Use For the order-related billing of a third-party order, the new order item category Y2 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: IMG Menu

Sales and Distribution  Billing  Billing Documents  Maintain Copy control For Billing Documents

Transaction Code

VTFA

2. If you access the transaction via the IMG menu, in the Choose Activity dialog box, doubleclick Copy control: Sales Document to Billing Document. 3. On the Display View “Header”: Overview screen, choose Display Change (Ctrl+F1). 4. On the Change View “Header”: Overview screen, choose Position. 5. In the Another entry dialog box, in the Billing Type field, enter F2 and in the SalesDoc Type field, enter OR. 6. Choose Continue (Enter). 7. Select the Tgt F2 and Source OR line and in the Dialog Structure, double-click Item. 8. On the Change View: Item Overview screen, check whether the entry YB2 exists: 

If the entry is available on the Item subscreen, select 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 following values:

Field name

Description

User action and values

Target Bill Type

Invoice

F2

From Sale Doc. Type

Standard Order

OR

Item Category © SAP SE

rd

3 Party with SN

Comment

YB2 Page 6 of 7

SAP Best Practices

Field name Copying requirements

Sales Processing Using Third Party (without Shipping Notification) (114): Configuration Guide

Description

User action and values

Comment

012

rd

Ord.rel 3 pty item

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

User action and values

Target Bill Type

Invoice

F2

From Sale Doc. Type

Standard Order

OR

Item Category

YB2

Copying requirements

012

Billing quantity

F

Pos./neg. quantity

+

Pricing Type

G

Comment

If you created the item category Y1 manually as a copy of a standard item category and chose copy dependent entries, the copy control from OR to F2 must already be available. If so, you still must change the Billing quantity field to E, which ensures that the quantity to be invoiced is GR quantity less invoiced quantity. 9. Save your entries. 10. Choose Back (F3).

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

© SAP SE

Page 6 of 7

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF