[18.0][ADD] edi_purchase_diapar_oca

[P-H-Phuc]

This module was initially part of the Foodcoop set of addons. We're now migrating it to 18.0 and taking this occasion to contribute it to OCA.

[nguyenminhchien]

• Check the analysis from Thien: https://tms.trobz.com/web#cids=1&id=66037&menu_id=424&model=tms.forge.ticket&view_type=form
• There're 3 modules: edi_purchase_diapar, edi_purchase_base edi_purchase_config. You could consider to merge/rename them to adapt with the existing modules in edi-framework.

[P-H-Phuc]

CONFIGURATION

I. FS Storage

Go to Settings > Technical > FS Storage

• Name: Diapar FTP Storage
• Code: diapar_ftp
• Protocol: ftp (FTPFileSystem)
• Options: {"host": "127.0.0.1", "username": "admin", "password": "admin", "port": 5000}

II .EDI Backend Type

Go to EDI > Config > Backend types

• Name: DIAPAR
• Code: diapar
• Name: Diapar

III. EDI Backend

Go to EDI > Config > Backends

• Name: Diapar
• EDI Backend type: DIAPAR
• FS Storage: Diapar FTP Storage
• Input pending directory: IN/PENDING
• Input done directory: IN/DONE
• Input error directory: IN/ERROR
• Output pending directory: OUT/PENDING
• Output done directory: OUT/DONE
• Output error directory: OUT/ERROR

IV. EDI Exchange Template Output

Go to EDI > Config > EDI Exchange Template Output

• Name: Diapar Output Exchange Template
• EDI Backend type: Diapar
• Backend: Diapar
• Code: diapar.output.exchange.template
• Output Type: text
• Generator: Qweb Template
• Qweb Template: create new template
• Business params: Vrp Code, Customer Code, Constant File Start / End,...

V. EDI Exchange Type

Go to EDI > Config > Exchange types
1. OUTPUT: PO

• Name / Code: diapar_out_order
• Backend / Backend type?: Diapar
• Direction: Output
• Enabled for partners: Select partners...
• Filename pattern: edi.config.system.po_text_file_pattern
• File ext: C99
• Encoding: iso-8859-1

2. INPUT: BLE (Despatch Advice)

• Name / Code: diapar_in_despatch_advice
• Backend / Backend type: Diapar
• Direction: Input
• partner_ids: Select partners...
• Filename pattern: BLE*
• File ext: txt
• Encoding: iso-8859-1
• Advanced Settings:

components:
    process:
        usage: input.process.diapar.purchase.price
        env_ctx:
            msg_type: 'Purchase Price'

• INPUT: Purchase Price (CH)
  • Name/Code: diapar_in_purchase_price
  • Backend: Diapar
  • Direction: Input
  • partner_ids: from edi.config.system.supplier_id
  • Filename pattern: CH*
  • File ext: txt
  • Encoding: iso-8859-1
  • Advanced Settings:

components:
    process:
        usage: input.process.diapar.purchase.price
        env_ctx:
            msg_type: 'Purchase Price'

VI. EDI Configuration

Go to EDI > Config > Configurations

• Name: Diapar Purchase Order
• Backend: Diapar
• Exchange Type: diapar_out_order
• Trigger: On record write
• Model: Purchase Order
• EDI Config Do:

if record.state == 'purchase':
  record._edi_send_via_edi(conf.type_id)

VII. Vendor

Open Vendor form > EDI > Purchase > Select EDI Configure Diapar Purchase Order

[nguyenminhchien]

• I cannot test the module
• When creating new product supplierinfo, i faced this error:

• When creating new PO without supplierinfo, i faced this error:

• Add unit tests please.
• Create demo data following your guideline

[nguyenminhchien]

only apply this constraint to edi supplier

[nguyenminhchien]

Admin user faced this error: