Long Term Planning (LTP) in SAP PP: MS04, MS31, MD61

โšก Smart Summary

Long Term Planning in SAP PP simulates a future demand and supply situation across every BOM level, so planners can test capacity, material availability and vendor coverage without touching the operative plan.

  • ๐Ÿ”˜ Simulation only: LTP is an MRP run in a simulative version, so operative planning data is never changed.
  • โ˜‘๏ธ Inactive PIRs: Requirements are created in MD61 under an inactive version such as 02, ignored by operative MRP.
  • โœ… Planning scenario: MS31 binds the version, plants, periods and BOM selection ID, then releases the planning file entries.
  • ๐Ÿงช Run and evaluate: MS02 executes the run, MS04 lists simulative planned orders and CM38 shows the capacity load.
  • ๐Ÿ› ๏ธ Purchasing view: MS70 updates the purchasing information system so buyers can negotiate annual volumes.
  • ๐Ÿ“ˆ S/4HANA note: SAP positions Predictive MRP as the successor to long term planning from release 1909.

Long Term Planning in SAP PP Using MS31, MS02, MS04 and MD61

SAP PP Long Term Planning (LTP)

Long Term Planning (LTP) in SAP PP is used to simulate the future demand and supply situation at all BOM levels. Its main function is to check the capacity situation, the material requirement and the ability of vendors to supply the material in the required time.

This is not an operative run but a simulative one: the actual planning situation is not affected, and the capacity situation of the work centers can be seen well ahead of time. A plant can therefore decide early whether additional machines are needed to cope with capacity bottlenecks.

  • LTP is nothing but an MRP run in a simulation version, used to simulate the production plan for the future.
  • The plan can be transferred from the simulative version to the operative version โ€œ00โ€ (actual planning) if the simulation shows that all capacity and requirements can be fulfilled.
  • The purchasing department can also use the outcome. Future requirement quantities help buyers estimate purchase orders and negotiate delivery schedules and contracts with vendors.
  • Vendors benefit from long-term planning results as well, because they are sent a preview of the estimated future purchase orders and delivery schedules.
  • A Planned Independent Requirement (PIR) version can be either active or inactive. For LTP the version must be inactive, because it is simulative. Only an active PIR version is taken into operative planning (MRP).
  • Existing master data can be used for LTP, but it is also possible to maintain different master data (a separate BOM and routing) for LTP.
  • To delete long-term planning data, delete the planning scenario. The whole cycle can then be re-run with new requirements in another inactive version.
  • Long-term planning data can also transfer routing activity quantities to the respective cost centers. Controlling divides the cost center budget value by the activity quantity from the LTP run to calculate the activity price, which feeds the standard cost calculation.

How to Create an Inactive Version of Independent Requirements in SAP

Step 1) From SAP Easy Access, open transaction MD61.

Transaction MD61 opened to create planned independent requirements

  1. Enter the material code for which the requirement needs to be created.
  2. Enter the Plant code.
  3. Enter version โ€œ02โ€, the inactive version, so that the requirements are considered in the long-term planning run and not in MRP.
  4. Enter the Planning horizon dates for which demand needs to be created.
  5. Enter the planning period as month, M.

MD61 initial screen with material, plant, version 02 and planning horizon entered

After filling in all the fields, click Green check mark button used to confirm the MD61 entries or press Enter to go to the next screen.

Step 2) In this screen, we input the requirement quantity of the material in monthly buckets.

  1. Version โ€œ02โ€ is shown and the Active check box is unflagged, which means this is an inactive, simulative requirement that is considered in the LTP run only.
  2. Enter the requirement quantity in monthly buckets.

MD61 planning table with monthly requirement quantities in inactive version 02

Click Save button in the SAP toolbar to save after entering all the data. The system shows the message Status bar message confirming the requirements were saved.

How to Create Planning Scenario in SAP PP

A planning scenario is required for the long-term planning run. The annual simulative requirements, in the form of PIRs, are assigned to it, together with a BOM selection ID so the run explodes the relevant BOM. Current stock and existing planned receipts can be included or excluded.

Step 1) From the SAP Easy Access screen, open transaction MS31.

Transaction MS31 create planning scenario entry screen

Enter the Planning scenario (numeric or alphanumeric, as you choose) and give the scenario a description. MS31 dialog for the planning scenario key and description Press Enter on the keyboard to move to the next screen.

Step 2) In this screen:

  1. Enter the planning periods for which the LTP run needs to take place.
  2. Keep Opening stock blank, which means the current stock is not considered in the LTP run.
  3. BOM selection ID โ€œ01โ€ means the active BOM is exploded in the LTP run.

Planning scenario detail screen with planning periods, opening stock and BOM selection ID

Step 3) In the same screen:

  1. Press the โ€œPlanned independent requirementsโ€ button at the top; a small pop-up window appears.
  2. In the pop-up screen, enter version โ€œ02โ€ and the planning periods.

Pop-up assigning the inactive PIR version 02 to the planning scenario

Step 4) In the same screen:

  1. Press the โ€œPlantsโ€ button at the top; a small pop-up screen appears.
  2. Enter your manufacturing Plant code.
  3. Press the โ€œConfirmโ€ button after verifying all the details.

Pop-up assigning the manufacturing plant to the planning scenario

Step 5) In the same screen:

  1. Press the โ€œRelease + saveโ€ button, and the planning file entries are generated.
  2. Click โ€œYesโ€ in the pop-up window to release the scenario.

Release and save prompt that generates the planning file entries

On clicking Yes, the system asks whether the planning file entries should be created online or in the background.

Step 6) In this screen:

  1. Planning file entries are generated. Click the โ€œImmediatelyโ€ button to generate the entries.

Dialog offering online or background creation of the planning file entries

Messages are generated about the planning file entries, which means the system has identified the number of materials relevant for the long-term planning run.

Message log listing the materials flagged for long-term planning

You can close this screen or move back to the SAP Easy Access screen.

How to Run Long Term Planning (LTP) in SAP PP

Step 1) In transaction MS02, we take the LTP run and enter the required details.

Transaction MS02 selection screen for the long-term planning run

  1. Enter your planning scenario.
  2. Enter the material code.
  3. Enter your manufacturing Plant code for which you want to take the run.
  4. Enter Processing key as โ€œNETCHโ€ (net change in total horizon).
  5. Enter โ€œ1โ€ in MRP List, so the system creates an MRP list for later analysis of the run.
  6. Enter Planning mode โ€œ1โ€, as we are taking an LTP run.
  7. Enter Scheduling indicator โ€œ2โ€, so LTP performs lead time scheduling and uses the routing times to calculate the duration of the simulative planned order.
  8. Enter โ€œ1โ€ to use the settings from the planning scenario, which means firmed receipts are not considered in the LTP run.

MS02 screen with the planning scenario and control parameters filled in

Press Enter twice to start the LTP run. The system takes some time and then issues messages about the planning result.

Step 2) Check the procurement proposals status. In this screen:

  1. Check the messages about the number of procurement proposals created.

LTP run statistics showing the number of procurement proposals created

How to Check Stock/Requirement List in SAP

This list shows the requirements (the inactive PIRs) and the receipt elements, such as simulative planned orders, for the planning scenario. It shows simulative data only, not the real-time operative data.

Step 1) In transaction MS04:

  1. Enter the Planning scenario.
  2. Enter the material code.
  3. Enter the Plant code.

MS04 initial screen with planning scenario, material and plant

Press Enter to move to the next screen.

Step 2) In this screen:

  1. Check whether the planned orders were generated against the PIR, and check the rescheduling dates in those planned orders. These are simulative planned orders and have nothing to do with real-time data.

MS04 simulative stock requirements list with the generated planned orders

How to Check Capacity Situation in SAP

Step 1) From SAP Easy Access, open transaction CM38 to check the capacity requirement at the work center. The work center is loaded with the simulative planned orders, which produce capacity requirements expressed in time.

  1. Enter the planning scenario.
  2. Enter the plant code.

CM38 selection screen for the simulative capacity evaluation

Press Enter to move to the next screen.

Step 2) In this screen:

  1. Check the capacity load at the work center, which is the ratio of the capacity requirement (in hours) to the available capacity (in hours).

CM38 capacity load report comparing requirement and available capacity

How to Analyze Simulative Purchase Info System in SAP

LTP generates planned orders instead of purchase requisitions, and those planned orders carry no source of supply. The vendor can still be seen in the standard information system reports.

After the LTP activity, a new version of the PURCHIS information system is created.

Step 1) In transaction MS70:

  1. Enter the Planning scenario.
  2. Select the option โ€œStandard/moving avg. priceโ€, which means the simulative planned orders are valued at standard or moving average price.
  3. Unmark โ€œTest modeโ€ and execute. Version info structure 001 is created automatically.

MS70 selection screen for evaluating the simulative purchasing data

On execution, the system updates the purchasing information system in version 001 with the simulative purchase order quantity and value, so buyers can plan raw materials for the whole year and negotiate with suppliers.

Step 2) In transaction MCEC, you can see the updates to the purchasing information system made in the previous step. The order quantity can be seen vendor by vendor for a given period, all in the simulation version.

  1. Enter the Planning scenario.
  2. Enter your plant code.
  3. Enter the period to analyze.

MCEC selection screen for the simulative purchasing information system report

Press the execute button or F8 to run the report.

Step 3) This screen displays the anticipated purchase quantity and value for raw materials, based on the simulative annual production plan.

  1. Check the PO quantity and value in the simulation version.

MCEC report showing anticipated purchase quantity and value per vendor

Troubleshooting Long Term Planning Errors

  • All PP master data, such as the BOM and the routing, must be in place. Without it, the run cannot drill down to the lowest BOM level, that is, the raw materials.
  • Enter the PIR quantity in the inactive version to avoid any conflict with real data.
  • If the run plans nothing, check that the scenario was released. Planning file entries are only created when the scenario is released and saved.
  • If a material is missing from the result, confirm that its plant is assigned to the scenario and that the PIR version matches the one assigned in MS31.

FAQs

Machine learning sharpens the demand forecast behind the simulative requirements and surfaces capacity risks earlier. SAP positions Predictive MRP for this scenario work, where algorithms rank simulations instead of leaving the planner to compare them manually.

Copilot can draft the ABAP or scripting code that schedules a background LTP run and exports MS04 or MCEC output. The planning logic stays in SAP, so test any generated program in a sandbox client.

Predictive Material and Resource Planning, introduced with release 1909, is positioned by SAP as the successor. It simulates demand and capacity with a simplified algorithm and needs far less master data setup than LTP.

SOP plans at product group level and transfers the result to demand management. LTP takes those requirements down through the BOM, producing component quantities, capacity load and purchasing volumes.

Transaction MS64 copies the simulative planned independent requirements from the inactive version into active version 00. The simulative planned orders are never converted; operative MRP recreates them from the copied requirements.

Transaction KSPP transfers the activity requirements from the LTP run into scheduled activity quantities on the cost center. Controlling then reconciles those figures into planned activity for the activity price calculation.

MS01 runs total planning for a whole plant in the scenario, MS02 plans a single item at multiple levels, and MS03 a single item at one level. MS05 displays the LTP list.

MS32 changes a scenario and MS33 displays it. Deleting the scenario removes its simulative data, after which the cycle can be repeated with new requirements in another inactive version.

Summarize this post with: