How To Fix /PF1/PE_PP_BASIS504 - Deactivate the application for general ledger update in the BDT

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/PE_PP_BASIS -

• Message number: 504

• Message text: Deactivate the application for general ledger update in the BDT

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 /PF1/PE_PP_BASIS504 - Deactivate the application for general ledger update in the BDT ?

  The SAP error message /PF1/PE_PP_BASIS504 indicates that there is an issue related to the Business Data Toolset (BDT) where the application for general ledger (G/L) update is deactivated. This typically occurs in the context of the Production Planning (PP) module when trying to post data that requires G/L updates.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Configuration Settings: The application for G/L updates may not be activated in the BDT configuration. This can happen if the settings were changed or not properly configured during the initial setup.
  Authorization Issues: The user may not have the necessary authorizations to perform G/L updates.
  System Settings: There may be system-wide settings that prevent G/L updates for certain applications or scenarios.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check BDT Configuration:
  
  Go to the BDT configuration settings in the SAP system.
  Ensure that the application for G/L updates is activated. You may need to consult with your SAP Basis or configuration team to verify this.
  
  
  
  Review User Authorizations:
  
  Check if the user encountering the error has the necessary authorizations to perform G/L updates. This can be done by reviewing the user's roles and authorizations in the SAP system.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation or notes related to the specific error message. SAP Notes may provide additional insights or patches that can resolve the issue.
  
  
  
  System Settings:
  
  Review any system-wide settings that may affect G/L updates. This could include settings in the Financial Accounting (FI) module or other related modules.
  
  
  
  Testing:
  
  After making any changes, perform a test to ensure that the error no longer occurs. This may involve trying to post the same data again to see if the issue is resolved.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They may provide specific guidance based on your system configuration and version.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, SU01 for user authorization checks, and SE80 for checking BDT applications.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the SAP Help Portal for documentation related to BDT and G/L updates in the context of the PP module.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.