SAP Configuration Document - V1.0
SAP Configuration Document - V1.0
SAP Implementation
Configuration Document
Customer Service
VERSION 1.0
GENERAL INFORMATION
DOCUMENT INFORMATION
REFERENCE DOCUMENTS
TABLE OF CONTENTS
General Description
Warranty Type is a sub-division of a warranty category that allows for a more detailed
description. You can freely define the warranty type
Purpose
Warranty types have been defined to differentiate between the Vendor and Customer
Warranty.
Configuration Details
General Description
Number range is a range of numbers that you can assign to business objects (or their
sub-objects) of the same type. Each number range has one or number range
intervals and a number assignment type. Number Ranges can be internal or external.
Purpose
Configuration Details
Version 1.0 5 of 100
SAP IMPLEMENTATION
General Description
In this step you can define warranty counters and specify one warranty counter as a
default counter. This counter will be copied automatically when you create a master
warranty.
Purpose
To track the warranty of the machine in number of days we have to specify the
number of days in the warranty master and that has to be attached to the machine.
To specify the warranty value, warranty counter has been created
Configuration Details
1.2 Partners
General Description
Partner Determination Procedure: A plan that specifies how, when, and from what
sources the system determines partners in a business transaction, what partner
functions are mandatory or suggested in this transaction, and what rules apply to
these partner functions. You can define partner determination procedures and assign
any number of partner functions to each one. You can define whether a particular role
in the notification or order should be changeable, and whether it is obligatory.
Purpose
Version 1.0 7 of 100
SAP IMPLEMENTATION
To define the partner functions which are being used in customer service and assign
those partner functions to one partner determination procedure. That procedure will
in turn assigned to equipment category, notification and order types so that during
customer service business transactions, the required partner role being determined.
Configuration Details
General Description
In this work step, you can define which of your partner functions should be copied
automatically into the corresponding movement data. You can make this assignment
unique for each partner profile and each partner function.
Purpose
To reduce the manual maintenance requirements for maintaining partner data in the
processing of maintenance and service tasks.
Configuration Details
General Description
User Status is the status set by the user to complement the system status for a given
status object. You can use only a user status belonging to a status profile (defined in
Customizing) and assigned to the relevant status object. User statuses enable you to
extend the control of business processes managed by the system status. You can set
and delete user statuses manually when carrying out business transactions
Purpose
To facilitate the quotation creation from the service order based on the user status
Create Quotation for Order, user status profile SERVICE has bee created and
assigned to the service order
Configuration Details
General Description
In this Customizing activity, you define authorization groups for your technical
objects. Authorization groups are used to categorize similar objects from the point of
view of authorizations. Authorization group field contains the name of a program
group for which the following operations can be permitted:
Execute programs
Schedule jobs for background processing
Maintain programs
Maintain variants
Purpose
Configuration Details
General Description
This Customizing activity allows you to create individual screens for technical objects.
The data fields for the technical objects are sorted by contents, so-called screen
groups. You can define one or more view profiles for each screen group, for example,
equipment. Each view profile enables you to assign pre-grouped and accompanying
data fields to individual screen templates. These screen templates can be labeled
individually using tab pages.
Purpose
Configuration Details
General Description
In this step you can define different object information keys. An object information key
can be assigned to the following object types:
Via the parameterization of the object information key, you determine the data of a
technical object (equipment, functional location, structure) that is shown in a special
information window. The object information also contains history data from the PM
Information System and data from the notifications and orders executed. You can use
the parameterization of the object information to define whether the notification and
order information should be displayed: for a technical object or for the higher-level
object, etc
Purpose
To view the previously created notifications / orders and its status while creating a
new notification / order in the specified pop window format, object information key
has been defined.
Configuration Details
1.5 Equipment
General Description
In this IMG activity you define the description for an equipment category. This allows
you to control which basic characteristics a corresponding equipment master record
should have. Using the control characteristics, you can decide how many and which
equipment categories you require.
Purpose
To differentiate and view the Customer Owned equipment master data from Plant
Maintenance Equipment master data, Customer Equipment Category S has been
created.
Configuration Details
General Description
In this step, you can define other views for each equipment category. The views
represent additional data screens for the equipment master record. You can activate
or deactivate the following views.
If you activate a view, the assigned data fields and screens can be automatically
maintained.
Purpose
To view the Sales and Distribution Data in Customer Equipment master record
Configuration Details
General Description
In this step you can define the number assignment category in the step equipment
categories. You must allocate a unique number for each equipment master record.
You have the following options:
internal number assignment (In this case, the SAP System assigns the
numbers.)
external number assignment (In this case, the user assigns the numbers)
You can define both an internal and an external number range for each equipment
category. The same number ranges can be shared by several equipment categories.
Purpose
In order to differentiate the customer equipment master record from other types of
equipment master record, unique internal number range has been assigned to
Customer Equipment Category.
Configuration Details
General Description
You define the equipment categories for which you want an ongoing usage history to
be kept in this step. Changes to certain master data fields will be logged in the usage
history. You define the fields concerned for each reference category.
Purpose
To record the changes in the equipment master data field, usage history update
check box has been activated for equipment category S
Configuration Details
General Description
Partner Determination Procedure is a plan that specifies how, when, and from what
sources the system determines partners in a business transaction, what partner
functions are mandatory or suggested in this transaction, and what rules apply to
these partner functions. You can define partner determination procedures and assign
any number of partner functions to each one. You can define whether a particular role
in the notification or order should be changeable, and whether it is obligatory.
Purpose
To define the partner functions which are allowed in equipment master and assign
those partner functions to one partner determination procedure. Then assign that
procedure to Equipment Category.
Configuration Details
General Description
Purpose
To track the customer equipment with unique number and also to track the sub
assemblies with serial number which are assigned to main equipment.
Configuration Details
General Description
In this step, you define a central default equipment category for the serial number
management. This equipment category is proposed by the system if the system
cannot find an equipment category in the serial number profile for a serialization
operation.
Purpose
As customer equipment is only having tracked with serial number, default equipment
category is set as Category S.
Configuration Details
General Description
In this activity, you can deactivate the lock, which is set in the standard system for the
internal assignment of serial numbers. Several users can thereby create serial
numbers for a material at the same time.
Purpose
Configuration Details
General Description
This step allows you to define maintenance planner groups. Planner groups or
maintenance planning groups must be defined separately for each maintenance
planning plant. Depending on the size and structure of your company, a maintenance
planning group may be an individual department (for central work preparation), a
group of skilled craftsmen or a workshop.
Purpose
To stream line the maintenance / service planning and also to monitor the activities
going on by planner group wise, planner group is being created
Configuration Details
General Description
In this key, you can store the person or the group of people responsible for
maintaining the master data of a particular work center. This area of responsibility
does not refer to possible planning activities but to the management of the work
center in the sense of parameter maintenance instead.
Purpose
Configuration Details
General Description
In the settlement profile, you define a range of control parameters for settlement. You
must define the settlement profile before you can enter a settlement rule for a sender.
If you want to settle the costs each time to just one cost center or just one G/L
account, you need a settlement profile. As you cannot maintain the settlement
parameters during settlement to a receiver, you must save the settlement profile
either in the order type or in the model order or reference order.
Purpose
The purpose of this activity is to define a range of control parameters for settlement in
the settlement profile. You must define the settlement profile before you can enter a
settlement rule for a sender.
Configuration Details
General Description
You assign the debit cost element groups to a settlement cost element.
You settle by cost element - that is, the debit cost element is the settlement
cost element.
Purpose
Configuration Details
General Description
Value categories are intervals for: Cost elements, financial items & Statistical key
figures. For performance reasons, it is advisable to group together cost elements into
value categories. This reduces the volume of data. If you still want to create value
categories according to the cost elements, then you can generate the value
categories automatically. Quantities are only updated in the order if you have
assigned a unit of measure to the value category.
Purpose
The purpose of this activity is to maintain value categories. Value categories are
intervals for cost elements. These are required to update the:
Plant Maintenance Information System
Customer Service Information System
Configuration Details
General Description
Purpose
The purpose of this activity is to define a cost element, a cost element interval or a
cost element group as a value category
Configuration Details
General Description
In this dynamic IMG activity you create dynamic item processor profiles for billing,
quotation creation and results determination. So that you can bill the items of a sales
document or a service order or create a quotation, you must assign a profile to the
item of the sales document or the service order. You can maintain default values for
the profile:
In the step Define item types you can specify a default for the profile of a
sales document item.
In the step Credit limit checks, sales document types for service orders you
can store a default for the service order profile.
Purpose
For billing the customer based on the resources used for carrying out the service /
repair activities, DIP profile ACECSGPR has been created and assigned to the
service orders
Configuration Details
General Description
The notification types that is available in the system. All notification types for
all notification categories and notification origins are listed.
The settings of a particular notification type. You can display all assignments
of notification parameters for one notification type.
Purpose
The display screen of notification with various features have been defined in order to
meet the client specific requirements
Configuration Details
General Description
In this section, you define the notification types and the basic functions connected to
the notification type. In the standard system, the notification types are structured
according to factual criteria (malfunction, activity report). The notification type is an
important criterion in the selection of notifications. You can also define a separate
number range for each notification type.
Purpose
To service the various types of customer requests and for easy tracking of those
services, different notification types have been created
Configuration Details
General Description
In this work step, you define the accompanying number range interval for each
notification type. You can define a number range interval for each notification type,
whereby you can choose between internal and external number assignment.
Purpose
In order to differentiate the various notification types records, unique internal number
range has been assigned to each notification type.
Configuration Details
General Description
You can work with different notification types and order types. In this step, you can
assign a single order type to a single notification type in each case.
Purpose
The purpose of this activity is to define which order type is generated from which
notification type
Configuration Details
General Description
In this step, you can set additional special notification parameters. For service
notifications, you can:
Define a sales order type for creating a sales order from the service
notification
Activate automatic contract determination
Define another order type for notifications with reference to service contracts
Purpose
In order create a sales order from the notification link this setting has to be done.
Configuration Details
General Description
In this step, you structure the content of the notifications based on the following
definition of catalog profiles. This means you can define the structural elements of
the notification that are to be used and the information these elements are to contain.
You can organize and maintain the catalogs that are used in the notifications and
when defects are recorded.
Purpose
The purpose of this activity is to define various catalog types being used, defining
code groups and codes.
Configuration Details
General Description
Purpose
The purpose of this activity is to define the catalog profile for notifications. In the first
step catalogs are to be defined.
Configuration Details
General Description
Partner Determination Procedure is a plan that specifies how, when, and from what
sources the system determines partners in a business transaction, what partner
functions are mandatory or suggested in this transaction, and what rules apply to
these partner functions. You can define partner determination procedures and assign
any number of partner functions to each one. You can define whether a particular role
in the notification or order should be changeable, and whether it is obligatory.
Purpose
To define the partner functions which are allowed in notification type and assign
those partner functions to one partner determination procedure. Then assign that
procedure to Equipment Category.
Configuration Details
General Description
In this step, you define the priorities for the notifications. You can define different
priority types and assign a priority type to each notification type. For each priority
type, you define:
Purpose
To automatically determine the required start date and finish date of the notification
based on the priority type assigned to the notification type
Configuration Details
General Description
In this step, you define the response time monitoring functions for notifications. For
this purpose, you must first define response profiles and service profiles. You must
then assign these profiles to the quality notification types.
In the response profile, you define a sequence of standard tasks (based on the
priority of the notification) that can be proposed in the notification and which must be
carried out within a predefined period of time. When the system processes a
notification, it always assigns the tasks that have been selected on the basis of a
response profile to the notification header.
The service profile defines the times during each work day when a notification is
processed. You can also specify several time periods for each weekday and you can
assign a separate response profile to each of these periods.
The system finds the basic dates for the notification header with the help of the
priority; the system automatically suggests tasks to be included in the notification
header using the response profile and specifies the processing deadlines. These two
scheduling functions work independently of one another.
The processing times defined in the service profile are only valid for the tasks defined
in these profiles that the system suggests for the notification header. The resulting
processing deadlines take precedence over the basic dates that come from the
notification priority.
Purpose
To automatically determine the task for the notification types while creating the
notification based on the priority type assigned to the notification
Configuration Details
General Description
In this step, you define the functions, with which you can generate tasks or activities
(known as supplementary actions) for a notification. These functions should be
defined using a key and a label. They are assigned to a notification type, and are
available at header level when processing notifications. When the function is called
up, the system copies the task or activity defined into the notification. For calling up
the function, you can define a label, and an icon together with explanatory quick
information.
For each function, you can specify an internally programmed function module that is
processed when the function is called up. A dialog with the user can also be
programmed here. If you link a business operation with the function, then the function
is only executed if the status of the notification belonging to the operation allows this.
If a task is involved, you have released or completed the alternatives for this status.
In addition, you can define a workflow task that is activated when the notification is
saved. You can also enter a function module which still changes the workflow
container when the notification is saved.
Purpose
To create a follow up actions from the notification screen itself, in the action box
some activities have been defined and that will be available as a link in the
notification initial screen. By clicking that link we can carry out that follow up function.
Configuration Details
General Description
In this step you can assign an object information key to each notification type.
Purpose
To view the previously created notifications / orders and its status while creating a
new notification / order in the specified pop window format, object information key
has been defined and assigned to notification types.
Configuration Details
General Description
In this step, you set up your order types for Plant Maintenance and Customer
Service. In addition to the business reasons for configuring several order types,
there are also technical controls which depend on the order type and may require the
creation of different order types.
Purpose
The purpose of this activity is to configure order types. In addition to the business
reasons for configuring several order types, there are also technical controls which
depend on the order type and may require the creation of different order types
Configuration Details
3.3.2 Credit Limit Checks, Sales Document Types for Service Orders
General Description
In this step, you define which sales document type is used in resource-related billing.
You can assign a sales document type to each order type. You can also define if and
how a credit limit check should be performed
Purpose
Configuration Details
General Description
In this Customizing activity, you can allow the individual order types refurbishment
processing.
This business process usually involves a special form of Plant Maintenance which is
treated differently from maintenance, repair and inspection orders in terms of
planning, time and costs.
Purpose
Configuration Details
General Description
In this step, you define the number ranges for the individual order types. From the
point of view of program control and selections, it is not necessary to define different
number ranges for the individual order types. If your company does not need to
define several number ranges, you can work with one number range for the
maintenance or service orders
Purpose
In order to differentiate the various order types records, unique internal number range
has been assigned to each order type.
Configuration Details
General Description
In this Customizing activity, you determine the order types allowed for the individual
planning plants. If you want to allow all order types for all planning plants, you must
enter all the order types for each plant.
Purpose
The purpose of this activity is to determine the allowed maintenance order types for
the individual maintenance plants.
Configuration Details
General Description
In this step, you define the profiles for external procurement of services and
materials. In the external processing profile, you can store default values to generate
purchase requisitions from maintenance- or service orders. In each profile, you can
store a default value for the following values:
Since both of these procurement processes generally require different data for
purchasing, for example, different purchasing groups or different cost element
accounts, you should also define different profiles for them.
Purpose
The purpose of this activity is to define the profiles for external procurement of
services and materials. In the external processing profile, you can store default
values to generate purchase requisitions from maintenance orders
Configuration Details
3.3.7 Default Values for Task List Data and Profile Assignments
General Description
In this IMG activity you define which default values should be copied to the order
data for order processing.
You can define the profile assignment individually for each plant and each
order type.
If the profile should be independent of the order type, only make one
assignment for the plant.
If you want the assignment to be cross-company for all plants, only define
one entry without plant and without order type.
You can perform the masking of the entries by entering the value **** in the
entry field
Purpose
The purpose of this activity is to define which default values are copied into the order
data during the order processing.In the previous steps, you have maintained a profile
for the procurement of material, external processing profiles and a general order
profile.
Configuration Details
General Description
In this step, you can define for each order type the time by which the settlement rule
must be maintained during order processing. You can also define a default value for
the distribution rule for each order type, according to which the settlement rule should
be calculated, if an order of this order type has a superior order.
Purpose
For the Service Order type settlement profile is mandatory for technical completion of
the order. In this step, it has been configured when the settlement rule is to be
created for the service order.
Configuration Details
General Description
External processing
Completion confirmation
Printing
Scheduling
Costing
In this step, you maintain the allowed control keys for the individual operations of the
maintenance- and service orders. A subsequent change to the parameterization of
the control keys is always critical when these control keys have already been used in
orders or task lists
Purpose
Control key is used to determine which business functions you want to carry out and
how you want to handle the operation
Configuration Details
3.3.10 Maintain Default Values for Control Keys for Order Types
General Description
In this step, you maintain the default control keys for each service order types from
the already maintained control keys.
Purpose
Configuration Details
General Description
In this step, you define the allowed maintenance activity types. A key for the type of
maintenance activity provided. Activities are divided into repairs, shutdowns, regular
activities, inspections and so on. In cost evaluations, for example, total costs or
number of orders for each technical object, you can classify data according to
maintenance activity type.
Purpose
To determine for what type of problems the service order is being executed in the
header level. This is will be used for further analysis of service order as well.
Configuration Details
General Description
In this step, you can determine which maintenance activity types allowed with which
order types. Allocate the corresponding maintenance activities to the PM and CS
order types.
Purpose
To determine the maintenance activity types allowed for each service or maintenance
orders.
Configuration Details
3.3.13 Default Values for Maintenance Activity Type for Each Order Type
General Description
In this step, you can assign a maintenance activity to an order type. This activity is
proposed during order processing.
Purpose
Configuration Details
General Description
Costing variants contain control parameters for costing. The costing variant
determines how costing is carried out. Among other things, it controls how the
quantity structure and the value structure are created.
Purpose
The costing variant forms the link between the application and Customizing, since all
cost estimates are created and saved with reference to a costing variant.
Configuration Details
General Description
Here you create a valuation variant that contains the parameters for valuating a cost
estimate. You also define which costing sheet is proposed in the order master data
Material components: Here you define the order in which the system looks
for prices in the accounting view and the costing details screen of the material
master record to valuate materials.
Version 1.0 75 of 100
SAP IMPLEMENTATION
Internal activities: Here you define the order in which the system looks for
prices in activity type planning in cost center accounting to valuate internal
activities. You also define which plan version is used in cost center
accounting.
External processing in the operation: Here you define the order in which
the system looks for prices in the purchasing info record or in an operation in
the work order or in the routing to valuate external activities.
Subcontracting: Here you define the order in which the system looks for
prices in the purchasing info record. In purchasing, quota arrangements are
used to create a mixed price for materials that are supplied by external
vendors with materials provided by the customer. You can specify whether the
quota of the suppliers that are entered in the source list for the material to be
processed should be determined with the planned quota arrangement or the
actual quota arrangement.
Costing sheet: The costing sheet contains the parameters that control the
calculation of overhead. To check an existing costing sheet or to create a new
costing sheet, process Define overhead. To group overhead according to
material groups, process Define overhead groups and assign the overhead
groups to the overhead key in the costing sheet.
Purpose
This is used to determine how the planned and actual cost of the service and
maintenance order is being calculated
Configuration Details
General Description
In this step, you can set the costing parameters for maintenance and service orders.
You can also assign a results analysis key to each order type
Purpose
The purpose of this activity is to set the costing parameters for maintenance orders.
Configuration Details
3.3.17 Define Change Docs, Collective Purc. Req. Indicator, Operation No.
Interval
General Description
Whether changes to the order header are recorded using documents and are
displayed in the form of an action log
The increment at which numbers for the individual operations should be
assigned
Whether just one purchase requisition (collective purchase requisition) should
be generated for external material and operations for each order
Whether a workflow should be generated for changes to dates and quantities
for components not held in stock, operations processed externally and
external elements, if a purchase requisition is already available
Whether certain order types are maintained
Purpose
The purpose of this activity is to specify in which plant and for which order type
specific functions are active. Also to create the Purchase requisition from the service
order automatically and collectively for all the non-stock item in the service order.
Configuration Details
General Description
In this Customizing activity you can define which types of goods movement are
documented for each individual PM order. This function can be called from order
processing in list form. You can determine whether the list contains
Purpose
To have the documents for each movements with respect to service order for future
analysis and records
Configuration Details
General Description
In this menu option, you define the check scope. Checking group and checking rule
together specify the scope of the check.
Purpose
To determine
which elements relevant to MRP (inward goods movements/outward goods
movements) are taken into account (for example, purchase requisition,
purchase order, planned order)
which stock categories are taken into account
whether replenishment lead time is checked
Configuration Details
General Description
In this activity, you define the check control. The checking rule together with the
checking group specifies the scope of the check. You can make the checking rule as
well as the actual check itself dependent on the following parameters:
Plant
order type
operation
The operation can have the following characteristics: order created, release(d) order,
scope of the check
Purpose
In maintenance and service orders components are being reserved to carry out the
repair job. In order to have the material availability check for the service and
maintenance orders this activity has been carried out
Configuration Details
General Description
Version 1.0 83 of 100
SAP IMPLEMENTATION
In this work step, you can determine the proposal values for the item categories of
the order components. The proposal values can be determined dependent on the
material type and the maintenance plant.
Purpose
To propose the item category once it has been assigned in the service and
maintenance order component tab
Configuration Details
3.3.22 Define Account Assignment Cat. and Document Type for Purchase
Requisitions
General Description
In this Customizing activity you define the purchasing account assignment category
and purchasing document type for purchase requisitions for maintenance and service
orders. For the document type, you can choose whether you always want to generate
purchase requisitions for standard purchase orders, contracts or other document
types of the purchasing system.
Purchase requisitions for PM/SM orders must always be assigned to PM/SM orders.
This means that you must change the standard setting for the account assignment
category only if you defined a new account assignment category for order-account
assignment in Customizing for the purchasing system.
Purpose
To create the Purchase requisition from the service order automatically with correct
account assignment and purchase order type
Configuration Details
General Description
You define priority types in this Customizing activity. You can define your own
priorities for every priority type.
Purpose
To automatically determine the required start date and finish date of the order based
on the priority type assigned to the order.
Configuration Details
General Description
In this step, you can define for which plants the current date should be proposed as a
basic date for the order.
Purpose
To propose the current date as the start date of the order / notification automatically.
Configuration Details
General Description
Status set by the user to complement the system status for a given status object. You
can use only a user status belonging to a status profile (defined in Customizing) and
assigned to the relevant status object. User statuses enable you to extend the control
of business processes managed by the system status. You can set and delete user
statuses manually when carrying out business transactions.
Version 1.0 86 of 100
SAP IMPLEMENTATION
define your own statuses (user statuses) and document their function in a
respective long text
determine the status numbers for user statuses which predefine the possible
sequence for processing user statuses
define an initial status which is activated automatically when creating the
object
determine which user status is automatically activated when carrying out a
business transaction
define which operations are allowed or prohibited if a certain status is active
Purpose
To facilitate the quotation creation from the service order based on the user status
Create Quotation for Order, user status profile SERVICE has bee created and
assigned to the service order
Configuration Details
General Description
Purpose
To define the partner functions which are allowed in service and maintenance order
and assign those partner functions to one partner determination procedure. Then
assign that procedure to service and maintenance order type
Configuration Details
General Description
In this Customizing activity you can set the following scheduling parameters for every
maintenance- and service order and for every maintenance plant:
Automatic scheduling
Display scheduling log automatically after scheduling
Maximum number of days for start in the past
Automatic adjustment of the start/finish dates
Shift order indicator
Scheduling to incorporate breaks (breaks at the work center are taken into
account when scheduling is created)
Purpose
The purpose of this activity is to define a range of control parameters that will
facilitate the automatic scheduling of the service and maintenance order once it is
created and released
Configuration Details
General Description
In this step you can assign an object information key to each order type.
Purpose
To view the previously created notifications / orders and its status while creating a
new notification / order in the specified pop window format, object information key
has been defined
Configuration Details
General Description
In this work step, you maintain the control parameters for completion confirmations
for maintenance- and service orders. You can set control parameters for each order
type. Using the completion parameters you define:
Purpose
The purpose of this activity is to define a range of control parameters that will
facilitate the completion confirmation of the maintenance and service orders as per
the requirement of the clients
Configuration Details
4. Customer Service
General Description
Number ranges for entries in the Solution Database are defined under number range
object: ISDB. Only internal number assignments are possible. Group 1 is the number
range for symptom records. Group 2 is the number range for solution records. The
number range assignment for symptoms and solutions are independent from their
types and categories.
Purpose
In order to differentiate the symptoms and solutions, unique internal number range
has been assigned to symptoms and Solutions.
Configuration Details
General Description
Symptom type is the highest level of grouping and categorizing for symptom records
in the Solution Database. Each symptom type has defaults for code group, catalog
type, profile, and priority group for symptom records. Default values can be
overwritten in each symptom record.
Purpose
Configuration Details
General Description
Solution types are the highest level of grouping and categorizing for solution records
in the Solution Database. Each solution type has defaults for code group, catalog
type, and profile for tasks. The default value can be overwritten in each solution
record.
Purpose
Configuration Details
General Description
In this menu option, you define and maintain the requirement classes with which you
control all functions relevant to requirements in logistics.
The requirement class controls the MRP and the requirements consumption strategy
as well as the relevancy for planning. Specifications on the settlement of the
requirement class, for example, the settlement profile and the results analysis key,
are preferably used by Materials Management and do not have to be used when
configuring the availability check and transfer of requirements.
Purpose
In order facilitate the automatic rework order (with required order type) creation from
the repair sales order this setting has been done.
Configuration Details
General Description
In this IMG step, you change or define requirements types which identify the different
requirements, such as sales order requirements, delivery requirements or individual
customer requirements. The requirements types can be changed, for example, in
order to represent customer-specific terms.
Together with the item category and the MRP type of the material, an allocation to the
individual transactions in sales and distribution is carried out by means of the
requirements type. Every requirements type is allocated to a requirements class with
its corresponding control features.
Purpose
In order facilitate the automatic rework order (with required order type) creation from
the repair sales order this setting has been done.
Configuration Details
General Description
First, an attempt is made to find a requirements type using the strategy group
in the material master.
If the strategy group has not been maintained, the system will determine it
using the MRP group.
If the MRP group has not been defined, the system uses the material type
instead of the MRP group when accessing the corresponding control tables.
If no requirements type is found here, the system assumes a special rule and
attempts to find a requirements type with the aid of the item category and the
MRP type.
If this is not possible, a last attempt is made to find a requirements type with
the item category only.
If the last attempt fails, the system declares the transaction as not relevant for
the availability check or transfer of requirements.
Purpose
In order facilitate the automatic rework order (with required order type) creation from
the repair sales order this setting has been done.
Configuration Details
5.2 Sales
General Description
In this IMG activity, you define the repairs procedures that you need so that actions
can be automatically created for the repair order. The repairs procedure contains the
rules according to which the system generates actions for the repair request item in
the repairs order.
Stages : Represent the individual steps or stages within the repair process
Actions : Represent the activities that are necessary to meet the customer's
repair requirements
In the repairs procedure, you assign actions to each stage in the repairs process that
may be carried out at that particular stage.
You then combine the action and stage to determine the type of action it is. The
following types are available:
An action that the system proposes automatically once a certain stage in the
repairs process has started. This is given the default indicator
An action that the system generates according to the repair indicator. The
repair indicator reports inspection lots, notifications or service orders back to
the repair order. This is given the confirmation indicator.
An action that requires permission and has to be created manually. This is
given a manual indicator
Purpose
In order to generate repair items automatically from the repair sales order based on
the transaction results, this settings has been done.
Configuration Details
General Description
In this menu option, you define item categories for sales documents. The item
categories that are contained in the standard SAP R/3 System together with the
sales document types represent the usual business transactions. You have the
following options for defining your own item categories:
Purpose
In order to generate repair items automatically from the repair sales order based on
the transaction results, this settings has been done.
Configuration Details