Maintaining Assignment Between Event Without Field Restrictions and Change Document

The event that you want to create is defined as a component of an object type.

You make the following settings to create an event each time a particular change document is written.

1. Choose  Tools  Business Workflow  Development  Definition Tools  Results  Result Creation  Change Documents  Access .

2. Create a new entry in the first view Change "Results for Change Document": Overview. To do this, choose the function New Entries.

3. Specify a change document object in the field Chng.doc.obj..

4. In the field Business Obj. Type, enter the object type whose status change is to be indicated by the event created. Use the F4 input help.

   Note

   The object types offered to you by the system in the F4 input help usually have the same key structure as the change document object.

   It may, however, make sense from a business point of view to create the event for an object type whose key structure is different from the key structure of the change document object. In this case, you must first enter a structure for the object type key and a function module in the workflow-relevant settings for change documents. For more information, see Maintenance of Workflow-Relevant Settings for Change Documents.

5. Enter the ID of the event to be created in the field Event. The event must be defined for the specified object type. The name is taken automatically from the object type definition.

6. Select whether the event is to be created upon change, create, or delete actions.

   Note

   Changes to fields in various tables are generally logged with a change document object. Only one of these tables is the main table in the sense that the relevant change document is written with its key. The create, change, and delete actions always associated with the main table.

   Depending on how the change documents are used in the application, it may be that no change document is written upon create or delete actions.

   Note

   When an item in a sales and distribution document (structure VBAP) is created, the header data of the document (structure VBAK = main table of the change document object) is changed. Therefore, in this case the change document written logs a change and not a create action.

   For more information on how you can react to the creation or deletion of non-main tables, see Maintaining the Assignment Between Change Document and Event with Field Restrictions.

7. Save your entries and exit view maintenance.

If you have catered for the creation of an event in the manner described above, you can use this event as a triggering event of a task or workflow in the normal way.