SAP Knowledge Base Article - Public

2357821 - Advanced Reporting Validation Errors Descriptions, Cause and Fix - tips and tricks

Symptom

The most common Advanced Reporting Validation Errors Descriptions, Causes and fixes are explained in this article.

Environment

SAP SuccessFactors HXM Suite

Resolution

Often one validation error can generate related validation errors.
Fixing the root validation error, will result in a fix for any related errors. 
Some validation errors will not present with an Editor Delete option – these errors are often related to a root validation issue and
will be automatically fixed when the root validation error is resolved.

Given this, rather than working “top to bottom” from the list of errors presented in the validation interface,
it is recommended that you work through the validation errors in the order of:

1. “table” related errors
2. then the “column” related errors

If a table cannot be found in an instance then the label used for that table will not exist –given this, the table name will be displayed in it’s “raw” form.

Typically the first part of this “raw” label will be the category that the table is found in (for eg):

  • PERSON_VIEW
  • EMPLOYMENT_VIEW
  • AUTO_FOUNDATION_OBJECTS_VIEW
  • EMPLOYMENT (or the MDF-specific label)

The last portion of the “raw” label gives the most insight into the table origins (for eg):

  • EMP_JOB_INFO: Employee Job Information
  • EMP_PHONE_INFO: Employee Phone Information
  • EMP_EMAIL_INFO: Employee Email Information
  • MDF_EmployeeClass: MDF Picklist for Employee Class labels
Error message Description Cause
No primary table defined: (). Table: Validator cannot find table
Table () is not found. Table: Validator cannot find table
Table ()is not a possible driving table Table: Validator cannot find table
Query condition is invalid due to missing or invalid left query member. Column:Validator cannot find column
Query contains an invalid auto link column–[column] from [table] to [table]. Column:Table exists, but validator cannot find column
Column () is not found in Table (). Column:Table exists, but validator cannot find column
Query contains an invalid runtime filter: Autolink column [column] from [table] to [table]. Column:Validator cannot find column
Query condition is invalid due to missing or invalid left query member. Column:Validator cannot find column
Query contains an invalid runtime filter: Column () is not found in Table (). Column:Validator cannot find column
Calculated column requires column () is not found in Table () Column: Validator cannot find column
Query contains an invalid calculated column (). Typically caused by the Calculated column requires column () is not found in Table ()error

List of the missing tables and detailed cause description:

  • Table () is not found
  • No primary table defined: ()
  • Table () is not a possible driving table

Cause: These errors indicate that a table used in the report template is not found in the target instance. The validator may be unable to find a table due to it not existing in the instance or simply having a different label in the instance configuration.
A missing table can also have the flow on effect of causing missing columns so these errors are often seen together and accompanied by other validation errors relating to joins and columns.
These errors should be fixed first, as this will potentially resolve any other validation issues that stem from this error, including other validation errors from the same list.

Fix: 

1. First, confirm that the missing table has been implemented in the instance’s EC configuration. Eg: if the report template contains the Time Account Detail object, then this object is pivotal to the report results. If this object hasn’t been configured for EC, then the report is effectively redundant for the target instance and can be removed / sent to an archive folder. The Advanced Reporting: Standard Reports reference guide and Technical guide will outline the main tables used for each individual report.

2. If the table has been configured for the instance, then the table label might be different to the report template. In some cases, tables have been labeled according to a particular “type” code (eg: Phone type, or Email type) and it will be required to select the corresponding “type” for the table in the target instance. To update the report template so that it uses the table label for the target instance, click on Edit next to the error and review the list of alternative tables offered (shown in following slides).

3. If the table has been configured and the table label is the same in the target instance as the report definition, then there may be an issue with the table appearing in the target instance. Please raise a ticket with Support to investigate.

List of the missing tables and detailed cause description:

  • Column () is not found in Table ().
  • Query contains an invalid auto link column –[column] from [table] to [table].
  • Query contains an invalid runtime filter : Autolink column [column] from [table] to [table].
  • Query contains an invalid runtime filter : Column () is not found in Table ().
  • Calculated column requires column () is not found in Table ()
  • Query contains an invalid calculated column ().
  • Query condition is invalid due to missing or invalid left query member

Cause: These errors indicate that a column used in the report template cannot be found in the target instance. The validator may be unable to find a column due to a missing table, different labels, or the column simply not existing in the configuration.
It is recommended that errors are resolved in the order given above (if possible) as errors higher in the list can automatically resolve errors lower in the list.

Fix:

  1. Some columns use a picklist or foundation object table (these are identified by PICKLIST or FOUNDATION_OBJECTS in the table name):
    1. Ensure that the picklist or foundation object is configured for the instance.
      Most picklists and foundation objects are typically not pivotal to the report results.
      If the picklist or foundation object is not configured and not required in the instance, it can simply be deleted from the report template using the Delete option.

    2. The picklist or foundation object table be configured with a different label.
      To update the report template so that it uses the table label for the target instance, click Edit next to the error and review the list of alternative tables offered (shown in following slides).

  2. If the table has been configured and the table label is the same in the target instance as the report definition, then there may be an issue with the join configuration in the target instance. Please raise a ticket with Support to investigate.

See Also

2973443 - Post picklist migration errors validating reports - Advanced Reporting

2357604 - How to Fix Advanced Reporting validation Group errors or Single error

Keywords

ORD, Online, Report, Designer, Standard, std, EC, templates, Validation, Error, Missing, Fields, Tables, filter, join , KBA , thennan_ecstd_report_validate , LOD-SF-ANA-ADV , Advanced Reporting (ODS) , Problem

Product

SAP SuccessFactors HXM Suite all versions