How To Fix WGDS_PROCESS765 - Training data for model &1 is not ready to be split

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_PROCESS - Global data synchronisation

• Message number: 765

• Message text: Training data for model &1 is not ready to be split

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 WGDS_PROCESS765 - Training data for model &1 is not ready to be split ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WGDS_PROCESS765: Training data for model &1 is not ready to be split
  
  
  Cause:
  This error occurs in the SAP Predictive Analytics or SAP Data Intelligence context when the system attempts to split the training data for a machine learning model, but the training data is not yet prepared or available in the expected state.
  Possible reasons include:
  
  The training dataset has not been fully loaded or processed.
  The data preparation step (such as data cleansing, feature engineering, or data transformation) has not been completed.
  The dataset is empty or does not meet the minimum requirements for splitting (e.g., too few records).
  The model configuration or pipeline is incomplete or incorrectly set up, causing the system to look for training data that does not exist or is not ready.
  There might be a timing issue where the split operation is triggered before the data preparation finishes.
  
  
  
  Solution:
  To resolve this