You can add containers to an existing manifest or add to a new manifest after packing it.
To add containers to a manifest:
If the item is serial-tracked or if the serial number is not captured during the pick or pack process, capture the item's serial number. For more information about capturing the serial number, See the section, "Capturing the Item's Serial Number".
To customize the manifest station:
Problem
The system does not automatically generate the tracking number and freight charges for a manifested container.
Cause
No records are found for parcel carrier preferences pertaining to the node.
Resolution
In the Applications Manager, add parcel carrier preferences to a node, and also enter the node's shipping account number associated with the carrier. For more information about parcel carrier preferences, see the Defining a Node's Parcel Carrier Preferences in the Configuring system-wide settings.
Problem
An error message, "No record found in YFS_FREIGHT_TERMS table" occurs.
Cause
The freight term is not configured for your Enterprise.
Resolution
Configure the freight terms for the Enterprise. For more information about configuring freight terms, see the section Creating a Freight Term in the Configuring Sterling Logistics Management.
You cannot add containers to a manifest that is in "Closed" or "Requested for Closure" status.
Cause
The system does not allow to add containers to a manifest that is in "Closed" or "Requested for Closure" status.
Resolution
Add containers to a manifest that is in "Closure Failed" or "Open" status.
Problem
An error message, "NMFC data is not set up for the item" occurs.
Cause
The NMFC code does not exist for the item.
Resolution
Enter the item's NMFC code. For more information about defining product item's classifications, see the Defining a Product Item's Classifications in the Catalog Management: Configuration Guide.
Problem
An error message, "Shipping Account No not set up for the carrier" occurs.
Cause
A. The Shipping Account number is not configured for the Parcel Carrier of the shipping node, OR
B. The Shipping Account number is not configured for the Carrier of the Buyer.
Resolution
A. If the Freight Terms on the shipment is Prepaid, configure the Shipping Account number for the Parcel Carrier of the shipping node. For more information about defining the parcel carrier preferences of the node, see the section Defining a Node's Parcel Carrier Preferences in the Configuring system-wide settings.
B. If the Freight Terms on the shipment is Collect, configure the Billing Account number for the Carrier of the Buyer. For more information about defining the carrier preferences of the buyer, see the section Defining Carrier Preferences Parameters in the Configuring system-wide settings.
Problem
An error message, "Class not found exception" occurs.
Cause
The ycsbe.jar file is not included in the classpath environment variable.
Resolution
Include the ycsbe.jar file in the classpath and restart the Application Server.
Problem
Using a weighing scale you cannot capture the package's weight.
Cause
The weighing scale is not integrated with the system, the weighing scale's power is off, or the weighing scale is configured incorrectly.
Resolution
Make sure that the weighing scale is integrated with the system, the weighing scale's power is on, and the weighing scale is configured correctly.
You cannot print a FedEx label for a package that is manifested.
Cause
The printer may not be connected, the printer power or green light may not be on, or the printer that you want to print to is selected incorrectly.
Resolution
Make sure your printer is connected, the printer power or green light is on, and select the correct printer that you want to use.
Problem
While scanning a package to manifest, an error message pops up.
Cause
The problem is related to FedEx Powership limitations.
Resolution
See the FedEx Powership guide for a list of error codes and their descriptions.