On the Expediting Events tab, you can track expediting events, enter planned, forecasted, and actual dates, and define those events that are critical for the selected requisition or tagged item.
Updates of an activity on the requisition level are populated to all tagged items of the requisition without individual data. Individual data means that this same activity of the tagged item has been changed manually. Updates on the tagged item level are always only processed for that individual item. Once data has been updated on the tagged item level, this data is regarded as individual data even if this data is identical again with the data on the requisition level.
Any modifications applied to the assignment of events to levels on the P.10.57 Events to Levels screen are not populated to orders that already had this level when the change was applied. So, what you see here is the status of the assignment at the time this level was assigned to this order.
You may, however, amend this specific expediting plan in individual cases by deleting events that turn out to be superfluous or by adding additional events of the expediting level assigned. Such modifications will not affect the general assignment of events to levels as defined on P.10.57.
When selecting an expediting level for a requisition or a tagged item, all events that have been assigned to this level on P.10.57 are automatically attached to the requisition / tagged item.
This screen is a core workflow screen. For more information, see Core Workflow Screens.
The Seq field displays the sequence in which the individual events take place according to the assignment made on the P.10.57 Events to Levels screen. To order the data by sequence and planned date, you can double-click in this field.
The Event field displays the name of the event. To see the setup of an event, you can double-click in this field to open the P.10.57 Events to Levels screen where events are defined.
The descriptions of the expediting event are displayed in the Short Desc and Description fields.
The date for which this event is planned is displayed in the Planned Date field. If you enter a date in the past, a warning appears. You can double-click in this field to order the data by this field and the order sequence. See Events to Levels for the details on how and when this field is filled automatically.
Entering the planned date initially for an event of frequency 'Once' will also set the forecasted date of this event. The date for which this event has been forecasted is displayed in the Forecasted Date field. You can double-click in this field to order the data by this field and the order sequence. See Events to Levels for the details on how and when this field is filled automatically.
The date on which this event took place is displayed in the Actual Date field. You can only enter dates of the past or the current date. You can double-click in this field to order the data by this field and the order sequence.
The Critical indicator shows whether this is a critical event. Together with project default ZP_RD_CRIT, the planned date and the actual system date, this indicator is evaluated for the Exp Event check box on the P.70.71 Expediter Workload screen. See Expediter Workload.
The Document Code field displays the name of the document. Only documents are available whose type matches the project default setting ZP_EX_EV. You can double-click in this field to open the D.10.11 Documents screen.
The document revision is shown in the Rev field. The default value is 0 (zero).
The date the document was created is displayed in the Document Date field.
The document descriptions are displayed in the Short Desc and Description fields.
The Origin field shows the name for the origin.
The type of the path is displayed in the Path Type field, the path of the file containing the document in the Source Path field, the name of the file containing the document in the File Name field, the document format (for example, ASCII, WordPerfect, and so forth) in the Format field, the client reference of the document in the Client Ref. field, and the partner reference of the document in the Partner Ref. field. You can enter any comments on the event in the Comment field.
You can click the Order By ... button to change the order by criteria for the displayed records. When you click this button, a list of values is opened, offering you all the columns currently visible in the form. Select the field by which you want the data to be ordered by in the first place. Then a second list of values comes up, allowing you to select a second field. In this way, you can select up to four fields by which the data is to be ordered. If you do not need any further fields as order by criteria, just click the Cancel button in the LOV box. After the last LOV has been closed, your last query is performed again, this time using the new order by criteria. The data is always sorted in ascending order. The selected and changed order by criteria are displayed in the Ordered by field.
The Ordered by field shows by which fields the displayed records are sorted. By default, the data is ordered by seq, event. To change the order criteria, click the Order By ... button at the bottom of the screen, or select either the Order by this field ascending or the Order by this field descending item from the pop-up menu available on the field level. If you select Order by this field descending, the field name is lengthened by ‘(desc)’ to show that the data is currently displayed in a descending order.
If a document has been attached to the expediting event, you can click the Open button to view that document.