Enterprise service bus-based master data system integration method

Abstract

The application discloses a kind of based on enterprise service bus's main data system integration method, specifically related to enterprise informatization technical field, including the following steps: step 1, by enterprise service bus receives project declaration system, science and technology service system, proxy accounting system and customer management system sends enterprise basic data, service matter data, business material data and business state data, and according to preset data interface protocol to the data is parsed, format verification and field integrity check.The application realizes the data standardization, unified coding and correlation sharing of project declaration, science and technology service and proxy accounting system by enterprise service bus and unified main data model, reduces duplicate data and information island;Through message routing, abnormal retry, conflict processing and version control, improve the consistency, reliability and expansibility of data exchange;Through permission management, data desensitization and operation trace, improve data security and business traceability ability.

Description

Technical Field

[0001] This invention relates to the field of enterprise information technology, and more specifically, to a master data system integration method based on an enterprise service bus. Background Technology

[0002] Currently, enterprise service agencies typically use separate project application systems, technology service management systems, accounting systems, customer management systems, and financial management systems to conduct their business. Due to differences in system development timelines, data standards, and development methods, the same enterprise may exhibit inconsistencies in information such as name, unified social credit code, contact person, address, and service items across different systems. This easily leads to data duplication, information silos, difficulty in linking business data, and asynchronous data updates. Existing systems typically exchange data via point-to-point interfaces. When the number of business systems increases or business processes change, multiple interfaces need to be repeatedly developed and maintained, resulting in high integration costs and poor scalability. Furthermore, existing data exchange methods struggle to provide unified encoding, version control, conflict resolution, and full-process auditing of master data, failing to effectively guarantee the consistency, integrity, and traceability of business data such as project applications, technology services, and accounting.

[0003] Therefore, there is an urgent need for a master data system integration method based on enterprise service bus to solve the above problems. Summary of the Invention

[0004] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a master data system integration method based on an enterprise service bus. This invention, through an enterprise service bus and a unified master data model, achieves data standardization, unified coding, and associated sharing in project application, technology service, and agency accounting systems, reducing duplicate data and information silos; improves the consistency, reliability, and scalability of data exchange through message routing, exception retries, conflict handling, and version control; and enhances data security and business traceability through access control, data anonymization, and operation logging, thereby solving the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a master data system integration method based on an enterprise service bus, comprising the following steps: Step 1: Receive basic enterprise data, service item data, business material data, and business status data sent by the project application system, technology service system, agency accounting system, and customer management system through the enterprise service bus, and parse, format-check, and field integrity-check the data according to the preset data interface protocol; Step 2: Based on the unified master data model, perform field mapping, data type conversion, code conversion and standardization on the verified data to form standard enterprise master data, standard service item data and standard business material data; Step 3: Match enterprise records in different business systems according to the unified social credit code, enterprise internal code, enterprise name and preset matching rules, generate or update corresponding master data records, and assign a unique enterprise master data identifier to each enterprise master data record. Step 4: Based on the service category, service contract, service period, responsible personnel, and business system source, generate unique service item identifiers for project application, technology services, and bookkeeping services, and establish the association between the enterprise master data identifier and the service item identifier; Step 5: Encapsulate the standardized master data and its change information into a unified business message through the Enterprise Service Bus, and route the business message to one or more target business systems according to the data permissions, subscription relationships and interface protocols of the target business systems; Step 6: The target business system performs add, modify, associate, review, archive, or status synchronization operations based on the business message, and feeds back the processing results to the master data system through the enterprise service bus; Step 7: The master data system updates the synchronization status based on the processing results fed back by the target business system. When field conflicts, missing data, duplicate records, message transmission failures, or inconsistent business status are detected, an exception record is generated, and retry, manual confirmation, version rollback, or conflict merging are performed. Step 8: Log the operations of adding, modifying, publishing, synchronizing, reviewing, handling exceptions, querying, downloading and exporting master data, and form a traceable master data operation chain based on the operation user, business system, operation time, data version and operation type; Step 9: Set data access permissions according to user role, organization, responsible customer, responsible service item and data sensitivity level. De-identify or encrypt the display of identity information, bank account information, tax information and financial amount. Perform permission verification during data release, interface call, batch export and exception handling. Step 10: Generate business management indicators based on the completeness rate of materials, task completion rate, timely processing rate, number of exceptions, approval rate and service status of service items, and output statistical results in the enterprise dimension, service category dimension, business personnel dimension and time dimension through the management terminal.

[0006] In a preferred embodiment, the unified master data model includes basic enterprise information, legal representative information, contact person information, registered address, business status, enterprise tags, service item information, service personnel information, business material information, and business status information. The basic enterprise information uses the unified social credit code as the preferred matching field.

[0007] In a preferred embodiment, the standardization process includes unifying full-width and half-width characters in company names, removing spaces, converting case, and cleaning special characters; converting phone numbers, dates, amounts, addresses, and certificate numbers according to preset formats; and converting service categories, company types, material types, review status, and business status using a unified code table.

[0008] In a preferred embodiment, the enterprise record matching includes determining that enterprise records in different business systems with the same unified social credit code are the same enterprise; when the unified social credit code is missing or inconsistent, a matching score is calculated based on the similarity of enterprise names, legal representative information, registered address, contact number, and historical association relationships; when the matching score reaches a preset threshold, an association relationship between enterprise records is established; when the matching score is lower than the preset threshold, the corresponding record is marked as a record awaiting manual confirmation.

[0009] In a preferred embodiment, the unique service item identifier includes an enterprise master data identifier, a service category code, a business year, a sequence number, and a check code; the service category includes at least project application, technology services, and bookkeeping services.

[0010] In a preferred embodiment, for project application business, the enterprise service bus synchronizes with the project application system the enterprise entity information, basic information of the application project, application conditions, application material list, material review status, and submission status; for science and technology service business, the enterprise service bus synchronizes with the science and technology service requirements, technical fields, service tasks, responsible personnel, service process records, and service results; for bookkeeping agency business, the enterprise service bus synchronizes with the invoice receipt status, invoice identification results, accounting subjects, voucher status, ledger status, report status, and application status.

[0011] In a preferred embodiment, the unified business message includes a message number, message type, source business system identifier, target business system identifier, enterprise master data identifier, service item identifier, data version number, change time, change fields, business data, and verification information; the enterprise service bus performs message publishing, subscription, filtering, routing, caching, retrying, and sequence control according to the message type.

[0012] In a preferred embodiment, the conflict merging process includes determining the target field value according to field priority, data source credibility, update time, and audit status; when the field values ​​of multiple data sources cannot be determined according to preset rules, each data version is retained, a conflict pending task is generated, and a new master data version is formed after manual confirmation.

[0013] The technical effects and advantages of this invention are as follows: This invention decouples and integrates business systems such as project application, technology services, and bookkeeping through an enterprise service bus and a unified master data model. It achieves unified coding, standardized conversion, and associated management of enterprise information, service items, business materials, and business status, reducing duplicate data and information silos. Through unified message encapsulation, subscription routing, exception retries, and conflict merging, it improves the stability, consistency, and scalability of cross-system data exchange. It establishes associations between the enterprise and different service businesses through unique enterprise master data identifiers and service item identifiers, facilitating business collaboration and end-to-end tracking. Version control, access control, data anonymization, and operation logs enhance the security of sensitive data and the auditability of data processing. Simultaneously, it provides a unified data foundation for project application progress management, technology service process management, and bookkeeping business collaboration. Detailed Implementation

[0014] The technical solutions in the embodiments of the present invention will be clearly and completely described below. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0015] This invention provides a master data system integration method based on an enterprise service bus, comprising the following steps: Step 1: Receive basic enterprise data, service item data, business material data, and business status data sent by the project application system, technology service system, agency accounting system, and customer management system through the enterprise service bus, and parse, format-check, and field integrity-check the data according to the preset data interface protocol; Step 2: Based on the unified master data model, perform field mapping, data type conversion, code conversion and standardization on the verified data to form standard enterprise master data, standard service item data and standard business material data; Step 3: Match enterprise records in different business systems according to the unified social credit code, enterprise internal code, enterprise name and preset matching rules, generate or update corresponding master data records, and assign a unique enterprise master data identifier to each enterprise master data record. Step 4: Based on the service category, service contract, service period, responsible personnel, and business system source, generate unique service item identifiers for project application, technology services, and bookkeeping services, and establish the association between the enterprise master data identifier and the service item identifier; Step 5: Encapsulate the standardized master data and its change information into a unified business message through the Enterprise Service Bus, and route the business message to one or more target business systems according to the data permissions, subscription relationships and interface protocols of the target business systems; Step 6: The target business system performs add, modify, associate, review, archive, or status synchronization operations based on the business message, and feeds back the processing results to the master data system through the enterprise service bus; Step 7: The master data system updates the synchronization status based on the processing results fed back by the target business system. When field conflicts, missing data, duplicate records, message transmission failures, or inconsistent business status are detected, an exception record is generated, and retry, manual confirmation, version rollback, or conflict merging are performed. Step 8: Log the operations of adding, modifying, publishing, synchronizing, reviewing, handling exceptions, querying, downloading and exporting master data, and form a traceable master data operation chain based on the operation user, business system, operation time, data version and operation type; Step 9: Set data access permissions according to user role, organization, responsible customer, responsible service item and data sensitivity level. De-identify or encrypt the display of identity information, bank account information, tax information and financial amount. Perform permission verification during data release, interface call, batch export and exception handling. Step 10: Generate business management indicators based on the completeness rate of materials, task completion rate, timely processing rate, number of exceptions, approval rate and service status of service items, and output statistical results in the enterprise dimension, service category dimension, business personnel dimension and time dimension through the management terminal.

[0016] The unified master data model includes basic enterprise information, legal representative information, contact person information, registered address, business status, enterprise tags, service item information, service personnel information, business material information, and business status information. The basic enterprise information uses the unified social credit code as the preferred matching field.

[0017] The standardization process includes unifying full-width and half-width characters in company names, removing spaces, converting case, and cleaning special characters; converting phone numbers, dates, amounts, addresses, and license numbers according to preset formats; and using a unified code table to convert service categories, company types, material types, review status, and business status.

[0018] The enterprise record matching includes determining that enterprise records in different business systems with the same unified social credit code are the same enterprise; when the unified social credit code is missing or inconsistent, a matching score is calculated based on the similarity of enterprise names, legal representative information, registered address, contact number, and historical association; when the matching score reaches a preset threshold, an association relationship between enterprise records is established; when the matching score is lower than the preset threshold, the corresponding record is marked as a record awaiting manual confirmation.

[0019] The unique service item identifier includes the enterprise master data identifier, service category code, business year, sequence number, and verification code; the service category includes at least project application, technology services, and bookkeeping services.

[0020] For project application, the enterprise service bus synchronizes with the project application system the enterprise entity information, basic information of the application project, application conditions, list of application materials, material review status, and submission status. For science and technology service, the enterprise service bus synchronizes with the science and technology service requirements, technical fields, service tasks, responsible personnel, service process records, and service results. For bookkeeping services, the enterprise service bus synchronizes with the invoice receipt status, invoice identification results, accounting subjects, voucher status, ledger status, report status, and application status.

[0021] The unified business message includes message number, message type, source business system identifier, target business system identifier, enterprise master data identifier, service item identifier, data version number, change time, change fields, business data, and verification information; the enterprise service bus performs message publishing, subscription, filtering, routing, caching, retry, and sequence control according to the message type.

[0022] The conflict merging process includes determining the target field value based on field priority, data source credibility, update time, and audit status; when the field values ​​of multiple data sources cannot be determined according to preset rules, each data version is retained, a conflict pending task is generated, and a new master data version is formed after manual confirmation.

[0023] This invention adopts an integrated architecture consisting of a master data management platform, an enterprise service bus, a project application system, a technology service system, an accounting agency system, a customer management system, and a unified authentication system. The master data management platform is used to maintain enterprise master data, a unified code table, data matching rules, field priorities, and data versions; the enterprise service bus is used to provide interface adaptation, message conversion, message routing, message subscription, caching, retry, and logging functions.

[0024] When enterprise information is first entered into the system, the Enterprise Service Bus receives information submitted by the source system, including the enterprise name, unified social credit code, legal representative, contact person, contact number, registered address, operating status, and industry. The system then parses the data according to the interface protocol. The master data management platform performs non-empty checks, format checks, certificate number checks, and duplicate checks on the data. For enterprises with a unified social credit code, the system uses the unified social credit code as the primary matching criterion; for data lacking a unified social credit code, a matching score is calculated by combining the enterprise name, legal representative, contact number, and registered address. Upon successful matching, the system merges the data into existing enterprise master data records; if matching fails and cannot be confirmed, a task awaiting manual confirmation is generated.

[0025] After the enterprise master data is established, business personnel can create project applications, technology services, or bookkeeping services based on customer needs. The master data management platform generates a unique service item identifier according to the service category, business year, and sequence number, and associates this identifier with the enterprise master data identifier, service contract, responsible personnel, service period, and business status. In the project application process, the system generates application conditions and a list of materials based on the project type, associates materials such as business licenses, financial statements, intellectual property certificates, and project plans with corresponding task nodes, and synchronizes enterprise information and material review status to the project application system.

[0026] In technology service operations, the system records customer technology needs, technical fields, service content, service personnel, service nodes, and service deliverables. It also synchronizes the status of needs registration, task allocation, process recording, deliverables, and customer confirmation to relevant systems via the enterprise service bus. In bookkeeping services, the system receives invoices and financial documents, and synchronizes the invoice receipt status, invoice identification results, accounting subjects, voucher processing status, ledger status, financial statement status, and tax declaration status to the bookkeeping system.

[0027] When enterprise master data or service item data changes, the master data management platform generates a standard business message containing a message number, data version number, changed fields, change time, and business data, and sends the message to the corresponding business system according to the subscription relationship. The target business system processes the message and returns a success, failure, or pending confirmation status. For messages with transmission failures, the enterprise service bus automatically retries the message a preset number of times. For field conflicts, the system determines the field value based on the data source's credibility, update time, and audit status. If automatic determination is not possible, all versions of data are retained, and a conflict resolution task is generated. A new master data version is then released after confirmation by authorized personnel.

[0028] Regarding data security, the system restricts access for different personnel through unified authentication and role-based access control. Business personnel can only access the enterprises and services they are responsible for, managers can access data within their authorized organizational scope, and auditors can query operation logs but cannot directly modify business data. For bank accounts, tax information, identity verification information, and financial amounts, the system anonymizes the data during display and encrypts it during transmission. It also records the user, time, data version, and processing result for data query, modification, review, download, export, and publishing operations, thus forming a complete business data traceability chain.

[0029] This invention decouples and integrates business systems such as project application, technology services, and bookkeeping through an enterprise service bus and a unified master data model. It achieves unified coding, standardized conversion, and associated management of enterprise information, service items, business materials, and business status, reducing duplicate data and information silos. Through unified message encapsulation, subscription routing, exception retries, and conflict merging, it improves the stability, consistency, and scalability of cross-system data exchange. It establishes associations between the enterprise and different service businesses through unique enterprise master data identifiers and service item identifiers, facilitating business collaboration and end-to-end tracking. Version control, access control, data anonymization, and operation logs enhance the security of sensitive data and the auditability of data processing. Simultaneously, it provides a unified data foundation for project application progress management, technology service process management, and bookkeeping business collaboration.

[0030] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A master data system integration method based on Enterprise Service Bus, characterized in that, Includes the following steps: Step 1: Receive basic enterprise data, service item data, business material data, and business status data sent by the project application system, technology service system, agency accounting system, and customer management system through the enterprise service bus, and parse, format-check, and field integrity-check the data according to the preset data interface protocol; Step 2: Based on the unified master data model, perform field mapping, data type conversion, code conversion and standardization on the verified data to form standard enterprise master data, standard service item data and standard business material data; Step 3: Match enterprise records in different business systems according to the unified social credit code, enterprise internal code, enterprise name and preset matching rules, generate or update corresponding master data records, and assign a unique enterprise master data identifier to each enterprise master data record. Step 4: Based on the service category, service contract, service period, responsible personnel, and business system source, generate unique service item identifiers for project application, technology services, and bookkeeping services, and establish the association between the enterprise master data identifier and the service item identifier; Step 5: Encapsulate the standardized master data and its change information into a unified business message through the Enterprise Service Bus, and route the business message to one or more target business systems according to the data permissions, subscription relationships and interface protocols of the target business systems; Step 6: The target business system performs add, modify, associate, review, archive, or status synchronization operations based on the business message, and feeds back the processing results to the master data system through the enterprise service bus; Step 7: The master data system updates the synchronization status based on the processing results fed back by the target business system. When field conflicts, missing data, duplicate records, message transmission failures, or inconsistent business status are detected, an exception record is generated, and retry, manual confirmation, version rollback, or conflict merging are performed. Step 8: Log the operations of adding, modifying, publishing, synchronizing, reviewing, handling exceptions, querying, downloading and exporting master data, and form a traceable master data operation chain based on the operation user, business system, operation time, data version and operation type; Step 9: Set data access permissions according to user role, organization, responsible customer, responsible service item and data sensitivity level. De-identify or encrypt the display of identity information, bank account information, tax information and financial amount. Perform permission verification during data release, interface call, batch export and exception handling. Step 10: Generate business management indicators based on the completeness rate of materials, task completion rate, timely processing rate, number of exceptions, approval rate and service status of service items, and output statistical results in the enterprise dimension, service category dimension, business personnel dimension and time dimension through the management terminal.

2. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The unified master data model includes basic enterprise information, legal representative information, contact person information, registered address, business status, enterprise tags, service item information, service personnel information, business material information, and business status information. The basic enterprise information uses the unified social credit code as the preferred matching field.

3. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The standardization process includes unifying full-width and half-width characters in company names, removing spaces, converting case, and cleaning special characters; and converting phone numbers, dates, amounts, addresses, and certificate numbers according to preset formats. A unified code table is used to convert service categories, enterprise types, material types, review status, and business status.

4. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The enterprise record matching includes determining that enterprise records in different business systems with the same unified social credit code are the same enterprise; when the unified social credit code is missing or inconsistent, a matching score is calculated based on the similarity of enterprise names, legal representative information, registered address, contact number, and historical association; when the matching score reaches a preset threshold, an association relationship between enterprise records is established; when the matching score is lower than the preset threshold, the corresponding record is marked as a record awaiting manual confirmation.

5. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The unique service item identifier includes the enterprise master data identifier, service category code, business year, sequence number, and verification code; the service category includes at least project application, technology services, and bookkeeping services.

6. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: For project application, the enterprise service bus synchronizes with the project application system the enterprise entity information, basic information of the application project, application conditions, list of application materials, material review status, and submission status. For science and technology service, the enterprise service bus synchronizes with the science and technology service requirements, technical fields, service tasks, responsible personnel, service process records, and service results. For bookkeeping services, the enterprise service bus synchronizes with the invoice receipt status, invoice identification results, accounting subjects, voucher status, ledger status, report status, and application status.

7. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The unified business message includes message number, message type, source business system identifier, target business system identifier, enterprise master data identifier, service item identifier, data version number, change time, changed fields, business data, and verification information; The enterprise service bus performs message publishing, subscription, filtering, routing, caching, retrying, and sequence control based on message type.

8. The master data system integration method based on Enterprise Service Bus according to claim 1, characterized in that: The conflict merging process includes determining the target field value based on field priority, data source credibility, update time, and audit status; when the field values ​​of multiple data sources cannot be determined according to preset rules, each data version is retained, a conflict pending task is generated, and a new master data version is formed after manual confirmation.