[PS] Phantom BoM triggers a Manufacturing Order

Asked by Harmel Delphine (OpenERP)

trunk addons revno 4784

* Having a stockable product, make to stock, produce
* Create a phantom BoM for this product containing two CPU1 product (for example)
* Sell this product
* Trigger the scheduler checking the "Automatic order point" option

Obtained result : a manufacturing order is generated

Expected result : no manufacturing order is generated

reported by dha, OpenERP Prof Serv

Question information

Language:
English Edit question
Status:
Open
For:
Odoo Addons (MOVED TO GITHUB) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Harmel Delphine (OpenERP) (dha-openerp) said :
#1

trunk addons revno 4784

* Having a stockable product, make to stock, produce
* Create a phantom BoM for this product containing two CPU1 product (for example)
* Sell this product
* Trigger the scheduler checking the "Automatic order point" option

Obtained result : a manufacturing order is generated

Expected result : no manufacturing order is generated

reported by dha, OpenERP Prof Serv

Revision history for this message
Amit Parik (amit-parik) said :
#2

Hello Harmel,

I have checked your issue and this is not a bug, It is the current behavior.

I am explain the system behavior.

If you are creating a product (make to stock-> produce) and which have not a real stock.
And you are creating a SO for this product then this product 's procurement will be generated.

Now there is two way to run this procurement:
 1) If you run the procurement manually (going on particular procurement and press the "Run procurement" ) the procurement goes in to exception with this error: "Not enough stock and no minimum orderpoint rule defined."(you can run this scheduler by changing procurement method "On order" ) .

2) If you run the scheduler with checked the "Automatic order point" option and procurement goes in exception then it will create a one automatic operation of the scheduler with the quantity of the procurement order (it will not take care about minimum stock rule) So it will create a related MO (if the supply method = "produce" and if you give supply method = "buy" it will create related purchase order.)

Form your bug specification you have run the scheduler checking with the "Automatic order point" option so the MO will generated which is the normal behavior and this is not a bug that's why I am closing this issue.

Hope this will help for you.

Thanks for the understanding!

Revision history for this message
Quentin THEURET @Amaris (qtheuret) said :
#3

Hello Amit,

Is also the normal behaviour when the product has a Phantom BoM ? I
don't think so.

I think the correct behavior is to have a generation of stock moves not
MO because there is nothing to produce with a Phantom BoM.

Quentin

Le 21/06/2011 13:31, Amit Parik (OpenERP) a écrit :
> Question #162205 on OpenERP Addons changed:
> https://answers.launchpad.net/openobject-addons/+question/162205
>
> Status: Open => Answered
>
> Amit Parik (OpenERP) proposed the following answer:
> Hello Harmel,
>
> I have checked your issue and this is not a bug, It is the current
> behavior.
>
> I am explain the system behavior.
>
> If you are creating a product (make to stock-> produce) and which have not a real stock.
> And you are creating a SO for this product then this product 's procurement will be generated.
>
> Now there is two way to run this procurement:
> 1) If you run the procurement manually (going on particular procurement and press the "Run procurement" ) the procurement goes in to exception with this error: "Not enough stock and no minimum orderpoint rule defined."(you can run this scheduler by changing procurement method "On order" ) .
>
> 2) If you run the scheduler with checked the "Automatic order point"
> option and procurement goes in exception then it will create a one
> automatic operation of the scheduler with the quantity of the
> procurement order (it will not take care about minimum stock rule) So it
> will create a related MO (if the supply method = "produce" and if you
> give supply method = "buy" it will create related purchase order.)
>
> Form your bug specification you have run the scheduler checking with
> the "Automatic order point" option so the MO will generated which is the
> normal behavior and this is not a bug that's why I am closing this
> issue.
>
> Hope this will help for you.
>
> Thanks for the understanding!
>

Revision history for this message
Amit Parik (amit-parik) said :
#4

Hello Quentin,

Yes, I have missed the specification of the BOM type.
This doesn't create any changes is your BOM type is "Phantom" or "Normal" in above specification.

Because "Phantom" type 's BOM are used when have a BOM 's sub product in hierarchy.
like Main product (produce)->Subproduct(produce)->(last product)(buy).

In this example if you select the Phantom BoM then only one production order/ procurement order has been generated and if you select the BoM type as a "Normal" for all BoM structure production order/procurement order has been generated.

So it doesn't matter in this scenario which BoM type you have selected the above behavior works same.

Thanks.

Revision history for this message
Quentin THEURET @Amaris (qtheuret) said :
#5

Okay, but when you sale a product which is itself a Phantom BoM (it's the Delphine's example), you want to deliver all components of the BoM, not the final product. So the MO is useless.

Quentin

Revision history for this message
Harmel Delphine (OpenERP) (dha-openerp) said :
#6

I confirm what Quentin said. It should generate stock moves and NOT a manufacturing order. This is the goal of the phantom or SET type of a BoM.

Revision history for this message
bgfcj jhgfcg (reawer654) said :
#7

I also ordered from there and did not received ,y order then I tried to clear this issue and took guide from here https://easytrackings.com/ and you can also take guide from here.

Can you help with this problem?

Provide an answer of your own, or ask Harmel Delphine (OpenERP) for more information if necessary.

To post a message you must log in.