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

[Łukasz Nowak]

Hello,

Jérôme Perrin napisał(a):
(...)

>> 1. Is my path correct and upstream acceptable?
> 
> In theory it is not needed, InvoiceTransactionRule_asCellRange contains:
> 
> dimension_list.extend([ pred.getStringIndex()
>             for pred in context.objectValues(portal_type='Predicate')
>             if pred.getStringIndex() not in dimension_list ])
> 
> I saw a bug in Predicate_getMembershipCriterionCategoryList, it only supported 
> destination_region, and this has been broken recently, so it maybe the reason 
> of your problem. I repaired it and added support for source_region in r13723 
> (and more cleanly in r13724). And also source_region was not cleanly 
> configured (r13729).

Ok. I've merged my implementation with that fixes. Thanks.

>> 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"?
> 
> Yes, put all together in the same matrix and make a dimension with some 
> predicates with method id ( a script Movement_explanationPortalTypeIsSale 
> exists for this) to make this dimension only for sale or purchase.

Wow! That's what I was looking for. Right now all simulations are 
creating well, and I'm able to set proper rules for accounting.

As soon as I test it I'll try to write some text about it.

Thank you very much!
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...''