Release note/20240411
| Release date Date and time when a concept, e.g. a data quality rule, is released, i.e. when the status changes to <code>RELEASED</code>. | 2024-04-11 |
|---|---|
| Feature Affected feature(s) | |
| Idea portal Ideas that have been introduced with the release | https://cdqag.aha.io/ideas/ideas/IPOC-I-467 |
Updates on Data Quality Rules
In our latest data quality rules update, we're excited to unveil a series of enhancements and updates aimed at refining your experience with our data quality rules engine. Here's a concise overview of what's included:
- Indian GST Validation: Stay up-to-date with recent changes in Indian regions for GST validation, ensuring seamless compliance with updated state codes.
- Organization Registration Number (Sweden): We've bolstered our rules engine to identify missing organization registration numbers in Sweden, enhancing data quality checks.
- Albanian Tax Number Revision: Experience improved accuracy with revised identifier types and checks for Albanian tax numbers.
- French EU VAT Validation: Enable validation of French EU VATs for partners in specific regions, streamlining compliance processes.
- Pakistani NTN Alphanumeric Format: Adapt to the latest NTN format allowing alphanumeric characters.
- Unallowed Name Pattern Criticality Change: We've adjusted the criticality of unallowed name pattern checks to provide clearer insights into potential issues.
- Adjustments on Dummy Postal Code Identification: Benefit from refined detection of dummy postal codes in Colombia, Germany, and Egypt, ensuring accurate address validation.
- Kosovo Post Code Format Adjustment: Enjoy improved flexibility with post codes in Kosovo, now allowing for variations without mandatory whitespace.
These updates are designed to elevate your user experience and enhance the efficiency of your operations. Please see the details below. All new rules are in HYPERCARE status.
[Identifier checks] Adapt latest changes of Indian regions for the GST validation
The first two segments of the GST number refer to the state code, with each state being assigned a unique identifier.
- The combination of Daman and Diu, previously designated by the state code 25, has been amalgamated with Dadra & Naga Haveli to now solely use the code 26. This change has been also updated in SAP’s S4 table content.
- The state of Andhra Pradesh, formerly recognized by the code 28, will now utilize the code 37, rendering the previous code obsolete.
- New additions to the list of state codes include:
- Ladakh, with the state code being introduced as 38.
- Another category labeled "Other territory" has been assigned the state code 97.
- "Centre jurisdiction" receives the code 99.
For the transitional period, the state codes 25 and 28 will continue to be accepted. However, they will be flagged as outdated in specific data quality checks when associated with a GST number. See Deprecated identifier found (GST number (India)) and Identifier format invalid (GST number (India))
[Identifier checks] Organization Registration Number (Sweden)
The data quality rules engine is capable now to identify missing organization registration numbers. The following rules have been added:
- Mandatory identifier not maintained (Sweden) (ERROR): A business partner in Sweden should have at least a European value added tax identifier (Sweden) or a Organization Registration Number (Sweden). If none of these two is available the record is considered as defective.
- Identifier missing (Organization Registration Number (Sweden)) (INFO): Each legal entity in Sweden should have a Organization Registration Number
Accordingly the following rule has been changed as default to just INFO: Identifier missing (European value added tax identifier (Sweden))
[Identifier checks] Revise identifier types and check of the Albanian tax number
The first character is a capital letter, indicating the decade the TIN was issued (e.g. "J" for 1990 - 1999, "K" for 2000 - 2009, etc.) The current check missed the capital letter M for the years 2020 to 2029. This is fixed with this release. See Identifier format invalid (Tax Registration Number (Albania))
[Identifier checks] Support French EU VAT validation for partners located in Guadeloupe, Martinique and Reunion
On customer request we now enable validation of French EU VATs that are hold by business partners located in Martinique, Guadeloupe or Reunion. Please note that you have to map to the French EU VAT identifier. An example looks like this. Here we have the EU VAT maintained in the field STCEG. In case of the country FR, MQ, GP or RE the value from this field is considered as European Value Added Tax Identifier for France.
{
"sourceAttributes": [
"['STCEG']"
],
"targetAttributes": [
"businessPartner.identifiers"
],
"targetAttributeTypes": [
"EU_VAT_ID_FR"
],
"countryScopes": [
"FR", "MQ", "GP", "RE"
]
}
See Identifier unknown (European value added tax identifier (Martinique)), Identifier unknown (European value added tax identifier (Reunion)), Identifier unknown (European value added tax identifier (Guadeloupe))
[Identifier checks] Pakistan NTN numbers may have alphanumeric characters
The NTN format now allows alpha-numeric digits. While all official documentation that we have talk about 7 + 1 (checkdigit) numeric digits, it is prooven that there are also NTNs with alphanumeric digits. See: Identifier format invalid (Tax Identification Number (Pakistan))
[Name Checks] Change criticality of unallowed name pattern rules
The name pattern checks such as Unallowed pattern in name detected (DE) are now considered as WARNING by default (before: just INFO). Example of an unallowed name pattern: DELETE CDQ AG or CDQ AG Do not use
[Address checks] Adjustments on the dummy postal code identification for Colombia, Germany and Egypt
We fixed some issues with the dummy postal code detection in Colombia, Germany and Egypt. For example
- 111111 is now considered as valid post code of Bogota (CO).
- 33333 as valid post code of Gütersloh (DE)
- 1111 as valid post code of Kairo (EG)
See: Dummy post code detected (DE), Dummy post code detected (CO), Dummy post code detected (EG)
[Address checks] Allow for post codes in Kosovo without whitespaces
The data quality rules engine now allows post codes in Kosovo without a mandatory whitespace after the first two digits. See: Post code format invalid (Kosovo)