87
Generated by Jive on 2016-01-08+01:00 1 SAP MM Configuration MM – Configuration Documentation 2 Enterprise Structure - Definition 2.1 Define Valuation Level

MM – Configuration Documentation

Embed Size (px)

DESCRIPTION

MM – Configuration Documentation

Citation preview

Page 1: MM – Configuration Documentation

Generated by Jive on 2016-01-08+01:001

SAP MM Configuration

MM – Configuration Documentation

2 Enterprise Structure - Definition

2.1 Define Valuation Level

Page 2: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:002

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Definition ® Logisticsgeneral ® Define Valuation Level

Transaction Code OX14

Configuration DescriptionHere we specify the level at which material stocks

are valuated. We 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 companycode in the material master record.

• If material stocks are valuated at company codelevel, all plant stocks of a material are managed ina joint stock account for each company code.

• If material stocks are valuated at plant level, thematerial stocks for each plant can be managedin different accounts. We can define a separateaccount determination for each plant.

2.2 Define Plant

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Definition ® Logisticsgeneral ® Define, copy, delete, check plant

Transaction Code SPRO

Configuration DescriptionAs a part of the Logistics OrganizationalStructure, Plants are defined in SAP. The ‘Plant’is an operating area or a branch or a locationwithin a company. Each 'Plant' is assigned to asingle 'company code'. A 'company code' canhave several 'Plants'. In case of ITZ Pvt. Ltd., the

various 'Plants' are assigned to each 'company code'.

Configuration of One Plant is depicted here, (for list of

all please refer to MM KDS Document)

Page 3: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:003

2.3 Maintain Storage Location

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Definition ® MaterialsManagement ® Maintain Storage Location

Transaction Code OX09

Configuration DescriptionA storage location is the place where stock is

physically kept within a plant. 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)

2.4 Maintain purchasing organization

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Enterprise Structure ® Definition ®Materials Management à Maintain PurchasingOrganization

Transaction Code SPRO

Configuration DescriptionAt this node we configure the Purchasing

Organization .The purchasing 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 :

Page 4: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:004

3 Enterprise Structure Assignments

3.1 Assign Plant to Company Code

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Assignment ® Logisticsgeneral ® Assign Plant to Company Code

Transaction Code SPRO

Configuration DescriptionA Plant needs to be assigned to one of the Company

Codes, the relation 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 completelist refer MM KDS document)

3.2 Assign purchasing organization to company code

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Assignment ® Logisticsgeneral ® Assign purchasing organization tocompany code

Transaction Code SPRO

Configuration DescriptionIn this node we assign the Purchasing Organization

to the company code under which it works.

In case of ITZ the Purchasing Organization is Central,

so it is not assigned to any Company Code

3.3 Assign purchasing organization to Plant

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Enterprise Structure ® Assignment ® Logisticsgeneral ® Assign purchasing organization toPlant

Transaction Code SPRO

Page 5: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:005

Configuration DescriptionIn this step we assign purchasing organizations to the

plants for which 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

3.4 Assign standard purchasing organization to plant

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Enterprise Structure ® Assignment ®Logistics general ® Assign standard purchasingorganization to plant

Transaction Code SPRO

Configuration DescriptionIf several purchasing organisations procure for a

certain plant, we can define one of them as the

standard purchasing organization for the transactions

"pipeline procurement", "consignment" 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

4 General Logistics

4.1 Assign Fields to Fields Selection Groups

Menu path 1. Implementation Guide for R/3Customizing (IMG) ® Logistics- General à Material Master àField Selectionà Assign Fieldsto Fields Selection Groups

Transaction Code OMSR

Page 6: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:006

Configuration DescriptionAssignment of Material Master

Fields is required to define whether

a 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

DescriptionChanged

Field Grp

MVKE-

MVGR1

Material

group 1

211

MVKE-

MVGR2

Material

group 2

211

MVKE-

MVGR3

Material

group 3

211

4.2 Maintain Field Selection for Data Screens

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à FieldSelectionà Maintain Field Selection for DataScreens

Transaction Code OMS9

Configuration DescriptionIn this step we define the nature of a Field belonging

to a particular Field 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 fieldreference as required.

Page 7: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:007

4.3 Maintain Company Codes for Materials Management

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Logistics - General à Material Master àBasic Settingsà Maintain Company Codes forMaterials Management

Transaction Code OMSY

Configuration DescriptionThis activity is done for making a Company Code

relevant for materials Management and to define

the starting posting period This is a prerequisite for

creating a Material Master

4.4 Define Attributes of Material Types

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à BasicSettingsà Material Typesà Define Attributes ofMaterial Types

Transaction Code OMS2

Configuration DescriptionMaterial type is analogous to the family of a material

master; all the important attributes of a material are

governed by settings in the material type. To be

precise it governs :1. 1. Number range pattern and nature (external/

internal)2. 2. Hide/optional fields in the material master3. 3. Valuation Control at valuation area level

(ultimately used to derive G/L)4. 4. Control on Production/Purchase

4.5 Define Number Ranges for each material types

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à BasicSettingsà Material Typesà Define NumberRanges for each Material Types

Transaction Code MMNR

Page 8: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:008

Configuration DescriptionIn this step, we have defined the type of number

assignment and the 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 numberrange interval allowed. We can define the intervalsfor external number assignment numerically andalphanumerically.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 externalnumber range interval for the material type.

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

4.6 Define Attributes of system messages

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Logistics - General à Material Masterà Basic Settingsà Define Attributes of systemmessages

Transaction Code OMT4

Configuration DescriptionWhen processing material master records, the system

issues a number of system 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.

Page 9: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:009

• The message can be displayed as an errormessage. (can’t be surpassed)

For ITZ requirement Message Numbers MM189 &

312 are changed as Error message

We are using Standard SAP Messages.

4.7 Define Material Groups

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à Settingsfor Key Fieldsà Define Material Groups

Transaction Code OMSF

Configuration DescriptionHere we define the Groups for Materials & Services,

This Grouping shall 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

4.8 Define External Material Groups

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à Settingsfor Key Fieldsà Define External Material Groups

Transaction Code SPRO

Configuration DescriptionHere we define the Groups for giving an extra key for

filtering, sorting the list of materials from a criterion

other than Material grouping

In case of ITZ we have not used External Material

Groups

Page 10: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0010

4.9 Initialize Period

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Logistics - General à Material Master à ToolsàInitialize Period

Transaction Code MMPI

Configuration DescriptionThis Transaction can be used to initialize the period

in materials management , 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

5 Materials Management –Consumption based Planning

5.1 Activate MRP for MRP Areas

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Consumption-basedPlanning à Master Data à MRP Areas àActivateMRP for MRP Areas

Transaction Code SPRO

Configuration DescriptionThis setting is required if we want to have planning

at a level other than plants i.e. 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.

Page 11: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0011

5.2 Define MRP Areas

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Consumption-basedPlanning à Master Data à MRP Areas àDefineMRP Areas

Transaction Code SCAL

Configuration DescriptionHere we define the MRP areas for a plant for which

we would like to carry out 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.

Page 12: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0012

6 Materials Management – Purchasing

6.1 Define Attributes of System Messages

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasing àEnvironment Data à Define Attributes of SystemMessages

Transaction Code SPRO

Configuration DescriptionIn Purchasing, certain system messages containing

important 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 cannotbe continued until user input has been corrected

For ITZ requirement, messages (as a change from

standard) are configured as given below:

6.2 Define Purchasing Value Keys

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing à MaterialMaster à Define Purchasing Value Keys

Transaction Code SPRO

Configuration DescriptionWith Purchasing value key we can control following

functions by using it in the material master purchasing

view, purchasing value key governs:• The issue of reminders and urging letters

(expediters) with respect to nearly due andoverdue deliveries

• The admissibility of over- and under deliveries("overages" and "under ages")

• Order acknowledgment requirements for PO items• Shipping/packaging instructions

Page 13: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0013

This data appears as default data in purchasingdocuments and is taken from the material masterrecord (unless a purchasing info record exists, inwhich case it is taken from the info records).

6.3 Entry Aids for Items without a Material Master

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasing àMaterial Master à Entry Aids for Items Without aMaterial Master

Transaction Code SPRO

Configuration DescriptionIn this step we assign In this step, we can assign

a purchasing value key 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.

6.4 Create Purchasing Groups

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing à CreatePurchasing Groups

Transaction Code SPRO

Configuration DescriptionIt’s a key for a buyer or group of buyersresponsible for certain purchasing activities.useful in accessing information, controllingauthorizations, setting up release strategiesetc. for ITZ ‘s Requirement following groupsare configured, configuration is a simpletable entry but purchasing group has

Page 14: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0014

a comprehensive use in all purchasingtransactions/ documents

6.5 Define Document Types (RFQ/Quotation)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing à RFQ/Quotation à Define Document Types

Transaction Code SPRO

Configuration DescriptionSAP manages RFQs and quotations as documents

which are grouped into 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

• internal• external

• Chosen

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

6.6 Define Text Types for Header Texts (RFQ/Quotations)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àRFQ /

Page 15: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0015

Quotations à Define Text Types for HeaderTexts

Transaction Code SPRO

Configuration DescriptionIn this step we define different Texts which appear

in RFQ/Quotation Headers, which are used to store

information applicable for a particular RFQ document

We have standard Header Text Types.

6.7 Define copying rules for Header Texts (RFQ/

Quotations)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àRFQ /Quotations à Define copying rules for LineTexts (RFQ/Quotations)

Transaction Code SPRO

Configuration DescriptionIn this step we define copying rules for different

header Texts which 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 beedited in the destination document or not. This type ofsetting is more useful in PO Header Texts

6.8 Define document types (Purchase Requisitions)

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasing àPurchase Requisitions à Define document types(Purchase Requisitions)

Page 16: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0016

Transaction Code SPRO

Configuration DescriptionSAP manages Purchase Requisitions as documents

which are grouped into various 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

• internal• external

• Chosen

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

6.9 Release Procedure with Classification (Purchase

Requisitions)

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasingà Purchase Requisitions à Release ProcedureàProcedure with Classification à Set UpProcedure with Classification

Transaction Code SPRO

Configuration DescriptionIn this step, we have set up the release procedure

with classification.

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.

Page 17: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0017

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. Forexample, certain changes may require a newrelease strategy to be determined for therequisition.

• Via the Value change field, we can cause therelease strategy to be re-started if the value of apurchase requisition item is increased by morethan a certain percentage (e.g. 10%). To do so,set the Changeability indicator to "4 - Changeable,new release in case of new strategy or valuechange" and enter a percentage in the Valuechange field.

Release Strategy

Page 18: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0018

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

Page 19: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0019

Create the class as master data thru transaction

CL02

and attach the Characteristics created earlier to the

class

6.10 Define Number Ranges (Purchase Orders)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseorder à Define Number Ranges

Transaction Code OMH6

Configuration DescriptionIn this step we define number ranges for Purchase

order document types, (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 numberrange interval allowed. We can define the intervalsfor external number assignment numerically andalphanumerically.

In case of ITZ all the documents are assignedwith internal number ranges with the exceptionfor document type “Legacy Open P.O”, as itwas required to retain the legacy P.O numberfor this case.

go in change mode and define the intervals as

shown:

Page 20: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0020

6.11 Define Document types (Purchase Orders)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrders à Define document types

Transaction Code SPRO

Configuration DescriptionSAP manages Purchase Orders as documents which

are grouped into various document types., in this step

we have :• Created new document types• Defined item interval• Define allowable item categories• Defined admissible follow-on document types• Assigned document types to a number range

group• Defined number range interval• Chosen

• internal• external

• Chosen

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

6.12 Set Tolerance Limits for Price Variance

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseorder à Set Tolerance Limits for Price Variance

Transaction Code SPRO

Configuration DescriptionWhen processing a purchase order, the system

checks whether the effective price of a PO item

shows variances compared with the valuation price

stored in the material master record. In addition, it

Page 21: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0021

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

• • Tolerance limit for system message no. 207.This message appears if the specified effectiveprice exceeds the predefined tolerances whencompared with the material price.

• SE Maximum cash discount deduction,Purchasing

• • Tolerance limit for system message no. 231.This is a warning message, which appearswhen the specified cash discount percentageexceeds the predefined tolerances.

6.13 Release Procedure for Purchase Orders

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrder à Release Procedure for PurchaseOrders

Transaction Code SPRO

Configuration DescriptionIn this step, we have set up the release procedure

for Purchase Orders(this 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.

Page 22: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0022

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 ofa purchase order is increased by more than acertain percentage (e.g. 10%). To do so, set theChangeability indicator to "6 - Changeable, newrelease 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.

Page 23: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0023

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

6.14 Define Screen Layout at Document Level

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchase

Page 24: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0024

Orders à Define Screen Layout at DocumentLevel

Transaction Code SPRO

Configuration DescriptionIn this step we define the attributes of various fields

contained in a field 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 fieldinside a field selection group reference asrequired.

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

6.15 Define Text Types for Header Texts (Purchase

Orders)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrder à Define Text Types for Header Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define different Texts which appear

in Purchase order header, these are used to store

information applicable for a particular PO document

Page 25: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0025

6.16 Define copying rules for Header Texts (Purchase

Order)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrders à Define copying rules for Header Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define copying rules for different

header Texts which appear in Purchase Order

Headers

Copying rules are used to determine which texts can

be adapted from 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

We can also specify whether the adopted text can beedited in the destination document or not. Currentlywe are not maintaining any copying rule for headertexts

6.17 Define Text Types for Item Texts (Purchase Orders)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrder à Define Text Types for Item Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define different Texts which appear

in Purchase order item level, these are used to store

information applicable for a particular PO document

line item

Page 26: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0026

6.18 Define copying rules for Item Texts (Purchase

Order)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPurchaseOrders à Define copying rules for Item Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define copying rules for different item

Texts which appear in Purchase Order ITEM

Copying rules are used to determine which texts can

be adapted from 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• Purchase Requisition• Purchase Info record• Contract• Material master

We can also specify here whether the adopted textcan be edited in the destination document or not.

maintain the rules for a text as under

6.19 Define Document Types (Contracts)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define Document Types

Transaction Code OMH6

Configuration DescriptionSAP manages Contracts as documents which are

grouped into various document types., in this step we

have :• Created new document types• Defined item interval• Define allowable item categories• Defined admissible follow-on document types• Assigned document types to a number range

group

Page 27: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0027

• Defined number range interval• Chosen

• internal• external

• Chosen

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

6.20 Define Screen Layout at Document Level

(Contracts)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define Screen Layout at Document Level

Transaction Code SPRO

Configuration DescriptionIn this step we define the attributes of various fields

contained in a field 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 fieldinside a field selection group reference asrequired.

Select a field selection key and set the attributes

inside as shown:

get inside a field group and choose the attributes

Page 28: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0028

settings can be made similarly for other fields in

various other groups as & when required

6.21 Define Text Types for Header Texts (Contracts)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define Text Types for Header Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define different Texts which appear in

Contract header, these are used to store information

applicable for a particular Contract document

6.22 Define copying rules for Header Texts (Contracts)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define copying rules for Header Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define copying rules for different

header Texts which appear in Contract Headers

Copying rules are used to determine which texts can

be adapted from 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 can also specify whether the adopted text can beedited in the destination document or not.

We are maintaining Standard Text and copying Rules

for Header Texts

Page 29: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0029

6.23 Define Text Types for Item Texts (Contracts)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define Text Types for Item Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define different Texts which appear

in Contract item level, these are used to store

information applicable for a particular Contract

document line item

6.24 Define copying rules for Item Texts (Contract)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àContractsà Define copying rules for Item Texts

Transaction Code SPRO

Configuration DescriptionIn this step we define copying rules for different item

Texts which appear in Contract Headers

Copying rules are used to determine which texts can

be adapted from other objects (for example, vendor

master records, contracts, RFQ) to the header text of

the Contract. We link text types in the Contract with

text types in other objects. System can adopt header

texts from the following objects:• RFQ / Quotation• Purchase Requisition• Contract• Purchase Info record• Material master

We can also specify here whether the adopted textcan be edited in the destination document or not.

maintain the rules for a text as under

6.25 Define External Confirmation Categories

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasing

Page 30: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0030

àConfirmations à Define External ConfirmationCategories

Transaction Code SPRO

Configuration DescriptionNotification from the vendor to the recipient regarding

the status of a purchase order., In case of ITZ ,

CONFIRMATIONS are not being used Confirmation

categories are defined to symbolize the key for a type

of confirmation

6.26 Define Internal Confirmation Categories

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConfirmations à Define Internal ConfirmationCategories

Transaction Code SPRO

Configuration DescriptionIn this step, we assign an external confirmation

category to each internal confirmation category.

Internal Categories are for system controls.

6.27 Set Up Confirmation Control

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConfirmations à Set Up Confirmation Control

Transaction Code SPRO

Configuration DescriptionIn this step, we assign an external confirmation

category to each internal confirmation 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

6.28 Define Access Sequence

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à Purchasing

Page 31: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0031

àConditionsà Define Price Determination Processà Define Access Sequence

Transaction Code SPRO

Configuration DescriptionAccess sequence is an important element of

pricing determination. It is the Order 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.1. 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 1st 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),

6.29 Define Condition Types

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Define Condition Types

Transaction Code M/06

s

Configuration Description

In this step we have defined condition types.

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

Page 32: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0032

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

6.30 Define Calculation Schema

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Define Calculation Schema

Transaction Code M/08

Configuration DescriptionIn this step, we have defined the calculation

schemas.

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

Page 33: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0033

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

6.31 Define Schema Group

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Define Schema Group

Transaction Code SPRO

Configuration DescriptionEvery External Purchase document derives

Calculation Schema from a 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 :

Page 34: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0034

the other part i.e. vendors are assigned with schema

group in vendor master

6.32 Define Schema Determination

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Define Schema determination

Transaction Code SPRO

Configuration DescriptionIn this step we have defined the determination of

Pricing schema for 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

6.33 Define Transaction Event keys

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Define Transaction Event keys

Transaction Code SPRO

Configuration DescriptionIn this step, we have defined transaction/event keys

for condition types involving provisions.

This enables the system to find the relevant

account for provisions (for accrued delivery costs or

miscellaneous provisions, for example),

Page 35: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0035

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

6.34 Maintain Condition Table

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàConditionsà Define Price Determination Processà Maintain Condition Table

Transaction Code SPRO

Configuration DescriptionIn this step, we create custom tables, these table are

used to store 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.

Page 36: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0036

• Note that we can only choose names between501 and 999. If we make no entry, the system willautomatically assign a consecutive number.

• Specify whether we wish to create the table with orwithout 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.

6.35 Define Grid for Quantity Variances

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àStatisticsàDefine Grid for Quantity Variances

Transaction Code SPRO

Configuration DescriptionFor Purchasing information system for vendor

performance the statistics is 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

6.36 Define Grid for Delivery Date Variance

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àStatisticsàDefine Grid for Delivery date

Page 37: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0037

Transaction Code SPRO

Configuration DescriptionDelivery date variance data is used in statistics for

evaluating vendor 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

6.37 Define Weighing keys

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àVendorEvaluation à Define Weighing keys

Transaction Code SPRO

Configuration DescriptionIn vendor evaluation criteria are weighted according

to their importance through 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.

Page 38: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0038

6.38 Define Criterion (Vendor Evaluation)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àVendorEvaluation à Define Criterion

Transaction Code SPRO

Configuration DescriptionHere we have defined the criteria by which the

system computes scores for 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

6.39 Define Scope of List (Vendor Evaluation)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àVendorEvaluation à Define Scope of List

Transaction Code SPRO

Configuration DescriptionIn this step we define various types of list, each

representing different main 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 overallscore. The main criteria are arranged in theorder "Price", "Quality", "Delivery", "Generalservice/support” and "Externally performedservice/work".

• The parameter Version 1 yields a ranking list ofvendors sorted according to the score for the maincriterion "Price". Then follow the overall evaluationand the main criteria "General service/support","Quality", "Delivery", and "Externally performedservice/work".

check the details of list inside

Page 39: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0039

6.40 Maintain Purchasing Organization data

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àVendorEvaluation à Maintain Purchasing Organizationdata

Transaction Code SPRO

Configuration DescriptionSelect 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.

6.41 Define Permissible Partner Roles per Account

Group

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàPartner Determination à Partner Rolesà DefinePermissible Partner Roles per Account Group

Transaction Code SPRO

Configuration DescriptionHere we can specify for each account group of

the vendor which roles the vendor may assume.

Example we can specify that certain vendors may

only serve as an ordering address, not as an invoicing

party.

Page 40: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0040

6.42 Define Partner Schemas (Vendor Master)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPartnerDetermination à Partner settings in Vendor Masterrecordsà Define Partner Schemas

Transaction Code SPRO

Configuration DescriptionPartner schemas allow us to group various partner

roles. We can specify 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

6.43 Assign Partner Schemas to Account Groups

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPartnerDetermination à Partner settings in Vendor Masterrecordsà Assign Partner Schemas to accountgroups

Transaction Code SPRO

Configuration DescriptionHere we assign the already defined schema groups to

vendor account groups

6.44 Define Partner Schemas (Purchasing Documents)

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPartnerDetermination à Partner settings in Purchasingdocumentsà Define Partner Schemas

Transaction Code SPRO

Page 41: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0041

Configuration DescriptionPartner schemas allow us to group various

purchasing documents for 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

6.45 Assign Partner Schemas to Document Types

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à Purchasing àPartnerDetermination à Partner settings in Purchasingdocumentsà Assign Partner Schemas todocument types

Transaction Code SPRO

Configuration DescriptionIn this step, we have assigned the partner schemas

to the various types of purchasing document.

As a result, only the roles of the schema in question

can be maintained in documents of the relevant

types.

7 Materials Management – ExternalServices Management

7.1 Define Service Category

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à External ServicesManagementà Service Master à Define ServiceCategory

Transaction Code SPRO

Configuration DescriptionIn this step, we define the service category.

The service category is the most important criterion

for structuring

Service master records. It provides a default value for

the valuation

Page 42: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0042

1. Classes. Service master records can be assignedto number ranges on the basis of the servicecategory.

7.2 Define Number Ranges

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à External ServicesManagementà Service Master à Define NumberRanges

Transaction Code SPRO

Configuration DescriptionIn this step, we define Number Ranges for each

service category.

7.3 Define Number Range for Service Entry Sheets

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à External ServicesManagementà Service Master à Define ServiceCategory

Transaction Code SPRO

Configuration DescriptionIn this step, we define the service category.

The service category is the most important criterion

for structuring

Service master records. It provides a default value for

the valuation1. Classes. Service master records can be assigned

to number ranges on the basis of the servicecategory.

7.4 Define Attributes of System messages

Menu path 1. Implementation Guide for R/3 Customizing (IMG)® Materials Management à External ServicesManagementà Service Master à Define ServiceCategory

Transaction Code SPRO

Page 43: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0043

Configuration DescriptionIn External Services Management, a number of

system messages 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

8 Materials Management – InventoryMgmt. & Physical Inventory

8.1 Plant Parameters

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® PlantParameters

Transaction Code SPRO

Configuration DescriptionIn this step, we make the general plantsettings for ‘Inventory Management’. Allsettings are also contained in the individualsteps of the Implementation Guide forInventory Management. • If we have created a plant in the enterprise

structure using the Copy plant function, we do notneed to make any settings.

• If we have created a plant manually, we have tocreate a new entry for the plant parameters.

Page 44: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0044

8.2 Define Number Assignment for Accounting

Documents

Menu path 1. Implementation Guidefor R/3 Customizing(IMG) ® MaterialsManagement® InventoryManagement andPhysical Inventory ®Number Assignment® Define NumberAssignmentfor AccountingDocuments

Transaction Code OMBA

Configuration

Description

In this step, we set the

number ranges for the

accounting documents

which are created when

goods movements or

inventory differences are

posted.

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.

Page 45: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0045

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

TCodeTransaction

text

Type Description

MB05 1. Subseq.Adjustmt:Act.IngredientMat

WE Goods

receipt

MB11 Goods

Movement

WA Goods

issue

MB1A Goods

Withdrawal

WA Goods

issue

Page 46: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0046

MB1B Transfer

Posting

WA Goods

issue

MB26 Picking

list

WA Goods

issue

MBSUPlace

in

Stor.for

Mat.Doc:

Init.Scrn

MIGO_GIGoods

Movement

WA Goods

issue

MIGO_TRTransfer

Posting

WA Goods

issue

Goods Receipt Document

Type

TCodeTransaction

text

Type Description

MB01 Post

Goods

Receipt

for

PO

WE Goods

receipt

MB04 1. Subsequ.Adj.of"Mat.Provided"Consmp.

WE Goods

receipt

MB0A Post

Goods

Receipt

for

PO

WE Goods

receipt

MB1COther

Goods

Receipts

WA Goods

issue

MB31 Goods

Receipt

for

WE Goods

receipt

Page 47: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0047

Production

Order

MBNLSubsequent

Delivery

f.

Material

Doc.

MBRLReturn

Delivery

for

Matl

Document

MBSFRelease

Blocked

Stock

via

Mat.

Doc.

WE Goods

receipt

MBSL Copy

Material

Document

MBSTCancel

Material

Document

MIGO_GOGoods

Movement

WE Goods

receipt

MIGO_GRGoods

Movement

WE Goods

receipt

MIGO_GS1. Subseq.Adjust.ofMaterialProvided

WE Goods

receipt

Automatic Movements

Document Type

TCodeTransaction

text

Type Description

Page 48: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0048

BMBCBatch

Information

Cockpit

WA Goods

issue

BORGRGR

Automotive

WE Goods

receipt

BORGR_BGR

Automotive:

Posting

WE Goods

receipt

BORGR_CGR

Automotive:

Clearing

WE Goods

receipt

CAT5 Data

Transfer

CATS

->

PS

WA Goods

issue

CAT9 Data

Transfer

CATS

->

PM/

CS

WA Goods

issue

CIP2 CC2:

Update

PDC

messages

WA Goods

issue

CIP3 CC3:

Update

PDC

messages

WA Goods

issue

CIP4 CC4:

Update

PDC

messages

WA Goods

issue

CIP5 CC5:

Update

PDC

messages

WA Goods

issue

Page 49: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0049

CIPV Posting

PDC

records

WA Goods

issue

Physical Inventory

Document Type

TCodeTransaction

text

Type Description

MI07 Process

List

of

Differences

WI Inventory

document

MI08 Create

List

of

Differences

with

Doc.

WI Inventory

document

MI10 Create

List

of

Differences

w/o

Doc.

WI Inventory

document

8.3 Define Number Assignment for Material and Physical

Inventory Documents

Menu path 1. ImplementationGuide for R/3Customizing(IMG) ®MaterialsManagement® InventoryManagementand PhysicalInventory® NumberAssignment ®

Page 50: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0050

Define NumberAssignmentfor Materialand Phys.InvDocuments

Transaction Code OMBT

Configuration

Description

In this step, we

maintain the number

assignment for

the following

documents:• material

documents• physical

inventorydocuments

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

Page 51: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0051

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

StatusExt

01 010000000001999999990

02 490000000049999999994900002419

03 500000000059999999995000000219

04 020000000002999999990

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

Page 52: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0052

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.

8.4 Define Number Assignment for Reservations

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® NumberAssignment ® Define Number Assignment forReservations

Transaction Code OMJK

Page 53: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0053

Configuration DescriptionIn this step, we set up number assignment for

reservations.

The number assignment applies to all plants in the

client.

Note

If we create reservations with method

CreateFromData1 (function module

BAPI_RESERVATION_CREATE1), we can use the

number range RB for an external number assignment.

8.5 Field Selection for Goods Movement/Initial Header

Screens

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® FieldSelection for Goods Movement/HeaderScreens

Transaction Code OMJN

Configuration DescriptionIn this step, we define the field selection for goods

movements initial and header screens.

Note that the field selection for the item screens

depends on the movement type and is configured in

separate steps.

In this step, we specify whether the fields are input,

mandatory, display or hidden.

8.6 Field Selection for MIGO

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® Settingsfor Enjoy Transactions ® Settings for GoodsMovements ® Field Selection for MIGO

Transaction Code OMJX

Configuration DescriptionHere we can:• Hide the header data completely or hide particular

fields that we do not require• Hide pushbuttons that we do not require

Page 54: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0054

• Define the Delivery note and Bill of lading fieldsas mandatory entries if we use evaluated receiptsettlement

• Show the GR/GI slip (GOHEAD-XABLN) field if weuse GR/GI slip numbers (only necessary in certaincountries)

• Show the Plant (GODYNPRO-PO_WERKS) field ifwe require the ordering-plant name for purchase-order-related goods movements as a selectioncriterion in addition to the purchase order numberand item number

Hide the print indicator if we do not want to print outGR/GI slips in Inventory Management

8.7 Field Selection per Movement Type

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® Settingsfor Enjoy Transactions ® Settings for GoodsMovements ® Field Selection per Mvt Type

Transaction Code SPRO

Configuration DescriptionIn this step, we maintain all the settings for field

selection by movement type. This step replaces

the activity Define Screen Layout for the Enjoy

transactions. The settings from Define Screen Layout

are adopted in these settings automatically so that we

do not need to maintain new entries here.

We can specify for each field whether it is an optional

entry or a mandatory entry. In the table, we see all

fields that are visible. We can access the setting Field

Invisible by deleting the appropriate entry from the

table.

There is no distinction between different special stock

indicators in these entries. Special stock fields are

always suppressed automatically.

8.8 Settings for Transactions and Reference Documents

Menu path 1. ImplementationGuide for R/3Customizing

Page 55: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0055

(IMG) ®MaterialsManagement® InventoryManagementand PhysicalInventory® Settingsfor EnjoyTransactions® Settingsfor GoodsMovements® SettingsforTransactionsandReferenceDocuments

Transaction

Code

SPRO

Configuration

Description

We can limit

the number

of selectable

transactions

(goods receipt,

goods issue,

and so on)

and reference

documents

(material

document,

delivery note),

and we can

specify the

movement type

that the system

is to propose for

every reference

document.

If we need

only certain

transactions

(for example,

goods receipts

Page 56: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0056

or goods

issues), we can

choose from the

following preset

transactions:

MIGO - Used to

enter all goods

receipts.

MIGO_GR -

Used to enter

goods receipts

from external

procurement.

MIGO_GO -

Used to enter

goods receipts

for production

orders.

MIGO_GI -

Used to enter

goods issues.

We can always

display material

documents.

Transaction

MIGO; Actions

Mentioned in the

table

ActionActiveActionActive

A01 A08

A02 A09X

A03X A10

A04X A11

A05

A06

Page 57: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0057

A07X

Reference

Document

Types (For

details go to the

path mentioned)

1. Ref.ActiveMvT1. Ref.ActiveMvT

R01X 101R02X

R04X 101R03X

R05 101R01X 351

R06 101R08X 261

R07 101R09X 201

R08X 101R10X 201

R09 501R09X

R10X 511R10X 301

R02X R10X 303

R03X R02X

R02X R10X 305

R02X R01X

R02X

8.9 Create Storage Location Automatically

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsIssue/Transfer Postings® Create StorageLocation Automatically

Transaction Code OMB2

Configuration DescriptionIn this step, we specify whether the automatic

creation of storage location data is allowed for goods

issues and transfer postings.

Page 58: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0058

This is advisable if we work with negative stocks

and a material's first movement may be an outward

movement.

Note that the reversal movement for a goods issue,

for example, movement type 202 or 262, is not

considered as an issue but as a receipt. If we only

use the automatic creation of storage location data

for reversals of goods issues, we do not have to allow

negative stocks.

We have to allow automatic creation per plant first

of all. We then have to explicitly allow the creation of

storage location data for each movement type.

The storage location data is only created if the

quantity is posted to 'standard' storage location stock.

It is not created for receipts into a special stock

(for example, into sales order stock).We are using

standard movement types for automatic Storage

Location Creation

8.10 Set Manual Account Assignment

Menu path 1. Implementation Guidefor R/3 Customizing(IMG) ® MaterialsManagement® InventoryManagement andPhysical Inventory® Goods Issue/Transfer Postings®Set Manual AccountAssignment

Transaction Code OMB6

Configuration

Description

In the R/3 System,

account assignment

is predefined via the

automatic account

determination facility.

When we enter material

movements that are

Page 59: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0059

assigned to a cost

account, we can enter

the account number

manually. In doing so,

we change the account

assignment predefined

as offsetting entry for

inventory posting.

MvT Acct MvT Acct

201 309 -

202 310 -

292 311 -

301 - 312 -

302 - 313 -

303 - 314 -

304 - 317 -

8.11 Define Screen Layout

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsIssue/Transfer Postings® Define Screen Layout

Transaction Code OMBW

Configuration DescriptionIn this step, we set the field selection for the

movement types including goods issues and transfer

postings.

When creating a goods movement, the field selection

determines which fields• can be filled ( optional entry)• must be filled (required entry)• are suppressed fields

In Inventory Management, the field selection depends

on the movement type.

Page 60: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0060

The field selection defined for a movement type is

valid for entering goods movements and reservations.

Note

We do not maintain the input features of the G/L

account and Reason fields here, but in the following

steps:• Manual account assignment (for the G/L account

field)• Reason (for the Reason field)

Caution

The field selection for the movement type must

correspond with the following field selections:• field status definition of the G/L account to which

postings are made (through the field status group)• field selection of the posting key

We must take care that a mandatory entry in the G/L

account is also defined as a mandatory entry for the

movement type.

8.12 Maintain Copy Rules for Reference Documents

Menu path 1. Implementation Guide for R/3Customizing (IMG) ® MaterialsManagement ® InventoryManagement and PhysicalInventory ® Goods Issue/Transfer Postings® MaintainCopy Rules for ReferenceDocuments

Transaction Code SPRO

Configuration DescriptionIn this step, we configure whether

the items of the reference

document are proposed as

selected on the item selection list

when entering a document with

reference, or not.

The user can delete the check

marks manually on the item

Page 61: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0061

selection list if she/he does not

want to adopt some items.

TCode Transaction

text

Prsl

MB11 Goods

Movement

X

MB1A Goods

Withdrawal

X

MB1B Transfer

Posting

X

8.13 Set up Dynamic Availability Check

Menu path 1. ImplementationGuidefor R/3Customizing(IMG) ®MaterialsManagement®InventoryManagementandPhysicalInventory® GoodsIssue/TransferPostings® SetupDynamicAvailabilityCheck

Transaction

Code

OMCP

Configuration

Description

In this

step, we

configure

Page 62: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0062

the dynamic

availability

check.

In Inventory

Management,

two types of

availability

check are

carried out.• availability

checkduringtheentry ofreservations

• availabilitycheckduringthe entryof goodsmovements

The system

checks

whether

the material

to be

withdrawn

is available

and

issues a

message, if

necessary.

The

availability

check is

only carried

out if:• the

materialmasterrecordcontainsa

Page 63: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0063

checkinggroupfor theavailabilitycheck(MRPdata)

• acheckingrule isassignedto thetransactioninCustomizing

We can

define• for each

movementtypewhichtype ofmessageis issued(objectMovementtype)

• whichcheckingrules aresupported(objectCheckingrule)

• percheckinggroupandcheckingrule:whichobjects(documents,stocks,materialrequirements)areincludedin theavailabilitycheck

Page 64: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0064

(objectDefinecheckingrule)

• pertransactionofInventoryManagement:whichcheckingruleapplies(objectTransactioncodes)

MvT1. Val.

update

Qty

update

SMvtRecCnsAv

201 P

201 X A

201 XK A

201 XP

201X

201XX A

201XXK A

201XXP

202 P

202 XP

202X

202XX

202XXK

202XXP

221 Q A

221 Q PA

221 QL A

Page 65: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0065

221 QL PA

221 X A

221 XK A

221 XQ A

221 XQ PA

This is an

indicative

table.

Checking

Rule

ChRDescription

of

checking

rule

01Checking

rule

01

02Checking

rule

02

03Checking

rule

03

ASD

order

AESD

order;

make-

to-

order

stock

AQSD

order;

Page 66: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0066

project

stock

AVSD

order;

returnable

packaging

AWSD

order;

consignment

BSD

delivery

BBSD

delivery;

customer

stock

BESD

delivery;

make-

to-

order

stock

BOBackorder

processing

BQSD

delivery;

project

stock

BVSD

delivery;

returnable

packaging

BWSD

delivery;

consignment

Define

Checking

Rule

Page 67: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0067

Transaction

Codes

TCodeTransaction

text

ChRChecking

rule

CO27Picking

list

MB11Goods

Movement

MB1AGoods

Withdrawal

03Checking

rule

03

MB1BTransfer

Posting

MB26Picking

list

MIGO_GIGoods

Movement

MIGO_TRTransfer

Posting

8.14 Generate Physical Inventory Documents for

Goods Movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsIssue/Transfer Postings ®Generate PhysicalInventory Documents for Goods Movements

Transaction Code OMCC

Configuration DescriptionIn this step, we define for each plant and movement

type whether a physical inventory document is

Page 68: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0068

automatically generated when posting a goods

movement.

We can create a physical inventory document in

addition to the material document at the time of a

goods movement. This function is important when

inventory differences are posted from the Warehouse

Management System. These inventory differences

are thereby documented in Inventory Management

with a physical inventory document.

In order to create an inventory document in addition

to a material document for a goods movement, the

following conditions must be met:

In the plant, we must define the transaction/event

type WV for automatically generated physical

inventory documents.

We must define the document number assignment for

this transaction/event type.

Automatic generation of physical inventory

documents must be allowed for the movement type.

MvT Idoc

717 X

718 X

The above list is indicative

8.15 Check Tolerance Limits

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsReceipt ® Set Tolerance Limits

Transaction Code OMC0

Configuration DescriptionIn this step, we set the tolerance limits for goods

receipts.

Page 69: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0069

When processing a goods receipt, the system checks

each item to determine whether the goods receipt

varies from the purchase order or the material master

data.

The different types of variances are defined by

tolerance keys. For each tolerance key, tolerance

limits can be set per company code.

The following variances are checked in Inventory

Management:

• Variance in the purchase order price quantity

(Explanation)

For this variance, two tolerance keys are provided:• • Tolerance key B1 (error message)

• We use tolerance key B1 to define themaximum percentage variance. If the varianceis greater than the maximum variance, thesystem creates an error message. The usercannot post the goods receipt.

• Tolerance key B2 (warning message)• Tolerance key B2 defines the percentage

variance from which a warning message isto be issued. It is possible to post the goodsreceipt.

• Variance for the moving average price of thematerial

(Explanation)We use tolerance key VP to define the percentage

variance from which a warning message is issued.

This warning message indicates a price change.

8.16 Create Storage Locations Automatically

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ®Goods Receipt ® Create Storage LocationsAutomatically

Transaction Code OMB3

Page 70: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0070

Configuration DescriptionIn this step, we specify whether the automatic

creation of storage location data is allowed for goods

receipts.

This is advisable if we want to post a goods receipt

without having to maintain the storage location view

of the material master record in advance.

We have to allow automatic creation per plant first

of all. We then have to explicitly allow the creation of

storage location data for each movement type.

The storage location data is only created if the

quantity is posted to 'standard' storage location stock.

It is not created for receipts into a special stock (for

example, into sales order stock).

8.17 Set Manual Account Assignment

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsReceipt ® Set Manual Account Assignment

Transaction Code OMCH

Configuration DescriptionIn the R/3 System, account assignment is predefined

via the automatic account determination facility.

When we enter goods receipts which are assigned to

a cost account, we can enter the account manually.

In doing so, we change the account assignment

predefined as offsetting entry for inventory posting.

8.18 Define Screen Layout

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsReceipt ® Define Screen Layout

Transaction Code OMCJ

In this step, we set the field selection for the goods

receipt movement types.

Page 71: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0071

Configuration Description

When entering a goods receipt, the field selection

controls which fields (account assignment fields) are• ready for input ( optional entry fields)• have to be filled (required entry fields)• suppressed fields

In Inventory Management, the field selection depends

on the movement type.

8.19 Maintain Copy Rules for Reference Documents

Menu path 1. Implementation Guide for R/3Customizing (IMG) ® MaterialsManagement ® InventoryManagement and PhysicalInventory ® Goods Receipt ® Maintain Copy Rules forReference Documents

Transaction Code SPRO

Configuration DescriptionIn this step, we configure whether

the items of the reference

document are proposed as

selected on the item selection list

when entering a document with

reference, or not.

The user can delete the check

marks manually on the item

selection list if she/he does not

want to adopt some items.

TCode Transaction

text

Prsl

MB01 Post

Goods

Receipt

for PO

X

MB0A Post

Goods

X

Page 72: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0072

Receipt

for PO

MB1C Other

Goods

Receipts

X

MB31 Goods

Receipt

for

Production

Order

X

MBRL Return

Delivery

for Matl

Document

X

MBSF Release

Blocked

Stock via

Mat. Doc.

X

MBSL Copy

Material

Document

X

MBST Cancel

Material

Document

X

8.20 Set Dynamic Availability Check

Menu path 1. ImplementationGuidefor R/3Customizing(IMG) ®MaterialsManagement®InventoryManagementandPhysicalInventory® GoodsReceipt ® Set

Page 73: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0073

DynamicAvailabilityCheck

Transaction

Code

OMCM

Configuration

Description

In this

step, we

configure

the dynamic

availability

check.

In Inventory

Management,

two types of

availability

check are

carried out.• availability

checkduringtheentry ofreservations

• availabilitycheckduringthe entryof goodsmovements

The systemcheckswhetherthe materialto bewithdrawnis availableandissues amessage, ifnecessary.

Movement

Type

Page 74: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0074

MvT1. Val.updateQty

update

SMvtRecCnsAv

101 XQB V

101 XQBX

101 XQBXP

101 XQF

101 XQF P

101X B

101X B A

101X B V

101X BX

101X BXA

101X BXV

101XX B

101XX B A

Checking

Rule

ChRDescription

of

checking

rule

01Checking

rule

01

02Checking

rule

02

03Checking

rule

03

ASD

order

Page 75: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0075

AESD

order;

make-

to-

order

stock

AQSD

order;

project

stock

AVSD

order;

returnable

packaging

AWSD

order;

consignment

BSD

delivery

BBSD

delivery;

customer

stock

BESD

delivery;

make-

to-

order

stock

BOBackorder

processing

BQSD

delivery;

project

stock

BVSD

delivery;

Page 76: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0076

returnable

packaging

BWSD

delivery;

consignment

Transaction

Code

TCodeTransaction

text

ChRChecking

rule

MB01Post

Goods

Receipt

for

PO

MB0APost

Goods

Receipt

for

PO

MB1COther

Goods

Receipts

03Checking

rule

03

MB31Goods

Receipt

for

Production

Order

03Checking

rule

03

MBNLSubsequent

Delivery

f.

Material

Doc.

03Checking

rule

03

MBRLReturn

Delivery

for

Matl

Document

Page 77: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0077

MBSFRelease

Blocked

Stock

via

Mat.

Doc.

MBSLCopy

Material

Document

03Checking

rule

03

MBSTCancel

Material

Document

MIGO_GOGoods

Movement

MIGO_GRGoods

Movement

8.21       Set “Delivery Completed” IndicatorMenu path 1. Implementation Guide for R/3 Customizing

(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsReceipt ® Set “Delivery Completed”Indicator

Transaction Code SPRO

Configuration DescriptionIn this step, we can define that the R/3 System

automatically suggests• the delivery completed indicator for goods receipts

if the delivered quantity lies within the under/over-delivery tolerance

The "delivery completed" indicator has the following

effects:• The item is regarded as closed, even if the total

quantity was not delivered.• A further delivery is not expected, may, however,

arrive.

Page 78: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0078

• In the next goods receipt, the item appears on theselection list but has no selection indicator.

• The item can be reorganized even if the totalquantity has not been delivered.

Note

Even if the "delivery completed" indicator has not

been set, an item is considered closed once the total

quantity has been delivered. This means that the

"delivery completed" indicator is not necessary in this

case.

8.22 Set Expiration Date Check

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® GoodsReceipt ® Set Expiration Date Check

Transaction Code OMJ5

Configuration DescriptionIn this step, we set the material shelf life expiration

date check for goods receipts for each plant and

movement type.

Prerequisites

The shelf life expiration date of a material can only be

entered if:• the minimum remaining shelf life is maintained in

the material master record• The minimum remaining shelf life is the time

the material must still be usable, so that thegoods receipt is accepted by the system.We can define the time unit the system usesin the storage data of the material masterrecord in the ‘Period indicator’ field.

• the shelf life expiration date check is active in theplant

• the shelf life expiration date check is active for themovement type

No expiration date check has been activated for ITZ.

Page 79: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0079

8.23 Create Storage Location automatically for

automatic movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® AutomaticMovements ® Create Storage Locationsautomatically

Transaction Code OMJ8

Configuration DescriptionIn this step, we specify whether the automatic

creation of storage location data is allowed for

automatic goods movements.

This is advisable for goods movements via Shipping

or when we post physical inventory differences, for

example.

We have to allow automatic creation per plant first

of all. We then have to explicitly allow the creation of

storage location data for each movement type.

The storage location data is only created if the

quantity is posted to 'standard' storage location stock.

It is not created for receipts into a special stock (for

example, into sales order stock).

8.24 Set manual account assignment for automatic

movements

Menu path 1. Implementation Guidefor R/3 Customizing(IMG) ® MaterialsManagement® InventoryManagement andPhysical Inventory ®Automatic Movements® Set manualaccount assignment

Page 80: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0080

for automaticmovements

Transaction Code OMJ9

Configuration

Description

Maintenance of this

indicator is only useful

in conjunction with

movements for which

a G/L account can be

entered or is provided by

the calling program.

In the R/3 System,

account assignment

is predefined via the

automatic account

determination facility.

When we enter material

movements that are

assigned to a cost

account, we can enter

the account number

manually. In doing so,

we change the account

assignment predefined

as offsetting entry for

inventory posting.

MvT Acct MvT Acct

121 601

131 602

132 603 -

340 - 604 -

341 - 621 -

342 - 622 -

543 - 623 -

544 - 624 -

545 - 631 -

Page 81: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0081

546 - 632 -

8.25 Define Screen Layout for automatic movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® AutomaticMovements ® Define Screen Layout

Transaction Code OMJA

Configuration DescriptionIn this step, we set the screen Layout for automatic

movement types.

8.26 Generate Physical Inventory Documents for

Goods Movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® AutomaticMovements ® Generate Physical InventoryDocuments for Goods Movements

Transaction Code OMJC

Configuration DescriptionIn this step, we define for each plant and movement

type whether a physical inventory document is

created automatically when a goods movement is

posted.

In conjunction with automatic movements, please

also note that this indicator is not set for goods

movements which are created from within a physical

inventory since, in this case, the physical inventory

document already exists. This applies to movement

types 701 to 708.

8.27 Define Default Values for Reservations

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ®Reservations ® Define Default Values

Page 82: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0082

Transaction Code OMBN

Configuration DescriptionIn this step, we specify the default values for the

following functions for each plant:• allow goods movements for reservations• delete reservations• create storage-location stock data automatically

for reservations

Allow movements for reservations

We can only post a goods movement with reference

to a reservation if the Movement allowed indicator is

set in the reservation item.

We are not using Reservations for ITZ.

Delete reservations

The management program sets the deletion indicator

for reservation items whose requirements date is

earlier than the number of days specified here.

Create storage-location stock data automatically for

reservations

When this indicator is set, the storage-location stock

data is automatically created when a reservation

is posted. This applies both to planned outward

movements and planned receipts.

8.28 Maintain Copy Rules for Reference Documents

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ®Reservations ® Define Default Values

Transaction Code SPRO

Configuration DescriptionIn this step, we configure whether the items of the

reference document are proposed as selected on

the item selection list when entering a document with

reference, or not.

Page 83: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0083

The user can delete the check marks manually on the

item selection list if she/he does not want to adopt

some items

8.29 Set Dynamic Availability Check for Reservations

Menu path 1. Implementation Guidefor R/3 Customizing(IMG) ® MaterialsManagement® InventoryManagement andPhysical Inventory ®Reservations ® SetDynamic AvailabilityCheck

Transaction Code OMB1

Configuration

Description

In this step, we configure

the dynamic availability

check.

In Inventory

Management, two types

of availability check are

carried out.• availability check

during the entry ofreservations

• availability checkduring the entry ofgoods movements

The system checks

whether the material to

be withdrawn is available

and issues a message, if

necessary.

TCodeTransaction

text

ChR Checking

rule

Page 84: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0084

MB21 Create

Reservation

03 Checking

rule

03

MB22 Change

Reservation

03 Checking

rule

03

8.30 Default Values for Physical Inventory

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® PhysicalInventory ® Default Values for PhysicalInventory

Transaction Code SPRO

Configuration DescriptionIn this step, we specify the following default values for

physical inventory for each plant:

Pre-settings for entering physical inventory

documents• the stock type (unrestricted-use, in quality

inspection, blocked)• the indicator for batch determination (in the

foreground or in the background)• the unit of entry (stock keeping unit or unit of

issue)

These indicators are suggested as default valueswhen we enter a physical inventory document. But wecan also change them there.

Pre-settings for entering physical inventory

documents• Reason for inventory difference• The default value we specify here is only

displayed when we enter an inventory differencewithout reference to the corresponding document.But we can also change the default value here.

Note:

We only see this field when we enter inventory

differences if we have activated it in the step Field

selection for physical inventory.

Page 85: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0085

8.31 Record Reasons for Goods Movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® MovementTypes ® Record Reasons for GoodsMovements

Transaction Code OMBS

Configuration DescriptionIn this step, we can carry out the following for each

movement type:• maintain the input status of the Reason field• store a key that gives a reason for the movement

(for example, reason for return delivery) and acorresponding text.

When we enter a goods movement, we can only enter

reasons which have been defined for the movement

type here.

8.32 Copy, Change Movement Types

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ® MovementTypes ® Copy, Change Movement Types

Transaction Code OMJJ

Configuration DescriptionIn this step, we can• change the setting of existing movement types• define new movement types

When we enter a goods movement, we must always

enter the movement type. The movement type has

important control functions in Inventory Management.

It is essential for• updating the quantity fields• updating the stock and consumption accounts• selection of the fields used for entering documents• printing goods receipt/issue slips

Page 86: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0086

9 Materials Management – Valuationand Account Assignment

9.1 Split Valuation

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® Valuation andAccount Assignment ® Split Valuation ® ActivateSplit Valuation

Transaction Code OMW0

Configuration DescriptionYou configure whether split valuation is allowed at

your company. If you generally allow split valuation,

this does not mean that you must valuate each

material on this basis. You decide whether to do so or

not for a particular material when creating the material

master record.

9.2 Configure Split Valuation

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® Valuationand Account Assignment ® Split Valuation ®Configure Split Valuation

Transaction Code OMWC

Configuration DescriptionIn split valuation, we can distinguish between partial

stocks of a material according to certain criteria and

valuate them separately.• The material stock is divided according to

valuation category and valuation type:• The valuation category determines how the partial

stocks are divided, that is, according to whichcriteria.

• The valuation type describes the characteristics ofthe individual stocks.

• With the function "Setting" we can determine:• which valuation categories exist in our

company (global categories)

Page 87: MM – Configuration Documentation

SAP MM Configuration

Generated by Jive on 2016-01-08+01:0087

• which valuation types exist in our company(global types)

• which valuation types belong to which valuationcategory

• which valuation categories exist in a valuationarea (local categories)

To select split valuation, proceed as follows:1. 1. Determine the valuation categories and

valuation types that are allowed for all valuationareas:

• • Global valuation categories via menu "Goto -->Global Categories"

• Global valuation types via menu "Goto -->Global Types"

1. 2. Allocate the valuation types to the valuationcategories.

a) Select "Goto --> Global Categories".

b) Position the cursor on a valuation category and

select "Goto --> Global Categories --> Allocations -->

Types->Category".

c) Activate the valuation types you want.

1. 3. Determine the local valuation categories for

each valuation area.

a) Select "Goto --> Local definitions".

b) Position the cursor on a valuation area and select

"Goto --> Local Definitions --> Allocate Categories-

>Org.units". You obtain a list of the global valuation

categories.

c) Activate the categories to be used in this valuation

area.

The system creates the local valuation types based

on the allocations under point 2.