sap mm configuration - scn

Getting Started Newsletters Store

Products Serv ices & Support About SCN Downloads

Industries Training & Education Partnership Dev eloper Center

Lines of Business Univ ersity Alliances Ev ents & Webinars Innov ation

Log On Join UsHi, Guest

Activ ity Communications Actions

Browse

11 TweetTweet 4

created by Prasanna Soundar on Mar 5, 2013 5:04 AM, last modified by Prasanna Soundar on Aug 22, 2014 10:13 AM

MM – Conf iguration Documentation

2 Enterprise Structure - Def inition

2.1 Define Valuation Level

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Enterprise Structure ®

Def inition ® Logistics general ® Define Valuation Level

I.

Transaction Code OX14

Configuration

Description

Here we specif y the lev el at which material stocks are v aluated. We hav e used

the Plant lev el since the application component Production Planning (PP) and

Costing are being used.

Depending on the v aluation lev el chosen, accounting data (in particular the

v aluation price) is maintained f or each plant or f or each company code in

the material master record.

If material stocks are v aluated at company code lev el, all plant stocks of

a material are managed in a joint stock account f or each company code.

If material stocks are v aluated at plant lev el, the material stocks f or each

plant can be managed in dif f erent accounts. We can def ine a separate

account determination f or each plant.

2.2 Define Plant


Def inition ® Logistics general ® Define, copy, delete, check plant

I.

Transaction Code SPRO

Configuration

Description

As a part of the Logistics Organizational Structure, Plants are def ined in SAP.

The ‘Plant’ is an operating area or a branch or a location within a company. Each

'Plant' is assigned to a single 'company code'. A 'company code' can hav e

sev eral 'Plants'. In case of ITZ Pv t. Ltd., the v arious 'Plants' are assigned to

each 'company code'.

Conf iguration of One Plant is depicted here, (f or list of all please ref er to MM

KDS Document)

2.3 Maintain Storage Location

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Enterprise Structure ®I.

SAP MM Configuration

ShareShare 14 33LikeLike

Version 3

SAP MM Configuration | SCN http://scn.sap.com/docs/DOC-38642

1 of 39 09-03-2015 17:54

Def inition ® Materials Management ® Maintain Storage Location

Transaction Code OX09

Configuration

Description

A storage location is the place where stock is phy sically kept within a plant.

There may be one or more storage locations within a plant.

A storage location has the f ollowing attributes:

A storage location has a description and at least one address.

It is possible to store material data specif ic to a storage location.

Stocks are managed only on a quantity basis and not on a v alue basis at

storage location lev el.

Phy sical inv entories are carried out at storage location lev el.

Conf iguration of Storage Locations under One Plant is depicted here, (f or list of

all please ref er to MM KDS Document)

2.4 Maintain purchasing organization


Def inition ® Materials Management à Maintain Purchasing Organization

I.


Configuration

Description

At this node we conf igure the Purchasing Organization .The purchasing

organization is the highest lev el of aggregation (af ter the organizational unit

"client") f or purchasing statistics.

In case of ITZ One single Purchase Organization is created as under :

3 Enterprise Structure Assignments3.1 Assign Plant to Company Code


Assignment ® Logistics general ® Assign Plant to Company Code

I.


Configuration

Description

A Plant needs to be assigned to one of the Company Codes, the relation is

alway s one to one i.e. One Plant can be assigned to only one company code

All the plants can’t be shown here(f or complete list ref er MM KDS document)

3.2 Assign purchasing organization to company code


Assignment ® Logistics general ® Assign purchasing organization to

company code

I.


Configuration

Description

In 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


Assignment ® Logistics general ® Assign purchasing organization to

Plant

I.


Configuration

Description

In this step we assign purchasing organizations to the plants f or which they are

responsible.

In case of ITZ since it operates with Centralized Purchasing Org. we hav e

assigned the Purchasing Org. to all the plants def ined as of now

3.4 Assign standard purchasing organization to plant


Assignment ® Logistics general ® Assign standard purchasing

organization to plant

I.


Configuration

Description

If sev eral purchasing organisations procure f or a certain plant, we can def ine

one of them as the standard purchasing organization f or the transactions

"pipeline procurement", "consignment" and "stock transf ers".

In source determination f or stock transf ers and consignent, the sy stem

automatically utilizes this standard purchasing organization. In the case of goods


2 of 39 09-03-2015 17:54

issues of pipeline materials, the purchasing inf o records of the standard

purchasing organization are read.

In ITZ, we hav e not def ined this Setting as we are using single Purchasing

Organisation

4 General Logistics 4.1 Assign Fields to Fields Selection Groups

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Logistics - General à

Material Master à Field Selectionà Assign Fields to Fields Selection

Groups

I.

Transaction Code OMSR

Configuration

Description

Assignment of Material Master Fields is required to def ine whether a f ield is

hidden or display ed, or whether an entry is mandatory or optional in material

master maintenance, it is alway s adv isable to work with Standard SAP settings,

but f or f ew business requirement some assignments are changed to new f ield

selection groups def ined as per reserv ed name space. in case of ITZ, some of

the list of changed entries is as giv en below:

Field Name Description Changed Field

Grp

MVKE-MVGR1 Material group 1 211



4.2 Maintain Field Selection for Data Screens


Material Master à Field Selectionà Maintain Field Selection for Data

Screens

I.

Transaction Code OMS9

Configuration

Description

In this step we def ine the nature of a Field belonging to a particular Field

Selection Group wrt the Screen Ref erence of a Material Ty pe. Steps inv olv ed

are :

Selecting the f ield selection group.

Select the f ield selection option (hide, display, required entry, or Optional

entry ) f or each f ield ref erence as required.

4.3 Maintain Company Codes for Materials Management


Material Master à Basic Settingsà Maintain Company Codes for

Materials Management

I.

Transaction Code OMSY

Configuration

Description

This activ ity is done f or making a Company Code relev ant f or materials

Management and to def ine the starting posting period This is a prerequisite f or

creating a Material Master

4.4 Define Attributes of Material Types

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Logistics - General à Material

Master à Basic Settingsà Material Ty pesà Define Attributes of Material Types

I.

Transaction Code OMS2

Configuration

Description

Material 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. Number range pattern and nature (external/internal)1.

2. Hide/optional fields in the material master2.

3. Valuation Control at valuation area level (ultimately used to derive

G/L)

3.

4. Control on Production/Purchase4.

4.5 Define Number Ranges for each material types


Material Master à Basic Settingsà Material Ty pesà Define Number Ranges

for each Material Types

I.


3 of 39 09-03-2015 17:54

Transaction Code MMNR

Configuration

Description

In this step, we hav e def ined the ty pe of number assignment and the number

range interv als f or material master records. When creating a material master

record, sy stem must assign it a unique number. There are two way s of doing

this:

internal number assignment

In this case, a number within the number range interv al allowed is

assigned by the SAP sy stem.

external number assignment

Here, the user assigns a number within the number range interv al allowed. We

can def ine the interv als f or external number assignment numerically and

alphanumerically.

We hav e def ined the number range interv als f or so-called groups. We assign

one or more material ty pes to each group.

If we assign just one material ty pe to a group, we can def ine both an

internal and an external number range interv al f or the material ty pe.

If we group together more than one material ty pe, we can def ine an internal

and an external number range interv al here too. This allows sev eral material

ty pes to hav e the same number range interv als.

4.6 Define Attributes of system messages


Material Master à Basic Settingsà Define Attributes of system messages

I.

Transaction Code OMT4

Configuration

Description

When processing material master records, the sy stem issues a number of

sy stem messages containing important user inf ormation. In this activ ity, we

def ine how the SAP sy stem handles these messages. We hav e the f ollowing

options:

The message can be suppressed.

The message can be display ed as a warning.

The message can be display ed as an error message. (can’t be surpassed)

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

message

We are using Standard SAP Messages.

4.7 Define Material Groups


Material Master à Settings f or Key Fieldsà Define Material Groups

I.

Transaction Code OMSF

Configuration

Description

Here we def ine the Groups f or Materials & Serv ices, This Grouping shall be

def ined keeping in mind the reporting requirement of the company f or analy sing

Purchases, Consumptions, Stocks etc,

Setting is just a table entry, f ew records are shown in the screen shot, f or

complete list ref er to the MM KDS document or the actual sy stem node

4.8 Define External Material Groups


Material Master à Settings f or Key Fieldsà Define External Material

Groups

I.


Configuration

Description

Here we def ine the Groups f or giv ing an extra key f or f iltering, sorting the list of

materials f rom a criterion other than Material grouping

In case of ITZ we hav e not used External Material Groups

4.9 Initialize Period


Material Master à Toolsà Initialize Period

I.

Transaction Code MMPI

Configuration

Description

This 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 bef ore initialization


4 of 39 09-03-2015 17:54

5 Materials Management – Consumption basedPlanning5.1 Activate MRP for MRP Areas

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Materials Management

à Consumption-based Planning à Master Data à MRP Areas àActivate MRP

for MRP Areas

I.


Configuration

Description

This setting is required if we want to hav e planning at a lev el other than plants

i.e. either of Storage location / at Subcontractor lev el.

An MRP area represents an organizational unit f or which we can perf orm material

requirements planning separately.

An MRP area can include one or sev eral storage locations of a plant or a

subcontractor. We can def ine MRP areas in a plant.

For ITZ Ltd., we hav e not used MRP Areas.

5.2 Define MRP Areas


à Consumption-based Planning à Master Data à MRP Areas àDefine MRP

Areas

I.

Transaction Code SCAL

Configuration

Description

Here we def ine the MRP areas f or a plant f or which we would like to carry out

material requirements planning separately.

When creating an MRP area, we enter the number, which must hav e at least 5

digits to av oid any ov erlapping with the plant MRP area, the description and the

MRP area ty pe

In case of ITZ we hav e not def ined MRP area

Important : If MRP area is activ ated Conv ersion of Planning f ile entries needs

to be run in ev ery new Sy stem Client through Report RMDBVM00 in Txn : SE38

The conv ersion report causes the sy stem to create a new planning f ile. In

addition, the sy stem creates MRP area f or the existing plants. These MRP areas

do not, howev er, af f ect the way material requirements planning is carried out.

The number f or plant MRP areas is identical to the plant number and theref ore

consists of f our digits.

The conv ersion of the current planning f ile (table MDVM) to the new planning f ile

(table DBVM) is a prerequisite f or carry ing out material requirements planning

with MRP areas.

6 Materials Management – Purchasing6.1 Define Attributes of System Messages


à Purchasing à Env ironment Data à Define Attributes of System

Messages

I.


Configuration

Description

In Purchasing, certain sy stem messages containing important inf ormation f or

users may be issued f rom time to time

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

Suppresses the relev ant inf ormation

Issues it as a warning message

Issues it as an error message

In the case of an error message, processing cannot be continued until user input

has been corrected

For ITZ requirement, messages (as a change f rom standard) are conf igured as

giv en below:

6.2 Define Purchasing Value Keys


à Purchasing à Material Master à Define Purchasing Value Keys

I.


Configuration

Description

With Purchasing v alue key we can control f ollowing f unctions by using it in the

material master purchasing v iew, purchasing v alue key gov erns:

The issue of reminders and urging letters (expediters) with respect to nearly

due and ov erdue deliv eries

The admissibility of ov er- and under deliv eries ("ov erages" and "under


5 of 39 09-03-2015 17:54

ages")

Order acknowledgment requirements f or PO items

Shipping/packaging instructions

This data appears as def ault data in purchasing documents and is taken f rom the

material master record (unless a purchasing inf o record exists, in which case it is

taken f rom the inf o records).

6.3 Entry Aids for Items without a Material Master


à Purchasing à Material Master à Entry Aids for Items Without a Material

Master

I.


Configuration

Description

In this step we assign In this step, we can assign a purchasing v alue key and a

v aluation class to a material group.

The assignment of a purchasing v alue key def ault v alues f or reminder

lev els etc. in purchase order items without a material master record and

without an inf o record.

The assignment of a v aluation class to a material group enables the

sy stem to determine dif f erent accounts f or the indiv idual material

groups.

For ITZ we hav e maintained Valuation Classes in the accounting v iew of the

materials.

6.4 Create Purchasing Groups


à Purchasing à Create Purchasing Groups

I.


Configuration

Description

It’s a key for a buyer or group of buyers responsible for certain purchasing

activities. useful in accessing information, controll ing authorizations,

setting up release strategies etc. for ITZ ‘s Requirement following groups

are configured, configuration is a simple table entry but purchasing

group has a comprehensive use in all purchasing transactions/

documents

6.5 Define Document Types (RFQ/Quotation)

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Materials Management à

Purchasing à RFQ/Quotation à Define Document Types

I.


Configuration

Description

SAP manages RFQs and quotations as documents which are grouped into dif f erent

document ty pes., in this step we hav e :

Created new document ty pes

Def ined item interv al

Def ined admissible f ollow-on document ty pes

Assigned document ty pes to a number range group

Def ined number range interv al

Chosen

internal

external

Chosen

The update group determines how the data f rom the document header is

updated in the statistics f ile.

Linkage determines which PR document ty pes can be ref erenced f or creating a

particular RFQ document ty pe

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


à Purchasing àRFQ /Quotations à Define Text Types for Header Texts

I.


Configuration

Description

In this step we define different Texts which appear in RFQ/Quotation

Headers, which are used to store information applicable for a particular

RFQ document


6 of 39 09-03-2015 17:54

We hav e standard Header Text Ty pes.

6.7 Define copying rules for Header Texts (RFQ/Quotations)


à Purchasing àRFQ /Quotations à Define copying rules for Line Texts

(RFQ/Quotations)

I.


Configuration

Description

In this step we define copying rules for different header Texts which

appear in RFQ/Quotation Line ItemsCopy ing rules are used to determine which texts can be adapted f rom other

objects (f or example, v endor master records, contracts) to the header text of

the RFQ. We link text ty pes in the RFQ with text ty pes in other objects. Sy stem

can adopt header texts f rom the f ollowing objects:

RFQ / Quotation

Contract

Scheduling agreement

Vendor master

We can also specif y whether the adopted text can be edited in the destination

document or not. This ty pe of setting is more usef ul in PO Header Texts

6.8 Define document types (Purchase Requisitions)


à Purchasing à Purchase Requisitions à Define document types

(Purchase Requisitions)

I.


Configuration

Description

SAP manages Purchase Requisitions as documents which are grouped into

v arious document ty pes., in this step we hav e :






Chosen

internal

external

Chosen



Abov e linkage gov erns which ty pe of PO can be created using PR of a

particular ty pe

6.9 Release Procedure with Classification (Purchase Requisitions)


à Purchasing à Purchase Requisitions à Release Procedure àProcedure

with Classif ication à Set Up Procedure with Classification

I.


Configuration

Description

In this step, we hav e set up the release procedure with classif ication.

Purchase Requisition release is the process in which Purchase Requisition is

approv ed and released by HOD of concern department f or request of required

material or serv ices specif ied in Purchase Requisition. Once the Purchase

Requisition is approv ed and released then Purchase Order or RFQ will be created

f or that material or serv ices against same Purchase Requisition.

Conf iguration inv olv es f ollowing elements in sequence:

Release Group:

Specif y f or the release group either "ov erall release" or "item-wise release"

Release codes:

The Release Code is a two-character ID allowing a person to release (approv e) a

requisition.(analogous to approv er code)

Release Indicators:

A release indicator shows the release status of a purchase requisition


7 of 39 09-03-2015 17:54

Release Indicators also inv olv e:

Field selection key

v ia the f ield selection key, we can specif y which f ields 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 specif y the ef f ects of changes to

a requisition. For example, certain changes may require a new release

strategy to be determined f or the requisition.

Via the Value change f ield, we can cause the release strategy to be

re-started if the v alue of a purchase requisition item is increased by more

than a certain percentage (e.g. 10%). To do so, set the Changeability

indicator to "4 - Changeable, new release in case of new strategy or v alue

change" and enter a percentage in the Value change f ield.

Release Strategy

The Release Strategy defines the approval process for Purchase

Requisitions. The strategy specifies the release codes which are

necessary and the sequence in which releases have to be affected. We

can define a maximum of eight release codes i.e. 8 Levels of approval.

Release Prerequisites indicate the sequence in which a Purchase

Requisition must be approved via the release codes. (In ITZ case release

is parallel(either / or so indicators are kept blank) Release Status indicates the af f ect af ter the release by a particular release

code

Release Values

These v alues need to be maintained in ev ery client manually, this f orms the

basis on which release strategy is triggered f or a PR.

An important prerequisite f or this is to create Class & Characteristics in class

ty pe 032

Characteristics for Release Strategy

Create the Characteristics required f or release strategy as master data thru

transaction CT04, here the most important setting is to attach the characteristics

to corresponding f ield of structure CEBAN

attach it to the structure

Class for Release Strategy

Create the class as master data thru transaction CL02

and attach the Characteristics created earlier to the class

6.10 Define Number Ranges (Purchase Orders)


à Purchasing àPurchase order à Define Number Ranges

I.

Transaction Code OMH6

Configuration

Description

In 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 way s of doing this:

internal number assignment

In this case, a number within the number range interv al allowed is

assigned by the SAP sy stem.

external number assignment

Here, the user assigns a number within the number range interv al allowed. We

can def ine the interv als f or external number assignment numerically and

alphanumerically.

In case of ITZ all the documents are assigned with internal number ranges with

the exception f or document ty pe “Legacy Open P.O”, as it was required to retain

the legacy P.O number f or this case.

go in change mode and def ine the interv als as shown:


8 of 39 09-03-2015 17:54

6.11 Define Document types (Purchase Orders)


à Purchasing àPurchase Orders à Define document types

I.


Configuration

Description

SAP manages Purchase Orders as documents which are grouped into v arious

document ty pes., in this step we hav e :



Def ine allowable item categories




Chosen

internal

external

Chosen



Abov e linkage gov erns which ty pe of PR can be ref erenced created while

creating a particular Contract document ty pe

6.12 Set Tolerance Limits for Price Variance


à Purchasing àPurchase order à Set Tolerance Limits for Price Variance

I.


Configuration

Description

When processing a purchase order, the sy stem checks whether the ef f ectiv e

price of a PO item shows v ariances compared with the v aluation price stored in

the material master record. In addition, it checks whether the specif ied cash

discount v alue is admissible.

Variances are allowed within the tolerance limits. If a v ariance exceeds a

tolerance limit, the sy stem issues a warning or error message. In SAP, the ty pes

of v ariance are represented by the tolerance key s. For each tolerance key, we

can def ine percentage and v alue-dependent upper and lower limits per company

code.

PE Price v ariance, Purchasing

Tolerance limit f or sy stem message no. 207. This message appears if

the specif ied ef f ectiv e price exceeds the predef ined tolerances when

compared with the material price.

SE Maximum cash discount deduction, Purchasing

Tolerance limit f or sy stem message no. 231. This is a warning

message, which appears when the specif ied cash discount percentage

exceeds the predef ined tolerances.

6.13 Release Procedure for Purchase Orders


Purchasing àPurchase Order à Release Procedure for Purchase Orders

I.


Configuration

Description

In this step, we hav e set up the release procedure f or Purchase Orders(this also

cov ers the process f or other external purchasing documents e.g.

contracts/scheduling agreements)

Purchase Order release is the process in which PO is approv ed and released by HOD

of concern department f or request of required material or serv ices specif ied in PO.

Once the Order is approv ed and released then GR can be created against the PO

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

Conf iguration inv olv es f ollowing elements in sequence:

Release Group:

Release groups are created f or each ty pe of purchasing

Release codes:

The Release Code is a two-character ID allowing a person to release (approv e) a

requisition.(analogous to approv er code)

Release Indicators:


9 of 39 09-03-2015 17:54

A release indicator shows the release status of a Purchase Order

Release Indicators also inv olv e:

Changeability Indicator

With the Changeability indicator, we can specif y the ef f ects of changes to a PO

document. For example, certain changes may require a new release strategy to be

determined f or the requisition.

Via the Value change f ield, we can cause the release strategy to be re-started if

the v alue of a purchase order is increased by more than a certain percentage

(e.g. 10%). To do so, set the Changeability indicator to "6 - Changeable, new

release in case of new strategy or v alue change" and enter a percentage in the

Value change f ield.

Release Strategy

The Release Strategy defines the approval process for PO. The strategy

specifies the release codes which are necessary and the sequence in which

releases have to be affected. We can define a maximum of eight release

codes i.e. 8 Levels of approval.

Release Prerequisites indicate the sequence in which a Purchase Requisition

must be approved via the release codes. (In ITZ case release is by a single

authority so there are no prerequisite involved) Release Status indicates the af f ect af ter the release by a particular release code

Release Values

These v alues need to be maintained in ev ery client manually, this f orms the basis on

which release strategy is triggered f or a PO.

An important prerequisite f or this is to create Class & Characteristics in class ty pe

032

Characteristics for Release Strategy

Create the Characteristics required f or release strategy as master data thru

transaction CT04, here the most important setting is to attach the characteristics to

corresponding f ield 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


à Purchasing àPurchase Orders à Define Screen Layout at Document

Level

I.


Configuration

Description

In this step we def ine the attributes of v arious f ields contained in a f ield

selection key (def ined f or a document ty pe) inside which v arious f ields are

grouped into f ields selection groups.Steps inv olv ed in the process are :

Selecting the f ield selection key (def ined f or a document ty pe)

Select the f ield selection option (hide, display, required entry, or Optional

entry ) f or each f ield inside a f ield selection group ref erence as required.

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

get inside a f ield group and choose the attributes

settings can be made similarly f or other f ields in v arious other groups as &

when required

6.15 Define Text Types for Header Texts (Purchase Orders)


à Purchasing àPurchase Order à Define Text Types for Header Texts

I.


Configuration

Description

In this step we define different Texts which appear in Purchase order

header, these are used to store information applicable for a particular

PO document


10 of 39 09-03-2015 17:54

6.16 Define copying rules for Header Texts (Purchase Order)


à Purchasing àPurchase Orders à Define copying rules for Header Texts

I.


Configuration

Description


appear in Purchase Order HeadersCopy ing rules are used to determine which texts can be adapted f rom other

objects (f or example, v endor master records, contracts, RFQ) to the header text

of the Purchase Order. We link text ty pes in the PO with text ty pes in other

objects. Sy stem can adopt header texts f rom the f ollowing objects:

RFQ / Quotation

Contract

Scheduling agreement

Vendor master

Purchase Requisition


document or not. Currently we are not maintaining any copy ing rule f or header

texts

6.17 Define Text Types for Item Texts (Purchase Orders)


Purchasing àPurchase Order à Define Text Types for Item Texts

I.


Configuration

Description

In 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 l ine item

6.18 Define copying rules for Item Texts (Purchase Order)


à Purchasing àPurchase Orders à Define copying rules for Item Texts

I.


Configuration

Description

In this step we define copying rules for different item Texts which

appear in Purchase Order ITEMCopy ing rules are used to determine which texts can be adapted f rom other


of the Purchase Order. We link text ty pes in the PO with text ty pes in other


RFQ / Quotation


Purchase Inf o record

Contract

Material master

We can also specif y here whether the adopted text can be edited in the

destination document or not.

maintain the rules f or a text as under

6.19 Define Document Types (Contracts)


à Purchasing àContracts à Define Document Types

I.

Transaction Code OMH6

Configuration

Description

SAP manages Contracts as documents which are grouped into v arious document

ty pes., in this step we hav e :



Def ine allowable item categories




Chosen

internal

external

Chosen




11 of 39 09-03-2015 17:54

In case of ITZ, use of Contracts and Scheduling agreements is v ery minimal so

we hav e retained and used standard SAP document ty pes

Abov e linkage gov erns which ty pe of PR can be ref erenced created while

creating a particular Contract document ty pe

6.20 Define Screen Layout at Document Level (Contracts)


Purchasing àContracts à Define Screen Layout at Document Level

I.


Configuration

Description

In this step we def ine the attributes of v arious f ields contained in a f ield selection

key (def ined f or a document ty pe) inside which v arious f ields are grouped into

f ields selection groups.Steps inv olv ed in the process are :

Selecting the f ield selection key (def ined f or a document ty pe)

Select the f ield selection option (hide, display, required entry, or Optional entry )

f or each f ield inside a f ield selection group ref erence as required.

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

get inside a f ield group and choose the attributes

settings can be made similarly f or other f ields in v arious other groups as & when

required

6.21 Define Text Types for Header Texts (Contracts)


à Purchasing àContracts à Define Text Types for Header Texts

I.


Configuration

Description

In 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)


à Purchasing àContracts à Define copying rules for Header Texts

I.


Configuration

Description


appear in Contract HeadersCopy ing rules are used to determine which texts can be adapted f rom other

objects (f or example, v endor master records, Contract, RFQ) to the header text

of the Contract. We link text ty pes in the PO with text ty pes in other objects.

Sy stem can adopt header texts f rom the f ollowing objects:

RFQ / Quotation

Contract

Vendor master


document or not.

We are maintaining Standard Text and copy ing Rules f or Header Texts

6.23 Define Text Types for Item Texts (Contracts)


Purchasing àContracts à Define Text Types for Item Texts

I.


Configuration

Description

In this step we define different Texts which appear in Contract item level,

these are used to store information applicable for a particular Contract

document l ine item

6.24 Define copying rules for Item Texts (Contract)


à Purchasing àContracts à Define copying rules for Item Texts

I.


Configuration

Description

In this step we define copying rules for different item Texts which

appear in Contract HeadersCopy ing rules are used to determine which texts can be adapted f rom other


of the Contract. We link text ty pes in the Contract with text ty pes in other


12 of 39 09-03-2015 17:54


RFQ / Quotation


Contract

Purchase Inf o record

Material master

We can also specif y here whether the adopted text can be edited in the

destination document or not.

maintain the rules f or a text as under

6.25 Define External Confirmation Categories


Purchasing àConf irmations à Define External Confirmation Categories

I.


Configuration

Description

Notification 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


Purchasing àConf irmations à Define Internal Confirmation Categories

I.


Configuration

Description

In this step, we assign an external conf irmation category to each internal conf irmation

category.

Internal Categories are for system controls.

6.27 Set Up Confirmation Control


Purchasing àConf irmations à Set Up Confirmation Control

I.


Configuration

Description

In this step, we assign an external conf irmation category to each internal conf irmation

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 wil l get defaulted with qty of last conf. category

6.28 Define Access Sequence


Purchasing àConditionsà Def ine Price Determination Process à Define Access

Sequence

I.


Configuration

Description

Access 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.

E.G.A.

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


Purchasing àConditionsà Def ine Price Determination Process à Define

Condition Types

I.

Transaction Code M/06


13 of 39 09-03-2015 17:54

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


Purchasing àConditionsà Def ine Price Determination Process à Define

Calculation Schema

I.

Transaction Code M/08

Configuration

Description

In 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 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


à Purchasing àConditionsà Def ine Price Determination Process à Define

Schema Group

I.


Configuration

Description

Every 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 :


14 of 39 09-03-2015 17:54

the other part i.e. vendors are assigned with schema group in vendor

master

6.32 Define Schema Determination



Schema determination

I.


Configuration

Description

In 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



Transaction Event keys

I.


Configuration

Description

In 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),

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


à Purchasing àConditionsà Def ine Price Determination Process à Maintain

Condition Table

I.


Configuration

Description

In 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

f ollows:

Enter the name of the table we wish to create.

Note that we can only choose names between 501 and 999. If we make no

entry, the sy stem will automatically assign a consecutiv e number.

Specif y whether we wish to create the table with or without a v alidity

period.

Enter the ty pe of condition table (f or example, transparent table).

Enter a description f or the condition table.

From the list of allowed f ields that are included in the f ield catalog and

which can be extended there, choose the desired f ields f or the condition

table.


15 of 39 09-03-2015 17:54

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


à Purchasing àStatistics àDefine Grid for Quantity Variances

I.


Configuration

Description

For 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 l imits for every purchasing

organization. Five intervals are then available to we for evaluation of

vendors

6.36 Define Grid for Delivery Date Variance


à Purchasing àStatistics àDefine Grid for Delivery date

I.


Configuration

Description

Delivery 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 l imits for every purchasing

organization. Five intervals are then available to we for evaluation of

vendors

6.37 Define Weighing keys


à Purchasing àVendor Ev aluation à Define Weighing keys

I.


Configuration

Description

In 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 reliabil ity."

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.

6.38 Define Criterion (Vendor Evaluation)


à Purchasing àVendor Ev aluation à Define Criterion

I.


Configuration

Description

Here 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 dril ldown to sub criterion

6.39 Define Scope of List (Vendor Evaluation)


à Purchasing àVendor Ev aluation à Define Scope of List

I.



16 of 39 09-03-2015 17:54

Configuration

Description

In this step we def ine v arious ty pes of list, each representing dif f erent main

criteria or the same main criteria in a dif f erent order.

In the standard sy stem, the scope-of -list parameters 'standard' and 'v ersion 1'

are supplied as an example:

The parameter Standard prov ides the user with a ranking list of v endors

by ov erall score. The main criteria are arranged in the order "Price",

"Quality ", "Deliv ery ", "General serv ice/support” and "Externally perf ormed

serv ice/work".

The parameter Version 1 y ields a ranking list of v endors sorted according

to the score f or the main criterion "Price". Then f ollow the ov erall ev aluation

and the main criteria "General serv ice/support", "Quality ", "Deliv ery ", and

"Externally perf ormed serv ice/work".

check the details of l ist inside

6.40 Maintain Purchasing Organization data


à Purchasing àVendor Ev aluation à Maintain Purchasing Organization

data

I.


Configuration

Description

Select a row and displays criterion for Purchasing Organization

Sub criterions for main criterion

Weighing for a Purchasing Org.

We have provided Equal Weighting to the Criteria as we have different

weighing parameters for ITZ

Point scores for a Purchasing Org.

6.41 Define Permissible Partner Roles per Account Group


à Purchasing àPartner Determination à Partner Rolesà Define Permissible

Partner Roles per Account Group

I.


Configuration

Description

Here we can specif y f or each account group of the v endor which roles the

v endor may assume. Example we can specif y that certain v endors may only

serv e as an ordering address, not as an inv oicing party.

6.42 Define Partner Schemas (Vendor Master)


à Purchasing àPartner Determination à Partner settings in Vendor Master

recordsà Define Partner Schemas

I.


Configuration

Description

Partner 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


à Purchasing àPartner Determination à Partner settings in Vendor Master

recordsà Assign Partner Schemas to account groups

I.


Configuration

Description

Here we assign the already defined schema groups to vendor account

groups

6.44 Define Partner Schemas (Purchasing Documents)


à Purchasing àPartner Determination à Partner settings in Purchasing

documentsà Define Partner Schemas

I.


Configuration

Description

Partner 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


17 of 39 09-03-2015 17:54

6.45 Assign Partner Schemas to Document Types


à Purchasing àPartner Determination à Partner settings in Purchasing

documentsà Assign Partner Schemas to document types

I.


Configuration

Description

In 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 – External ServicesManagement7.1 Define Service Category


à External Serv ices Managementà Serv ice Master à Define Service

Category

I.


Configuration

Description

In this step, we def ine the serv ice category.

The serv ice category is the most important criterion f or structuring

Serv ice master records. It prov ides a def ault v alue f or the v aluation

Classes. Serv ice master records can be assigned to number ranges on the

basis of the serv ice category.

A.

7.2 Define Number Ranges


à External Serv ices Managementà Serv ice Master à Define Number

Ranges

I.


Configuration

Description

In this step, we def ine Number Ranges f or each serv ice category.

7.3 Define Number Range for Service Entry Sheets



Category

I.


Configuration

Description

In this step, we def ine the serv ice category.

The serv ice category is the most important criterion f or structuring

Serv ice master records. It prov ides a def ault v alue f or the v aluation

Classes. Serv ice master records can be assigned to number ranges on the

basis of the serv ice category.

A.

7.4 Define Attributes of System messages



Category

I.


Configuration

Description

In External Serv ices Management, a number of sy stem messages containing

important inf ormation f or users may be issued. Users can process this

inf ormation f urther.

In this step, we can def ine whether the SAP Sy stem

Suppresses this inf ormation

Issues it in the f orm of a warning

Issues it in the f orm of an error message

For ITZ requirement, additional messages no. SE 346 / 347 / 361 is activ ated as

Error along with other additional Standard SAP Messages

8 Materials Management – Inventory Mgmt. & PhysicalInventory


18 of 39 09-03-2015 17:54

8.1 Plant Parameters

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Materials Management ®

Inv entory Management and Phy sical Inv entory ® Plant Parameters

I.


Configuration

Description

In this step, we make the general plant settings f or ‘Inv entory Management’. All settings

are also contained in the indiv idual steps of the Implementation Guide f or Inv entory

Management.

If we hav e created a plant in the enterprise structure using the Copy plant

f unction, we do not need to make any settings.

If we hav e created a plant manually, we hav e to create a new entry f or the plant

parameters.

8.2 Define Number Assignment for Accounting Documents


Inv entory Management and Phy sical Inv entory ® Number Assignment ® Define

Number Assignment for Accounting Documents

I.

Transaction

Code

OMBA

Configuration

Description

In this step, we set the number ranges f or the accounting documents which are created

when goods mov ements or inv entory dif f erences are posted.

For accounting-relev ant goods mov ements, the sy stem creates two dif f erent documents:

material document

accounting document

Both the material documents and the accounting documents hav e their own document

numbers. When inv entory dif f erences are posted, the sy stem also creates an accounting

document f or the phy sical inv entory document.

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

Accounting documents are split into document ty pes to allow dif f erentiated document

number assignment, which is the basis f or distinguishing between the v arious accounting

operations. A number range is assigned to each document ty pe. In a company code, we

hav e to def ine number interv als f or each number range and f iscal y ear. In inv entory

management, the transaction determines which document ty pe is used.

Goods Issue Document Ty pe

TCode Transaction text Ty pe Description

MB05 Subseq. Adjustmt: Act.Ingredient MatA. WE Goods receipt

MB11 Goods Mov ement WA Goods issue

MB1A Goods Withdrawal WA Goods issue

MB1B Transf er Posting WA Goods issue

MB26 Picking list WA Goods issue

MBSU Place in Stor.f or Mat.Doc: Init.Scrn

MIGO_GI Goods Mov ement WA Goods issue

MIGO_TR Transf er Posting WA Goods issue

Goods Receipt Document Ty pe


MB01 Post Goods Receipt f or PO WE Goods receipt

MB04 Subsequ.Adj.of "Mat.Prov ided"Consmp.A. WE Goods receipt

MB0A Post Goods Receipt f or PO WE Goods receipt

MB1C Other Goods Receipts WA Goods issue

MB31 Goods Receipt f or Production Order WE Goods receipt

MBNL Subsequent Deliv ery f . Material Doc.

MBRL Return Deliv ery f or Matl Document

MBSF Release Blocked Stock v ia Mat. Doc. WE Goods receipt

MBSL Copy Material Document

MBST Cancel Material Document

MIGO_GO Goods Mov ement WE Goods receipt

MIGO_GR Goods Mov ement WE Goods receipt

MIGO_GS Subseq. Adjust. of Material Prov idedA. WE Goods receipt

Automatic Mov ements Document Ty pe


BMBC Batch Inf ormation Cockpit WA Goods issue

BORGR GR Automotiv e WE Goods receipt

BORGR_B GR Automotiv e: Posting WE Goods receipt


19 of 39 09-03-2015 17:54

BORGR_C GR Automotiv e: Clearing WE Goods receipt

CAT5 Data Transf er CATS -> PS WA Goods issue

CAT9 Data Transf er CATS -> PM/CS WA Goods issue

CIP2 CC2: Update PDC messages WA Goods issue




CIPV Posting PDC records WA Goods issue

Phy sical Inv entory Document Ty pe


MI07 Process List of Dif f erences WI Inv entory document

MI08 Create List of Dif f erences with Doc. WI Inv entory document

MI10 Create List of Dif f erences w/o Doc. WI Inv entory document

8.3 Define Number Assignment for Material and Physical InventoryDocuments



Number Assignment for Material and Phys.Inv Documents

I.

Transaction Code OMBT

Configuration

Description

In this step, we maintain the number assignment f or the f ollowing documents:

material documents

phy sical inv entory documents

The number assignment f or these documents is not to be conf used with the number

assignment f or accounting documents which we completed in the step Def ine number

assignment f or accounting documents. The number assignment f or accounting

documents depends on the document ty pe which is allocated to the transaction.

The number assignment f or material documents and phy sical inv entory documents

depends on the transaction/ev ent ty pe which is also allocated to each transaction in

Inv entory Management. The transaction/ev ent ty pes are div ided into groups of number

ranges. A number range interv al has to be def ined f or each group.

No From no. To number Status Ext

01 0100000000 0199999999 0

02 4900000000 4999999999 4900002419

03 5000000000 5999999999 5000000219

04 0200000000 0299999999 0

Note

We cannot change the transaction/ev ent ty pes. Howev er, we can change the

number range interv als or we can allocate transaction/ev ent ty pes to new

groups.

SPRO-> IMG-> Materials Management-> Inv entory Management and Phy sical

Inv entory -> Number Assignment-> Def ine Number Assignment f or Material and Phy s.

Inv. Docs

Her y ou ned to maintain the number ranges f or the group attched to the key.

If y ou want to maintain new number range interv als f or an existing group:

a) Choose Group -> Maintain.

b) Select a group and choose Interv al -> Maintain.

c) Choose Edit -> Insert y ear.

d) Maintain the number interv al f or the new f iscal y ear.

8.4 Define Number Assignment for Reservations



Number Assignment for Reservations

I.

Transaction Code OMJK

Configuration

Description

In this step, we set up number assignment f or reserv ations.

The number assignment applies to all plants in the client.

Note

If we create reserv ations with method CreateFromData1 (f unction module

BAPI_RESERVATION_CREATE1), we can use the number range RB f or an

external number assignment.

8.5 Field Selection for Goods Movement/Initial Header Screens


20 of 39 09-03-2015 17:54


Inv entory Management and Phy sical Inv entory ® Field Selection for Goods

Movement/Header Screens

I.

Transaction Code OMJN

Configuration

Description

In this step, we def ine the f ield selection f or goods mov ements initial and header

screens.

Note that the f ield selection f or the item screens depends on the mov ement ty pe and is

conf igured in separate steps.

In this step, we specif y whether the f ields are input, mandatory, display or hidden.

8.6 Field Selection for MIGO


Inv entory Management and Phy sical Inv entory ® Settings f or Enjoy Transactions

® Settings f or Goods Mov ements ® Field Selection for MIGO

I.

Transaction Code OMJX

Configuration

Description

Here we can:

Hide the header data completely or hide particular f ields that we do not require

Hide pushbuttons that we do not require

Def ine the Deliv ery note and Bill of lading f ields as mandatory entries if we use

ev aluated receipt settlement

Show the GR/GI slip (GOHEAD-XABLN) f ield if we use GR/GI slip numbers (only

necessary in certain countries)

Show the Plant (GODYNPRO-PO_WERKS) f ield if we require the ordering-plant

name f or purchase-order-related goods mov ements as a selection criterion in

addition to the purchase order number and item number

Hide the print indicator if we do not want to print out GR/GI slips in Inv entory

Management

8.7 Field Selection per Movement Type



® Settings f or Goods Mov ements ® Field Selection per Mvt Type

I.


Configuration

Description

In this step, we maintain all the settings f or f ield selection by mov ement ty pe. This step

replaces the activ ity Def ine Screen Lay out f or the Enjoy transactions. The settings

f rom Def ine Screen Lay out are adopted in these settings automatically so that we do

not need to maintain new entries here.

We can specif y f or each f ield whether it is an optional entry or a mandatory entry. In

the table, we see all f ields that are v isible. We can access the setting Field Inv isible by

deleting the appropriate entry f rom the table.

There is no distinction between dif f erent special stock indicators in these entries.

Special stock f ields are alway s suppressed automatically.

8.8 Settings for Transactions and Reference Documents



® Settings f or Goods Mov ements ® Settings for Transactions and Reference

Documents

I.


Configuration

Description

We can limit the number of selectable transactions (goods receipt, goods issue, and so

on) and ref erence documents (material document, deliv ery note), and we can specif y

the mov ement ty pe that the sy stem is to propose f or ev ery ref erence document.

If we need only certain transactions (f or example, goods receipts or goods issues), we

can choose f rom the f ollowing preset transactions:

MIGO - Used to enter all goods receipts.

MIGO_GR - Used to enter goods receipts f rom external procurement.

MIGO_GO - Used to enter goods receipts f or production orders.

MIGO_GI - Used to enter goods issues.

We can alway s display material documents.

Transaction MIGO; Actions Mentioned in the table

Action Activ e Action Activ e

A01 A08

A02 A09 X

A03 X A10

A04 X A11


21 of 39 09-03-2015 17:54

A05

A06

A07 X

Ref erence Document Ty pes (For details go to the path mentioned)

Ref .A. Activ e Mv T Ref .A. Activ e Mv T

R01 X 101 R02 X

R04 X 101 R03 X

R05 101 R01 X 351

R06 101 R08 X 261

R07 101 R09 X 201

R08 X 101 R10 X 201

R09 501 R09 X

R10 X 511 R10 X 301

R02 X R10 X 303

R03 X R02 X

R02 X R10 X 305

R02 X R01 X

R02 X

8.9 Create Storage Location Automatically


Inv entory Management and Phy sical Inv entory ® Goods Issue/Transf er

Postings® Create Storage Location Automatically

I.

Transaction Code OMB2

Configuration

Description

In this step, we specif y whether the automatic creation of storage location data is

allowed f or goods issues and transf er postings.

This is adv isable if we work with negativ e stocks and a material's f irst mov ement

may be an outward mov ement.

Note that the rev ersal mov ement f or a goods issue, f or example, mov ement ty pe

202 or 262, is not considered as an issue but as a receipt. If we only use the

automatic creation of storage location data f or rev ersals of goods issues, we do not

hav e to allow negativ e stocks.

We hav e to allow automatic creation per plant f irst of all. We then hav e to explicitly

allow the creation of storage location data f or each mov ement ty pe.

The storage location data is only created if the quantity is posted to 'standard' storage

location stock. It is not created f or receipts into a special stock (f or example, into

sales order stock).We are using standard mov ement ty pes f or automatic Storage

Location Creation

8.10 Set Manual Account Assignment


Inv entory Management and Phy sical Inv entory ® Goods Issue/Transf er Postings®

Set Manual Account Assignment

I.


Configuration

Description

In the R/3 Sy stem, account assignment is predef ined v ia the automatic account

determination f acility.

When we enter material mov ements that are assigned to a cost account, we can enter

the account number manually. In doing so, we change the account assignment

predef ined as of f setting entry f or inv entory posting.

Mv T Acct Mv T Acct

201 309 -

202 310 -

292 311 -

301 - 312 -

302 - 313 -

303 - 314 -

304 - 317 -

8.11 Define Screen Layout


Inv entory Management and Phy sical Inv entory ® Goods Issue/Transf er Postings®

Define Screen Layout

I.

Transaction Code OMBW

Configuration

Description

In this step, we set the f ield selection f or the mov ement ty pes including goods issues

and transf er postings.


22 of 39 09-03-2015 17:54

When creating a goods mov ement, the f ield selection determines which f ields

can be f illed ( optional entry )

must be f illed (required entry )

are suppressed f ields

In Inv entory Management, the f ield selection depends on the mov ement ty pe.

The f ield selection def ined f or a mov ement ty pe is v alid f or entering goods mov ements

and reserv ations.

Note

We do not maintain the input f eatures of the G/L account and Reason f ields

here, but in the f ollowing steps:

Manual account assignment (f or the G/L account f ield)

Reason (f or the Reason f ield)

Caution

The f ield selection f or the mov ement ty pe must correspond with the f ollowing

f ield selections:

f ield status def inition of the G/L account to which postings are made (through the

f ield status group)

f ield selection of the posting key

We must take care that a mandatory entry in the G/L account is also def ined as a

mandatory entry f or the mov ement ty pe.

8.12 Maintain Copy Rules for Reference Documents



Postings® Maintain Copy Rules for Reference Documents

I.


Configuration

Description

In this step, we conf igure whether the items of the ref erence document are proposed

as selected on the item selection list when entering a document with ref erence, 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

MB11 Goods Mov ement X

MB1A Goods Withdrawal X

MB1B Transf er Posting X

8.13 Set up Dynamic Availability Check



Postings ® Set up Dynamic Availability Check

I.

Transaction Code OMCP

Configuration

Description

In this step, we conf igure the dy namic av ailability check.

In Inv entory Management, two ty pes of av ailability check are carried out.

av ailability check during the entry of reserv ations

av ailability check during the entry of goods mov ements

The sy stem checks whether the material to be withdrawn is av ailable and issues a

message, if necessary.

The av ailability check is only carried out if :

the material master record contains a checking group f or the av ailability check

(MRP data)

a checking rule is assigned to the transaction in Customizing

We can def ine

f or each mov ement ty pe which ty pe of message is issued (object Mov ement

ty pe)

which checking rules are supported (object Checking rule)

per checking group and checking rule: which objects (documents, stocks,

material requirements) are included in the av ailability check (object Def ine

checking rule)

per transaction of Inv entory Management: which checking rule applies (object

Transaction codes)

Mv T Val.A.

update

Qty update S Mv t Rec Cns Av


23 of 39 09-03-2015 17:54

201 P

201 X A

201 X K A

201 X P

201 X

201 X X A

201 X X K A

201 X X P

202 P

202 X P

202 X

202 X X

202 X X K

202 X X P

221 Q A

221 Q P A

221 Q L A

221 Q L P A

221 X A

221 X K A

221 X Q A

221 X Q P A

This is an indicativ e table.

Checking Rule

ChR Description of checking rule

01 Checking rule 01

02 Checking rule 02

03 Checking rule 03

A SD order

AE SD order; make-to-order stock

AQ SD order; project stock

AV SD order; returnable packaging

AW SD order; consignment

B SD deliv ery

BB SD deliv ery ; customer stock

BE SD deliv ery ; make-to-order stock

BO Backorder processing

BQ SD deliv ery ; project stock

BV SD deliv ery ; returnable packaging

BW SD deliv ery ; consignment

Def ine Checking Rule

Transaction Codes

TCode Transaction text ChR Checking rule

CO27 Picking list

MB11 Goods Mov ement

MB1A Goods Withdrawal 03 Checking rule 03

MB1B Transf er Posting

MB26 Picking list

MIGO_GI Goods Mov ement

MIGO_TR Transf er Posting

8.14 Generate Physical Inventory Documents for GoodsMovements



Postings ®Generate Physical Inventory Documents for Goods Movements

I.

Transaction Code OMCC

Configuration

Description

In this step, we def ine f or each plant and mov ement ty pe whether a phy sical

inv entory document is automatically generated when posting a goods mov ement.

We can create a phy sical inv entory document in addition to the material document at

the time of a goods mov ement. This f unction is important when inv entory dif f erences

are posted f rom the Warehouse Management Sy stem. These inv entory dif f erences

are thereby documented in Inv entory Management with a phy sical inv entory

document.

In order to create an inv entory document in addition to a material document f or a


24 of 39 09-03-2015 17:54

goods mov ement, the f ollowing conditions must be met:

In the plant, we must def ine the transaction/ev ent ty pe WV f or automatically

generated phy sical inv entory documents.

We must def ine the document number assignment f or this transaction/ev ent ty pe.

Automatic generation of phy sical inv entory documents must be allowed f or the

mov ement ty pe.

Mv T Idoc

717 X

718 X

The abov e list is indicativ e

8.15 Check Tolerance Limits


Inv entory Management and Phy sical Inv entory ® Goods Receipt ® Set

Tolerance Limits

I.

Transaction Code OMC0

Configuration

Description

In this step, we set the tolerance limits f or goods receipts.

When processing a goods receipt, the sy stem checks each item to determine whether

the goods receipt v aries f rom the purchase order or the material master data.

The dif f erent ty pes of v ariances are def ined by tolerance key s. For each tolerance

key, tolerance limits can be set per company code.

The f ollowing v ariances are checked in Inv entory Management:

Variance in the purchase order price quantity

(Explanation)

For this v ariance, two tolerance key s are prov ided:

Tolerance key B1 (error message)

We use tolerance key B1 to def ine the maximum percentage v ariance. If

the v ariance is greater than the maximum v ariance, the sy stem creates an

error message. The user cannot post the goods receipt.

Tolerance key B2 (warning message)

Tolerance key B2 def ines the percentage v ariance f rom which a warning

message is to be issued. It is possible to post the goods receipt.

Variance f or the mov ing av erage price of the material

(Explanation)

We use tolerance key VP to def ine the percentage v ariance f rom which a warning

message is issued. This warning message indicates a price change.

8.16 Create Storage Locations Automatically


Inv entory Management and Phy sical Inv entory ® Goods Receipt ® Create

Storage Locations Automatically

I.


Configuration

Description


allowed f or goods receipts.

This is adv isable if we want to post a goods receipt without hav ing to maintain the

storage location v iew of the material master record in adv ance.



The storage location data is only created if the quantity is posted to 'standard' storage

location stock. It is not created f or receipts into a special stock (f or example, into

sales order stock).

8.17 Set Manual Account Assignment


Inv entory Management and Phy sical Inv entory ® Goods Receipt ® Set Manual

Account Assignment

I.

Transaction Code OMCH

Configuration

Description



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 predef ined as

of f setting entry f or inv entory posting.

8.18 Define Screen Layout


25 of 39 09-03-2015 17:54


Inv entory Management and Phy sical Inv entory ® Goods Receipt ® Define

Screen Layout

I.

Transaction Code OMCJ

Configuration

Description

In this step, we set the f ield selection f or the goods receipt mov ement ty pes.

When entering a goods receipt, the f ield selection controls which f ields (account

assignment f ields) are

ready f or input ( optional entry f ields)

hav e to be f illed (required entry f ields)

suppressed f ields

In Inv entory Management, the f ield selection depends on the mov ement ty pe.



Inv entory Management and Phy sical Inv entory ® Goods Receipt ® Maintain

Copy Rules for Reference Documents

I.


Configuration

Description




does not want to adopt some items.

TCode Transaction text Prsl

MB01 Post Goods Receipt f or PO X

MB0A Post Goods Receipt f or PO X

MB1C Other Goods Receipts X

MB31 Goods Receipt f or Production Order X

MBRL Return Deliv ery f or Matl Document X

MBSF Release Blocked Stock v ia Mat. Doc. X

MBSL Copy Material Document X

MBST Cancel Material Document X

8.20 Set Dynamic Availability Check



Dynamic Availability Check

I.

Transaction Code OMCM

Configuration

Description







Mov ement Ty pe

Mv T Val.updateA. Qty update S Mv t Rec Cns Av

101 X Q B V

101 X Q B X

101 X Q B X P

101 X Q F

101 X Q F P

101 X B

101 X B A

101 X B V

101 X B X

101 X B X A

101 X B X V

101 X X B

101 X X B A

Checking Rule

ChR Description of checking rule

01 Checking rule 01

02 Checking rule 02

03 Checking rule 03

A SD order

AE SD order; make-to-order stock


26 of 39 09-03-2015 17:54

AQ SD order; project stock

AV SD order; returnable packaging

AW SD order; consignment

B SD deliv ery

BB SD deliv ery ; customer stock

BE SD deliv ery ; make-to-order stock

BO Backorder processing

BQ SD deliv ery ; project stock

BV SD deliv ery ; returnable packaging

BW SD deliv ery ; consignment

Transaction Code


MB01 Post Goods Receipt f or PO

MB0A Post Goods Receipt f or PO

MB1C Other Goods Receipts 03 Checking rule 03

MB31 Goods Receipt f or Production Order 03 Checking rule 03

MBNL Subsequent Deliv ery f . Material Doc. 03 Checking rule 03

MBRL Return Deliv ery f or Matl Document

MBSF Release Blocked Stock v ia Mat. Doc.

MBSL Copy Material Document 03 Checking rule 03

MBST Cancel Material Document

MIGO_GO Goods Mov ement

MIGO_GR Goods Mov ement

8.21 Set “Delivery Completed” Indicator



“Delivery Completed” Indicator

I.


Configuration

Description

In this step, we can def ine that the R/3 Sy stem automatically suggests

the deliv ery completed indicator f or goods receipts if the deliv ered quantity lies

within the under/ov er-deliv ery tolerance

The "deliv ery completed" indicator has the f ollowing ef f ects:

The item is regarded as closed, ev en if the total quantity was not deliv ered.

A f urther deliv ery is not expected, may, howev er, arriv e.

In the next goods receipt, the item appears on the selection list but has no

selection indicator.

The item can be reorganized ev en if the total quantity has not been deliv ered.

Note

Ev en if the "deliv ery completed" indicator has not been set, an item is considered

closed once the total quantity has been deliv ered. This means that the "deliv ery

completed" indicator is not necessary in this case.

8.22 Set Expiration Date Check



Expiration Date Check

I.

Transaction Code OMJ5

Configuration

Description

In this step, we set the material shelf lif e expiration date check f or goods receipts f or

each plant and mov ement ty pe.

Prerequisites

The shelf lif e expiration date of a material can only be entered if :

the minimum remaining shelf lif e is maintained in the material master record

The minimum remaining shelf lif e is the time the material must still be usable, so

that the goods receipt is accepted by the sy stem. We can def ine the time unit

the sy stem uses in the storage data of the material master record in the ‘Period

indicator’ f ield.

the shelf lif e expiration date check is activ e in the plant

the shelf lif e expiration date check is activ e f or the mov ement ty pe

No expiration date check has been activ ated f or ITZ.

8.23 Create Storage Location automatically for automaticmovements

Menu path Implementation Guide f or R/3 Customizing (IMG) ® Materials Management ®I.


27 of 39 09-03-2015 17:54

Inv entory Management and Phy sical Inv entory ® Automatic Mov ements ®

Create Storage Locations automatically


Configuration

Description


allowed f or automatic goods mov ements.

This is adv isable f or goods mov ements v ia Shipping or when we post phy sical

inv entory dif f erences, f or example.



The storage location data is only created if the quantity is posted to 'standard'

storage location stock. It is not created f or receipts into a special stock (f or

example, into sales order stock).

8.24 Set manual account assignment for automatic movements


Inv entory Management and Phy sical Inv entory ® Automatic Mov ements ® Set

manual account assignment for automatic movements

I.


Configuration

Description

Maintenance of this indicator is only usef ul in conjunction with mov ements f or which a

G/L account can be entered or is prov ided by the calling program.



When we enter material mov ements that are assigned to a cost account, we can enter

the account number manually. In doing so, we change the account assignment

predef ined as of f setting entry f or inv entory posting.

Mv T Acct Mv T Acct

121 601

131 602

132 603 -

340 - 604 -

341 - 621 -

342 - 622 -

543 - 623 -

544 - 624 -

545 - 631 -

546 - 632 -

8.25 Define Screen Layout for automatic movements



Define Screen Layout

I.

Transaction Code OMJA

Configuration

Description

In this step, we set the screen Lay out f or automatic mov ement ty pes.

8.26 Generate Physical Inventory Documents for GoodsMovements



Generate Physical Inventory Documents for Goods Movements

I.

Transaction Code OMJC

Configuration

Description

In this step, we def ine f or each plant and mov ement ty pe whether a phy sical

inv entory document is created automatically when a goods mov ement is posted.

In conjunction with automatic mov ements, please also note that this indicator is not

set f or goods mov ements which are created f rom within a phy sical inv entory since, in

this case, the phy sical inv entory document already exists. This applies to mov ement

ty pes 701 to 708.

8.27 Define Default Values for Reservations


Inv entory Management and Phy sical Inv entory ® Reserv ations ® Define

Default Values

I.

Transaction Code OMBN


28 of 39 09-03-2015 17:54

Configuration

Description

In this step, we specif y the def ault v alues f or the f ollowing f unctions f or each plant:

allow goods mov ements f or reserv ations

delete reserv ations

create storage-location stock data automatically f or reserv ations

Allow mov ements f or reserv ations

We can only post a goods mov ement with ref erence to a reserv ation if the Mov ement

allowed indicator is set in the reserv ation item.

We are not using Reservations for ITZ.

Delete reserv ations

The management program sets the deletion indicator f or reserv ation items whose

requirements date is earlier than the number of day s specif ied here.

Create storage-location stock data automatically f or reserv ations

When this indicator is set, the storage-location stock data is automatically created

when a reserv ation is posted. This applies both to planned outward mov ements and

planned receipts.



Inv entory Management and Phy sical Inv entory ® Reserv ations ® Define

Default Values

I.


Configuration

Description




does not want to adopt some items

8.29 Set Dynamic Availability Check for Reservations


Inv entory Management and Phy sical Inv entory ® Reserv ations ® Set Dynamic

Availability Check

I.


Configuration

Description








MB21 Create Reserv ation 03 Checking rule 03

MB22 Change Reserv ation 03 Checking rule 03

8.30 Default Values for Physical Inventory


Inv entory Management and Phy sical Inv entory ® Phy sical Inv entory ® Default

Values for Physical Inventory

I.


Configuration

Description

In this step, we specif y the f ollowing def ault v alues f or phy sical inv entory f or each

plant:

Pre-settings f or entering phy sical inv entory documents

the stock ty pe (unrestricted-use, in quality inspection, blocked)

the indicator f or batch determination (in the f oreground or in the background)

the unit of entry (stock keeping unit or unit of issue)

These indicators are suggested as def ault v alues when we enter a phy sical inv entory

document. But we can also change them there.

Pre-settings f or entering phy sical inv entory documents

Reason f or inv entory dif f erence

The def ault v alue we specif y here is only display ed when we enter an inv entory

dif f erence without ref erence to the corresponding document. But we can also

change the def ault v alue here.

Note:

We only see this f ield when we enter inv entory dif f erences if we hav e activ ated it in


29 of 39 09-03-2015 17:54

the step Field selection f or phy sical inv entory.

8.31 Record Reasons for Goods Movements


Inv entory Management and Phy sical Inv entory ® Mov ement Ty pes ® Record

Reasons for Goods Movements

I.

Transaction Code OMBS

Configuration

Description

In 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 a corresponding 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


Inv entory Management and Phy sical Inv entory ® Mov ement Ty pes ® Copy,

Change Movement Types

I.

Transaction Code OMJJ

Configuration

Description

In 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

9 Materials Management – Valuation and AccountAssignment9.1 Split Valuation


Valuation and Account Assignment ® Split Valuation ® Activate Split Valuation

I.

Transaction Code OMW0

Configuration

Description

You conf igure whether split v aluation is allowed at y our company. If y ou generally

allow split v aluation, this does not mean that y ou must v aluate each material on this

basis. You decide whether to do so or not f or a particular material when creating the

material master record.

9.2 Configure Split Valuation


Valuation and Account Assignment ® Split Valuation ® Configure Split

Valuation

I.

Transaction Code OMWC

Configuration

Description

In split v aluation, we can distinguish between partial stocks of a material according to

certain criteria and v aluate them separately.

The material stock is div ided according to v aluation category and v aluation ty pe:

The v aluation category determines how the partial stocks are div ided, that is,

according to which criteria.

The v aluation ty pe describes the characteristics of the indiv idual stocks.

With the f unction "Setting" we can determine:

which v aluation categories exist in our company (global categories)

which v aluation ty pes exist in our company (global ty pes)

which v aluation ty pes belong to which v aluation category

which v aluation categories exist in a v aluation area (local categories)

To select split valuation, proceed as follows:

1. Determine the v aluation categories and v aluation ty pes that are allowed f or all

valuation areas:

1.

Global v aluation categories v ia menu "Goto --> Global Categories"


30 of 39 09-03-2015 17:54

Av erage User Rating

(67 ratings)

11 TweetTweet 4

Global v aluation ty pes v ia menu "Goto --> Global Ty pes"

2. Allocate the v aluation ty pes to the v aluation categories.1.

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

b) Position the cursor on a v aluation category and select "Goto -->

Global Categories --> Allocations --> Ty pes->Category ".

c) Activ ate the v aluation ty pes y ou want.

3. Determine the local v aluation categories f or each v aluation area.1.

a) Select "Goto --> Local def initions".

b) Position the cursor on a v aluation area and select "Goto --> Local

Def initions --> Allocate Categories->Org.units". You obtain a list of

the global v aluation categories.

c) Activ ate the categories to be used in this v aluation area.

The sy stem creates the local v aluation ty pes based on the allocations under

point 2.

88151 Views Products: sap_erp_logistics_materials_management Topics: enterprise_resource_planning

ShareShare 14 33LikeLike

97 Comments

Like (2)

Ragini sap Mar 5, 2013 6:47 PM

Thanks f or sharing usef ul document , In the next v ersion batch management is expected.

Like (0)

Prasanna Soundar Mar 6, 2013 4:53 AM (in response to Ragini sap)

Thank y ou so much f or the comment Prasanna

Like (0)

Ngonidzashe Nhongonhema Feb 22, 2014 7:45 AM (in response to Ragini sap)

Ragin do y ou hav e any conf ig documentation f or Batch Please

Like (0)

Sanjib Naik Sep 17, 2013 12:52 AM

Excellent f or making this document . You take so much time to make this document Cheers Sanjib

Like (0)

Ramesh T Jun 19, 2013 7:19 AM

Good.. Thanks f or Sharing...

Like (2)

ДЖОРДЖ ЧЖАН ХУНЛЯН Jun 24, 2013 12:10 PM

Usef ul! But its better to make an additional note about the v ersion of SAP ECC, because menupath may exists dif f erences.

sanjeet kumar Jun 24, 2013 12:50 PM

Very marv elous... well planned and creativ e. Thanks f or sharing with us.


31 of 39 09-03-2015 17:54

Like (0)

Like (0)

KALAIYARASAN M Jun 24, 2013 12:57 PM

A v ery good document.

Like (0)

Pravin Kadam Jun 24, 2013 3:47 PM

It is v ery usef ul document, Thanx f or y ou share...

Like (0)

Vignesh Veerasamy Jun 25, 2013 7:47 AM

Very usef ul document f or conf iguration beginners.Hope if possible prov ide "Variant Conf iguration- PP/MM" Thanks in adv ance. Vignesh.V

Like (0)

raghavendra sai Jun 27, 2013 1:36 PM

Great compilation

Like (0)

Sajish Kumar S Jun 27, 2013 3:57 PM

Thanky ou f or the share.

Like (0)

Mahboob Rahman Jun 27, 2013 7:27 PM

Thank y ou so much, it is a great ref erence point

Like (0)

Amit Anasane Jun 28, 2013 1:02 PM

great job..

Like (0)

Vinay SAP MM Jun 28, 2013 1:33 PM

v ery helpf ul document !

Like (0)

Narendra Konnipati Jun 28, 2013 4:08 PM

Dear, I dont hav e words to describe y our talent and about y our document .Very * Very *Very Nice .Keepit up . Thanks,Naren

Like (0)

saurabh chaplot Jun 29, 2013 1:14 PM

gud one

Like (0)

Pampaniya Rakesh Jul 2, 2013 10:37 AM

v ery v ert helpf ul f or mm consultant. regards,rakesh

Abu Mohammad Shoyeb, SAP MM Consultant Jul 3, 2013 1:16 PM

v ery helpf ul doc....


32 of 39 09-03-2015 17:54

Like (0)

Like (0)

Benjamin Allsopp Jul 3, 2013 3:49 PM

What an incredibly well put together document. Thank y ou!

Like (0)

sravan kumar Jul 4, 2013 9:48 AM

good work . thank u sharing

Like (0)

naresh babu Jul 9, 2013 2:36 PM

Thank y ou f or sharing.appreciate y our hardwork.

Like (0)

CAROLINE NJUE Jul 11, 2013 9:40 AM

This is so amazing.. i hav e been in search f or such a document! Thanks Prassana.

Like (0)

Sangeetha Kamatkar Jul 15, 2013 9:13 PM

This is an excellent document f or the beginners like us. Thank y ou Sangeetha

Like (0)

Mahammad Jafar Jul 18, 2013 8:36 AM

Thank y ou so much f or this document.

Like (0)

Ashok Kodavati Jul 18, 2013 9:09 AM

thank y ou so much!

Like (0)

Andrey Belyaev Jul 18, 2013 3:24 PM

it's v ery usef ul

Like (0)

SAP WARRIOR Jul 20, 2013 6:24 PM

Thanks f or sharing it.

Like (0)

Niranjan Nagle Jul 20, 2013 8:52 PM

Good Share

Like (0)

Chetan Panchal Jul 21, 2013 2:19 PM

Nice Sharing

Like (3)

Deepak Singh Jul 23, 2013 12:55 PM

good one..itz help a lotz..:)

Like (2)

The Uttkarsh Jul 25, 2013 1:15 PM (in response to Deepak Singh)

Keep it Dea


33 of 39 09-03-2015 17:54

Like (1)

Ravindra Devarapalli Jul 25, 2013 1:38 PM

Great . It is v ery usef ul to all.

Like (0)

Vinay H Jul 28, 2013 6:03 PM

Its simple and best thanks f or sharing...

Like (1)

Deepak Singh Jul 29, 2013 9:07 AM

hey its v ery ny c ...thanx n keep posting..

Like (0)

Roberto Bevacqua Jul 29, 2013 9:57 AM

Very good resume! Thanks.

Like (0)

Navedali Chaudhary Jul 29, 2013 10:58 AM

Great Work .... Thanks f or sharing excellent doc.Can y ou please share " How to conf igure JIT methodology in SAP MM?" What are the change's inSPRO & master data.OR where can i get this becoz i need it urgently.

Like (1)

Jürgen L Aug 6, 2013 7:48 AM

we hav e already 27 wikis, 25 blogs, 17 documents and 4899 discussions f or batch management.No extra document needed. It will be rejected.

Like (0)

Adriaan Fourie Aug 6, 2013 9:28 AM

Good summaries. Thank y ou.

Like (0)

Tarun Rathore Aug 6, 2013 2:14 PM

Really Good Document.........

Like (0)

Sundar Ramanujam Aug 7, 2013 8:40 AM

It is v ery usef ul documents. Thank y ou

Like (0)

Mohsin Borkar Aug 7, 2013 8:43 AM

Hi Prasanna,Thanks f or sharing the document...it's indeed of great use

Like (1)

krishna v Aug 15, 2013 8:20 PM

Good document, Thanks.

Like (0)

Deepa Tate Aug 16, 2013 6:34 AM

Hi Prasanna, Thanks f or sharing the document...Very usef ul f or beginners.

Vijay Anandwala Aug 16, 2013 5:40 PM

Great inf ormation, Thanks f or sharing.


34 of 39 09-03-2015 17:54

Like (0)

Like (0)

kush kumar Aug 21, 2013 12:02 PM

thanks a lot f or sharing. Excellent Work

Like (0)

rajesh dasari Aug 24, 2013 7:20 AM (in response to kush kumar)

Great Inf ormation Thanks f or sharing the document

Like (0)

Allen Wang Aug 24, 2013 3:15 PM

Very usef ul! Thanks a lot f or sharing. Best regardsAllen

Like (0)

Sudhir Singh Aug 26, 2013 12:44 PM

Dear Prasanna Sounder, Thanks f or sharing inf ormation...!!! <remov ed by moderator>

Like (1)

Jamie Jiang Aug 28, 2013 7:21 AM

Good summaries,thanks f or sharing

Like (1)

Sandeep Panuganti Sep 10, 2013 10:29 PM

Very good inf ormation.Thank y ou f or sharing.

Like (1)

Anupam Kumar Sep 11, 2013 11:28 AM

Really a v ery inf ormativ e document. Thanks f or taking all the ef f ort in preparing this.

kudos to y ou

Like (1)

Satyabrata Sahoo Sep 12, 2013 10:58 AM

Very usef ul. Thank y ou f or posting such v aluable document.

Like (0)

Miguel Ramirez Sep 20, 2013 4:32 AM

v ery good

Like (0)

sathya babu Sep 25, 2013 2:53 PM

Very inf ormativ e...also shows ur humanity by preparing and sharing..thank u..

Like (0)

sriman palugula Sep 27, 2013 1:28 PM

really superb notes..thanks

Chetan Panchal Sep 28, 2013 7:53 AM

It's really v ery nice documents. Please keep sharing.


35 of 39 09-03-2015 17:54

Like (0)

Best regards,

Chetan Panchal

Like (0)

Shokat Ali Oct 2, 2013 5:50 PM

It is v ery usef ul doc.Thank y ouRegards,Ali

Like (0)

Nisha Prasad Oct 7, 2013 9:09 PM

Nice Documentation..

Like (0)

Pradeep Mani Oct 8, 2013 6:20 AM

Thanks f or sharing,patiently prepared.

Like (0)

Rupesh Kumar Oct 22, 2013 8:42 AM

It is v ery helpf ul and use. Thanks...............

Like (0)

ratnam sri Oct 27, 2013 12:43 PM

Thanks f or Sharing Regards Ratnamsree

Like (0)

Sanjib Naik Nov 2, 2013 12:11 PM

Nice document, Br,Sanjib

Like (0)

PREETI KASHYAP Nov 19, 2013 12:15 PM

Really this document is v ery inf ormativ e and knowledge sharing. Thanks f or posting. Regards.

Like (0)

Cristina Martínez Dec 5, 2013 7:48 PM

Thanks a lot f or this document!!! is v ery usef ul!I really appreciate it!!

Like (0)

S Ramaraju Dec 14, 2013 1:36 PM

Good Document. Thank y ou.

Like (0)

Sandeep Damania Dec 18, 2013 11:57 AM

Very Nice documentation. Thanks a Lot..

Ismail Koca Dec 25, 2013 9:52 AM

Thanks, v ery usef ul document. Cov ers almost all main customizing steps.ismail


36 of 39 09-03-2015 17:54

Like (0)

Like (0)

Ravishankar Venkat Ramanan Dec 26, 2013 9:19 AM

Very Handy, Thanks Prasanna

Like (1)

Muhammad Umar Farooq Jan 1, 2014 12:52 PM

Great Job, keep it up

Like (1)

Nihal Viradiya Jan 3, 2014 7:12 PM

Hi Prasanna,This not only helps me to understand how to do MM conf iguration but makes me able to v isualize

all element of org structure in more detail. Thank y ou -a beginner

Like (1)

rucha jadhav Jan 22, 2014 10:56 AM

Thanks, v ery usef ul document. Cov ers almost all main customizing steps.

Like (1)

SURJIT SINGH Jan 22, 2014 11:54 AM

Nice Documentation....

Like (1)

Rajendar K Jan 25, 2014 7:13 PM

Thanks alot nice one

Like (1)

faraz hussain khan Jan 26, 2014 7:48 AM

Thanks, v ery usef ul document. Cov ers almost all main customizing steps. .

Request Prasanna to upload more usef ul documents relating to SAP MM conf iguration.

Thanks once again.

Like (1)

Sridhar kumar kommana Jan 28, 2014 4:01 PM

thanks f or sharing y ar.... good work... keep going...

Like (1)

Nitin J Jan 30, 2014 9:06 AM

Indeed a book. Amazing work !!! ntn

Like (1)

Vineeth P Baby Feb 3, 2014 8:20 AM

HI, The document is v ery usef ul f or beginners as it is v ery handy and prov ides all the importantconf igurations. Regards, Vineeth

Like (0)

elham abdi Feb 9, 2014 11:39 AM

thanks


37 of 39 09-03-2015 17:54

Like (0)

Radha krishna Gandrakota Feb 18, 2014 5:22 PM

thanks, helpf ul inf ormation...

Like (0)

Sandeep Panuganti Mar 20, 2014 3:56 PM

Wow!! Nice...ev ery thing in one place.Thank y ou f or sharing.

Like (0)

Khash Slaby May 26, 2014 8:45 AM

Thanks f or sharing, great job.

Like (0)

Santosh Sharma Jul 7, 2014 12:31 PM

Thanks f or sharing. great!!!!!

Like (0)

SAP Consultant Jul 30, 2014 6:04 PM

Very good document. One stop knowledge bank. Thanks f or sharing!

Like (0)

Ravi kumar Aug 27, 2014 12:47 PM

Very good document. Thanks f or sharing

Like (0)

Vick Patel Sep 2, 2014 8:23 PM

v ery well written and simple to understand...

Like (0)

Ramprasad Atkuri Sep 6, 2014 12:13 PM

Dear Prasanna , Thanks f or sharing , Great work .

Like (0)

kumar kumar Sep 6, 2014 1:22 PM

Hi prasanna Very good document. Thanks f or sharing Regards Kuamr

Like (1)

Farooq Basha Sep 15, 2014 2:40 PM

Thanks, v ery usef ul document. Cov ers almost all main customizing steps

Like (0)

Gururaj Bettahalli-Rajegowda Sep 16, 2014 2:52 PM

Good Document...:)

Like (0)

Roberto Mendoza Sep 18, 2014 4:14 PM

Thanks f or sharing, good source of inf ormation. .

Like (0)

Wily Wendiatma Sep 22, 2014 2:48 PM

thanks prasanna

VIVEK KUMAR Sep 28, 2014 12:56 PM

v ery usef ul document. thanks


38 of 39 09-03-2015 17:54

Follow SCNSite Index Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright

Like (0)

Like (0)

Devendra F Oct 5, 2014 7:24 AM

Those docs def initely change the rule of the games, Very Nice one.

Like (0)

Bharath Babu Oct 21, 2014 4:35 PM

Thank y ou f or sharing the document. It is v ery usef ul f or me.

Like (0)

Nassar fathy Oct 29, 2014 3:54 PM

thank y ou v ery much f or y our strong support

Like (1)

amira rashed Oct 29, 2014 9:31 PM

v ery v ery usef ul and so easy f or the beginners, thanks a lot Amira,


39 of 39 09-03-2015 17:54

sap mm configuration - scn

Documents

material stocks f

company code lev

toeach company code

single company code

plant stocks ofa material

f ollowing attributes

v aluation lev

joint stock account