Mandatory Fields!(MM01)

Hi,
I dunt have a live system here...Can anyone send me the screen shots of the whole process of creation of a material? using MM01?
PLease its very very urgent..
I just want to know where these mandatory fields fall in which screens in the SD perspective.. in basic data1
sales org1 / sales org2/ sales/ general/ mrp1/ accounting 1
Material name
Gross weight
Net weight
Quantity
Division
Plant
MRP type
Availability check
Price
Material Description
Unit of measure
Valuation Class
Purchasing Group
Material Group
Profit center
Regards
AK

sales org 1:base unit of measure,material group,tax classification type.
sales org. 2:material statistic group,account assignment group,item category group
sales general: base unit of measure,availability check,transportaion group,loading group
mrp1:base unit of measure,mrp type,mrp controller,lot size,minimum and maximum lot size
accounting1: base unit of measure,valuation category(in case of split valuation),valuation class,price control,base on price control either moving price/standard price
regards,
indranil

Similar Messages

Badi for making gross weight field mandatory in MM01.

Hi,
Pls tell me the Badi for making gross weight field mandatory in MM01/MM02.
Thanks in Advance.

Hi!
if it is not working with customizing I would do it in this userexit (CMOD)
MGA00001
it is the user exit before saving the material master data.
have fun
Flo

Making Moving average price a mandatory field in MM01

Hello,
I've tried to make MBEW-VERPR a mandatory field in TC MM01, but with no success.
I tried using field selection (OMSR), screen variant (SHD0), making system message M3 131 an Error - nothing worked.
Please advice.
Thanks,
Dikla

Dear Lakshman,
You are right in what you are saying, and to explain the reason why I'm trying to make this field mandatory, I'll describe a scenario:
You have a Make To Order purchased material and you received an order for this material from one of your customers. You go out to purchase this material.
When you do GR for this PO, the PO price does not change the moving average price (MAP) of this material - it changes the sales order MAP of this material.
If, for some reason, the customer cancels his order at this point, you will do transfer posting to this material and change it from sales order stock to own stock.
We do this transfer posting with movement type 414 and that movement does not change the MAP of the material.
Now we have stock for this material, but with MAP zero.
If now we receive another customer order, we don't have to go out for purchase because we have this material in stock.
If we will use MvT 413 to allocate the stock to the sales order,
it will be allocated with price zero.
In this case, when we'll post the outbound delivery, no financial document will be created because the price of the material was zero.
I want to prevent this situation.
If the field is mandatory, even a price of 0.01 will be enough for the creation of financial document when I post a material document.
Dikla

BDC not inserting data in mandatory fields of MM01

Suddenly My BDC for sales maintenance View is not working as it is not inserting data in Mandatory fields.?can any one tell me the reason

Hi Satyanarayan,
1. Check ur code in debug to see if your internal table contains value in mandatory fields
2. Try executing BDC program online to figure out the problem....
3. Check ur code to see whether u r assigning values to this fields...
Let me know if these things are ok in ur code...
Enjoy SAP.

Mandatory fields!

Create Material Master Data (MMD) for Required Material ( MM01)
In the first Screen I am Entering the mandatory fields for creating a material
     Material
     Industry Sector
     Material type
After filling these details   , click on SELECT VIEWS
For MM point of view select , Basic Data 1, Purchasing , Accounting 1
Basic Data 1 :
Give the material description -
Basic Unit of Measure -
Material Group----
Division -
General Item Category group----
After entering it therethese values will be copied or take the same values in the next screen also But there would be some of the fields again mandatory like in Purchasing..
Purchasing :
Purchasing Value key -
Reminder 1, 2, 3 , Standard Del time Varience
Shipping Instructions----
Under delivery tolerance , Over delivery tolerance , Minimum delivery Quantity in %
GR Processing time -
Accounting 1 :
Valuation Class -
Price Control- If it is S( standard price give the Standard Price value )
--If it is V( Moving average price , give moving average price from which date)
After completion of these details save the data
Material has been created
Now before creating a material there are screen in SD point of view
So what are the remaining fields that are mandatory in SD point of view
Regards
AK

Hi AK
in material master the Screen and Field selection depend upon the Client requirement anyway
i would like to add more screen and field in continuation of thread
Screen-General plant data 1/2
Field - Profit Center
as far as material creation cycle is concern
Run TCode MM01
after that Select Material Type
and Industry Type
after that click OK you will get another screen of Department view
select as per your requirement
1-Basic data 1/2
2-purchasing View
3-accounting
4-General plant data
5- sales data1/2/3
by putting enter you will get another Screen in this screen you will have to define the plant storage location Sales organization etc.........
Thanks

Mandatory field for ABC indicator

Hi,
I would like to make the ABC indiator field to be mandatory on MM01 and MM02 transaction. I've tried to config this under SPRO and OSM9 but couldn't find the right group or object. Do you have any steps that can help me on this?
Thanks,
Tai

Background info.
The values of the field selection groups have been preassigned as follows:
001-110 Material master for industry
111-120 Reserved for customers (except where the values are already in use)
121-150 Material master for industry
151-210 Material master for retail
211-240 Reserved for customers 
Step by step
1. Transaction code OMSR. Change Selection Group to 211 for example. Save.
2. Transaction code OMS9. Enter 211 into Field sel. group. (MARC-MAABC now should be in a list of fields).
3. Double-click the relevant field reference. Say MM01.
4. Change MM01 to required.
5. Save.
Message was edited by: Vyerah Yende
to correct spelling
Vyerah Yende

MM Manage mandatory field in material master data

Hi,
i need to manage some fields in MM01 and MM02 in order to have these fields mandatory if other fields have particular value. For example, if material type is ZFER and Prod.hierarc (in Basic Data 1) is AL001, only in this case i want that field Comm./imp. code ,in view Foreign Trade import, is mandatory.
I'm looking for an user-exit. I find EXIT_SAPLMGMU_001 but with this solution i have a problem. The mandatory of field is active only during saving, on the contrary i would like that this mandatory will be similar to the standard.
Thanks for help,
Michele Garofalo

Hi,
I would like to make a field mandatory in Master Data.....how can i make a field mandatory field?
please provide me solution for this one
Cheers...

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

Dynamic mandatory field error message is not getting displayed in webui

Hi,
In Appointment if the importance is HIGH i made Location as mandatory.For this i enhanced BT126H_APPT/ApptDetails. In the get_p_location() method of BTACTIVITYYH i have written the code.
Now the problem is Error message for this dynamic mandatory field is not getting displayed in webui.
I debugged in DO_FINISH_INPUT error message is getting generated but it is not getting displayed in ui.
Can anybody tell where the problem is?
Thanks,
Hari.

Hi Hari,
Really sorry do not know how to convert this nug file to text
How ever quick solution for your problem would be just keep your validation in 'DO_VALIDATE_INPUT' method of the view controller.
Means even if the User clicks on SAVE , Since it fails here , it would not allow you to go further.
Thanks,
Rajesh P

Mandatory fields while using Group chart of accounts

Hi,
Which are the mandatory fields while maintaining GL accounts in FS00 if i am using Group chart of accounts.
And how attached these group chart of accounts gl to the operational chart of account GL.
raj

Hi,
the assignment from operational chart of accounts to group chart of accounts is done in OB13. Follow the steps in Customizing IMG FIn. Acc. (new) / Consolidation preparation (new) / General specifications / G/L and FS Charts of accounts...
Best regards, Christian

What are all the mandatory fields of the BAPI_PO_GETDETAIL?

Hi friends,
I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
Where should i look to identify the mandatory fields of a BAPI?
Thanks.
Senthil Nathan.

Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
Kind regards
Mikkel

What are the Mandatory fields????

Hi.... Experts...
Please spend your valueble time for me.... I can get back to you with 10 points....
Here I got a requirement to create contract with VA41 transaction...
But I am in confusion with feilds which should be must record...
Please guide me on mandatory fields of VA41 transaction....
Thanks,
Naveen.I

Hi,
When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
You will easily get to know the required fields to be entered for a given transaction.
Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
for this VA41, ther mandatory fields are-
contract type (VBAK-AUART)
Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
1st screen-
Sales Area(VBAK-VKORG)
Division(VBAK-SPART)
D.Channel(VBAK-VTWEG),
2nd screen-
Customer code(kunnr),
Contract validity,
material code(matnr),
quantity
plant(werks).
Best Wishes,
Chandralekha
Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM

What are the Mandatory Fields in Transaction ME51

Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIV

hi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena

Mandatory Field in ALV Grid

Hello,
i've a editbale alv grid.
Is it possible to set a field/colum as mandatory field?
Best regards,
TomSd

Hi,
Have a look at the report BCALV_EDIT_03.
In this report the program logic is such that if the user enters an incorrect value an error is displayed.
Instead you can check if the field of your ALV filelds are null and validate them accordingly.
Regards,
Sandeep

Mandatory field validation on Page links.

We have created a Portal application where we included different applications as taskflows. We have also created a tabbed interface which helps us to communicate from one task flow to another taskflow. When we are in one page of taskflow and try to move to another page of different taskflow using tabbed interface we receive mandatory field validation error which prevents us to move to any other page until we fill all the mandatory fields. We need to move to different page of taskflow by using the tabbed interface even without filling all the necessary mandatory fields. Can anyone help us to resolve this issue as this is very important for our project.

Layout
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<htmlb:content design="design2003" >
<htmlb:page title="Check Pernr " >
 <htmlb:form>
 <htmlb:textView text = "Personnel No."
 design = "EMPHASIZED" />
 <htmlb:inputField id = "pernr"
 value = "<%= lv_pernr %>" />
<%
if lv_no_pernr = 'X'.
%>
<script language="Javascript">
alert ("Personnel no. is not Valid")
</script>
<%endif.%>
 </htmlb:form>
</htmlb:page>
</htmlb:content>
ONINPUTPROCESSING
DATA: l_pernr TYPE persno.
DATA: data TYPE REF TO cl_htmlb_inputfield.
data ?= cl_htmlb_manager=>get_data( request = runtime->server->request
 name = 'inputField'
 id = 'pernr' ).
IF data IS NOT INITIAL.
 l_pernr = data->value.
ENDIF.
CLEAR lv_no_pernr.
SELECT SINGLE pernr FROM pa0000 INTO l_pernr WHERE pernr EQ lv_pernr.
IF sy-subrc NE 0.
lv_no_pernr = 'X'.
ENDIF.
PAGE ATTRIBUTES
lv_no_pernr TYPE FLAG
lv_pernr TYPE PERSNO
hope this helps.
A

Mandatory Fields!(MM01)

Similar Messages

Maybe you are looking for