Community mailing list archives

RE: Stock Moves for In-Transit Location (same company, v7)

Ursa Information Systems, Ray Carnes
- 04/27/2015 22:37:31
Thanks to both of you.


You suggestion is working well - just verifying some of the predictable corner cases that may come up.  


In Transit is the Customer's term.

For what my customer needed, it was pretty simple to implement once I had a push from Graeme.

(1) PO issued to record the 'original agreement' including the original address and order.  Note that whatever happens after this is the 'fulfillment' of this agreement.  The agreement remains the agreement, the fulfillment can be as similar or as different to the agreement as needed.  Odoo has a suggested incoming stock quantity, the most accurate number it CAN have until the fulfillment details are known.

(2) FIRST Incoming Shipment to record the 'fulfillment of the original agreement' receives the items into "In Transit" with as much a match to the PO as the Supplier and Customer agreed upon after the original agreement was considered.  In there is information that allows the customer to enter the predicted arrival date, they can do so and Odoo now has the most accurate number it CAN have of items actually received, and by having them in a global stock location, just doesn't know where they will ultimately end up.  If this is know at this stage, the NEXT Incoming Shipment can be updated.  If not, the Customer waits until they know.

(3) SECOND Incoming Shipment (or Internal Move - works equally well with both) receives the items into "Local Stock" with the ACTUAL arrival date.  Both the 'estimated'and the 'actual' receiving dates are retained.  By repurposing the serial number SPLIT function, the Customer can update the local stock locations and quantities and have the corresponding stock moves updated (generating the correct Stock Accounting moves).  This matches their need to not always decide the end shipping location until the boat clears Customs.

Inspection Locations and/or Shipping and Receiving location can be handled in a similar way if needed.

Accounting moves at (2) are Stock Input / In Transit Assets **
Accounting moves at (3) are In Transit / Inventory Assets

The only thing about this is living with an two part stock accounting move ( ** from Stock Input to Inventory Assets and them immediately from Inventory Assets to In Transit Assets) instead of just the NET of that (from Stock Input to In Transit Assets).  

I actually don't mind this because these 'extra' accounting moves can be used in Accounting as a double check to make sure the second part of the receiving actually happens.


Subject: Re: Stock Moves for In-Transit Location (same company, v7)
Date: Tue, 28 Apr 2015 00:33:34 +0000

while I've never coded for this platform, logistics is my hobby. and I've made some weird moves in my day,  think 50 piece moves, each piece over 64 MT from all over the word having to arrive within 7 days at 1 location, not fun LOL
some things you might what to model ( the cargo flow )

Purchase order issued to supplier
purchase order has delivery address and product order
supplier place it on a truck with product
supplier then gives a bill of lading with date stamp, product in truck, and estimated delivery date ( indexed to PO )

( skip live tracking  )

truck arrives at deliver terminal 
bill of lading received
truck accepted and given an unloading bay assignment
product unloaded at bay, counted, confirmed and signed for

product sorted and given inside stock location OR cross docked for outbound ( product was sold before arrival so it is just moved from unloading bay to loading bay )

your problem while very easy to see, seems to be hard to implement 
because the Purchase Order ( PO ) does not seemed to be confirmed at the unloading bay " intransit location "
your "intransit" is really a discharge/receiving bay and that's the  first confirmation point that you have product.

ALSO rename intransit to something else. with cargo, in transit has a movement definition
as in ... on truck going somewhere, on pallet in warehouse moving to loading bay or a waypoint storage location like a hub.

i hope this helps out and adds a little bit of luck to your solution

Michael Rasch
Cell : 305-741-1819
Skype : michael.rasch.florida


On Mon, Apr 27, 2015 at 7:23 PM, Graeme Gellatly <> wrote:
Transfers between internal locations from memory don't create entries.  Maybe if you chained Internal -> Virtual -> Internal

On Tue, Apr 28, 2015 at 10:57 AM, Ray Carnes <> wrote:

I have a use case that I am having problems configuring Odoo to support:

Receive goods first into an InTransit location, with corresponding debits to "InTransit" (credit from Stock Input).
Receive goods second into a Stock location, with corresponding debits to "Stock" (credit from InTransit).

The purpose is to see a value of inventory assets onsite and offsite. 

1) Company creates a standard PO. (OK, Incoming QTY set correctly)
2) Company receives stock into In Transit location. (OK, )
3) Journal Entries created: Debit to "Stock Valuation - InTransit" via Credit from "Stock Input". (OK)
4) Company receives stock into Stock location. (OK)

This is where I can't work it out:

5) Journal Entries created: Debit to "Stock Valuation - Stock" via Credit from "Stock Valuation - InTransit"

I have setup 'Transit'  as an Internal Location, chained to Stock, manual, Getting Goods (child of stock) and have played with the way this is setup.

Has anyone done something similar?  Am I thinking about this the right way?


Post to:

Post to:

Post to: