Published at: 2026-09-17
Equipment asset reference
Overview
This reference set lists the objects, automation triggers, quantity rules, and irreversible limits for equipment asset management. Specific field visibility, buttons, and record types are still affected by enterprise permissions and configuration.
Objects and fields
| Name | API Name | Purpose or Rules |
|---|---|---|
| Equipment | DeviceObj |
Equipment asset master file; default associated product and associated serial number fields |
| Equipment asset BOM | DeviceComponentsObj |
Record the hierarchical relationship of root equipment, parent equipment, child equipment or child products |
| Equipment asset history | DeviceLifeCycleObj |
Record equipment life cycle events and automatically initialize when device capabilities are enabled |
| QR code/barcode encoding | device_code |
The basis for equipment code generation and code scanning identification; the default value is the serial number, and the field name in historical enterprises may be “equipment serial number” |
Enable entry and results
| Enterprise purchasing method | Activation portal | Activation results |
|---|---|---|
| Purchased ShareService Professional Edition | ShareService > System Settings > Configuration Overview > Equipment Management | Add basic objects such as equipment, equipment asset BOM, and equipment asset history |
| Purchase equipment asset management separately | CRM Management > Business Rule Management > Asset Management | Initialize the same basic object and add the asset management menu in CRM |
Basic setting rules
| Setting | Trigger or effect | Limitation |
|---|---|---|
| Automatically generate equipment assets | After the invoice process ends and the shipment status is updated to received, the equipment is generated according to the configured customer record type | Dependent on customer fields and record type mapping |
| The work order supports multiple devices | The new work order device slave object in the work order can be associated with multiple devices at one time | The page prompts that the opening action is irreversible |
| Work order updates device location | Engineers can update device address when executing equipment-related work orders | Corresponding field permissions are required |
| Equipment asset BOM | Initialize DeviceComponentsObj, configurable equipment component level |
Cannot be closed after opening; can only be maintained from device details |
| Asset tracking management | Add new self-owned asset record types and objects for borrowing, extension, return, and transfer | It cannot be closed after being opened; the customers and addresses of self-owned assets can only be changed through transfer |
Ledger default values and conditions
| Project | Rules |
|---|---|
| Related products | Required |
| Device name | After selecting a product, the product name is used by default; modification is allowed |
| Associated serial number | Can be filled in after enabling serial number management for associated products |
| Device coding | After filling in the serial number, the serial number will be used by default; modification is allowed |
| File creation method | Manual creation, import, external system integration, or automatically generated by the delivery process after meeting configuration conditions |
OBOM level and quantity rules
| Current node or new content | Rules |
|---|---|
| Root node | Must reference equipment; a product cannot be the root node |
| Equipment node | You can add lower-level equipment or lower-level products |
| Product node | Only lower-level products can be added, lower-level devices cannot be added |
| Subordinate equipment | The number of parts is fixed at 1; the serial number is automatically brought in when serial number management is enabled |
| Subordinate products | You can enter the quantity when serial number management is not enabled; after it is enabled, the quantity is fixed at 1 |
| Maintenance portal | Only supports Configuration OBOM of device details, and does not support directly creating or importing the BOM object |
Asset tracking rules
| Business | Prerequisites or required items | Automatic updates after configuring the approval flow |
|---|---|---|
| Borrowing | The equipment is own assets and the management status is available for borrowing; fill in the applicant, phone number, date and purpose | The upstream data does not clearly define the unified post-approval fields, check according to the enterprise process |
| Extension | Associate the original borrowing details; fill in the reason for the extension and the date of application for extension | Update the expected return date after approval |
| Return | Associate the original borrowing details; fill in the actual return date | After approval, the management status is updated to Borrowable |
| Transfer | Fill in the reason for the move; fill in the new address for address changes, fill in the new customer for customer changes | Update customer, delivery address and other information after approval |
Borrowing, extension, return and transfer will generate corresponding equipment asset history.
Conditions for automatic resume generation
| Event | Condition |
|---|---|
| Equipment creation | Create equipment manually or automatically from a delivery note |
| Equipment maintenance | The work order is associated with the equipment, and the work order status changes to Completed |
| Equipment recycling | Account field changed from specific customer to empty |
| Equipment is down | Status changes from Available to Disabled |
| Device activation | Status changed from Disabled to Available |
| Custom events | Enterprise custom event types, written through functions, etc. |
Device code difference
| Code type | Content | Whether to jump directly to device details | Typical uses |
|---|---|---|---|
| The system generates a QR code | Equipment details link | Yes | Engineers or end users scan the code to view and report repairs |
| External machine generates QR code | Device link generated in the format specified by the company | Yes | Factory code and synchronize device data |
| Equipment live code | A blank QR code that is later bound to equipment | Yes, after binding | Label deployed equipment that did not previously have a code |
| Barcode or QR code without link | device_code text |
No | Query tool or form scanning and matching device |
Key limitations
- There are irreversible restrictions on equipment asset BOM and work orders supporting multiple devices; the settings page of asset tracking management also prompts that it cannot be turned off after it is turned on.
- Automatically generate equipment assets, work orders support multiple equipment, and work orders update equipment locations are independent switches.
- Submitting an extension, return, or transfer does not immediately update equipment fields. If approval applies, use the post-approval values.
- End users need object and data permissions to scan QR codes. Public guest access increases visibility across all equipment.
- Barcodes only return text and do not go directly to device details like QR codes that contain links.
- Equipment IoT integration requires the purchase of separate plug-ins; scenarios such as scanning QR codes for repairs, installation, inspections, and repairs need to be coordinated with service capabilities.