Do you have any question about this error?
Message type: E = Error
Message class: FR - Messages for FI Reporting
Message number: 852
Message text: Blocked vendor data is not reported; you do not have authorization
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.
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.
FR852
- Blocked vendor data is not reported; you do not have authorization ?The SAP error message FR852 indicates that a user is attempting to access or report on vendor data that has been blocked, but they do not have the necessary authorization to do so. This error typically arises in the context of vendor management and reporting within the SAP system.
Cause:
- Blocked Vendor Data: The vendor data in question has been marked as blocked, which means it cannot be processed or reported on until the block is lifted.
- Authorization Issues: The user does not have the required authorization to access or report on blocked vendor data. This could be due to missing roles or permissions in their user profile.
Solution:
Check Vendor Status: Verify if the vendor is indeed blocked. This can be done by checking the vendor master data in the SAP system.
- Use transaction code XK03 (Display Vendor) to check the status of the vendor.
- If the vendor is blocked and should not be, you may need to unblock it using transaction code XK02 (Change Vendor) if you have the necessary permissions.
Review User Authorizations:
- Check the user’s roles and authorizations to ensure they have the necessary permissions to access blocked vendor data.
- This can be done by using transaction code SU53 to analyze the last authorization check after the error occurred.
- If the user lacks the necessary authorizations, you may need to contact your SAP security team or administrator to request the appropriate roles or permissions.
Consult with SAP Security Team: If you are not able to resolve the authorization issue, it may be necessary to involve your SAP security team to review and adjust the user’s roles and authorizations.
Documentation and Training: Ensure that users are aware of the policies regarding blocked vendor data and the necessary authorizations required to access such data. Providing training or documentation can help prevent similar issues in the future.
Related Information:
By following these steps, you should be able to identify the cause of the FR852 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FR851
BP data is not masked; no authorization to create file
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FR850
Valuation run with valuation area &1 and parameter &2 started
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FR855
Specify either posting date only or posting period only.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FR856
Do not use field & for selecting parked documents
What causes this issue? Field &v1& is not in table VBKPF for parked documents. Therefore field &v1& cannot be used for selecting park...
Click on this link to search all SAP messages.