Performing setup tasks common to ACE and ACI

When you pre-validate an EDI 309, 353, or 358 message, ACE or ACI can write the results to a folder on your system. These settings in the TTS50.ini file specify the folder paths:

If you want, you can use a test environment until you are ready to go live with ACE.

ACE:ReceiverID

If you want, you can use an alternate SCAC ID on shipment-level data in ACE and ACI documents. The alternate SCAC code is based on the order’s revenue type. Before activating this functionality, you must determine which revenue type will provide the alternate SCAC ID. In System Administration, access the appropriate label and enter an alternate SCAC ID in the EDI Code field. If you activate this feature but do not make entries in the EDI Code field, the system will use the value from the Abbr field instead.

ACE:AlternateSCAC

This example of the RevType4 label shows applicable reference number options that might be used for eManifest. You view the label in the System Administration label file.

Because there is no entry in the EDI Code field for the Filotrans Container option, the system would use the Abbr field value as the alternate SCAC ID.

The Shipment Control Number (SCN) is a unique number identifying a shipment. You can set up the system to require an SCN at the freight detail level for all ACE and ACI shipments.

Emanifest:EnforceManifestSCN

To use a reference number as a Shipment Control Number, you must record the SCN, ACE, and freightdetail values in the ReferenceNumbers label as shown here.

The shipment control number is a unique number identifying a shipment. You can set up the system to substitute the order number on ACE and ACI documents when a Shipment Control Number (SCN) does not exist for the order.

ACE:BlankDefaultPAPs

When sending EDI 358 or 309 messages, the system checks that stops have Trailer Seal reference types and reference numbers. You can tell the system what to do if they are missing:

[EDIfilesave]AceTrailerSealValidationRule

You may need to send 309 and 358 update messages for previously submitted eManifest. You can set up the system to send them automatically.

Each resource performing ACE trips must have an ACE ID type and number. ACE ID type options are defined in the AceIDtype label. The label is accessed in the System Administration application. You record the resource’s ACE ID type in its profile, using the Additional Information sub window.

Some applications used with eManifest contain the ACE Status field. This read-only field automatically displays the last known incoming 300-series EDI message.

In this example, in the TMWSuite Trip Folder, the ACE Status field appears in the header.

The AceEdiStatus label defines the statuses displayed by the ACE Status field. You can edit this label in the System Administration application. The following illustration shows a partial list of label options. Please check your label file to see all the options available on your system.

eManifest documents require specific reference number types. The ReferenceNumbers label defines these reference number types. You edit this label in the System Administration application.

Edit the ReferenceNumbers label to provide the options shown in the following table.