Output Processing for Visit Lists 

Use

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

During output processing of the visit list, the creation of spool requests or IDocs is dependent on the execution date.

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

Visit lists must be active (Inactive indicator not set), so that output processing creates spool requests or IDocs for the visit list.

 

Prerequisites

The following settings must be entered for output processing of visit lists:

...

       1.      Printout/IDoc: Define output types

¡        The Condition Access indicator must be set.

¡        The Multiple Transmission indicator cannot be set. Only one download takes place for each visit list. Each further download can be requested separately.

¡        By default, the value of the shipping time must be 2 (=job and time information), and a processing routine must be entered in which the shipping time is defined (as a rule the execution date of the visit list).

The download of a visit list (sales-oriented business process) is, as a rule, dependent on the execution date of the visit list. Output processing takes place by means of a periodically scheduled job that processes the due messages and consequently triggers the download.

 

       2.      Printout/IDoc: Output processing only takes place if the visit list to be printed is active.

If this prerequisite is not satisfied, output processing is cancelled. The system displays an appropriate note in the processing log with the status Incorrect Processing.

       3.      Printout: For each visit plan type it must be defined which individual messages the system should print in which order.

By default, the system groups all documents together in a spool request. If the system is not to transfer the printout of a message to the printer of 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.

The system creates a processing log for each visit list in which the processed messages for each document, and any arising errors 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 visit plan type it must be defined which IDocs the system should create and with which function modules.

Features

Print Output

·        In Customizing, you can define for each visit plan type which individual messages the system should process sequentially for a particular 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 from the reference documents in the visit list.

IDoc Creation

·        In Customizing, you can define which IDocs the system should create and with which function modules.

·        The system does not save the visit list in the sales document flow. During output processing from visit list reference documents, the system determines those documents for which an IDoc ist to be created.