SD BOM - Item category group and item category

[Former Member]

Dear Sirs,

My question is regarding SD BOM. I have the following process - the company buys two materials from different suppliers and put this components on the stock. Then the Client make a request for the set of the components. Our company does not do any production or merging with these components, just sells them as a kit. Valuation is made at header material level. Also we have no set as itself on our stock, just components.

Could you please advice me which item category group and item category I should use?

Should I use 0002 or ERLA or LUMF item category group? TAC or TAQ item category?

Thank you in advance, Daria.

[reazuddin_md]

Hi Podrezova,

As per my understanding,

- Company will buy components from different suppliers/vendors & keep it in stock seperately (not combined as one part)

- Client places order these components as KIT. A single part

- Components will be delivered from Warehouse & Material valuation is at KIT level, not at component level

Options:

- Create KIT item. specific KIT for the combination of Components (assume components are not keep changing for this KIT)

Some where in system, you have to define "KIT components". Eg: KIT X = Component A + Component B. You can do this by creating Sales BoM, but delivery will be @ component level to reduce the stock & Valuation @ KIT item (here you need to be more clear, how to do the valuation for Header item, either you wanted to sum up cost of Components & add to KIT, which can be done with copy control config @ item using "Cumulate Cost" option.

in your query, its not mentioned, what level is the pricing? I understand, Pricing will be @ KIT level. So its main item level pricing.

You can use ERLA item cat group.

- Create Order for KIT (explode Sales BOM for components)

- Create Delivery for KIT & Components

- PGI for Components / Valuation for KIT.

- Create Billing only for KIT (Make Components are not relevant for pricing/billing)

Note:

Not exactly sure your current business scenario. Above is only based on assumption

Regards,

RMD