Add Containers to a Manifest

About this task

You can add containers to an existing manifest or add to a new manifest after packing it.

To add containers to a manifest:

Procedure

  1. From the navigation bar, select Outbound > Add to Manifest. The Add To Manifest screen is displayed.
  2. In Station, select the station from the drop-down list where you are manifesting the containers.
  3. In Scan Identifier, enter or scan the container SCM that you want to add to the 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".

  4. Enter other information in the applicable fields.
  5. Click Add to Manifest.
    Note: Save the container's information and packing notes entered (if any) before manifesting.
    Note: You can customize the manifest station to perform generic status changes on a container.

    To customize the manifest station:

    • Define the custom pipeline by extending the default pipeline associated with a transaction ID. For more information about configuring process models, see the Configuring system-wide settings.
    • Extend the existing resource and modify the JSP to contain JSP=/wms/wmsmanifest/detail/exuimanifest_detail_anchor. jsp?TransactionId=<TransactionId>. For more information about defining or extending resources, see the Configuring system-wide settings.
    • Create a Menu Entry for the newly created resource and use the new screen to perform a generic status change. For more information about defining menus, see the Configuring system-wide settings.
    Note: The Tracking Number and Freight Charges are not getting generated while manifesting

    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.

    Note: An error message, "YDM00166 - No record found in YFS_FREIGHT_TERMS table" pops up

    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.

    Note: Problem

    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.

    Note: An error message "YCS00006 - NMFC data is not set up for the item" pops up

    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.

    Note: An error message, "YDM00171 - Shipping Account No not set up for the carrier" pops up

    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.

    Note: An error message, "Class not found exception" pops up

    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.

    Note: Capturing Weight using the Weighing Scale

    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.

    Note: Problem

    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.

    Note: Error while Manifesting

    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.