Normal view

There are new articles available, click to refresh the page.
Today — 5 February 2026SCM Blogs by Members

Technical Deep dive to understand HU label print from Work Center with PPF actions with scenarios

This blog will give you an idea & help you to understand what standard coding  is trying to perform when you hit the print HU button in the work center. How the Action merging and processing time influence the PPF action processing and also the main tips and tricks to find the condition record is matching or not where we often find that sometimes even though the condition record is there system is unable to print. PPF topic has been always been technical in nature so this blog tries to decode the mystery.

Mapping Stock to New Nested Handling Units Using Migration Cockpit in SAP S/4HANA Public Cloud

Mapping Stock to New Nested Handling Units Using Migration Cockpit in SAP S/4HANA Public Cloud

Step 1: Go to the ‘Migrate Your Data’ tile and create a project by selecting the ‘HUM – Handling Unit’ object.

Img:1

Gowtham5_0-1768392077248.png

Img:2

Gowtham5_1-1768392077253.png

Gowtham5_2-1768392077256.png

Img:3

Gowtham5_3-1768392077260.png

Gowtham5_4-1768392077263.png

Gowtham5_5-1768392077263.png

Img:4

Gowtham5_6-1768392077266.png

Step 2: Once the project is created, select the project and download the migration template.

Gowtham5_7-1768392169114.png 

Gowtham5_8-1768392169122.png

Step 3: Fill in the required data in the tabs of the template. The detailed steps are provided below.

Tab 1: Bundles for Nested HUs

  • Maintain a Run ID when creating Nested HUs for a material.
  • The Run ID is used to group multiple Handling Units into a single Nested HU structure.

Example: If a carton containing material is packed together with other cartons onto a pallet, the cartons (inner HUs) and the pallet (outer HU) together form a Nested Handling Unit structure and must share the same Run ID (Bundle ID).

Gowtham5_9-1768392214900.png

Tab 2: Header Data

  • Since an external number range is maintained in the backend configuration for HU packing types, the External HU ID is filled for the respective packing materials, Plant details.

Gowtham5_10-1768392214903.png

Tab 3: Item Data

  • Maintain the material against the respective HU ID and enter the quantity to be migrated into the new Handling Units.

Scenario example used in this document:

  • At Pallet HU level, the Carton Box HU is assigned.
  • At Carton Box HU level, the Small Box HU is assigned.
  • At the Small Box HU level, the material “42 – SFG Material” is maintained with a quantity of 15 KG.

When this data is uploaded, the system:

  • Automatically assigns the stock to the respective HUs, and Creates the complete Nested HU structure, finally resulting in the Pallet HU containing all lower-level HUs.

Gowtham5_12-1768392365935.png

Step 4: Upload File and Mapping Task

  • Upload the completed data template.

Gowtham5_13-1768392432386.png 

Step 5: Simulate

Gowtham5_14-1768392432388.png

Step 6: Migrate

Gowtham5_15-1768392432390.png

Gowtham5_16-1768392432434.png

  • Finally, migration completed, the system creates the Handling Units (HUs) and assigns them to the existing stock for the material.

Check Stock: Display Stock Overview

Gowtham5_17-1768392484482.png

Gowtham5_18-1768392484486.png

Gowtham5_19-1768392484489.png

  • The below screenshot confirms successful creation of Nested HUs, with stock correctly assigned from Small Box → Carton Box → Pallet HU.

Gowtham5_20-1768392484496.png

  • Using Migration Cockpit, we successfully mapped existing stock into a nested HU structure, enabling accurate HU tracking and improved stock visibility in SAP S/4HANA Public Cloud.

 

Travel Under Quarantine(TUQ): A supply chain concept of utilizing the quarantine time in Shipping

Travel  Under Quarantine (TUQ) solution to use quarantine time for in-transit

Abstract: This is a unique supply chain concept of utilizing the quarantine time in productive way to improve efficiency without additional investment by leveraging existed integrated supply‑chain technologies. It represents a paradigm shift for MedTech and pharmaceutical companies — moving from extended supply‑chain practices to an orchestrated supply chain that strengthens the company’s bottom line, better serves patient needs, and supports environmental sustainability.

In general, standard supply‑chain practice entails manufacturing followed by quality inspection and batch‑release activities. Production captures, records and documents all product and process related to Critical Quality Attributes (CQAs) documented. Following production completion, each batch is transferred to Quality for inspection and the batch’s shelf‑life countdown commences. To validate product conformity and other batch documentation is a quite lengthy process itself but unavoidable process to run the business complied manner.

Also many situations samples need to be sent to specialized laboratories to ensure conformities and Bio-Buurden*1 testing or Endotoxin testing *2  for medical devices. Similarly, other long‑lead‑time tests required for long‑term stability assessment of medical devices and pharmaceutical products are crucial for determining shelf life and ensuring that products remain safe and effective during storage and use; such testing is essential to establish and verify that a product retains its intended characteristics for a specified period under defined storage conditions. This is required to demonstrate compliance with applicable national, regional, and statutory /regulatory requirements.

This process typically requires 2-6 weeks and sometimes longer. For established products manufactured in pre-validated production line with approved production recipes, 99% of cases of those test results show promising result.

Improvement Opportunity: As illustrated in Diagram 1, instead of quarantine a batch under quality stock at the manufacturing facility or a sterilization site, or a 3PL/4PL logistics location, the manufactured, sellable batches can be moved from the manufacturing site to an OTC site through systematically controlled shipping process (for example, shipped to  a primary distribution center or a company/affiliate-owned DC within the company distribution network). Physical inventory deployment /shipment typically takes an additional 2–4 weeks to reach global hub DCs. Once the batch is released post arrival of the product, the product becomes immediately available for customer fulfillment, effectively providing customers with an extra 4–6 weeks of usable shelf life.

How to create new entry in Material Group 1~5, in the T-Code: MM01 (MM02 & MM03) > Sales: sales org2

How to create new entry in Material Group 1~5, which is in the T-Code: MM01 (MM02 & MM03) à Sales: sales org 2 <tab>

 

Khan_0-1767326675623.png

 

 

 

Resolution: for resolution goto following menu path:

SPRO > Logistics – General à Material Master > Settings for Key Fields > Data Relevant to Sales and Distribution > Define Reserve Fields in Material Master

 

Khan_1-1767326675629.png

 

Khan_2-1767326675633.png

 

Khan_3-1767326675651.png

 

 

On save a transport will be generated

 

***end of doc***

 

search tags:

Material group 1, Material group 2, Material group 3, Material group 4, Material group 5, Material price group, TVM2

By: Khan
2 January 2026 at 04:08

Insights from ERP Implementation Projects

Read this article to expand your ideas about implementation projects. SAP Consultants with good technical experience can help in the success of the project, but there are more insights than just technical skills. Implementation projects are a journey filled with different phases. This article could help expand this knowledge.

❌
❌