If a trip with accounting status
open
or
to be settled
is assigned the approval status r
equest awaiting settlement
or
trip awaiting settlement
, a workflow is started, based on template type
TripWaits.
Workflow Template: WS12500017
Abbreviation: TripWaits
Name: Mail: Trip On Hold
Triggering Event of Workflow Template
The event
ExpenseWaits
(
trip on hold
) or
RequestWaits
(request on hold) from object type
BUS2089
(
employee trip
) is entered as the triggering event of the workflow template.
Note
This "link" between the event and the workflow template to be started is deactivated in the standard system. If you want to start the workflow template, the link must be activated in Customizing for SAP Business Workflow (Transaction SWETYPV).
Workflow Container and Binding
The most important information that must be available during workflow is the object reference to the trip to be processed ( _Evt_Object ), and the name of the person who entered the trip data ( _Evt_Creator ). This information is available as event parameters in the container for the triggering event, and must be transferred to the workflow container by "binding".
The standard system includes the following binding definition between the triggering event and the workflow container:
Workflow Container |
Event Parameter Container |
|
_WF_Initiator |
<- |
_Evt_Creator |
TRIP |
<- |
_Evt_Object |
In the standard system, the _WF_Initiator element is included in the workflow container. The Trip element was created in addition to the existing standard elements.