SAP MM Support Problem Solution

Lock a field in material master from change

You have a requirement to protect the field MARC-SERNP 'Serial number profile', found within the material master data 'Sales General/Plant' and 'Plant data / stor.2' tabs, from being changed by all but two employees.

How can you restrict change access to the material master data views entirely through authorisation settings or any other good method to control this?

Answer:

A couple of options are:

1. Create a transaction variant with that field as display only. Assign variant to a custom z-tcode and distribute (cons are that most users use the custom z-tcode).

2. Work with a developer to use the enhancement framework to restrict that field to display only unless users have additional auth (e.g. new auth object or re-used existing).
 

How to edit the description name of a storage location?

It is very simple, go to OX09 and straight away you can change the Storage location name. Only thing is that you should have access to change it and in view mode it is greyed out and not possible to change. If you want to change the address of S.Loc, select the desired S.Loc double click on address folder in left side, it allow you to maintain the address too.
 

Is it possible to maintain the same material master with same code in all plants in a company. Our client is using same materials in all their four plants?

Material numbers are always maintained at Company code level. If you look at the Material master data, some data is maintained at Company code level, some at Plant level and some at Storage location level. If you have all the 4 plants attached to one company code, they should have the same material number. What you need to do is to extend the material to all the 4 plants if thats your requirement. Also, if you have your valuation area as your Plant, then you have the flexibility to maintain Plant specific pricing for the same material.

You can use MM01 T code to copy material from old plant to new plant. But check for the required details in your new plant and make changes accordingly. 

Where we do the configuration for the cost centre allocation, because whenever we GR a material, accounting document is created for that particular material.  How that particular material go in to the particular accounting (G/L account)

In Tcode: OBYC  -- Automatic Postings. 
     for Inventory Posting Trns Key is: BSX
     for Off setting entries like Goods issue, initial stock......Trans Key is :  GBB

Based on the Movement types, Valuation class it will be assigned to a G/L account.
You can refer the configuration in Tcode: OBYC
 

Could any one can explain complete configuration of pricing procedure & application.

The Basic thing is Condition Technique. In which there are 
1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table. 

A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a  Condition Technique.This is a simple logic 

Here the Condition Type is very important like PB00, PBXX,RA01 etc. 
In the background every Condition Type has its own defition means the purpose of the Condition Type  like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.  Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement. 

The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement. 

The Pricing Schema means the calculations procedure of Condition Type. 

Ex.  RA01 - Discoount % is caclulated on PB00 - Gross Price  means 
RA01 is based on PB00  like that we have to define in the Pricing Schema
which makes easy to use in real time. 
Here PB00 has the Access Sequence - 0002. 
But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types. 

In the system, by default some standard  Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define. 

For the configuration, I may not able to explain properly through here but will give some idea. 

Configuration: SPRO - IMG - Material Management - Purchasing - Conditions - Define Price Deternmination Process:
1. Define Access Sequence 
2. Define Condition Type 
3. Defince Calculation Schema:- Here you have to define the Schema - Define Schema group 
1. Define Schema Group vendor 
2. Define Pricing Schema group 
3.  Schema group for Purchase Organisation 
4. Assign Schema group to Purchase Organisation - Define Schema determination 
1.define calculation schema for Standard purchase organisation 

After completion of the Schema Group, we have to assign it to Vendors. 
Then whenever we use any transaction with this Vendor, the concerned  Schema will work as configured by us. 

The Pricing in MM is vast because each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above. 

See also
History Changes On Reservation

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.