SAP Best Practices for
Industrial Machinery &
Components (IM&C)
V1.603
(China)
What’s New?
Short Overview of What’s New

Scope of Predefined Scenarios

Master Data Descriptions

Predefined SAP Smart Forms

New Tool for Installation: SAP Best Practices Solution Builder
SAP Best Practices Solution for Industrial
Machinery & Components China V1.603:
Content Overview:
The SAP Best Practices for Industrial Machinery & Component comprises various
predefined Scenarios that cover all key business areas for the Industrial Machinery &
Components:








Research & Development
Sales & Marketing
Supply Chain Planning
Manufacturing
Procurement
Logistics & Distribution
Aftermarket Sales & Service
Enterprise Management & Support
The Best Practices for Industrial Machinery & Components Solution is based on:



SAP Best Practices Baseline Package V1.603
SAP Best Practices for Discrete Manufacturing V1.603
SAP Best Practices for Industrial Machinery & Components V2.600
Overview of NEW Scenarios

661: Records Management

662: Collaboration with cFolders

663: MTO Quotation Processing with Variant Pricing

664: MTO Production with Variant Configuration and Assembly Processing

665: Configuration MTO - Sales Order Processing with order BOM and OCM

666: Engineering Change Management for Discrete Industry

667: Scheduling Agreement Processing with FDS and Invoice Processing

668: APQP – Efficient Project Management with Control Plan

669: Handling Unit Management for a Set of Products

274: Maintenance and Warranty Processing

275: Easy Depot Repair

276: Supply Replacement Material
Overview of DELETED/CHANGED Scenarios

E70: MTO – Quotation Processing with Variant Pricing

E71: MTO – Sales Order Processing with Variant Configuration

E72: ETO – Quotation Processing with Easy Cost Planning

E73: ETO – Project Manufacturing – Sales Order Processing

E74: MTS – Production with External Processing & Serial Numbers

E75: Service – On–Site Service

E76: Service – Repairs at Plant

E77: NPDI – Product Development & Collaboration

E78: NPDI – Prototype Development

E79: MTS – Production with Batch Mgmt, Warehouse Mgmt, and HUM
Overview of DELETED/CHANGED Scenarios

E80: Service – Return Processing

E82: Operational Procurement with Vendor Evaluation & QM

E83: ETO – Quot. Process. w. BOM PS Interf. & Machine History

E84: ETO – Project Manuf. – Sales Order Processing w. ProMan

E85: MTS – Production Versions and Kanban Processing

E89: Preventive Maintenance with Job Scheduling

E90: Major Repair with Customer Contract and Warranty

E91: MTO – Order Processing w. Sales Order BOM, Collect. Order and OCM

E92: Global Trade Services (GTS) – Customs Management

E93: Global Trade Services (GTS) – Risk Management

E94: Global Trade Services (GTS) – Compliance Management
SAP Best Practices Master Data Descriptions

SAP Best Practices delivers standard values which allow you to test the business
processes without having to create your own master data.

If you want to test the business processes with customized values for specific
material or organizational data, you need to create these in your SAP ERP system. To
help you create your own master data, SAP Best Practices provides you with detailed
step-by-step instructions that tell you exactly what you need to know to set up master
data for your specific purpose.

For an overview of the Master Data Descriptions delivered with the SAP Best
Practices see the next slides.
SAP Best Practices
Master Data Descriptions -1Descriptions for Generic Master Data Creation
BPD
Area
BPD
Area
Create Accounts and Account Groups
Financials
Maintain Capacity
Production
Create Assets
Financials
Create Work Center
Production
Segments and Profit Center Maintenance
Financials
Maintain Work Center Hierarchy
Production
Functional Areas Maintenance
Financials
Create Resources for Process Industry
Production
Create Cost Center and Cost Center Group
Controlling
Create Product Group
Production
Create Raw (ROH) Material
Material Creation
Maintain Cost Center Hierarchy
Controlling
Create Semifinished Good (HALB) Material
Material Creation
Create Cost Element and Cost Element Group
Controlling
Create Trading Good (HAWA) Material
Material Creation
Create Finished Good (FERT) Material (non configurable)
Material Creation
Create Finished Good (FERT) Material (configurable)
Material Creation
Create Configurable Material Variant
Material Creation
Create Engineering Change Number
Material Creation
Create Production Version
Material Creation
Maintain Material Plant Extension
Extensions
Maintain Material Storage Location Extension
Extensions
Create Serial/Equipment Number
Extensions
Maintain Material Sales Organization Extension
Extensions
Create New Bill of Material
Bill of Materials
Maintain Bill of Material - Configurable Material Link
Bill of Materials
Create Cost Collector
Controlling
Maintain Assessment Cycles
Controlling
Create Standard Cost for Individual Material
Controlling
Create Activity Type / Groups
Controlling
Create Internal Order
Internal Orders
Maintain Vendor Evaluation
Vendor
Create Vendor Master
Vendor
Create Purchasing Info Record
Purchasing
Create Source List
Purchasing
Create Purchasing Contract
Purchasing
Create Customer Master
Customer
Create Sales Price Condition
Customer
SAP Best Practices
Master Data Descriptions -2Descriptions for Generic Master Data Creation
BPD
Area
BPD
Area
Create Routing
Routing & Master Recipe
Maintain Catalogs - Create Code Groups and
Codes
QM
Create Reference Operation Set
Routing & Master Recipe
Routing & Master Recipe
Maintain Catalogs - Create Selected Sets and
Selected Set Codes
QM
Maintain Material Scheduling via Routing
Create Master Inspection Characteristic
QM
Create Master Recipe
Routing & Master Recipe
Maintain Material Specification
QM
Attach Material Variants Routing to Parent
Material Routing
Routing & Master Recipe
Create Batch Classification
Logistics General
Create Configuration Profile
Variant Configuration
Maintain Material Master Extensions
Extensions
Create Variant Classification
Variant Configuration
Create Employee
Human Capital
Management
Load BOM Dependencies
Variant Configuration
Create Sales Representative
Create Standard Work Breakdown
Structure (WBS)
Projects Systems
Human Capital
Management
Create Task List
Plant Maintenance
Create Standard Network
Projects Systems
Create Service Master
Plant Maintenance
Allocate Material to Standard Network
Projects Systems
Create Service Product
Customer Service
Create Output Conditions SD
Sales and Distribution
Create Warranty
Customer Service
Create Tax Conditions SD
Sales and Distribution
Create Service (DIEN) Material
Material Creation
Create Material determination info record
Sales and Distribution
Create Free Good determination info
record
Sales and Distribution
SAP Best Practices
Predefined SAP Smart Forms

SAP Smart Forms is an easy, robust print form tool. This tool allows you to create and modify
forms easily using a graphical design tool, and provides more robust functionality and color.

You can use the preconfigured Smart Forms delivered with the SAP Best Practices in the
respective scenarios. Depending on your requirements, and with some minor adaptations,
these preconfigured Smart Forms can be made ready to be used in your business.

The scenarios delivered with the SAP Best Practices use SAP Smart Forms whenever
possible. For some areas standard and preconfigured Smart Forms are not available; in
these cases SAPscript forms are used (standard SAPscript forms, preconfigured SAPscript
forms).

For each preconfigured SAP Smart Form a printout example (PDF format) is delivered in
English and Chinese language.

In addition, in the Where-Used list, you can see which business scenarios use which Smart
Forms. You also get additional technical information on, for example, the delivered forms
templates, print programs, and subroutines used.
New Tool for Installation
SAP Best Practices Solution Builder
The SAP Best Practices Solution Builder

is the successor tool of the SAP Best Practices Installation Assistant

is technically fully compatible to previous SAP Best Practices Deliveries (regarding technical
Implementation)

provides additional functionality for managing SAP Solutions and facilitating End-User
Procedures

focuses on “Solutions” (SAP Best Practices Offerings)

supports a clearer separation of end-user and development related tasks

comprises extended functionality for
development and deployment

supports graphical scoping
(details see next slide)
SAP Best Practices Solution Builder
Graphical Scoping
Graphical Scoping based on templates

Solution can easily be enhanced with further templates

Based on scoping, a new solution (customer solution) is defined
 The scenarios of a
solution are sized
dynamically and ordered
into a solution map-like
view
 The color of a scenario is
determined by its
assignment to an
application area
 The application areas are
defined in the application
area editor. Here, color,
short text and long text
and the sequence is
defined
Legend
<Function>
Symbol
Description
Usage
Comments
Band: Identifies a user role, such as Accounts
Payable Clerk or Sales Representative. This band
can also identify an organization unit or group,
rather than a specific role.
Role band
contains tasks
common to that
role.
Symbol
Diagram
Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario.
Hardcopy /
Document
External
to SAP
External Events: Contains events that start or end the
scenario, or influence the course of events in the
scenario.
Business
Activity /
Event
Flow line (solid): Line indicates the normal sequence
of steps and direction of flow in the scenario.
Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. Line can
also lead to documents involved in the process flow.
Connects two
tasks in a
scenario
process or a
non-step event
Business Activity / Event: Identifies an action that
either leads into or out of the scenario, or an outside
Process that happens during the scenario
Does not
correspond to a
task step in the
document
Unit Process: Identifies a task that is covered in a
step-by-step manner in the scenario
Corresponds to
a task step in
the document
SubProcess
Reference
Proces
s
Decisio
n
Usage Comments
To next / From last Diagram: Leads
to the next / previous page of the
Diagram
Flow chart continues on the next /
previous page
Hardcopy / Document: Identifies a
printed document, report, or form
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Financial Actuals: Indicates a
financial posting document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Budget Planning: Indicates a
budget planning document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Manual Process: Covers a task
that is manually done
Does not generally correspond to
a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.
Existing Version / Data: This block
covers data that feeds in from an
external process
Does not generally correspond to
a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines
System Pass / Fail Decision: This
block covers an automatic
decision made by the software
Does not generally correspond to
a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.
Financial
Actuals
Budget
Planning
Manual
Proces
s
Unit Process
Process
Reference
Description
Process Reference: If the scenario references another
scenario in total, put the scenario number and name
here.
Sub-Process Reference: If the scenario references
another scenario in part, put the scenario number,
name, and the step numbers from that scenario here
Process Decision: Identifies a decision / branching
point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.
Corresponds to
a task step in
the document
Corresponds to
a task step in
the document
Does not
usually
correspond to a
task step in the
document;
Reflects a
choice to be
made after step
execution
Existing
Version /
Data
System
Pass/F
ail
Decisio
n