How To Fix RP652 - Debit memo procedure is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: RP - Error Messages for Infotype Module Pools

• Message number: 652

• Message text: Debit memo procedure is not permitted

What causes this issue?

In the External Bank Transfers infotype (0011) a wage type was assigned
that is flagged in the processing class 24 as a debit memo.
However, there is no automatic debit authorization available for the
payee from infotype 0011.

System Response

Processing continues. However, the debit memo wage type is ignored.
No debit memo is carried out for the specified payee.

How to fix this error?

Please check whether a debit memo actually has to be created.
If so, set the automatic debit authorization indicator in table
T521B for the payee.
If a debit memo does not have to be created, delete the wage type in the
infotype 0011 or replace the wage type with one that is marked as
bank transfer in the processing class 24.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RP652 - Debit memo procedure is not permitted ?

  The SAP error message "RP652 Debit memo procedure is not permitted" typically occurs in the context of invoice processing, particularly when dealing with debit memos in the SAP system. This error indicates that the system is not allowing the creation or processing of a debit memo due to certain configuration or procedural issues.
  Causes:
  
  Configuration Settings: The debit memo procedure may not be configured correctly in the system. This could be due to missing settings in the relevant configuration tables or transaction codes.
  Document Type Restrictions: The document type used for the debit memo may not be allowed for the transaction you are trying to perform. Each document type has specific settings that determine its usage.
  Account Assignment Issues: There may be issues with the account assignment or the vendor/customer master data that prevent the debit memo from being processed.
  Authorization Issues: The user may not have the necessary authorizations to create or process debit memos in the system.
  Business Rules: Certain business rules or validations may be preventing the debit memo from being processed, such as specific conditions that must be met before a debit memo can be issued.
  
  Solutions:
  
  
  Check Configuration: Review the configuration settings for the debit memo procedure in the SAP system. This can be done through the following transaction codes:
  
  SPRO: Access the SAP Reference IMG and navigate to the relevant configuration settings for Accounts Payable or Accounts Receivable.
  Ensure that the debit memo procedure is properly defined and that all necessary settings are in place.
  
  
  
  Review Document Type: Verify that the document type you are using for the debit memo is allowed for the transaction. You can check this in the configuration settings for document types in the Financial Accounting module.
  
  
  Validate Master Data: Ensure that the vendor or customer master data is correctly set up and that there are no issues with account assignments. Check for any missing or incorrect information that could be causing the error.
  
  
  Check User Authorizations: Ensure that the user attempting to create or process the debit memo has the necessary authorizations. This can be checked through transaction code SU53 or by consulting with your SAP security team.
  
  
  Consult Business Rules: Review any business rules or validations that may be in place regarding debit memos. Ensure that all conditions are met before attempting to process the debit memo.
  
  
  SAP Notes and Support: If the issue persists, check for any relevant SAP Notes that may address this specific error message. You can search for notes in the SAP Support Portal.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB60 (Enter Incoming Invoice), FB70 (Enter Outgoing Invoice), and FB75 (Enter Debit Memo) to understand where the error might be occurring.
  Documentation: Review SAP documentation related to Accounts Payable and Accounts Receivable processes to understand the standard procedures and configurations.
  Testing: If changes are made to the configuration or master data, conduct thorough testing to ensure that the issue is resolved and that debit memos can be processed without errors.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.