Output Processing for Shipments 

Use

The system uses this process to control the output (printout and IDocs) of the data collated during output determination.

During message processing of the shipment, the creation of spool requests or IDocs is dependent on the shipment status. In the Customizing table for the DSD output types, you enter the minimum shipment status required for the system to be able to process the message successfully. If the shipping status differs from the value defined in Customizing, output processing is aborted with a corresponding note in the processing log with status Incorrect Processing.

For each sales document object there is a fixed assignment to an application in the system. In Output Control, message control for the shipment is based on application V7 (shipment).

Prerequisites

If the system is to use output processing for the download (printout and IDoc) during shipment, the following conditions must be satisfied:

...

       1.      Printout and IDoc: The output types must be defined.

When creating output types for the download you must make the following settings:

§         The Condition Access indicator must be set.

§         If the system is to create a change message after a download has been completed for a change in the shipment, the Multiple Transmission indicator must be set.

 

       2.      Printout and IDoc: The minimum shipment status that the system requires for the download must be defined.

You define the shipment status in the Customizing table of the download output types.

 

       3.      Printout: For each shipment type and per transportation planning point, it must be defined which individual messages the system should print and in which order.

By default, the system groups all documents together in a spool request. If the system is not to transfer the print output of a message to the printer for the triggering DSD message, set the Different Printer indicator in Customizing. The print output then continues, based on the printing settings of the individual messages to be printed. This is necessary if, for example, one of the documents (for example, delivery note) must be printed on a separate printer because of the different paper format.

The system creates a processing log for each shipment in which the processed messages for each document, and any errors that have arisen are logged. If errors occur during processing of an individual message, the system logs the error in the processing log for the individual message.

 

       4.      IDoc: For each shipment type and transportation planning point, it must be defined which IDocs the system should create and with which function modules.

Features

Print Output

·        In Customizing, for each shipment type and transportation planning point, you can define which individual messages the system should process sequentially for the relevant application. The system begins by processing the individual message as soon as it processes the output type relevant for the download.

·        Documents for which the system should create a printout are determined by the system from the shipment document flow.
The system determines which visit list is assigned to a shipment using the header reference documents for the visit list, because visit lists are not saved in the document flow.

IDoc Creation

·        In Customizing, you can define for each shipment type and transportation planning point which IDocs the system should create and with which function modules.

·        Documents for which the system should create an IDoc according to output type are determined by the system from the shipment document flow.
The system determines which visit list is assigned to a shipment, using the header reference documents for the visit list, as visit lists are not saved in the document flow.