Tutorial: How to monitor Business Partner updates? (API Approach)
Overview
Use case
Customer and vendor data quality decreases, even if the data is not touched, e.g., due to address changes, M&A, or insolvencies. Keeping the data up to date manually is a complex and high effort on a global scale. Commercial registers and other reference data sources have to be monitored continuously. And for countries without reliable reference data, data has to be researched business partner by business partner. The CDQ Business Partner Update Monitoring takes over the effort of manual update screening. Business Partner Updates are automatically collected and made available in an easy to analyze and integrate way.
Use Case: Situation, Approach and Results |
Learning Goals
In this tutorial, you will learn how to:
- Create Augmentation Configuration for updates
- Create Augmentation Monitor
- Read Subscriptions
- Read updates
Prerequisites
Authorization
Before trying CDQ APIs, user must be authenticated:
- Paste the API Key in the console's security bar into the
X-API-KEY
field.
- After pasting the API Key, the green padlock will appear.
Be careful
Green padlock doesn't mean that the API Key was pasted correctly.
- Check your API key for missing characters or extra space before trying.
No API Key?
- Check how to get one on authentication page.
- Follow the steps above.
Data Mirror
For tutorial purposes, the CDQ Data Mirror is used. Use your organization's Data Mirror to recreate the happy path.
info
Get more information about Data Mirror Setup and Synchronization here.
Step 1: Create Augmentation Configuration
List available reference Data Sources
To receive updates, define which data sources should be monitored. All data sources should be activated in the Global settings.
To list all available reference Data Sources:
- Use the List Data Sources of Update Monitors endpoint,
- Send the request,
info
Visit List Data Sources of Update Monitors documentation page for more details.
- Select the desired reference Data Source.
All available reference Data Sources will be listed in the schema below:
{
"referenceDataSources": [
{
"aleiPrefix": "REF_DATASOURCE_PREFIX",
"technicalKey": "REF_DATASOURCE_TECHNICAL_KEY"
}
]
}
Create the configuration
- Use the Create augmentation configuration endpoint,
- Select the Client Configuration (VIES and CH_UIDR) example,
- Send the request,
- Save
id
value from the response for next step.
{
"id": "YOUR_AUGMENTATION_CONFIGURATION_ID"
}
attention
Remember, the Augmentation Configuration must be created in the same workspace as data mirrors with Business Partners. Use the API KEY with correct workspace assigned.
Step2: Create an Augmentation Monitor
Selected reference Data Sources can be added to Augmentation Monitor. To activate or make changes to the Augmentation Monitor for your data source or sources:
- Use the Create Update Monitors endpoint to send the below request.
REMEMBER!
The Create Update Monitors endpoint's request must contain all current and updated reference Data Sources. If reference Data Source is linked to your Data Source and the request does not contain it the link will be removed.
- Select Create an Augmentation Monitor example,
- Replace values in the example:
YOUR_DATA_SOURCE_ID
with proper data sourceID
orIDs
,YOUR_AUGMENTATION_CONFIGURATION_ID
with proper configurationID
,
- Send the request.
Step 3: Browse the subscription
Browsing subscription allows seeing the list of Business Partners to be monitored for updates.
Check already subscribed Business Partners:
- Use the Read Links endpoint to send the below request,
- Replace values in the example:
YOUR_STORAGE_ID
with proper Data Storage ID in a Parameters section,
- Clean the:
startAfter
filed in a Parameters section,
- Send the request.
true
indicates that particular Business Partner is
subscribed for update monitoring.{
"id": "BUSINESS_PARTNER_ID",
"updateMonitoring": true
}
info
true
by default.attention
GOLDEN_RECORD
and update Business Parnters with new, curated data.
Get back to Step 1 and create a new configuration using the Client Configuration
(VIES and CH_UIDR) example.Step 4: Read updates
Once linkage is created, it's possible to check updates.
Regular updates
When the update monitors are updated and all necessary Business Partners are updated, you can check Business Partners updates.
To read all updates:
- Use the Read Business Partner Updates endpoint to send the below request.
- Replace values in the example:
YOUR_STORAGE_ID
with proper Data Storage ID in a Parameters section,
- Clean below fields in the Parameters section:
conceptClassification
dataTransformationDefinitionId
from
startAfter
summaryClassification
- Send the request.
Filtering
A list of updated Business Partners can be filtered in various ways, with tags being the most powerful and important. Tags combine concepts (e.g.,NAME_LOCAL
, IDENTIFIER
, LOCALITY
) with actions (e.g., ADDED
, MODIFIED
). There are two
types of classification filters:summaryClassification
: This filter provides Business Partners with a summary classification, which is determined by the highest classificationlevel among all Business Partner concepts.conceptClassification
: This filter indicates the classification of a Business Partner's concept (e.g.,name
,street
,legal
form
).
LOCAL_NAME
was MODIFIED
and this change was classified as MAJOR. When filtering by tag and summaryClassification, the endpoint returns
all Business Partners where the specified tags were added to the summary and the general summary classification is, for example,
IDENTIFIER_ADDED
, + the highest classification for all updates MINOR
. Additional filtering options include country,
provenance, and external IDs. Providing the data source (or your mirror) in the request can enhance response speed. It's
possible to check the total number of updates using featuresOn NUMBER_OF_TOTAL
, but can slow down the response.There is also an option to use updateTagsProfiles. Profiles are container for tags, grouped in: ADDRESS_DATA
, LEGAL_DATA
,
RELATIONS
, VAT_DATA
.info
The list of all filtering options can be found in the endpoint description.
Generate seed updates
Seed updates are generated as an initial step in the update monitoring. All business partners from the mirror, for which linkage was created, receive full BP from reference data sources with the comparison (update assessment). In case update monitoring was turned on in the past, and some updates were not consumed, there is a possibility to generate seed updates on demand. It's possible to do that for a specific BP or for a big, defined group.
- Use the Start Seed Updates Generate Job endpoint to send the below request,
- Select Seed Updates example,
attention
If there is no dropdown-list to choose the example, Seed Updates example is set by default.
- Set the
storageId
in the Parameters section, - Send the request.
- Save the
jobId
for the next step.
Additional info about parameters
Parameters:referenceDataSource
(required): provide a technicalKey of reference data source, for which linked Business Partners from your mirror should get seed updates
externalId
,
businessPartnerIds
; or could be provided for a group of Business Partners from specific dataSourceIds
, countryShortName
.- Check the status of the job using the Poll Seed Updates Generate Job endpoint.
- Set the
jobId
andstorageId
in the Parameters section, - Send the request.
Customized response
Response from the Read Business Partner Updates endpoint can be customized to the required structure and chosen elements. To do that, it's required to have Data Transformation Definition.
attention
The Data Transformation Definition can be created only by CSMs.
A customized response is provided in the "jsonRecord" section in the response from the Read Business Partner Updates endpoint:
{
"limit": "100",
"total": "67",
"startAfter": "5712566172571652",
"nextStartAfter": "5712566172571652",
"values": [
{
"id": "5712566172571652",
"businessPartnerId": "63e635235c06b7396330fe40",
"externalBusinessPartnerId": "The ID managed in the customer's SAP systems.",
"updatedBusinessPartner": {
"id": "63e635235c06b7396330fe40",
"summary": {},
"names": [],
"legalForm": {},
"identifiers": [],
"categories": [],
"status": {},
"addresses": [],
"externalId": "The ID managed in the customer's SAP systems.",
"profile": {},
"types": [],
"relations": [],
"jsonRecord": "{\"key\":\"value\"}"
},
"storageBusinessPartner": {}
}
]
}
Option 1 - DTD ID provided in the request
Ask dedicated CSM to create a Data Transformation Definition based on provided needs in the workspace where the Augmentation Monitor is created.
- Use the Read Business Partner Updates endpoint to send the below request.
- Replace values in the example:
YOUR_STORAGE_ID
with proper Data Storage ID in a Parameters section,dataTransformationDefinitionId
with the Data Transformation Definition ID (Provided by CMS) in the Parameters section,
- Clean below fields in the Parameters section:
conceptClassification
from
startAfter
summaryClassification
- Send the request.
Option 2 - Configuration assigned to the API KEY
Ask CSM to create a Data Transformation Definition based on your needs in the workspace where the Augmentation Monitor is created.
- Go to the Data Transformation Configurator APP,
- Create a new configuration,
- Select created Data Transformation Definition in the Business Partner Updates selector,
- Save the configuration,
- Go to the API Key Management,
- Select the existing API KEY or create a new one and click a "See Details" button,
- Scroll down and assign a new configuration for Data Transformation Configuration,
- Save the changes,
Use API KEY in requests to get data in a customized way from the Read Business Partner Updates endpoint.
To read updates:
- Use the Read Business Partner Updates endpoint to send the below request.
- Replace values in the example:
YOUR_STORAGE_ID
with proper Data Storage ID in a Parameters section,
- Clean below fields in the Parameters section:
conceptClassification
dataTransformationDefinitionId
from
startAfter
summaryClassification
- Send the request.
Update Report
CDQ Cloud APPs offer the creation of update report. Report for now provides data in the old model (v4). More about creating reports check here.
Your opinion matters!
We are constantly working on providing an outstanding user experience with our products. Please share your opinion about this tutorial!
Mail our developer-portal team: developer-portal@cdq.com