Material Master Layout

Hi Experts,
I have to maked two fields in material master as mandatory fields in all material type.
moving average price and standard cost price, how to do in spro.
Regards
Ishu
Edited by: Csaba Szommer on Jan 7, 2012 12:53 PM

Hi,
If you satisfied with answer then you must do the following things:
1. Close the thread, so others can understnad no more discussion on this thread.
2. Give the points to solution provider

Similar Messages

Screen layout for pr and PO in respect to Material master

Dear Experts,
I know that we can control the screen layout display, optional... with respect to document type...
But there is one requirement... When there is BATCH activated for the material... in Material master( batch avl) the "batch" field in PR.....Item details >Material Data needs to be optional field.. (possible to enter value)..
When material is not not acivated for batch.. then that field to be Display only(Not possible to enter value)
pls guide me is this possible.. ?

Hi,
This can be done with both customizing and specific developpement.
In SPRO: Materials Management/Purchasing/Purchase Order/Define Screen Layout at Document Level, you can define new fieldselection key (allways define new one as copy of standard in order to copy the document type).
Then you can define your own strategy to assign fieldselection key to a purchase order item in BADI ME_PROCESS_REQ_CUST method FIELDSELECTION_ITEM_REFKEYS according to the item data
This user exit allows you to had new fieldselection keys.
- CH_KEY0 is used for the transaction (in ME51N the fieldselection key is ME51N)
- CH_KEY1 is used for the activity (in creation mode the fieldselection key is AKTH)
- CH_KEY2 is used for the document type (defined in customizing for each document type)
- CH_KEY3 is used for the line type (if the item type is standard the fieldselection key is PT0B)
- CH_KEY4, CH_KEY5 and CH_KEY6 are free to use
Keep in mind that the system take the union of all fieldselection key. If a field is changeable in fieldselection ME52N and PT0B but not in AKTH then it will not be changeable.
Hope it helps
Regards

Workflow for Material Master and Vendor Master Creation

Hi
Has anyone mapped creation of Material Master & Vendor Master through SAP Workflow.
Seek your valuable inputs.
Best Regards
--Vikas

You may not get the complete standard form which will match this functionality. But you can develop your business logic in custom code for fetching the data and the interface and use the standard templates for layouts if any template matches your requirement. You can see the complete lest of templates in : "transaction SFP->Form->Layout->Tools->Template Manager
Most of the common templates are available here.

PR, PO, GR for a consumable material without material master record

Hi,
I have created a complete cylcle till Invoice Verification for a material without a material master record.
But i have one query i.e. in the cylce i created i had to create a GR before entering MIRO. Is there any way by which i need not create a GR for a consumable material i.e. to be posted directly to a GL without any inventory management.
In my case, the GR checkbox in the PO was automatically ticked.
Can anyone help on this please.
Regards,
Laxmi

Customizing Error Message in ME23N
When displaying of modifying Purchase Orders with a document type of Framework Order, a user selects the LIMITS tab, they get the error message Customizing incorrectly maintained, message number SE729.
The problem is caused by version upgrades of the SAP software.
Number of entries in table T162V is different to the number of columns in table control for screen SAPLMLSP (400). You can use screen painter SE51 to display the screen. View the Element list for TC_VIEW.
The list of fields can also be viewed within the program. Transaction code ML81N (service entry sheet), program SAPLMLSR. Click on the Configuration button (top right hand corner) select Administrator. This shows the number of fields as 67.
Using SE16N to view table T162V shows 69 fields. This table contains six layouts (variants), they must all be the same. Before the change the total count was 414 (69 x 6).
The ME23N transaction only checks that the number of entries is correct. You will notice that the fields are not in the same sequence, but that should not matter if you donot use the service transaction ML81N and it is not a selectable tab on ME23N.
Transaction SM31 was used to delete the extra fields. As this is a SAP table, you may need extra authorisations to make the change.
Note: the number of fields shown above will be different in each site. This is because of different SAP versions and in what software is loaded.

Material Description to be overwritten in PR/PO from material master

Hi,
when we create a PO/PR from ME51n and ME21n the material description field is mandatory hence inspite of making setting as display only in SPRO the inital screen will except any description and will save it.
Is there any thing else by which the description data can be overwritten from material master so that even if the user enters any xyz description the system overwrites it from the material master.
Regards,
Reena

Hi,
You can very well achieve it by making the field "Material description" a "Display" field in the IMG path: Maintain screen layout at document level
However, you have to use the right "Field selection key" to make the screen changes. For eg. for NB purchase order, the field selection key would be NBF and not ME21N.
The field selection key that is applicable for the document type can be found in "Define Document types" img activity.
I have checked this and it works perfectly fine for both PR & PO.
Once you enter the material number in PR (or PO), the material description is brought from material master and then the field is greyed out. (thought initially the matl. description field looks editable).
<< Moderator message - Point begging removed >>
Cheers.
Prabhu S
Edited by: Rob Burbank on Nov 24, 2011 10:24 AM

LSMW Material Master - create several valution types within one Run

Hello @ll,
i created a LSMW for material master migration, and i would like to create up to 4 different accounting views (based on different valuation types) within one LSMW Run.
As there is the Field BWTAR on Structure BMM00, and the accounting fields on Structure BMMH1 i dont know if:
1. this is possible in general with LSMW and
2. if possible where i have to set the "transfer_record" commands...
Does anybody have experience on this?
BR,
Gregor H.

I never used the standard batch input method, so I cant answer this part. But with IDOC as import method I do this right now and it works without any problem
The transfer record command is set in the section of processing time __END_OF_RECORD__
you can display this section when you are in field mapping and conversion rules. choose from menu Extras > Layout and activate all boxes.

Text linkages from material master to purchase requisition

I already set the text linkage between basic data text in material master with item text in PR. I left fix indicator blank since I want the text to be adopted automatically.
I run MRP and create planned orders. Then I convert planned order to purchase requisition. Material master basic data text is not shown in purchase requisition. I tested using N and * and they both show. With N it shows (reading from material master) and I accnot modify it. With * it shows but I have to adopted to actually store the text as part of this document. With blank is not working. We want the text from material master to be automatically adopted in PR without manual intervention as with *.
Thanks and regards, Jose Oyon.

Hi
If got ur query correctly : you want to make short text field in Preq as Display.
If yes then go to Tcode OLME (or SPRO) -> Purchase requistion->Define Screen layout at doc level->select ME51N--->double click basic data, item and make short text filed as display.
regards
rahul.

Material Master External Number Range problem

Material Master External Number Range that allows numerics only and combo of numerics, Alpha and Characters
I have the following issue. My client wants to use a purely External Numbering System in SAP
- They only use one Material Type (HALB).
The range must be able to manage material numbers that:
1. Are up to 18 CHAR
2. Have Leading Zero's(Numeric Only) - example 0123, 0000223, etc
3. Purely numeric (no zeros) - ex 56788, 1235456
4. Have Leading Zero's with (Alpha Numeric) - ex 00A456
5. Alpha numeric (No Zeros) ex T123542
6. Leading Zero's with a '.' in the Mat Number
Four examples
005.009.23
0000A.123.5544 M1
000.593.33234
0.1234
I have the Lexiographical Setting Checked
Leading Zero's Checked
Range is - 000000000000000000 to ZZZZZZZZZZZZZZZZZZ
The issue I have is with the last two examples in 6 above 'Leading zero's with a '.' in the Mat Number.
It seems the system has an issue with zero's then a decimal point without having another number of letter in between. It will allow 00000002.1223 but not 000000.1223. The only way I can get the system to take the leading zero then '.' entries is to check 'X' the 'External Number Assignment w/o Check in the Material Type HALB. When I do that I am no longer allowed to create purely numeric numbers. Any help?
Creating another material type is not an option. Also the '.' can be in any position in the layout.
Thanks in Advance!
--Chris

ASCII and UNICODE values of period (.) are lower that 0.
Solution: Change your number range like this
From
Range is - 000000000000000000 to ZZZZZZZZZZZZZZZZZZ
To
Range is - - - - - - - - - - - - - - - - - - to ZZZZZZZZZZZZZZZZZZ
(replace zeroes with hyphen, because the value of hyphen is lower than period)
[ASCII table|http://www.asciitable.com/] for reference.
Edited by: Jeevan Sagar on Nov 29, 2011 1:04 PM

Custom fields on Material Master - ECC6.0

Hello
We have added custom fields on material master basic data screen following these steps :
1) Copied Func. grp MGD1 to Z Fgrp via Spro -> Logistics General ..
2) Created a subscreen in Z fungrp by copying screen from original program.
3) Deleted the unwanted fields and added new fields to the layout and Fields in PAI.
4) Attached the subscreen in screen sequuence via SPRO
We are now able to see the new fields on the baisc data screen and also able to input data in these fields , but on SAVE the data is not getting saved to database table MARA.
We have also referred to OSS note 44410 but with no help.
Are we missing something , is there anything additional that needs to be done in ECC6.0 ?
Thanks

Hi Kalidas,
In your customized subscreen, did you update the PAI to include your custom field?
process before output.
* Verarbeitung vor der Ausgabe
module init_sub.
module get_daten_sub.
module feldauswahl.
module sonderfaus.
module sonfausw_in_fgruppen.
module feldhistorie. "Aenderungsdienst
module bildstatus.
module zusref_vorschlagen_b.
module refdaten_vorschlagen.
module zusref_vorschlagen_a.
module set_daten_sub.
process after input.
module get_daten_sub.
* Put your custom fields here to copy to structure for saving
field: mara-zzcustom.
module set_daten_sub.

Add fields to material Master (MM01)

Hi Experts, after checking OMS2, OMS3, OMS9, OMSA...I still have no idea about how to show some fields in my material master data. They belong to group 103 which is assignet to material type FERT and Basic Data 1. They are setup as "Optional" but they are not shown when I try to create a new material.
I expected to find it easy to solve, as when you modify others screen layouts (p.e. Materials Management> Purchasing>Purchasing Info Record-->Define Screen Layout) but it seems not. Any idea?
Thank you

Hello Cristian,
You cannot define the field selection for an individual field, however,
the fields are grouped together in field selection groups.(Customizing
'Assign Fields to Field Selection Groups') The input/output attributes
are determined per field selection group.For the specification of the
properties of a field selection group, there are several criteria. They
are called field selection references.Not only one criterion (= field
selection reference) is relevant for the definition of the field
selection attributes but SIX criteria are.
Some of the field selection references are hard-coded (for example,
transaction) others can be defined (for example, plant, material
type...).In the following, the six field selection references are listed
and also the transactions in which they can be defined.
1. Transaction (MM01, MM02 ....)
2. Industry sector (you can assign the field selection reference to the
    industry sector by using Transaction OMS3)
3. Material type (You can assign in field FELDREFERENZ by using
    Transaction OMS2.The name of the material type is not automatically
    the field selection reference but it depends on what is on field
    FELDREFERENZ in Transaction OMS2.If the field is empty, there is no
    specific settings for this material type.)
4. Plant (you can assign the reference to the plant in Transaction
    OMSA)
5. Procurement-releated field selection references. There are the two
    field references E (internal procurement) and F (external
    procurement). It depends on the settings in Customizing for the
    corresponding material type under 'Internal/external purchase
    orders' whether one or which one of the field references is used. If
    internal purchase orders are allowed (setting 1 or 2) and external
    orders are forbidden (setting 0), the field selection uses E. If
    external purchase orders are allowed (setting 1 or 2) and internal
    orders are forbidden (setting 0), the field selection uses F. When
    both internal and external purchase orders are allowed, the field
    selection uses neither E nor F.
6. Customer-specific field reference KB (customer-specific
    requirements)
Since a field can have only one attribute at the end (display = '*',
change = '.', hide = '-', required entry = '+') a property must be
determined from these six criteria.You do this by prioritizing the
above-mentioned properties:
The hide function has a greater effect than the display function.The
display function has a greater effect than the required entry function
and the change/ready for input function has the least effect.
If for one of the six mentioned field selection references 'Hide' is
set for the relevant field selection group, all fields which were
assigned to this field selection group are hidden, no matter how the
attributes were set in the other five field selection
references.Therefore, you must always check all six field selection
references.It is not sufficient just to look at one field selection
reference.
If you checked this setting and, however, the field does not have the
display attribute required, then it is possible that the attributes of
the field are hard-coded.
Regards,
Mauro

Step by step instruction for Using LSMW Recoding method for Material Master

Guys,
Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..
Thanks guys,
Dhanu.

Hi,
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
The LSM Workbench covers the following steps:
(1)Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files)
(2)Convert the data from source format to target format
(3)Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
The Steps for LSME are:
Example: Customer Master upload:
LSMW to Update Customer Master Records with Transaction Recording
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Step 2. Maintain Source Structures
Give a name and a description to the source structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field
Step 4: Maintain Structure Relations
Execute a step to u2018Maintain Structure Relationsu2019. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose u2018Sales viewu2019 for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of u2018Xu2019.
If your source file already has the field value, you choose rule u2018Source Fieldu2019.
Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.
Step 8: Assign files
Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.
Step 9: Read data
In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.
Step 10: Display read data
This step is optional. If required, you can review the field contents for the rows of data read.
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates.
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Follow the link for material master
http://www.sap123.com/showthread.php?t=98
Regards,
Biju K

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

Copy of Material Master charac. values to the batch classif. in GR for PO

Dear gurus,
Could you please help me with the following issue. I have a material managed in batches, and it has a classification type 023 in material master. I fill one chaacteristic of this classification with some value. Now I want this value to be copied to the batch classification during the creation of new batch while making GR to production order.
Is it possible?

Hi Nikolaj,
What I am understand your requirement is like,
You want to fetch the value of Characteristic maintain in Batch class in Material master to the Batches, correct?
But my Friend if you maintain value of characteristic in Batch Class in material master then it will works as a validation.
For Example,
Suppose your Characteristic is Colour and in Material Master Batch classification view you have maintain value as Red.Then system will not allow you any other colour in Batches.You will find that value in Drop Down list.
Regards,
Dhaval

Automatic creation of Material Master at the time raising the PO !!!

Hello All,
I am stuck in a scenario of our client which should be implemented (or mapped) in SAP.
Scenario: At the time of creating the PO (in there legacy system -in house developed) they can choose the items from the existing master data or/and they can also add a new item (which is not present in the master data records at the time of creating the PO).
Now as soon as the system realise that a new item is inserted into the PO, it will create that item record automatically in the backend (database) and the master data will be present from there on.
The items they are dealing with are all fashion accessories and they generate order on the following basis:
1. Demand of particular item in market.
2. List of items provided by the vendor.
3. Based on the requirement in there outlets.
So for them its very difficult to fix there master data records, as it can be changed daily or monthly as per the market conditions. At the same time every time they order, its almost around 100 different items (some time 80 of them are new) in a single PO so they cannot create 80 records manually each time.
These items are not consumable material so obviously they are maintaining the stock for them. They are also not going to use IS Retail.
I am not at all sure how can we map this particular practice in SAP, it would be really appreciated if any one could help me on this problem.
Please let me know if you need any other details from my side.

Hi,
As you have two different systems one in house developed and another SAP, and the PO creation part starts from Legasy system which creats the PO in SAP, you can do some development as per below
1: While Passing the details from legasy to SAP, use two columns in legasy one will contain the Material Code of ECC (for laready exist material ) and another for deescription of material.
2: In case material is new for which there is no material master in ECC pass only description from legasy systems.
3:While getting triggred from Legasy to ECC to create the PO, first check whehter all the material code exists or not in ECC.
4:If some material are not created (only description present) for those material first create the Material Code using BAPI 'BAPI_MATERIAL_SAVEDATA'.
5: Aftre creation of Material code create the PO using BAPI ' BAPI_PO_CREATE1'.
6:For the new created material , trnasfre the master record from ECC to Legasy systemso that next time user can see that material in your legasy system.
Regards,
Zafar

Creation of material master

Dear all,
While entering of MM01, MM02, MM03 T codes, The system showing the error message - "Record Y1 01 does not exist in Table T133A" - for this what do I do, Plz suggest.
reg
Vishnu.Ch

Hi Madhu,
Thanks for your reply. But, I have one more doubt. For non stock materials, we
will specify the cost centre and G/L account at the time of creation of Purchase order. Then, do we have to specify the valuation class at the time of creation of
Material Master since there is no automatic account determination?
Regards
Yoga

Material Master Layout

Similar Messages

Maybe you are looking for