How To Fix FB478 - The user entries are ignored

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 478

• Message text: The user entries are ignored

What causes this issue?

You did not select the parameter "X - Data from trigger table".
However, specifications on the user are only needed for selection if
data in the trigger table is to be read.

System Response

The program ignores entries on the user. Data is selected directly
depending on the report by means of the select options "Company code",
"Account type" and "Account" or "Company code", "Document number" and
"Fiscal year".

How to fix this error?

Check your entry. If data is to be read from the trigger table, select
the corresponding parameter.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FB478 - The user entries are ignored ?

  The SAP error message FB478 ("The user entries are ignored") typically occurs in the context of financial transactions, particularly when posting documents in the SAP system. This error indicates that certain user entries or inputs are not being processed or are being disregarded by the system due to specific conditions or settings.
  Causes of FB478
  
  
  Field Settings: The fields that the user is trying to fill in may not be relevant for the transaction type or may be set as optional or not required in the configuration.
  
  
  Document Type Restrictions: Certain document types may have restrictions on which fields can be filled out. If the user is trying to enter data in a field that is not allowed for that document type, the system will ignore those entries.
  
  
  User Authorizations: The user may not have the necessary authorizations to enter data in certain fields, leading to the system ignoring those entries.
  
  
  Custom Validation Rules: Custom validation rules or enhancements may be in place that prevent certain entries from being accepted based on specific criteria.
  
  
  Data Consistency Checks: The system may perform checks to ensure data consistency, and if the entries do not meet the required criteria, they will be ignored.
  
  
  Solutions to FB478
  
  
  Check Field Settings: Review the field settings in the configuration for the transaction. Ensure that the fields you are trying to fill in are set as required or optional as needed.
  
  
  Review Document Type Configuration: Check the configuration for the specific document type you are using. Ensure that the fields you are trying to enter data into are allowed for that document type.
  
  
  Verify User Authorizations: Ensure that the user has the necessary authorizations to enter data in the fields. This may require coordination with the SAP security team.
  
  
  Examine Custom Code: If there are custom validations or enhancements in place, review them to ensure they are not inadvertently causing the issue. You may need to work with a developer to adjust the logic if necessary.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be known issues or patches available.
  
  
  Testing in a Sandbox: If possible, replicate the issue in a sandbox environment to test different scenarios and configurations without affecting production data.
  
  
  Related Information
  
  
  Transaction Codes: The error may occur in various transaction codes related to financial postings, such as FB50 (G/L Account Document Entry), FB60 (Enter Incoming Invoices), or FB70 (Enter Outgoing Invoices).
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on the specific transaction and its field requirements.
  
  
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP support team or consult with an SAP expert for further investigation.