How To Fix PM170 - Doc. no. &1 from CC &2 and fyear &3 missing in table BKPF; termination


SAP Error Message - Details

  • Message type: E = Error

  • Message class: PM - Extended Payment Functions

  • Message number: 170

  • Message text: Doc. no. &1 from CC &2 and fyear &3 missing in table BKPF; termination

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


Smart SAP Assistant

  • What is the cause and solution for SAP error message PM170 - Doc. no. &1 from CC &2 and fyear &3 missing in table BKPF; termination ?

    The SAP error message PM170 indicates that there is a missing document number in the BKPF table for a specific company code and fiscal year. This error typically occurs during processes that involve financial postings, such as asset accounting or other financial transactions.

    Cause:

    1. Missing Document: The document number specified in the error message does not exist in the BKPF table for the given company code and fiscal year.
    2. Data Inconsistency: There may be inconsistencies in the database, possibly due to incomplete transactions or issues during data migration.
    3. Incorrect Configuration: The configuration settings for document types or number ranges may not be set up correctly, leading to missing entries.
    4. Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the document.

    Solution:

    1. Check Document Existence:

      • Use transaction code SE16 or SE16N to check the BKPF table for the specified document number, company code, and fiscal year.
      • If the document is indeed missing, you may need to investigate why it was not created.
    2. Review Number Ranges:

      • Check the configuration of number ranges for the relevant document type in transaction code OBA7. Ensure that the number range is correctly defined and that it is not exhausted.
    3. Repost the Transaction:

      • If the document was not created due to an error during posting, you may need to repost the transaction that generated the error.
    4. Check for Data Migration Issues:

      • If this issue arose after a data migration, verify that all necessary data was migrated correctly and that there are no missing entries.
    5. Consult with Basis Team:

      • If you suspect a database issue or corruption, consult with your SAP Basis team to check the integrity of the database.
    6. Authorization Check:

      • Ensure that the user has the necessary authorizations to access the document in question.

    Related Information:

    • Transaction Codes:

      • SE16/SE16N: For checking table entries.
      • OBA7: For managing number ranges.
      • FB03: For displaying financial documents.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for PM170 in the SAP Support Portal.

    • Documentation: Review SAP documentation related to Financial Accounting (FI) and Asset Accounting (AA) for more context on document management and posting processes.

    If the issue persists after following these steps, it may be beneficial to engage with SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author