The following data actions occur when Kitting. (In this set of information a limited BOM was created with only two components, one of which was allocated to a project.)

When kitting the first part, (which is a part allocated to a project)

The  “Inv_res” table, will have a record created for this part and a link to the “Fk_Prjunique” project key.

Once the user issues it to the kit, the stored procedure (trigger) in INVT_ISU table will be create. Once this record is created, the program will check if the part has any allocation records, and decrease allocation qty (actually insert a negative qty record) if found. It first checks if part is allocated to work order, then checks it it’s allocated to project.

The INVTMFGR Qty_oh and Reserved fields are reduced by the amount issued.

In the JBSHPCHK table, a recorded is added that the kit is in process.

In the KAMAIN table, records of all parts of the kit are added, and the record of the issue is recorded.

In the KADETAIL table, all parts in the kit are added as parts shortage, and issue records are added for parts kitted.

In the KALOCATE table, a record is added of the issue.

In the WOENTRY table, the kit status is changed to true. (on first issue)

In kitting the second part,  a non-allocated part:

A record is added to the INVT_ISU table, indicating that the parts were issued to WIP, and a specific work order. Various keys are used for tracking purposes.

The INVTMFGR Qty_oh field is reduced by the amount issued.

In the KAMAIN table records are added of the parts used in the kit, and actual issues thereof.

In the KADETAIL table, issue records are added for parts kitted.