1P352 - Account holder &1 is not contained in table BUT000

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: 1P - BCA: Payment Transactions

  • Message number: 352

  • Message text: Account holder &1 is not contained in table BUT000

  • Show details Hide details


  • 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.


AnswerBot

  • What is the cause and solution for SAP error message 1P352 - Account holder &1 is not contained in table BUT000 ?

    The SAP error message 1P352 indicates that the account holder specified in the transaction is not found in the table BUT000. The BUT000 table is part of the Business Partner (BP) data model in SAP, which stores general information about business partners, including customers, vendors, and other entities.

    Cause:

    The error typically occurs due to one of the following reasons:

    1. Missing Business Partner: The account holder (business partner) you are trying to reference does not exist in the system.
    2. Incorrect Account Holder ID: The ID or number you are using to reference the account holder may be incorrect or mistyped.
    3. Data Synchronization Issues: If your system is integrated with other systems, there may be synchronization issues leading to missing data.
    4. Inactive Business Partner: The business partner may exist but is marked as inactive or not available for the transaction you are trying to perform.

    Solution:

    To resolve this error, you can take the following steps:

    1. Verify Business Partner Existence:

      • Use transaction code BP to check if the business partner exists in the system.
      • Search for the account holder using the correct ID or name.
    2. Create or Update Business Partner:

      • If the business partner does not exist, you will need to create it using the BP transaction.
      • If it exists but is inactive, you may need to reactivate it or ensure it is set up correctly for the intended use.
    3. Check for Data Consistency:

      • Ensure that the data in the system is consistent and that there are no issues with data synchronization if you are using multiple systems.
    4. Consult with Your SAP Administrator:

      • If you are unable to resolve the issue, consult with your SAP administrator or support team. They can check for any underlying issues in the configuration or data setup.
    5. Review Authorization:

      • Ensure that you have the necessary authorizations to access the business partner data.

    Related Information:

    • Transaction Codes:
      • BP: Business Partner Maintenance
      • SE11: Data Dictionary (to view the structure of the BUT000 table)
    • Tables:
      • BUT000: General Data for Business Partners
      • BUT020: Business Partner Roles
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.

    By following these steps, you should be able to identify the cause of the error and implement the necessary solution.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.