Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
moneyworks:edi [2014/12/16 12:13] – [Shipping charges for customers] Adrian Boonemoneyworks:edi [2024/11/26 06:16] (current) – [Notes] Adrian Boone
Line 11: Line 11:
   * The EDI format used by EDI connector contains data for the customer, invoice recipient, buyer and delivery recipient. Currently the buyer is modelled as the customer in MW e.g. "STARK.AA", where the head office has a code of "STARK.". For generating invoices, we have to also lookup and export the GLN/EAN for the head office.   * The EDI format used by EDI connector contains data for the customer, invoice recipient, buyer and delivery recipient. Currently the buyer is modelled as the customer in MW e.g. "STARK.AA", where the head office has a code of "STARK.". For generating invoices, we have to also lookup and export the GLN/EAN for the head office.
   * The customer GLN/EAN codes (name.custom1 in MW as name.code has only 11 characters) must be consistent across all systems. When importing an order, MW searches for a match on [Name.Custom1] - import will fail if no match is found.   * The customer GLN/EAN codes (name.custom1 in MW as name.code has only 11 characters) must be consistent across all systems. When importing an order, MW searches for a match on [Name.Custom1] - import will fail if no match is found.
-  * The product GTIN codes ([Product.Barcode] in MW = <detail.stockcode> in XML) must be consistent across all systems - importing an order will fail if no match is found. Note also that [Product.Code] (= [Detail.Stockcode]) in MW translates to <detail.supplierarticle> in XML, [Product.Custom1] (=TUN) in ME translates to <detail.manufacturerpart> in XML, and [Product.Custom2] in MW translates to <detail.buyerpart> in XML+  * The product GTIN codes ([Product.Barcode] in MW = <detail.stockcode> in XML) must be consistent across all systems - importing an order will fail if no match is found. Note also that [Product.Code] (= [Detail.Stockcode]) in MW translates to <detail.supplierarticle> in XML, [Product.Custom1] (=TUN) in MW translates to <detail.manufacturerpart> in XML, and [Product.Custom2] in MW translates to <detail.buyerpart> in XML
   * When importing orders, MW uses the account code of 1000 - import will fail if that account code is missing.   * When importing orders, MW uses the account code of 1000 - import will fail if that account code is missing.
   * The tax rates and tax codes must be consistent across all systems - import will fail if no match is found.   * The tax rates and tax codes must be consistent across all systems - import will fail if no match is found.
Back to top