[Openerp-community] New Intercompany Process Modules for OpenERP

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[Openerp-community] New Intercompany Process Modules for OpenERP

Eric Caudal - www.elico-corp.com

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
<big>Eric CAUDAL</big> --
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Enapps :: Vadim Chobanu
Eric CAUDAL

Thats great, thanks!

 

Vadim

 

From: Openerp-community [mailto:[hidden email]=[hidden email]] On Behalf Of Eric Caudal
Sent: 21 January 2014 08:27
To: openerp-community
Subject: [Openerp-community] New Intercompany Process Modules for OpenERP

 

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.

 

What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon

 

Looking forward to your feedback!

/**/ --

Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com
 

Elico Corp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Numérigraphe
In reply to this post by Eric Caudal - www.elico-corp.com
Great news, and a lucky timing for our own projects. Congratulations!
May I ask if both companies can/must be in separate databases?
Lionel Sausin

Le 21/01/2014 09:27, Eric Caudal a écrit :

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback!
<big>Eric CAUDAL</big> --
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Eric Caudal - www.elico-corp.com
For the moment they are in the same database but we plan to extend the backend so that they can communicate from different databases via XMLPRC. It is not complicated but we didnot have the need yet...
Some reporting will be added to the core with a clear logging of the different operations.
Eric CAUDAL
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico
          Corp
On 01/21/2014 04:45 PM, "Lionel Sausin, de la part de l'équipe informatique Numérigraphe" wrote:
Great news, and a lucky timing for our own projects. Congratulations!
May I ask if both companies can/must be in separate databases?
Lionel Sausin

Le 21/01/2014 09:27, Eric Caudal a écrit :

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback!
<big>Eric CAUDAL</big> --
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Thorsten Vocks
In reply to this post by Eric Caudal - www.elico-corp.com
Dear Eric (ElicoCorp),

congratulations! 

I like that you show openerp-connector can be used for more than e-commerce connectors.
Your modules seems to add essential missing functionality in multi-company standard setup.

Thank you very much.


Thorsten Vocks

openBIG.org
Web: http://www.openbig.org         


2014/1/21 Eric Caudal <[hidden email]>

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Bidoul, Stéphane
In reply to this post by Eric Caudal - www.elico-corp.com
Thanks for this contribution, Eric!

-sbi


On Tue, Jan 21, 2014 at 9:27 AM, Eric Caudal <[hidden email]> wrote:

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Pedro Manuel Baeza Romero
Wow, Eric, ¡¡excelent work!!

I think these modules should go directly to OCA repository https://launchpad.net/multi-company, don't you think?

Regards.


2014/1/21 Bidoul, Stéphane <[hidden email]>
Thanks for this contribution, Eric!

-sbi


On Tue, Jan 21, 2014 at 9:27 AM, Eric Caudal <[hidden email]> wrote:

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Eric Caudal - www.elico-corp.com
I can prepare a merge proposal for tomorrow indeed!

Eric CAUDAL
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico
          Corp
On 01/21/2014 09:47 PM, Pedro Manuel Baeza Romero wrote:
Wow, Eric, ¡¡excelent work!!

I think these modules should go directly to OCA repository https://launchpad.net/multi-company, don't you think?

Regards.


2014/1/21 Bidoul, Stéphane <[hidden email]>
Thanks for this contribution, Eric!

-sbi


On Tue, Jan 21, 2014 at 9:27 AM, Eric Caudal <[hidden email]> wrote:

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback!
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a moz-do-not-send="true" href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Pedro Manuel Baeza Romero
Thank you! I will review it with one real case.

Regards.


2014/1/21 Eric Caudal <[hidden email]>
I can prepare a merge proposal for tomorrow indeed!


Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico
          Corp
On 01/21/2014 09:47 PM, Pedro Manuel Baeza Romero wrote:
Wow, Eric, ¡¡excelent work!!

I think these modules should go directly to OCA repository https://launchpad.net/multi-company, don't you think?

Regards.


2014/1/21 Bidoul, Stéphane <[hidden email]>
Thanks for this contribution, Eric!

-sbi


On Tue, Jan 21, 2014 at 9:27 AM, Eric Caudal <[hidden email]> wrote:

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback!
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com

Elico Corp

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp





_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

jeff.wang-2
In reply to this post by Eric Caudal - www.elico-corp.com
Great module with great document, Thank you Eric !

------------------
Jeff Wang |  [hidden email] | 18016291663 | 02158980787
@OpenERP_Jeff "As simple as possible, As complex as needed"
Maintainer of Open ERP china community 
http://www.openerp-china.org
 


------------------ Original ------------------
From:  "Eric Caudal";<[hidden email]>;
Date:  Tue, Jan 21, 2014 04:27 PM
To:  "openerp-community"<[hidden email]>;
Subject:  [Openerp-community] New Intercompany Process Modules for OpenERP

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Joël Grand-Guillaume @ camptocamp
Thanks a lot Eric, that is a very much appreciated contribution :) ! And I wouldn't have done it differently, this is an amazing great job !


On Tue, Jan 21, 2014 at 4:42 PM, jeff.wang <[hidden email]> wrote:
Great module with great document, Thank you Eric !

------------------
Jeff Wang |  [hidden email] | 18016291663 | 02158980787
@OpenERP_Jeff "As simple as possible, As complex as needed"
Maintainer of Open ERP china community 
 


------------------ Original ------------------
From:  "Eric Caudal";<[hidden email]>;
Date:  Tue, Jan 21, 2014 04:27 PM
To:  "openerp-community"<[hidden email]>;
Subject:  [Openerp-community] New Intercompany Process Modules for OpenERP

Based on the new OpenERP connector, Elico Corp has created a new set of modules that makes Intercompany Process (ICOPS) ready in minutes.


What is Intercompany Process?

It is the possibility to automatically create objects from one company (Origin) into another one (destination). Main intercompany process operations involve SO, PO, stock moves and invoicing.

In multi-company environment, a SO to a sister company needs to be reflected as a PO in that company: the objective of these modules is to make transparent the creation of the necessary duplicated documents.

You can  have a look at the following blueprint: https://blueprints.launchpad.net/multi-company/+spec/icops

What do you need to get started:

  • Multi-company products, visible in all the companies involved in the process
  • 2 companies: one origin and one destination
  • 2 backends linked to each company involved in the communication
  • one user in each company able to perform the actions (to be setup in the backends).
  • Setup the back end to perform the requested action, depending on the events.

Necessary Modules:

  • Standard OpenERP Modules
  • openerp-connector modules (http://openerp-connector.com/)
  • base_intercompany: this is the main module with all generic methods, adapters, mappings etc.
  • base_intercompany_sale: this is the module for sales/purchases intercompany process
  • base_intercompany_stock (planned): this is the module for stock intercompany process
  • base_intercompany_invoicing (planned): this is the module for invoicing intercompany process

How to test it?

  1. Create a demo database
  2. Install the module base_intercompany_sale
  3. Go to connector/ backend and create the setup in Backend Origin (eg PO to SO: create, update, delete and confirm)
  4. Connect to Origin company
  5. Create a PO to the Destination company with products and save it
  6. Connect to Destination company
  7. Check that a SO has been created

Here are the current working patterns:

  • SO 2 SO: a SO created in company A will automatically create a SO in company B
  • DO 2 DO: The DO created in company A will automatically create a DO in company B (subcase of SO to SO)
  • SO 2 PO: a SO created in company A will automatically create a PO in company B
  • PO 2 SO: a PO created in company A will automatically create a SO in company B

Patterns planned in the future (community contribution accepted!):

  • PO 2 PO: a SO created in company A will automatically create a SO in company B
  • IS 2 IS: The IS created in company A will automatically create a IS in company B (subcase of PO to PO)
  • CI 2 SI: a CI created in company A will automatically create a SI in company B
  • SI 2 CI: a SI created in company A will automatically create a CI in company B


You can configure the following events to perform an action in the destination company:

  • Creation of objects
  • Update of the objects
  • Deletion of the objects
  • Cancel (equivalent to press button Cancel)
  • Confirm (equivalent to press button Confirm or Validate)

The functionality has been built on the openerp-connector  and provide the following features:

  • Possibility to enqueue all jobs
  • Queue Error management
  • By default no delay is setup in current module (no job queue)

Notes:

  • Patterns are generic and behaviors are transitive: you can have multiple company involved with several cascade up and down.
  • You can setup complex rules such as creating the object in one company and confirmation in the other.
    • Company Origin (to Destination): SO2PO (Create, update, delete but no confirm)
    • Company Destination (to Origin): PO2SO (only confirm)
  • A video will be posted soon
 
Looking forward to your feedback![hidden email]
--
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner 
Cell: <a href="tel:%2B%2086%20186%202136%201670" value="+8618621361670" target="_blank">+ 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
[hidden email]
http://www.elico-corp.com


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp
Reply | Threaded
Open this post in threaded view
|

Re: [Openerp-community] New Intercompany Process Modules for OpenERP

Guewen Baconnier @ Camptocamp
In reply to this post by Eric Caudal - www.elico-corp.com
On 01/21/2014 09:27 AM, Eric Caudal wrote:
>
>       Based on the new OpenERP connector, Elico Corp has created a new
>       set of modules that makes Intercompany Process (ICOPS) ready in
>       minutes.
>

Congratulations! This is a step forward for the Connector framework and
the intercompany processes.

I added a link on the http://openerp-connector.com/ page.

Best,

--
Guewen Baconnier
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 39
Office: +41 21 619 10 10
http://www.camptocamp.com/

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [hidden email]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp