sap mm configuration

Generated by Jive on 2013-07-02+02:001

SAP MM Configuration

MM – Configuration Documentation



2 Enterprise Structure - Definition

2.1 Define Valuation Level

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

Transaction Code OX14

Configuration Description Here we specify the level at which materialstocks are valuated. We have used thePlant level since the application component



Production Planning (PP) and Costing arebeing used.

• Depending on the valuation level chosen,accounting data (in particular the valuationprice) is maintained for each plant or for eachcompany code in the material master record.

• If material stocks are valuated at companycode level, all plant stocks of a material aremanaged in a joint stock account for eachcompany code.

• If material stocks are valuated at plant level,the material stocks for each plant can bemanaged in different accounts. We can definea separate account determination for eachplant.

2.2 Define Plant

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

Transaction Code SPRO

Configuration Description As a part of the LogisticsOrganizational Structure, Plantsare defined in SAP. The ‘Plant’ isan operating area or a branch or alocation within a company. Each 'Plant'is assigned to a single 'company code'.A 'company code' can have several'Plants'. In case of ITZ Pvt. Ltd., the various'Plants' are assigned to a each 'companycode'.

Configuration of One Plant is depictedhere, (for list of all please refer to MM KDSDocument)



2.3 Maintain Storage Location

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

Transaction Code OX09

Configuration Description A storage location is the place where stockis physically kept within a plant. There maybe one or more storage locations within aplant.

A storage location has the followingattributes:

• A storage location has a description and atleast one address.

• It is possible to store material data specific toa storage location.

• Stocks are managed only on a quantity basisand not on a value basis at storage locationlevel.

• Physical inventories are carried out at storagelocation level.

Configuration of Storage Locations underOne Plant is depicted here, (for list of allplease 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


Configuration Description At this node we configure the PurchasingOrganization .The purchasing organizationis the highest level of aggregation (after theorganizational unit "client") for purchasingstatistics.

In case of ITZ One single PurchaseOrganization is created as under :

3 Enterprise Structure Assignments

3.1 Assign Plant to Company Code

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


Configuration Description A Plant needs to be assigned to one of theCompany Codes, the relation is always oneto one i.e. One Plant can be assigned to onlyone company code

All the plants can’t be shown here(forcomplete list 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® Logistics general ® Assign purchasingorganization to company code


Configuration Description In this node we assign the PurchasingOrganization to the company code underwhich it works.

In case of ITZ the Purchasing Organizationis Central, so it is not assigned to anyCompany Code

3.3 Assign purchasing organization to Plant

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


Configuration Description In this step we assign purchasingorganizations to the plants for which they areresponsible.

In case of ITZ since it operates withCentralized Purchasing Org. we haveassigned the Purchasing Org. to all theplants 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 standardpurchasing organization to plant




Configuration Description If several purchasing organisations procurefor a certain plant, we can define oneof them as the standard purchasingorganization for the transactions "pipelineprocurement", "consigmnent" and "stocktransfers".

In source determination for stock transfersand consignent, the system automaticallyutilizes this standard purchasingorganization. In the case of goods issuesof pipeline materials, the purchasinginfo records of the standard purchasingorganization are read.

In ITZ, we have not defined this Settingas we are using single PurchasingOrganisation

4 General Logistics

4.1 Assign Fields to Fields Selection Groups

Menu path 1. Implementation Guide forR/3 Customizing (IMG)® Logistics - General àMaterial Master à FieldSelectionà Assign Fields toFields Selection Groups

Transaction Code OMSR

Configuration Description Assignment of MaterialMaster Fields is requiredto define whether a fieldis hidden or displayed,or whether an entry ismandatory or optional



in material mastermaintenance, it is alwaysadvisable to work withStandard SAP settings, butfor few business requirementsome assignments arechanged to new fieldselection groups defined asper reserved name space.in case of ITZ, some of thelist of changed entries is asgiven below:

FieldName

DescriptionChangedFieldGrp

MVKE-MVGR1

Materialgroup 1

211

MVKE-MVGR2

Materialgroup 2

211

MVKE-MVGR3

Materialgroup 3

211

4.2 Maintain Field Selection for Data Screens

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

Transaction Code OMS9

Configuration Description In this step we define the nature of a Fieldbelonging to a particular Field SelectionGroup wrt the Screen Reference of aMaterial 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.

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 Codesfor Materials Management

Transaction Code OMSY

Configuration Description This activity is done for making a CompanyCode relevant for materials Managementand to define the starting posting periodThis is a prerequisite for creating a MaterialMaster

4.4 Define Attributes of Material Types

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

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. 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à Basic Settingsà Material Typesà DefineNumber Ranges for each Material Types

Transaction Code MMNR

Configuration Description In this step, we have defined the type ofnumber assignment and the number rangeintervals for material master records. Whencreating a material master record, systemmust assign it a unique number. There aretwo ways of doing this:

• internal number assignment

In this case, a number within the numberrange interval allowed is assigned by theSAP 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 intervalsfor so-called groups. We assign one or morematerial 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 materialtype, we can define an internal and an externalnumber range interval here too. This allowsseveral material types to have the same numberrange intervals.

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 Description When 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.• The message can be displayed as an error

message. (can’t be surpassed)

For ITZ requirement Message NumbersMM189 & 312 are changed as Errormessage

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à Settings for Key Fieldsà Define MaterialGroups

Transaction Code OMSF

Configuration Description Here we define the Groups for Materials &Services, This Grouping shall be definedkeeping in mind the reporting requirementof the company for analysing Purchases,Consumptions, Stocks etc,

Setting is just a table entry, few records areshown in the screen shot, for complete listrefer to the MM KDS document or the actualsystem node

4.8 Define External Material Groups

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


Configuration Description Here we define the Groups for giving anextra key for filtering, sorting the list ofmaterials from a criterion other than Materialgrouping

In case of ITZ we have not used ExternalMaterial Groups



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 Description This Transaction can be used to initializethe period in materials management , i.e.it opens the already closed period (thruTxn : MMPV), but opening a period hasserious implications on data consistency inSAP so as recommended by SAP Followthe instructions in Note 487381 beforeinitialization

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-based Planning à Master Data àMRP Areas àActivate MRP for MRP Areas


Configuration Description This 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.

5.2 Define MRP Areas

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

Transaction Code SCAL

Configuration Description Here 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 MRParea

Important : If MRP area is activated Conversion of Planning file entries needs tobe run in every new System Client throughReport RMDBVM00 in Txn : SE38

The conversion report causes the system tocreate a new planning file. In addition, thesystem creates MRP area for the existingplants. These MRP areas do not, however,affect the way material requirementsplanning is carried out. The number for plant



MRP areas is identical to the plant numberand therefore consists of four digits.

The conversion of the current planning file(table MDVM) to the new planning file (tableDBVM) is a prerequisite for carrying outmaterial requirements planning with MRPareas.

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


Configuration Description In Purchasing, certain system messagescontaining important information for usersmay be issued from time to time

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

• Suppresses the relevant information

• Issues it as a warning message

• Issues it as an error message

In the case of an error message, processing cannot becontinued until user input has been corrected

For ITZ requirement, messages (as achange from standard) are configured asgiven below:



6.2 Define Purchasing Value Keys

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


Configuration Description With Purchasing value key we can controlfollowing functions by using it in the materialmaster purchasing view, purchasing valuekey 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 POitems

• Shipping/packaging instructions

This data appears as default data in purchasingdocuments and is taken from the material master record(unless a purchasing info record exists, in which case itis 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 ItemsWithout a Material Master




Configuration Description In this step we assign In this step, wecan assign a purchasing value key and avaluation class to a material group.

The assignment of a purchasing value keydefault values for reminder levels etc. inpurchase order items without a materialmaster record and without an info record.

The assignment of a valuation class toa material group enables the systemto determine different accounts for theindividual material groups.

For ITZ we have maintained ValuationClasses in the accounting view of thematerials.

6.4 Create Purchasing Groups

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


Configuration Description It’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 hasa 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


Configuration Description SAP manages RFQs and quotations asdocuments which are grouped into differentdocument 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 datafrom the document header is updated in thestatistics file.

Linkage determines which PR documenttypes can be referenced for creating aparticular 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 /Quotations à Define Text Types forHeader Texts


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

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 forLine Texts (RFQ/Quotations)


Configuration Description In this step we define copying rules for different

header Texts which appear in RFQ/Quotation Line

Items

Copying rules are used to determine whichtexts can be adapted from other objects (forexample, vendor master records, contracts)to the header text of the RFQ. We link texttypes in the RFQ with text types in other



objects. System can adopt header texts fromthe 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 documenttypes (Purchase Requisitions)


Configuration Description SAP manages Purchase Requisitions asdocuments which are grouped into variousdocument 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



• Chosen


Above linkage governs which type of PO canbe 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


Configuration Description In this step, we have set up the releaseprocedure with classification.

Purchase Requisition release is the processin which Purchase Requisition is approvedand released by HOD of concern departmentfor request of required material or servicesspecified in Purchase Requisition. Oncethe Purchase Requisition is approved andreleased then Purchase Order or RFQ willbe created for that material or servicesagainst same Purchase Requisition.

Configuration involves following elements insequence:

Release Group:

Specify for the release group either "overallrelease" or "item-wise release"



Release codes:

The Release Code is a two-character IDallowing a person to release (approve) arequisition.(analogous to approver code)

Release Indicators:

A release indicator shows the release statusof a purchase requisition

Release Indicators also involve:

Field selection key via the field selectionkey, we can specify which fields in apurchase requisition with this releaseindicator can be changed or must bepopulated

Changes after start of release process

• With the Changeability indicator, we canspecify the effects of changes to a requisition.For example, certain changes may require anew release strategy to be determined for therequisition.

• Via the Value change field, we can cause therelease strategy to be re-started if the valueof a purchase requisition item is increased bymore than a certain percentage (e.g. 10%).To do so, set the Changeability indicatorto "4 - Changeable, new release in case ofnew strategy or value change" and enter apercentage in the Value change field.



Release Strategy

The Release Strategy defines the approval process

for Purchase Requisitions. The strategy specifies the

release codes which are necessary and the sequence

in which releases have to be affected. We can define

a maximum of eight release codes i.e. 8 Levels of

approval.

Release Prerequisites indicate the sequence

in which a Purchase Requisition must be approved

via the release codes. (In ITZ case release is

parallel(either / or so indicators are kept blank)

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

Release Values

These values need to be maintained inevery client manually, this forms the basis onwhich release strategy is triggered for a PR.



An important prerequisite for this is to createClass & Characteristics in class type 032

Characteristics for Release Strategy

Create the Characteristics required forrelease strategy as master data thrutransaction CT04, here the most importantsetting is to attach the characteristics tocorresponding field of structure CEBAN

attach it to the structure

Class for Release Strategy

Create the class as master data thrutransaction CL02

and attach the Characteristics created earlierto the class



6.10 Define Number Ranges (Purchase Orders)

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

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 ways of doing this:

• internal number assignment

In this case, a number within the numberrange interval allowed is assigned by theSAP 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 areassigned with internal number rangeswith the exception for document type“Legacy Open P.O”, as it was requiredto retain the legacy P.O number for thiscase.

go in change mode and define the intervalsas shown:



6.11 Define Document types (Purchase Orders)

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


Configuration Description SAP manages Purchase Orders asdocuments which are grouped into variousdocument 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



• Chosen


Above linkage governs which type of PRcan be referenced created while creating aparticular Contract document type



6.12 Set Tolerance Limits for Price Variance

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


Configuration Description When processing a purchase order, thesystem checks whether the effective priceof a PO item shows variances comparedwith the valuation price stored in thematerial master record. In addition, it checkswhether the specified cash discount value isadmissible.

Variances are allowed within the tolerancelimits. If a variance exceeds a tolerancelimit, the system issues a warning or errormessage. In SAP, the types of variance arerepresented by the tolerance keys. For eachtolerance key, we can define percentage andvalue-dependent upper and lower limits percompany code.

• PE Price variance, Purchasing

• Tolerance limit for system messageno. 207. This message appears ifthe specified effective price exceedsthe predefined tolerances whencompared with the material price.

• SE Maximum cash discount deduction,Purchasing

• Tolerance limit for system messageno. 231. This is a warning message,which appears when the specifiedcash discount percentage exceedsthe predefined tolerances.



6.13 Release Procedure for Purchase Orders

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


Configuration Description In this step, we have set up the releaseprocedure for Purchase Orders(this alsocovers the process for other externalpurchasing documents e.g. contracts/scheduling agreements)

Purchase Order release is the process inwhich PO is approved and released byHOD of concern department for request ofrequired material or services specified in PO.Once the Order is approved and releasedthen GR can be created against the PO

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

Configuration involves following elements insequence:

Release Group:

Release groups are created for each type ofpurchasing

Release codes:



The Release Code is a two-character IDallowing a person to release (approve) arequisition.(analogous to approver code)

Release Indicators:

A release indicator shows the release statusof a Purchase Order

Release Indicators also involve:

Changeability Indicator With theChangeability indicator, we can specify theeffects of changes to a PO document. 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 ofa purchase order is increased by more than acertain percentage (e.g. 10%). To do so, setthe Changeability indicator to "6 - Changeable,new release in case of new strategy or valuechange" and enter a percentage in the Valuechange field.

Release Strategy

The Release Strategy defines the approval process

for PO. The strategy specifies the release codes

which are necessary and the sequence in which

releases have to be affected. We can define a



maximum of eight release codes i.e. 8 Levels of

approval.

Release Prerequisites indicate the sequence in

which a Purchase Requisition must be approved via

the release codes. (In ITZ case release is by a single

authority so there are no prerequisite involved)

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

Release Values

These values need to be maintained inevery client manually, this forms the basis onwhich release strategy is triggered for a PO.

An important prerequisite for this is to createClass & Characteristics in class type 032

Characteristics for Release Strategy

Create the Characteristics required forrelease strategy as master data thrutransaction CT04, here the most importantsetting is to attach the characteristics tocorresponding field of structure CEKKO



And attach it to the structure

Class for Release Strategy

Create the class as master data thrutransaction CL02 and attach theCharacteristics 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 Orders à Define Screen Layout atDocument Level


Configuration Description In this step we define the attributes ofvarious fields contained in a field selectionkey (defined for a document type) insidewhich various fields are grouped into fieldsselection groups.Steps involved in theprocess are :

• Selecting the field selection key (defined for adocument type)

• Select the field selection option (hide, display,required entry, or Optional entry) for each field



inside a field selection group reference asrequired.

Select a field selection key and set theattributes inside as shown:

get inside a field group and choose theattributes

settings can be made similarly for otherfields in various other groups as & whenrequired

6.15 Define Text Types for Header Texts (Purchase

Orders)

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



in Purchase order header, these are used to store

information applicable for a particular PO document



6.16 Define copying rules for Header Texts (Purchase

Order)

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



header Texts which appear in Purchase Order

Headers

Copying rules are used to determine whichtexts can be adapted from other objects (forexample, vendor master records, contracts,RFQ) to the header text of the PurchaseOrder. We link text types in the PO with texttypes in other objects. System can adoptheader 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. Currently weare not maintaining any copying rule for header texts

6.17 Define Text Types for Item Texts (Purchase Orders)

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





in Purchase order item level, these are used to store

information applicable for a particular PO document

line item

6.18 Define copying rules for Item Texts (Purchase

Order)

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


Configuration Description In this step we define copying rules for different item

Texts which appear in Purchase Order ITEM

Copying rules are used to determine whichtexts can be adapted from other objects (forexample, vendor master records, contracts,RFQ) to the header text of the PurchaseOrder. We link text types in the PO with texttypes in other objects. System can adoptheader texts from the following objects:

• RFQ / Quotation• Purchase Requisition• Purchase Info record• Contract• Material master

We can also specify here whether the adopted text canbe 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 Description SAP manages Contracts as documentswhich are grouped into various documenttypes., 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



• Chosen


In case of ITZ, use of Contracts andScheduling agreements is very minimal sowe have retained and used standard SAPdocument types



Above linkage governs which type of PRcan be referenced created while creating aparticular 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 atDocument Level


Configuration Description In this step we define the attributes ofvarious fields contained in a field selectionkey (defined for a document type) insidewhich various fields are grouped into fieldsselection groups.Steps involved in theprocess are :

• Selecting the field selection key (defined for adocument 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 theattributes inside as shown:

get inside a field group and choose theattributes

settings can be made similarly for otherfields in various other groups as & whenrequired



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 HeaderTexts


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)

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



header Texts which appear in Contract Headers

Copying rules are used to determine whichtexts can be adapted from other objects (forexample, vendor master records, Contract,RFQ) to the header text of the Contract.We link text types in the PO with text typesin other objects. System can adopt headertexts 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 andcopying Rules for Header Texts



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



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 ItemTexts


Configuration Description In this step we define copying rules for different item

Texts which appear in Contract Headers

Copying rules are used to determine whichtexts can be adapted from other objects (forexample, vendor master records, contracts,RFQ) to the header text of the Contract. Welink text types in the Contract with text typesin other objects. System can adopt headertexts from the following objects:

• RFQ / Quotation• Purchase Requisition• Contract• Purchase Info record• Material master

We can also specify here whether the adopted text canbe 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àConfirmations à Define External ConfirmationCategories


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

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


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


Configuration Description In 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àConditionsà Define Price DeterminationProcess à Define Access Sequence


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.

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

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 DeterminationProcess à Define Calculation Schema

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

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


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 :



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 DeterminationProcess à Define Schema determination


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

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


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

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


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

• Enter the name of the table we wish to create.• Note that we can only choose names between

501 and 999. If we make no entry, the systemwill automatically assign a consecutive number.

• Specify whether we wish to create the table withor without a validity period.

• Enter the type of condition table (for example,transparent table).

• Enter a description for the condition table.• From the list of allowed fields that are included

in the field catalog and which can be extendedthere, choose the desired fields for the conditiontable.

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


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


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 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àVendor Evaluation à Define Weighing keys


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

6.38 Define Criterion (Vendor Evaluation)

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


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 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àVendor Evaluation à Define Scope of List


Configuration Description In this step we define various types of list,each representing different main criteria orthe same main criteria in a different order.

In the standard system, the scope-of-listparameters 'standard' and 'version 1' aresupplied as an example:

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

• The parameter Version 1 yields a rankinglist of vendors sorted according to thescore for the main criterion "Price". Thenfollow the overall evaluation and the maincriteria "General service/support", "Quality","Delivery", and "Externally performed service/work".

check the details of list inside

6.40 Maintain Purchasing Organization data

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàVendor Evaluation à Maintain PurchasingOrganization data




Configuration Description Select a row and displays criterion for Purchasing

Organization

Sub criterions for main criterion

Weighing for a Purchasing Org.

We have provided Equal Weighting to the Criteria as

we have different weighing parameters for ITZ

Point scores for a Purchasing Org.

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àDefine Permissible Partner Roles per AccountGroup


Configuration Description Here we can specify for each accountgroup of the vendor which roles the vendormay assume. Example we can specifythat certain vendors may only serve as anordering address, not as an invoicing party.

6.42 Define Partner Schemas (Vendor Master)

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàPartner Determination à Partner settingsin Vendor Master recordsà Define PartnerSchemas




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

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàPartner Determination à Partner settingsin Vendor Master recordsà Assign PartnerSchemas to account groups


Configuration Description Here 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àPartner Determination à Partner settingsin Purchasing documentsà Define PartnerSchemas


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

6.45 Assign Partner Schemas to Document Types

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management à PurchasingàPartner Determination à Partner settingsin Purchasing documentsà Assign PartnerSchemas to document types


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 – ExternalServices Management

7.1 Define Service Category

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


Configuration Description In this step, we define the service category.

The service category is the most importantcriterion for structuring

Service master records. It provides a defaultvalue for the valuation



1. Classes. Service master records can beassigned to number ranges on the basis of theservice category.

7.2 Define Number Ranges

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


Configuration Description In this step, we define Number Ranges foreach service category.

7.3 Define Number Range for Service Entry Sheets



Configuration Description In this step, we define the service category.

The service category is the most importantcriterion for structuring

Service master records. It provides a defaultvalue for the valuation

1. Classes. Service master records can beassigned to number ranges on the basis of theservice category.



7.4 Define Attributes of System messages



Configuration Description In External Services Management, a numberof system messages containing importantinformation for users may be issued. Userscan process this information further.

In this step, we can define whether the SAPSystem

• Suppresses this information• Issues it in the form of a warning

• Issues it in the form of an error message

For ITZ requirement, additional messagesno. SE 346 / 347 / 361 is activated as Erroralong with other additional Standard SAPMessages



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


Configuration Description In this step, we make the general plantsettings for ‘Inventory Management’.All settings are also contained in theindividual steps of the ImplementationGuide for Inventory Management.

• If we have created a plant in the enterprisestructure using the Copy plant function, we donot need to make any settings.

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

8.2 Define Number Assignment for Accounting

Documents

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



® NumberAssignment ®Define NumberAssignmentfor AccountingDocuments

Transaction Code OMBA

ConfigurationDescription

In this step, we setthe number rangesfor the accountingdocuments whichare created whengoods movements orinventory differencesare posted.

For accounting-relevant goodsmovements, thesystem creates twodifferent documents:

• materialdocument

• accountingdocument

Both the materialdocuments andthe accountingdocuments havetheir own documentnumbers. Wheninventory differencesare posted, thesystem also createsan accountingdocument for thephysical inventorydocument.



In this step, weonly maintain thenumber assignmentfor accountingdocuments.

Accountingdocuments are splitinto document typesto allow differentiateddocument numberassignment, whichis the basis fordistinguishingbetween thevarious accountingoperations. A numberrange is assigned toeach document type.In a company code,we have to definenumber intervalsfor each numberrange and fiscalyear. In inventorymanagement,the transactiondetermines whichdocument type isused.

Goods IssueDocument Type

TCodeTransactiontext

Type Description



MB05 1. Subseq.Adjustmt:Act.IngredientMat

WE Goodsreceipt

MB11GoodsMovement

WA Goodsissue

MB1AGoodsWithdrawal

WA Goodsissue

MB1BTransferPosting

WA Goodsissue

MB26Pickinglist

WA Goodsissue

MBSUPlaceinStor.forMat.Doc:Init.Scrn

MIGO_GIGoodsMovement

WA Goodsissue

MIGO_TRTransferPosting

WA Goodsissue

Goods ReceiptDocument Type


Type Description

MB01PostGoodsReceiptforPO

WE Goodsreceipt

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

WE Goodsreceipt



MB0APostGoodsReceiptforPO

WE Goodsreceipt

MB1COtherGoodsReceipts

WA Goodsissue

MB31GoodsReceiptforProductionOrder

WE Goodsreceipt

MBNLSubsequentDeliveryf.MaterialDoc.

MBRLReturnDeliveryforMatlDocument

MBSFReleaseBlockedStockviaMat.Doc.

WE Goodsreceipt

MBSLCopyMaterialDocument

MBSTCancelMaterialDocument

MIGO_GOGoodsMovement

WE Goodsreceipt



MIGO_GRGoodsMovement

WE Goodsreceipt

MIGO_GS1. Subseq.Adjust.ofMaterialProvided

WE Goodsreceipt

AutomaticMovementsDocument Type


Type Description

BMBCBatchInformationCockpit

WA Goodsissue

BORGRGRAutomotive

WE Goodsreceipt

BORGR_BGRAutomotive:Posting

WE Goodsreceipt

BORGR_CGRAutomotive:Clearing

WE Goodsreceipt

CAT5DataTransferCATS->PS

WA Goodsissue

CAT9DataTransferCATS->PM/CS

WA Goodsissue



CIP2 CC2:UpdatePDCmessages

WA Goodsissue


WA Goodsissue


WA Goodsissue


WA Goodsissue

CIPVPostingPDCrecords

WA Goodsissue

Physical InventoryDocument Type


Type Description

MI07 ProcessListofDifferences

WI Inventorydocument

MI08 CreateListofDifferenceswithDoc.




MI10 CreateListofDifferencesw/oDoc.


8.3 Define Number Assignment for Material and Physical

Inventory Documents

Menu path 1. ImplementationGuidefor R/3Customizing(IMG) ®MaterialsManagement® InventoryManagementandPhysicalInventory® NumberAssignment® DefineNumberAssignmentfor MaterialandPhys.InvDocuments

TransactionCode

OMBT


In this step,we maintainthe numberassignment forthe followingdocuments:

• materialdocuments



• physicalinventorydocuments

The numberassignment forthese documentsis not to beconfused withthe numberassignmentfor accountingdocumentswhich wecompletedin the stepDefine numberassignmentfor accountingdocuments.The numberassignmentfor accountingdocumentsdepends onthe documenttype which isallocated to thetransaction.

The numberassignmentfor materialdocumentsand physicalinventorydocumentsdepends on thetransaction/eventtype which isalso allocated toeach transaction



in InventoryManagement.The transaction/event typesare dividedinto groups ofnumber ranges.A number rangeinterval has to bedefined for eachgroup.

No Fromno.

Tonumber

StatusExt

01 010000000001999999990

02 490000000049999999994900002419

03 500000000059999999995000000219

04 020000000002999999990

Note

We cannotchange thetransaction/event types.However, wecan change thenumber rangeintervals or wecan allocatetransaction/eventtypes to newgroups.



SPRO-> IMG-

> Materials

Management-

> Inventory

Management and

Physical Inventory->

Number Assignment-

> Define Number

Assignment for

Material and Phys.

Inv. Docs Her you

ned to maintain the

number ranges for the

group attched to the

key.

If you want to maintain

new number range

intervals for an

existing group: a)

Choose Group ->

Maintain. b) Select

a group and choose

Interval -> Maintain. c)

Choose Edit -> Insert

year. d) Maintain the

number interval for the

new fiscal year.

8.4 Define Number Assignment for Reservations

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

Transaction Code OMJK



Configuration Description In this step, we set up number assignmentfor reservations.

The number assignment applies to all plantsin the client.

Note

If we create reservations with methodCreateFromData1 (function moduleBAPI_RESERVATION_CREATE1), we canuse the number range RB for an externalnumber 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 Description In this step, we define the field selectionfor goods movements initial and headerscreens.

Note that the field selection for the itemscreens depends on the movement type andis configured in separate steps.

In this step, we specify whether the fields areinput, 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 ®Settings for Enjoy Transactions ® Settings forGoods Movements ® Field Selection for MIGO

Transaction Code OMJX

Configuration Description Here we can:

• Hide the header data completely or hideparticular fields that we do not require

• Hide pushbuttons that we do not require• Define the Delivery note and Bill of lading

fields as mandatory entries if we useevaluated receipt settlement

• Show the GR/GI slip (GOHEAD-XABLN) fieldif we use GR/GI slip numbers (only necessaryin certain countries)

• Show the Plant (GODYNPRO-PO_WERKS)field if we require the ordering-plant name forpurchase-order-related goods movements asa selection criterion in addition to the purchaseorder number and item number

Hide the print indicator if we do not want to print out GR/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 ®Settings for Enjoy Transactions ® Settings forGoods Movements ® Field Selection per MvtType


Configuration Description In this step, we maintain all the settings forfield selection by movement type. This stepreplaces the activity Define Screen Layoutfor the Enjoy transactions. The settings fromDefine Screen Layout are adopted in these



settings automatically so that we do notneed to maintain new entries here.

We can specify for each field whether it isan optional entry or a mandatory entry. Inthe table, we see all fields that are visible.We can access the setting Field Invisible bydeleting the appropriate entry from the table.

There is no distinction between differentspecial stock indicators in these entries.Special stock fields are always suppressedautomatically.

8.8 Settings for Transactions and Reference Documents

Menu path 1. ImplementationGuidefor R/3Customizing(IMG)®MaterialsManagement®InventoryManagementandPhysicalInventory®SettingsforEnjoyTransactions®Settings



forGoodsMovements®SettingsforTransactionsandReferenceDocuments

TransactionCode

SPRO


We can limitthe numberof selectabletransactions(goodsreceipt,goods issue,and so on)and referencedocuments(materialdocument,deliverynote), andwe canspecify themovementtype that thesystem isto proposefor everyreferencedocument.

If we needonly certaintransactions(for example,goodsreceipts



or goodsissues), wecan choosefrom thefollowingpresettransactions:

MIGO - Usedto enterall goodsreceipts.

MIGO_GR- Used toenter goodsreceipts fromexternalprocurement.

MIGO_GO- Used toenter goodsreceipts forproductionorders.

MIGO_GI -Used to entergoods issues.

We canalwaysdisplaymaterialdocuments.



TransactionMIGO;ActionsMentioned inthe table

ActionActiveActionActive

A01 A08

A02 A09X

A03X A10

A04X A11

A05

A06

A07X

ReferenceDocumentTypes (Fordetails goto the pathmentioned)

1. Ref.ActiveMvT 1. 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 Description In this step, we specify whether theautomatic creation of storage location datais allowed for goods issues and transferpostings.

This is advisable if we work with negativestocks and a material's first movement maybe an outward movement.

Note that the reversal movement for a goodsissue, for example, movement type 202 or262, is not considered as an issue but as areceipt. If we only use the automatic creationof storage location data for reversals ofgoods issues, we do not have to allownegative stocks.



We have to allow automatic creation perplant first of all. We then have to explicitlyallow the creation of storage location data foreach movement type.

The storage location data is only created ifthe quantity is posted to 'standard' storagelocation stock. It is not created for receiptsinto a special stock (for example, intosales order stock).We are using standardmovement types for automatic StorageLocation Creation

8.10 Set Manual Account Assignment

Menu path 1. ImplementationGuide for R/3Customizing(IMG) ®MaterialsManagement® InventoryManagementand PhysicalInventory ®Goods Issue/TransferPostings® SetManual AccountAssignment



In the R/3 System,account assignmentis predefined via theautomatic accountdetermination facility.

When we entermaterial movements



that are assignedto a cost account,we can enter theaccount numbermanually. In doingso, we change theaccount assignmentpredefined asoffsetting entry forinventory 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 ScreenLayout

Transaction Code OMBW

Configuration Description In this step, we set the field selection for themovement types including goods issues andtransfer postings.

When creating a goods movement, the fieldselection determines which fields



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

In Inventory Management, the field selectiondepends on the movement type.

The field selection defined for a movementtype is valid for entering goods movementsand reservations.

Note

We do not maintain the input features of theG/L account and Reason fields here, but inthe following steps:

• Manual account assignment (for the G/Laccount field)

• Reason (for the Reason field)

Caution

The field selection for the movement typemust correspond with the following fieldselections:

• field status definition of the G/L account towhich postings are made (through the fieldstatus group)

• field selection of the posting key

We must take care that a mandatory entryin the G/L account is also defined as amandatory entry for the movement type.



8.12 Maintain Copy Rules for Reference Documents

Menu path 1. Implementation Guide forR/3 Customizing (IMG) ®Materials Management ®Inventory Managementand Physical Inventory® Goods Issue/TransferPostings® Maintain CopyRules for ReferenceDocuments


Configuration Description In this step, we configurewhether the items of thereference document areproposed as selected onthe item selection list whenentering a document withreference, or not.

The user can delete thecheck marks manually on theitem selection list if she/hedoes not want to adopt someitems.

TCode Transactiontext

Prsl

MB11 GoodsMovement

X

MB1A GoodsWithdrawal

X

MB1B TransferPosting

X



8.13 Set up Dynamic Availability Check

Menupath

1. ImplementationGuideforR/3Customizing(IMG)®MaterialsManagement®InventoryManagementandPhysicalInventory®GoodsIssue/TransferPostings®SetupDynamicAvailabilityCheck

TransactionCode

OMCP


In thisstep, weconfigurethedynamicavailabilitycheck.

InInventoryManagement,two



types ofavailabilitycheck arecarriedout.

• availabilitycheckduringtheentryofreservations

• availabilitycheckduringtheentryofgoodsmovements

Thesystemcheckswhetherthematerialto bewithdrawnisavailableandissues amessage,ifnecessary.

Theavailabilitycheckis only



carriedout if:

• thematerialmasterrecordcontainsacheckinggroupfortheavailabilitycheck(MRPdata)

• acheckingruleisassignedtothetransactioninCustomizing

We candefine

• foreachmovementtypewhichtypeofmessageisissued(objectMovementtype)

• whichcheckingrulesaresupported(object



Checkingrule)

• percheckinggroupandcheckingrule:whichobjects(documents,stocks,materialrequirements)areincludedintheavailabilitycheck(objectDefinecheckingrule)

• pertransactionofInventoryManagement:whichcheckingruleapplies(objectTransactioncodes)

MvT 1. Val.

update

Qtyupdate

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

221 QL PA

221 X A

221 XK A

221 XQ A

221 XQ PA

This is anindicativetable.

CheckingRule

ChRDescriptionofcheckingrule



01Checkingrule01

02Checkingrule02

03Checkingrule03

ASDorder

AESDorder;make-to-orderstock

AQSDorder;projectstock

AVSDorder;returnablepackaging

AWSDorder;consignment

BSDdelivery

BBSDdelivery;customerstock

BESDdelivery;make-to-



orderstock

BOBackorderprocessing

BQSDdelivery;projectstock

BVSDdelivery;returnablepackaging

BWSDdelivery;consignment

DefineCheckingRule

TransactionCodes


ChRCheckingrule

CO27Pickinglist

MB11GoodsMovement



MB1AGoodsWithdrawal

03Checkingrule03

MB1BTransferPosting

MB26Pickinglist

MIGO_GIGoodsMovement

MIGO_TRTransferPosting

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 ®Goods Issue/Transfer Postings ®GeneratePhysical Inventory Documents for GoodsMovements

Transaction Code OMCC

Configuration Description In this step, we define for each plant andmovement type whether a physical inventorydocument is automatically generated whenposting a goods movement.

We can create a physical inventorydocument in addition to the materialdocument at the time of a goods movement.This function is important when inventorydifferences are posted from the WarehouseManagement System. These inventorydifferences are thereby documented inInventory Management with a physicalinventory document.



In order to create an inventory document inaddition to a material document for a goodsmovement, the following conditions must bemet:

In the plant, we must define the transaction/event type WV for automatically generatedphysical inventory documents.

We must define the document numberassignment for this transaction/event type.

Automatic generation of physical inventorydocuments must be allowed for themovement 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 Description In this step, we set the tolerance limits forgoods receipts.



When processing a goods receipt, thesystem checks each item to determinewhether the goods receipt varies from thepurchase order or the material master data.

The different types of variances are definedby tolerance keys. For each tolerance key,tolerance limits can be set per companycode.

The following variances are checked inInventory Management:

• Variance in the purchase order price quantity

(Explanation)

For this variance, two tolerance keys areprovided:

• Tolerance key B1 (error message)• We use tolerance key B1 to define the

maximum percentage variance. If thevariance is greater than the maximumvariance, the system creates an errormessage. The user cannot post thegoods receipt.

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

percentage variance from which awarning message is to be issued. It ispossible to post the goods receipt.

• Variance for the moving average price of thematerial

(Explanation)

We use tolerance key VP to define thepercentage variance from which a warningmessage is issued. This warning messageindicates 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


Configuration Description In this step, we specify whether theautomatic creation of storage location data isallowed for goods receipts.

This is advisable if we want to post a goodsreceipt without having to maintain thestorage location view of the material masterrecord in advance.


The storage location data is only created ifthe quantity is posted to 'standard' storagelocation stock. It is not created for receiptsinto a special stock (for example, into salesorder 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 Description In the R/3 System, account assignmentis predefined via the automatic accountdetermination facility.

When we enter goods receipts which areassigned to a cost account, we can enter theaccount manually. In doing so, we changethe account assignment predefined asoffsetting 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

Configuration Description In this step, we set the field selection for thegoods receipt movement types.

When entering a goods receipt, the fieldselection controls which fields (accountassignment fields) are

• ready for input ( optional entry fields)• have to be filled (required entry fields)• suppressed fields



In Inventory Management, the field selectiondepends on the movement type.


Menu path 1. Implementation Guide forR/3 Customizing (IMG) ®Materials Management ®Inventory Managementand Physical Inventory ®Goods Receipt ® MaintainCopy Rules for ReferenceDocuments


Configuration Description In this step, we configurewhether the items of thereference document areproposed as selected onthe item selection list whenentering a document withreference, or not.

The user can delete thecheck marks manually on theitem selection list if she/hedoes not want to adopt someitems.

TCode Transactiontext

Prsl

MB01 PostGoodsReceiptfor PO

X

MB0A PostGoods

X



Receiptfor PO

MB1C OtherGoodsReceipts

X

MB31 GoodsReceiptforProductionOrder

X

MBRL ReturnDeliveryfor MatlDocument

X

MBSF ReleaseBlockedStockvia Mat.Doc.

X

MBSL CopyMaterialDocument

X

MBST CancelMaterialDocument

X

8.20 Set Dynamic Availability Check

Menupath

1. ImplementationGuideforR/3Customizing(IMG)®MaterialsManagement®InventoryManagementand



PhysicalInventory®GoodsReceipt ®SetDynamicAvailabilityCheck

TransactionCode

OMCM


In thisstep, weconfigurethedynamicavailabilitycheck.

InInventoryManagement,twotypes ofavailabilitycheck arecarriedout.

• availabilitycheckduringtheentryofreservations

• availabilitycheckduringtheentryof



goodsmovements

The systemcheckswhetherthe materialto bewithdrawnis availableand issues amessage, ifnecessary.

MovementType

MvT 1. Val.updateQtyupdate

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

CheckingRule



ChRDescriptionofcheckingrule

01Checkingrule01

02Checkingrule02

03Checkingrule03

ASDorder

AESDorder;make-to-orderstock

AQSDorder;projectstock

AVSDorder;returnablepackaging

AWSDorder;consignment

BSDdelivery

BBSDdelivery;



customerstock

BESDdelivery;make-to-orderstock

BOBackorderprocessing

BQSDdelivery;projectstock

BVSDdelivery;returnablepackaging

BWSDdelivery;consignment

TransactionCode


ChRCheckingrule

MB01PostGoodsReceiptforPO

MB0APostGoodsReceiptforPO



MB1COtherGoodsReceipts

03Checkingrule03

MB31GoodsReceiptforProductionOrder

03Checkingrule03

MBNLSubsequentDeliveryf.MaterialDoc.

03Checkingrule03

MBRLReturnDeliveryforMatlDocument

MBSFReleaseBlockedStockviaMat.Doc.

MBSLCopyMaterialDocument

03Checkingrule03

MBSTCancelMaterialDocument

MIGO_GOGoodsMovement

MIGO_GRGoodsMovement



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


Configuration Description In this step, we can define that the R/3System automatically suggests

• the delivery completed indicator for goodsreceipts if the delivered quantity lies within theunder/over-delivery tolerance

The "delivery completed" indicator has thefollowing effects:

• The item is regarded as closed, even if thetotal quantity was not delivered.

• A further delivery is not expected, may,however, arrive.

• In the next goods receipt, the item appears onthe selection 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" indicatorhas not been set, an item is consideredclosed once the total quantity has beendelivered. This means that the "deliverycompleted" indicator is not necessary in thiscase.



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 Description In this step, we set the material shelf lifeexpiration date check for goods receipts foreach plant and movement type.

Prerequisites

The shelf life expiration date of a materialcan only be entered if:

• the minimum remaining shelf life is maintainedin the material master record

• The minimum remaining shelf life is thetime the material must still be usable,so that the goods receipt is accepted bythe system. We can define the time unitthe system uses in the storage data ofthe material master record in the ‘Periodindicator’ field.

• the shelf life expiration date check is active inthe plant

• the shelf life expiration date check is active forthe movement type

No expiration date check has been activatedfor ITZ.

8.23 Create Storage Location automatically for

automatic movements

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



Management and Physical Inventory ®Automatic Movements ® Create StorageLocations automatically


Configuration Description In this step, we specify whether theautomatic creation of storage location data isallowed for automatic goods movements.

This is advisable for goods movements viaShipping or when we post physical inventorydifferences, for example.


The storage location data is only created ifthe quantity is posted to 'standard' storagelocation stock. It is not created for receiptsinto a special stock (for example, into salesorder stock).

8.24 Set manual account assignment for automatic

movements

Menu path 1. ImplementationGuide for R/3Customizing(IMG) ®Materials



Management® InventoryManagementand PhysicalInventory ®AutomaticMovements® Set manualaccountassignmentfor automaticmovements



Maintenance of thisindicator is onlyuseful in conjunctionwith movements forwhich a G/L accountcan be entered oris provided by thecalling program.

In the R/3 System,account assignmentis predefined via theautomatic accountdetermination facility.

When we entermaterial movementsthat are assignedto a cost account,we can enter theaccount numbermanually. In doingso, we change theaccount assignmentpredefined asoffsetting entry forinventory posting.



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

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

Transaction Code OMJA

Configuration Description In this step, we set the screen Layout forautomatic 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 ®



Automatic Movements ® Generate PhysicalInventory Documents for Goods Movements

Transaction Code OMJC

Configuration Description In this step, we define for each plant andmovement type whether a physical inventorydocument is created automatically when agoods movement is posted.

In conjunction with automatic movements,please also note that this indicator is notset for goods movements which are createdfrom within a physical inventory since, inthis case, the physical inventory documentalready exists. This applies to movementtypes 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

Transaction Code OMBN

Configuration Description In this step, we specify the default values forthe 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 withreference to a reservation if the Movementallowed indicator is set in the reservationitem.



We are not using Reservations for ITZ.

Delete reservations

The management program sets the deletionindicator for reservation items whoserequirements date is earlier than the numberof days specified here.

Create storage-location stock dataautomatically for reservations

When this indicator is set, the storage-location stock data is automatically createdwhen a reservation is posted. This appliesboth to planned outward movements andplanned receipts.


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


Configuration Description In this step, we configure whether the itemsof the reference document are proposedas selected on the item selection list whenentering a document with reference, or not.



The user can delete the check marksmanually on the item selection list if she/hedoes not want to adopt some items

8.29 Set Dynamic Availability Check for Reservations

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



In this step, weconfigure thedynamic availabilitycheck.

In InventoryManagement, twotypes of availabilitycheck are carried out.

• availability checkduring the entryof reservations

• availabilitycheck during theentry of goodsmovements



The system checkswhether the materialto be withdrawnis available andissues a message, ifnecessary.


ChR Checkingrule

MB21CreateReservation

03 Checkingrule03

MB22ChangeReservation

03 Checkingrule03

8.30 Default Values for Physical Inventory

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


Configuration Description In this step, we specify the following defaultvalues for physical inventory for each plant:

Pre-settings for entering physical inventorydocuments

• the stock type (unrestricted-use, in qualityinspection, blocked)



• the indicator for batch determination (in theforeground or in the background)

• the unit of entry (stock keeping unit or unit ofissue)

These indicators are suggested as default values whenwe enter a physical inventory document. But we canalso change them there.

Pre-settings for entering physical inventorydocuments

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

displayed when we enter an inventorydifference without reference to thecorresponding document. But we can alsochange the default value here.

Note:

We only see this field when we enterinventory differences if we have activatedit in the step Field selection for physicalinventory.

8.31 Record Reasons for Goods Movements

Menu path 1. Implementation Guide for R/3 Customizing(IMG) ® Materials Management ® InventoryManagement and Physical Inventory ®Movement Types ® Record Reasons forGoods Movements

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

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

Transaction Code OMJJ

Configuration Description In this step, we can

• change the setting of existing movementtypes

• 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 – Valuationand Account Assignment

9.1 Split Valuation



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

Transaction Code OMW0

Configuration Description You configure whether split valuation isallowed at your company. If you generallyallow split valuation, this does not meanthat you must valuate each material on thisbasis. You decide whether to do so or notfor a particular material when creating thematerial 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 Description In split valuation, we can distinguishbetween partial stocks of a materialaccording to certain criteria and valuatethem separately.

• The material stock is divided according tovaluation category and valuation type:

• The valuation category determines how thepartial stocks are divided, that is, according towhich criteria.

• The valuation type describes thecharacteristics of the individual stocks.With the function "Setting" we can determine:

• which valuation categories exist in ourcompany (global categories)

• which valuation types exist in ourcompany (global types)

• which valuation types belong to whichvaluation category

• which valuation categories exist in avaluation area (local categories)

http://scn.sap.com/sapevent:DOCU_LINKGL:valuation_category

http://scn.sap.com/sapevent:DOCU_LINKGL:valuation_type



To select split valuation, proceed as follows:

1. 1. Determine the valuation categories andvaluation types that are allowed for allvaluation areas:

• 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 valuationcategory and select "Goto --> GlobalCategories --> Allocations --> Types->Category".

c) Activate the valuation types you want.

1. 3. Determine the local valuation categories foreach valuation area.

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

b) Position the cursor on a valuation areaand select "Goto --> Local Definitions -->Allocate Categories->Org.units". You obtaina list of the global valuation categories.

c) Activate the categories to be used in thisvaluation area.

The system creates the local valuation typesbased on the allocations under point 2.

sap mm configuration

Documents

plant stocks

material stocks

eachcompany code

companycode level

implementation guide

assign plant

plant isan

single company code