---
schema_version: "1"
id: 9300aa1ff96e68ccdcb243e3fc0c496342c630657179050be0d1242ffe10593f
title: Error Messages and Validation Checks for 254
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/cg_tpm_error_messages_254.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.cg_tpm_error_messages_254.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 74ead64ea53d2af8e40c40a0640d3f18f58a26ef0aac27094bc05b1c2a844350
description: Validation checks are triggered when users interact with the TPM application and when operations are performed via API integrations. Users can then take corrective actions in either the TPM application or the API.
products:
  - Consumer Goods
release: "264"
---
# Error Messages and Validation Checks for 254

Validation checks are triggered when users interact with the TPM application and when operations are performed via API integrations. Users can then take corrective actions in either the TPM application or the API.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: Lightning Experience</p>
            <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions where Consumer Goods
              Cloud is enabled</p>
          </td>

        </tr>
      </tbody>
    </table>

These validations are enforced through:

- Salesforce object validation rules: Configured in the setup for relevant custom and standard objects.
- Backend logic: Asynchronous processes within managed packages, which enforce business rules and ensure data consistency.

    
| Validation Check | Triggered When | Applied Via (Validation Rule / Backend Logic / Apex / Processing Services) | Enforced in (TPM Application/API) | Corrective Action |
| --- | --- | --- | --- | --- |
| `TPM_CUSTOMER_SET_EXCEED_LIMIT` | The number of accounts in an account set exceeds the limit. | Backend Logic | Both | Select a customer set with a customer count within the allowed limit, and try again. |
| `TPM_CUSTOMER_SET_EXCEED_LIMIT_ANCHOR` | An account set is selected that either has no accounts or exceeds the defined limit of accounts. | Backend Logic | Both | Select a customer set with a customer count within the allowed limit, and try again. |
| `TPM_CUSTOMER_SET_EXCEED_LIMIT_DATES` | One or more accounts in an account set has a promotion role with dates outside the promotion's timeframe. | Backend Logic | Both | Make sure that all customers in the customer set have promotion role dates within the promotion's Date From and Date Thru dates. |
| `TPM_CUSTOMER_SET_NO_CUSTOMERS` | An account set with 0 customers is selected as the promotion anchor. | Backend Logic | Both | Select a customer set with at least one customer and try again. |
| `TPM_CUSTOMER_SET_CUSTOMERS_NO_PROMOTION_ROLE` | At least one customer in the selected account set doesn't have a valid promotion role. | Backend Logic | Both | Make sure that all customers in the set have a valid promotion role and try again. |
| `TPM_CUSTOMER_SET_UNABLE_TO_CHECK` | The number of customers in the account set is too large to be validated in a single transaction. | Backend Logic | Both | Reduce the number of customers in the set and try again. |
| `TPM_CUSTOMER_INVALID_PROMOTION_ROLE` | A single customer anchor is selected whose promotion role is invalid for the promotion's timeframe. | Backend Logic | Both | We couldn’t create the promotion because the selected customer’s promotion role isn't valid for the promotion's timeframe. Select a customer whose role is valid for the Date From and Date Thru dates. |
| `TPM_ACCOUNT_SET_ACCOUNT_PROMOTION_ERROR` | A generic, unhandled error occurs when validating the selected account set. | Backend Logic | Both | — |