How To Fix WT117 - No historical data exits for combination entered

SAP Error Message - Details

• Message type: E = Error

• Message class: WT - Retail: Replenishment

• Message number: 117

• Message text: No historical data exits for combination entered

What causes this issue?

For the combination you entered of material groups / materials and
customers no historical data exists. This is, however, required for
calculating weighting factors.

System Response

No weighting factors were calculated.

How to fix this error?

Transfer the required historical data - possibly from your legacy
system.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WT117 - No historical data exits for combination entered ?

  SAP Error Message:
  
  WT117 - No historical data exists for combination entered
  
  Cause:
  This error occurs in SAP when you try to perform a transaction or generate a report that requires historical data for a specific combination of parameters (such as cost center, internal order, WBS element, or other controlling objects), but the system cannot find any historical data for that combination in the database.
  Common scenarios include:
  
  Attempting to display or analyze actual costs or plan data for a controlling object that has no posted transactions or plan data.
  Running reports or planning functions where the system expects prior period data to calculate or compare, but none exists.
  Entering a combination of controlling objects or cost elements that have never been used or have no data in the system.
  
  
  Solution:
  
  
  Check the Combination Entered:
  
  Verify that the controlling object (cost center, internal order, WBS element, etc.) and other parameters you entered are correct.
  Ensure that the combination actually exists and is valid in the system.
  
  
  
  Check for Posted Data:
  
  Confirm that there are posted transactions or plan data for the controlling object in the relevant periods.
  Use transaction codes like KSB1 (Cost Centers: Actual Line Items), KO03 (Display Internal Order), or CJ20N (Project Builder) to check if data exists.
  
  
  
  Create or Post Data:
  
  If no data exists, you may need to post actual transactions or enter plan data for the controlling object.
  For planning, ensure that plan data has been maintained for the relevant periods.
  
  
  
  Adjust Reporting Period or Parameters:
  
  Try changing the period or fiscal year to one where data exists.
  Modify the selection criteria to include objects or periods with data.
  
  
  
  Check Master Data Validity:
  
  Ensure that the controlling object is valid and not closed or deleted.
  Check the validity dates of the controlling object.
  
  
  
  Consult with Controlling Team:
  
  Sometimes, the absence of data is expected (e.g., new cost centers or projects).
  Coordinate with controlling or finance teams to understand if data should exist.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  KSB1 - Cost Centers: Actual Line Items
  KOB1 - Orders: Actual Line Items
  S_ALR_87013611 - Cost Centers: Actual/Plan/Variance
  CJ20N - Project Builder (for WBS elements)
  KP06 - Cost Center Planning
  
  
  
  SAP Notes and Documentation:
  
  Check SAP Notes related to controlling and planning for any known issues.
  Refer to SAP Help Portal for controlling module documentation.
  
  
  
  Typical Modules Involved:
  
  Controlling (CO)
  Project System (PS)
  Financial Accounting (FI)
  
  
  
  
  Summary:
  The WT117 error indicates that the system cannot find any historical data for the combination of controlling objects and parameters you entered. Verify the correctness of the input, ensure that data exists for the objects and periods, and if necessary, post or plan data before retrying the operation.