A01 BB Configguide en de
A01 BB Configguide en de
00
March 2007
English
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices Automotive Basic Settings: Configuration Guide
Copyright
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.
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.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
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.
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
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.
Contents
Automotive Basic Settings: Configuration Guide..........................................................................10
1 Purpose................................................................................................................................. 10
2 Preparation............................................................................................................................ 10
2.1 Prerequisites................................................................................................................ 10
2.1.1 Building Blocks........................................................................................................ 10
3 Configuration in the Supplier System.....................................................................................10
3.1 Basic Settings.............................................................................................................. 10
3.1.1 User Maintenance for DIMP....................................................................................10
3.1.2 Client Settings (Create Logical System and Maintain Client Settings)....................11
3.1.3 Creating RFC Destination........................................................................................ 12
3.2 Organizational Enhancements.....................................................................................13
3.2.1 Creating Storage Location.......................................................................................13
3.2.2 Defining Storage Conditions....................................................................................14
3.2.3 Assigning Picking Locations....................................................................................15
3.2.4 Creating Warehouse............................................................................................... 16
3.3 Financial Accounting................................................................................................... 16
3.3.1 Creating Bank.......................................................................................................... 16
3.4 Automatic Posting........................................................................................................ 17
3.4.1 Defining Selection Rules for Payment Advice Notes...............................................17
3.4.2 Assigning Selection Fields for Payment Advice Notes............................................18
3.5 Controlling................................................................................................................... 18
3.5.1 Changing Message Control for CO with different Profit Center...............................18
3.5.2 Transfer of Billing Documents-Assign Value Fields.................................................19
3.6 Logistic General........................................................................................................... 20
3.6.1 Changing Maintenance Status of Screen................................................................20
3.6.2 Defining Partner Roles............................................................................................ 20
3.6.3 Maintaining Terms of Payment................................................................................21
3.7 Sales & Distribution..................................................................................................... 22
3.7.1 Defining Attributes for System Messages No. 295..................................................22
3.7.2 Defining Account Groups and Field Selection for Customers..................................22
3.7.3 Defining Mandatory Partner Function for Customer Master....................................23
3.7.4 Defining General Parameters for SD Self-Billing.....................................................24
3.7.5 Maintaining EDI Partner Parameters.......................................................................25
3.7.6 Defining Tolerance Group.......................................................................................26
3.7.7 Setting Tolerance Check.........................................................................................26
1 Purpose
This 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.
2 Preparation
2.1 Prerequisites
2.1.1 Building Blocks
Before you start installing this building block, the installation of the following building blocks must
have been completed:.
Use
Create default system users for system connection and communication.
Users created automatically are assigned the profiles SAP_ALL and SAP_NEW, which
gives them full authorization rights. If this authorization does not apply to your project,
you should restrict the rights of the user according to your internal authorization
guidelines. See SAP Note 0338537 for some guidelines.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Tools Administration User Maintenance Users
Transaction Code SU01
2. On the User Maintenance: Initial Screen, enter RFCUSR in the User field.
3. Choose Create.
4. On the Address tab page, enter RFC USER in the Last Name field, and RFC USER in the First
Name field.
5. Go to Logon Data and enter the initial password initial, and set the user type as
Communication.
6. On the Defaults tab page, enter the logon language as EN, and keep the default decimal
notation as 1.234.567, 89 and the date format DD.MM.YYYY.
7. On the Profiles tab page, enter the profiles SAP_ALL and SAP_NEW.
8. Choose Save.
9. Repeat the above steps to create the following users:
User Name Last Name First Name Logon Initial Profile 1 Profile 2
Lang. Passwor
d
ME- TESTUSER TESTUSER initial SAP_AL SAP_NE
TESTER EN L W
CUSTOME CUSTOMER TESTUSER initial SAP_AL SAP_NE
R EN L W
SUBCON SUBCON TESTUSER initial SAP_AL SAP_NE
EN L W
AM-USTER AUTOMOTIV TESTUSER initial SAP_AL SAP_NE
E EN L W
AS-TESTER OEM cFolders- initial SAP_AL SAP_NE
EN L W
SUPPLIER SUPPLIER SUPPLIER initial SAP_AL SAP_NE
EN L W
You can refer to the following file for details of the master data:
SMB0V_SU01_O001_A01_SUP.TXT.
Result
The system users have been created.
Use
The purpose of this activity is to maintain the client settings to ensure that the implementation
activities to implement your solution be supported.
Procedure
2. On the Display View: Clients: Overview screen, switch to the change mode.
3. Select your current client and choose Details.
4. Maintain the following settings:
Field name Description User action and values Note
ORT01 City <Your Location>
LOGSYS Logical System Select the logical system of Defined before
the current client
MWAER Std Currency EUR
CCCATEGORY Client Role Customizing
CCCOR_ACTV Automatic Recording select
of Changes
CCNOCLIIND Cross-Client Object Changes to Cross-Client
Changes Customizing and
Repository Objects allowed
Use
For SAP Best Practices Automotive, you need to set logical system destination.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SM59
IMG Menu Tools Administration Administration Network RFC
Destinations
2. On the Display and maintain RFC destinations screen, select the R/3 connections entry and
choose Edit Create.
3. On the RFC Destination screen, enter the system name in the RFC destination field. Enter 3
in the Connection type field. Enter Logical System Name (For example
ES6CLNT050) in the Description field and choose Enter.
4. Choose Save.
5. Now check that the RFC connection works, by choosing Test connection. If successful, the
connection time is displayed in msecs. Return to the RFC Destination XXXXXXXXX screen.
6. Choose Save.
7. Choose System information Remote logon. A new session opens after the test
successfully running.
8. Choose Back to return to the SAP Easy Access menu.
Refer to the following file for details of the master data required:
SMB0V_SM59_O001_A01_SUP.TXT
Result
You have created the RFC destinations in the system.
Use
In this step you create a storage location, which is the place where stock is physically kept within
a plant.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code OX09
IMG Menu Enterprise Structure Definition Materials Management
Maintain Storage Location
2. On the Determine Work Area: Entry, enter BP02, and choose Enter.
3. On the Change View Storage Locations: Overview screen, enter the following.
SLoc Description
0005 lean WM&HU
0006 Component FullWM
0007 Sparepart FullWM
4. Choose Save.
Result
You have created the storage locations.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SPRO
IMG Menu Logistics Execution Shipping Picking Determine Picking
Location Define Storage Conditions
2. On the Change View Storage Conditions Overview screen, press New Entries (F5) and enter
the following Storage Conditions.
SC Description
03 Customer Packaging
K1 Lean WM
Y1 Config & Service
YH HUM
K2 Full WM
3. Choose Save.
4. Choose Back (F3).
Result
You have created the storage conditions.
Use
In this step you assign the picking locations to the combinations of shipping point and storage
condition for every plant.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code OVL3
IMG Menu Logistics Execution Shipping Picking Determine Picking
Location Assign Picking Locations
2. On the Change View Picking Location Determination: Overview screen, enter the following.
ShPt Plnt SC SLoc
BP01 BP01 0010
BP01 BP01 02 0002
BP01 BP01 K1 0005
BP01 BP01 K2 0007
BP02 BP02 0010
BP03 BP03 0010
BP0X BP0X 0007
BP0X BP0X 01 0010
3. Choose Save.
Result
You have assigned the picking locations.
Use
In this step you create a warehouse. A warehouse complex is represented in the Warehouse
Management system as a warehouse number that is used to identify a complex warehouse
setup. The physical location is decisived for assigning the definition of the warehouse number. A
warehouse number group together storage types and storage bins that are organized and
maintained as a complete unit
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SM30 with Customizing Object V_T3001
IMG Menu Enterprise Structure Definition Logistics Execution Define,
copy, delete, check warehouse number
4. Choose Save.
Result
You have created the warehouses.
Use
The purpose of this activity is to create bank master data.
Procedure
2. On the Create Bank: Initial Screen, maintain the values in the following fields:
Field name Description User action and values Note
Bank country DE
Bank Key 20080040
3. Choose Enter.
4. On the Create Bank: Detail Screen, maintain the values in the following fields:
Field name Description User action and values Note
Bank name Dresdner Bank
5. Choose Save.
6. Repeat step 1 - 5 to create the following bank master records:
Bank Country Bank Key Bank Name
DE 40030020 Bank B
DE 10020030 Deutsche Bank
US 11000390 Bank B
Result
You have maintained the bank master data.
Use
In this activity you make the preparations for the correct identification of open items.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting (New) Accounts Receivable and
Accounts Payable Business Transactions Incoming
Payments Incoming Payments Global Settings
Payment Advice Notes (Incoming) Define Selection Rules
3. Choose Save.
Use
In this step you assign internal selection fields, that is, selection fields the system knows, to external
selection fields (data the customer sends you, such as a delivery note number) under a certain selection
rule.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OBCU
IMG Menu Financial Accounting (New) Accounts Receivable and
Accounts Payable Business Transactions Incoming
Payments Incoming Payments Global Settings
Payment Advice Notes (Incoming) Allocate selection fields
3. Choose Save.
3.5 Controlling
3.5.1 Changing Message Control for CO with different Profit
Center
Use
Change message control to allow CO account assignment with different profit center.
Procedure
1. Access the activity using one of the following navigation options:
2. On the Determine Work Area: Entry screen, enter the following data:
Field name Description User action and Note
values
Application Area BK
3. Choose Enter.
4. On the Change View “Message Control by User”: Overview screen, choose New Entries (F5).
5. On the New Entries: Overview of Added Entries screen, make the following entry.
Field name Description User action and Note
values
MsgNo 134
Online ─ Switch off message
BatchIs ─ Switch off message
6. Choose Save.
Result
The system switches off the message control for CO account assignment with different Profit
Center.
Use
Define how billing document items for sales from stock are transferred to Profitability Analysis.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Controlling Profitability Analysis Flows of Actual Values
Transfer of Billing Documents Assign Value Fields
6. On the New Entries: Overview of the Add Entries Screen, making the following data:
Field name Description User action and values Note
CType Condition Type PDIF
Val.fld PRABA
7. Choose Save.
Use
The purpose of this activity is to change Maintenance Status of Screen for discrete industries.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OMT3B
IMG Menu Logistics - General Material Master Configuring the
Material Master Define Structure of Data Screens for Each
Screen Sequence
2. On the Change View Screen sequences: Overview screen, choose entry DI Discrete
Industries.
3. Double-click Data screens folder on the left part of the screen.
4. On the Change View Data screens: Overview screen, find the following entry:
Field name Description User action and values Note
SSq Screen sequences DI
Scrn Logical screen 90
6. Choose Save.
Result
You have changed the Maintenance Status of Screen.
Use
The purpose of this activity is to define partner role TK tracking partner.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Material Management Purchasing Partner Determination
Partner Roles Define Partner Roles
2. On the Change View Definition of Partner Roles: Overview screen, choose New Entries (F5).
3. Make the following entry:
Field name Description User action and values Note
Funct Partner function TK
Name Partner function Tracking partner
description
NoTpe Type of partner KU
number
Unique Uniqueness in the X
master data
HigherPar. Role Higher-level
partner function
4. Choose Save.
Result
You have defined partner role TK tracking partner.
Use
The purpose of this activity is to create new terms of payment.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Materials Management Purchasing Vendor Master
Define Terms of Payment
Account Type: X
Vendor
Fixed day 25
Additional months 1
4. Choose Save.
Result
You have created the terms of payment AUTO.
Use
Create system message No. 295.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OPJB
IMG Menu Plant Maintenance and customer Service Maintenance and
Service Processing Configuration Control Define
Attributes for System Messages
2. On the Change View System Messages: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following information:
Field name Description User action and values
Version Message control version 00000000
Appl.A. Application Area C2
No. Message number 295
4. Choose Save.
5. Choose Back to return to the SAP Easy Access screen.
Result
You have system message No. 295.
Use
In this activity, you define the account groups to which you assign customer master records with
the same features (for example, group of one-time customers, group of ship-to-parties).
Common features include:
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OVT0
IMG Menu Logistics - General Business Partner Customers Control
Define Account Groups and Field Selection for Customers
2. On the Change View Customer Account Groups: Overview screen, choose New Entries and
make the following entries:
Field Name Description User Action and Values
Account group YA01
Description Sold-to Party BP
Number range XX
CentrTextDetPrc 01
TextDetProc SD 01
Cust.pric.proc. 1
PartnDet.Proc. AG
Result
You have defined Account Group and Field Selection for Customers.
Use
Define some partner functions as mandatory.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code VOPA
5. Ensure partner function SP, BP, PY, and SH have been selected as mandatory partner
function.
6. Choose Save.
Result
The partner function SP, BP, PY, SH have been marked as mandatory.
Use
In this activity, you set the general parameters for the automotive enhancement to SD self-billing.
We set following items:
The time delay for the transmission number (it only makes sense to do this if the external
transmission number is created from the date).
The permitted time period during which processing can be started (for example, only
during the night, to maintain system performance). This enables you to plan processing
for a time at which system performance is less critical (for example, between 12am and
6am).
The order reasons and document types for automatic postings or open items (so that
the cause of the automatic posting or new open item - value or quantity difference - can
be seen in financial accounting).
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OVD4
IMG Menu Sales and Distribution Billing SD Self-Billing Procedure
(Automotive) Maintain General Parameters
if value/quant.
variance
3. Choose Save.
Use
In this step, you can set the processing parameters for the EDI partner.
How the transmission is ended (when target number of IDocs reached, or when
processing started).
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Sales and Distribution Billing Billing Document Self-
Billing Procedure (Automotive) Setting Maintain EDI
Partner Parameters
Transaction Code OVD5
transmission processing
Delay time for start 01:00:00
Make sure that you have set right logical system name in the field of Partner Number.
To get right partner number, you can use the following menu paths:
SAP Menu IMG SAP Web Application Server Application Link
Enabling (ALE) Sending and Receiving Systems Logical
Systems Assign Client to Logical System
Transaction Code SPRO
3. Choose the right client (OEM client in your system landscape) and check the details for
Logical system.
4. Choose Save.
Use
In this step, you define a blank tolerance groups that group together tolerance limits for creating
new open items.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Sales and Distribution Billing SD Self-Billing Procedure
(Automotive) Maintain Tolerance Groups
Transaction Code OVD6
3. Choose Save.
Use
In this step, you define the percentage tolerance limits for your tolerance group.
Prerequisites
Tolerance groups have been defined in previous step.
Procedure
For tolerance group YG02 in which has deactivated all checks, the system never
create new open items where this tolerance group is used.
3. Choose Save.
Use
This step allows you to define the item categories for deliveries.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OVLP
IMG Menu Logistics Execution Shipping Deliveries Define Item
2. On the Change View Delivery item categories: Overview screen, choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
Item category YZN
Document cat. J
Check quantity 0 A
Check overdelivery A
AvailCkOff X
Relevant for picking
StLocation required
Determine SLoc
4. Choose Save.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SPRO
IMG Menu Financial Accounting (New) Accounts Receivable and Accounts
Payable Vendor Accounts Master Data Preparations for
Creating Vendor Master Data Define Account Groups with Screen
Layout (Vendors)
2. On the Change View Vendor Account Group Overview Screen, Select Group 0007 to Choose
Details (F2).
3. On the Change View Vendor Account Group Details Screen, double click General data under
Field Status.
4. On the Maintain Field Status Group: Overview Screen, double click Contact Person under
select group.
5. On the Maintain Field Status Group: Contact Person Screen, Choose the Opt. entry radio
button for Contact Person.
6. Choose Save.
Use
The purpose of this activity is to maintain plant parameters.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SM30 with Customizing Object V_159L
IMG Menu Materials Management Inventory Management and Physical
inventory Plant Parameters
2. On the Change View General plant settings in inventory Management: Overview screen,
select Plant BP01, and make the following entries.
Field Entry
Del. Compl. Default X
BBD/Prod Date X
BOM Usage 1
BOM Application BEST
Trans./Event Type WV
Stock type 1
Alternative unit X
Batch in background X
Movement allowed X
Days mvt. Allowed 10
Retention period 30
Result
You have maintained the plant parameters.
Use
Activate the possibility to work with Manufacturer part number.
1. To access the activity, choose one of the following navigation options:
Transaction Code OMT0
2. On the Change View General Control Indicators: Details screen, make the following entries:
Field name Description User action and values Note
General control indicators:
Updating S
Std document type DRW
Std country (retail) DE
Reference materials:
Manufacturer part no. Activate Keep the standard
settings for the
Reference materials
and Activate
Manufacturer part no.
Result
You now can work with manufacturer part number.
Use
The purpose of this activity is to create material group.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OMSF
IMG Menu Logistics - General Material Master Settings for Key
Fields Define Material Groups
2. Refer to the following table for details of the master data required:
Matl group Matl grp description
1000 Kanban material
P01 Packaging material 1
P02 Packaging material 2
Result
You have created a new material group.
Use
The purpose of this activity is to deselect the partner function TK in standard partner
determination procedure TA.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Basic Functions Partner
Determination Setup Partner Determination Set Up
Partner Determination Set Up Partner Determination for
Sales Document Header
2. On the Change View Partner Determination Procedures: Overview screen, choose the
partner determination procedure TA.
3. Double-click Partner Functions in Procedure on the left side of the screen.
4. Maintain the values in the following fields:
Field name Description User action and values Note
Part. Det. Proc Partner TA
determination
procedure
Partn. Funct. Partner function TK
Mandat. Funct. Mandatory function Deselect the
checkbox
5. Choose Save.
Result
You have deselected the partner function TK from the partner determination procedure TA.
Use
Define partner schemas which allow you to group together different partner roles.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu IMG Material Management Purchasing Partner
Determination Partner Settings in Purchasing Documents
Define Partner Schemas
2. On the View Partner Schemas Purchasing documents Change: Overview screen, Choose
New Entries.
3. Name this new partner schema Y001, and enter description Scheduling Agreement.
4. Choose Enter.
5. Choose Save.
Result
The new partner schema Y001 has been created.
Use
Define partner schemas which allow you to group together different partner roles.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu IMG Material Management Purchasing Partner
Determination Partner Settings in Purchasing Documents
Define Partner Schemas
2. On the View Partner Schemas Purchasing documents Change: Overview screen, Select
Partner Schemas Y001.
3. Double click Partner Functions in Procedure in left Area.
4. On the View Partner Schemas Purchasing documents Change: Overview screen, make the
following entries:
Field No Change Mandatory End Higher Level Note
name
OA
VN Select Select Select
PI
GS
5. Choose Enter.
6. Choose Save.
Result
The new partner function of schema Y001 has been maintained.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu IMG Material Management Purchasing Partner
Determination Partner Settings in Purchasing Documents
Assign Partner Schemas to Document Types
2. For purchasing document type LPA, assign partner schema Y001 to it.
3. Choose Save.
Result
The new partner schema Y001 has been assigned to scheduling agreement LPA.
Use
Assign the partner schemas to account group 0007 (plant).
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Material Management Purchasing Partner Determination
Partner Settings in Vendor Master Record Assign Partner
Schemas to Account Groups
3. Choose Save.
Result
The partner schemas have been assigned to account group.
Use
The purpose of this activity is to define permissible partner roles per account group.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu IMG Materials Management Purchasing Partner
Determination Partner Roles Define Permissible Partner
Roles per Account Group
2. On the Change View Permissible Partner Roles per Account Group: Overview screen,
choose New Entries and maintain the following data:
Funct Group
OA 0007
VN 0007
PI 0007
CR 0005
GS 0007
3. Choose Save.
Result
The permissible partner roles per account group are defined.
Use
The purpose of this activity is to maintain the profiles that control the transfer of stock and sales
data by IDoc to vendors.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Materials Management Purchasing Messages EDI
Profiles for Sending Stock/Sales Data
2. On the screen Change View Maintain Control Profile: Details, choose New Entries.
3. Maintain the values in the following fields:
Field name Description User action and values Note
PROACT control AM01
profile
Selection key Only S1
materials of
vendor
Transfer stock level X
Do not transfer zero X Under the
qties Transfer stock
level
Transfer current X Under Transfer
period quantity sold
4. On the left part of the screen, double-click Maintain Stock Types per Profile.
5. On the screen Change View Maintain Stock Types per Profile: Overview, choose New
Entries.
6. Maintain the values in the following fields:
Field name Description User action and values Note
Stock Type LABST
Description Unrestricted use
Result
You have created the profiles for sending stock/sales data AM01.
Use
In this step, you can define the release creation profile, which controls the creation periodicity of
the releases and - starting from the current date of release creation - the way in which the
quantities are aggregated.
Via the creation profile, you can specify that a tolerance check is to be carried out in the case of
releases generated on the strength of changed schedule lines.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Material Management Purchasing Scheduling
Agreement Maint. Rel. Creation Profile for Sched. Agmt.
w. Rel. Docu.
2. On the Change View “Release Creation Profile”: Overview screen, choose the following item:
Field name Description User actions and values Note
Plnt Plant 0001
Profile Release creation profile 0001
Description for release Description for release 14 days JIT and 6 months FRC
creation profile creation profile
6. Choose Enter.
7. Choose Save and Back.
8. On the Change View “Release Creation Profile”: Overview screen, choose the following item:
Field name Description User actions and values Note
Plnt Plant 0001
Profile Release creation profile 0001
Description for release Description for release 14 days JIT and 6 months FRC
creation profile creation profile
11. On the Change View “Release Creation Profile”: Details of Select screen, make the following
entries:
Field name User actions and values
General Parameters Tab
JIT Delivery Schedule Creation Changed Only
Strategy
FRC Schedule Creation Strategy Changed Only
Aggregation horizons in workdays Tab
JIT Delivery Schedule No Aggregation
17. On the Change View “Release Creation Profile”:Details of Select screen, make the following
entries:
General Parameters Tab
JIT Delivery Schedule Creation Strategy Changed Only
FRC Schedule Creation Strategy Changed Only
Determine backlog/imm. Reqt.: Select
Backlog Creation-relevant: Select
Result
Different Creation profiles have been defined and can be used in respective scenarios.
Use
The SAP System manages scheduling agreements as documents. You can group scheduling
agreements together to form any number or document types.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Material Management Purchasing Scheduling Agreement
Define Document Types
2. On the Document Types Scheduling agreement Change screen, choose document type LU
item.
3. Choose Copy as…(F6).
4. On the Document Types Scheduling agreement Change screen, make the following entries:
Field name Description User actions and values Note
Type Document Type YLUC
Control Control indicator for purchasing type Set empty
Results
A new purchasing scheduling agreement type YLUC has been defined.
Use
The vendor determines the correct SD scheduling agreement using the
purchase order number. When this is carried out, the LVED4FZZ program in the
user exit USEREXIT_M_CODE_AUSWAHL checks whether the outline agreement
number in the customer’s procurement scheduling agreement, which is
transferred in the IDoc, is the same as the purchase order number in the SD
scheduling agreement.
Since standard deliverables of SAP Best Practices for Automotive does not allow
direct changes to the standard programs, we have to implement the modification
manually.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SE38
6. Load the source code from USEREXIT_M_CODE_AUSWAHL.txt under MISC folder on the
DVD.
7. Choose Save.
8. Choose Activate.
You must to be registered as a developer and reggisterd the object as well to make
this modification. Otherwise, the system refuses any change of the standard source
code change.
Use
In this activity you define transportation connection points.
A connection point can be one of the following:
An airport
A border crossing
A railway station
Procedure
3. Choose Save.
Results
The following transportation connection points have been created:
DES1, which represents shipping point BP01.
Use
In this activity, you can set the route determination per country of departure/departure zone and
country of destination/receiving zone in the sales order or delivery.
Prerequisites
Transportation zone has been assigned to Ship-to party.
The transportation group has been maintained in the material master data.
For Transportation Group You can check it according to the following menu path:
SAP Menu SAP Easy Access Materials Management Material
Master Material Display Display Current
Transaction Code MM03
Procedures
2. On the Change View “Ctry of Dep. /Dep. Zone and Dest. /Recv. Zone” screen, Select the
following entry:
Field name Description User actions an values Note
CDEP Departure Country DE
DEPZ Departure Zone 0000000001
DESC Destination Country DE
RecZ Destination Zone 0000000001
5. Choose Enter.
6. Choose copy all, in the following screen.
7. Choose Save.
If the vendor has created several deliveries (documents), the standard SAP System always
attempt to combine these deliveries in one invoice after it create the SD invoice. To do so, the
system checks specific data (for example, whether the payer customer number, terms of
payment, and so on are the same). If the result of this check is positive, one invoice can contain
all the deliveries. Invoice combination can be carried out with the following transactions:
VT12: Shipment completion (VF04 is processed in the background),
VF01: Create billing document (if several delivery numbers for billing are entered),
VF04: Process billing due list.
The customer posts a goods receipt for each delivery and sends a credit memo (IDoc = SBWAP)
to the vendor for each goods receipt. If the vendor has combined the deliveries in one invoice, the
same invoice number is found for each credit memo (via the deliver note number). In this case,
the accounting document can be given only one credit memo number.
Invoice combination is not desirable with the credit memo procedure between customer and
vendor; this is to ensure that each credit memo number can be updated in a separate
"Reference" field in the accounting document header. In the vendor's system, each delivery note
and billing document must be posted one to one. In addition, data transfer formula 901 (which
replaces data transfer formula 001) must be added to copy control: delivery with type YALF,
billing document with type YAF2, and item category YZN, this data transfer formula does not
permit invoice combination. In other words, deliveries are not combined in one invoice.
Explanation
The vendor creates a shipment with two SD deliveries for the customer. During completion of this
shipment (transaction VT12), a goods issue is posted for both deliveries; the status of the
shipment is set to "completed"; and the two deliveries are combined in one invoice (standard SAP
System).
The customer posts two goods receipts. During these postings, the customer enters the delivery
note numbers of the vendor as reference numbers. On the basis of the two goods receipts, the
credit memo procedure is carried out in the customer's system by means of two invoice
verifications: Logistics Materials Management Invoice Verification Logistics Invoice
Verification Further Processing Execute Automotive ERS. The two credit memo procedure
IDocs are sent to the vendor via EDI.
Using these "credit memo procedure" IDocs (SBWAP), the vendor's system determines the SD
invoice number via the delivery note numbers (posted with the goods receipt in the customer's
system). The system then updates the credit memo number in the invoice header. The vendor's
system interprets the MM invoice numbers as credit memo numbers.
The customer sends a credit memo for both goods receipts. Since there is only one invoice in the
vendor's system, the first credit memo number in the reference field in the accounting document
is overwritten when the second credit memo is sent.
With an invoice split in the vendor's system, this number is not overwritten. This is because there
are two invoices with two accounting documents, which means that the credit memo information
can be updated correctly in the vendor's system.
The following activities are ABAP4 program related, we recommended that this activity
is performed by one skilled ABAP4 programmer and one application consultant.
Use
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code VOFM
For maintaining German description, log on the system with log on language DE.
4. The system asks for Change Request, create a new change request and Save.
5. Activate the 901 routing by choosing Edit Activate, the system may ask you for access
key, register on OSS or SAP Service Marketplace for the access keys.
Use
In this step, you add your ABAP4 extension.
Procedure
The string VBRK-ZUKRI is generated for each delivery and delivery item. If specific header data
matches this string, the deliveries are copied to one invoice. Because the delivery note number
has been added as a string field, each delivery note and invoice is posted one to one. The string
is generated not only at the header level; it is generated for each delivery item.
NB: Data transfer formula 901 is a copy of 001.
1. Access the activity using one of the following navigation options:
Transaction Code SE80
8. Load the source code from RV60C901.txt under MISC folder on the DVD.
9. Choose Save (Create a workbench request if required).
10. Activate the program.
Use
Create production supply areas for KANBAN processing.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics Production KANBAN Supply Area Maintain
Transaction Code PK05
2. Refer to the following file for details of the master data required:
SMB0V_PK05_O001_A01_SUP.TXT
Result
You have created the three production supply areas KANBAN and PROD_MTS and PVB 0001.
Use
The purpose of this activity is to create spool parameters for users.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OPK8
IMG Menu Production Shop Floor Control Operations Define Print
Control
2. On the Change View “Names of Lists”: Overview screen, choose Spool parameters for user
from the dialog structure on the left.
3. Choose New Entries and make the following entries:
Print List List Name Output Hold Retention Immed.
list Device per.
X LG01 Object list LP01 X 2
X LG02 Op. control ticket LP01 X 2
X LG03 Goods receipt list LP01 X 2
X LG04 Kanban ticket LP01 X 2
X LV01 Time ticket LP01 X 2
Use
The purpose of this activity is to create standard value key.
Prerequisites
Related customizing must exist.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OP19
IMG Menu IMG Production Basic Data Work Center General
Data Standard Value Define Standard Value Key
3. Choose Save.
Result
You have defined the standard value key.
Use
The purpose of this activity is to create special repetitive profiles, which control the activity in
repetitive manufacturing.
Procedure
1. Access the activity using one of the following options:
Transaction Code SPRO
IMG Menu Production Repetitive Manufacturing Control Data Define
Repetitive Manufacturing Profiles
2. On the Change View Overall Maintenance of Repetitive Manufacturing Profile screen, choose
New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
Field name Description User actions and Note
values
REM profile Y001
Desc.REM profle Final backflush w/o
activities
Production type PKMN
Control data1
GI backflush at GR posting X
RP backflush
Mandatory
Optional
Automatic GR posting at last
RP when backflushing
Process control
Create cumulated X
postprocessing records
create individual
postprocessing records
Execute correction in dialog X
mode
Mandatory
Optional X
Post activity
Backflush using standard
cost estimate for material
Using data from prelim.
Costing f. prod. cost collector
Control data 2
Reduced planned order X
assigned to version
Plus planned orders not yet
assigned
Plus planned orders
assigned to other versions
Reduction period 3
Comp. Withdrawal
Corresponding to Plnd.
Orders for Processing
Do not firm
Always firm X
Firm within plng time fence
Create planned orders when
reversing
For the GR amount of the
current day
By requirement
( asynchronous MRP run)
Stock determination rule
Batch search procedure
Aggregate reqmts
Create reqmts for phantom X
assemblies
Movement
type
Goods issue 261
Goods receipt 131
Scrap 551
By-product 531
Goods issue/reversal 262
Goods receipt/reversal 132
Scrap/reversal 552
By-product/reversal 532
GR indiv.sales order 571
GI ind.stck/salesOrd 572
GI plntstk/salesOrd. 291
GR ind.sales ord./reverse 572
GI ind.stck/salesOrd/rev. 571
GI plntStck/salesOrd/rev. 292
11. On the Change View Overall Maintenance of Repetitive Manufacturing Profile screen, choose
New Entries.
12. On the New Entries: Details of Added Entries screen, make the following entries:
Field name Description User actions and Note
values
REM profile YSOZ
Desc.REM profle Final backflush w.
activities
Production type PKMN
Control data1
GI backflush at GR posting X
RP backflush
Mandatory
Optional
Automatic GR posting at last
RP when backflushing
Process control
Create cumulated X
postprocessing records
Create individual
postprocessing records
Execute correction in dialog X
mode
Mandatory
Optional X
Post activity X
Backflush using standard X
cost estimate for material
Using data from prelim.
Costing f. prod. cost
collector
Control data 2
Reduced planned order X
assigned to version
Plus planned orders not yet
assigned
Plus planned orders
assigned to other versions
Reduction period 3
Comp. Withdrawal
Corresponding to Plnd.
Orders for Processing
Do not firm
Always firm X
Firm within plng time fence
Create planned orders when
reversing
For the GR amount of the
current day
By requirement
(asynchronous MRP run)
Stock determination rule
Batch search procedure
Aggregate reqmts
Create reqmts for phantom X
assemblies
Movement type
Goods issue 261
Goods receipt 131
Scrap 551
By-product 531
Goods issue/reversal 262
Goods receipt/reversal 132
Scrap/reversal 552
By-product/reversal 532
GR indiv.sales order 571
GI ind.stck/salesOrd 572
GI plntstk/salesOrd. 291
GR ind.sales ord./reverse 572
GI ind.stck/salesOrd/rev. 571
GI plntStck/salesOrd/rev. 292
Use
The purpose of this activity is to maintain the cost view of work center (production line in repetitive
manufacturing). So that, activity cost could be posted into production.
Procedure
1. Access the activity using one of the following navigation options:
Transaction OP67
IMG Menu Production Basis Data Routing Operation Data Define
control key
2. On the Change View Control key for operations: Overview Screen, choose New Entries.
3. On the New entries: Details of Added Entries screen, enter the following values:
Field name Description User actions and values Note
Control key YP01
Description Routing/Ref. op. set - internal
proc.
Scheduling X
Det.Cap. Reqmnts X
Insp. char. required
Aut. goods receipt
Print time tickets X
Rework
Print confirmation X
Print X
Cost X
Sched. external op.
External processing
Confirmations 1
Print confirmation X
Print X
Cost X
Sched. external op.
External processing
Confirmations 1
3.13 KANBAN
Procedure
Even-Driven KANBAN
In this building block, only classic KANBAN is used.
Use
In the classic KANBAN production control method, the demand source, the supply source and the
procedure to be used to replenish the material are defined in the control cycle as well as the
number of KANBANs that circulate between the supply source and the demand source and the
quantity per KANBAN.
In this classic KANBAN procedure, the KANBAN signal always only triggers replenishment for the
KANBAN quantity defined in the control cycle. Moreover, you cannot circulate more KANBANs
than are defined in the control cycle without changing the control cycle first.
In KANBAN production control, depending on the setting in the material master, you have two
options for organizing replenishment: with or without MRP:
Without MRP: Replenishment is only triggered by the KANBAN signal. Materials for
which replenishment is only triggered by the KANBAN signal are not planned in the
planning run. However, you can include these materials in long-term planning.
With MRP: The materials are planned in the planning run and corresponding
procurement proposals are created. These procurement proposals do not directly trigger
replenishment but provide a preview of future consumption. In this process,
replenishment is triggered by the KANBAN signal.
Four different kinds of replenishment strategies are preconfigured in this building block to be used
in different scenarios. Therefore four sets of master data are set up for these four replenishment
strategies. In this building block, all the four kinds of replenishment strategies are used as with
MRP.
KANBAN Control
The functions of KANBAN control explain, amongst other things, how the signal is triggered to
replenish a material and which replenishment strategies are available. In this building block, the
setting is focusing on different replenishment strategies. And use system default and standard for
the other setting such as KANBAN signal and KANBAN board and so on.
Use
There are several replenishment strategies available for in-house production. With following
steps, you have all the necessary settings for replenishment using Run Schedule Quantities.
You use this function when you produce the necessary material yourself, using repetitive
manufacturing. As soon as a KANBAN is set to EMPTY the system creates run schedule
quantities for this material, for example planned orders for repetitive manufacturing, and this
triggers production.
In this step, you define the settings for the replenishment strategies for materials that are
produced in-house.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Production KANBAN Replenishment Strategies Define
In-House Production Strategies
2. On the Change View "Control Key; In-House Production": Overview screen, select the
following entry:
Field name Description User actions and values Note
Plnt 0001
In-hseProd 0004
Description of Container control / MRP
Replenishment
Strategy
5. Choose Enter.
6. Choose Save (Ctrl + S).
7. Choose Back (F3).
Use
There are several replenishment strategies available for external procurement. With following
steps, you have all the necessary settings for replenishment using Scheduling Agreement.
You use this function when you have negotiated a scheduling agreement with a vendor for a
certain material. The scheduling agreement determines the purchase quantity for a longer period
of time. As soon as a KANBAN is set to EMPTY, the system generates a schedule line for this
scheduling agreement.
In this step, you define the settings for the external procurement strategies.
Procedure
2. On the Change View "Control Key; External Replenishment": Overview screen, select the
following entry:
Field name Description User actions and values Note
Plnt 0001
Ext.proc. 0006
Description of Container control / MRP
Replenishment
Strategy
5. Choose Enter.
6. Choose Save (Ctrl + S).
7. Choose Back (F3).
Use
There are several replenishment strategies available for stock transfer. With the following steps,
you have all the necessary settings for replenishment using Direct Transfer Posting.
You use this function when you want to transfer components without any previous reservation.
When the KANBAN is set to EMPTY it automatically triggers a transfer posting.
Procedure
2. On the Change View "Control Key; Stock Transfer": Overview screen, select the following
entry:
Field name Description User actions and values Note
Plnt 0001
In-hseProd 0002
Replenishment Working with direct transfer
Strategy posting
Description
5. Choose Enter.
6. Choose Save (Ctrl + S).
7. Choose Back (F3).
Use
In this step, you define the parameters for the calculation profile for the automatic kanban
calculation.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Production KANBAN Automatic KANBAN Calculation
Define Calculation Profile
2. On the Change View "Kanban Calculation Profile": Overview screen, select following entry:
Field name Description User actions and values Note
Plnt 0001
Calc 0001
5. Choose Enter.
6. Choose Save (Ctrl + S)
7. Choose Back (F3).
3.14 HR Settings
3.14.1 Generating HR Tables
Use
The purpose of this activity is to maintain HR Features.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Human Resources Time Management Administration
Tools Tools Selection Maintain Features
Transaction Code PE03
2. Choose Activate.
3. Go to Generate features screen, choose Execute.
4. System then displays the generated result.
5. Choose Back.
Result
The HR Features are maintained.
Procedure
1. Access the activity using one of the following navigation options:
Result
The HR Features are maintained.
Procedure
1. Access the activity using the following navigation option:
Transaction Code SM30
Result
You have created global settings for personnel groups.
Use
The purpose of this activity is to maintain assignment of corporate features.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Payroll Payroll: Germany Basic Settings Maintain
Assignment of Corporate Features
2. In the Choose Activity dialog box, double click on Generated Table for View V_T5D0P.
3. On the Change View “Assignment of Company Features”: Overview screen, maintain the
following data:
Personnel Personnel Company West/East State Community no.
area sub area number indicator
BP01 0001 21223673 W 8226095
BP01 0002 21223673 W 2000000
BP0X 0001 21223673 W 8226095
BP0X 0002 21223673 W 2000000
4. Choose Save.
Result
You have maintained the assignment of corporate features.
Procedure
1. Access the activity using the following navigation option:
Transaction Code OOCM_AD
IMG Menu Personnel Management Compensation Management
Planning and Administration Set Control Parameters
Result
You have simplified the maintenance of Human Resources master data.
Procedure
1. Access the activity using one of the following navigation options:
Result
You have created feature data in the personnel management of HR to be used in the scenarios.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Human Resources Personnel Management Administration
HR Master Data Personnel Actions
Transaction Code PA40
2. Refer to the following file for details of the master data required:
SMB0V_PA40_O001_A01_SUP.TXT.
Result
You have created the necessary personnel master data.
Use
The purpose of this activity is to maintain personnel master data in HR.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Human Resources Personnel Management Administration
HR Master Data Maintain
Transaction Code PA30
2. On the Maintain HR Master Data screen, maintain the personnel master records with the
personnel number 5.
3. Refer to the following file for details of the master data required:
SMB0V_PA30_O001_A01_SUP.TXT.
Result
You have maintained the personnel master data records.
Use
The purpose of this activity is to maintain the address.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Tools ABAP Workbench Development ABAP Editor
Transaction Code SE38
Result
You have maintained the address.
Use
The purpose of this activity is to generate the variable field movement.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Tools ABAP Workbench Development ABAP Editor
Transaction Code SE38
Result
You have generated the variable field movement.
Use
The purpose of this activity is to maintain workflow standard settings. Checks are performed to
establish whether Customizing is complete with regard to further important settings. You can start
an initial verification workflow.
Automatic Workflow Customizing does not cover maintenance of the organizational plan nor task-
specific Customizing (assignment between tasks and possible agents and activation of triggering
events - - this has to be done at scenario level).
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Tools Business Workflow Development Utilities
Verify Customizing
Transaction Code SWU3
Result
You have activated the standard workflow settings.
Use
The purpose of this activity is to delete unnecessary warehouse assignment.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SM30
IMG Menu Enterprise Structure ® Assignment ® Logistics Execution ®
Assign warehouse number to plant/storage location
2. Choose Maintain.
3. On the Change View “MM-IM Storage Location <-> LE-WM Warehouse Number”: Overv
screen, choose the following entry:
Plant Storage location Wharehouse
BP01 0005 100
4. Choose Delete.
5. Choose Save.
6. On the screen Prompt for Customizing request, choose an appropriate change request or
create a new customizing request.
7. Choose Continue (Enter).
Result
Use
In this activity, you specify which payment methods are to be used in each country.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Financial Accounting (New) Accounts Receivable and
Accounts Payable Business Transactions Incoming
Payments Automatic Incoming Payments Payment
Method/Bank Selection for Payment Program Set Up
Payment Methods per Country for Payment Transactions
2. On the Change View "Payment Method/Country": Overview screen, select the line with the
following key value:
Field name Description User action and Note
values
Country DE Germany
Pmt method U Überweisung
3. Choose Details.
4. On the Change View "Payment Method/Country": Details screen, make the following entries:
Field name Description User action and Note
values
Payment method
classification
Allowed for X Check the check box
personnel payments
Required master
record
specifications
Bank details X Check the check box
Posting details
Document type for ZP
payment
Clearing document ZV
type
Payment medium
Use classic payment X select
medium program
(RFFO*)
Payment medium RFFOD__U
program
Name of print LIST3S
dataset
5. Choose Save.
Result
You have set up payment method for Germany.
4.5 Controlling
4.5.1 Changing Characteristic Derivation
The Changing Characteristic Derivation settings in the OEM system are the same as those in the
Supplier system.
Refer to Changing Characteristic Derivation in the Supplier system.
4.11 KANBAN
4.11.1 Defining Time Definition
Use
In this step, you define time definitions for summarizing JIT calls to the minute or to the day.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Production KANBAN JIT Call Define Time Definition
Use
In this step, you define the settings for the external procurement strategies.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Production KANBAN Replenishment Strategies Define
External Procurement Strategies
2. On the Change View 'Control Key; External Replenishment": Overview screen, select the
following entry:
Field name Description User actions and values Note
Plnt 0001
Ext. Proc. 0007
Description of Summarized JIT calls (w/o
Replenishment summary)
Strategy
5. Choose Enter.
6. Choose Save (Ctrl + S).
7. Choose Back (F3).
Use
In this step, you define your message schema for the summarized JIT call and assign it
accordingly.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Production KANBAN JIT Call Message Control For
Summarized JIT Call Define Message Pattern for
Summarized JIT Call
8. Choose Save.
9. Choose Back (F3) twice.
5.4 Controlling
5.4.1 Changing Characteristic Derivation
The Changing Characteristic Derivation settings in the SALES system are the same as those in
the Supplier system.
Refer to Changing Characteristic Derivation in the Supplier system.
Use
Define how billing document items for sales from stock are transferred to Profitability Analysis.
Procedure
1. Access the activity using one of the following navigation options:
7. Choose Save.
Use
The purpose of this activity is to give the possibility to create a classification view for service
materials.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu IMG Logistics - General Material Master Basic Settings
Material Types Define Attributes of Material Types
Result
You can now maintain a classification view for a service material.
Use
In this activity, you define the account groups to which you assign customer master records with
the same features (for example, group of one-time customers, group of ship-to-parties).
Common features include:
Structure of the master record input screens (field status)
Number ranges
Number assignment (internal/external)
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OVT0
IMG Menu Logistics - General Business Partner Customers Control
Define Account Groups and Field Selection for Customers
2. On the Change View “Customer Account Groups”: Overview screen, choose New Entries and
make the following entries:
Field Name Description User Action and Values
Account group YA01
Description Sold-to Party BP
Number range XX
CentrTextDetPrc 01
TextDetProc SD 01
Cust.pric.proc. 1
PartnDet.Proc. AG
Result
You have defined Account Group and Field Selection for Customers.
Use
In this activity, you define the rules that should be used to perform automatic partner
determination. You perform the following steps:
Define the partner functions that differentiate the roles of partners in your system.
Define the partner determination procedure, and assign the key of the relevant partner object
to this procedure.
Assign the partner functions you define to the account groups
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
IMG Menu Sales and Distribution Basic Functions Partner
Determination Set Up Partner Determination
2. On the Choose Activity dialog box, choose Set Up Partner Determination for Customer
Master.
3. On the Change View “Partner Determination Procedures”: Overview screen, choose the
Partner Determination Procedures folder from the dialog structure and choose New Entries.
4. Make the following entries:
Field Name Description User Action and Values
Part.Det.Proc AS
Name Sold-To Party
5. Select your entry and choose Partner Functions in Procedure. Make the following entries:
Part.Det. Partn. Name Not modifiable Mandat.
Proc Funct. Funct
AS AA SP Contract rel. ord
AS PE Con.pers.fresh prod.
AS SP Sold-to party Set indicator Set indicator
AS CP Contact person
AS AW SH Contract rel. ord
AS ED EDI mail recipient
AS BU Buyer
AS EU Enduser for F.Trade
AS VN Vendor
AS Q1 QtyCertRec/shpTo pt
AS Q2 QtyCertRec/soldTo pt
AS BP Bill-to party Set indicator
AS PY Payer Set indicator
AS SB Spec.stock partner
AS CR Forwarding Agent
AS SH Ship-to party Set indicator
AS ER Employee respons.
6. Double-click the folder Partner Determination Procedure Assignment in the dialog structure.
Choose New Entries and make the following entries:
Field Name Description User Action and Values
Group Account group YA01
PartnerDetermProced. AG AG
7. Double-click the folder Partner Functions in the dialog structure. Choose New Entries and
make the following entries:
Field Name Description User Action and Values
Partn.Funct. AS
Name Claimant
PartnerTy. Type of partner KU
number
Error Group Incompletion 07
procedure for sales
document
Sup.Partn.Func. Higher level partner
8. Double-click the folder Account Groups – Function Assignment in the dialog structure.
Choose New Entries and make the following entries:
Partn.Funct. Name Account Grp Name
SP Sold-to party YA01 Sold-to Party BP
AS Sold-to party 0001 Sold-to Party
BP Sold-to party YA01 Sold-to Party
PY Sold-to party YA01 Sold-to Party
SH Sold-to party YA01 Sold-to Party
Result
You have defined the partner determination.
Use
In this step, you define item category group for VMS scenarios.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Sales and Distribution Sales Sales Documents Sales
Document Item Define Item Category Groups
2. On the Change View “Material: Item Category Groups in Material Master”: screen, Choose
New Entries.
3. On the “New Entries: Overview of Add Entries” Screen, make the following entry:
Field name Description
VMS0 VMS vehicle
4. Choose Save.
Use
The purpose of this activity is to define characteristic for warranty counter.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Cross-Application Components Classification System
Master Data Characteristics
Transaction Code CT04
3. Choose Enter.
4. On the New Entries: Overview of Added Entries screen, Choose Basic data Tab, maintain the
following data:
Field name Description User action and values Note
Description Mileage
Status 1 Released
Number of Chars 6
Unit of Measure KM
Exp. Display 0 No exponent
5. Set Single-value.
6. Choose Descriptions Tab, make the following entries:
Field name Description User action and values Note
Language EN
Description Mileage
7. Choose Save.
Result
Characteristic is created.
Use
The purpose of this activity is to define warranty counter.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code GM04
IMG Menu Plant Maintenance and Customer Service Master Data in
Plant Maintenance and Customer Service Basic Settings
Guarantees Define Warranty Counters
Result
Warranty counter is created.
Use
The purpose of this activity is to create master warranty external number range.
Procedure
1. Access the activity using one of the following navigation options:
2. On the Master warranty number range screen, choose from menu Group Maintain (F6).
3. On the Maintain Number Range Groups screen, choose Group Insert.
For maintaining German description, log on the system with log on language DE.
5. In the Intervals area, place the cursor on the line with Ext indicator set.
Field name Description User actions and values Note
From number A00001
To number A99999
6. Choose Insert.
7. On the Maintain Number Range Groups screen, put the cursor on the line with 1, then choose
Select Element (F2), select the box before Customer master warranty external number range,
then choose Element/Group.
8. Choose Save.
9. Confirm with Enter the appearing information transport number range intervals.
10. Choose Back to go back to the installation role.
Use
The purpose of this activity is to create the warranty general settings.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing General Settings
2. On the Change View “General Settings for Warranty Processing”: Details Screen, enter the
following data:
3. Choose Save.
Result
Warranty general setting created.
Use
The purpose of this activity is to assign the G/L account.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OWTY
IMG Menu Warranty Claim Processing Revenue Account
Determination Assign G/L Accounts
2. On the Assign G/L Accounts screen, choose Table 005 by double-clicking the line.
3. On the Change View “Acct Key” : Overview Screen, maintain the following data:
App CndTy. ChAc SOrg. ActKy G/L Account NO. G/L Account
NO.
RW KOFI IKR BP01 ERL 266390 266390
RW KOFI IKR BP01 ERS 266390 266390
4. Choose Save.
Result
G/L Account assigned successfully.
Use
The purpose of this activity is to classify document type for document splitting.
Procedure
2. On the Change View “Classify Document Type for Document Splitting”: Overview Screen,
3. Select the Document Types WR and WP, and make the following entries:
Field name Description User action and values Note
Transactn. 0000
Variant 0001
Result
Classification of the document types WR and WP for document splitting is set up.
Use
The purpose of this activity is to create the characteristic WTY_DIENMAT.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Cross-Application Components Classification System
Master Data Characteristics
Transaction Code CT04
3. Choose Create.
4. On the Create Characteristic screen, make the following entries:
Field Name User action and values Note
Basic Data Tab
Description Material
Status Released
Data Type Character Format Select from the
dropdown list
Number of Chars 18
5. Choose Save.
Result
The characteristic WTY_DIENMAT is created.
Use
The purpose of this activity is to create the class to be used for variant configuration.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Cross-Application Components Classification System
Master Data Class
Transaction Code CL01
3. Choose Enter.
4. On the Create Class screen, make the following entries:
Field Name User action and values Note
Basic Data Tab
Description Flatrates
Status Released
Char. Tab
Char. WTY_DIENMAT
5. Choose Save.
6. Repeat steps 2 to 5 making the following entries.
Field Name User action and values Note
Class WTY_SUBLET
Class type 600
Valid From Today’s Date Default
Basic Data Tab
Description Sublet
Status Released
Char. Tab
Char. WTY_DIENMAT
Result
Class WTY_FLATRATE and WTY_SUBLET are created.
Use
The purpose of this activity is to define the catalog structure.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Logistics General Equipment and Tools Management
Master Data Catalogs Define Catalog Code
4. Choose Save.
Result
The catalog structure is created.
Use
This step is to define the internal number range for warranty.
Prerequisite
Document type already exists.
Procedure
1. Access the activity using one of the following navigation options:
2. On the Warranty Claim screen, choose from menu Group Maintain (F6).
3. On the Maintain Number Range Groups Screen, from the menu choose Group Insert.
4. On the appearing Insert Group screen, make the following entries:
Field name Description User actions and values Note
Text 01
DE description: 01
From number 100000
To number 1000000
For maintaining German description, log on the system with log on language DE.
5. Choose Insert.
6. Choose Save.
7. Confirm with Enter the appearing information transport number range intervals.
8. Repeat step 2-7 to make the following entries:
Field name Description User actions and values Note
Text Group for Recall
DE description: Gruppe für
Rüeckruf
From number 80000000
To number 89999999
9. Choose Back.
Use
Define Document type number range.
Prerequisite
Document type already exists.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code FBN1
IMG Menu Financial Accounting Financial Accounting Global Settings
Document Document Number Rangers Define Number
Rangers
2. On the Number Ranges for Accounting Documents screen, enter the value BP01 (or your
personalized company code) in the Company Code field.
In our solution we use the company code BP01. If you wish to personalize your
solution and change your storage location for returnable parts to another value,
ensure you change the value ‘BP01’, to your own company code.
3. Choose Change Intervals.
4. On the Maintain Number Range Intervals Screen, choose Insert (Shift+F1).
5. On the appearing Insert Interval screen, make the following entries:
NO Year From Number To Number
WY 9999 9300000000 9399999999
6. Choose Insert.
7. Choose Save.
8. Confirm with Enter the appearing information transport number range intervals.
Result
Use
The purpose of this activity is to set the view profiles of technical objects.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Plant Maintenance and Customer Service Master Data in
Plant Maintenance and Customer Service Technical Objects
General Data Set View Profiles for Technical Objects
2. On the Change View “Definition of view profiles”: Overview Screen, Choose New entries, and
make the following entries.
Screen Group Profile Profile
Screen group equipment data SEQ Standard equipment data profile
3. Choose Enter.
4. Select the Screen group you just entered, and double click Activity and layout of views.
5. On the Change View “Activity and layout of views “: Overview Screen, maintain the following
data:
Number Descriptn Table Active Seq. No Seq. No Seq. No
10 General X 005 010 015
20 Location X 020 025
30 Organization X 110 030 035
50 Structure X 040 045
60 Additional data 1 X 100
100 Additional data 2 X 110
120 Other X 095
6. Choose Save.
Use
The purpose of this activity is to set the texts for the views
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Plant Maintenance and Customer Service Master Data in
Plant Maintenance and Customer Service Technical Objects
General Data Set View Profiles for Technical Objects
2. On the Change View “Definition of view profiles”: Overview Screen, select the line of H2
Screen group equipment data. Double-click Icons and Texts of views.
3. On the Change View “Icons and Texts of views “: Overview Screen, maintain the following
data:
Number Descriptn Tab Title
60 Additional data 1 Partner Data
100 Additional data 2 Guarantee
4. Choose Save.
Result
The view profiles of technical objects have been set.
Use
The purpose of this activity is to maintain the equipment category.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Plant Maintenance and Customer Service Master Data in
Plant Maintenance and Customer Service Technical Objects
Equipment Maintain Equipment Category
3. Choose Save.
Result
Equipment category is defined.
Use
The purpose of this activity is to assign IDs to the applications in the portal. This enables you to
then assign properties and values to these IDs in the IMG activities Maintain Application
Properties and Maintain Application Settings.
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 Maintain ID
2. On the Change View “Value Table for Application ID”: 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 Note
+(First Field) Application ID 2
+(Second Field) Description of the Application Vehicle Management
ID System
4. Choose save.
Result
IDs have been assigned to the applications in the portal.
Use
The purpose of this activity is to define properties for the application and assign identifiers to
them. A property can, for example, be a style sheet or a print form for spare part orders.
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 Maintain Application Properties
2. On the Change View “Value Table for Application Property”: Overview screen, choose New
Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
App Prop AppPropDes (Description of the Application Note
(Application Property)
Property)
1 DEFAULT BACKEND SYSTEM
2 THEMES
3 PORTALS
4 COUNTRY CODE
5 VMS END CUSTOMER PARTNER FUNCTION
6 SMARTFORM - ORDER
7 SMARTFORM - DELIVERY
8 SMARTFORM - INVOICE
9 SMARTFORM - PERFORMA INVOICE
10 SMARTFORM - WARRANTY CLAIM For Warranty
11 IMPORTER EMAIL ID
12 VMS-GET CHANGED VEHICLES FOR LAST X
DAYS
13 VMS VEHICLE CREATION CODE IN MTO
14 DISTRIBUTED SYSTEM
15 DESIGN For Warranty
16 GRACEPERIOD For Warranty
17 COOKIELIFE For Warranty
4. Choose save.
Result
The application properties have been defined.
Use
The purpose of this activity is to assign values (name of the corresponding system) to application
properties.
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 Maintain Application Settings
2. On the Change View “Application Settings for Dealer Portal”: Overview screen, choose New
Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
AppID App Prop AppPropVal (Application Property Note
(Applicati (Application Value)
on ID) Property)
2 1 <SYS>AUTO<XXX> For VMS
(According to your current system:
<system name >+ “AUTO” +< client
number>
2 13 CREA For VMS
2 35 DORCU For VMS
3 1 NONE For Warranty
3 10 /SAPDII/CLM_FORM For Warranty
3 15 DESIGN2002 For Warranty
3 16 0 For Warranty
3 17 60 For Warranty
3 18 For Warranty
3 22 /sapdii/di_wty_ui/overview For Warranty
3 23 /sapdii/di_wty_ui/claims For Warranty
3 24 /sapdii/di_wty_ui/recalls For Warranty
3 25 /sapdii/di_wty_ui/returnparts For Warranty
3 26 /sapdii/di_wty_ui/financials For Warranty
3 27 /sapdii/di_wty_ui/contact For Warranty
3 28 /sapdii/di_wty_ui/personalize For Warranty
3 29 /sapdii/di_wty_ui/logoff For Warranty
3 32 /SAPDII/RETPA_TAG For Warranty
3 33 /SAPDII/RETPA_LIST For Warranty
3 34 /SAPDII/FINC_LIST For Warranty
3 37 BP01 For Warranty
4. Choose save.
Result
The name of the corresponding system has been assigned to application properties.
Use
The purpose of this activity is to enter identifiers and descriptions for these interfaces to external
Systems, for the individual Internet applications.
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 Maintain IDs for Interfaces to
External Systems
2. On the Change View “Value Table for External Interface Id”: 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 Note
values
Ext Int ID External Interface ID 0
Ex Int Des External Interface Description OCI CATALOG
4. Choose save.
Result
The interface which connects the Internet application Vehicle Management System to the Internet
Pricing and Configuration (IPC) has been entered.
Use
The purpose of this activity is to assign an ID to a logical system that has been maintained as an
RFC destination.
Prerequisites
You must use transaction SM59 to maintain an RFC destination for the dealer portal.
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 Assign Logical System
2. On the Change View “Logical system to RFC dest mapping”: Overview screen, choose New
Entries.
3. On the New Entries: Overview of Added Entries screen, make the follow entries:
Field name Description User action and values Note
Dest ID Destination ID DEST_ID
Lang. Language Key EN
4. Choose save.
Result
The logic system has been assigned.
Use
The purpose of this activity is to activate Dealer Portal services.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SICF
IMG Menu Tools Administration Administration Network HTTP Service
hierarchy maintenance
2. On the Maintain Service screen, in Hierarchy Type field choose F4 and select SERVICE .
Result
Dealer Portal services are activated.