How To Fix FP129 - No authorization to delete parked documennts in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FP - Invoice Parking

• Message number: 129

• Message text: No authorization to delete parked documennts in company code &

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 FP129 - No authorization to delete parked documennts in company code & ?

  The SAP error message FP129 indicates that a user does not have the necessary authorization to delete parked documents in a specific company code. This error typically arises in the context of financial transactions where parked documents are used to temporarily hold accounting entries before they are finalized.
  Cause:
  
  Authorization Issues: The user attempting to delete the parked document lacks the required authorization in their user role. This could be due to missing authorization objects related to document deletion in the Financial Accounting (FI) module.
  Company Code Restrictions: The user may have authorization for other company codes but not for the specific company code mentioned in the error message.
  Role Configuration: The roles assigned to the user may not include the necessary permissions to perform deletion actions on parked documents.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization objects are missing.
  Review the user’s roles and authorizations in transaction code SU01 or PFCG.
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, you can modify the user’s roles to include the required authorizations for deleting parked documents. This typically involves adding the relevant authorization objects (e.g., F_BKPF_BEA for document management) to the user’s role.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary access to change roles, contact your SAP security or basis team. Provide them with the details of the error and the company code involved, and they can assist in adjusting the authorizations.
  
  
  
  Testing:
  
  After changes are made, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt to delete the parked document again.
  
  
  
  Related Information:
  
  
  Authorization Objects: Common authorization objects related to parked documents include:
  
  F_BKPF_BEA: Authorization for document management.
  F_BKPF_AKT: Authorization for accounting documents.
  
  
  
  Transaction Codes:
  
  FBV0: Park document.
  FBV2: Change parked document.
  FBV3: Display parked document.
  
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues or provide additional guidance related to authorization errors.
  
  
  By following these steps, you should be able to resolve the FP129 error and successfully delete the parked documents as needed.