Custom EDI

The Custom EDI option allows StarShip to work with EDI solutions for which there are no out-of-the-box integrations. This option provides shipment details in real-time via a file. The EDI solution simply needs to consume the file to create the ASN and automate the workflow.

Custom EDI also supports generating the ASN number if this needs to be assigned during the shipping process for printing on labels or uploading to carriers. In this case, the ASN number will be included along with all the other shipment detail in the EDI file.

This topic shows you how to set up Custom EDI options.

Custom EDI Settings

Select Setup > Preferences > EDI and then click Custom EDI.

Enable Custom EDI

Check the “Enable Custom EDI integration” option.

For EDI shipments, activate Custom EDI integration

• Manually: This option allows the user to manually check (or uncheck) Custom EDI in the Recipient > EDI Integration in the Shipment Editor.
• Conditionally: This option allows you to add conditions under which your custom EDI solution will be used for EDI shipments. When conditions are met, StarShip will automatically check the Custom EDI check box under Recipient > EDI Integration in the Shipment Editor. Note that when this field is set to Conditionally, the user cannot manually check the Custom EDI check box while shipping. See Activation Conditions for more information.

Generate ASN in StarShip

When checked, StarShip automatically generates the ASN number for any shipment where custom EDI is activated. If this option is not checked, StarShip will not generate the ASN number. It can be typed in manually in the Recipient > EDI Integration section in the Shipment Editor or mapped to an ERP or other source interface field.

Generate EDI file

When this option is checked, the EDI file is created on Ship/Process in the Shared EDI folder location. If the path is unavailable, StarShip will create an EDI\Custom EDI\ folder to contain the EDI file.

ASN Type

Select the type of ASN required by your Trading Partner. You can select from:

• Always use “Pick and Pack”: StarShip generates the file read by the Custom EDI provider to create the ASN in this format: Shipment > Order > Pallet > Pack > Item. “Pick and Pack” allows items of mixed types to be packed into the same container.
• Always use “Standard Pack”: StarShip generates the file read by the Custom EDI provider to create the ASN in this format : Shipment > Order > Pallet > Item > Pack. “Standard Pack” allows only one item type to be packed into any given container.
• Use “Standard Pack” when: Allows you to define the conditions under which the Standard format is used. Use the condition builder as described in Set Up Conditions above to add conditions by clicking the Edit button next to the ASN Conditions field.

In order to generate the Standard ASN, a shipment cannot contain mixed line items in any packages. Each line item must have its own package. If two or more line items are placed in the same package, StarShip can only generate the file used to create the Pick and Pack ASN.

EDI File Settings

This option will appear if you have “Generate EDI file” checked above.

EDI XSL Transformation file

You can use your own transformations of StarShip EDI file format. Select the XSL Transformation file or accept the default “CustomEDI.XSL”.

EDI File Prefix

Enter a prefix for the EDI file.

Use XML schema (XSD) to produce EDI file

Check to use the XML schema (XSD) to create the EDI file.

Activation Conditions

This section helps you define conditions for Custom EDI activation. When you set conditions, the Custom EDI integration can only be activated when these conditions are met. The Custom EDI check box will be disabled in the Shipment Editor and more info is available to the user about why the field is disabled.

Conditions are a number of field values (operands) connected by operators. They can be based on:

• Constant Values: These are fixed values that you define. You can add a Constant Value by selecting New Constant Value from the drop-down list. Values you already created are also saved to the drop-down list.
• StarShip Fields: These are fields from the Ship screen (shipment fields).

Set Up Conditions

1. Click the Edit button next to the “Activation conditions” field to add conditions.
2. On the Conditions Builder dialog, click the “+” button to add a condition.
   
3. Select a Shipment field value as the first operand. Let’s say we want to use the Billing Type shipment field value to trigger integration with Custom EDI. You can also type a field name into Search field to narrow down the list of fields that are displayed in the drop-down.
   
4. Select an operator, for example “contains” or “is equal to”. Here we are choosing “is equal to” since we want to Custom EDI to be activated for a specific billing type.
5. Choose a second operand, which can be either a Shipment value or a Constant value. In this example, we’ll select “Third Party”.The second operand can also be a constant value, depending on the shipment field selected. In some cases, you can also select whether the condition applies to each order or package (Pack) in the shipment or at least one order or package in the shipment. Basically, what is available in the second operand list will depend upon the field you select as the first Operand.

Multiple Conditions

Set Conditionally to Always

To always enable the Custom EDI integration check box, open the Conditions Builder and then click OK without adding any conditions. When you return to the Preferences screen, you will see the “Activation conditions” field set to “ALWAYS”.