How To Fix >4387 - Creditworthiness entry was saved

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 387

• Message text: Creditworthiness entry was saved

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 >4387 - Creditworthiness entry was saved ?

  The SAP error message "4387 Creditworthiness entry was saved" typically indicates that a creditworthiness check has been performed and the relevant data has been saved in the system. This message is not necessarily an error but rather an informational message indicating that the creditworthiness data for a customer or vendor has been successfully processed.
  Cause:
  
  Creditworthiness Check: The message is triggered when a creditworthiness check is executed for a customer or vendor, and the system saves the results of this check.
  Data Entry: It may occur during the creation or modification of customer/vendor master data where creditworthiness is assessed.
  Configuration: The message can also be related to the configuration settings in the SAP system regarding credit management.
  
  Solution:
  Since this message is informational, there is typically no action required unless you are expecting a different outcome. However, if you are looking to ensure that the creditworthiness check is functioning as intended, consider the following steps:
  
  Review Credit Management Settings: Check the configuration settings in the SAP system related to credit management. Ensure that the credit limits and risk categories are set up correctly.
  Check Customer/Vendor Master Data: Verify that the customer or vendor master data is complete and accurate, including financial information that may affect creditworthiness.
  Monitor Creditworthiness Results: If you are expecting a specific creditworthiness result, review the details of the credit check to ensure that it aligns with your expectations.
  Consult Documentation: Refer to SAP documentation or help resources for more detailed information on credit management and the specific message.
  
  Related Information:
  
  Transaction Codes: You may want to look into transaction codes related to credit management, such as FD32 (Change Customer Credit Management) or FD33 (Display Customer Credit Management).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or enhancements related to creditworthiness checks.
  User Exits and BAdIs: If you need to customize the behavior of credit checks, consider looking into user exits or Business Add-Ins (BAdIs) that can be implemented to modify the standard functionality.
  
  If you are encountering issues beyond this informational message, it may be helpful to provide more context or specific symptoms to diagnose further.