Using planning and requirements scheduling

There are two parts of the Requirements Planning are:

  • Project planning
    Enables you to maintain the activity structures, financial analysis, general planning data, and links with external scheduling packages.
  • Project requirements
    Enables you to generate planned orders for material, equipment, and subcontracting, by using data supplied from the Planning and project planning.

External scheduling packages (ESP) Project can also use an external scheduling package (for example, Microsoft Project) to determine scheduling information for activities, budget milestones, OBS elements, and baselines. The ESP currency that is defined in the Project Planning Parameters (tppss0100s000) session will be used in ESP. The external scheduling packages do not support multi-currency. If the cost rate of a cost object defined in LN is in a currency other than the ESP currency, the rate for the currency is calculated with the Exchange Rate Type of the project definition. In the Calendar Parameters (tcccp0100m000) session you can enter a maximum calendar code length for ESP of 59. The default start time is the time the ESP calendar day starts. The ESP time unit defined in the Project Planning Parameters (tppss0100s000) session will be the unit for budget lines, such as labor, equipment and subcontracting in the integration.

The Project Planning Parameters (tppss0100s000) session enables you to set parameters that relate to both parts of the Requirements Planning module. These parameters cover the default project plan and details that relate to the external scheduling package (including currency, time unit, and details of code lengths).

Project planning provides the functionality for time-driven budgets, revenues, and unit costs in a project. Maintenance of planning data, setting up the activity structure, and performing a financial analysis is also covered in project planning.

Note

You can maintain more than one plan for an individual project. For example, to simulate different project scenarios.

The Project Planning Parameters (tppss0100s000) session includes the default number groups and series used by warehouse orders and purchase orders. You can also have the option here to select if you require inventory checks to be made for warehouse deliveries by default.

Requirement scheduling enables you to generate and maintain planned orders for material, equipment, and subcontracting during a project.

These recommendations are based on the activity or element control data in Planning. This is dependent on the budget type, Project Control and the planning data stored in the activity-budget line of planning part of the Requirements Planning. Create the planned purchase orders or planned warehouse orders in the Generate Planned PRP Orders (tppss6200m000) session.

After you confirm these orders you can transfer:

  • Planned purchase orders to Purchase Control (as either a purchase order, a request for quotation, or a purchase schedule).
  • Planned warehouse orders to Warehousing (as a transfer order).

LN also records the planned transactions in the Order Line Balance (Material) (tppss6500m000) session and the delivery transactions in the Delivered Order Lines (Material) (tppss6550m000) session.

Project requirements planning also includes the generation of rescheduling messages. These messages appear when you change either the budget or the timing and quantity of an order.

Generate orders using a project requirement planning run from the control data. This data is based on the actual budget. You define the control data in Planning. If you select multiple projects, a control budget is created for each project.

Note

Generating orders is called project requirements planning (PRP). Purchase orders and warehouse orders are referred to collectively as PRP orders.

Related topics