当前位置:网站首页>Yixin Huachen talks about how to do a good job in customer master data management
Yixin Huachen talks about how to do a good job in customer master data management
2022-06-12 01:04:00 【Brother Chen loves learning】
The competition of enterprises in the future is the competition of ecosystem . Suppliers and customers, as an enterprise, are upstream and downstream in the ecosystem , Whether the enterprise can effectively integrate the two information , And whether it can share applications unimpeded within the enterprise , It is directly related to the position of enterprises in market competition . To achieve the connection between upstream and downstream , Facilitate the operation and information flow of relevant businesses within the enterprise , It is very important to manage the customer / supplier master data well .
01、 What is customer / supplier master data ?
Customer / supplier refers to an entity or organization that has external transactions with an enterprise , Including customers and suppliers . When the enterprise is large , Customers and suppliers have a high degree of coincidence , Enterprises will regard these external trading partners as “ merchants ” To unify management .
Customer / supplier master data refers to the data that can meet the needs of cross department business collaboration , Basic information that reflects the status attribute of the customer / supplier entity .
We can regard customer / supplier master data as “ The nerve center ”, Link the enterprise's raw material procurement 、 machining 、 Product packaging 、 Quality testing 、 sales 、 Warehouse logistics 、 Customer satisfaction evaluation and other links , Its timeliness and effectiveness , It affects the accurate analysis and decision-making of information in each link , So as to affect the position of enterprises in market competition .
02、 Why should we manage customer / supplier master data well ?
Because the customer / supplier master data is biased towards the bottom in its own characteristics and application architecture , It mainly plays the role of service and support , Direct benefits don't seem to be so immediate , So its governance is often ignored , This leads to the occurrence of duplicate customers and suppliers 、 Customer / supplier information is missing or invalid 、 Customer data error and other problems , Affect the normal operation of the business .
For example, a supplier fails to meet the supply quality 、 For reasons such as poor service, an enterprise subordinate to the group is no longer used as an alternative supplier , However, the information was not synchronized to by other departments in time , There is still a transaction with the supplier , It has caused further losses to the enterprise ……
Such as customers 、 Inaccurate supplier information , As a result, enterprises are 、 The supplier carries out historical purchase price 、 Data distortion occurs in multi-dimensional statistical analysis such as regional sales , Accurate data cannot support enterprise decision-making ……
The emergence of these problems , Disrupt the normal business decisions of the enterprise , And these questions , You can manage the customer / supplier master data in advance , To avoid . Now let's talk in detail , How to manage customer / supplier master data ?
03、 How to manage customer / supplier master data ?
1. Identification range
Customer / supplier master data is a part of enterprise data , When managing customer / supplier master data , First, we need to identify the customer / supplier master data , Define the scope of requirements , In order to carry out the subsequent optimization work .
To define this scope , We mainly need to consider two dimensions : First, the existing operation and management of the enterprise 、 Production and operation 、 Analyze the business and application systems at the decision-making level , The second is the future strategic development or planning of the enterprise .
The following figure shows the commonly used customer / supplier master data , May refer to .
2. Set the standard
Whether the customer / supplier master data is accurate and standardized , Affect subsequent business and decision-making , Therefore, the determination of customer / supplier master data standard , It is a basic project for customer / supplier master data management . For customer / supplier master data , Mainly from the classification 、 code 、 And attributes to determine the standard .
(1) Classification criteria
The principles of classification design mainly include 4 spot : The first is not heavy, not missing ; Second, the coarse and fine particle size should be reasonable ; The third is to meet business needs ; The fourth is to conform to industry habits .
One important point here is , In the whole process of classification design , The implementation personnel shall repeatedly confirm with the customer . Because once the classification is not done well , Subsequent may lead to a large number of repeated entries , And have a great impact .
(2) coding standard
Customer / supplier code is the unique identification of customer / supplier master data , Digital pipeline code is generally recommended , Try to be brief , It should be able to meet the needs of enterprises in the next ten years ; You can also refer to the actual application management status and use requirements of the enterprise , Conduct “ Fixed meaning code + Digital pipelining ” code , for example : commonly ERP The system uses “ Area classification code + Digital pipelining ”, Facilitate the use habits of enterprise users and reduce the impact on existing business systems .
But in principle , Only one code can be assigned to a customer / supplier , After a customer / supplier is deactivated , This code is no longer assigned to it .
(3) Attribute criteria
To sort out the attribute standards, we can refer to some standards , For example, external international standards 、 National standard ; Industry standards and system requirements at the business level ; In addition, when combing attributes , We HIA You can refer to the data dictionary from the source system , Look at some code tables ; Finally, we can also learn from some good practical experience and achievements to sort out the attribute standards .
As shown in the figure is an example of an attribute standard .

3. Data cleaning
The premise for the value of customer / supplier master data is , It has high data quality , Can be accurate 、 complete 、 Agreement 、 It works 、 And only . For this , We need to clean the customer / supplier master data , This process is mainly divided into two steps: data filtering and data confirmation and warehousing .
(1) Data filtering
First, filter the historical data field through the customer / supplier standard field 、 To reprocess , Filter out the existing and useful customer / supplier data . Customer / supplier master data can be filtered according to the following classification steps :
① Tax number ( Unified social credit code ) And the only customer data : Fill in the information according to the master data template .
② No tax number , But there is the full name of the customer or tax registration code : Get tax number and other fields with tools , And fill in the information according to the master data template .
③ No tax number , But for SAP And SRM、SAP And CIS/DMS Data with code name shared by the system : Sift out similar data , And sort out and merge similar data by means of system tools and manual intervention , Then fill in the information according to the master data template .
④ Communicate with the business department whether to keep other data without screening basis , In case of cleaning, the business department needs to fill in the data according to the master data template .
(2) Confirm warehousing
For the data cleaned by the business system , Summarize according to master data standard template . Then check the cleaned data uniformly , Record the problem data after cleaning and feed back to the business system for re cleaning , So that the data completely meets the customer / supplier master data standard . When the cleaned data meets the standard , Import its initialization into the system , Wait for the system to go online .
4. Data landing
(1) Customer / supplier master data switching
It refers to the main data used by the customer / supplier and the main system , Generally according to the structure of each business system 、 Data volume 、 Importance, etc , Finally determine the appropriate strategy . Common handoff strategies include : Adopt the master data of master data management platform completely 、 Realize the connection with old data through mapping 、 Through mapping and step-by-step data switching , Gradually realize that all systems use unified master data .
(2) Customer / supplier master data distribution
It mainly determines the data distribution method between the customer / supplier master data system and each business system , Generally, there are three kinds of situations : High real-time requirements , Through interface (ESB) distribution ; Batch acquisition , Distribute by exchanging tasks ; The system is busy , Offline batch distribution .
Yixin Huachen's master data management platform Rui code , It can provide diversified master data services . It can support the distribution of customer / supplier master data 、 Inquire about 、 download 、 Analysis etc. , Help maximize the value of master data , At the same time, it provides rich interfaces, which can be quickly integrated with the business platform , Meet the personalized needs of different business systems for customer / supplier master data .
(3) Customer / supplier master data maintenance
It mainly determines the maintenance source and management mode of customer / supplier master data .
Common maintenance strategies include :
① Add master data in the master data management platform 、 Change and delete , Timely distribution of , It is suitable for high control requirements , Customer / supplier master data with low real-time requirements ;
② Add master data in a single business system 、 Change and delete , The master data management platform updates the synchronous data in time and distributes it to other business systems , For a single trusted source , Customer / supplier master data that is not affected by other systems ;
③ Add master data in multiple business systems 、 Change and delete , It is integrated and processed by the master data platform and distributed to all business systems , It is applicable to customer / supplier master data with high real-time requirements .
Use the right platform , The application and maintenance of customer / supplier master data can get twice the result with half the effort . Remade platform supports centralized and distributed management of master data , Strictly regulate the addition of master data 、 change 、 Review and other processes , Realize the full life cycle management of various master data , Can be added manually 、 Import 、 Interface transmission and other ways to collect master data , And provide all-round quality inspection , Ensure the quality of master data .
04、 Summary
Although the customer / supplier master data is relatively stable , But it is not invariable , The management of customer / supplier master data also requires continuous iteration 、 The process of continuous operation . Take customer / supplier master data as the center , Do a good job in its management and Application , Accurate positioning of customers 、 Supplier data , Can effectively help enhance the added value of information , Help enterprises build their competitiveness in the ecosystem .
边栏推荐
- Devops landing practice drip and pit stepping records - (1)
- Article 6: Design of multi-functional intelligent trunk following control system | undergraduate graduation design - [Key Technology - positioning technology related data (UWB WiFi Bluetooth)]
- be based on. NETCORE development blog project starblog - (11) access statistics
- Comparison of OpenCV basic codes of ros2 foxy~galactic~humble
- Vscode - the problem of saving a file and automatically formatting the single quotation mark 'into a double quotation mark'
- 一看就懂的JMeter操作流程
- Online Fox game server - room configuration wizard - component attribute and basic configuration assignment
- One article to show you how to understand the harmonyos application on the shelves
- 写代码复现论文的几点建议!
- Explain asynchronous tasks in detail: the task of function calculation triggers de duplication
猜你喜欢

A knowledge map (super dry goods, recommended collection!)

Explain asynchronous tasks in detail: the task of function calculation triggers de duplication

Started with trust and loyal to profession | datapipeline received a thank you letter from Shandong city commercial bank Alliance

MS-HGAT: 基于记忆增强序列超图注意力网络的信息扩散预测

【ROE】(2)ROE协议

Argodb 3.2 of star ring technology was officially released to comprehensively upgrade ease of use, performance and security

Sharing of Manta network parallel chain solutions by Hufu Research Institute

基于.NetCore开发博客项目 StarBlog - (11) 实现访问统计

leetcodeSQL:614. Secondary followers
![Is interface automation difficult? Take you from 0 to 1 to get started with interface automation test [0 basic can also understand series]](/img/78/f36cdc53b94dc7da576d114a3eb2a6.png)
Is interface automation difficult? Take you from 0 to 1 to get started with interface automation test [0 basic can also understand series]
随机推荐
Flink CDC + Hudi 海量数据入湖在顺丰的实践
模块八-设计消息队列存储消息数据的 MySQL 表格
Go out with a stream
How to optimize plantuml flow diagram (sequence diagram)
Data visualization big screen - big screen cloud minimalist user manual
ROS2之OpenCV基础代码对比foxy~galactic~humble
Equipment encryption of industrial control security
Flutter uses local pictures
Argodb 3.2 of star ring technology was officially released to comprehensively upgrade ease of use, performance and security
一、Flutter 入门学习写一简单客户端
Defect detection, introduction to Halcon case.
1、 Getting started with flutter learn to write a simple client
Henan Zhongchuang - from cloud to edge, how edge computing enables data centers
Elegant throttling / de buffeting decorator under LAYA
一看就懂的JMeter操作流程
一文get,最容易碰上的接口自动化测试问题汇总
100 deep learning cases | day 41: speech recognition - pytorch implementation
be based on. NETCORE development blog project starblog - (11) access statistics
[answer] is ubiquitous language a pseudo innovation?
Article 4: Design of multifunctional intelligent trunk following control system | undergraduate graduation project - [data search skills + reference resource integration]