/ISDFPS/FDP848 - Error reading IT 1953 records. No authorization?

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/FDP -

• Message number: 848

• Message text: Error reading IT 1953 records. No authorization?

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.

AnswerBot

• What is the cause and solution for SAP error message /ISDFPS/FDP848 - Error reading IT 1953 records. No authorization? ?

  The SAP error message /ISDFPS/FDP848 Error reading IT 1953 records. No authorization typically indicates that the user does not have the necessary authorizations to access the specified data or transaction related to IT 1953 records. This error is often encountered in the context of SAP's Flexible Real Estate Management (RE-FX) or similar modules.
  Cause:
  
  Lack of Authorization: The user executing the transaction does not have the required authorization objects assigned to their user profile.
  Role Assignment: The user may not be assigned the correct roles that include the necessary authorizations for accessing IT 1953 records.
  Authorization Object: The specific authorization object related to the transaction or data access may not be included in the user's profile.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization check failed. This will provide insight into what specific authorization is missing.
  
  
  
  Review Roles and Profiles:
  
  Go to transaction PFCG to review the roles assigned to the user. Ensure that the roles include the necessary authorizations for accessing IT 1953 records.
  If the roles are missing the required authorizations, you may need to modify the role or create a new one that includes the necessary authorizations.
  
  
  
  Authorization Object:
  
  Identify the specific authorization object that is causing the issue. This can often be found in the error message details or by using transaction SU24 to check the authorization checks for the relevant transaction codes.
  Ensure that the user has the necessary values for the authorization object.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to modify roles or authorizations, consult with your SAP security team or administrator. They can help you identify and assign the correct authorizations.
  
  
  
  Testing:
  
  After making changes to the user’s roles or authorizations, have the user log out and log back in to ensure that the changes take effect. Then, attempt to access the IT 1953 records again.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SU24: Authorization Object Check
  
  
  Documentation: Refer to SAP documentation or help resources for detailed information on authorization objects related to your specific module (e.g., RE-FX).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message.