# SyteLine csi_kit_live_kit and what a CSI warning means

> Source: https://netray.co/erp-help/syteline-csi-kit-live-kit-and-csi-warnings
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

CSI is Infor CloudSuite Industrial, the current name of SyteLine, so a CSI warning is a non-blocking message from the application that tells you something is questionable but lets you continue. We cannot confirm a documented public meaning for an object named csi_kit_live_kit, so the dependable method is to locate it in your own database, read its definition and check how kits are configured.

## Kind

error

## System

syteline

## Erp

Infor SyteLine (CloudSuite Industrial)

## Module

Kits / Messages

## Query

infor syteline csi_kit_live_kit

## Alternate Queries

- what is a csi warning
- syteline kit warning
- csi_kit_live_kit table or procedure

## Applies To

Infor SyteLine / CloudSuite Industrial on SQL Server. Object names are specific to your version and any custom or bundled extensions.

## Steps

### Investigate a kit-related warning or object

**Items:**

- Read the exact warning text in the message bar or the error log, and note the form you were on.
- Search SQL Server for the object: SELECT name, type_desc FROM sys.objects WHERE name LIKE '%kit%live%'.
- If it is a procedure or view, read it with sp_helptext 'objectname', or script it in SQL Server Management Studio.
- Check where it is called from: search the Mongoose configuration (forms, IDO methods, event handlers) and your custom code for the name.
- Check the kit item setup: the item is flagged as a kit, its components exist and are active, and the quantities and UMs are valid.
- Test the same action with a simple kit item to see if the warning depends on the data.
- Check recent customisations, upgrades and custom stored procedures that may have introduced or changed the object.
- If it remains unexplained, open a case with Infor support and attach the message text, the object definition and the steps to reproduce.

## Sections

### What a CSI warning is

**Body:**

SyteLine messages come in grades. Errors stop the action, while warnings and informational messages let the user continue. A warning on a kit usually concerns data that is allowed but suspicious, such as a component with no stock or a quantity of zero.

The message text, not the object name, is the best search term for Infor documentation and community posts.

### How kits work in general

**Body:**

A kit in SyteLine is an item that is sold or issued as a parent made of component items. Depending on setup, the components can be reserved, picked and shipped with the parent, and the parent's availability depends on the components.

A live kit view or procedure of the kind your question names would typically report or compute that component availability in real time. Treat that as an inference to verify in your own database, not as documented behaviour.

### Why the object may not be documented

**Body:**

SyteLine ships many internal procedures, views and functions that Infor does not document. Others come from add-ons, partner extensions or your own customisations, and names prefixed with a company or product code are common.

Never modify an Infor-delivered object directly. Changes belong in your own extension layer so an upgrade does not overwrite them.

**Code:**

- SELECT name, type_desc, create_date, modify_date
FROM sys.objects
WHERE name LIKE '%kit%'
ORDER BY modify_date DESC;

EXEC sp_helptext 'dbo.YourObjectName';

### Troubleshooting data, not code

**Body:**

Most kit warnings clear when the data is fixed: add the missing component, fix the quantity or unit of measure, activate the item, or correct the warehouse. Check the data before changing any code.

If the warning appears only for a specific item or customer order, compare it with a working kit. The difference is usually in the setup.

## Pitfalls

- Editing a delivered stored procedure or view and losing the change in the next upgrade.
- Treating a warning as an error and reworking data that is acceptable.
- Assuming an object name proves what it does; read its definition.
- Ignoring the exact message text when searching for help.
- Testing kit changes in production rather than a test database.

## Ai Angle

SyteRay can search a SyteLine database for an unfamiliar object, read its definition and the forms and IDOs that reference it, and explain what it does in plain language, all against your own schema and on-prem if needed. That is faster than guessing from the name, and it states clearly what it could and could not verify.

## Faq

### What is a CSI warning?

**Answer:** CSI stands for CloudSuite Industrial, the current name of SyteLine. A CSI warning is a non-blocking message from the application: it flags something questionable but lets you continue.

### What is csi_kit_live_kit?

**Answer:** We cannot confirm a documented public definition. Find it in sys.objects in your own database, read its definition with sp_helptext and check what calls it. The name suggests kit availability logic, but verify that.

### How do I find where a SQL object is used?

**Answer:** Search procedure and view definitions with sys.sql_modules for the name, and search the Mongoose forms, IDOs and event handlers. Include custom code and scheduled jobs.

### Should I edit the object to remove the warning?

**Answer:** No. Fix the data causing it or add your own extension. Direct edits to delivered objects are lost at upgrade and may break support.

## Search terms

csi_kit_live_kit, syteline kit warning, what is a csi warning, cloudsuite industrial kit, syteline kit item, syteline sql object search

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json