Field selection layout - MM

Hi,
Can any one provide me the complete MM field selection layout. (want to maintain mandatory/supress fileds) for ex mmr, vmr, po, migo, miro and etc ..

hi
mat master OMSR and oms9
vendor master OMSG
now go to SM30 here use following objects
VV_162_B for pr and po
OMJX for MIGO
OB41 for miro
regards
kunal

Similar Messages

Field selection layout for MIRO

Hi,
I want to maintain the field selection layout for MIRO transaction (i.e i want to maintain mandatory/supress fileds for MIRO header data). Where i can manage......?
Thanks & Regards
Anilkumar Dalai

Hi,
Using the filed selection of the posting key, you can get the required effect.
Goto OB41, select the posting key 31 and change the field status as required.
Regards,

Transfer Purchase Order - Error message "Field selection ZTR not defined"

Hi all,
I've customized a new transfer purchase order type : TRA.
When I go to ME21N and choose TRA type, SAP displays this error message :
"Field selection ZTR not defined
Message no. ME028
The field selection required by the system is not defined in table 162.
Further processing is currently not possible."
How can I fix that please ?
Regards,
Bahia.

Hello,
Check in IMG - MM - Purchasing - Purchase order -define screen layout - Check any field selction ZTR has been configured. And also check in Purchasing - purchase order - define document types - your PO doc type has reference to field selection group ZTR - if yes change it..
Regards
Mahesh Naik

Purchase order field selection.

Dear All,
I have one query.
The filed selection for purchase order can be done only for some specific purchase organisations.
When I do field selection this field should reflect only for some specific purchase organisations.
Thanks in advance.
With Rgds,
Babu

the field selection key is assigned to Document type.
First create diff a Field selection key with the field combinations at
Spro > MM > Purchasing > Purchase order > Define screen layout ,
Then you nedd to create Many Document types as per your Requirement and then assign Field selection key for the doc type
Then Use BADI ME_PROCESS_PO_CUST and allow different Pur org & Doc types

Field selection in ME21n

hi,
I want to make batch field in T.Code ME21n as a mandatory field for those material manage in batches
Thanks
aMit Ranjana

u first see what is the field selection key assigned with ur PO document type thru spromm-purchasing-purchase order-define document type.
then go to spromm-purchasing-purchase order-define screen layout at document level---double click on the select field selection key,then double click on GR/IR control and make the field Batch as required entry.
regards,
indranil

Field Selection PT4B

Hi,
When i am creating a PR with Doc type RV & item category M it is showing me an error Field selection PT4B not defined.
How can i resolve the query?
Thanks
Anupam

I think you can define PT4B through spro@MM@Purchasing@Purchase requisition@Define Screen Layout at Document Level....But frankly since i haven't worked with RV document so i am unable to understand why this error is coming
Regards,
Indranil

"Select Layout" option in alv output

Hi All,
I have developed a ALV report.
In the output, on clicking the "Select Layout" button, a small window opens with some layout option/variant say "ZSLEB".
When i choose this layout, the output changes and takes the form of the chosen layout i.e. ZSLEB.
Now, on refresh, the alv output doesnt display this new layout, but goes back to the default layout/variant.
Actually, i am not passing anythin to the IS_Variant parameter in the ALV_GRID_Display FM.
I suppose i need to somehow manage to fetch the "ZSLEB" layout value during refresh and pass it to Is_Variant. Please help me in doing this.
Thanks & Regards,
Tejas Savla

Variant information
Description
This structure is only relevant if display variants are to be saved and/or read.
Variant information including the name of the list variant that is used to output the list.
To allow display variants to be read within the ALV, you must specify the acess path using fields REPORT (required field), HANDLE (optional field) and/or LOG_GROUP (optional field).
If you also want to allow display variants to be saved, you must additionally fill parameter I_SAVE accordingly.
See also the documentation on IMPORTING parameter I_SAVE.
A variant is uniquely described through:
The program to which the variant is assigned (REPORT)
The handle (HANDLE), if, for example, multiple lists with different structures and data are called in a program (I_CALLBACK_PROGRAM).
The handle is a CHAR(4) field that must be uniquely defined and describes the assignment of the call to the current structure of the internal output table.
Example:
Depending on the user interaction, several types of lists can be output in program x.
The user should be able to define display variants for each type of list.
You provide this function to the user by assigning a HANDLE to each list. If variants for the program and the handle are saved, the handle must not be modified any more.
The logical group, if, for example, the same list is created with different settings through various transactions (LOG_GROUP).
The logical group is a CHAR(4) that must be uniquely defined and specifies the assignment.
Example:
Program x is called through transactions T1 and T2. Depending on the transaction code, the fields available to the user through the field catalog differ in their assignment to different logical groups.
If variants for the program and the logical group are saved, the logical group must not be modified any more.
The user name, if user-specific variants are saved (USERNAME).
You do not have to fill this parameter manually since the variant name is unique.
The variant name (VARIANT).
You only have to fill this parameter if this structure is to be used to read a concrete variant and the list is to be output with this variant.
Value range
To call a list with a variant, you must specify the above fields.
Default
If the structure is initial, but saving is active (I_SAVE is not initial), then
IS_VARIANT-REPORT = I_CALLBACK_PROGRAM is set.

Use of field selection Key.

Hello
I am implementing the release strategy for the Purchase requisition. can anyone please tell me what is the significance of "Field selection key" and "Value change" under the release indicator.
Regards

Dear,
In the standard system, SAP will not allow changes to the quantity, unit of measure, or price when an approver is executing the release
transaction. If you require that other fields, such as delivery date, plant, etc., not be modified via the release transaction, this field selection key is useful.
Field selection key: If you want to allow certain fields to be changed during or after a release, you can modify the Field Selection Key. To modify the Field Selection Key, follow the menu path in the IMG: Materials Management > Purchasing > Purchase Requisition >
Define Screen Layout at Document level. Once you have created a custom field selection key, you should create a custom release indicator by maintaining a new entry in the u201CCreate Release Indicatorsu201D screen.
It is also possible to configure the release to not be restarted if the amounts have only changed a specified percentage. To do this, enter u201C4 - Changeable, new release in case of new strategy or valueu201D and a percentage in the u201CValue chgsu201D field.
Regards,
Syed Hussain.

Order of Precedence in Field Selection settings for Vendor Master

Hi,
There are three transactions which help define the list of mandatory, optional, suppressed and finally display only fields during vendor maintenance.
These are,
OMSG -> Define Account Groups and Field Selection( Vendor)
OMFK -> Define Screen Layout Specific to Purchasing Organizations
OMSX -> Define Transaction-Dependent Screen Layout.
All these settings are independently maintained.
In case of conflicting settings, say for example, Field Name 1 is made mandatory with tcode OMSG, but suppressed with tcode OMFK, how does the Vendor transaction(XK01, FK01, MK01) behave.
How are these conflicts resolved ?. Is there any order of precedence.
Regards,
Jeron

Hi,
If both purchasing organizations have separate account group then you can very well achieve in customizing otherwise you need to control it in exit SAPMF02K
Regards
Melih

User specific field selection ????

hi friends
i have an issue , i have to make some field optional or display for specific user in ME21N.
like quantity field will be in display mode for X user where as it can be changed by Y user (at ME22N).
regards
ravikant dewangan

Hi,
1. Go to SPRO > MM > Purchasing > Purchase Order > Define Screen Layout at Document Level > here define the Field Selection Key (For e.g. Z001)
2. Go to SPRO > MM > Purchasing > Authorization Management > Define Function Authorizations for Buyers > Function Authorizations: Purchase Order > Here "New Entries" and define Function Authorization Key as "01" and give description.
Here you can maintain Field Selection Key "Z001" in FieldSel. option
3. Now go to SU01 > Enter User ID > Parameters Tab > Here for Parameter ID EFB i.e. Function Authorization: Purchase Order, maintain value "01" and check in PO field selection will get applied for that user.
Similary you can define many Field Selection Keys and Function Authorization keys and maintain in user masters.

Field selection for Account Assignment Tab in PR

I set up my own field selection key where only storage location can be changed after release.
But when I do the test, I found that not only the storage location field but also all the fields in Account Assignment Tab can be changed!!! (Like cost center, profit center and GL account etc)
So, please help me to control the fields in Account Assignment Tab. I can't find related setting.
Thanks a lot.

You guys misunderstood.
Here's my business flow:
I enter PR with account assignment K, input cost center and then save.
After PR is released, there's only storage location can be changed.
So I set up my own field seletion key in which I set storage location as optional, and other fields as display.
But when I use ME52N to check my released PR, not only storage location but also all the fields in Account Assignment Tab can be changed!
I can't find the corresbonding setting for cost center or GL account in "Define Screen Layout at Document Level".
I can't use OME9 either, because once I set cost center as display, I have no change to enter even if I use ME51N.
Sorry I didn't make myself clear enough. Hope you understand now and please help me to solve it. Thanks a lot.

Field References, Field Selection Group & Screen Sequence

Dear Experts,
Please whare are the importance of field References, Field Selection group & Screen Sequence? How do i use them?

Hi,
These are Object based (Like Material master, BOM, Routing etc..), so depending on how you want the screen layout and how you want the mandatory/optional field defination you can define it here.
Regards,
Prasobh

Field selection on PO

Gurus,
How can i get the following fields show up on the PO. What is the field selection that needs to be changed. I am trying to get the fields for free text items for non stock PO's
Condition control tab: PR Date Category
                                Condition group
                                Price Date
                                No cash Disc (Check box)
Thanks in advance
MV

Hi,
Spro>Materials Management>Purchasing>Purchase Order>Define Document Types
Here check the "Field Selection Key" against the PO doc type
(ex: Standard NB doc type the "Field Selection Key" would be "NBF")
Then go to
Spro>Materials Management>Purchasing>Purchase Order>Define Screen Layout at Document Level
Select the " Field Selection Key" of ur doc type..Just Double click on that
Select your fields and against that field you can see three options, Reqd.entry Opt. entry Display...
Thx
Raju

Field selection for order

Hi all
Can I know use of custumization trxn OIXW and OIRS (Field selection for order and sub order data field.)
My assumption was that when I make sequence chane in OIXW then tht will reflect in IW38/IW39.
but it is not so.
Basically I want to araange column sequence in Iw38 as per my requirement. instead of creating layout is there
any other procedure ?
Regards,
Prasad

Hi,
Any changes you make in field selection through OIXW or OIRS will reflect in IW38/IW39 as a global default variant.Any user variant created as default variant will have priority over this.So make it sure that this default variant is Protected one so that no one can chnage as you want this to be global variant.
regds,
atul

Field selection PT1L not defined

Hi,
We have configured a new document type and field selection for scheduling agreement. When we tried creating an SA, system prompted "Field selection PT1L not defined" error. What does the error mean? How do we go about it?
Please advise.

Hi,
PT1L is something whose use is not at all logical the reasons are and thus not defined in standard SAP
1> From the term PT1L it represents Limit item (i.e Blanket ) for Scheduling agreement
2>Now we use SA to work with schedule lines but for Limit items there no GR or any goods receipt so what is the use of SA in this case better you go with PO.
3>obviously you can create PT1L by copying any other existing field selections in (but I would suggest not to do this)
OLME ->Scheduling agreement ->Define Screen Layout at Document Level
Also read this
http://www.sap123.com/a/41/

Field selection layout - MM

Similar Messages

Maybe you are looking for