back to top

MAS 500 Items – Kit Structure

In MAS 500 there is the concept of a “Kit” which is a group of items that are bundled together and sold as a single entity.  Think of something like a computer which consists of various hardware and software components. The Kit itself has a separate price than what the sum of all of the components may be.


MAS 500 uses two tables to store the Kits in the item catalog.  First of the Kit item has an ordinary line in the timItem table, just like any other item.  These items exist with an ItemType = 7.  These items then have a foreign key relationship in the timKitCompList via timItem.ItemKey = timKitCompList.KitItemKey.  The timKitCompList is a table which contains the definitions of what items make up the kit.  As described, the KitItemKey contains the ItemKey of the actual kit item from the timItem table, while the timKitCompList.ItemKey contains the ItemKey for the various components in the kit.  These components can then tie back to the timItem table via timKitCompList.ItemKey = timItem.ItemKey.


We can see a sample query showing the complete query here:


select
    a.itemkey as kit_itemkey, –primary kit item
    b.shortdesc as kit_shortdesc, –primary kit description
    a.stdprice as kit_stdprice, –price of kit
    cast(c.compitemqty as int) as comp_quantity, –quantity of component in kit
    d.itemkey as comp_itemkey, –component item
    e.shortdesc as comp_shortdesc –component description
from
    dbo.timitem a with(NOLOCK) left join  –Product table
    dbo.timitemdescription b with(NOLOCK) –Product description
        on a.itemkey = b.itemkey left join
    dbo.timkitcomplist c with(NOLOCK) –List sub components
        on a.itemkey = c.kititemkey left join
    dbo.timitem d with(NOLOCK) –sub product table
        on c.compitemkey = d.itemkey left join
    dbo.timitemdescription e with(NOLOCK) –Sub Product description
        on d.itemkey = e.itemkey
where
    a.itemtype = 7 


It should be noted that there are two types of Kits: BTO Kits and Assembled Kits.  BTO Kits (ItemType=7) stand for Build To Order Kits and are kits where the components are modifiable.  One other type of kit is the Assembled Kit which is a pre-defined kit that is not modifiable.  This type of kit has a ItemType=8.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos