Sharing Warehouses between companies

[Hendrik Brandes]

Hello,

I have a requirement, where a company has a set of affiliate companies, which are taking products from a central warehouse.

The main company holds the warehouse and all of the affiliate companies can access the warehouse for their own business.
When taking a product from the main warehouse, a new line is added to an invoice, which will be closed at the end of the day
and which will be used for the internal payment process.

In the existing solution, the used software component has a direct link between both database files ( dbase ).

I asked, if it is possible, to use the multi company feature of tryton to meet this requirement, or should I develop a module,
which communicates via proteus or something else between the main instance and the instances of the affiliates.

Thank you and kind regards,
Hendrik

[Cédric Krier]

Using multi-company should always been the last solution because it is
complex and has many constraints like using exactly the same sets of
modules for all companies etc.
Indeed what you describe looks like a EDI communication between the
companies. There have been already many discussion about this topic but
as far as I know there is not yet any module available.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[Hendrik Brandes]

Am Samstag, 21. November 2015 14:35:04 UTC+1 schrieb Cédric Krier:

On 2015-11-17 08:46, Hendrik Brandes wrote:
> I have a requirement, where a company has a set of affiliate companies,
> which are taking products from a central warehouse.
>
> The main company holds the warehouse and all of the affiliate companies can
> access the warehouse for their own business.
> When taking a product from the main warehouse, a new line is added to an
> invoice, which will be closed at the end of the day
> and which will be used for the internal payment process.
>
> In the existing solution, the used software component has a direct link
> between both database files ( dbase ).
>
> I asked, if it is possible, to use the multi company feature of tryton to
> meet this requirement, or should I develop a module,
> which communicates via proteus or something else between the main instance
> and the instances of the affiliates.

Using multi-company should always been the last solution because it is
complex and has many constraints like using exactly the same sets of
modules for all companies etc.

Ok, but that's no problem in this context at all. For me it looks like an alternative idea for having this shared-warehouse concept.
But through the discussions about having multi-company instances, I wonder, how long this feature stays within the tryton-kernel.
 

Indeed what you describe looks like a EDI communication between the
companies. There have been already many discussion about this topic but
as far as I know there is not yet any module available.

Regarding the EDI: Do you think, that using proteus within a tryton module is possible?
 

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Best regards,
Hendrik Brandes

[Cédric Krier]

On 2015-11-23 06:42, Hendrik Brandes wrote:
> Am Samstag, 21. November 2015 14:35:04 UTC+1 schrieb Cédric Krier:
> > Using multi-company should always been the last solution because it is
> > complex and has many constraints like using exactly the same sets of
> > modules for all companies etc.
> >
>
> Ok, but that's no problem in this context at all. For me it looks like an
> alternative idea for having this shared-warehouse concept.
> But through the discussions about having multi-company instances, I wonder,
> how long this feature stays within the tryton-kernel.

I think you should ask the opposite question when will multi-company
available. But as usual, we can not answer such question.

> > Indeed what you describe looks like a EDI communication between the
> > companies. There have been already many discussion about this topic but
> > as far as I know there is not yet any module available.
> >
>
> Regarding the EDI: Do you think, that using proteus within a tryton module
> is possible?

I don't see the point. But I guess as far as you have the credentials.

[Hendrik Brandes]

It's because of my less experiences with python ;-) I suggest, that it could be problematic
when mixing concrete tryton objects with remote "proteus.tryton.xxxx" objects. So I think, I will give it a try!
 

[Dominique Chabord]

2015-11-23 15:42 GMT+01:00 Hendrik Brandes <hendrik....@googlemail.com>:
>
>
>>
>> Using multi-company should always been the last solution because it is
>> complex and has many constraints like using exactly the same sets of
>> modules for all companies etc.
>
>
> Ok, but that's no problem in this context at all. For me it looks like an
> alternative idea for having this shared-warehouse concept.
> But through the discussions about having multi-company instances, I wonder,
> how long this feature stays within the tryton-kernel.

using the multi company for this leads to a problem of consistency
between goods movements, content lists and accounting documents

>
>>
>> Indeed what you describe looks like a EDI communication between the
>> companies. There have been already many discussion about this topic but
>> as far as I know there is not yet any module available.
>
>
> Regarding the EDI: Do you think, that using proteus within a tryton module
> is possible?

I think you should keep proteus script independent from any party. It
could be a kind of man-in-the-middle which
- gets products data and stock levels from head-office database and
pushes it to every affiliate so affiliate can purchase
- collects purchase orders from affiliates and send them as sales to head-office
- get shipping list and create reception lists
- gets invoices from head-office and distributes them to affiliates.
- log every data exchange

This man-in-the-middle might mimic a true EDI.

I think this would keep everything consistent anytime with no double
encoding, people don't loose contrôle on process and every tryton
instance works as it is supposed to work.

>
>>
>>
>> --
>> Cédric Krier - B2CK SPRL
>> Email/Jabber: cedric...@b2ck.com
>> Tel: +32 472 54 46 59
>> Website: http://www.b2ck.com/
>
>
> Best regards,
> Hendrik Brandes
>

> --
> You received this message because you are subscribed to the Google Groups
> "tryton" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tryton/4db13982-6dcb-441a-8959-7b1cbc3f3a81%40googlegroups.com.

[Dominique Chabord]

2015-11-23 17:06 GMT+01:00 Hendrik Brandes <hendrik....@googlemail.com>:
>

>> >
>> > Regarding the EDI: Do you think, that using proteus within a tryton
>> > module
>> > is possible?
>>
>> I don't see the point. But I guess as far as you have the credentials.
>
>
> It's because of my less experiences with python ;-) I suggest, that it could
> be problematic
> when mixing concrete tryton objects with remote "proteus.tryton.xxxx"
> objects. So I think, I will give it a try!
>

It will certainly work if you make enough assumptions.
My intuition leads me to think it a very bad design.
Concerns will be about complexity, maintanability, security,
flexibility, auditability etc...

[Cédric Krier]

Of course you can not mix.

PS: Please don't copy the original email twice in your answer, see
http://groups.tryton.org/netiquette