Most Powerful Open Source ERP

Technical Note on Property Sheets

ERP5 Documentation Technical Note showing arrow explanation
  • Last Update:2016-04-22
  • Version:001
  • Language:en

Many documents in ERP5 are described using special vector, defined in Arrow property sheet. Few words about those vectors are in FaqOnCoreModel, here is document oriented arrow explanation.

/!\ Same source and destination is not supported. Sometimes it will not generate movements (like for Sale Order) sometimes it will break simulation system (like for wrongly defined Supply Chain in MRP). Same applies to section and others variations of arrows.

{i} TODO: trade, function, project, transport (?= shipper), advice, region (virtual) variations

Table of Contents

Orders and Packing Lists

Sale/Purchase Order/Packing List:

  • source:
    • physical location from where goods are moved
  • destination:
    • physical location to where goods are moved
  • source_section:
    • entity, which is selling goods
  • destination_section:
    • entity, which is purchasing goods
  • source_decision:
    • entity, which is responsible for accepting order
  • destination_decision:
    • entity, which is responsible for sending order
  • source/destination administration:
    • not used / do not known?
  • source/destination payment (not sure):
    • parties involved in payment

Accounting Transactions: Purchase and Sale Invoice, Payment and Accounting Transaction

  • source/destination:
    • not needed, no influence on simulation system
  • source_section:
    • entity, which will send cash
  • destination_section:
    • entity, which will receive cash
  • source_administration:
    • entity, which is responsible for issuing document
  • destination_administration:
    • entity, which is responsible for receiving document
  • source/destination decision:
    • not used / do not known?
  • resource (it shall not be here, but explains something):
    • price currency of document, acquired by transaction lines
  • source_reference (it shall not be here, but explains something):
    • source entity reference of document, for Sale Invoice Transaction so called invoice number
  • destination_reference (it shall not be here, but explains something):
    • destination entity reference of document, for Purchase Invoice Transaction so called invoice number
  • source/destination payment (not sure):
    • parties involved in payment

Accounting Transaction Line

  • source:
    • account, from which cash is sent
  • destination:
    • account, to which cash is sent
  • source/destination section:
    • same as on accounting documents

Related Articles