Sap MM-configuration-step-by-step-guide

MM – Configuration Documentation

Table of Contents
1PURPOSE OF THE DOCUMENT................................................................................................................5
ENTERPRISE STRUCTURE - DEFINITION...............................................................................................6
1.1 DEFINE VALUATION LEVEL ...........................................................................................................................6
1.2 DEFINE PLANT...............................................................................................................................................6
1.3 MAINTAIN STORAGE LOCATION....................................................................................................................7
1.4 MAINTAIN PURCHASING ORGANIZATION.......................................................................................................8
ENTERPRISE STRUCTURE ASSIGNMENTS.............................................................................................9
1.5 ASSIGN PLANT TO COMPANY CODE..............................................................................................................9
1.6 ASSIGN PURCHASING ORGANIZATION TO COMPANY CODE............................................................................9
1.7 ASSIGN PURCHASING ORGANIZATION TO PLANT.........................................................................................10
1.8 ASSIGN STANDARD PURCHASING ORGANIZATION TO PLANT.......................................................................11
GENERAL LOGISTICS ...............................................................................................................................12
1.9 ASSIGN FIELDS TO FIELDS SELECTION GROUPS..........................................................................................12
1.10 MAINTAIN FIELD SELECTION FOR DATA SCREENS...................................................................................12
1.11 MAINTAIN COMPANY CODES FOR MATERIALS MANAGEMENT................................................................13
1.12 DEFINE ATTRIBUTES OF MATERIAL TYPES...............................................................................................14
1.13 DEFINE NUMBER RANGES FOR EACH MATERIAL TYPES............................................................................16
1.14 DEFINE ATTRIBUTES OF SYSTEM MESSAGES.............................................................................................17
1.15 DEFINE MATERIAL GROUPS.......................................................................................................................17
1.16 DEFINE EXTERNAL MATERIAL GROUPS....................................................................................................18
1.17 INITIALIZE PERIOD.....................................................................................................................................18
MATERIALS MANAGEMENT – CONSUMPTION BASED PLANNING.............................................20
1.18 ACTIVATE MRP FOR MRP AREAS............................................................................................................20
1.19 DEFINE MRP AREAS.................................................................................................................................20
MATERIALS MANAGEMENT – PURCHASING......................................................................................21
1.20 DEFINE ATTRIBUTES OF SYSTEM MESSAGES............................................................................................21
1.21 DEFINE PURCHASING VALUE KEYS...........................................................................................................21
1.22 ENTRY AIDS FOR ITEMS WITHOUT A MATERIAL MASTER........................................................................22
1.23 CREATE PURCHASING GROUPS..................................................................................................................23
1.24 DEFINE DOCUMENT TYPES (RFQ/QUOTATION)........................................................................................23
1.25 DEFINE TEXT TYPES FOR HEADER TEXTS (RFQ/QUOTATIONS)...............................................................25
1.26 DEFINE COPYING RULES FOR HEADER TEXTS (RFQ/QUOTATIONS)..........................................................25
1.27 DEFINE DOCUMENT TYPES (PURCHASE REQUISITIONS).............................................................................26
1.28 RELEASE PROCEDURE WITH CLASSIFICATION (PURCHASE REQUISITIONS)...............................................27
1.29 DEFINE NUMBER RANGES (PURCHASE ORDERS)......................................................................................32
1.30 DEFINE DOCUMENT TYPES (PURCHASE ORDERS).....................................................................................33
1.31 SET TOLERANCE LIMITS FOR PRICE VARIANCE........................................................................................35
1.32 RELEASE PROCEDURE FOR PURCHASE ORDERS........................................................................................36
1.33 DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL......................................................................................39
1.34 DEFINE TEXT TYPES FOR HEADER TEXTS (PURCHASE ORDERS)..............................................................40
1.35 DEFINE COPYING RULES FOR HEADER TEXTS (PURCHASE ORDER)..........................................................41
1.36 DEFINE TEXT TYPES FOR ITEM TEXTS (PURCHASE ORDERS)...................................................................41
1.37 DEFINE COPYING RULES FOR ITEM TEXTS (PURCHASE ORDER)................................................................42
1.38 DEFINE DOCUMENT TYPES (CONTRACTS).................................................................................................43
1.39 DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL (CONTRACTS)...............................................................45
1.40 DEFINE TEXT TYPES FOR HEADER TEXTS (CONTRACTS)..........................................................................46

1.41 DEFINE COPYING RULES FOR HEADER TEXTS (CONTRACTS)....................................................................47
1.42 DEFINE TEXT TYPES FOR ITEM TEXTS (CONTRACTS)...............................................................................47
1.43 DEFINE COPYING RULES FOR ITEM TEXTS (CONTRACT)...........................................................................47
1.44 DEFINE EXTERNAL CONFIRMATION CATEGORIES.....................................................................................49
1.45 DEFINE INTERNAL CONFIRMATION CATEGORIES......................................................................................49
1.46 SET UP CONFIRMATION CONTROL............................................................................................................50
1.47 DEFINE ACCESS SEQUENCE.......................................................................................................................51
1.48 DEFINE CONDITION TYPES........................................................................................................................52
1.49 DEFINE CALCULATION SCHEMA................................................................................................................54
1.50 DEFINE SCHEMA GROUP............................................................................................................................56
1.51 DEFINE SCHEMA DETERMINATION............................................................................................................57
1.52 DEFINE TRANSACTION EVENT KEYS..........................................................................................................59
1.53 MAINTAIN CONDITION TABLE...................................................................................................................60
1.54 DEFINE GRID FOR QUANTITY VARIANCES................................................................................................61
1.55 DEFINE GRID FOR DELIVERY DATE VARIANCE.........................................................................................61
1.56 DEFINE WEIGHING KEYS............................................................................................................................61
1.57 DEFINE CRITERION (VENDOR EVALUATION).............................................................................................62
1.58 DEFINE SCOPE OF LIST (VENDOR EVALUATION)......................................................................................63
1.59 MAINTAIN PURCHASING ORGANIZATION DATA........................................................................................63
1.60 DEFINE PERMISSIBLE PARTNER ROLES PER ACCOUNT GROUP.................................................................65
1.61 DEFINE PARTNER SCHEMAS (VENDOR MASTER)......................................................................................66
1.62 ASSIGN PARTNER SCHEMAS TO ACCOUNT GROUPS..................................................................................67
1.63 DEFINE PARTNER SCHEMAS (PURCHASING DOCUMENTS)........................................................................67
1.64 ASSIGN PARTNER SCHEMAS TO DOCUMENT TYPES..................................................................................68
MATERIALS MANAGEMENT – EXTERNAL SERVICES MANAGEMENT......................................70
1.65 DEFINE SERVICE CATEGORY.....................................................................................................................70
1.66 DEFINE NUMBER RANGES.........................................................................................................................70
1.67 DEFINE NUMBER RANGE FOR SERVICE ENTRY SHEETS............................................................................71
1.68 DEFINE ATTRIBUTES OF SYSTEM MESSAGES.............................................................................................71
MATERIALS MANAGEMENT – INVENTORY MGMT. & PHYSICAL INVENTORY.....................73
1.69 PLANT PARAMETERS..................................................................................................................................73
1.70 DEFINE NUMBER ASSIGNMENT FOR ACCOUNTING DOCUMENTS..............................................................73
1.71 DEFINE NUMBER ASSIGNMENT FOR MATERIAL AND PHYSICAL INVENTORY DOCUMENTS......................76
1.72 DEFINE NUMBER ASSIGNMENT FOR RESERVATIONS.................................................................................77
1.73 FIELD SELECTION FOR GOODS MOVEMENT/INITIAL HEADER SCREENS...................................................77
1.74 FIELD SELECTION FOR MIGO....................................................................................................................78
1.75 FIELD SELECTION PER MOVEMENT TYPE..................................................................................................79
1.76 SETTINGS FOR TRANSACTIONS AND REFERENCE DOCUMENTS.................................................................80
1.77 CREATE STORAGE LOCATION AUTOMATICALLY.......................................................................................81
1.78 SET MANUAL ACCOUNT ASSIGNMENT......................................................................................................82
1.79 DEFINE SCREEN LAYOUT...........................................................................................................................82
1.80 MAINTAIN COPY RULES FOR REFERENCE DOCUMENTS............................................................................83
1.81 SET UP DYNAMIC AVAILABILITY CHECK..................................................................................................84
1.82 GENERATE PHYSICAL INVENTORY DOCUMENTS FOR GOODS MOVEMENTS.............................................87
1.83 CHECK TOLERANCE LIMITS.......................................................................................................................87
1.84 CREATE STORAGE LOCATIONS AUTOMATICALLY.....................................................................................88
1.85 SET MANUAL ACCOUNT ASSIGNMENT......................................................................................................89
1.86 DEFINE SCREEN LAYOUT...........................................................................................................................90
1.88 SET DYNAMIC AVAILABILITY CHECK.......................................................................................................92
1.89 SET “DELIVERY COMPLETED” INDICATOR................................................................................................93
1.90 SET EXPIRATION DATE CHECK..................................................................................................................94

1.91 CREATE STORAGE LOCATION AUTOMATICALLY FOR AUTOMATIC MOVEMENTS.......................................94
1.92 SET MANUAL ACCOUNT ASSIGNMENT FOR AUTOMATIC MOVEMENTS.......................................................96
1.93 DEFINE SCREEN LAYOUT FOR AUTOMATIC MOVEMENTS..........................................................................97
1.94 GENERATE PHYSICAL INVENTORY DOCUMENTS FOR GOODS MOVEMENTS.............................................97
1.95 DEFINE DEFAULT VALUES FOR RESERVATIONS........................................................................................98
1.97 SET DYNAMIC AVAILABILITY CHECK FOR RESERVATIONS......................................................................99
1.98 DEFAULT VALUES FOR PHYSICAL INVENTORY.......................................................................................102
1.99 RECORD REASONS FOR GOODS MOVEMENTS..........................................................................................103
1.100 COPY, CHANGE MOVEMENT TYPES.......................................................................................................103
MATERIALS MANAGEMENT – VALUATION AND ACCOUNT ASSIGNMENT...........................105
1.101 SPLIT VALUATION..................................................................................................................................105
1.102 CONFIGURE SPLIT VALUATION..............................................................................................................105

1 Purpose of the Document

This document captures in detail the steps required to configure the SAP system to meet the
business requirements as envisaged in the ITZ Process Definition Documents of Business Blueprint
phase. The configuration steps have mappings to the corresponding menu path where the
configuration has been done in the IMG (Implementation Guide). The descriptive procedure along
with rationale of all configurations is also provided.

The documentation provides visibility to all project teams members on the proposed system
settings and changes. This is very important due to the highly integrated nature of SAP. All future
changes or updates to the system should be done based on this document and the documentation
updated accordingly.

This customisation manual outlines the way, how the Materials Management Module has been
configured for ITZ as per the requirement of their business scenarios and should be seen in
conjunction with the KDS document.

This document explains the settings done i.e. Configurations done for the present implementation
only and not all the nodes available.

Other Nodes are kept as standard (as delivered by SAP)

Enterprise Structure - Definition

1.1 Define Valuation Level

Menu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure
→ Definition → Logistics general → Define Valuation Level
Transaction Code OX14
Configuration Here we specify the level at which material stocks are valuated. We
Description have used the Plant level since the application component Production
Planning (PP) and Costing are being used.

• Depending on the valuation level chosen, accounting data (in
particular the valuation price) is maintained for each plant or for
each company code in the material master record.
• If material stocks are valuated at company code level, all plant
stocks of a material are managed in a joint stock account for each
company code.
• If material stocks are valuated at plant level, the material stocks for
each plant can be managed in different accounts. We can define a
separate account determination for each plant.

1.2 Define Plant
→ Definition → Logistics general → Define, copy, delete, check plant
Transaction Code SPRO
Configuration As a part of the Logistics Organizational Structure, Plants are defined in
Description SAP. The ‘Plant’ is an operating area or a branch or a location within a
company. Each 'Plant' is assigned to a single 'company code'. A
'company code' can have several 'Plants'. In case of ITZ Pvt. Ltd., the
various 'Plants' are assigned to a each 'company code'.

Configuration of One Plant is depicted here, (for list of all please refer to
MM KDS Document)

1.3 Maintain Storage Location
→ Definition → Materials Management → Maintain Storage Location
Transaction Code OX09
Configuration A storage location is the place where stock is physically kept within a plant.
Description There may be one or more storage locations within a plant.

A storage location has the following attributes:

• A storage location has a description and at least one address.
• It is possible to store material data specific to a storage location.
• Stocks are managed only on a quantity basis and not on a value
basis at storage location level.
• Physical inventories are carried out at storage location level.

Configuration of Storage Locations under One Plant is depicted here,
(for list of all please refer to MM KDS Document)

1.4 Maintain purchasing organization

→ Definition → Materials Management  Maintain Purchasing
Organization
Configuration At this node we configure the Purchasing Organization .The purchasing
Description organization is the highest level of aggregation (after the organizational
unit "client") for purchasing statistics.
In case of ITZ One single Purchase Organization is created as under :

Enterprise Structure Assignments

1.5 Assign Plant to Company Code
→ Assignment → Logistics general → Assign Plant to Company Code
Configuration A Plant needs to be assigned to one of the Company Codes, the relation
Description is always one to one i.e. One Plant can be assigned to only one
company code

All the plants can’t be shown here(for complete list refer MM KDS
document)

1.6 Assign purchasing organization to company code
→ Assignment → Logistics general → Assign purchasing
organization to company code
Configuration In this node we assign the Purchasing Organization to the company
Description code under which it works.
In case of ITZ the Purchasing Organization is Central, so it is not
assigned to any Company Code

1.7 Assign purchasing organization to Plant
→ Assignment → Logistics general → Assign purchasing
organization to Plant
Configuration In this step we assign purchasing organizations to the plants for which
Description they are responsible.
In case of ITZ since it operates with Centralized Purchasing Org. we
have assigned the Purchasing Org. to all the plants defined as of now

1.8 Assign standard purchasing organization to plant
→ Assignment → Logistics general → Assign standard purchasing
organization to plant
Configuration If several purchasing organisations procure for a certain plant, we can
Description define one of them as the standard purchasing organization for the
transactions "pipeline procurement", "consigmnent" and "stock
transfers".

In source determination for stock transfers and consignent, the system
automatically utilizes this standard purchasing organization. In the case
of goods issues of pipeline materials, the purchasing info records of the
standard purchasing organization are read.

In ITZ, we have not defined this Setting as we are using single
Purchasing Organisation

General Logistics

1.9 Assign Fields to Fields Selection Groups
Menu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General
 Material Master  Field Selection Assign Fields to Fields
Selection Groups
Transaction Code OMSR
Configuration Assignment of Material Master Fields is required to define whether a
Description field is hidden or displayed, or whether an entry is mandatory or optional
in material master maintenance, it is always advisable to work with
Standard SAP settings, but for few business requirement some
assignments are changed to new field selection groups defined as per
reserved name space. in case of ITZ, some of the list of changed entries
is as given below:

Field Name Description Changed Field
Grp
MVKE-MVGR1 Material group 1 211

1.10 Maintain Field Selection for Data Screens
Menu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General 
Material Master  Field Selection Maintain Field Selection for Data
Screens
Transaction Code OMS9
Configuration In this step we define the nature of a Field belonging to a particular Field
Description Selection Group wrt the Screen Reference of a Material Type. Steps
involved are :
• Selecting the field selection group.
• Select the field selection option (hide, display, required entry, or
Optional entry) for each field reference as required.

1.11 Maintain Company Codes for Materials Management
 Material Master  Basic Settings Maintain Company Codes for
Materials Management
Transaction Code OMSY
Configuration This activity is done for making a Company Code relevant for materials
Description Management and to define the starting posting period This is a
prerequisite for creating a Material Master

1.12 Define Attributes of Material Types
Material Master  Basic Settings Material Types Define Attributes of
Material Types
Transaction OMS2
Code
Configuratio Material type is analogous to the family of a material master; all the important
n attributes of a material are governed by settings in the material type. To be precise
Description it governs :

1. Number range pattern and nature (external/internal)
2. Hide/optional fields in the material master

3. Valuation Control at valuation area level (ultimately used to derive G/L)

4. Control on Production/Purchase

1.13 Define Number Ranges for each material types
 Material Master  Basic Settings Material Types Define
Number Ranges for each Material Types
Transaction Code MMNR
Configuration In this step, we have defined the type of number assignment and the
Description number range intervals for material master records. When creating a
material master record, system must assign it a unique number. There are
two ways of doing this:
• internal number assignment

In this case, a number within the number range interval allowed is
assigned by the SAP system.
• external number assignment

Here, the user assigns a number within the number range interval
allowed. We can define the intervals for external number
assignment numerically and alphanumerically.

We have defined the number range intervals for so-called groups. We
assign one or more material types to each group.

• If we assign just one material type to a group, we can define both an
internal and an external number range interval for the material type.

• If we group together more than one material type, we can define an
internal and an external number range interval here too. This allows
several material types to have the same number range intervals.

1.14 Define Attributes of system messages
 Material Master  Basic Settings Define Attributes of system
messages
Transaction Code OMT4
Configuration When processing material master records, the system issues a number of system
Description messages containing important user information. In this activity, we define how the
SAP system handles these messages. We have the following options:

• The message can be suppressed.
• The message can be displayed as a warning.
• The message can be displayed as an error message. (can’t be
surpassed)

For ITZ requirement Message Numbers MM189 & 312 are changed as
Error message

We are using Standard SAP Messages.

1.15 Define Material Groups
 Material Master  Settings for Key Fields Define Material Groups
Transaction Code OMSF
Configuration Here we define the Groups for Materials & Services, This Grouping shall
Description be defined keeping in mind the reporting requirement of the company for
analysing Purchases, Consumptions, Stocks etc,

Setting is just a table entry, few records are shown in the screen shot,
for complete list refer to the MM KDS document or the actual system
node

1.16 Define External Material Groups
 Material Master  Settings for Key Fields Define External
Material Groups
Configuration Here we define the Groups for giving an extra key for filtering, sorting
Description the list of materials from a criterion other than Material grouping
In case of ITZ we have not used External Material Groups

1.17 Initialize Period
Material Master  Tools Initialize Period
Transaction MMPI
Code
Configuratio This Transaction can be used to initialize the period in materials management ,
n Description i.e. it opens the already closed period (thru Txn : MMPV), but opening a period
has serious implications on data consistency in SAP so as recommended by
SAP Follow the instructions in Note 487381 before initialization

Materials Management – Consumption based Planning

1.18 Activate MRP for MRP Areas
Menu path Implementation Guide for R/3 Customizing (IMG) → Materials
Management  Consumption-based Planning  Master Data  MRP
Areas Activate MRP for MRP Areas
Configuration This setting is required if we want to have planning at a level other than plants i.e.
Description either of Storage location / at Subcontractor level.

An MRP area represents an organizational unit for which we can perform material
requirements planning separately.
An MRP area can include one or several storage locations of a plant or a
subcontractor. We can define MRP areas in a plant.
For ITZ Ltd., we have not used MRP Areas.

1.19 Define MRP Areas
Management  Consumption-based Planning  Master Data  MRP
Areas Define MRP Areas
Transaction Code SCAL
Configuration Here we define the MRP areas for a plant for which we would like to carry out
Description material requirements planning separately.
When creating an MRP area, we enter the number, which must have at least 5
digits to avoid any overlapping with the plant MRP area, the description and the
MRP area type

In case of ITZ we have not defined MRP area

Important : If MRP area is activated Conversion of Planning file entries
needs to be run in every new System Client through Report RMDBVM00
in Txn : SE38

The conversion report causes the system to create a new planning file.
In addition, the system creates MRP area for the existing plants. These
MRP areas do not, however, affect the way material requirements
planning is carried out. The number for plant MRP areas is identical to
the plant number and therefore consists of four digits.

The conversion of the current planning file (table MDVM) to the new
planning file (table DBVM) is a prerequisite for carrying out material
requirements planning with MRP areas.

Materials Management – Purchasing

1.20 Define Attributes of System Messages
Management  Purchasing  Environment Data  Define Attributes
of System Messages
Configuration In Purchasing, certain system messages containing important
Description information for users may be issued from time to time

In this step, we can specify whether the SAP System:

• Suppresses the relevant information
• Issues it as a warning message
• Issues it as an error message
In the case of an error message, processing cannot be
continued until user input has been corrected

For ITZ requirement, messages (as a change from standard) are
configured as given below:

1.21 Define Purchasing Value Keys
Management  Purchasing  Material Master  Define Purchasing
Value Keys
Configuration With Purchasing value key we can control following functions by using it
Description in the material master purchasing view, purchasing value key governs:
• The issue of reminders and urging letters (expediters) with respect
to nearly due and overdue deliveries
• The admissibility of over- and under deliveries ("overages" and
"under ages")
• Order acknowledgment requirements for PO items
• Shipping/packaging instructions
This data appears as default data in purchasing documents and is taken
from the material master record (unless a purchasing info record exists,

in which case it is taken from the info records).

1.22 Entry Aids for Items without a Material Master
Management  Purchasing  Material Master  Entry Aids for Items
Without a Material Master
Configuration In this step we assign In this step, we can assign a purchasing value key
Description and a valuation class to a material group.
The assignment of a purchasing value key default values for
reminder levels etc. in purchase order items without a material
master record and without an info record.
The assignment of a valuation class to a material group enables
the system to determine different accounts for the individual

material groups.

For ITZ we have maintained Valuation Classes in the accounting view of
the materials.

1.23 Create Purchasing Groups
Management  Purchasing  Create Purchasing Groups
Configuration It’s a key for a buyer or group of buyers responsible for certain purchasing
Description activities. useful in accessing information, controlling authorizations, setting
up release strategies etc. for ITZ ‘s Requirement following groups are
configured, configuration is a simple table entry but purchasing group has a
comprehensive use in all purchasing transactions/ documents

1.24 Define Document Types (RFQ/Quotation)
Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management
 Purchasing  RFQ/Quotation  Define Document Types
Transaction SPRO
Code
Configuration SAP manages RFQs and quotations as documents which are grouped into
Description different document types., in this step we have :
• Created new document types
• Defined item interval
• Defined admissible follow-on document types
• Assigned document types to a number range group
• Defined number range interval
• Chosen type of number assignment
- internal
- external
• Chosen update group
The update group determines how the data from the document header
is updated in the statistics file.

Linkage determines which PR document types can be referenced for
creating a particular RFQ document type

1.25 Define Text Types for Header Texts (RFQ/Quotations)
Management  Purchasing RFQ /Quotations  Define Text Types
for Header Texts
Configuration In this step we define different Texts which appear in RFQ/Quotation
Description Headers, which are used to store information applicable for a particular
RFQ document

We have standard Header Text Types.

1.26 Define copying rules for Header Texts (RFQ/Quotations)
Management  Purchasing RFQ /Quotations  Define copying
rules for Line Texts (RFQ/Quotations)
Configuration In this step we define copying rules for different header Texts which
Description appear in RFQ/Quotation Line Items

Copying rules are used to determine which texts can be adapted from
other objects (for example, vendor master records, contracts) to the
header text of the RFQ. We link text types in the RFQ with text types in
other objects. System can adopt header texts from the following objects:
• RFQ / Quotation
• Contract
• Scheduling agreement
• Vendor master
We can also specify whether the adopted text can be edited in the
destination document or not. This type of setting is more useful in PO
Header Texts

1.27 Define document types (Purchase Requisitions)
 Purchasing  Purchase Requisitions  Define document types
(Purchase Requisitions)
Configuration SAP manages Purchase Requisitions as documents which are grouped
Description into various document types., in this step we have :
- internal
- external
The update group determines how the data from the document
header is updated in the statistics file.

Above linkage governs which type of PO can be created using PR of a
particular type

1.28 Release Procedure with Classification (Purchase Requisitions)
 Purchasing  Purchase Requisitions  Release Procedure
Procedure with Classification  Set Up Procedure with Classification
Transaction SPRO
Code
Configuration In this step, we have set up the release procedure with classification.
Description
Purchase Requisition release is the process in which Purchase Requisition is
approved and released by HOD of concern department for request of required
material or services specified in Purchase Requisition. Once the Purchase
Requisition is approved and released then Purchase Order or RFQ will be
created for that material or services against same Purchase Requisition.

Configuration involves following elements in sequence:

Release Group:
Specify for the release group either "overall release" or "item-wise release"

Release codes:
The Release Code is a two-character ID allowing a person to release
(approve) a requisition.(analogous to approver code)

Release Indicators:

A release indicator shows the release status of a purchase requisition

Release Indicators also involve:

Field selection key
via the field selection key, we can specify which fields in a purchase
requisition with this release indicator can be changed or must be populated

Changes after start of release process

• With the Changeability indicator, we can specify the effects of changes to a
requisition. For example, certain changes may require a new release
strategy to be determined for the requisition.
• Via the Value change field, we can cause the release strategy to be re-
started if the value of a purchase requisition item is increased by more
than a certain percentage (e.g. 10%). To do so, set the Changeability
indicator to "4 - Changeable, new release in case of new strategy or value
change" and enter a percentage in the Value change field.

Release Strategy

The Release Strategy defines the approval process for Purchase Requisitions.
The strategy specifies the release codes which are necessary and the
sequence in which releases have to be affected. We can define a maximum of
eight release codes i.e. 8 Levels of approval.

Release Prerequisites indicate the sequence in which a Purchase Requisition
must be approved via the release codes. (In ITZ case release is
parallel(either / or so indicators are kept blank)

Release Status indicates the affect after the release by a particular release
code

Release Values

These values need to be maintained in every client manually, this forms the
basis on which release strategy is triggered for a PR.
An important prerequisite for this is to create Class & Characteristics in
class type 032

Characteristics for Release Strategy

Create the Characteristics required for release strategy as master data thru
transaction CT04, here the most important setting is to attach the
characteristics to corresponding field of structure CEBAN

attach it to the structure

Class for Release Strategy

Create the class as master data thru transaction CL02

and attach the Characteristics created earlier to the class

1.29 Define Number Ranges (Purchase Orders)
Management  Purchasing Purchase order  Define Number
Ranges
Transaction Code OMH6
Configuration In this step we define number ranges for Purchase order document types,
Description (defined separately in customizing), this setting also includes number
ranges for other external purchasing documents i.e. for

Contracts/Scheduling Agreements and RFQs.

There are two ways of doing this:

• internal number assignment

In this case, a number within the number range interval allowed is
assigned by the SAP system.
• external number assignment

Here, the user assigns a number within the number range interval
allowed. We can define the intervals for external number
assignment numerically and alphanumerically.

In case of ITZ all the documents are assigned with internal number ranges
with the exception for document type “Legacy Open P.O”, as it was
required to retain the legacy P.O number for this case.

go in change mode and define the intervals as shown:

1.30 Define Document types (Purchase Orders)
Management  Purchasing Purchase Orders  Define document
types
Configuration SAP manages Purchase Orders as documents which are grouped into

Description various document types., in this step we have :
• Define allowable item categories
- internal
- external
The update group determines how the data from the document
header is updated in the statistics file.

Above linkage governs which type of PR can be referenced created
while creating a particular Contract document type

1.31 Set Tolerance Limits for Price Variance
Management  Purchasing Purchase order  Set Tolerance Limits
for Price Variance
Configuration When processing a purchase order, the system checks whether the
Description effective price of a PO item shows variances compared with the
valuation price stored in the material master record. In addition, it checks
whether the specified cash discount value is admissible.
Variances are allowed within the tolerance limits. If a variance exceeds a
tolerance limit, the system issues a warning or error message. In SAP,
the types of variance are represented by the tolerance keys. For each
tolerance key, we can define percentage and value-dependent upper
and lower limits per company code.
• PE Price variance, Purchasing
o Tolerance limit for system message no. 207. This message
appears if the specified effective price exceeds the
predefined tolerances when compared with the material
price.
• SE Maximum cash discount deduction, Purchasing
o Tolerance limit for system message no. 231. This is a
warning message, which appears when the specified cash
discount percentage exceeds the predefined tolerances.

1.32 Release Procedure for Purchase Orders
 Purchasing Purchase Order  Release Procedure for Purchase
Orders
Transaction SPRO
Code
Configuration In this step, we have set up the release procedure for Purchase Orders(this
Description also covers the process for other external purchasing documents e.g.
contracts/scheduling agreements)
Purchase Order release is the process in which PO is approved and released
by HOD of concern department for request of required material or services
specified in PO. Once the Order is approved and released then GR can be
created against the PO

In case of ITZ, Release strategy is used in case of all purchases.

Configuration involves following elements in sequence:

Release Group:
Release groups are created for each type of purchasing

Release codes:
The Release Code is a two-character ID allowing a person to release (approve)
a requisition.(analogous to approver code)

Release Indicators:

A release indicator shows the release status of a Purchase Order

Release Indicators also involve:

Changeability Indicator
With the Changeability indicator, we can specify the effects of changes to a
PO document. For example, certain changes may require a new release
strategy to be determined for the requisition.

• Via the Value change field, we can cause the release strategy to be re-
started if the value of a purchase order is increased by more than a certain
percentage (e.g. 10%). To do so, set the Changeability indicator to "6 -
Changeable, new release in case of new strategy or value change" and
enter a percentage in the Value change field.

Release Strategy

The Release Strategy defines the approval process for PO. The strategy
specifies the release codes which are necessary and the sequence in which
releases have to be affected. We can define a maximum of eight release codes
i.e. 8 Levels of approval.

Release Prerequisites indicate the sequence in which a Purchase Requisition
must be approved via the release codes. (In ITZ case release is by a single
authority so there are no prerequisite involved)

Release Status indicates the affect after the release by a particular release
code

Release Values

These values need to be maintained in every client manually, this forms the
basis on which release strategy is triggered for a PO.
An important prerequisite for this is to create Class & Characteristics in class
type 032

Characteristics for Release Strategy

Create the Characteristics required for release strategy as master data thru
transaction CT04, here the most important setting is to attach the
characteristics to corresponding field of structure CEKKO

And attach it to the structure

Class for Release Strategy

Create the class as master data thru transaction CL02 and attach the
Characteristics created earlier to the class

1.33 Define Screen Layout at Document Level
 Purchasing Purchase Orders  Define Screen Layout at Document
Level
Configuration In this step we define the attributes of various fields contained in a field
Description selection key (defined for a document type) inside which various fields are
grouped into fields selection groups.Steps involved in the process are :
• Selecting the field selection key (defined for a document type)
• Select the field selection option (hide, display, required entry, or
Optional entry) for each field inside a field selection group
reference as required.

Select a field selection key and set the attributes inside as shown:

get inside a field group and choose the attributes

settings can be made similarly for other fields in various other groups as
& when required

1.34 Define Text Types for Header Texts (Purchase Orders)
Management  Purchasing Purchase Order  Define Text Types
for Header Texts
Configuration In this step we define different Texts which appear in Purchase order
Description header, these are used to store information applicable for a particular PO
document

1.35 Define copying rules for Header Texts (Purchase Order)
Management  Purchasing Purchase Orders  Define copying
rules for Header Texts
Description appear in Purchase Order Headers

other objects (for example, vendor master records, contracts, RFQ) to
the header text of the Purchase Order. We link text types in the PO with
text types in other objects. System can adopt header texts from the
following objects:
• RFQ / Quotation
• Contract
• Scheduling agreement
• Vendor master
• Purchase Requisition
destination document or not. Currently we are not maintaining any copying
rule for header texts

1.36 Define Text Types for Item Texts (Purchase Orders)
Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management 
Purchasing Purchase Order  Define Text Types for Item Texts
Transaction SPRO
Code
Configuration In this step we define different Texts which appear in Purchase order item level,
Description these are used to store information applicable for a particular PO document line

item

1.37 Define copying rules for Item Texts (Purchase Order)
Management  Purchasing Purchase Orders  Define copying
rules for Item Texts
Configuration In this step we define copying rules for different item Texts which appear in
Description Purchase Order ITEM

the header text of the Purchase Order. We link text types in the PO with
following objects:
• RFQ / Quotation
• Purchase Info record
• Contract
• Material master
We can also specify here whether the adopted text can be edited in the
destination document or not.

maintain the rules for a text as under

1.38 Define Document Types (Contracts)
Purchasing Contracts  Define Document Types
Transaction OMH6
Code
Configuratio SAP manages Contracts as documents which are grouped into various
n document types., in this step we have :
Description • Created new document types
• Define allowable item categories

- internal
- external
The update group determines how the data from the document header is
updated in the statistics file.
In case of ITZ, use of Contracts and Scheduling agreements is very minimal so we
have retained and used standard SAP document types

Above linkage governs which type of PR can be referenced created while
creating a particular Contract document type

1.39 Define Screen Layout at Document Level (Contracts)
Purchasing Contracts  Define Screen Layout at Document Level
Transaction SPRO
Code
Configuratio In this step we define the attributes of various fields contained in a field selection
n key (defined for a document type) inside which various fields are grouped into
Description fields selection groups.Steps involved in the process are :
• Selecting the field selection key (defined for a document type)
• Select the field selection option (hide, display, required entry, or Optional
entry) for each field inside a field selection group reference as required.

Select a field selection key and set the attributes inside as shown:

get inside a field group and choose the attributes

settings can be made similarly for other fields in various other groups as &
when required

1.40 Define Text Types for Header Texts (Contracts)
Management  Purchasing Contracts  Define Text Types for
Header Texts
Configuration In this step we define different Texts which appear in Contract header,
Description these are used to store information applicable for a particular Contract
document

1.41 Define copying rules for Header Texts (Contracts)
Management  Purchasing Contracts  Define copying rules for
Header Texts
Description appear in Contract Headers

other objects (for example, vendor master records, Contract, RFQ) to
the header text of the Contract. We link text types in the PO with text
types in other objects. System can adopt header texts from the following
objects:
• RFQ / Quotation
• Contract
• Vendor master

We are maintaining Standard Text and copying Rules for Header Texts

1.42 Define Text Types for Item Texts (Contracts)
Purchasing Contracts  Define Text Types for Item Texts
Transaction SPRO
Code
Configuration In this step we define different Texts which appear in Contract item level, these
Description are used to store information applicable for a particular Contract document line
item

1.43 Define copying rules for Item Texts (Contract)

Management  Purchasing Contracts  Define copying rules for
Item Texts
Configuration In this step we define copying rules for different item Texts which appear in
Description Contract Headers

the header text of the Contract. We link text types in the Contract with
following objects:
• RFQ / Quotation
• Contract
• Purchase Info record
• Material master
We can also specify here whether the adopted text can be edited in the

maintain the rules for a text as under

1.44 Define External Confirmation Categories
 Purchasing Confirmations  Define External Confirmation
Categories
Transaction SPRO
Code
Configuration Notification from the vendor to the recipient regarding the status of a purchase
Description order., In case of ITZ , CONFIRMATIONS are not being used Confirmation
categories are defined to symbolize the key for a type of confirmation

1.45 Define Internal Confirmation Categories
Purchasing Confirmations  Define Internal Confirmation Categories
Transaction SPRO
Code
Configuration In this step, we assign an external confirmation category to each internal confirmation
Description category.

Internal Categories are for system controls.

1.46 Set Up Confirmation Control
Purchasing Confirmations  Set Up Confirmation Control
Transaction SPRO
Code
Configuration In this step, we assign an external confirmation category to each internal confirmation
Description category.

Internal Categories are for system controls.

As shown all the conformation categories are relevant for MRP, but the last one is
relevant to GR also, which means that when a GR is made against the P.O line

item it will get defaulted with qty of last conf. category
1.47 Define Access Sequence
Purchasing Conditions Define Price Determination Process  Define
Access Sequence
Transaction SPRO
Code
Configuratio Access sequence is an important element of pricing determination. It is the Order
n Description in which the system searches through the condition tables when searching for
particular condition records. The search order goes from specific condition records
to general condition records.

E.G.

Access sequence is made up of condition table (the level at which data is stored)

In the access sequence shown system will search for the record from first to last

table in sequence. (e.g. if Custom duty % for a material is maintained at all the
three levels i.e. Incoterms-plant-maerial / Plant-Material / Plant-Material Type
level , then system will take the record from 1 st available level only i.e. Incoterms-
plant-maerial in this case)

Each condition table is defined as an combination of fields for data access and is
assigned to different condition types ( In case of ITZ , we are not maintaining any
access sequence),

1.48 Define Condition Types
Condition Types
Transaction M/06
Code
sConfiguratio In this step we have defined condition types.
n Description
The condition types are used to represent pricing elements such as prices,
discounts, surcharges, taxes, or delivery costs in the SAP. These are stored in
the system in condition records.

For condition types for which we want to maintain conditions with their own
validity period we have specified an access sequence. (e.g. for all import duty
conditions

Important Settings Condition type include:

Condition Class: Defines nature of condition as Prices / surcharge / discounts
etc.

Calculation type: Defines nature of condition unit i.e. Amount type /
Percentage / Qty etc

Condition Category : e.g. Packaging, Cost , Tax, Delivery Costs(requiring extra
vendor at condition level)

Access Sequence : Allows condition records to be maintained

Header Condition : Allows usage at Header level of Purchasing document

Accruals : Makes a condition irrelevant to net price calculation i.e. excluded from
tax base
1.49 Define Calculation Schema
Calculation Schema
Transaction M/08
Code
Configuratio In this step, we have defined the calculation schemas.
n
Description In MM area, a calculation schema is a framework of steps used to calculate pricing
in as purchasing document

Analogous to this is referred to in the Sales and Distribution (SD) area as a pricing
procedure.

In the calculation schema (pricing procedure), we specify which condition types are
to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically
determines which calculation schema is valid for a business transaction and takes
into account, one after another, the condition types it contains .

In case of ITZ we have defined schemas all starting with Z*, these will get derived
in different types of purchasing documents as per the rule explained in Schema
determination configuration

Select one of the schema and see the control data as shown below:

Important keys in defining Schema are as under:

Step No. & Counter: For determination the sequence of conditions and to act as a
base for calculations with in condition

From- To : Base for calculation of condition value, this is only relevant for % type

of conditions

Statistical: Makes a condition non-relevant to account postings

Subtotal: Used to pass the condition value in to fields of P.O item tables and other
pricing structure

Requirement : Used for validating Condition value determination using small
ABAP written formulae

Base Type: Here a Formula for determining the condition basis as an alternative
to the standard.

Accrual key: for deriving a separate account during GR / Invoice postings

1.50 Define Schema Group
Management  Purchasing Conditions Define Price Determination
Process  Define Schema Group
Configuration Every External Purchase document derives Calculation Schema from a
Description combination of Purchasing Organization and Vendor, to simplify data
maintenance for this process SAP works with grouping concept. So all the
purchasing org. are grouped in to a Schema group and Vendors requiring
same pricing stricture are grouped into a Schema group , now for the
combination of these , system derives the pricing schemas

Click on a row to enter :

the other part i.e. vendors are assigned with schema group in vendor
master
1.51 Define Schema Determination
Process  Define Schema determination
Configuration In this step we have defined the determination of Pricing schema for
Description different type of Purchasing documents and for Stock transport orders

For standard purchase orders
(depending on the schema group of the vendor and the purchasing
organization)
For stock transport orders
(depending on the supplying plant, the document type and the schema
group of the purchasing organization)

select first item ,

and second item

1.52 Define Transaction Event keys
Transaction Event keys
Transaction SPRO
Code
Configuration In this step, we have defined transaction/event keys for condition types involving
Description provisions.
This enables the system to find the relevant account for provisions (for accrued
delivery costs or miscellaneous provisions, for example),
We have assigned these transaction/event key to each condition type that is
relevant to provisions in the step Define Calculation Schema.

Select the 1st row

Select second row, it displays the usage of key in schema

1.53 Maintain Condition Table
Process  Maintain Condition Table
Configuration In this step, we create custom tables, these table are used to store
Description condition records for different condition types , for this these tables should
be a part of access sequence
With help of this we can derive prices, discounts and surcharges
dependent on almost all the fields in a purchasing document.
In a condition table, we specify the combination of fields for which we can
create condition records.
As per SAP recommendation we should not change the condition tables
that are included in the standard version of the SAP System.
Check the extent to which we can use the condition tables that are supplied
with the standard SAP System, for our tables we can only choose names
between 501 and 999. If we make no entry, the system will automatically
assign a consecutive number.

For ITZ we have not defined any tables:

Steps:

For creating new condition tables. copy a similar condition table and proceed as
follows:
• Enter the name of the table we wish to create.
• Note that we can only choose names between 501 and 999. If we make no
entry, the system will automatically assign a consecutive number.
• Specify whether we wish to create the table with or without a validity
period.

• Enter the type of condition table (for example, transparent table).
• Enter a description for the condition table.
• From the list of allowed fields that are included in the field catalog and
which can be extended there, choose the desired fields for the condition
table.
• Generate the new condition table.

IMP: All the fields that shall be used to pick up any condition value must be
part of Header/Key field in the condition table.
1.54 Define Grid for Quantity Variances
Management  Purchasing Statistics Define Grid for Quantity
Variances
Configuration For Purchasing information system for vendor performance the statistics is
Description managed on the amount of quantity variances of vendors.
The delivery quantity variance specifies in percent the variance between
the purchase order quantity and the quantity actually delivered.
This key figure is determined if an order item is completed and is updated
for the entry date of the goods receipt or for the entry date of purchase
order change.
In this step we can determine four interval limits for every purchasing
organization. Five intervals are then available to we for evaluation of
vendors

1.55 Define Grid for Delivery Date Variance
Management  Purchasing Statistics Define Grid for Delivery
date
Configuration Delivery date variance data is used in statistics for evaluating vendor
Description performance.
The delivery date variance specifies the difference in days the difference
between the statistically relevant delivery date and the date of the goods
receipt.

This key figure is updated during the goods receipt for the entry date.

In this step we can determine four interval limits for every purchasing
organization. Five intervals are then available to we for evaluation of
vendors

1.56 Define Weighing keys
 Purchasing Vendor Evaluation  Define Weighing keys
Transaction SPRO
Code
Configuration In vendor evaluation criteria are weighted according to their importance through

Description Weighing key.

For example, the overall evaluation of a vendor is calculated from the scores
awarded for the main evaluation criteria "price," "quality," and "delivery." The
latter comprises "on-time delivery performance" and "quantity reliability."

If we consider a vendor's price to be more important than quality, and quality to
be more important than delivery, we can assign weights to the criteria in a ratio
of three for price, two for quality, and one for delivery. This ratio is recorded in a
weighting key.

1.57 Define Criterion (Vendor Evaluation)
 Purchasing Vendor Evaluation  Define Criterion
Transaction SPRO
Code
Configuration Here we have defined the criteria by which the system computes scores for
Description vendors and specify whether the scores for the subcriteria are computed
manually, semi-automatically, or automatically.

Select One of the criterion and drilldown to sub criterion

1.58 Define Scope of List (Vendor Evaluation)
 Purchasing Vendor Evaluation  Define Scope of List
Transaction SPRO
Code
Configuration In this step we define various types of list, each representing different main
Description criteria or the same main criteria in a different order.

In the standard system, the scope-of-list parameters 'standard' and 'version 1'
are supplied as an example:

• The parameter Standard provides the user with a ranking list of
vendors by overall score. The main criteria are arranged in the order
"Price", "Quality", "Delivery", "General service/support” and "Externally
performed service/work".

• The parameter Version 1 yields a ranking list of vendors sorted
according to the score for the main criterion "Price". Then follow the
overall evaluation and the main criteria "General service/support",
"Quality", "Delivery", and "Externally performed service/work".

check the details of list inside

1.59 Maintain Purchasing Organization data
Management  Purchasing Vendor Evaluation  Maintain
Purchasing Organization data

Configuration
Description

Select a row and displays criterion for Purchasing Organization

Sub criterions for main criterion

Weighing for a Purchasing Org.

We have provided Equal Weighting to the Criteria as we have different
weighing parameters for ITZ

Point scores for a Purchasing Org.

1.60 Define Permissible Partner Roles per Account Group
Management  Purchasing Partner Determination  Partner Roles
Define Permissible Partner Roles per Account Group
Configuration Here we can specify for each account group of the vendor which roles
Description the vendor may assume. Example we can specify that certain vendors
may only serve as an ordering address, not as an invoicing party.

1.61 Define Partner Schemas (Vendor Master)
Management  Purchasing Partner Determination  Partner settings
in Vendor Master records Define Partner Schemas
Configuration Partner schemas allow us to group various partner roles. We can specify
Description that certain roles in a schema are mandatory, i.e. cannot be changed after
entry.

For ITZ, Schema groups Z1 is defined

select a schema to detail the allowed partner functions

1.62 Assign Partner Schemas to Account Groups
in Vendor Master records Assign Partner Schemas to account
groups
Configuration Here we assign the already defined schema groups to vendor account
Description groups

1.63 Define Partner Schemas (Purchasing Documents)
in Purchasing documents Define Partner Schemas

Configuration Partner schemas allow us to group various purchasing documents for
Description partner determination. We can specify that certain roles in a schema are
mandatory, i.e. cannot be changed after entry.

For ITZ, Schema group Z001 is defined

Select a Schema to detail the partner function allowed

1.64 Assign Partner Schemas to Document Types
in Purchasing documents Assign Partner Schemas to document
types
Configuration In this step, we have assigned the partner schemas to the various types of
Description purchasing document.
As a result, only the roles of the schema in question can be maintained in
documents of the relevant types.

Materials Management – External Services Management

1.65 Define Service Category
Management  External Services Management Service Master 
Define Service Category
Configuration In this step, we define the service category.
Description The service category is the most important criterion for structuring
Service master records. It provides a default value for the valuation
Classes. Service master records can be assigned to number ranges on
the basis of the service category.

1.66 Define Number Ranges
Define Number Ranges
Configuration In this step, we define Number Ranges for each service category.
Description

1.67 Define Number Range for Service Entry Sheets
Configuration In this step, we define the service category.
Description The service category is the most important criterion for structuring
Service master records. It provides a default value for the valuation
Classes. Service master records can be assigned to number ranges on
the basis of the service category.

1.68 Define Attributes of System messages
Configuration In External Services Management, a number of system messages
Description containing important information for users may be issued. Users can
process this information further.

In this step, we can define whether the SAP System
• Suppresses this information
• Issues it in the form of a warning
• Issues it in the form of an error message

For ITZ requirement, additional messages no. SE 346 / 347 / 361 is
activated as Error along with other additional Standard SAP Messages

Materials Management – Inventory Mgmt. & Physical Inventory

1.69 Plant Parameters
Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management →
Inventory Management and Physical Inventory → Plant Parameters
Transaction SPRO
Code
Configuratio In this step, we make the general plant settings for ‘Inventory Management’. All
n settings are also contained in the individual steps of the Implementation Guide
Description for Inventory Management.

• If we have created a plant in the enterprise structure using the Copy plant
function, we do not need to make any settings.
• If we have created a plant manually, we have to create a new entry for the
plant parameters.

1.70 Define Number Assignment for Accounting Documents
Inventory Management and Physical Inventory → Number Assignment → Define
Number Assignment for Accounting Documents
Transaction OMBA
Code

Configuratio In this step, we set the number ranges for the accounting documents which are
n created when goods movements or inventory differences are posted.
Description
For accounting-relevant goods movements, the system creates two different
documents:
• material document
• accounting document

Both the material documents and the accounting documents have their own
document numbers. When inventory differences are posted, the system also
creates an accounting document for the physical inventory document.

In this step, we only maintain the number assignment for accounting documents.

Accounting documents are split into document types to allow differentiated
document number assignment, which is the basis for distinguishing between the
various accounting operations. A number range is assigned to each document
type. In a company code, we have to define number intervals for each number
range and fiscal year. In inventory management, the transaction determines
which document type is used.

Goods Issue Document Type

TCode Transaction text Type Description
Subseq. Adjustmt: Act.Ingredient Goods
MB05 Mat WE receipt
MB11 Goods Movement WA Goods

issue
Goods
MB1A Goods Withdrawal WA issue
Goods
MB1B Transfer Posting WA issue
Goods
MB26 Picking list WA issue
Place in Stor.for Mat.Doc:
MBSU Init.Scrn
Goods
MIGO_GI Goods Movement WA issue
MIGO_T Goods
R Transfer Posting WA issue

Goods Receipt Document Type

Typ
TCode Transaction text e Description
Goods
MB01 Post Goods Receipt for PO WE receipt
Subsequ.Adj.of Goods
MB04 "Mat.Provided"Consmp. WE receipt
Goods
MB0A Post Goods Receipt for PO WE receipt
Goods
MB1C Other Goods Receipts WA issue
Goods Receipt for Production Goods
MB31 Order WE receipt
Subsequent Delivery f. Material
MBNL Doc.
MBRL Return Delivery for Matl Document
Release Blocked Stock via Mat. Goods
MBSF Doc. WE receipt
MBSL Copy Material Document
MBST Cancel Material Document
MIGO_G Goods
O Goods Movement WE receipt
MIGO_G Goods
R Goods Movement WE receipt
MIGO_G Subseq. Adjust. of Material Goods
S Provided WE receipt

Automatic Movements Document Type

TCode Transaction text Type Description
BMBC Batch Information Cockpit WA Goods issue
Goods
BORGR GR Automotive WE receipt
Goods
BORGR_B GR Automotive: Posting WE receipt
Goods
BORGR_C GR Automotive: Clearing WE receipt
CAT5 Data Transfer CATS -> PS WA Goods issue
Data Transfer CATS ->
CAT9 PM/CS WA Goods issue
CIP2 CC2: Update PDC messages WA Goods issue

CIPV Posting PDC records WA Goods issue

Physical Inventory Document Type

TCod
e Transaction text Type Description
Inventory
MI07 Process List of Differences WI document
Create List of Differences with Inventory
MI08 Doc. WI document
Create List of Differences w/o Inventory
MI10 Doc. WI document

1.71 Define Number Assignment for Material and Physical Inventory Documents
Inventory Management and Physical Inventory → Number Assignment →
Define Number Assignment for Material and Phys.Inv Documents
Transaction OMBT
Code
Configuratio In this step, we maintain the number assignment for the following documents:
n • material documents
Description • physical inventory documents

The number assignment for these documents is not to be confused with the
number assignment for accounting documents which we completed in the step
Define number assignment for accounting documents. The number assignment
for accounting documents depends on the document type which is allocated to
the transaction.

The number assignment for material documents and physical inventory
documents depends on the transaction/event type which is also allocated to
each transaction in Inventory Management. The transaction/event types are
divided into groups of number ranges. A number range interval has to be
defined for each group.

No From no. To number Status Ext
01 0100000000 0199999999 0
02 4900000000 4999999999 4900002419
03 5000000000 5999999999 5000000219
04 0200000000 0299999999 0

Note
We cannot change the transaction/event types. However, we can
change the number range intervals or we can allocate transaction/event
types to new groups.

SPRO-> IMG-> Materials Management-> Inventory Management and Physical Inventory->
Number Assignment-> Define Number Assignment for Material and Phys. Inv. Docs
Her you ned to maintain the number ranges for the group attched to the key.

If you want to maintain new number range intervals for an existing group:
a) Choose Group -> Maintain.
b) Select a group and choose Interval -> Maintain.
c) Choose Edit -> Insert year.
d) Maintain the number interval for the new fiscal year.

Sap MM-configuration-step-by-step-guide

Sap MM-configuration-step-by-step-guide

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Sap MM-configuration-step-by-step-guide

Semelhante a Sap MM-configuration-step-by-step-guide (20)

Mais de Venet Dheer

Mais de Venet Dheer (11)

Último

Último (20)

Sap MM-configuration-step-by-step-guide