How To Fix WS805 - New count data, old (val.day &1, cond. &2, days 1, &3 percent 1 &4 %)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 805

• Message text: New count data, old (val.day &1, cond. &2, days 1, &3 percent 1 &4 %)

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 WS805 - New count data, old (val.day &1, cond. &2, days 1, &3 percent 1 &4 %) ?

  The SAP error message WS805 with the text:
  New count data, old (val.day &1, cond. &2, days 1, &3 percent 1 &4 %)
  typically occurs in the context of time evaluation in SAP HR (Human Resources), specifically during the processing of time data in the Time Management module.
  
  Cause
  
  The message WS805 is related to time evaluation and indicates a discrepancy or conflict between new and old count data for a particular day or condition.
  It usually arises when the system detects that the newly calculated time data (e.g., working hours, absence, attendance) for a specific day or condition does not match the previously stored (old) data.
  The placeholders in the message (&1, &2, &3, &4) represent:
  
  &1: Valuation day (date)
  &2: Condition type (e.g., absence, attendance, overtime)
  &3: Number of days
  &4: Percentage value
  
  
  This mismatch can be caused by:
  
  Incorrect or inconsistent time data input.
  Custom time evaluation rules or schemas that produce conflicting results.
  Changes in master data or infotypes affecting time evaluation.
  Errors in the time evaluation schema or PCR (Personnel Calculation Rule) logic.
  Data inconsistencies after retroactive changes or corrections.
  
  
  
  
  Solution
  
  
  Check the Time Evaluation Log:
  
  Run the time evaluation (transaction PT60) for the affected employee and period.
  Review the detailed time evaluation log to identify where the discrepancy occurs.
  Look for the specific day (&1) and condition (&2) mentioned in the message.
  
  
  
  Analyze Time Data:
  
  Verify the time data entered in infotypes such as:
  
  IT2001 (Absences)
  IT2002 (Attendances)
  IT2011 (Time Events)
  
  
  Check for overlapping or conflicting entries.
  
  
  
  Review Custom PCRs and Time Evaluation Schema:
  
  If custom rules are used, check the logic for counting days and percentages.
  Ensure that the PCRs do not produce contradictory results.
  Validate that the schema is consistent with the business rules.
  
  
  
  Check Master Data:
  
  Verify employee master data (e.g., work schedule, public holidays, leave quotas).
  Ensure that the work schedule and holiday calendar are correctly assigned.
  
  
  
  Correct Data or Adjust Rules:
  
  Correct any incorrect time data entries.
  Adjust PCRs or schema logic if necessary to avoid conflicts.
  Re-run time evaluation after corrections.
  
  
  
  Consult SAP Notes:
  
  Search for SAP Notes related to WS805 for any known issues or patches.
  Example SAP Note: Sometimes SAP releases notes addressing specific time evaluation errors.
  
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  PT60 - Time Evaluation
  PA20/PA30 - Display/Maintain HR Master Data
  PE04 - Time Evaluation Schema
  PE02 - Personnel Calculation Rules (PCR)
  
  
  
  SAP Tables:
  
  T510S - Time Evaluation Schema
  T556A - Time Evaluation Rules
  PA2001 - Absences
  PA2002 - Attendances
  
  
  
  Documentation:
  
  SAP Help Portal: Time Evaluation in SAP HR
  SAP HR Time Management Configuration Guides
  
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Mismatch between new and old time evaluation count data for a specific day/condition.
  
  
  Solution
  Check time evaluation logs, verify time data, review PCRs and schema, correct inconsistencies, re-run evaluation.
  
  
  Related
  Transactions PT60, PE04, PE02; Infotypes 2001, 2002; SAP Notes on WS805.
  
  
  
  
  If you provide the exact values for the placeholders (&1, &2, etc.) or the context (e.g., which time evaluation schema or PCR is used), I can help you analyze the issue more specifically.