Skip to content

Step 7 – Sage 200 SOP Import

Connectors

Connectors perform destructive mapping

A connector changes the dataset it passes on.

Note two things about connectors:

  1. Only the fields you map 'flow' out the other side of a connector. A field you do not map leaves the dataset, and no transform after the connector can use it.
  2. Connectors rename the fields and transaction ids to the internal names used within IMan. Orders becomes SOPOrder, OrderDetails becomes SOPOrderLine, and Sage200OrderNo comes out the other side as DocumentNo.

Design > Transform Setup

  1. Open the Connectors group in the palette and drag a Sage 200 connector onto the design surface.

  2. Drag a Connector from the Transforms group and join the Filter transform to it.

    The design surface, with a second Sage 200 connector added to the end of the row that runs Aggregate, Filter

  3. Save the integration before opening the connector.

Connector > Setup

  1. Double click the connector to open it.

    1. Transform Id
      • Identifies the transform in the audit report. Give this one a name: a second connector is named Connector_1, which means nothing in a report that lists several.
      • For training, enter: OrderImport
    2. Sage 200 Extra Connector
      • For training, choose: Sage200 Demo Data
    3. Sage 200 Extra Import Type
      • For training, choose: SOP Sales Order
    4. Update Operation
      • For training, leave as: Insert

    The connector's Setup tab, with the Transform Id set to OrderImport and the import type set to SOP Sales Order

Connector > Field Mapping — the order

  1. Press the Field Mapping tab.
  2. Make sure Orders is selected in Current Transaction Id.

  3. Choose SOPOrder from Sage 200 Extra Transaction Type.

    The Field Mapping tab with Orders selected and the transaction type set to SOPOrder

The two drop-downs do different jobs

To switch the Field Mapping grid on display, change the top drop-down (Current Transaction Id). Changing the bottom drop-down (Transaction Type) changes the Sage 200 record that the top one maps to.

  1. Press Edit above the grid and set the Sage 200 Extra Field on each of these rows:

    Incoming Field Sage 200 Extra Field
    OrderId Customer Document No
    ShipName Postal Name
    ShipAddress1 Address Line1
    ShipAddress2 Address Line2
    ShipCity City
    ShipCounty County
    ShipPostcode Post Code
    DateTime Document Date
    CustomerNo Customer
    Warehouse Warehouse
    UseInvoiceAddress Use Invoice Address
    OverrideCreditLimit Override Credit Limit
    Sage200OrderNo Document No

    The middle of the field grid, showing the Ship address fields mapped to Postal Name, Address Line1, Address Line2, City, County and Post Code

    • CustomerNo is the account number that Step 4 looked up or generated and Step 5 imported. Sage 200 cannot attach the order to a customer that does not exist.
    • Sage200OrderNo goes in empty and comes back with the order number Sage 200 allocates during the import. That is why Step 4 creates it.

    The end of the field grid, showing Sage200OrderNo mapped to Document No and CustomerNo, Warehouse, UseInvoiceAddress and OverrideCreditLimit mapped to their Sage 200 fields

  2. Press Save above the grid.

Connector > Field Mapping — the order lines

  1. Change Current Transaction Id to OrderDetails, then choose SOPOrderLine from Sage 200 Extra Transaction Type.

  2. Press Edit and map:

    Incoming Field Sage 200 Extra Field
    Qty Line Quantity
    SkuCode Item
    Description Item Description
    UnitPrice Unit Selling Price
    LineType SOPLine Type
    StoredCharge Stored Charge
    StoredValue Charge Value
    Warehouse Warehouse
    • LineType tells Sage 200 whether each line is an item, a charge or a comment, using the values you set in 6.1 and 6.2.
    • Leave OrderId and LineNo unmapped. The lines are already nested under their order, so Sage 200 does not need these fields to know which order they belong to.

    The OrderDetails field grid after saving, with Qty, SkuCode, Description, UnitPrice, LineType, StoredCharge, StoredValue and Warehouse mapped

  3. Press Save above the grid.

Running the import

  1. Press Refresh.

    • When the status reads Progress - Completed, the orders are in Sage 200.
    • Scroll the preview to the right: DocumentNo now carries the Sage 200 order number for each of the three orders. It went in empty.

    The connector preview reading Progress - Completed, with DocumentNo carrying a Sage 200 order number for each of the three orders and Customer carrying the account number

  2. Press Close at the bottom of the transform, then Save the integration.

Your order numbers will not match the screenshots

The order numbers will not match the ones in these screenshots. Sage 200 allocates the next number each time the import runs, and the import has run before.

Step 8: Auditing >