Business Partner Cleansing and Enrichment

From CDQ
Capability/Business Partner Cleansing and Enrichment
Jump to navigation Jump to search
Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. Business Partner Cleansing and Enrichment (category: Quality, sort rank: 150)
Short description Informal and short human-readable definition of a concept. Enrichment of legal forms, legal addresses, tax numbers, company status, etc.
Description Informal and comprehensive human-readable definition of a concept. Legal entity data, in particular name and tax numbers, have to be correct for e.g. invoicing, authority tax reporting, or compliance checks. Quotations or invoices do not always provide accurate legal names, or are misunderstood due to trade names or abbreviations. Manual data maintenance in global shared service centers is error-prone due to missing link of data worker and given use case. Reference data for enrichment is not available in 1 data source but has to gathered country-wise from several sources per country. Given records are matched against reference data and shared data, and missing or wrong attributes are added or replaced. Enrichment works in real-time for single records, e.g. in a workflow, or in batch processing jobs. Legal addresses can be identified in records with multiple addresses or added. The same for registered addresses (e.g. from tax authorities).

Tax numbers and other IDs can be added, and legal names, legal forms, company status, etc.

Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it. LIVE
Use cases Analyze and Prepare a Business Partner Storage for Get Clean, Business Partner Data Maintenance Workflow (Lean Update), Cleanse and Enrich a Business Partner Storage
Apps
Following apps provide this capability
APIs
Following APIs provide this capability

Features

Feature Short description Informal and short human-readable definition of a concept. Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it.
Business Partner Augmentation Reports A result of the business partner data curation is the report containing all cleansing activities. LIVE
Business and Tax Identifier Harmonization Harmonizes identifiers according to a specified reference schema. LIVE
Legal Form Enrichment and Harmonization Provides the user with information about the legal form of a business partner. LIVE
Registered Address Enrichment Enriches the officially registered address of a business partner. LIVE
Address Type Identification Allows e.g. for finding out if a given address is a registered address. The feature identifies the type of an address (e.g. registered address) by searching in reference data and identifies the differences between the input address and the reference address. BETA
Business Partner Status Enrichment Identify whether a business partner is still in business in general or whether a particular address is still active BETA
Business and Tax Identifier Enrichment Enriches identifier information for a given business partner. BETA
Golden Record Generation Generate a consolidated, best-guess record by intelligently combining the input record and identified reference business partners (i.e. lookup matches) BETA
Name Standardization and Harmonization Harmonizes given business partner names based on registered names and legal forms if available BETA
Registered Name Enrichment Enriches business partner name(s) that are officially registered, e.g. in a company register BETA
Service Quality Indicators CDQ cloud services create many results based on fuzzy matching, different rule sets and machine learning techniques. So the reliability and confidence in the correctness of enrichments are highly dependent on the machine's decisions that are not necessarily always accurate. Different kind of quality indicators provides support in deciding and judging a result's correctness. BETA
VAT Registration Data Enrichment Enriches the name and address with which a given VAT identifier is registered and identify if the identifier is a group VAT BETA
Business Partner Type Identification Identify what a given business partner record is representing in terms of representing a legal entity, a branch, or e.g. in industry-specific scenarios such as healthcare a doctor's practice DEVELOPMENT
International Name Enrichment Generate (by translation of the registered or if not available the input name) an English latin-character version of the business partner's name or alternatively enrich it from trusted data sources that provide different language versions DEVELOPMENT
Address Function Identification Allows for identifying the operational use of an address such as bill to-, sold to-, delivery addresses IDEA
Augmented Record Configuration Configure the generation of an augmented record in terms of augmentation views (legal entity view, VAT registration view, operational locations view, business relationship/hierarchy view) and the reference data sources that are employed IDEA