Do you have any question about this error?
Message type: E = Error
Message class: 5C - HR: Messages for Switzerland
Message number: 813
Message text: Dependent postings could not be determined
An error occurred when determining dependent postings for the recently
created, manual posting (value type &V1&).
With most manual postings no dependent postings are planned so that
this error in the rule can be ignored.
No dependent posting is generated.
Make sure if a dependent posting should be generated for a posting with
value type &V1&.
Check if necessary the cause of error with the message list.
Error message extract from SAP system. Copyright SAP SE.
5C813
- Dependent postings could not be determined ?The SAP error message 5C813, "Dependent postings could not be determined," typically occurs in the context of financial transactions, particularly when dealing with document postings in the SAP system. This error indicates that the system is unable to determine the necessary dependent postings for a transaction, which can be due to various reasons.
Causes:
Missing Configuration: The configuration for the relevant account or transaction type may not be set up correctly. This can include missing account assignments or incorrect settings in the financial accounting (FI) or controlling (CO) modules.
Incorrect Document Type: The document type used for the transaction may not be compatible with the expected postings, leading to the inability to determine dependent postings.
Missing Master Data: Required master data (such as cost centers, internal orders, or profit centers) may be missing or incorrectly maintained.
Posting Period Issues: The posting period may be closed or not open for the transaction being processed, preventing the system from determining the necessary postings.
Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard posting logic, leading to this error.
Solutions:
Check Configuration: Review the configuration settings for the relevant account and transaction type in the SAP system. Ensure that all necessary settings are correctly maintained.
Verify Document Type: Ensure that the document type being used is appropriate for the transaction and that it is configured to allow the necessary postings.
Review Master Data: Check the master data related to the transaction. Ensure that all required fields are filled out and that the data is valid.
Check Posting Period: Verify that the posting period is open for the transaction. If it is closed, you may need to open it or post the transaction in an open period.
Debug Custom Code: If there are custom enhancements or user exits, review the code to ensure it is not causing the issue. Debugging may be necessary to identify the root cause.
Consult SAP Notes: Check the SAP Support Portal for any relevant notes or updates related to this error message. There may be specific patches or updates that address known issues.
Related Information:
FB50
(General Ledger Account Document Entry) or F-02
(General Posting) to replicate the issue and gather more information.If the issue persists after trying the above solutions, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
5C812
PF accounts locked through &1 in current client
What causes this issue? The current evaluation is set so that all PF accounts are locked in the data bank. There is however at least one account alre...
5C811
Account locked with account type &2 in fund &1
What causes this issue? A data bank lock was set for the account with account type &V2& in the employee's fund &V1&. Therefore n...
5C814
Postings exist
What causes this issue? Postings were generated with processing. These have not yet been written to the database.System Response The postings can be...
5C815
Not all generated postings were processed
What causes this issue? Evaluation &V1& has determined a list of dependent postings that were not fully written to the database.System Respon...
Click on this link to search all SAP messages.