StarShip allows you to customize the way data is translated between Sage 300 documents and the StarShip shipment. Using the field mapping feature, you can control how the data in the source document is translated to StarShip, allowing you to define what information populates the shipment fields, and how the data is interpreted into accepted shipment values, when necessary.
How to Access Field Mapping
- To access field mapping, go to Setup > Source Interfaces > Sage 300 (version), and click the Interfaces heading.
- Select the Customize Interface button for the source document.
- Then, click the Select Mappings heading.
Many fields from Sage 300 are mapped by default as part of the basic interface. If you want more control over how data is translated from Sage 300 into shipment fields, you can add fields or customize field mapping to suit your company’s needs. For any information that you want imported with the Sage 300 source documents, you can map those fields to StarShip shipment fields and when applicable, set up value translations.
If you want to import a field that doesn’t have a corresponding field in StarShip, you can use StarShip User Definable fields and map your Sage 300 field to one of them. Mapping User Definable fields to Sage 300 fields allows you to bring in values that may not normally be imported with the source document.
You can map any field in StarShip, but let’s look at a few common examples.
Ship Via is an example of a field that is mapped by default, but which requires you to set up value translations for the most accurate results. Although the field is mapped, you now need to define what the Sage 300 Ship Via methods mean in StarShip terms. For example, the Sage 300 Ship Via field value “AM” can be set up to translate to “FedEx 2Day® A.M.” when the source document is imported into StarShip. When the source document Ship Via is “AM”, the Carrier/Service fields on the Shipping screen will automatically populate with “FedEx 2Day® A.M.”.
The Sage 300 values are populated from Ship Via field values that are set up in Sage 300.
Expand Shipment > Carrier Information > Carrier – Service. For each of the Sage 300 Ship Via values In the Value Translations list, select or add the corresponding StarShip Carrier – Service value from the drop-down list.
Map a Field to a Fixed Value
You can set a fixed value for any mapped shipment field. You can either type in a value or choose one of the possible shipment values from a drop-down list. If the shipment field says (Select) next to it, then the fixed value will be either selected (checked) or not (unchecked).
Map a Field to any Sage 300 field
Select a field from the Sage 300 document as the mapped source for the corresponding StarShip field.
In the “Maps from” field, select Sage 300 Field and then choose the Sage 300 field to map to.
Map a Field to a Sage 300 field with Value Translations
This example illustrates an StarShip field that requires a set of possible values. Here is the StarShip “FOB” field that we map to the Sage 300 field “Terms”. You’ll see that an area for Value Translations becomes available. Click Add Value Translation.
Enter the values from Sage 300 and then select the StarShip value that they should translate to.
Map to a User Definable field
StarShip provides User Definable fields at the Item, Order, Packaging, Pallet and Shipment levels. Although it is possible to map StarShip User Definable fields to different level source fields, we recommend that you only map User Definable fields to the same level fields from Sage 300.
- Create the StarShip User Definable fields.
- In Select Field Mappings, locate the User Definable field. User Definable fields are noted by a (UDEF) after the field name you created.
- Select Maps from “Sage 300 Field” and then select the field to map to.