How To Fix FE760 - Custom selection with field & is not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: FE - CO-PA module pool messages

• Message number: 760

• Message text: Custom selection with field & is not possible

What causes this issue?

Field &V1& is not included in the totals table for the classic General
Ledger GLT0 and therefore cannot be used for the custom selection.

System Response

A selection restriction based on field &V1& is not applied.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

For the custom selection, use only those fields that are included in
totals table GLT0.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FE760 - Custom selection with field & is not possible ?

  The SAP error message FE760, which states "Custom selection with field & is not possible," typically occurs when there is an issue with the selection criteria in a report or transaction that involves custom fields or custom logic. This error can arise in various contexts, such as when using custom fields in selection screens or when trying to filter data in a way that is not supported by the underlying data model.
  Causes:
  
  Invalid Field Usage: The field specified in the error message may not be valid for the selection criteria being used. This can happen if the field is not part of the underlying database table or if it is not allowed in the context of the report or transaction.
  Field Configuration: The custom field may not be properly configured in the system, leading to issues when trying to use it in selections.
  Data Model Limitations: The data model may not support the specific selection criteria being applied, especially if it involves complex joins or relationships that are not defined.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain fields or data, leading to this error.
  
  Solutions:
  
  Check Field Validity: Verify that the field specified in the error message is valid and exists in the relevant database table. Ensure that it is correctly defined in the data dictionary (SE11).
  Review Selection Logic: If you are using a custom report or transaction, review the selection logic to ensure that it is compatible with the fields being used. Modify the selection criteria if necessary.
  Field Configuration: Ensure that the custom field is properly configured in the system. This includes checking its data type, length, and any associated domain or data element.
  Authorization Check: Confirm that the user has the necessary authorizations to access the field and the data it represents. This can be checked in transaction SU53 or by consulting with your security team.
  Consult Documentation: If the error persists, consult the SAP documentation or help resources for the specific transaction or report you are using. There may be known issues or limitations documented.
  Debugging: If you have access to the ABAP code, consider debugging the program to identify where the error is occurring and what specific conditions are leading to the error.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.
  Community Forums: SAP Community and other forums can be valuable resources for finding solutions to common errors, as other users may have encountered and resolved similar issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SE37 (Function Module) for troubleshooting.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or development team for further investigation.