To use the expediting/inspection events on the P.70.73 Order Reference screen, you must assign them to the appropriate expediting/inspection levels. Depending on how the data is set up, the planned and forecasted dates are filled automatically when assigning an expediting or inspection level to an order/requisition on the P.70.73 screen.
Events are assigned to expediting/inspection levels on the P.10.57 Events to Levels screen.
First, select the expediting/inspection level for which you want to assign events in the first (Levels) block. In the second (Events to Levels) block, enter a unique sequence number in the Seq field. This number will control the sequence in which the individual events take place. Select the event from the LOV in the Event field.
Only events matching the type of the level can be selected. For example, if you have queried for an inspection level, you can assign events of type 'Inspection' only.
The Short Desc and Description fields display the descriptions of the selected event. With the value selected from the drop-down list in the Frequency field, you specify the frequency of the event, which means how often and how long the event will take place. The available values are:
-
Once
-
Weekly
-
Monthly
-
Specific
If you select Specific, you must specify a number of days in the Days field. If the frequency is not set to Once, you must define a period. Enter the number of periods in the No. of Periods field and select a period from the drop-down list in the Period field. The available values are:
-
None
-
Days
-
Weeks
-
Months
You can also define a start date for the event. Select an option from the drop-down list in the Start Event field. The available values are:
-
None
-
Order Approval
-
Specific Date
If you select Specific Date, you must select a start date from the LOV in the Start Date field. If you select Order Approval, the order approval date of the order supplement 0 (zero) will be used. You can select the Skip check box to prevent the system from scheduling this event immediately for the day of the order approval. Instead, the event will be scheduled later depending on the frequency you have specified:
-
Once - The event will be scheduled one day after the order approval day.
-
Weekly - The event will be scheduled one week after the order approval day.
-
Monthly - The event will be scheduled one month after the order approval day.
-
Specific - The event will be scheduled Days days after the order approval day.
Select the Critical check box to mark the event as critical.
Examples
The results are displayed for the P.70.73 Order Reference screen, Expediting Events tab, and Inspection Events tab.
Case 1
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Once |
0 |
None |
None |
||
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
(empty) |
(empty) |
Case 2
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Once |
0 |
None |
Specific |
30-APR-2010 |
|
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
30-APR-2010 |
30-APR-2010 |
Case 3
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Weekly |
4 |
Weeks |
None |
||
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
(empty) |
(empty) |
Case 4
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Weekly |
5 |
Weeks |
Order Approval (25-SEP-2010) |
||
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
25-SEP-2010 |
25-SEP-2010 |
|||
EVENT-A |
02-OCT-2010 |
02-OCT-2010 |
|||
EVENT-A |
09-OCT-2010 |
09-OCT-2010 |
|||
EVENT-A |
16-OCT-2010 |
16-OCT-2010 |
|||
EVENT-A |
23-OCT-2010 |
23-OCT-2010 |
|||
EVENT/A |
30-OCT-2010 |
30-OCT-2010 |
Case 5
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Weekly |
2 |
Months |
Order Approval (25-SEP-2010) |
||
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
25-SEP-2010 |
25-SEP-2010 |
|||
EVENT-A |
02-OCT-2010 |
02-OCT-2010 |
|||
EVENT-A |
09-OCT-2010 |
09-OCT-2010 |
|||
EVENT-A |
16-OCT-2010 |
16-OCT-2010 |
|||
EVENT-A |
23-OCT-2010 |
23-OCT-2010 |
|||
EVENT/A |
30-OCT-2010 |
30-OCT-2010 |
|||
EVENT-A |
06-NOV-2010 |
06-NOV-2010 |
|||
EVENT-A |
13-NOV-2010 |
13-NOV-2010 |
|||
EVENT-A |
20-NOV-2010 |
20-NOV-2010 |
Case 6
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
Monthly |
1 |
Months |
Specific Date |
25-SEP-2010 |
|
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
25-SEP-2010 |
25-SEP-2010 |
|||
EVENT-A |
25-OCT-2010 |
25-OCT-2010 |
Case 7
Frequency |
Days |
No. of Periods |
Period |
Event Start |
Start Date |
---|---|---|---|---|---|
SPECIFIC |
15 |
10 |
Weeks |
Specific Date |
18-APR-2010 |
Result |
Event |
Planned Date |
Forecasted Date |
||
EVENT-A |
18-APR-2010 |
18-APR-2010 |
|||
EVENT-A |
03-MAY-2010 |
03-MAY-2010 |
|||
EVENT-A |
18-MAY-2010 |
18-MAY-2010 |
|||
EVENT-A |
02-JUN-2010 |
02-JUN-2010 |
-
The default settings for the fields are in such a manner that the system does no automatic calculation at all. Every event is only attached once to an order/requisition combination, and planned and forecasted dates remain empty.
-
If no start date has been defined for an event that is to occur more than once, the creation of all events takes place at the moment a (first) planned or forecasted date is entered on the P.70.73 screen.
-
If you change in any way an assignment of a level that is already used for an order, this update is not populated to the order. It is difficult to do so because dates may have already been entered. By modifying an assignment, these dates might get lost. Therefore, we recommend that you create a new level with different/new assignments and use this new level for future orders or use it as a modified level for existing orders if (major) changes have to be applied. Thus, it is easier for you to avoid any discrepancy that might else occur and be hard to understand.