Mandatory field in plant creation

dear cons
we want to make one field profit center as a required while creating plant. where is the menu path so that we can make it from optional to required.

Hi,
Follow the Path SPROLogistics - GeneralMaterial MasterField SelectionMaintain Field Selection for Data Screens.
Here you the options of amking the proft center field mandatory on Material type wise also.T-code OMS9
F4 on the upper side "Maintain Field Selection group" for Data Screens enter the field and goto find and enter the field name "PRCTR" and double click on the field selected and then enter.
Directly you can enter number 48 in the Field sel. group and enter and then double click on the table and field name a new screen opens make the field as "Requried Entry" and save.
The Goto MM01 and try to create the material the system will ask the profit center field to enter with error message..
Hope this may help you..

Similar Messages

Mandatory fields for plant address in SPRO

How do we set the mandatory fields when entering plant address in SPRO, i.e. in path : Enterprise Struct->Definition->Logistics general->Define plant?

This is based on country customizing.
IMG > Sap Netweaver > general setting > define countries > define country specific checks

Mandatory fields during PO creation - but optional in the customizing

Hi all,
If i create or change a PO, some fields are mandatory (ex: plant, account assignment category, purchasing group). However, in the customizing, theses fields are optional. I checked the customizing in tcode OMF4/field selection keys NBF, AKTA, AKTH, ME21N, ME22N, PT0F (we use standard item category). In all these field selection keys, the fields are optional.
Does anyone have any idea?
Thanks for your help.
Regards

The above mentioned by Manish is the correct way to check.
But sometimes it happens that you have copied some document type and created your own, then also changing in your new document type will not change the field setting. You have to change the setting in SAP default document type then only changes is reflected.
Eg: In PR document type which is generated from order standard SAP does not allow you to change Purchasing group, even if you copy this document type and create your own then also it will not allow. You have to change in the standard then only its results are reflected on the screen.
I hope this will help you
Enjoyyyyyyyyyyy
Akshit

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

Mandatory fields for creation of FB60(vendor invoice),and FK01(cost center)

Hi all,
can u plz send me the mandatory fields(along with discription) for creation of FB60(vendor invoice),and FK01(cost center).
thank u,
Srinivas Reddy.

The FK01 is the transaction used to create a Vendor.
The mandatory fields are:
a. NAME1: For Name
b. SORT1: For CUIT number.
c. SORT2: For alternative CUIT number.
d. CITY1: For city.
e. STCD1: Tax Number.
f. Others depending the case.
For FB60 (Vendor invoice) the mandatory fields are:
a. ACCNT: Number of Vendor Account.
b. BLDAT: Date.
c. XBLNR: Reference Number.
d. WRBTR: Invoice Amount.
e. HKONT: G/L Account Number.
f. WRBTR: Invoice Amount. The same as d but in the item.
g.MWSKZ: Tax Type. Depending the case.
h. KOSTL: Cost Center. Depending the case but is highly probable that the field were mandatory.
i. Others. Depending the case.
I have given to you the most probably fields that are mandatory for those transactions.
Your Sincerely
Leonardo Lopez
FI Consultant

Supress Mandatory field for Service Entry Sheet Creation

Hi,
I am using BDC for Service Entry Sheet creation as BAPI cannot fulfill the Business needs.
During Recording when I click on Service Overview and click on Service Selection we provide the Model Service Specification Number there I can see the Services and select it, but when I select the service and adopt, an error message ocuured to enter the quantity.
Is there any way to supress the standard error message without using acess Key.
BR
Aviram

Hi Aviram,
Messages type 'E' , 'I' or 'W' are controlled through configurations. Please check with your functional consultant with the message number you want to supress. It can be made as 'I' or 'W' through configuration.
Similarly if you do not want that particular field as mandatory field ask functional consultant to make it optional.
Regards
Sachin
Edited by: sachin G patil on Mar 9, 2011 3:13 PM
Edited by: sachin G patil on Mar 9, 2011 3:20 PM

Mandatory field in Production order creation field

Dea All,
I want to have a field mandatory at the time of production order creation. in CO01 Goods Receipt Tab there is a field of Goods Recipient in the second last row. Please guide me how can i make it mandatory field.

Dear,
Yes it is possible through the user exist, input check is carried out for enhancement PPCO0018.
User exit PPCO00018 should use ful for order header screens GENERAL ASSIGNMENT, GOODS RECEIPT and CONTROL tab.
Or go to SE51 enter program SAPLCOKO Screen No 5190 click on change and the Lay out here you can define it as Input field Take help from technical person.
Regards,
R.Brahmankar

Priority field mandatory for planning plant-order type

Hi
Is there a standard way through configuration that I may contol priority field in order header to be mandatory for some order types only in one planning plant?
Problem is that if I make the priority field mandatory for order type, it will be so for all the planning plants which i dont want. Also i dont want it to mandatory at planning plant level since there are many order types under one planning plant and requirement is to make priority field mandatory only for some order types under this plant.
TIA.

Hi Tehsin
Thanks for the reply.
In the transaction we can separately make it mandatory for either planning plant or order type.
My requirement is for combination of both.

One Time Customer Mandatory field during Sales Order Creation

Hi
My client has lots of one time customer and they need to capture the phone number and name of the individual customer at the time of sales order creation using one time customer code.
They want only "NAME & PHONE NO" as mandatory field so that the Person who creates a Salesorder should enter the NAME & PHONE NO" . Please let us know where the configuration for teh above is?
We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
Regards
Anis

Hi Anis,
In the Account group , if you check the one-time customer then while creating the sales order itself it will appear to change the address for that customer.
By the time you can enter your required fields.
I think you mentioned as
We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
Order creation and creation of sales order are both same.
May be you would have confused.
regards,
santosh

Materia Master field mandatory for specfic plant for a specfic mat type

HI,
I want to make one MARA-XCHPF field mandatory for a specific plant and specfic material type,If I Give Plant specfic Field referance and check the fiield as mandatory in OMSR for the field referance I have created If I mark it mandatory it become mandatory for all the material type,I want to make mandatory for some materials type only that too plant specfic
How to acheive this? kindly guide me
Kantha

Dear Kantha,
check this link may be useful to you.
Mandatory field per material type
Regards,
PK.

Sales Order Field "Delivery Plant" to be Mandatory

Hi,
In Sales Order VA01, the requirement is to make the field "Delivery plant" as mandatory field for particular document type called Tendor order ZTO. can i do this with Incompletion log or transaction variant or is there is any method to do the field mandatory using configuration.
Pl let me know who to go about this in details.
Thanks,
Regards
Ravi

Dear Ravishankar Mariyappa
In a sales order the delivering plant details is taken from these priority rules
Choice 1. CMIR of sold to party
Choice 2. CMR of ship tp party
Choice 3. MMR sales org data 1
According to me we will be mentioning in either one of these
In OBD2 we make delivering plant as a mandatory field for any new accont group so that it becomes a mandatory field in CMR
In MMR also thro OMS9 delivering plant in sales org data can be made mandatory
So far i have not seen practcally a sales order without a delivering plant in my experience
If you are talking about delivering plant in VA01 overview screen, then plant will never be there.
It has to be seen in item details shipping tab
Why it is not there in overview is, a sales order may have different items supplied or delivered from different plants hence it doesnt come in overview screen
It is always at item level
Without delivering plant shipping point cannot be determined and whole sales process comes to a stand still
Plant is maintained in master data and flows in sales order and that is it
Still i could not understand what do you mean by plant is not getting determined in your new order type ZTO always new order types has to be copied from the standard ones and to be modified according to your requirement
But Plant details will flow from master data only for any order type
Regards
Raja

Mandatory Field for Master Data Creation

Dear Experts,
How can I make "Street 2" Field as a Mandatory Field when I create Customer Master data (XD01) ?
Thanks in advance for your kind support.
Best Regards.
Ripon

Hi
KIndly go to the belwo path and choose Create customer centrally and make the street field mandatory
SPROFinancial accounting-Accounts receivable and accounts payable -Customer accounts-Mastr data---Define screen layout per activity (customers)
By doing above system will show mandatory for all account group when creating customer master thjrough XD01
If you want to do mandatory for account groupo the n go to t code OBD2
Regards
Damu

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

Making storage location mandatory for one plant.

Hi All ,
       I want to make storage location field mandatory in ME21N for only one plant .Like in our organisation structure two comp codes 1000 and 3000 are there .Under each comp code one plant like under 1000 1000plant is there and under 3000 3000 plant is there .I want to make storage location field mandatory for only 3000 plant during creation of PO.Is it possible ?
       Plz reply .

Hi Abhijit,
Suggestions:
        1) As per your last comment, new document type is used for doing PO for that particular plant. Check the Field Selection Group in the respective document type. (SPRO -> Materials Management -> Purchasing --> PO --> Define Document Type)
        2) Then SPRO -> Materials Management -> Purchasing --> PO --> Define Screen Layout at document level, Select the Field selection group. Then goto to Supplying plant and make the Issuing storage location as a "Mandatory field".
Note: But you can use this document type for this particular plant only. For the other plants, use the general document type.
          Please revert if you need any clarification.

Mandatory field in plant creation

Similar Messages

Maybe you are looking for