In pharmaceutical manufacturing, available stock is not necessarily usable stock. A product may physically be available, but its remaining shelf life may be too short to meet a future requirement.
This makes shelf life an important consideration in supply and production planning. The question is not only whether sufficient stock exists, but whether that stock will still be usable when it is actually needed.
Our team on site in a pharmaceutical manufacturing environment.
SAP S/4HANA embedded Production Planning and Detailed Scheduling (PP/DS) provides functionality for considering shelf life requirements as part of production planning.
This can be a suitable approach when shelf life is one of several constraints that need to be considered in detailed planning and scheduling. Particularly in more complex production environments, PP/DS provides planners with extensive capabilities for creating feasible production plans.
However, not every shelf life planning requirement necessarily requires the full scope of PP/DS.
In one of our projects for a global pharmaceutical company, this distinction became particularly relevant.
The existing system landscape included SAP APO, where PP/DS was also responsible for shelf life planning. As part of the transition to SAP S/4HANA, the question was how this requirement should be covered in the new architecture.
Instead of reproducing the existing PP/DS setup, we implemented shelf life planning through targeted enhancements to MRP in SAP S/4HANA.
For the specific requirements of the customer, this provided the necessary planning performance while significantly reducing the complexity of the previous solution.
Another practical advantage was the user experience. Planners could continue working with the familiar MD04 stock/requirements list, with shelf life considerations integrated into the existing MRP process. This reduced the amount of change required in their daily planning activities.
The implementation itself was completed within one sprint, and user acceptance testing was completed without defects. These results are specific to this project, but they illustrate an important point: the most comprehensive planning solution is not automatically the most appropriate one.
Shelf life can also play a role beyond production planning.
SAP Integrated Business Planning (IBP) can consider expiration dates and minimum required shelf life when matching supply and demand. This becomes relevant when shelf life requirements need to be reflected across a wider supply network rather than primarily within production execution.
SAP IBP can therefore complement operational planning in SAP S/4HANA, depending on the planning horizon and the scope of the business requirement.
There is no single approach that fits every shelf life planning scenario.
Embedded PP/DS is particularly relevant when shelf life constraints are part of a broader requirement for detailed production planning and scheduling.
Enhanced MRP can be an effective alternative when the shelf life requirement is clearly defined and can be addressed within the existing MRP process without introducing additional planning complexity.
SAP IBP becomes relevant when shelf life needs to influence supply and deployment decisions across the wider supply chain and over a longer planning horizon.
The appropriate architecture therefore depends on several factors: the specific shelf life requirements, the existing SAP landscape, the required planning horizon, the level of planning detail, and the complexity of the underlying production and supply network.
Shelf life planning is a good example of why SAP architecture decisions should start with the business requirement rather than with a particular application.
PP/DS may be the right answer for a complex detailed planning environment. In other situations, a focused enhancement to standard MRP may solve the same underlying requirement with considerably less complexity. And when the requirement extends into network-level supply planning, SAP IBP introduces another perspective.
The goal should therefore not be to implement the most sophisticated solution available, but to choose the simplest architecture that meets the planning requirements reliably.