cancel
Showing results for 
Search instead for 
Did you mean: 

Planning at Sub-Assy Phantom Level - Work order&Sales order FG Level

Former Member
0 Kudos

Hi everyone,

I'm searching for a way of setup my SAP to have my MPS loaded at the sub-assy(phantom) level and my work orders/sales orders loaded at the FG assy level.

Loading the MPS at the sub-assy and exploding requirements to the components are working fine, the issue is that I need to create a work order/sales order on the FG assy level to be able to backflush the components, create FG stock and sell the product. When I create a work order on the FG assy level SAP is adding additional dependent requirements on the raw material level, duplicating the demand some times,I would like to avoid that. Iwanted to keep just dep requirements generated by the FCST loaded under the Phantom Sub-assy level........Do you have any ideas on how to solve this? Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Sorry to bother......unfortunately it didn't work......anything I put as requirement (sales order, work order) under the FERT level is driving demand under the ZROH level.....so it;s still duplicating the demand...

Former Member
0 Kudos

Hi Dharma,

The most important thing is that I'm not creating stock/work orders on HALBS as they are Phantoms......my work orders are being created on the FERT level and consuming the ZROH direct.....I'm loading the demand on the HALB just to create requirements on the ZROH level as the customer sends me Forecast under HALB level. So when I load any requirement(Sales Order/Work orders) on the FERT level it doesn't net out the demand I have already loaded on the Halb(PHANTOM) nor the ZROH level.

Thanks!

Former Member
0 Kudos

Hi,

What I have given suggestion will work if the HALB is not a phantom assembly.

For your requirement use strategy 70 for ZROH. Maintain Mixed mrp - 1 in mrp3 view

Individual/ collective indicator 2 in mrp 4 view.

Try it & revert back.

Former Member
0 Kudos

Hi Dharma,

I've tested this Strategy but it didn't work for my case........let me try to explain my issue in a different way.

The way my BOM's are setup today, I have several Halbs(Which are setup as phantoms) that are options to the product I sell, and the customer is sending me forecast under these options only, not on the Ferts. I'm loading my LSF under this halb phantom level and this is demand is exploding to the ZROHS, which is what I want. When the customer wants to buy a product from me, they send me a PO under the FERT level (Each Fert has a different combination of Halbs). In order to backflush my ZROHs I have to create a work order under the FERT level(As the HALB is phantom) and this is generating additional dependent requirements on the ZROH level..........

One example, if I receive a Forecast for 1000 pcs of the HALB A, I load the LSF on Product A and my raw material will have 1000 pcs as depreq. When I receive an order from the customer, let's say they want to buy 200 pcs(which should be already included on the demand I loaded under the Halb), I create the work order on the Fert level for 200 pcs. If I run the MRP at this moment the system will request me to buy the 1000 pcs already forecasted plus these 200 pcs that I got one order for....

Hope I could explain better.

Thanks for the help,

Douglas

Former Member
0 Kudos

Hi Douglas Citro,

Clearly understood your problem.

you are creating demand for halb and making stock. When sales order comes for fert you want to consume halb from this stock. But now dependent requirement is creating duplication or additional req for HALB & ZROH.

Normal procedure is if you create order it will consume from stock. For that

use strategy group 10 & availability check 02 in mrp3 view of material master for HALB & ZROH

If you want to sell HALB, use strategy 40.

If any doubt please come back.

If cleared reward your points.

Regards,

Dharma

Former Member
0 Kudos

Hi,

Use strategy 40 for sub assembly.

This function is whenever requirements comes system will check the stock. If the stock is available, consumes from that. If not system will create planned order.

In your scenario you are creating independent requirement at sub assembly level(HALB).If the dependent req comes from FERT, it will check the stock. If stock is not available system will create planned order. No duplication of demand.

Regards,

Dharma