Creating Shipments with Collective Processing 

Procedure

  1. From shipment, choose Create ® Collective Processing.

    A screen appears on which you can define how the collective processing for the creation of shipments should be carried out.
  2. Enter which kind of shipments (inbound or outbound) you want to create in the Default settings section.

    Among other things, this entry controls which selection variants you can use to choose deliveries. One of the variants that is used to select inbound deliveries may not be used for outgoing shipments, for example.
  3. Enter which outbound (or inbound) deliveries are to be processed in this collective shipment in the Select deliveries section of the screen.

    You can also enter the name of a selection variant that you may have already created, for example, for the creation of individual shipments (transaction VT01). You can either enter the name of this selection variant here or choose it from the list of possible entries in input help. You can display and change the content of this variant by choosing Maintn (to the right of the field).

    You may also create a new variant. Simply enter the name of the new variant and choose Maintn. The selection screen for selecting deliveries then appears. Specify the criteria according to which you want to select deliveries. For example, you would enter here that all deliveries that have route
    000001 (north route) or 000002 (west route) should be selected.

    The Selection variant field is a mandatory entry field and therefore must contain a name.
  4. Enter the rules according to which the selected deliveries should be divided into shipments in the Grouping criteria field in the Rules section of the screen.

    As with the Selection variants field (see point 3), you can enter the name of a variant that defines the rules for grouping deliveries into shipments in this field. For example, you could specify that all deliveries with the same shipping point and route should be grouped together into one shipment. You can further specify that these deliveries are to be sorted according to the ship-to party’s zip code and that the shipment may weigh no more than 30 tons.

    The Grouping criteria field is optional. If it is left blank, all deliveries that are selected are assigned to one shipment.
  5. In the Data and options field in the Rules section of the screen, you can specify which data should be found in the shipment documents you create (transportation planning point, shipment type, service agent, route, etc.) and which functions should be carried out (leg determination, set status to planned, etc). As with the other fields, you must either enter the name of a variant or create a new variant here.

    This field is a mandatory entry field and therefore must be filled in.
  6. Enter whether or not the system should save the shipment if errors or warnings occur in the Save created shipments part of the screen.
  7. Some errors prevent a document from being created. For example, you cannot create a document with a shipment type that does not exist. Other errors or warnings do not necessarily indicate an inconsistent document, but the system indicates that you may want to reconsider creating the document in its current state. For example, you may not want to create the document if leg determination could not be carried out, if the service agent could not be transferred from the delivery or if the maximum weight has been exceeded.
    Indicate here whether the system should save shipments if one of the above-mentioned minor errors occur. If you choose Do not save if warning/error, shipments will only be created when all necessary data was entered (when no corrections are necessary).
    If you choose Do not save if error, a shipment is created in spite of any warnings that occur. As a result, a few corrections may be necessary after the document is created.
    If you choose Simulation (do not save), you are only running a test process to see if errors would occur.
    If you choose Always save data, the document is always saved, even if errors or warnings have occurred. In this case, we recommend that you check the document manually.

  8. Indicate whether you want a log to be created and how detailed it should be on the Log portion of the screen.

    For example, if you indicate that the log should not be saved, it is displayed at the end of collective processing, but disappears after the transaction is finished. Only errors, warnings (invalid service agent, etc.) and important messages ("Shipment 1013 was created") are included in the normal log. The detailed log also contains information about partial functions that were carried out successfully ("Leg determination was carried out," for example). The very detailed version of the log also includes technical information ("Stage with key 1013/0004 was created," for example).
  9. Choose Execute.

Result

The log that lists the collective processing results is then displayed after collective processing has been carried out.