Event Based Document Control

Outcome

A document is produced when a given event occurs. The document media is defined (printed, sent by mail etc) and also if the document should be produced immediately (synchronous) or sent to a queue and produced later, via an auto start job (asynchronous). The reason for sending the job to a job queue is to gain performance in M3.

EDC can be used in the dispatch flow to produce:

• Picking list
• Address label
• Package label
• Delivery note
• Dispatch advice
• Loading list
• Unloading list

The following files are affected:

• CREVNT – Document Events

  This file contains a list of the events to which documents can be attached for automatic creation and printing.

• MDOCEV – Event Controlled Documents

  This file is used to define that when a given event occurs, and the context matches the stored object values, the defined list of documents/variants will be produced according to the corresponding media definition.

• MDOCEO - Documents to produce for an Event Occurrence

  This file will store all data needed to produce any of the triggered documents for a given event occurrence, when the document is to be produced synchronously.

Before you start

• See the document Settings for Event Based Document Control
• Settings for the dispatch flow must be defined.

Overview

• Various documents can be produced automatically when various events occur, for example
  • Delivery Note when the delivery is issued
  • Address label when Picking Lists are released
  • Loading list when shipment is issued and past deadline

• Documents can be produced using specific media controls
• Documents may be produced synchronously or asynchronously
  • Synchronously means wait until the document has been produced before doing the next task on the computer.
  • Asynchronously means the document will be sent to a queue and produced by an auto start job. The reason for sending the job to a job queue is to gain performance in M3.

    A batch job can also be a part of a mainly interactive job, where the interactive part submits the batch part with specific settings attached to it. The batch job performs in that way as an extension of the interactive environment, to obtain better performance in the time-critical operations

Valid events

• RELEASE_PICK This event occurs when a picking list or group of picking lists is created after a delivery is released for pick. Note that this event may occur more than once depending on the closing point of the delivery. The event applies to pick lists that attain a status of 40= Ready for reporting, or greater for the first time. This means that the event is deemed to have occurred for picking lists going through pick resource planning only after release from pick resource planning. This event occurs after packing has been done.
• DELIVERY_ISSUED This event occurs when the status of a delivery becomes greater than or equal to 60=Delivery fully reported.
• SHIPMENT_ISSUED This event occurs when a shipment is in status 60/60=Shipment reported AND the shipment deadline has passed. That is, when all deliveries within the shipment are fully issued and no more deliveries may be automatically added to the shipment.

Valid documents

The document that may be triggered for each of these events is as follows:

In ‘Event.Open’ (CRS019) you can display all valid events and documents allowed for them.