Former Member

### How to group different BOM category with same BOM number ?

Hi,

While checking BOM header data from STKO table with BOM number, getting different BOM category data like E,M,S and T with same BOM number. How this different BOM category are linked with same BOM number ? How we need to do that.

When i am searching with BOM number in the respective BOM link category tables like Equipment BOM - EQST, Material BOM - MAST, Standard BOM - STST and Functional Location BOM - TPST all bill of materials are pointing out to the same number.

capture.jpg (51.3 kB)
1capture.jpg (38.2 kB)
2capture.jpg (42.7 kB)
3capture.jpg (36.3 kB)
4capture.jpg (39.8 kB)
10|10000 characters needed characters exceeded

• Apr 05, 2018 at 07:38 PM

That is no group.

All kind of BOMs are stored in the same tables.

Each BOM category can have their own number range.

And in each number range you can use the same interval.

A material BOM with number 310 is something totally different than a equipment BOM with the same number. Such searching BOMs by number does not make much sense., you always have to see it together with the BOM category.

10|10000 characters needed characters exceeded
• Former Member

Hi,

I agree with your point all kind of BOMs are stored in the same table (STKO and STPO) for Header and Details. When i am searching with BOM number in the respective BOM link category tables like Equipment BOM - EQST, Material BOM - MAST, Standard BOM - STST and Functional Location BOM - TPST all bill of materials are pointing out to the same number.

• Apr 06, 2018 at 12:11 PM

Each bom category has its very own number range:

STUEC

STUED

STUEE

STUEK

STUEM

STUEP

STUES

STUET

You can define the interval via SNRO

In standard all intervals are defined from 00000001 to 99999999

It is your own design decision if numbers matter for you or not. Some feel comfortable if the can identify based on the first digit whether it is a material BoM or an equipment BoM. Others don't bother about the numbers, as the number is only needed to have a unique identifier to enable a program to find records in a table.

And in case of a BOM it is by design that the number must only be unique within a BOM category. And this is the case with your BOM number 310.