1. Connection between K3C Price List & Salable Range
first step:
First enter the object configuration of the K3 Cloud price list.
Step two:
Add a custom slave object in the object, the object name is optional, the code must be: BD_SAL_PriceList.AvailablePriceBookObj, and the split type is slave object (details).
third step:
After configuring the object, enter the field configuration.
The field content is as shown in the figure below. The reference field name of the price list must be: AvailablePriceBookObj.
The object in K3 Cloud is the sales price list (BD_SAL_PriceList, if there is no preset object, please contact R&D to add it), which needs to be connected to the two object price list (PriceBookObj) and the available range (AvailableRangeObj) in CRM.
the fourth step:
Create two policies and create policy details separately.
the fifth step:
The CRM price list objects can be connected normally according to the requirements. Available sales range, currently does not support selecting customers and products by range, only supports docking by specific details. Therefore, the three ranges must be docked according to fixed values.
Customer: {"type":"FIXED","value":"FIXED"}, Organization: {"type":"ALL","value":"ALL"}, Product: {"type":"FIXED" ,"value":"FIXED"}.
Step 6: The remaining fields are connected according to the requirements.
2. Multi-specification Docking
To be added
3. Multi-unit Docking
1. Multi-unit docking involves two erp objects, as shown in the figure below. If these two preset objects are not found in the object management, contact R&D for initialization
2. If the material unit conversion does not have this field: CrmConvertNumber, please add it manually
3. Policy configuration of unit objects (crm unit docking erp unit of measurement)
4. Strategy configuration of multi-unit association table (crm multi-unit association table docking erp material unit conversion)
5. If some units already exist in crm, please import the existing unit mapping of crm in the data maintenance of the data unit
6. If there is no problem with the newly added test data, contact R&D to synchronize all historical units and unit conversion data
Note: If the erp unit has the same name, you need to contact the customer to modify it, or use a custom function to splicing some suffixes to the unit with the same name and synchronize it to crm.
Because the crm unit does not allow duplicate names
4. Docking of K3C's BOM & CRM's CPQ
4.1 Docking of K3C's BOM & CRM's CPQ (ERP -> ERP)
1. CPQ docking involves BOM objects. If there is no BOM object in the figure below, please contact R&D for initialization
You need to add 5 fields to the ERP BOM object by yourself: [Required], [Parent BOMid], [Product Code], [Quantity], [Root BOMid]
a.【Required】-- The field code is isRequired, and the field type is Boolean
b. 【Parent BOMid】-- the field code is parent_bom_id, the field type is lookup association, and the associated object is the bill of materials
c.【Product code】-- the field code is productId, the field type is lookup association, and the associated object is material
d. 【Quantity】-- The field code is quantity, and the field type is number
e. 【Root BOMid】-- the field code is root_id, the field type is lookup association, and the associated object is the bill of materials
2. Create a new product matching detail object strategy, and create a new strategy detail to connect the ERP [Bill of Materials] object with it, as shown in the figure below
The field mapping is as follows:
CRM [Product Selection Details] object [Enabled Status] field is set to a fixed value of "Yes"
The [Required] field of the CRM [Product Selection Details] object is mapped to the [Required] field in the ERP [Bill of Materials]
The mapping between the [Product Name] field of the CRM [Product Selection Details] object and the [Product Code] field in the ERP [Bill of Materials]
The mapping between the [Root BOMid] field of the CRM [Product Selection Details] object and the [Root BOMid] field in the ERP [Bill of Materials]
The [Quantity] field of the CRM [Product Selection Details] object is mapped to the [Quantity] field in the ERP [Bill of Materials]
The mapping between the [parent BOMid] field of the CRM [product selection details] object and the [parent BOMid] field in the ERP [material list]
The rest of the fields are connected by customers according to their needs
3. In ERP Data Synchronization -> Data Synchronization Settings -> ERP Object Management, the material object has a preset [kit] field, and the option settings are configured as shown in the figure below
4. In the product policy details, add the mapping between the [Product Portfolio] field of the CRM [Product] object and the [Kit] field in the ERP [Material]
Add the following field mapping
5. After the strategy is configured, add a bill of materials in K3C to check whether it can be correctly synchronized to CRM. The steps to add a BOM in K3C are as follows
(1) Add a new parent material, select "self-made" for the material attribute, and "yes" for the kit
(2) Create a new bill of materials, select the parent material and child material
6. After K3C synchronizes the BOM to CRM, the sales order in the direction of CRM->ERP needs to synchronize CPQ to K3C, the configuration is as follows
(1) Add the following fields in the ERP order detail object
a. Product combination virtual parent key, the field code is parent_prod_pkg_key, and the field type is text
b. Product combination virtual root key, the field code is root_prod_pkg_key, and the field type is text
c. Product combination virtual key, the field code is prod_pkg_key, and the field type is text
d. BOM id, the field code is FBOMEntryId, the view interface field code is BOMEntryId, the save interface field code is FBOMEntryId, the batch query interface field code is FBOMEntryId, the field type is search association, search association BOM
f. Parent product, the field code is FParentMatId.FNumber, the view interface field code is ParentMatId, the save interface field code is FParentMatId.FNumber, and the field type is text
(2) Add the field mapping of the red box to the order details
7. K3C does not synchronize the BOM to CRM, only the same as the parent material; CRM sales order-order product is the parent material, after synchronization to K3C, the package configuration needs to be automatically expanded as follows
(1) In ERP Data Synchronization -> Data Synchronization Settings -> ERP Object Management, the order detail object has a preset [Product Type] field, and the option settings are configured as shown in the figure below. The four option codes are Standard, Parent, Son, Service
(2) Add a [Product Type] field to the CRM [Order Product] object, the type is single choice, API Name is optional, the option settings are as follows, the four option codes are Standard, Parent, Son, Service
(3) In the sales order policy details, add the mapping between the [Product Type] field of the CRM [Order Product] object and the [Product Type] field in the ERP [Order Details]
Add new field mapping, as shown in the red boxed area in the figure below
(4) After the strategy is configured, add a sales order in CRM, select the parent material for the order product, and fill in the product type field of the order product object - refer to the figure below, and check whether the synchronization to ERP is correct after the creation is completed
(5) The K3C sales order package is automatically expanded, and the package management needs to be enabled. The operation is as shown in the figure below
4.2 Docking of CRM's CPQ & K3C's BOMa (CRM → ERP)
Background: When customers need to manage CPQ in CRM and synchronize to K3C's BOM, they can configure the CPQ connection of the integrated platform according to the current chapter. Starting from version 8.1 of FunShare, CRM provides a product selection instance (BomInstanceObj) that can be connected with k3c's bill of materials (BOM). Each product matching instance corresponds to a BOM version.
1. Connection between CRM product selection instance (BomInstanceObj) and K3C's bill of materials (BOM)
1. Open the product selection example
2. Preset BOM object
3. Create a crm→erp direction product matching instance (BomInstanceObj) integration flow
The CRM source system supports new events, but does not support edit and void events, and the ERP target system only supports new events.
Regarding the field mapping description of the product matching instance, please configure the organization and use code according to the actual situation; for other fields, please keep the field configuration consistent with the field configuration in this figure.
4. Dynamic generation of product matching instance (BomInstanceObj)
The product matching instance (BomInstanceObj) is dynamically generated when creating or editing an order product with CPQ on the CRM side. For synchronizing a parent product, if the number of sub-products changes, CRM will dynamically generate a product selection instance (BomInstanceObj). Also, if the configuration quantity and price of the sub-products of the parent product change, CRM will also dynamically generate a product selection instance Configuration instance (BomInstanceObj)
The product matching instance object is a preset object and is hidden, so we cannot see it directly. You can check it by the following method.
5. K3C bill of materials (BOM) parent material and child material description
5.1 The attribute of the parent material must be a kit, as shown in the figure:
5.2 The attributes of sub-materials cannot be virtual, as shown in the figure:
2. Sales order synchronization (crm→erp)
1. Sales orders support CPQ synchronization switch configuration (find R&D configuration)
2. Preset sales order object
3. Configure sales order object fields
The sales order detail object needs to add the following fields, namely prod_pkg_key, parent_prod_pkg_key, bom_instance_tree_id, bom_id
prod_pkg_key field detailed configuration
Detailed configuration of the parent_prod_pkg_key field
Detailed configuration of the bom_instance_tree_id field
Detailed configuration of the bom_id field
4. Sales order integration flow configuration
Order product field configuration, the fields in the red box must be configured
5. Sales order and product matching instance (BomInstanceObj) synchronization sequence logic
When creating or editing an order product with CPQ, first create a product matching instance, and then create or update the order. The integration platform will first trigger the synchronization of the product selection instance, and then trigger the synchronization of the order.
5. SAP's CPQ Docking
To be added
6. Order Change Docking
Step 1: Enable new order change order in K3C
Step 2: Add a [Reason for Change] field in the CRM sales order object, and the field type is text
Step 3: In the sales order policy details, add the change reason field mapping
Add the following field mapping
Note: When CRM modifies an order, the change reason field must be filled in to synchronize K3C
7. Multi-account/Multiple Data Center Docking
To be added
8. Country, Province, City & District Docking
There are two docking methods for the connection of K3C countries, provinces and municipalities. One is to associate the countries, provinces and municipalities on the side of Funshare with the K3C countries, provinces and municipalities in the system field management. The other way is to connect through auxiliary data.
1. The first way is to associate in the system field management
Step 1: Find national, provincial, urban data in K3C and CRM
The country, province, city, and district of K3C can be found in the list of auxiliary materials, as shown in the figure below
You can export the data of the country, province, city and city in the option operation, as shown in the figure below, click on the option to export
For CRM country, province, city, and district data, see the attachment [country, province, city, and district], or Get the latest data in real time (the browser needs to log in to CRM and the account has CRM permissions):
Step 2: In ERP Data Synchronization -> Data Synchronization Settings -> System Field Management, associate the country, province, city and city on the side of FunShare with the country, province, city, and city of K3C
Step 3: Map the country, province, city, and district fields in the synchronization strategy. Note that the field type must be country, province, city, and district, such as the country field mapping in the figure below.
2. The second way is to connect with auxiliary materials
The first step is to check whether the preset object has auxiliary information in ERP data synchronization -> data synchronization settings -> ERP object management, if not, find R & D to add
The second step is to create a new custom object-auxiliary data in CRM, and set the fields as follows, and search for the associated auxiliary data in the upper-level data field
The third step is to establish an auxiliary data synchronization strategy, and the field mapping is as follows
Step 4 After synchronizing the auxiliary data of K3C countries, provinces, and municipalities to CRM, create a new search associated auxiliary data field in CRM and map it
9. Attachment Field Docking
To connect the attachment field, you need to create a new attachment field in the ERP object first, and then map it with the CRM attachment field; the attachment field connection from CRM to ERP, and from ERP to CRM are both supported. It should be noted that Kingdee K3C attachment field can only upload one attachment , so if there are multiple CRM attachments, only the first one will be synchronized to Kingdee K3C
The following takes the connection of the attachment field of the account object as an example to explain
1. Create a new attachment field in the ERP account object, the field name is arbitrary, and the field type selects attachment. Field code, view interface field code, save interface field code fill in reference [3.4.3.1.2.1 New field]
2. Just map the attachment field in the field mapping of the synchronization policy
For other object attachment fields, please refer to this step
10. Batch Docking
The object in K3 Cloud is the main file of the batch number (BD_BatchMainFile, if the preset object is not available, please contact R&D to add it), which needs to be connected to the batch object of CRM
Step 1: Establish a batch object synchronization strategy
Step 2: Configure the field mapping of the batch object synchronization strategy, and connect according to the requirements
Step 3: Add three fields in the material object, 【Enable Batch Number Management】-- the field code is MaterialStock[0].IsBatchManage, check the interface field code is MaterialStock[0].IsBatchManage, and the field type is a Boolean value; 【whether Enable batch serial number management (virtual)]-- field code is VirtualHasBatchAndSerial, field type is single choice, option setting: 1 corresponds to disable; 2 corresponds to enable batch management, 3 corresponds to enable serial number management; [enable serial number management 】--The field code is MaterialStock[0].IsSNManage, the view interface field code is MaterialStock[0].IsSNManage, and the field type is Boolean
the fourth step:
Configure whether to enable batch serial number management field mapping in the product object synchronization policy. Field mapping for click product object
Add the field mapping in the figure below
11. K3C Serial Number Docking
Step 1: In the ERP object management, add the serial number related fields in the serial number master file, material object, and sales delivery order object (if there is no preset object in the serial number master file, please contact R&D to add it)
1. Serial number master file (if not available, please contact R&D to add)
2. Add three fields to the material object
a. [Enable Batch Number Management]: The field code is MaterialStock[0].IsBatchManage, the field code of the view interface is MaterialStock[0].IsBatchManage, and the field type is Boolean;
b. [Whether to enable batch serial number management (virtual)]: The field code is VirtualHasBatchAndSerial, the field type is single choice, option settings: 1 corresponds to not enable; 2 corresponds to enable batch management, 3 corresponds to enable serial number management;
c.【Enable serial number management】--The field code is MaterialStock[0].IsSNManage, the field code of the view interface is MaterialStock[0].IsSNManage, and the field type is Boolean;
3. Add four fields to the sales delivery form
a. [Serial number (encoding)]: The field encoding is crmSerialNo, and the field type is text
b. [Serial number note]: The field code is crmSerialNote, and the field type is text
c. [Serial number (id)]: The field code is serialId, the field type is search association, and the referenced object is the serial number master file
d. [Outbound serial number]: the field code is SAL_OutStockSerial, and the field type is text
Step 2: Establish the synchronization policy of the serial number master file object and complete the field mapping
Step 3: Add the "whether to enable batch serial number management" mapping field to the product object synchronization strategy
Add the field mapping in the figure below
Step 4: Add three mapping fields [serial number (number)], [serial number note], and [serial number (id)] to the detailed field mapping of invoice synchronization policy
Note: If the invoice is a custom object, there is no need to map the [serial number (id)] field.
Add the field mapping in the figure below to the invoice details
Note: After the synchronization is successful, the product details of each line of the K3C delivery order will be split into multiple delivery order product details with a quantity of 1 (the number of items is consistent with the delivery quantity of the product in the K3C delivery order). Without splitting (find R&D settings), multiple serial numbers will be concatenated and then sent together to the CRM serial number field.
12. Data docking cannot be queried according to time
To be added
13. The invoice is automatically associated with the inventory
first step:
Add a new field [No Stock ID Integration Platform Synchronization Flag] in the CRM invoice object, the field type is Boolean, and the API Name is set to field_no_stock_id_integration_flag__c
Step 2: Add [No Inventory ID Integration Platform Synchronization Identification] field mapping in the invoice synchronization strategy, and set it to the fixed value "Yes", as shown in the figure below
14. One object of ERP needs to dock with main-sub two objects of CRM
An ERP object is connected to two CRM master-slave objects. When creating a new ERP object, you need to select the split type of the ERP object as "ERP object is split into an intermediate object of master-slave relationship", and then connect with the CRM master-slave object.
Let's take ERP [sales order] as an example to explain.
1. First, you need to create a new object, enter ERP Data Synchronization -> Data Synchronization Settings -> ERP Object Management to add new objects, select the split type "ERP object split into intermediate objects of master-slave relationship", fill in the ERP object code and detail code Please refer to 【3.4.3.1.1 New Objects】
2. After creating the object, add the ERP master-slave object field according to the requirement. For the operation, please refer to [3.4.3.1.2.1 Adding a new field]
3. Then create a new synchronization strategy, map the split ERP master object with the CRM master object, and map the split ERP slave object with the CRM slave object, as shown in the figure below
The rest of the docking can refer to the above example configuration
15. One object of CRM connects to two objects of ERP
One CRM object connects two ERP objects, first establish the synchronization strategy of the CRM object, and then add the strategy details for docking with the two ERP objects.
The following takes the CRM [Billing Application] object as an example to explain. Assuming that the CRM [Invoicing Application] object needs to connect with ERP [VAT Sales Invoice] and [Sales Ordinary Invoice]
First create a new CRM [Invoicing Application] object synchronization strategy, and then add the strategy details for docking with ERP [VAT Sales Invoice] and [Sales General Invoice], as shown in the figure below
For the rest of the requirements, you can refer to this example for docking
16. The data under one object of ERP is connected to two independent objects of CRM according to conditions
An ERP object is connected to two independent objects of CRM according to conditions. The policy details of the two independent objects of ERP object and CRM must be created first, and data range conditions can be set in the policy details to filter data according to the conditions.
The following takes the ERP outbound order as an example to explain. Assuming that the ERP delivery order needs to be connected to the CRM preset object [delivery document] and the custom object [sales delivery document], when the field value of the ERP delivery document [sales organization] is equal to "Funxiang sales customer", it will be synchronized to The CRM preset object [Delivery Document]; when the field value of the ERP Outbound Document [Sales Organization] is not equal to "Funxiang Sales Customer", it will be synchronized to the CRM custom object [Sales Outbound Document], and it can be realized by following the steps below The function:
1. Firstly, establish the strategy details for docking CRM [delivery note] with ERP delivery order and the strategy details for connecting CRM [sales delivery order] with ERP delivery order
2. According to the conditions, when the field value of the ERP delivery order [Sales Organization] is equal to "Funxiang Sales", it will be synchronized to the CRM preset object [Delivery Document]; when the field value of the ERP delivery form [Sales Organization] is not equal to " "Funxiang Sales" is synchronized to the CRM custom object [Sales Outbound Document], and the data range conditions for setting the policies are as follows
Synchronization strategy for docking CRM [delivery note] with ERP delivery note, the data range is set as follows
Synchronization strategy for docking CRM [Sales Outbound Doc] with ERP Outbound Doc, the data range is set as follows
For other conditions, refer to the example configuration
17. After the CRM data is synchronized to the ERP, the ERP changes the data and writes it back to the CRM
To complete this connection, it is necessary to establish a synchronization strategy for connecting the same CRM object and the same ERP object in both synchronization directions, and in the synchronization rules of the CRM to ERP direction strategy, only check the new Added, in the synchronization rule of the ERP to CRM direction strategy, only check and modify the synchronization event monitoring and synchronization event writing
Let’s take the sales order as an example, assuming that the sales order data is synchronized from CRM to ERP, and written back to CRM after ERP changes the data
1. Establish sales order synchronization strategies in both synchronization directions as follows
2. In the synchronization rules of the CRM synchronization to ERP direction synchronization strategy, only check Add for synchronization event monitoring and synchronization event writing;
3. In the synchronization rules of the synchronization strategy of ERP synchronization to CRM direction, only check and modify the synchronization event monitoring and synchronization event writing;
The rest of the docking can refer to the above example configuration
18. After ERP price adjustment, quickly synchronize to CRM products
To be added