vms config guide
Post on 12-Apr-2015
1.091 Views
Preview:
DESCRIPTION
TRANSCRIPT
SAP R/3 4.7
Aug 2005
English
A23 - Vehicle Management System
SAP AGNeurottstr. 1669190 WalldorfGermany
Building Block Configuration Guide
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Copyright
© Copyright 2005 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, and Informix are trademarks or registered trademarks of IBM Corporation 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, 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 Page 2 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Icons
Icon Meaning
Caution
Example
Note or Tip
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 Page 3 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
ContentsA23 Vehicle Management System: Configuration Guide................................................................5
1 Purpose................................................................................................................................... 5
2 Preparation.............................................................................................................................. 5
2.1 Prerequisites..................................................................................................................5
3 Configuration........................................................................................................................... 6
3.1 Configuration in the Supplier System............................................................................6
3.1.1 VMS Related Configuration.......................................................................................6
3.1.2 Other Settings.........................................................................................................22
© SAP AG Page 4 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
A23 Vehicle Management System: Configuration Guide
1 PurposeThe purpose of this document is to describe the general configuration steps required, to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
The Configuration Guide describes how to set up the configuration of a Building Block manually, without the support of automated configuration tools. If you want to use BC Sets and CATT procedures for an automated installation process, refer to the Building Block Installation Guide of the scenario A23 – Vehicle Management System.
2 Preparation
2.1 PrerequisitesThe following building blocks form the basis for all mySAP All-in-One Automotive, High Tech and Industrial Machinery and Components solutions. You only have to install these building blocks once.
Install these building blocks in the Supplier client.
Building Blocks Comments
Baseline Building Blocks (Layer 0)
B32 - Best Practices R/3 Installation
J02 - Organizational Structure
B29 - Financial Accounting
B30 - Cost/Profit Center Accounting
J05 - Material Management
J04 - Sales and Distribution
Baseline Building Blocks (Layer 1)
J06 - Production Planning & Control
J07 - Quality Management
J18 - Product Cost Planning
© SAP AG Page 5 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Building Blocks Comments
J19 - Batch Management
J20 - Cost Object Controlling - Make-to-Order SP
J21 - Cost Object Controlling - Make-to-Stock
Industry-Generic Building Blocks (DIMP Layer)
A01 - DI Basic Settings
3 Configuration
3.1 Configuration in the Supplier System
3.1.1 VMS Related Configuration
3.1.1.1 Defining Number Ranges for Internal Vehicle Number
Use When creating a vehicle, a unique number is assigned which identifies the vehicle. The number comes from the number range.
Procedure 1. Access the activity using one of the following navigation options.
IMG Menu Logistics Execution Vehicle Management System(VMS) Number Ranges Determine Number Ranges for Internal Vehicle Number
Transaction Code OVELO2
2. On the VELO:Internal Vehicle Number screen, choose Intervals .
3. On the Maintain Number range Intervals choose Intervals. A Dialog box Insert
intervals appears.
4. On the Insert Intervals dialog box, make the following entries:
Field name Description R/O/C User action and values
Note
No Serial Number R 01 Enter the Serial Number
From Number Starting number of the Number Range
R 0000000001 Enter the starting number of the Number Range
To Number Ending Number of the Number Range
R 9999999999 Enter the ending number of the Number Range
© SAP AG Page 6 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Field name Description R/O/C User action and values
Note
Current Number
Current Running number
O
Ext Whether the number range is Internal or External
O by default the system takes Internal Number range. For External Number Range check the check box
5. Choose Insert and choose save.
Result Number ranges for the internal vehicle number are created.
3.1.1.2 Defining Number Ranges for Action Control Determination
UseWhen creating an action control, a unique number is assigned which identifies the action control as an internal key. The number comes from the number range.
Procedure 1. Access the activity using one of the following navigation options.
IMG Menu Logistics Execution Vehicle Management System(VMS) Number Ranges Define Number Ranges for Action Control
Transaction Code OVELO3
2. On the VELO:Interna Key for Action Control Determination screen, choose Intervals .
3. On the Maintain Number range Intervals choose Intervals. A Dialog box Insert intervals
appears.
4. On the Insert Intervals dialog box, make the following entries:
Field name Description R/O/C User action and values
Note
No. Serial Number R 01 Enter the Serial Number
From Number Starting number of the Number Range
R 0001 Enter the starting number of the Number Range
To Number Ending Number of the Number Range
R 9999 Enter the ending number of the Number Range
© SAP AG Page 7 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Field name Description R/O/C User action and values
Note
Current Number
Current Running number
O
Ext Whether the number range is Internal or External
O the system takes Internal Number range by default.
Choose Insert and choose save.
Result Number Ranges for the Internal Key for action control determination are created.
3.1.1.3 Defining Number Ranges for Determination of Configuration Change Profile
UseWhen creating a configuration change profile, a unique number is assigned which identifies the configuration change profile as an internal key. The number comes from the number range.
Procedure 1. Access the activity using one of the following navigation options.
IMG Menu Logistics Execution Vehicle Management System(VMS) Number Ranges Define Number Ranges for Determination of Configuration Change Profile
Transaction Code OVELO8
2. On the Internal Key for Determining Configuration Change Profile screen, choose Intervals.
3. On the Maintain Number range Intervals choose Intervals Icon. A Dialog box Insert
intervals appears.
4. On the Insert Intervals dialog box, make the following entries:
Field name Description R/O/C User action and values Note
No Serial Number R 01 Enter the Serial Number
From Number Starting number of the Number Range
R 0001 Enter the starting number of the Number Range
To Number Ending Number of the Number Range
R 9999 Enter the ending number of the Number Range
Current Number
Current Running number
O
© SAP AG Page 8 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Field name Description R/O/C User action and values Note
Ext Whether the number range is Internal or External
O by default the system takes Internal Number range. For External Number Range check the check box
5. Choose Insert and choose save.
Result Number Ranges for the Internal Key for determining configuration change profile are defined.
3.1.1.4 Defining VMS Roles
Use
The purpose of this activity is to define VMS roles. VMS roles serve as central control elements in VMS.
There are three types of roles:
Organizational Role
This is a role to which organizational data is assigned. Organizational data is dealer or importer data (plant, sales organization, distribution channel, division, SD document type, customer, ship-to party and payer).
Vehicle Model Role
This is a role to which vehicle models are assigned. This role determines which vehicles the system displays to the user in the vehicle model list.
Configuration role
This is a role that is assigned to a configuration change profile.
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Define VMS Roles
Transaction Code SPRO
2. On the Change View “Define VMS Roles”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
VMS Role
(Roles in the Vehicle Management System)
Descript.
(Description of VMS Role)
DEA1 dealer organization role A7801
DEA2 dealer organization role A7802
© SAP AG Page 9 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
DEA3 dealer organization role A7803
DE00 Dealer role for A79
GROS gross list price
IM01 Importer role for A79
KONF configuration change profile
MIMP material role A78
OIMP importer organization role A78
WTY Warranty create for vehicle
4. Choose save.
Result The roles have been created.
3.1.1.5 Defining Actions
UseThe purpose of this activity is to define VMS actions.
You use this IMG activity to first check the VMS actions that are offered as standard. You then define additional actions if you need them for your processes.
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Actions
Transaction Code SPRO
2. On the Change View “Define Actions”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Action Action Description
Interlinking Action
Internal Action
Primary Action
Secondary Action
SCEMRelRevancy
CRM Relevancy
Isolation
ZCONVehicle in Production X
ZCUS
Vehicle at End Customer X
ZENDVehicle at Dealer X
ZPOC
Confirm Purchase Order by OEM X
© SAP AG Page 10 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
ZSHI
Vehicle Shipped to End Customer X
4. Choose save.
5. Because action CREA and UGRE are used as both primary and secondary action in scenario A79, it is required to change standard action CREA and UGRE from primary actions into primary and secondary actions. Please ensure the following settings in system :
Action Action Description
Interlinking Action
Internal Action
Primary Action
Secondary Action
SCEMRelRevanc
CRM Relevancy
Isolation
CREA
Create Vehicle (Configurable) X X
UGRE
End Rework (Goods Receipt) X X
6. Choose save.
Result The actions have been created.
3.1.1.6 Defining Vehicle Status
UseThe purpose of this activity is to define the internal vehicle status
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Vehicle Status
Transaction Code SPRO
2. On the Change View “Define Vehicle status”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Veh.Status
(Vehicle Status)
Descript.
(Description of Vehicle Status)
Status Initial
* Generic *
L040 Goods Received
L050 Vehicle at Rework
L060 Vehicle at Rework
© SAP AG Page 11 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
L080 End Rework, Vehicle Available
L090 End Rework, Vehicle Available
L100 Goods Issued
L110 Goods Issued
L200 Vehicle at Dealer
L210 Vehicle at Dealer
M005 Vehicle Planned
M010 Vehicle Purchased
M020 Inbound Invoice Created
M030 Goods Received
P120 PO confirmed by OEM
P130 Manufactured
P140 Shipped
P180 VIN Assigned
P200 Shipped to End Customer
P210 Arrived at End Customer
RS01 Vehicle Reserved
SD01 Customer Spec. Veh. Identified
SD05 Sales Order Created
SD10 Rework Ended
SD25 Goods Issued
SD30 Outbound Invoice Created
SD35 Delivery Created
W200 Master Warranty Assigned
W400 General Object Number Created
4. Choose save.
Result The internal vehicle status has been created.
3.1.1.7 Defining Availability
UseThe purpose of this activity is to define the availability status.
Procedure
© SAP AG Page 12 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Availability
Transaction Code SPRO
2. On the Change View “Define Availability”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Availabil.
(Availability Status )
Descript.
(Description of Availability Status)
space - Initial -
AV available
NA not available
PL planned
RS Reserved
SD Sold
4. Choose save.
Result The availability status has been created.
3.1.1.8 Defining Vehicle Locations
UseThe purpose of this activity is to create the VMS-Vehicle locations.
You can use this field to map vehicle locations to your system. These locations are not covered in master data (customer master, vendor master, business partner management for end customers). Locations are defined for situations where the vehicle is not located at a business partner (vendor, customer or end customer) but is in transit (for example, at sea or on a lorry) or in one of the rework premises at a plant.
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Vehicle Locations
Transaction Code SPRO
© SAP AG Page 13 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
2. On the Change View “Define Vehicle Locations”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Veh. Loc.
(VMS-Vehicle Location )
Descript.
(Description of VMS Vehicle Location )
CU Customer
DC In transit: Dealer -> Customer
DE Dealer
ID In transit: importer -> dealer
IM Importer
MF Manufacturer
MI In transit: Manuf -> Importer
RW Re-Worker
4. Choose save.
Result The VMS-Vehicle locations have been created.
3.1.1.9 Defining Vehicle Usage
UseThe purpose of this activity is to define the vehicles usage.
Procedure2. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Vehicle Usage
Transaction Code SPRO
3. On the Change View “Define Vehicle Usage”: Overview screen, choose New Entries.
4. On the New Entries: Overview of Added Entries screen, make the following entries:
Veh. Usage
(Vehicle Usage )
Description
(Description of VMS Role)
CU Customer Vehicle
LF Stock Vehicle
SR Showroom Vehicle
5. Choose save.
© SAP AG Page 14 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Result The vehicle usages have been created.
3.1.1.10 Defining Action Controls and Action Matrices
UseThe purpose of this activity is to define the vehicle action controls that you need for your business processes, and then create an action grid (or matrix) for each action control. You also define which current vehicle status is permitted for which action and the new status that the action should give the vehicle. Finally you create an entry for each action control combination and action with specifications for availability status, delivery schedule (days remaining until delivery, start date for scheduling) and determination of the physical vehicle location.
Prerequisites You must have defined all the actions, vehicle status, availability status, and vehicle locations that you need for your business processes in the previous IMG activities.
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Control Data Define Action Control and Define Action Matrices
Transaction Code SPRO
2. On the Change View “Define Action Controls”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Action Control
LA Descript.
(Description of Action Control )
Note
MM01 EN VMS MTS Primary Action Control
For scenario A78
MM02 EN VMS MTO Primary Action Control
For scenario A79
SD01 EN VMS MTS Secondary Action Control
For scenario A78
SD02 EN VMS MTO Secondary Action Control
For scenario A79
Action Control
Old Vehicle Status
Action New Vehicle Status
Check Entry
MM01 CREA M005MM01 * HIDE *MM01 * SHOW *
© SAP AG Page 15 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
MM01 L040 INIV M020MM01 L100 ZEND L200MM01 L200 GEOB W400MM01 M005 CMOD M005MM01 M005 ORD1 M010MM01 M010 MORD M010MM01 M010 ZPOC P120MM01 M020 CUOR *MM01 M020 GOIS L100MM01 P120 ZCON P130MM01 P130 SMOD P180MM01 P180 GORE L040MM01 P200 ZCUS P210MM01 W200 ZSHI P200MM01 W400 WYVH W200MM02 CRCO M005MM02 CREA M005MM02 CUOR M005MM02 L050 UGRE L080MM02 L060 INIV L050MM02 L060 UGRE L090MM02 L080 GOIS L100MM02 L090 GOIS L110MM02 L090 INIV L080MM02 L100 ZEND L200MM02 L110 INIV L100MM02 L110 ZEND L210MM02 L210 INIV L200MM02 M005 CUOR M005MM02 M005 ORD1 M010MM02 M010 CCPO M010MM02 M010 MORD M010MM02 M010 ZPOC P120MM02 M020 UORD L050MM02 M030 INIV M020MM02 M030 UORD L060MM02 P120 CCPO P120MM02 P120 MORD P120MM02 P120 ZCON P130MM02 P130 CCPO P130MM02 P130 MORD P130MM02 P130 SHMT P140MM02 P140 CCPO P140MM02 P140 GORE M030MM02 P140 MORD P140
SD01 CREA SD01SD01 * SHOW *SD01 * HIDE *SD01 RS01 BUPA RS01SD01 RS01 CUOR SD05
© SAP AG Page 16 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
SD01 SD01 RSVN RS01SD01 SD05 BUPA SD05SD01 SD05 OUIV SD30SD01 SD30 DELI SD35SD01 SD35 GOIS SD25SD02 CRCO SD05SD02 CREA SD01SD02 SD01 CUOR SD05SD02 SD05 BUPA SD05SD02 SD05 CCPO SD05SD02 SD05 CHCO SD05SD02 SD05 UGRE SD10SD02 SD10 CHCO SD10SD02 SD10 DELI SD35SD02 SD25 OUIV SD30SD02 SD35 GOIS SD25
Action Control
Action Availability Scheduling basis
Days Until Delivery
Vehicle Location
Description Address Determination
MM01 CREA PL 0
MM01 GOIS 0 ID
in transit: importer -> dealer
MM01 GORE 0 IM Importer
MM01 ORD1 AV 0MM01 ZCON MF Manufacturer
MM01 ZCUS CU Customer End Customer
MM01 ZEND 0 DEDealer Customer
Master Record
MM01 ZSHI NA 0 DC
In transit: Dealer -> Customer
MM02 CRCO SD 0MM02 CREA SD 0MM02 CUOR SD 0MM02 GOIS SD 0 IDMM02 GORE RS 0 IMMM02 SHMT RS 0 MIMM02 UGRE RS 0 IMMM02 UORD RS 0 RWMM02 ZCON RS 0 MFMM02 ZEND SD 0 DESD01 CUOR SD 0SD01 GOIS IDSD01 RSVN RS
4. Choose save.
Result
© SAP AG Page 17 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
The action control and matrices have been created.
3.1.1.11 Defining Technical Details for Actions
UseThe purpose of this activity is to define technical details for actions if you have changed the delivered actions or have programmed your own actions.
Procedure 1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Enhancements Define Technical Details for Actions
Transaction Code SPRO
2. On the Change View “Define Technical Data for Actions”: Overview screen, ensure there are following entries:
Action Configuration Pushbutton
Action for Creating Obj.
Action Program
Action Screen
Alias Action
CREA Pushbutton Available X SAPLVELO10 0140UGRE Can be configured SAPLVELO17 0700ZCON Can be configured ZCUS Can be configured ZEND Can be configured ZPOC Can be configured ZSHI Can be configured
3. Choose save.
Result The technical details of actions have been maintained.
3.1.1.12 Defining Vehicle Search Area
UseThe purpose of this activity is to define the vehicle search area.
Procedure1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Vehicle Search Vehicle Search Areas Define Vehicle Search Areas
© SAP AG Page 18 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Transaction Code SPRO
2. On the Change View “Define Vehicle Search Areas”: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Veh. SchArea
(Vehicle Search Area )
Description
(Description of VMS Role)
BP01 Vehicles in Plant BP01
4. Select the new entry, the choose Assign Plants.
5. On the Change View “Assign Plants “: Overview screen, make the following entries:
Vehicle Search Area Plant Vehicle Search Area Name1
BP01 BP01 Vehicles in Plant BP01 Production Plant
6. Choose save.
Result The vehicle search area has been created.
3.1.1.13 Initializing Category Rule Maintenance
UseThe purpose of this activity is to initialize the category rule maintenance.
Procedure1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution Vehicle Management System(VMS) Vehicle Search Vehicle Search Areas Initialize Category Rule Maintenance
Transaction Code OVELOVSRINIT
2. Choose Execute.
3. You can ignore the error message Syntax error in substitution "1FP0001", step "001"( Message no GB032 ) and User exit UFP00 not declared in form pool RGGBS000 ( Message no GB308) by choosing Continue(Enter).
Result
The initial category rule has been maintained.
3.1.1.14 Defining Vehicle Categories
Use
© SAP AG Page 19 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
The purpose of this activity is to define the vehicle categories.
PrerequisitesRelated customizing must exist.
Procedure1. Access the activity using one of the following navigation options:
SAP R/3 Role Menu Installation Role of A23 Installation in Supplier System Vehicle Management System Define Vehicle Categories
Transaction Code OVELO20
2. On the Change Rule: Overview screen, expand VM Category Management.
3. Choose Rule Create.
4. On the Create Rule: New rule screen, make the following entries:
Rule name Description Application area
BP001 Search Rule for Dealer DPVMS7801
VM
5. Double click Rule definition.
6. Select the Table Fields tab, select Display technical name listed beside the tab block, to make sure you can see the tables with both the technical table name and the table short description.
7. Double click the table: VLCVEHICLE (VELO: Vehicle) then choose the field VLCVEHICLE-AVAIL(Availability) by double clicking the line. Choose “=”, then choose Constant, in the Enter constants: screen, input “AV” in field Availability.
8. Choose “OR”.
9. Choose “ ( “, then on the table: VLCVEHICLE (VELO: Vehicle), choose the field VLCVEHICLE-AVAIL(Availability) by double clicking the line. Choose “=”, then choose Constant, in the Enter constants: screen, input “RS” in field Availability.
10. Choose “AND”.
11. Choose to return to the table view.
12. Double click the table: VLCSEARCH_USER (VELO: Data for Vehicle Search) then choose the field VLCSEARCH_USER-KUNNR (Customer) by double clicking the line. Choose “=”, then choose the field VLCSEARCH_USER-KUNNR (Customer) by double clicking the line.
13. Choose “ ) “.
14. Choose “OR”.
15. Choose “ ( “.
16. Choose to return to the table view.
17. Double click the table: VLCVEHICLE (VELO: Vehicle) then choose the field VLCVEHICLE-AVAIL(Availability) by double clicking the line. Choose “=”, then choose Constant, in the Enter constants: screen, input “SD” in field Availability.
18. Choose “AND”.
© SAP AG Page 20 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
19. Choose the field VLCVEHICLE-KUNNR (Customer) by double clicking the line. Choose
“=”,Choose to return to the table view.Then Double click the table: VLCSEARCH_USER (VELO: Data for Vehicle Search) then choose the field VLCSEARCH_USER-KUNNR (Customer) by double clicking the line.
20. Choose “ ) “, “ OR”, “ ( “ separately.
21. Double click the table: VLCVEHICLE (VELO: Vehicle) then choose the field VLCVEHICLE-AVAIL(Availability) by double clicking the line. Choose “=”, then choose Constant, in the Enter constants: screen, input “NA” in field Availability.
22. Choose “AND”.
23. Double click the table: VLCVEHICLE (VELO: Vehicle) then choose the field VLCVEHICLE-
KUNNR (Customer) by double clicking the line. Choose “=”,choose to return to the table view.Then Double click the table: VLCSEARCH_USER (VELO: Data for Vehicle Search) then choose the field VLCSEARCH_USER-KUNNR (Customer) by double clicking the line.
24. Choose “AND”.
25. Choose to return to the table view.
26. Double click the table: VLCVEHICLE (VELO: Vehicle) then choose the field VLCVEHICLE-VBLTY(Visibility) by double clicking the line. Choose “=”, then choose Constant, in the Enter constants: screen, input “X” in field Availability.
27. Choose “ ) “.
28. Check the formula displayed in the window.It should be:VLCVEHICLE-AVAIL = 'AV' OR ( VLCVEHICLE-AVAIL = 'RS'AND VLCSEARCH_USER-KUNNR = VLCVEHICLE-KUNNR ) OR (VLCVEHICLE-AVAIL = 'SD' ANDVLCVEHICLE-KUNNR = VLCSEARCH_USER-KUNNR ) OR (VLCVEHICLE-AVAIL = 'NA' ANDVLCVEHICLE-KUNNR = VLCSEARCH_USER-KUNNR ANDVLCVEHICLE-VBLTY = 'X' )
29. Choose Save.
30. On the Create Rule: New rule screen,make the following entry:
Rule name Description Application area
BP002 Search Rule for Dealer DPVMS7802
VM
31. You can use the same method to define search rule BP002. Ensure the formula displayed in the window is:
VLCVEHICLE-VBLTY = ‘X’.
32. Choose Save.
33. Go back to SAP easy access screen.
ResultThe vehicle categories have been created.
© SAP AG Page 21 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
3.1.1.15 Assign Vehicle Category
UseThe purpose of this activity is to assign vehicle category to VMS roles.
PrerequisitesRelated customizing must exist.
Procedure1. Access the activity using one of the following navigation options:
SAP R/3 Role Menu Installation Role of A23 Installation in Supplier System Vehicle Management System Assign Roles and Vehicle Categories
Transaction Code OVELO21
2. On the Mainten.: Assign Vehicle Categories screen, under search Area /VMS role tab , choose Insert Row, enter the following entry :
Field name Description R/O/C User action and values Note
VehSchArea Vehicle Search Area
R BP01
VMS Roles VMS Roles R DEA1
3. Select the entered entry and choose tab Category Priority.
4. Choose Insert Row, enter the following entry for priority 1 row.
Field name Description R/O/C User action and values Note
Category Vehicle Category R BP001
5. Choose Save .
6. Specify a customizing request or create a new one.
7. Repeat Steps 2 to 6 to assign vehicle category BP002 to vehicle search area BP01 and VMS roles DEA2.
3.1.2 Other Settings
3.1.2.1 Defining Attribute of Material Type VEHI
UseThe purpose of this activity is to define attribute of material type VEHI.
© SAP AG Page 22 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Prerequisites
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Logistics - General Material Master Basic Settings Material Types Define Attributes of Material Type
2. On the Change View “Material types”: Overview screen, select material type VEHI.
3. Choose Quantity/value updating.
4. On the Change View “Quantity/value updating”: Overview screen, make the following entries:
Val.area Matl type Qty updating
Value updating
BP01 VEHI X X
5. Choose Save.
6. Choose Back.
ResultThe split material valuation has been activated.
3.1.2.2 Defining Item Category for Vehicle
UseThe purpose of this activity is to define a sales item category for vehicle.
Procedure 1. Access the activity using one of the following navigation options:
SAP R/3 Role Menu Installation Role of A23 Installation in Supplier System Other Settings Define Item Category for Vehicle
Transaction Code VOV7
2. On Change View “Maintain Item Categories” : Overview screen, select item category TACV and choose Copy As…
3. On Change View “Maintain Item Categories”: Details of Selected Set screen, make the following entries :
Field name Description R/O/C User action and values
Note
Item category
R VTAC
Item Category Description
R VConfig.at Mat.Level
© SAP AG Page 23 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
4. Choose enter, on the Dependent entries for copying control pop screen, choose Yes to confirm that this entry is relevant for copying control.
5. Choose enter.
6. Choose Save.
7. Choose Continue(Enter) on the Maintain Table Views: Initial Screen popup
screen
8. Go back to SAP easy access screen.
ResultThe sales item category VTAC has been maintained for vehicle.
3.1.2.3 Defining BP Number Range
UseThe purpose of this activity is to modify the BP number range for external
Prerequisites
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Cross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges
2. Choose Grouping 0002.
3. Change the Number Range from AB to 02.
4. Choose Save.
5. Choose Back.
ResultThe number range for business partner has been maintained.
3.1.2.4 Split Valuation
3.1.2.4.1 Activating Split Valuation
UseThe purpose of this activity is to activate the split valuation for VEHI material type.
Prerequisites
© SAP AG Page 24 of 25
SAP Best Practices A23 Vehicle Management System: Configuration Guide
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code OMW0
IMG Menu Materials Management Split Valuation Activate Split Valuation
2. Choose Split material valuation active.
3. Choose Save.
4. Choose Back.
ResultThe split material valuation has been activated.
3.1.2.4.2 Configuring Split Valuation
UseThe purpose of this activity is to configure split valuation.
Prerequisites
Procedure 1. Access the activity using one of the following navigation options:
Transaction Code OMWC
IMG Menu Materials Management Split Valuation Configure Split Valuation
2. On the Split Valuation of Materials screen, choose Local definitions.
3. On the Local Definitions: Select Plant screen, choose plant BP01.
4. Choose Cats.-> OU.
5. On the Plant BP01: Allocate Valuation Categories screen, choose Valuation Categories X Automat.(Batch).
6. Choose Activate.
7. Choose Save.
8. Choose Back.
ResultThe split valuation categories for automotive (batch) have been activated in plant BP01.
© SAP AG Page 25 of 25
top related