[Erp5-dev] Purchase path of system - from order to invoice - some questions

[Łukasz Nowak]

Hello,

As you know I'm working on purchase path from order to invoice.

I'd like to know how shall I define

With only Sale this was quite easy - I've created some predicates (on 
region in our case), then selected proper regions and expand on Orders 
was great.

With only Purchase - it is similar (after patching with 
InvoiceTransactionRule_asCellRange-source_region_patch.diff, which 
allows me to select source_region on Predicates) I was able to create 
good purchase invoices.

Questions:

1. Is my path correct and upstream acceptable?
2. How shall be default_invoice_transaction_rule, which will be able to 
support Purchase and Sale invoices? I've seen that putting together 
destination_ and source_ region do not work. Shall I them put into same 
matrix? What would be "the Nexedi way"?

When I'll now how to mix auto generation of Purchase and Sale Invoice 
Transaction objects and lines in "the Nexedi way", then I'll be able to 
write unit tests for such configuration and (maybe) put such extension 
upstream.

Well, I'm going back to experiments, thanks for any clues and suggestions,
Luke

-- 
Łukasz Nowak R&D Ventis http://www.ventis.com.pl/
tel: +48 32 768 16 85 fax: +48 32 392 10 61
``Use the Source, Luke...''
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InvoiceTransactionRule_asCellRange-source_region_patch.diff
URL: <http://mail.tiolive.com/pipermail/erp5-dev/attachments/20070327/e4cb9dd5/attachment.asc>