How To Fix COLL_PR_MSG036 - Customer &1 was not yet contacted.

SAP Error Message - Details

• Message type: E = Error

• Message class: COLL_PR_MSG - Messages in Process Receivables

• Message number: 036

• Message text: Customer &1 was not yet contacted.

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 COLL_PR_MSG036 - Customer &1 was not yet contacted. ?

  The SAP error message COLL_PR_MSG036, which states "Customer &1 was not yet contacted," typically occurs in the context of collections management or accounts receivable processes. This message indicates that a specific customer (represented by &1) has not been contacted regarding their outstanding debts or invoices.
  Cause:
  
  Lack of Communication: The system identifies that no communication (e.g., reminders, dunning letters) has been sent to the customer regarding their overdue payments.
  Process Configuration: The collections process may not have been properly configured to initiate contact with the customer.
  Data Entry Issues: There may be missing or incorrect data in the customer master record that prevents the system from recognizing that contact has been made.
  Workflow Status: The workflow for collections might not have progressed to the point where the customer has been contacted.
  
  Solution:
  
  Contact the Customer: Manually reach out to the customer to discuss their outstanding balance. This can be done via phone, email, or formal letters.
  Update the System: After contacting the customer, ensure that the system is updated to reflect this communication. This may involve changing the status of the collection process or logging the contact in the system.
  Review Configuration: Check the configuration settings in the collections management module to ensure that the process for contacting customers is set up correctly.
  Check Customer Data: Verify that the customer master data is complete and accurate, including contact information and communication history.
  Run Dunning Program: If applicable, run the dunning program to automatically generate reminders or notifications for overdue payments.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) or F110 (Automatic Payment Transactions) that may help in managing customer communications.
  Documentation: Refer to SAP documentation or help files for detailed instructions on managing collections and dunning processes.
  User Exits and Enhancements: If the standard process does not meet your business needs, consider implementing user exits or enhancements to customize the collections workflow.
  Training: Ensure that staff involved in collections management are trained on the processes and tools available in SAP to effectively manage customer communications.
  
  By addressing the underlying cause of the error and following the suggested solutions, you can resolve the issue and improve your collections management process.