122 Erp605 Bb Configguide en Cn

12
EHP5 for SAP ERP 6.0 December 2011 English Batch Recall (122) SAP AG Dietmar-Ho-Allee 16 6!1!0 "all#orf German$ %&il#ing %loc' (onfig&ration G&i#e

description

122 Erp605 Bb Configguide en Cn

Transcript of 122 Erp605 Bb Configguide en Cn

BB Installation Guide

EHP5 for SAP ERP 6.0December 2011EnglishEnglish

Batch Recall (122)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block Configuration Guide

Copyright

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

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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

IconMeaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type StyleDescription

Example textWords 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 textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames 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 textScreen 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 TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact 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

5Batch Recall

51Purpose

52Preparation

52.1Prerequisites

53Configuration

53.1Assigning Sales Area to Sales Document Types

63.2Basic Functions

63.2.2Defining Print Parameters

73.3Sales

73.3.1Maintaining Copy Control for Billing Documents

83.3.2Defining Order Reasons

93.4Output

93.4.1Creating Output Condition for Sales Activities

103.4.2Creating Output Condition for Billing

103.5Creating Master Data for Batch Recall

103.5.1HR Data for Sales Representatives

Batch Recall

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.2 Preparation2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix (Prerequisites_Matrix_[xx]_[yy]_ [zz].xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, BL refers to the SAP Best Practices Baseline Package, [yy] depends on the language version, for example, EN for English language, and [zz] depends on the country version, for example, CN for China: Prerequisites_Matrix_BL_EN_CN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\[xx]_[zz]\Documentation\; ([xx] depends on the SAP Best Practices version and [zz] depends on the country version).3 Configuration3.1 Assigning Sales Area to Sales Document TypesUse

The purpose of this activity is to assign sales area to sales document types.

Procedure

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

Transaction codeSPRO

IMG menuSales and Distribution ( Sales( Sales Documents ( Sales Document Header( Assign Sales Area To Sales Document Types

2. In the Choose Activity dialog box, choose Assign sales order types permitted for sales areas and Double click it.3. Choose New Entries, make following entries: Ref.SRefDDivSaTy

10001010RE

4. Choose Save.Result

Sales area has assigned sales document type.3.2 Basic Functions

3.2.1.1 Assigning Output Types to Partner FunctionsUse

In this step, you assign the allowed output types to partner functions.

In addition, specify the allowed type of output processing for the combination of output types and partner functions

Procedure

1. Access the activity using the following navigation options:Transaction codeS_ALR_87005941

IMG menuSales and Distribution ( Basic Functions( Output Control ( Output Determination ( Output Determination Using the Condition Technique ( Maintain Output Determination for Sales Activities.( Assign Output Types to Partner Functions

2. In change mode, select the entry MABC 1.3. Choose Copy as and MABC 1 ER.

4. Press Enter to confirm the data, and choose Save (F11).

Result

The partner function ER for output type MABC is maintained.3.2.2 Defining Print Parameters

Use

The purpose of this activity is to define the print parameters for sales, shipping, billing, transportation and sales activity output, for example. This is dependent on a predefined key.

In the standard version of the SAP R/3 system, print parameters can, for example, be dependent on

Sales organization Sales organization/distribution channel / division Sales office Shipping pointFor example, you can then print out picking lists on a printer which is assigned to a particular shipping point, and sales order confirmations on another printer which is assigned to a particular sales office.

Maintain the following print parameters for each output medium:

Key -- Depending on the setting (for example, key for the sales organization or shipping point) to which the print parameters apply Output device -- Key for the printer to which the output should be issued Dataset -- Name of spool order Suffix 1 -- ID 1 which identifies the spool order Suffix 2 -- ID 2 which identifies the spool order Issue immediately -- ID for printing immediately Release -- ID for deleting a print order from the spool file after printing has been carried outProcedure

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

Transaction codeVPO1

IMG menuSales and Distribution ( Basic Functions ( Output Control ( Define Print Parameters

2. On the Print Parameters screen, expand the node sales activities (K1) in the tree of Maintain print parameters.

3. Double-click on Batch Recall MABC.4. On the Change View Print Parameters for Sales Organization: Overview screen, choose New Entries on the application toolbar.

5. On the New Entries: Details of Added Entries screen, enter the following values:

Sales orgOutputDeviceNamePrint immed.Suffix 1Suffix 2

1000LP01MABCXPACTPRINT_ACT

6. Choose Save (Ctrl+S).

7. Choose Back (F3).8. On the Change View Print Parameters for Sales Organization: Overview screen, choose New Entries on the application toolbar.

9. On the New Entries: Details of Added Entries screen, enter the following values:

Sales orgOutputDeviceNamePrint immed.Suffix 1Suffix 2

1100LP01MABCXPACTPRINT_ACT

10. Choose Save (Ctrl+S).

11. Choose Back (F3).

Result

The print parameters have been defined.3.3 Sales3.3.1 Maintaining Copy Control for Billing DocumentsUse

The purpose of this activity is to define control data for the document flow of the return billing document.

You can specify for a particular billing type which has to be assigned to copied reference documents.

You must also make specifications for copying requirements and transferring data. This must be done for each copying procedure.

Check the document flow defined in the standard system. Define to what extent you have to modify its specifications to meet your requirements. Define the document flow for sales activity documents with reference to sales activities.Procedure1. Access the activity using one of the following navigation options:

Transaction codeVTFL

IMG menuSales and Distribution ( Billing ( Billing Documents ( Maintain Copying Control For Billing Documents

2. In the Choose Activity dialog box, double-click Copying control: Delivery document to billing document.3. On the Change View Header: Overview screen, choose New Entries on the application toolbar.

4. On the New Entries: Overview of Added Entries screen, enter the following values:

To activ.typeFrom active.typeCopying requirementscopy item number

RELR003X

5. Mark the new created entry and go to the item level by double-clicking Item in the left column.

6. On the Item Overview screen, choose New Entries on the application toolbar.7. On the New Entries: Item Overview screen, enter the following values:

ItemCtREN

Target Bill. TypeRE

Copying requirements004

Data VBRK/VBRP001

Update flow

Billing quantityG

Pos./neg. quantity+

Pricing typeG

8. Save your settings.

9. Choose Back (F3).

Result

The copy control for sales activities has been defined.3.3.2 Defining Order Reasons

Use

The purpose of this activity is to define the possible order reasons. They describe the reasons which led to an inquiry, quotation or order.When processing a sales document, you can specify the order reason in the overview at header level. It then applies to all the items. Sales calls, trade fair activities or newspaper advertisements often lead to sales orders.

Procedure

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

Transaction codeSPRO

IMG menuSales and Distribution ( Sales ( Sales Documents ( Sales Document Header ( Define Order Reasons

2. On the Change View Sales Documents: Order Reasons: Overview screen, choose New Entries on the application toolbar.

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

Order reasonRDescription

YB1Return from Recall

4. Choose Save (Ctrl+S).

5. Choose Back (F3).Result

The order reason YB1 has been defined.3.4 Output3.4.1 Creating Output Condition for Sales Activities

Use

The output condition is created to enable printing of sales activity related documents such as a letter.

Procedure

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

SAP ECC menuLogistics ( Sales and Distribution ( Master Data ( Output ( Sales Activities ( Create

Transaction codeVV51

2. On the Create Output Condition Records: Sales Activities screen, choose MABC: Batch Recall.3. Choose Enter.

4. On the Create Condition Records (Direct Mailing): Fast Entry screen, make the following entries: Field nameDescriptionUser action and values

Sales Organization1000

SalesActTy0001

Medium1

Date/Time1

5. Select the entry and choose Communication. Select the print option print immediately.

6. Save your entries.

7. Choose Back (F3).Result

The output condition MABC for sales activities has been created.3.4.2 Creating Output Condition for BillingUse

The output condition is created to enable printing of sales activity related documents such as a letter.

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

SAP ECC menuLogistics ( Sales and Distribution ( Master Data ( Output ( Billing Document ( Create

Transaction codeVV31

2. On the Create Output Condition Records: Billing screen, choose RD00: Direct Invoice.3. Choose Enter.

4. On the Create Condition Records (Direct Mailing): Fast Entry screen, make the following entries: Field nameDescriptionUser action and values

Sales Organization1000

Billing TypeRE

Medium1

Date/Time4

5. Select the entry and choose Communication. Select the print option print immediately.

6. Save your entries.

7. Choose Back (F3).

Result

The output condition RD00 for the billing type for returns has been created.3.5 Creating Master Data for Batch Recall3.5.1 HR Data for Sales Representatives3.5.1.1 Creating EmployeeUse

In this step, you create an employee.

Procedure

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

SAP ECC menuHuman Resources ( Personnel Management ( Administration ( HR Master Data ( Personnel Actions

Transaction codePA40

2. Select action type Hiring Service Provider.3. In the From field, enter 01.01.2007 and in the Personnel no. field, enter 999301.4. Choose Execute.5. On the Create Actions screen, maintain the data as shown in the table below:Personnel numberPositionEmployee GroupPersonnel AreaEmployee Subgroup

99930111000Y1

6. Choose Enter.

7. Save your entries.

8. On the Create Organizational Assignment screen, maintain the data as shown in the table below:Personnel numberCost CenterPersonnel SubareaPayroll Area

99930116021010YB

9. Choose Enter.

10. Save your entries.

11. On the Create Personnel Data screen, maintain the data as shown in the table below:PersNoTitleLast NameFirst NameBirth DateLanguageNationality

999301MrsLangerBarbara13.06.1956ENCN

12. Choose Enter.

13. Save your entries.

14. On the Create Planned Work time screen, enter Work schedule rule YB00.15. Choose Enter.

16. Save your entries.

17. On the Create Travel Privileges, set flag Changes Permitted to Trip screen in Company Code Changes area.18. Choose Enter.

19. Save your entries.

20. On the Create Time Sheet Defaults screen, maintain the data as shown in the table below:Personnel numberControlling AreaCost CenterActivity Type

999301100016029

Result

A new employee has been created.3.5.1.2 Creating Sales Representative

Use

In this step, you extend the employee with an additional view so that the employee becomes a sales representative.

Procedure

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

SAP ECC menuHuman Resources ( Personnel Management ( Administration ( HR Master Data ( Maintain

Transaction codePA30

2. In the Personnel no. field, enter 999301.3. Choose Enter.4. In the Infotype field, enter 0900.5. Choose Create (F5). 6. On the Create Sales Data screen, maintain the Sales data section as shown in the table below:Sales OrganizationSales OfficeSales Group

1000100100

7. In the Start field, enter 01.01.2007.8. In the To field, enter 31.12.9999.9. Choose Enter.10. Save your entries (Ctrl+S).Result

The additional view has been defined.

_1118216528.bin