Doorgaan naar hoofdinhoud

Send DESADV and INVOIC files

  • Admin

Send DESADV and INVOIC files when your ERP's dispatch advices and invoices should reach a trading partner as EDIFACT messages: your ERP puts each file as XML in a folder on an FTP server, and Hyperfox picks it up, finds the order it belongs to, translates it with the partner's EDI mapping and sends it over AS2 to the partner that placed the order. You set this up on top of the AS2 connection that receives the partner's orders, so set up the AS2 connection first.

Before you begin​

  • The partner's connection shows Active under Admin settings > EDI.
  • An FTP integration under Admin settings > Integrations, on the server where your ERP puts its DESADV and INVOIC files, with one folder for each type.
  • One example XML file of each type you send, as your ERP writes it.
  • Each order in Hyperfox carries the order number your ERP gave it. Hyperfox reads that number from your ERP's response with External ID path on your export profile.

Set up the outbound files on the AS2 channel​

  1. Go to Admin settings > Channels and click Manage (sliders) in the row of the AS2 channel.
  2. Under EDI Outbound > Source, fill in:
    • Integration: the FTP integration of your ERP files.
    • Processed folder: the subfolder of each base folder that Hyperfox moves a file into once it picked the file up. Keep processed unless your partner needs another name. Enter one folder name, without slashes.
  3. Under DESADV, fill in:
    • Base folder: the folder on that server where your ERP puts its DESADV files.
    • Example file: paste the content of your example DESADV file.
    • External ID query, External ID pattern or both: where Hyperfox finds, in each file, the order number your ERP gave the order. External ID query is a JMESPath query over the file, such as Order.Reference. External ID pattern is a regular expression, such as /ORD-(\d+)/. With both, the query runs first and the pattern narrows its result.
  4. Under INVOIC, fill in the same fields for your invoices. To send only one of the two types, leave the Base folder of the other type empty. Hyperfox picks up no files of a type without a base folder.
  5. Switch Paused to Active and click Save. Active starts the pickup of your files. When a field is missing, Hyperfox marks it.

Let Hyperfox generate the partner's DESADV and INVOIC mappings​

Hyperfox generates the partner's DESADV and INVOIC mappings from two sources: the partner's EDI specification for that type and your example file. Save your example files before the partner uploads those specifications in the partner portal.

  1. Ask the partner to upload their DESADV and INVOIC specifications in the partner portal, under EDI Specifications. When the partner uploaded them before you saved your example files, ask the partner to upload them again with Edit EDI Specs.
  2. In EDI, click Manage mappings (list) in the row of the partner.
  3. Check that an Active mapping exists with Document type DESADV and one with Document type INVOIC.

If a mapping is missing or translates a field wrongly, contact Hyperfox support at [email protected] and name the partner.

What happens to a file​

  • Hyperfox picks up every new file in a base folder and moves it into the processed folder.
  • Hyperfox reads the order number from the file with External ID query and External ID pattern, and finds the order in Hyperfox with that number. It sends the file to the partner that placed the order, as an EDIFACT DESADV or INVOIC.
  • When Hyperfox finds no order for a file, or the type has no External ID query or External ID pattern, Hyperfox does not send the file. Correct the channel, then contact Hyperfox support at [email protected] to send the file again.
  • Paused stops the pickup of files. Incoming orders are not affected.

See also​

Laatst bijgewerkt op