Create a Procurement BOM from multiple EBOM

[rkayasth]

create a new BOM from multiple EBOM.

Details:

For submitting a procurement request against an assembly (End Item), we create a procurement BOM

we will refer multiple sub assemblies (EBOM) of the End Item and get all the buy parts specific to a vendor in one BOM (Procurement BOM)

i.e. need a functionality for creating a BOM from multiple EBOM and maintaining the tractability between them (like MPMLink, MBOM management)

[BrianToussaint]

@rkayasth Have you seen this?  https://community.ptc.com/t5/Windchill/Customize-BOM-Type-values-in-MPMLink/m-p/560050#M57444

I know that I was looking into this a few years ago but we didn't do anything with it, but it was fairly easy to get a new BOM type in my test server.

[rkayasth]

@BrianToussaint 

How do we use 2 EBOM to create a new BOM (say Procurement type) in MAPSB browser (MPM Link)

we need to show the tractability between the EBOM's (2 different) and the Procurement BOM.

The Solution provided stands true for 1 to 1 BOM, i.e. 1 EBOM/MBOM to 1 Procurement BOM

[BrianToussaint]

@rkayasth 

Maybe I misunderstood your request.  From what you are saying now is that you want to have multiple End Items pointing to one Procurement BOM?  Because the way it reads with the multiple sub assemblies from one End Item is how it is designed to work.  I would change the wording of your original post to not include the multiple sub assemblies aspect as that is how it works.  Or am I still off base?

I could see a case for putting multiple End Items for building something like this.  But what BOM would drive the downstream BOM?  Wouldn't you basically be building a new BOM for the Procurement BOM to reference?  If that is the case, why don't you create a BOM with all the end items that the Procurement BOM will reference?

Another question is, are you wanting the Procurement BOM to be flat, which I think you do?

I'm just trying to better understand your requirement.

[rkayasth]

@BrianToussaint 

First of all thank you for the insights you are bringing to the table,

I will try to rephrase and explain the requirement in more detail in steps -

1. For us the top level Part is the End Item, which has various sub-assemblies in it.

2. For us each sub-assembly is an EBOM

3. Now, if i want to create a procurement order against the End Item (Top level part), i would consider all the sub assemblies in it (i.e multiple EBOM)

4. Say for Example, each of the the sub-assembly (Ebom) has a part (sensor) in it.

5. What we do is,  we will refer all the sub-assemblies in the END item and collate the sensor part requirement.

6. we will create a flat BOM (Procurement BOM) which will be then referred for sourcing, in this case BOM will have different sensor parts involved.

I hope the above will enable you to understand the exact requirement.

To Answer, some of your questions asked above -

1. We create a Procurement BOM against each End Item, 1 end item will have 1 Procurement BOM (as we deal with configurable products)

2. Procurement BOM could be derived from either EBOM or MBOM, the approach should be the same.

3. Procurement BOM is a flat BOM.

Considering the above details, all your suggestions will be appreciated to manage the procurement BOM with the best possible way.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.