Performing the Scenario

Prerequisites

In step 1, you created an object type as a sub-type of an existing object type and added an event to its definition. In steps 2 - 9, you set up the creation of the event via Message Control.

The necessary preparations have therefore been made. You will now create a document in this last section of the tutorial. The event created is logged in the event log.

Procedure

Proof of Event Creation: Event Log

Events created are logged in the event log. First make sure that the event log is switched on.

  1. In the workflow area menu for developers (transaction SWLD), select Utilities ® Event log ® On/off.
  2. If necessary, switch the event log on.

Creating a Sales Document

Create a standard order.

  1. Select Logistics ® Sales/distribution ® Sales, then Order ® Create.
  2. Enter TA for standard order in the field Order type.
  3. Enter 0001 in the field Sales organization.
  4. Enter 01 in the field Distribution channel.
  5. Enter 01 in the field Division.
  6. Select ENTER to confirm.

    You are now in the screen Create: Overview - Single-line Entry.

  7. Enter 1000 in the field Sold-to party.
  8. "Invent" a purchase order number.
  9. To go to the business header data, select Header ® Business data.

    You are now in the screen Create: Header - Business Data.

  10. Enter 02 in the field Delivery block.
  11. Save the document, even if it is still incomplete.
  12. Go Back.

Proof of Event Creation: Event Log

Call the event log again.

  1. In the workflow area menu for developers (transaction SWLD), select Utilities ® Event log ® Display.
  2. Carry out the selection without changing the selection parameters.

The event DeliveryBlockSet is recorded in the list of events created. The aim of this tutorial has therefore been reached.

It is noted that no receivers are entered for this event. This is not an error since the event you defined was not intended to have receivers. If you enter the event as the triggering event of a task and activate the linkage between event and task, this task appears in the event log as a receiver.