A79_Scen_ConfigGuide_EN_DE.docx

SAP ECC 6.00

March 2007

English

A79 – Make-to-Order Process with Configuration Change in Vehicle Management System

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Scenario Configuration Guide

SAP Best Practices A79 – MTO Process with Configuration Change in VMS: Configuration

Guide

Copyright

© Copyright 2007 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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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.

© SAP AG of 14


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

© SAP AG of 14


Guide

Contents

MTO Process with Configuration Change in VMS: Configuration Guide.........................................5

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

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

2.1 Prerequisites..................................................................................................................5

2.1.1 Building Blocks......................................................................................................5

3 Configuration........................................................................................................................ 6

3.1 Installation in the Sales System.....................................................................................6

3.1.1 Master Data..........................................................................................................6

3.1.1.1 Checking User Parameters..........................................................................6

3.1.1.2 Creating Material Master..............................................................................6

3.1.1.3 Creating BOM...............................................................................................7

3.1.1.4 Changing BOM (add dep.)............................................................................7

3.1.1.5 Creating Configuration Profile.......................................................................7

3.1.1.6 Creating Configuration Interface...................................................................8

3.1.1.7 Creating SD Condition Records - PR00.......................................................8

3.1.1.8 Creating SD Condition Records - VA00........................................................8

3.1.1.9 Creating Purchase Info Record....................................................................9

3.1.1.10 Creating MM Condition Records for OEM - VA00........................................9

3.1.1.11 Creating MM Condition Records for Rework - VA00....................................9

3.1.1.12 Creating User for VMS...............................................................................10

3.1.1.13 Assigning Vehicle Model............................................................................10

3.1.1.14 Assigning User Roles.................................................................................10

3.1.1.15 Assigning Organizational Data...................................................................11

3.1.1.16 Setting Determination of Action Control......................................................11

3.1.1.17 Initial Stock.................................................................................................11

3.1.1.18 Checking Field Status Compatibility of Movement Type and Account........12

3.1.1.19 Adding Images...........................................................................................13

3.1.1.20 Maintaining Picture for Vehicle in Dealer Portal.........................................14

MTO Process with Configuration Change in VMS: Configuration Guide

1 PurposeThis configuration guide provides 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 eCATTs and BC Sets, use the SAP Best Practices Installation Assistant.

© SAP AG of 14


Guide

2 Preparation

2.1 Prerequisites

2.1.1 Building BlocksBefore you start installing this building block, the installation of the following building blocks must have been completed:

Building Block Description

Baseline Project for Automotive In Sales client

Industry-Generic Blocks in Sales

A01 (Sales) Automotive Basic Settings

A05 (Sales) Master Data for Automotive

In order to run the scenario, you also have to install the following scenario specific building blocks:

In Sales client:

Scenario-Specific Building Blocks Description

A23 (Sales) Vehicle Management System

© SAP AG of 14


Guide

3 Configuration3.1 Installation in the Sales System

3.1.1 Master Data

3.1.1.1 Checking User Parameters

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

SAP Menu SAP Easy Access System User Profile Own Data

Transaction Code SU3

2. Ensure that the following parameters are set in your user master record.

3. Choose the tab parameters, and make the following entry:

Field name Description

CUQ 001

4. Save your settings.

5. Log off the system and log on again.

If the user parameter already exists, skip this step and continue with next activity.

3.1.1.2 Creating Material Master

UseThe purpose of this activity is to create the material masters for the materials required in this scenario.


SAP Menu Logistics Materials Management Material Master Material Create (General) Immediately

Transaction Code MM01

2. Refer to the following file for details of the material master data required: SMB0V_MM01_ALL_VIEWS_O001_A79_SAL.TXT

3.1.1.3 Creating BOM

UseThe purpose of this activity is to create bill of material.


© SAP AG of 14


Guide

SAP Role Menu Logistics Production Master Data Bills of Material Bill of Material Material BOM Create

Transaction Code CS01

2. Refer to the following file for details of the material master data required:SMB0V_CS01_O001_A51_A79_SAL.TXT

3.1.1.4 Changing BOM (add dep.)

UseThe purpose of this activity is to change BOM (add dep.).


SAP Role Menu Logistics Production Master Data Bills of Material Bill of Material Material BOM Change

Transaction Code CS02

2. Refer to the following file for details of the material master data required:SMB0V_CS02_O001_A79_SAL.TXT

3.1.1.5 Creating Configuration Profile

UseThe purpose of this activity is to create configuration profile.


SAP Role Menu Logistics Production - Process Process Order Environment Material Data Material Master Environment Configuration Profile Create

Transaction Code CU41

2. Refer to the following file for details of the material master data required:SMB0V_CU41_O001_A78_A79_SAL.TXT

3.1.1.6 Creating Configuration Interface

UseThe purpose of this activity is to create configuration external tab.


SAP Role Menu Logistics Production - Process Production Planning Demand Management Environment Configuration Simulation

© SAP AG of 14


Guide

Transaction Code CU50

2. Refer to the following file for details of the material master data required: SMB0V_CU50_O001_A79_SAL.TXT

3.1.1.7 Creating SD Condition Records - PR00

UseThe purpose of this activity is to create SD condition records - PR00.


SAP Role Menu Logistics Sales and Distribution Master Data Conditions Select Using Condition Type Create

Transaction Code VK11

2. Refer to the following file for details of the material master data required: SMB0V_VK11_O002_A79_SAL.TXT

3.1.1.8 Creating SD Condition Records - VA00

UseThe purpose of this activity is to create SD condition records - VA00.


SAP Role Menu Logistics Sales and Distribution Master Data Conditions Select Using Condition Type Create

Transaction Code VK11

2. Refer to the following file for details of the material master data required:

SMB0V_VK11_O003_A79_SAL.TXT

3.1.1.9 Creating Purchase Info Record

UseThe purpose of this activity is to create MM condition records – PB00.


SAP Role Menu Logistics Materials Management Purchasing Master Data Info Record Create

Transaction Code ME11

2. Refer to the following file for details of the material master data required: SMB0V_ME11_O001_A59_A79_SAL.TXT

© SAP AG of 14


Guide

3.1.1.10 Creating MM Condition Records for OEM - VA00

UseThe purpose of this activity is to create MM condition records for OEM – VA00.


SAP Role Menu Logistics Materials Management Purchasing Master Data Conditions Other Create

Transaction Code MEK1


SMB0V_MEK1_O001_A79_01.TXT

3.1.1.11 Creating MM Condition Records for Rework - VA00

UseThe purpose of this activity is to create MM condition records for rework - VA00.


SAP Role Menu Logistics Materials Management Purchasing Master Data Conditions Other Create

Transaction Code MEK1


SMB0V_MEK1_O001_A79_02.TXT

3.1.1.12 Creating User for VMS

UseThe purpose of this activity is to create user for VMS.


SAP Role Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. Refer to the following file for details of the material master data required:SMB0V_SU01_O001_A01_A78_A79_SAL.TXT

© SAP AG of 14


Guide

3.1.1.13 Assigning Vehicle Model

UseThe purpose of this activity is to assign user roles.


SAP Role Menu Logistics Logistics Execution Vehicle Management System Basic Data VMS Roles Assign Vehicle Model

Transaction Code VELORM

2. Refer to the following file for details of the material master data required: SMB0V_VELORM_O001_A79_SAL.TXT

.

3.1.1.14 Assigning User Roles

UseThe purpose of this activity is to assign vehicle model.


SAP Role Menu Logistics Logistics Execution Vehicle Management System Basic Data VMS Roles Assign User Roles

Transaction Code VELORU

2. Refer to the following file for details of the material master data required

SMB0V_VELORU_O001_A79_SAL.TXT

3.1.1.15 Assigning Organizational Data

UseThe purpose of this activity is to assign organizational data.


SAP Role Menu Logistics Logistics Execution Vehicle Management System Basic Data VMS Roles Assign Organizational Data

Transaction Code VELORO


SMB0V_VELORO_O001_A79_SAL.TXT

© SAP AG of 14


Guide

3.1.1.16 Setting Determination of Action Control

UseThe purpose of this activity is to set determination of action control.


SAP Role Menu Logistics Logistics Execution Vehicle Management System Basic Data Set Determination of Action Control

Transaction Code VELOS


SMB0V_VELOS_O001_A79_SAL.TXT

3.1.1.17 Initial Stock

UseThe purpose of this activity is to create stock for parts to be provided to subcontract vendor.

PrerequisitesMaterial masters have been created.


SAP Role Menu Logistics Logistics Execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Goods Receipt for Other Activities

Transaction Code MB1C


SMB0V_MB1C_O001_A51_A79_SAL.TXT

3.1.1.18 Checking Field Status Compatibility of Movement Type and Account

This step is not a must step in installation, as the field selection incompatibility cannot be foreseen. Instead, the problem could arise in transaction processing. Thus, this section can be used to do the troubleshooting.

UseThe purpose of this activity is to check the field status compatibility of movement type and account.


© SAP AG of 14


Guide

SAP Menu Tools ABAP Workbench Development ABAP Editor

Transaction Code SE38

2. On the ABAP editor: Initial screen, make the following entries.

Field name Description User action and values Note

Program RM07CUFA

3. Choose Execute.

4. On the Field selection comparison: Movement type – G/L account, make the following entries.

Field name User action and values Note

Movement type 543

Special stock indicator O Special stock for parts provided to Vendor

Company code BP01 (or personalized company code)

G/L account 600020

5. Choose Execute.

6. On the Field selection comparison: Movement type – G/L account screen, the report lists the result of comparison. Incompatibility is highlighted in red. Select the highlighted line and select Choose to correct the incompatibility.

7. Find the row containing Asset Retirement and choose - (dash) under the column A/c.

8. Double click the Group Asset Accounting.

9. Choose the Opt. entry radio button for Asset Retirement.

10. Choose Save.

11. On the Prompt for customizing request screen, choose from your own suitable change requests or create a new.

12. Choose Continue and go Back.

3.1.1.19 Adding Images

UseThe purpose of this activity is to define for the individual applications which images (for example, .gif files) the system displays.

You can find the pictures used in this installation on the documentation DVD under \Misc\A78.

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

Transaction Code SPRO

IMG Menu Discrete Industries Business Package for Automotive dealers General Setting Add Images

2. On the Change View “Value Table for Application ID”: Overview screen, choose New Entries.

© SAP AG of 14


Guide

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

Field name Description R/O/C User action and values Note

AppID Application ID R 2

Material Material Number R A79-MTO_SAL

Lang. Language Key R EN

IMG TXT Image Text R A79 VEHICLE the name and the type of the image that is being used

Image Image R A79.JPG the name of the file in which the image is stored

4. Choose save.

Result The images have been maintained for system to display.

3.1.1.20 Maintaining Picture for Vehicle in Dealer Portal

UseThe purpose of this activity is to maintain the picture for vehicle which is displayed in dealer portal.

You can find the pictures used in this installation on the documentation DVD under \Misc\A79.


SAP R/3 Menu Tools ABAP Workbench Overview Object Navigator

Transaction Code SE80

2. On the Object Navigator screen, click MIME Repository.

3. Under folder SAP, expand BC BSP SAPDII DWB DWB Vehicles model.

4. Right-click on model, choose Import MIME Objects.

5. On the SAP Custom – Open File screen, choose file A79.jpg from your computer and choose open.

6. On the Create New Document screen, enter description A79 Vehicle.

7. Choose Save.

© SAP AG of 14


Guide

8. On the dialog box Create Object Directory Entry, do not enter a package, and choose Local Object.

9. Go Back to SAP Easy Access screen.

© SAP AG of 14

A79_Scen_ConfigGuide_EN_DE.docx

Documents

Transcript of A79_Scen_ConfigGuide_EN_DE.docx