c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <834300@xxxxxxxxxxxxxxxxxx>]

Hello Kevin,

I just tested the scenarios you described, and something is not clear
for me. Let's consider the 2 cases separately.

* Case 1: Direct Delivery Supplier->Customer

As you noted yourself, this scenario bypasses a part of the regular stock flow, preventing the goods from actually entering your warehouse. As OpenERP relies on inwards and outwards stock moves to drive real-time valuation GL entries, this explains why the "inwards journal entry" is missing. In order to properly detect the need for the inwards entry, OpenERP would need to consider a Supplier->Customer stock move as a dual entry: first inwards, then outwards - this is not the case now.
We could add that, but as you have perhaps noticed, in this scenario you also have a duplicate stock move waiting - the delivery order for your SO! In your scenario you processed it, which is what created the outwards journal entry. This is actually incorrect, because you'd be doing the same operation twice, and the stock levels (even if virtual) will be wrong. And if we were doing the dual journal entry for the Supplier-Customer move, you'd end up with twice the outwards entry BTW.

I think the issue is more complicated than it looks like if we want to support this use case. This could perhaps be done by a 'direct_delivery' module that would take care of all the steps.
But I can only confirm what Amit says, this can only be handled as a improvement suggestion for the future (perhaps someone from the community would like to make such as module), not as an actual bug. And even more so because the same results can be achieved with a different use of the system (cfr Case 2).


* Case 2: PO was receipted into stock then dispatched

This case should work fine, as it follows the regular stock flows, and seems like a valid alternative to Case 1.
I have just tried to reproduce this case on v6.0.3, and I get the expected results, as you will see in the attached video. I did not change the default location selected by the system for the PQ - it was the default Stock location of my warehouse.
As you say it does not work for you, I would like to understand if we have a real bug for this case or not?
You mention in comment #1 that manually changing the destination location of the PQ seems to produce the correct results - as you can see I did not, and it worked. In fact, as long as the destination of the Incoming Shipment is any location of type "Internal" within your warehouse, it should work. Picking "Inwards" or plain "Stock" should work fine as far as GL entries are concerned, and it does seem to.
Could you clarify this second case (your video only covered the first iteration as far as I could see)?

Thanks a lot!


** Attachment added: "demo of so-po flow with real-time valuation"
   https://bugs.launchpad.net/openobject-addons/+bug/834300/+attachment/2366806/+files/so-po-demo-1.ogv

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/834300

Title:
  Linked SO to PO - inwards stock journal not being created

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  v 6.0.2 with anglo-saxon accounting

  Created a SO and made product from order. Ran scheduler & created PQ - confirmed as PO. I ran two iterations
  1. The PO was a direct ship to customer
  2. The PO was receipted into stock then dispatched.
  Both had the same issue (but obviously different entries)

  For iteration1 entries generated are:
  Purchase Jnl:
  DR Stock Input account
  CR Creditors

  Sales Jnl:
  DR Debtors
  CR   Income Account
  DR Expense Account
  CR  Stock Output Account

  Missing is the following journal which should be created by the inwards goods move
  DR Stock Output Account
  CR   Stock Input Account

  alternatively there should be two entries with Stock Variation Account
  as the other side (ie one for the in move one for the out move).

  Since there is no in/out move in this circumstance I thought that
  might be the problem, so processed as iteration 2 above - jnls created
  were:

  Via Outwards Jnl
  DR Stock Output Account
  CR      Stock Variation Account

  Via Purchase Jnl
  DR  Stock Input Account
  CR       Creditors

  Via Sales Jnl
  DR Debtors  
  CR     Income Account
  DR Expense Account
  CR    Stock Output Account

  
  Missing is the inwards goods stock journal - normally stock would come into the inwards location then have a transfer to stock but when a PO is generated from a SO the location is set to the stock location so it looks like the inwards entry is being missed.

  Entry should be:

  DR Stock Variation Account
  CR    Stock Input Account

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/834300/+subscriptions