Ansicht
Dokumentation
Monitoring Dates ( RELNPS_46A_TERMINVERFOLG )
CPI1466 during Backup ABAP Short ReferenceThis documentation is copyright by SAP AG.
Short text
Monitoring Dates
Scope of Functions
As of Release 4.6a, it is possible to define events for components in a project, and to monitor the dates of these events. You define events by entering a name and a short description. You can then enter the dates manually or let the system derive them. You can, for instance, define creating an order or a goods receipt as events, and can then control the schedule of the procurement process more tightly.
You can monitor the date types Baseline, Plan, Forecast, and Actual for each event.
The date for a date type of an event can be entered in different ways. For each date type of an event, you can
- Create a link to a reference date in an object that the component is assigned to, for instance, a network activity or a purchase order item
- Create a link to a reference filed not in the standard via a user exit
- Manually enter a date
You can call up Monitoring Dates for a project, WBS elements, or Networks.
To monitor particular dates together, you define groups to which you assign components and events. You can then analyze or edit the dates in these groups together in the dates overview.
It is possible to schedule events by linking an event with a milestone in the network. To do so, you must
- Assign the event a milestone in Customizing
- Link the event with an existing milestone in the network in the Monitoring Dates transaction itself
Effects on Customizing
In Customizing for Project Systems four new activities have beeen added under Material. Here you define Events, Reference fields, Statuses, and Profiles for monitoring dates
Further Information
For more information, see the R/3 Library under Project System -> Material.
ROGBILLS - Synchronize billing plans rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 2352 Date: 20240523 Time: 080916 sap01-206 ( 38 ms )
