How To Fix PFM_1279 - Divestiture account is equal to transfer account/removals

SAP Error Message - Details

• Message type: E = Error

• Message class: PFM_1 - Message class for POCLIS

• Message number: 279

• Message text: Divestiture account is equal to transfer account/removals

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 PFM_1279 - Divestiture account is equal to transfer account/removals ?

  The SAP error message PFM_1279, which states "Divestiture account is equal to transfer account/removals," typically occurs in the context of asset accounting or financial transactions involving divestitures or transfers. This error indicates that the system has detected that the divestiture account (the account where the asset is being transferred out) is the same as the transfer account or the account used for removals, which is not allowed.
  Cause:
  
  Configuration Issue: The configuration of the asset accounting settings may have been set up incorrectly, leading to the same account being used for both divestiture and transfer/removal.
  Data Entry Error: During the transaction entry, the same account may have been mistakenly selected for both the divestiture and transfer/removal.
  Business Logic Violation: The business rules or logic defined in the system may not allow for the same account to be used for both operations, as it could lead to incorrect financial reporting.
  
  Solution:
  
  
  Check Configuration:
  
  Review the configuration settings for asset accounting in SAP. Ensure that the divestiture and transfer/removal accounts are set up correctly and are distinct from one another.
  Navigate to the relevant configuration settings in the SAP system (usually found in the IMG under Financial Accounting > Asset Accounting).
  
  
  
  Correct Transaction Entry:
  
  If the error occurred during a specific transaction, review the transaction details. Ensure that the correct accounts are being used for divestiture and transfer/removal.
  If necessary, reverse the transaction and re-enter it with the correct accounts.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on the specific configuration and transaction processes related to asset divestitures and transfers.
  
  
  
  Engage with SAP Support:
  
  If the issue persists and cannot be resolved through configuration or data entry corrections, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration or version.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP for asset accounting, such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset).
  User Roles: Ensure that users involved in asset accounting have the appropriate roles and authorizations to perform transactions without encountering errors.
  Testing: After making any changes, conduct thorough testing to ensure that the issue is resolved and that no new issues arise from the changes made.
  
  By following these steps, you should be able to identify the cause of the PFM_1279 error and implement a solution to resolve it.