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/

Similar Messages

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

Field Selection PTFF not defined , error key : RFC_ERROR_SYSTEM_FAILURE

While executing BAPI_PO_CREATE1 by using Adaptive RFC Model in Webdynpro
I was facing the following Error
Field Selection PTFF not defined , error key : RFC_ERROR_SYSTEM_FAILURE
But while trying to create BAPI_SALEORDER_CREATE is working properly with the same configuration.
If anyone come accross this issue please help me out

This is beacuase of some issues in the parameters that are passed and is rectified.
krishna

Field selection PT0 not not defined

Hi All
I am creating purchase order i will checking the following error coming
" Field selection PT0 not not defined"
Thanks and regards
Deepa

hi,
Did you do any changes or deletion of the field reference key for the field maintainence of the PO..
this error comes when system doesn't find the field reference key maintained for the field maintenence for the combination of item cataory/document catagory...
check properly...
Regards
Priyanka.P

Field -RLTYP is not defined in ABAP-dictionary

Hello, gurus!
We have upgraded to ERP 6.0 (from 4.6c).
Now I have a problem with search help in TX.1
1. Transaction TX.1
2. F4 on the field KONTRH
3. Choose the "Partners by BP Role" tab
4. F4 on BU_PARTNERROLE
Next I see message "Field -RLTYP is not defined in ABAP-dictionary" instead of the roles list.
I appreciate any help!
Thanks in advance,
Anton.

I've found the solution!
Note 1525604

Jco error RFC adapter field PT F not defined

Hi Experts,
I am in a strange situation as I have become clue less on this issue
It is a file to XI to RFC scenario.. runs fine in dev environment
When I change the parameters in teh rfc communication channel to point to QAS it throws
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
pls help me ou ton this
Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

Hi,
First of all, can you please elaborate what you want?
secondly, why don't you transport your developments to QAS?
Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
Please check communication channel if you getting any error?
Regards
Aashish Sinha

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

SAPLMEPO control accounting tab field selection

The requirement has been given that when a PO is created with reference to another document that the accounting should not be able to be changed. On the surface this seems like a simple requirement. However I have yet to find a solution. Standard field selections seem not to show the accounting fields. The BADI ME_PROCESS_PO, which does cover modification of the accounting fields, is not open for customer implementation and the BADI ME_PROCESS_PO_CUST does not cover field selection for for accounting fields.
So am I forced to do an implict/explicit enhancment to LMEPOF3I?

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.

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

How to create user exit for MIGO check "item OK" Field select/unselect?

Hi All,
I want to know User Exit for MIGO Screen. when I click check button it will be show "Item OK " Field select or not.
MIGO Screen post if Item ok field select both parent id and line id . otherwise it will be show error message?.
Can Please every one tell me how to do user exit for MIGO?
mail id: [email protected]
thanks,
S.Muthu,

Hi,
check the BADI <b>MB_MIGO_BADI</b> ( method: POST_DOCUMENT).
COMD enhancment <b>MBCF0005</b>
Regards

Define Field Selection - PM Order

Hi,
We have Order types PM01 and PM02, processing for Planning Plants 1000,2000, 3000 and 4000.
Here for Planning Plant 1000,we have set up Equipment field, as mandatory for both Order type PM01 and PM02. This was set up through, Field Selection for Order Header Data, through Influencing Order type PM01 and PM02 and made Equipment as a mandatory field.
As this influencing field as made as per Order type PM01 and PM02, for Equipment as mandatory this is applicable for all Plants 1000,2000, 3000 and 4000.
Now we no need this Equipment as mandatory field in Order type PM01 and PM02 for Plant 4000. For only this requirement, can we make the influencing field for both Order type PM01 and PM02, for only Planning Plant 4000, not Equipment as a mandatory field.
This must not disturb the existing Equipment mandatory field for Order types PM01 and PM02 for other Plants 1000, 2000 and 3000.
Kindly provide your suggestions.
Raja.

Kutti Raja,
If you want to do this for all the order Types for Planning Plant 4000, you may achieve this by following Steps:
1. Go to Field Selection for Order Header Data and Reference Object (Plant Maintenance and Customer Service --> Maintenance and Service Processing --> Maintenance and Service Orders --> Define Field Selection for Order Header Data (PM))
2. Click on Influencing button and Double click on "Planning Plant".
3. Enter "4000" in Contents Fields and Select Radio Button "Input" instead of "Required" next to Equipment field.
For Rest of the Planning Plants Equipment will remain to be mandatory but for 4000 and all order Types, it will be an input field but not as Mandatory.
Hope this helps.
Chin2.

My app went from working fine to: Id field not defined for cfc Path.to.my.ORMCfCPag when I restarted

Hi everyone,
I have a CF9 ORM problem that I haven't been able to figure out and thought I'd see if you had any idea. I have seen a few postings talking about a "similar" problem but none of them correctly resolved this particular issue. I appreciate any help you can offer.
I recently created a CF9 app where I generated scripted ORM CFCs for my app using ColdFusion Builder. It worked great and my app was completely working. However, when I was adding some enhancements, I ran into an error when I restarted the CF app server. Here's the message I keep getting:
"Id field not defined for cfc Path.to.my.ORMCfCPage. Either the table should have a PK column mapped to a cfc field OR at least one field should be specified as id."
My App.cfc file only had orm enabled (no other mappings) when it was working. I've since tried specifying things like the cfc location etc. and it still hasn't helped.
// MORE DETAILS:
- When my app was working, I had moved it to 2 other servers. I had this error on both of those but not on my local copy. They all use the exact same database.
- The last change I made before the error was adding a generator="identity" field to my generated ORM beans. Once I got the message, I tried changing it back and restarting again but still got the error.
- I've also made sure all of the Adobe tags are in my web root (as suggested in a prior posting about this problem). I've search all over for a solution and nobody has a solution posted online that works so far.
Do you have any idea why this is happening?
Thanks!
Jeff

Quick thought and probably not relevant, but do you have this.ormsettings.savemapping set to true in your Application.cfc? I've fallen foul of this before - once CF has generated the hbmxml files and saved them to disk you can make all kinds of changes to your code which won't make a difference as it'll continue to read from the file versions, but only for certain properties and methods at times it seems.
Long shot I know, but I found CF ORM to be a nightmare for seemingly random caching.

Field symbol has not yet been defined-ALV Grid Display in Report

Hi all,
Iam calling a Function module for ALV grid display in Report programming. Its throwing the Error message Field Symbol has not yet defined. Can any one suggest what i have to do regarding it?

Hi,
<li> This is problem with fieldcatalog.
<li> Check field names or table name in small letters in quotes while building fieldcatalog internal table
<li> Check the fieldcatalog internal table , whether it has same fields as in data table which is shown using GRID_DISPLAY function module.
Thanks
Venkat.O

How do I resolve: Field Selection dialog [Pick... button] in "Mark as read-only" section of Signed tab for Digital Signature field is not working

I am using Acrobat Pro X on Windows 7 Enterprise x64 to create a form. When I have a simple form with a few fields, I am able to use the "Pick..." button to select the fields I want to select, but in a more complex form (20 fields with 3 Signature fields) The Field Selection dialog does not work. I can make the selections, but they are not saved. Removing fields does not resolve issue. IF I start with a blank form and add a few fields, the dialog will work, but after adding more, it quits working. Reader XI is also installed.

And that is why many responders use only the custom JavaScript calculation option.
The UI for the select fields and simplified field nations are only a way to pass field names to a JavaScript function that performs the actual calculation. Sometimes these functions call other functions and pass the parameters can lead to errors in the attempted code.
I would start to learn code JavaScript for Acrobat.
The pick field dialog is for performing calculations involving sums, products, averages, minimum, and maximum. I am not sure how that would work with a digital signature. Once a signature is applied the form fields could be locked.

Field in structure 'is not defined in the ABAP Dictionary'

Hi,
I have created an Infoset (SQ01) based on an external program and structure.
These two things are required.
However when I try to generate my Infoset I get an error message for each element in the structure I created in SE11.
The error is:
"<structure_name-field_name> is not defined in the ABAP Dictionary"
Each element in my structure gives this error yet I have defined this in SE11 as a structure and activated it.
These elements are included in my Infoset and as a field group in the infoset.
Has anyone come across this error before and knows how to resolve this problem?
Many Thanks
David

Hey,
I got the same prb.
Just reset the text buffers.
Rgds,
Martin

Field selection PT1L not defined

Similar Messages

Maybe you are looking for