SAP Project Manufacturing Management and Optimization (PMMO) helps achieve greater efficiency with project manufacturing in an Engineer to Order (ETO) environment to deliver complex end products (for example: military aircrafts, ships and submarines, complex industrial machinery etc.), that often involves complex engineering and production processes.

In this blog post, we’ll take a look at what’s new in Project Manufacturing Management and Optimization (PMMO) in S/4HANA 2023 FPS0 Release. Before reading this, I encourage you to check out my other blog posts to take a look at some of the key features available in previous releases.

With S/4HANA 2021 release, following key features were added:

• Costed Stock Gain
• Subcontracting purchase orders (Project R stock at vendor)
• Recursive rework orders
• Serial number handling

With S/4HANA 2022 release, following key features were added:

• Pegging Assignment history
• Order cost rollup Fiori report
• Pegging and Distribution header
• Manual change of Pegging Assignments
• Pegging Assignments Fiori report

Now let’s take a look at the major highlights from 2023 release in PMMO:

Excel upload for Breakpoints

A simple yet helpful feature to be able to upload pegging breakpoint master data from an excel spreadsheet is now available. Until now, breakpoints had to be manually maintained (via transaction PMMO_BREAKPOINT or PMMO_BREAKPOINT_LTD). A standard function module API (PMMO_MAINTAIN_PEG_BREAKPOINTS) was available in 2022 release for maintaining breakpoints. With this release, a excel upload transaction (PMMO_BREAKPOINT_UPL) is available to use an excel spreadsheet to maintain (i.e., create, update and delete) breakpoint records in PMMO. All standard checks that are performed via the API and maintenance dialog are performed also when uploading from an excel spreadsheet. In addition, there is a simulation feature and data preview feature before the data is updated.

Single screen maintenance for Breakpoints

The standard breakpoint maintenance transactions (PMMO_BREAKPOINT and PMMO_BREAKPOINT_LTD) have been changed from 2 screens to a single screen. This enables users to be able to copy and paste the data easily from clipboard when entering multiple rows of data.

Pegging Assignment history report by time range

Standard Fiori reports were delivered in 2022 release for current Pegging Assignments and Pegging Assignments based on a given point in time. In this release, the standard Pegging transaction (PMMO_PEGGING) has an integrated reporting option to query Pegging Assignment changes for a given time period. A flexible selection allows to enter criteria from the Pegging Assignments to query for changes in the given time period. For changed records, there is a simple comparison to highlight the differences.

Restore Pegging Assignments from History

Have you ever had the need to revert to Pegging Assignments from the past? With the availability of Pegging Assignment history, we now have the capability to restore Pegging Assignments from history. This feature provides the capability to not only reverse the latest pegging run, but any pegging run in the past. In an exceptional situation it might be necessary to restore Pegging assignments from a historical point in time. Other use cases for this feature is for internal test systems where tests have to be repeated from the same set of Pegging Assignment history (for example, assignment of excess, scrap, loss etc. from pegging history). This feature is integrated into the Pegging header and requires additional authorization to be able to restore the assignments from history. A simulation feature is also available.

Change reason for manual pegging assignment changes

When Pegging Assignment records are manually changed, it may be necessary to document the reason for the activity. For this purpose, there is a flexible configurable option to capture and edit change reason for manual pegging assignment changes. In addition, the pegging header transaction supports documenting header text for Pegging update runs.

Cost Distribution Fiori report

With the new Cost Distribution Fiori report, program and project finance teams can perform detailed analysis on distributed cost postings from PMMO. This includes commitment, actual and vendor down payment distributed postings.

Additional Q and R supported movement types

Following movement types have been added to the list of supported movement types in PMMO

561/R and 562/R: Goods Receipt without purchase order for project stock at vendor

545/R and 546/R: By products in AD subcontracting purchase orders

545/Q and 546/Q: By products in Core subcontracting purchase orders

581/Q and 582/Q: By products in Network Activity

Costed Stock gain configuration by movement type

With this release, there is additional flexibility in costed stock gain configuration. You can configure per stock difference category movement type, whether a costed stock gain should be created or not.

Stock consistency check report

A new transaction PMMO_STOCK_CHECK is available to compare PMMO stock and core Inventory Management stock. This includes project stock (special stock Q) and project stock at vendor (special stock R).

Check out the restriction note 3363143 for PMMO in S/4HANA 2023 release.

Further innovations are planned in PMMO in future releases. You can find the roadmap for upcoming features here. Thank you for reading this blog post. I am looking forward to your comments. See you soon in another blog post!