Skip to content

Step 9 – Order Status Feedback File

The integration now writes orders into Sage 300, but the system that sent them cannot tell what happened to them. In this step you add a CSV file that lists each incoming order id against the order number Sage 300 allocated it. Step 10 uploads the file.

The file holds the same pairs as the audit summary in step 8.

Design > Transform Setup

  1. Open the Writers group in the palette and drag a CSV Writer onto the design surface, to the right of the Sage 300 order connector.
  2. Drag a Connector from the Transforms group and join the order connector to it.

  3. Save the integration.

    The design surface with a CSV Writer added at the end of the order branch, joined to the Sage 300 order connector

A transform cannot be opened until the integration is saved

Save before you go further. You cannot open a newly dropped transform until you save the integration. Double-clicking it does nothing, and no message says why.

Writer > Setup

Double-click the writer to open it.

  1. Transform Id
    • It arrives called CSV Writer. The audit report uses this name.
    • For training, enter: CSVWRITE
  2. Target
    • Where the output goes. For training, leave as: File
  3. File System
    • For training, leave as: Windows
  4. File Path
    • The folder the file is written to.
    • For training, enter: C:\IMan\OutputData
  5. Evaluate FileName
    • Whether File Name is a literal name or a formula.
    • For training, tick it.
  6. File Name
    • For training, enter: "OrderStatus" & Format(Date, "yyyymmdd") & ".csv"
  7. Encoding Method
    • For training, leave as: Unicode (UTF-8) (utf-8)
  8. Overwrite Existing File
    • For training, tick it.

The CSV Writer's Setup tab with the transform id, file path, the evaluated file name formula and the encoding method filled in

Tick Evaluate FileName before typing the file name

Tick Evaluate FileName before you type the file name. The steps above follow that order.

Ticking it replaces the plain File Name text box with a formula editor and discards whatever was in the box. If you fill in the name first, it disappears with no warning and the writer has no file name.

The folder in File Path must exist. Auto-Create Folder, further down, creates it if it does not. For training, create C:\IMan\OutputData yourself and leave that option unticked.

Writer > Setup — the output format

The rest of the tab controls what the file looks like. Scroll down to Options.

  1. Field Delimiter
    • The character between values. For training, leave as: ,
  2. Line Delimiter
    • For training, leave as: Windows Carriage Return & Linefeed (CRLF)
  3. Quote Text Fields
    • Whether text values are wrapped in quotes. For training, leave as: NoQuotes
  4. Write Header Rows
    • Writes the field names as the first line of the file, so the file describes its own columns. It is not on by default.
    • For training, tick it.
  5. Create File When No Data
    • For training, leave unticked. A run that imported no orders should not leave an empty file for the other system to collect.
  6. Generate File Per Transaction
    • One file per transaction instead of one per run. For training, leave as: (none)

The Options section of the CSV Writer with the field and line delimiters, Quote Text Fields set to NoQuotes and Write Header Rows ticked

Writer > Field Mapping

By default the writer exports everything the connector passes on. Here that is the whole order header, but the file needs only two columns.

The fields are listed under their Sage 300 names

The fields are listed under their Sage 300 names, such as REFERENCE and ORDNUMBER, not the names the spreadsheet used. The connector renamed them, as described in step 7.

  1. Press the Field Mapping tab and check that OE0520 is the current transaction.
  2. Press Edit, then Deselect All Fields and confirm.
  3. Tick Export against REFERENCE and ORDNUMBER only.

  4. Save the grid with the green tick.

    The writer's field mapping for OE0520 in edit mode, with Export ticked against REFERENCE and ORDNUMBER and clear against every other field

  5. Change the current transaction to OE0500 (the order lines). Press Edit, then Deselect All Fields and confirm. Nothing from the lines goes into this file.

  6. Save the grid, close the writer and save the integration.

Running it

Press Refresh on the writer. IMan writes the file as the preview runs, so it appears in C:\IMan\OutputData immediately:

OrderStatus20260812.csv
REFERENCE,ORDNUMBER
FBRN-309242,ORD000000041743
FBRN-309243,ORD000000041744
FBRN-309244,ORD000000041745

The first line is there because you ticked Write Header Rows. The file name carries the run date because Evaluate FileName made the name a formula.

Refreshing the writer writes another three orders into Sage 300

Refreshing the writer runs everything upstream of it, including the Sage 300 order connector. Every press writes another three orders into Sage 300, as described in step 7. Your order numbers will differ from the ones in the file above.

Step 10: FTP Upload >