Copyright©2025 Yonyou Group All rights reserved.Without the written permission of Yonyou Group, no part or whole of the content of this user manual may be copied, reproduced, translated, or reduced for any purpose. The content of this user manual may change without notice, please be aware.Please note: The content of this user manual does not represent any commitments made by Yonyou.Overall OverviewData integration mainly undertakes the data integration of Yonyou Cloud and ERP hybrid cloud application scenarios and social applications; it provides connection configuration, data exchange definitions, data synchronization tasks, and scheduled task management. In the era of cloud computing, the architecture of enterprise application systems often exists in a hybrid cloud manner, such as purchasing ERP deployed in a private cloud environment, while a business system in a certain domain is based on a cloud service architecture. Data integration can facilitate the collaboration of master data and business documents, while the open connection service also provides a rich set of e-commerce connectors to help enterprises quickly connect to social e-commerce platforms, achieving cooperation and sourcing for product procurement.Data integration is pre-configured to provide enterprises with out-of-the-box integration services, offering synchronization of over 200 types of data and connecting various ERPs (NC, NCC, U8, U8C, U9, etc.). For customers who are already using NC/NCC/U8/U8C/U9, if they need to purchase cloud services (Social and Collaboration, Human Resource Management, Sales and Marketing, Procurement Management, Financial Management, etc.) while keeping the existing system unchanged, they can achieve master data synchronization and business document collaboration through data integration. The master data is primarily controlled by ERP, meaning that the main maintainer of the master data is ERP. The well-maintained master data is synchronized to the cloud through data integration, serving as the data foundation for conducting business in the cloud. The integration of business documents mainly varies according to different domain scenarios. For example, in the procurement scenario, the purchase demand document is uploaded to the cloud, and Yonyou Cloud initiates sourcing and other procurement processes. After generating the purchase order, it is sent back to ERP, thus achieving business integration. The pre-configured master data includes personnel, organization, material, supplier, and customer. Currently, master data synchronization only supports integration within a single group, and business documents are generally pre-configured as integration assets by different domains.Master Data Synchronization: Yonyou ERP customers, after years of system operation, have accumulated master data that the business relies on. After purchasing Yonyou's SaaS service, to achieve an integrated experience, it is necessary to first synchronize the master data to Yonyou Cloud as the golden data for the business. The integration service enables master data synchronization across network environments and systems through out-of-the-box, guided configuration, laying a solid foundation for business collaboration.Business Collaboration: Based on master data synchronization, it enables the flow of business documents between ERP and cloud services, facilitating cross-system and cross-cloud collaboration, ensuring an integrated experience for Yonyou customers, forming a smooth product integration system, and supporting the creation of out-of-the-box integration assets that can be directly reused by frontline personnel.App MapData Conversion RulesIntegration Scheme DesignData Synchronization TaskAlert ConfigurationApp ValueStarting from business scenarios, integrate development into assets, covering integration scenarios within the scenarios, allowing for the integration of ERP and cloud services without the need for development during implementation;The domain clouds that have been adapted for data integration mainly include: Human Resource Management, Social and Collaboration, Procurement Management, Sales and Marketing, Manufacturing, etc. This part of the domain can achieve master data synchronization between ERP and YonBP through data integration, and can also solve the security connectivity issues between private environments and public clouds through the data integration gateway;Each domain has pre-integrated a large number of data synchronization assets through data integration. Once initialization is complete, data integration can be quickly achieved. Taking NCC as an example, it has pre-integrated expense items, customers, materials, settlement methods, product lines, measurement units, basic customer classifications, material classifications, brands, customer bank accounts, material allocation relationships, customer delivery addresses, customer contacts, administrative organizations, prefabricated global group organizations, departments, financial organizations, asset functions, personnel categories, personnel, accounting delegation relationships, functional shared master tables, job categories, titles, functional shared sub-tables, positions, employee bank accounts, countries and regions, bank branches, administrative regions, document types, currencies, bank types, project types, projects, organization bank accounts, organization cash accounts, custom file maintenance, professional qualifications, customer properties, supplier contacts, supplier classifications, suppliers, supplier bank accounts, supplier contacts, document types, multilingual, bank types, currencies, bank records, countries and regions, ethnicities, education levels, degrees, learning methods, household registration types, spot inspection standard associated equipment, professions, asset categories, asset cards, asset statuses, measured items, spot inspection standard settings, supplier contacts, technical parameters, asset category technical parameters, critical levels, locations, spot inspection standards, reward situations, job levels, professional qualifications, title records, personnel resignations, change types, job grades, personnel part-time jobs, personnel contracts, personnel social relationships, change reasons, contract subjects, return reasons, personnel education levels, work information, personnel resumes, personnel performance;The management of data synchronization tasks provides users with certain extension capabilities, allowing for easy modification of scripts for data capture, conveniently solving the row and column-level data range for synchronized data, thus quickly meeting customer personalized needs.Data integration supports the use of public base connectors to achieve cross-system data synchronization needs, such as BIP and third-party system document integration.Application ScenarioScenario: ERP-Purchase Service IntegrationNote: The business scenario only provides an example from one domain. You can consult the corresponding domain product liaison for business solutions during use.Business DescriptionTypical Scenario: ERP - Procurement Service IntegrationERP and Procurement Management achieve synchronization of master data through data integration. Based on the premise of master data synchronization, the procurement scenario's business collaboration across systems is realized, generating a purchase requisition in ERP. With out-of-the-box integration assets through data integration, bidirectional synchronization between ERP and BIP documents is achieved, generating purchase demand. Sourcing procurement is completed in the procurement service, and the generated purchase order is sent back to ERP. After the purchased goods arrive, an arrival notice is generated, which is also synchronized to ERP. Business data synchronization is facilitated through the hybrid cloud channel and integration assets, promoting business flow across environments and applications.Integration DesignOverall OverviewIn the rapid data integration scenario, the provided integration flow is fixed. It is designed through a visual configuration method to achieve the integration process design of a pair of integration objects, suitable for master data synchronization between systems and upstream and downstream business data collaboration scenarios.Data Conversion RulesFunction DescriptionData Conversion Rules: Tenants can modify the mapping relationships. Generally, adjustments are not needed; in fact, making adjustments may lead to incorrect mappings. Modifications to the mapping should only be made in special cases, such as when the enterprise has specific mapping requirements.Business RuleManagement of mapping relationships for data exchange definitions;Add or delete data mapping.Operation InstructionsFunction Entry: Access the functionality through Menu, Integration Connection Service > Data Integration > Integration Design > Data Conversion Rules.Click the operation column button to enter the Data Exchange Mapping Configuration page:Click on the mapping relationship to display data mapping, and you can change the mapping relationship according to actual needs.After completing the maintenance, click
to complete the data mapping configuration.Integration Scheme DesignFunction DescriptionThe integration scheme is upgraded to a new version of the integrated application; an integrated application will contain multiple integration schemes to complete a complete business scenario;The integrated application includes a pair of connectors for data integration design;The integration scheme uses the objects, operations, mapping relationships, value conversion rules, source operations, and target operations under the connector to create a collection of inter-data schemes.Key AppsAdd/Edit App: Create Integrated Application, select the Connector to be used;Add/Edit Integration Scheme: The design of the Integration Scheme, including the selection of Integration Objects, setting mapping relationships, configuring prerequisite Tasks and other operational schemes, and setting filtering conditions;Initialize Integrated Application: Integration should be initialized based on the purchased Integration Asset Package.Column DescriptionColumn NameDescriptionIntegrated Application CodeUsed to distinguish different integrated application codesIntegrated Application NameUsed to distinguish different integrated application namesIntegration Scheme CodeUsed to distinguish different integration scheme codesIntegration Scheme NameUsed to distinguish different integration scheme namesSource Integration ObjectThe integration object serving as the data source for integrationTarget Integration ObjectThe integration object serving as the data target for integrationModeFollow-up processing scheme when data synchronization encounters issues; options include ignore on error or terminate on errorAutomatic Mapping RulesRules for automatic mapping between source and target objects, providing three options: none, by code, by nameIs Tree StructureIndicates whether it is a tree structureEnable CharacteristicsNew architecture supports using characteristics as auxiliary properties for data synchronizationData Conversion RulesSet the mapping relationship between source and target objectsTranslatorMapping translation capability between source and target dataOperationSet the method for source operations to retrieve data and target operations to write dataOperation InstructionsAdd/Edit Integrated ApplicationFill in the basic information of the integrated application: You need to fill in the name, code, and select a pair of connectors to determine the subsequent integration scheme and task execution channel;Once the connector is selected, it cannot be modified, only the connection configuration...
