3. Docking Configuration Description by CRM Object

1. First configure the ERP organization object in the CRM menu:

Go to Management > CRM Platform Management > Interface Customization Management > CRM Homepage Customization > Menu Module Management and select the application menu name on the right side as CRM, click Edit to enter the next step. On the setting menu item page, search for "ERP organization" and set it to visible (if If there is no such option, please add it by adding a custom menu), save and exit;

2. Log in to Yunxingkong with the Admin account and export the organization structure.

3. Go to CRM>ERP organization, and manually create new organization data on CRM, as shown in the figure below:

4. After adding the data on CRM, add the synchronization strategy and mapping relationship:

Go to Management > System Management > System Docking Management > ERP Data Synchronization > Synchronization Policy Select the ERP organization under the synchronization direction (ERP synchronization to CRM), add a policy on the right and enter the field mapping (set the business type and person in charge to insert a fixed value , see the figure below for other field configurations):

5. Go to Management > System Management > System Docking Management > ERP Data Synchronization > Data Maintenance ERP Synchronization to CRM direction, select the ERP organization object, enter the data maintenance page on the right, click the import button, download the import template, and fill in the corresponding relationship , import the system to suggest the association relationship;

Whether to synchronize accounts: When CRM synchronizes customers with K3C, it regards this organization as the creation organization.

Whether to synchronize materials: When K3C synchronizes products to CRM, the organization code will be used as the material use organization on K3C for conditional filtering.

Whether to synchronize warehouses: When K3C synchronizes products to CRM, it will use the organization code as the warehouse user organization on K3C for conditional filtering.

When the CRM order object is synchronized to the ERP, the setting method is the same.

To judge whether the content to be connected is auxiliary information of k3c, you can refer to Chapter 8, section 1.8.

Docking scheme: K3C auxiliary data data is connected to auxiliary data objects on CRM, and other objects on CRM search for associated auxiliary data.

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, please contact 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 configured as shown in the figure below

Set field mapping

Configure the field mapping and enable the synchronization strategy.

Taking the customer object as an example, configure the mapping of the country, and the configuration method of other objects is the same.

Change the field type to search association. If the preset type is not search association, just change it directly.

Set the field mapping relationship of the "country" field of the customer object

Finally, enable the synchronization strategy, and contact R&D to refresh historical data.

To determine whether the content to be connected is an auxiliary attribute of k3c, you can log in to the customer's K3C system and search for "auxiliary attribute list" to see if the field to be connected is in it.

Docking Scheme: The auxiliary attribute of K3C is several fields. Connect to CRM and choose different solutions according to the situation:

**The source of value is the basic data: the auxiliary attribute field is configured to find the associated field, and find the associated basic data object. **If the basic data object cannot be found in the ERP object management, contact the R&D preset.

**Value Source is Secondary: Secondary property field configured as Lookup Associated Field, Lookup Associated Secondary Object. ** For the docking of auxiliary data objects, please refer to Chapter 2.1.

Value source is manual entry: Auxiliary attribute fields are configured as text fields.

To put it simply, auxiliary attributes are a collection of attributes dynamically added to materials based on the basic attributes of existing materials. Material attributes = basic attributes + auxiliary attributes. We have established auxiliary attributes in k3cloud, which needs to be manually edited when editing materials. Check the auxiliary attributes that need to be enabled. After the auxiliary attributes are enabled, if there is an inventory record, the auxiliary attributes of the material can no longer be modified, and vice versa. Note: The docking of auxiliary attribute inventory objects currently only supports the docking of custom inventory objects

The value of the auxiliary attribute comes from the basic data object. When connecting, it also needs to connect to the corresponding basic data object. For example, if the value of the auxiliary attribute comes from the bank object, then it needs to connect to the bank object

Basic Data Object Finding Method

ID Field Configuration of Basic Data Object Bank

The docking method of the basic object is the same as that of the common object

The value of the auxiliary data comes from the auxiliary data object. When docking, the auxiliary data object also needs to be connected. It should be noted here that the id field of the auxiliary data must be configured as shown in the figure below.

Auxiliary Data ID Field Configuration

The value of auxiliary data comes from the data manually entered by the user. When docking, this type of auxiliary attribute can be docked as a common attribute field, and no special processing is required.

Example Diagram of k3cloud Auxiliary Attributes:

Auxiliary Attribute List

Materials with Auxiliary Attributes Enabled

When creating a new order, please select materials with auxiliary attributes

The value of the auxiliary attribute can be selected from the classification of the auxiliary data, that is, if the value of the auxiliary data comes from the auxiliary data

As long as materials with auxiliary attributes are used, auxiliary attributes are supported. Such as orders, storage orders, storage orders, inventory, invoicing, payment collection, etc.

Auxiliary attribute lookup associated field configuration

Auxiliary Attribute Code Field Configuration

Auxiliary Attribute Value Field Configuration

crm accounts, account address, account financial information -> k3 accounts, account address, bank information

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, contact the development to initialize the object, as shown in the figure:

Step 2: In the direction of Synchronization Policy - Synchronize CRM to ERP, click [Add Object] to add the synchronization policy of the customer object, as shown in the figure below

Step 3: In the synchronization policy of the customer object, click Add Policy on the upper right side, add policy details, and select the mapped object, as shown in the figure below

The fourth step is to configure the field mapping. Click the field mapping of the customer object synchronization policy details to configure it. The field mapping configuration can refer to the figure below. Some fields of the CRM customer, customer financial information, and customer address objects in the figure below need to be created in CRM by themselves. It should be noted that the [Create Organization] field of the customer object is the search association type, and the search is associated with the [ERP Organization] object.

The fifth step is to configure the synchronization rules. Select events that can trigger synchronization according to customer needs, and decide whether to configure custom functions according to customer needs

crm contacts -> k3 contacts

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, contact the development to initialize the object, as shown in the figure:

In the second step, in the direction of Synchronization Policy - Synchronization of CRM to ERP, click [Add Object] to add the synchronization policy of the contact object, as shown in the figure below

Step 3: In the synchronization policy of the contact object, click Add Policy on the upper right, add policy details, and select the mapped object

The fourth step is to configure the field mapping. Click the field mapping of the contact object synchronization policy details to configure it. The fields in the figure below are mapped as mandatory fields, and the remaining fields are added according to customer needs

The [Type] field of the ERP contact object is set to the fixed value BD_Customer

The CRM contact object [customer name] is mapped with the ERP contact object [company] field. The field of the ERP contact object [company] is preset, but you need to select the field coded as FCompany.FNumber

The above two fields need to be configured correctly in order to associate ERP contacts with customers

The fifth step is to configure the synchronization rules, check the events that need to trigger synchronization according to customer needs, and at the same time, the custom function also decides whether to configure according to customer needs

Product objects are the basis of docking. When docking product objects, you must be cautious. After the product objects are docked, the subsequent docking work of objects that rely on product objects will be much smoother.

The batch and serial number management field in the CRM product object is used by the server to mark whether the current product has a batch or serial number enabled, and returns the corresponding identification value according to the situation, 0 for ordinary products, and 2 for batch enabled Management, 3 is to enable the serial number management, this field does not need to be docked, this document is only for reference of technical students, please ignore it for implementation students

If the batch number management of the material is selected, then this product needs to be docked with CRM batches. To connect with CRM batches, you first need to turn on the CRM batch and serial number management switch, and then you can dock batches

In k3cloud, you can also not enable batches, but only enable shelf life management. If shelf life management is enabled, you only need to connect the shelf life, and you don’t need to connect batches. When k3cloud puts in the materials with shelf life enabled, you need to fill in the field information related to the shelf life. After warehousing, you can also query the fields related to the shelf life in the inventory, such as production date, expiration date, etc.

If inventory management is enabled for the material in the serial number management module, then this product needs to be docked with the serial number of CRM. To connect with the serial number of CRM, you first need to turn on the batch and serial number management switch of CRM, and then you can dock the serial number

If CRM has enabled multi-units and ERP has also enabled multi-units, then, in the process of docking, multi-unit docking can be considered, because objects such as orders, warehousing documents, delivery orders, etc. will depend on multiple units, the following is multi-unit The core operation of unit docking

Core Docking Object

Core Docking Field Mapping Configuration

Note: Currently, the docking platform does not support k3cloud multi-standard docking, only supports SAF multi-standard docking

The docking of product classification is to connect the material grouping of ERP with CRM and product classification. Since this piece of docking is quite special, it is explained separately.

The first step is to manage the fields of the docking platform system and import product categories, which can be imported automatically or in batches as mentioned above.

The second step is to add a product classification field to the product object, as shown in the figure

The third step is to configure the product classification field mapping in the synchronization policy details, as shown in the figure

The fourth step is to enable the synchronization strategy, and then the product and product classification can be synchronized normally

1.k3cloud supports bill of material objects (that is, BOM objects)
2. CRM has opened CPQ, which is the detailed object of product matching

1. CRM's CPQ supports nesting, that is, supports CPQ hierarchical tree structure
2. The bill of materials of k3cloud supports standard BOM and configuration BOM. Currently, we only support docking with standard BOM
3. The bill of materials of k3cloud has an overview of the BOM version, and the CPQ of CRM has no similar concept. Therefore, when we are docking, we will synchronize the BOM version number of k3cloud to the product name of CRM to distinguish out-of-sync CPQ products in BOM version

The first step is to create a new ERP BOM object, as shown in the figure

The second step is to add CPQ objects and policy details to the synchronization policy, and configure CPQ field mapping, as shown in the figure

The third step is to enable the synchronization strategy, and then the data can be synchronized

First complete the basic configuration of the ERP sales order object

Configure document type (encoding)

Configure settlement currency

Configure sales organization

Configure the sales unit of the order detail object

Refer to the figure below for field configuration

When crm->k3c creates an order, it will automatically assign customers and materials

k3Cloud's payment receipt object connects to crm's payment return object (it can also be connected to a custom object as needed)

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, submit a work order to initialize the object

The second step is to add the synchronization policy of payment return in the synchronization policy

Step 3: Select the repayment policy, click the button on the upper right to add policy details, and select the object to be mapped

The fourth step is to click Field Mapping to map each field that needs to be mapped. The most basic mapping is as follows:

The fifth step, click on the synchronization rule, and set according to the requirements: select polling, add/update according to customer needs, select synchronization time according to customer needs, whether functions are needed or not depends on the situation, and introduce custom functions.

There are not too many special places in the docking of payment collection. It is mainly necessary to pay attention to the mapping of several search-related fields: related customers, related orders

Receipt and refund form of k3Cloud -> refund object of crm (can also be connected to a custom object as needed)

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, submit a work order to initialize the object, as shown in the figure:

The second step is to add the synchronization policy of refund in the synchronization policy

The third step is to select the refund policy, click the button on the upper right to add policy details, and select the object to be mapped

The fourth step is to click Field Mapping to map each field that needs to be mapped. The most basic mapping is as follows:

According to business requirements, filter corresponding data that does not need to be synchronized, and only data that meets the configured data range will be synchronized

Note lookup related fields mapping lookup related fields

There are not many special places in the docking of refunds. The main thing to pay attention to is the mapping of several search-associated fields: associating customers

Note the associated order field

Associated order (select the SalesOrderComId field of the k3 object to map with the crm search associated order field), if the field SalesOrderComId does not exist, add it manually as shown in the figure below

k3 general sales invoice (main), general sales invoice details -> crm billing application (main), billing application details (can also be connected to custom objects as needed) VAT sales invoice (main), VAT sales invoice details -> crm invoicing application (main), invoicing application details (can also be connected to custom objects as needed)

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, submit a work order to initialize the object

The second step is to add the synchronization policy of billing in the synchronization policy

The third step is to select the billing policy, click the button on the upper right to add policy details, and select the mapped object

The fourth step is to click Field Mapping to map each field that needs to be mapped. The most basic mapping is as follows:

According to business requirements, filter corresponding data that does not need to be synchronized, and only data that meets the configured data range will be synchronized

Note lookup related fields mapping lookup related fields

There are not many special places in the docking of invoices. The main thing to pay attention to is the mapping of several search-associated fields: associating customers

Pay attention to the order field associated with the detail object

Associated order (select the SalesOrderComId field of the k3 invoice detail object to map with the field of the crm detail search associated order), if the field SalesOrderComId does not exist, add it manually as shown in the figure below

Before configuring, check whether there is a sales price list and sales control in the ERP object, if not, please add it yourself.

There are two plans for price list docking, please choose the corresponding plan according to the actual situation.

Option 1:

Option 2:

K3C Sales Price List-------->CRM Price List

K3C Sellable Control ----------->CRM Sellable Scope

It should be noted that there is only one customer in the sales scope of CRM, and synchronization is performed according to the customer dimension. A price list, including multiple ranges available for sale.

Option 1:

The object in K3 Cloud is the sales price list (BD_SAL_PriceList), which needs to be connected to the two objects price list (PriceBookObj) and sales range (AvailableRangeObj) in CRM.

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 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.

Option Two:

first step:

First enter the object configuration that can be controlled by K3 Cloud.

Step two:

Add three slave objects, the object codes are

Customer: SAL_SC_CustMat.AvailableAccountObj

Product: SAL_SC_CustMat.AvailableProductObj

Price list: SAL_SC_CustMat.AvailablePriceBookObj

third step:

After configuring the object, enter the field configuration.

The field configuration is as shown below

the fourth step:

Create two policies and create policy details separately.

the fifth step:

Customer: {"type":"FIXED","value":"FIXED"}, Organization: {"type":"ALL","value":"ALL"}, Product: {"type":"FIXED" ,"value":"FIXED"}.

Field reference configuration:

The K3C sales outbound order is connected to the CRM invoice. For Class B inventory, the invoice will automatically complete the associated inventory ID

1. Add the [No Stock ID Integration Platform Synchronization Flag] field to the CRM invoice object, the field type is Boolean, and the field API Name is field_no_stock_id_integration_flag__c

2. Add the field mapping in the field mapping and set it to a fixed value [Yes]

1. The docking scheme of the serial number of the delivery order:

1.1 Connect the serial number to CRM as a long text, and add 4 fields in the ERP delivery order detail object

Note: When there are many serial numbers, it may exceed the maximum length of CRM long text.

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

1.2 Connect each serial number to CRM as a separate slave data

1.3 Put the serial number in Excel and connect to CRM through docking accessories

2. Add two text fields in the product object of the CRM invoice - ERP serial number, ERP serial number remarks, the field Api Name is not required

3. Add the following fields in the detailed object field mapping

1. In the detailed object of the ERP delivery order, add a field [Lot Number], the field code is [FLot], the field code of the view interface is [Lot.Id], and the field code of the save interface is [FLot]; the field type is search association , associated with the batch number master file object

2. Add the following fields in the detailed object field mapping

1. In Invoicing Management - Plug-in Management, enable multi-order delivery

2. After selecting multiple orders in K3C (note that they must be orders from the same customer), click Push Down, and select Push Sales Outbound Order.

1. First confirm which organization's warehouses ERP needs to synchronize. .

2. If only one organization's warehouse is synchronized, it is necessary to ensure that the organization id of the ERP organization object in CRM is correct. You can refer to [Import K3C organization structure] (4.26.1 Import K3C organization structure first)

3. If you need to synchronize the warehouses of multiple organizations, you need to ensure that the warehouse codes of different organizations in K3Cloud are unique. Historical data can directly modify the encoding. You can modify the coding rules and add organization codes to ensure that there are no duplicate codes in the new warehouse.

4. In the ERP organization object, select [Yes] for the [Whether to synchronize the warehouse] option of the organization that needs to synchronize the warehouse, and select [No] for others

5. For a warehouse with a position, it needs to be synchronized according to the rules of the position. (Note: Even if you don't need to synchronize the position, if you synchronize the inventory, you need to synchronize the position)

If the K3Cloud warehouse has not opened a position, you can import the intermediate table on the [Data Maintenance] page after importing the CRM data. It should be noted that, for the K3Cloud channel, the ERP primary key id of the warehouse uses the warehouse code field by default.

Field Name	Field Code	View Interface Code	Save Interface Code	Description
Parent Warehouse Code	parentWarehouseNumber			Find associated warehouses for position docking
Warehouse Position

Class B inventory, the original inventory and batch inventory objects, do not need to be docked. After the data enters the inventory detail object, the data of inventory and batch inventory will be automatically generated.

In Yunxingkong, the object on the page is called instant inventory details, and the object in webapi is called instant inventory. Note that the "instant inventory" data on the page cannot be returned through the webapi interface.

Since only the inventory (basic unit) [FBaseQty] is accurate for the data stored in K3Cloud [Instant Inventory], it only supports accurate docking of this quantity for the time being. Accurate values for fields such as inventory (main unit), availability, etc. are under development.
If there are batch-enabled materials in K3Cloud that need to be synchronized, batch docking must be enabled and batch field mapping must be added to the inventory details.

The first step is in the purchase, sale and inventory management - plug-in management, set the synchronization mechanism of the docking plug-in to "synchronize inventory details", and then the CRM will have inventory detail objects

Step 2 In Data Synchronization Settings -> ERP Object Management, check whether the primary key field of the ERP instant inventory object is FID, and if not, set the primary key to this field.

The details of the primary key field are as follows, field coding, viewing interface field coding, and saving interface field coding are all set to FID

The third step is to add the synchronization strategy of the CRM [Inventory Details] object

The fourth step is to configure the field mapping, the basic field configuration is as follows

CRM inventory needs to be opened for batch and serialization management.
The product requires docking field [whether to enable batch serial number management (virtual)], refer to [product] docking instructions.

Note that the intermediate object id field preset by K3Cloud in the batch is K3Cloud's internal code Id field, and the value of this field needs to be imported as the ERP data id.

After K3C real-time inventory is connected to the inventory detail object of CRM, there is no need to connect to the batch inventory object.

CRM does not support opening batch and serial number for the same product.
The product requires docking field [whether to enable batch serial number management (virtual)], refer to [product] docking instructions.
There are two docking schemes for the serial number - related to the inventory docking scheme, the field mapping of different schemes is different, see the field mapping description for details

1. If K3C [Instant Inventory] adopts the scheme of docking to the CRM [Inventory] object, the serial number docking field mapping is as follows

It is necessary to add the [warehouse material mixed code] field in the ERP serial number master file object, the field code is StockMultiCode, the field type is search association, and the instant inventory is associated

2. If K3C [Instant Inventory] adopts the scheme of docking to the CRM [Inventory Details] object, the serial number docking field mapping is as follows

It is necessary to add [virtual inventory], [warehouse compound ID] and [position (ID)] fields in the ERP serial number master file object

a. [Virtual stock] field, the field code is virtual_stock_id, the field type is lookup association, lookup associated inventory

b. Warehouse composite ID (warehouse number || warehouse 1 number. warehouse 2 number...) field, the field code is warehouseComId, the field type is search association, find the associated warehouse

c. Position (ID) field, the field code is FSubHeadEntity.FStockLocId.Id, the view interface field code is BD_SERIALMASTEROTHER[0].StockLocId.Id, and the field type is text

k3 sales return order (main), return order details -> crm return order (main), return order products (can also be connected to custom objects as needed) You can consult the relevant implementation personnel of [Shenzhen Schroeder Industrial Group Co., Ltd.], this company has configured k3Cloud's return docking crm return object

The first step is to confirm that the ERP object already exists in the erp object management. If it does not exist, contact the development to initialize the object, as shown in the figure:

The second step is to add a synchronization strategy for returns in the synchronization strategy, as shown in the figure:

The third step is to select the return policy, click the upper right button to add policy details, and select the mapped object, as shown in the figure:

The fourth step is to click Field Mapping to map each field that needs to be mapped. The most basic mapping is as follows:

Step 5: Click Synchronization Rules, set according to requirements: select polling, add/update according to customer needs, select synchronization time according to customer needs, whether functions are needed or not depends on the situation, and the introduction of custom functions is in Section 4.21. The rules are as shown in the figure:

According to business requirements, filter corresponding data that does not need to be synchronized, and only data that meets the configured data range will be synchronized

Note lookup related fields mapping lookup related fields

There are not many special places in the docking of invoices. The main thing to pay attention to is the mapping of several search-associated fields: associating customers

Pay attention to the order field associated with the detail object

Create ERP objects and fields, and then call external interfaces for format conversion by writing custom functions

2023-02-22

3. Docking Configuration Description by CRM Object

1. K3C Multi-organization

1.1 Import K3C Organization Structure Firstly

1.2 Specify Organization of Accounts, Materials & Warehouses to be Synchronized

1.3 Synchronize CRM Accounts to ERP & Specify K3C Organization

2. K3C Auxiliary Data & Attributes

2.1 K3C Auxiliary Data Docking

2.2 K3C Auxiliary Attribute Docking

2.2.1 Concept of Auxiliary Attribute

2.2.2 Auxiliary Attribute Types & Value Sources

2.3 Auxiliary Attribute Field Configuration Description

2.3.1 Basic Data

2.3.2 Auxiliary Information

2.3.3 Manual Input (The value of auxiliary data comes from the data manually input by the user)

2.3.4 Relationship between Auxiliary Attributes & Auxiliary Data

2.3.5 Which objects support auxiliary attributes

2.3.6 Configuration of Auxiliary Attribute Fields

2.3.7 Auxiliary Field Docking

3. Accounts & Contacts

3.1 Accounts

3.2 Contacts

4. K3C Products

4.1 Product Docking (Required)

4.1.1 Product Docking Field Mapping Reference

CRM Batch & Serial Number Management Field Description

4.1.2 Batch Docking Reference

4.1.3 EXP Management Docking

4.1.4 Serial Number Docking

4.1.5 Multi-unit Docking

4.1.6 Interconnection of Multiple Specifications

4.2 Product Category Docking

4.2.1 Docking Steps

4.3 CPQ Docking (optional, if CRM has enabled CPQ and ERP has enabled BOM, you can consider docking)

4.3.1 Prerequisites for CPQ docking

4.3.2 Precautions for CPQ docking

4.3.3 k3cloud bill of materials and CRM product CPQ sample diagram

4.3.4 CPQ Docking Steps

5. K3C Order

5.1 Configuration Steps

5.2 Docking Notes

6. K3C Payment

6.1 Docking Steps

6.2 Docking Notes

7. K3C Refund

7.1 Docking Steps

7.2 Data Range

7.3 Docking Notes

8. K3C Invoice

8.1 Docking Steps

8.2 Data Range

8.3 Docking Notes

9. K3C Salable Range + Price List

9.1 Preparations before Docking

9.2 Detailed Configuration

10. K3C Invoice

10.1 Field Mapping Reference

10.2 Invoice automatically associated with inventory

10.3 Enable Serial Number Material Delivery

10.4 Enable Batch Material Delivery

10.5 Multiple Orders Delivery

11. K3C Warehouse

11.1 K3Cloud Channel Notes

11.2 Field Mapping Reference

11.3 ERP Data Import Description

11.4 K3Cloud Special Preset Fields

12. K3C Class B Inventory Docking Logic Diagram

13. K3C Real-time Inventory Kocking CRM Inventory Details

13.1 Precautions

14. K3C batch

14.1 Precautions

14.2 Field Mapping Reference

14.3 Data Import Description

15. K3C Batch Inventory

16. K3C Serial Number

16.1 Precautions

16.2 Field Mapping Reference

17. K3C Return Form

17.1 Docking Steps

17.2 Data Range

17.3 Docking Notes