How To Fix EI228 - Due to missing authorizations, not all entries are displayed

SAP Error Message - Details

• Message type: E = Error

• Message class: EI - Foreign Trade: Gen. Output

• Message number: 228

• Message text: Due to missing authorizations, not all entries are displayed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message EI228 - Due to missing authorizations, not all entries are displayed ?

  The SAP error message EI228, which states "Due to missing authorizations, not all entries are displayed," typically indicates that the user does not have the necessary authorizations to view certain data or entries in the system. This can occur in various SAP modules, such as SAP ERP, SAP S/4HANA, or SAP BW, depending on the context in which the error arises.
  Cause:
  
  Missing Authorizations: The primary cause of this error is that the user’s role does not include the necessary authorizations to access specific data or transactions.
  Role Configuration: The roles assigned to the user may not be configured correctly, or the necessary authorization objects may not be included in the role.
  Data Restrictions: There may be restrictions based on organizational levels, such as company codes, plants, or other criteria that limit data visibility.
  
  Solution:
  
  Check User Roles: Verify the roles assigned to the user in transaction code SU01 (User Maintenance). Ensure that the user has the appropriate roles that grant access to the required data.
  Review Authorization Objects: Use transaction code SU53 to check the last authorization check. This will show which authorization objects were checked and which ones failed. This can help identify what specific authorizations are missing.
  Modify Roles: If necessary, work with your SAP security team to modify the user’s roles or create new roles that include the required authorization objects. This may involve:
  
  Adding specific authorization objects related to the transaction or data being accessed.
  Ensuring that the roles cover the necessary organizational levels.
  
  
  Testing: After making changes to the roles, have the user log out and log back in to see if the issue is resolved. It may also be helpful to test the access in a development or quality assurance environment before applying changes in production.
  Documentation: Ensure that any changes made to roles and authorizations are documented for future reference and compliance.
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that pertain to the transactions or data the user is trying to access. Common authorization objects include S_USER_AUTH, S_TCODE, and others specific to the module in use.
  SAP Security Best Practices: Follow best practices for SAP security, including regular reviews of user roles and authorizations to ensure compliance and minimize security risks.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorizations or provide guidance on best practices for role management.
  
  If the issue persists after checking and updating authorizations, it may be necessary to consult with your SAP Basis or security team for further investigation.