We are proud to announce the latest release for Core Logistics in SAP S/4HANA Private Cloud 2025 FPS02. This update continues with our commitment across our teams to bring durable enterprise-grade capabilities to our customers.
Core Logistics provides the foundational execution and planning capabilities that underpin end-to-end logistics processes in SAP S/4HANA. Within the broader SAP S/4HANA Supply Chain portfolio, Core Logistics sits at the center — providing the essential, reliable core that enables advanced planning, warehouse management, transportation management and industry-specific extensions to work together seamlessly.
As an important reminder, we group the delivered innovations according to their corresponding solution capability. For those new to Logistics Execution – or as a quick refresher for readers of our previous blog post – here are the key capability categories we’ll be exploring:
- Delivery Management – a component of SAP Logistics Execution, Delivery Management is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles. In Delivery Management, all delivery procedure decisions can be made at the start of the process by: (1) Considering general business agreements with your customer; (2) Recording special material requests; (3) Defining shipping conditions in the sales order. The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.
- Handling Unit Management – used to map packing-controlled logistics in the SAP system, HU Management does not consider the movements of the individual materials, instead it maps the movements of the handling units that contain these materials. Available in all core logistic areas where logistic material bookings can take place, this feature uses handling units to map logistical processes to simplify the processing of goods movements thus optimizing logistical processes. This simplified process includes the existing packing function across core logistics and the storage unit processing in the Warehouse Management system.
- Inventory Management – Inventory Management is part of the Materials Management module and is fully integrated into the entire logistics system. Material is procured from external or internal sources based on the requirements determined by Material Requirements Planning. The delivery is entered in Inventory Management as a goods receipt. The material is stored (and managed under Inventory Management) until it is delivered to customers (Sales & Distribution), or is used for internal purposes (for example, for production).
- Batch Management – Batch Management lets you handle homogeneous partial quantities of a material or product across the entire logistics quantity and value chain. In practice, this means you can group and work with partial quantities that share the same characteristics, for example, the same quality grade or shelf-life expiration date. This is especially useful in industries where tracking these details matters, such as food, pharmaceuticals, and chemicals. By managing materials in batches, you can maintain full traceability, keep quality consistent, and stay on top of important information like expiration dates throughout production, storage, and distribution.
Delivery Management
Product Compliance Check Enhanced for Distributed System Landscapes
We’ve made an important update to how Product Compliance works, where now post goods issue is now blocked whenever Product Compliance check results are still pending. In other words, your goods can’t be shipped until the system knows for sure that everything checks out.
Product Compliance checks handle the important stuff during delivery processing: validating dangerous goods, confirming product marketability, and reviewing safety data sheets. But when these checks run on a remote system, network latency can slow things down. When that happens, you’ll see the status Blocked – Check Pending (H), which simply means the checks have kicked off but the results haven’t landed yet.
Previously, it was possible to execute post goods issue even while the compliance status was still “Check Pending.” That created a real risk in which goods could go out the door before their dangerous goods classification was confirmed.
Now, if any Product Compliance header status is set to Check Pending, post goods issue is blocked. You’ll simply need to wait until the final compliance status comes through before shipping. It’s a small pause that prevents a potentially costly compliance headache.
We’ve also improved support for dangerous goods that are only partially packed, or not yet packed, at the time of delivery processing. The dangerous goods check can now validate these items against the released dangerous goods classifications defined in your LO-HU Packing Instructions.
RAP Objects in Delivery Management
Developer extensibility lets you create development projects in SAP S/4HANA using ABAP Development Tools for Eclipse. From there, you can build extensions, services, and SAP Fiori apps with the full set of ABAP Cloud features released for SAP S/4HANA for example, the ABAP RESTful Application Programming model, HTTP services, and ABAP objects. For more details on the released objects and how to find them, see Released Development Objects.
With the SAP S/4HANA 2025 FPS02 release we also updated 3 RAP Business Objects (BO) available in Delivery Management:
- Inbound Delivery – I_INBOUNDDELIVERYTP
- Outbound Delivery – I_OUTBOUNDDELIVERYTP
- Customer Returns Delivery – I_CUSTOMERRETURNSDELIVERYTP
The following table summarizes the objects the changes made to the objects. In the Technical Name field you can see for which business objects the relevant feature is active for.
Feature | End-User Name | Technical Name | Details |
RAP Extensibility | Outbound Delivery, Inbound Delivery, Customer Returns Delivery | I_OutboundDeliveryTP, I_InboundDeliveryTP, I_CustomerReturnsDeliveryTP | You can extend all three delivery RAP BOs. For more information, see About RAP Extensibility. |
Enhanced Post Partial Goods Receipt Flexibility | Inbound Delivery | I_InboundDeliveryTP | For inbound deliveries, you can combine PostPartialGoodsReceipt operations with header and item updates in the same LUW. You can combine them in any order. Combinations involving multiple partial goods receipts for the same delivery, or mixing partial goods receipt with full goods movement in the same LUW, are not supported due to data integrity constraints. |
Delete Delivery Items via RAP | Outbound Delivery, Inbound Delivery, Customer Returns Delivery | I_OutboundDeliveryTP, I_InboundDeliveryTP, I_CustomerReturnsDeliveryTP | You can delete delivery item instances via RAP EML using item-level DELETE operations. |
Batch Split Item Action | Outbound Delivery, Inbound Delivery, Customer Returns Delivery | I_OutboundDeliveryTP, I_InboundDeliveryTP, I_CustomerReturnsDeliveryTP | You can create batch-split items programmatically using the new CreateBatchSplitItem operation at item level. The method accepts a Batch Number parameter. |
Extended Field Editability | Outbound Delivery, Customer Returns Delivery | I_OutboundDeliveryTP, I_CustomerReturnsDeliveryTP | You can edit additional fields on header and item level. |
Delivery Lock Alignment | Outbound Delivery, Inbound Delivery, Customer Returns Delivery | I_OutboundDeliveryTP, I_InboundDeliveryTP, I_CustomerReturnsDeliveryTP | Field editability in RAP-based applications matches SAP GUI behavior for late-change scenarios. The RAP delivery locking mechanism aligns with VL* transaction behavior for consistent locking across interfaces. |
Batch Management
Natural Language Search for Batches
Natural language search for Batches in the SAP Fiori launchpad lets you run search queries using everyday language. This makes it easier to interact with the system, improves the overall search experience, and helps you quickly find the business objects and information you need. Just type your query in natural language into the SAP Fiori launchpad search bar, and you’re good to go.
Depending on your role and authorizations, you can view data for the following business objects:
- Batch shelf-life expiration date
- Batch manufacturing date
- Batch status
- Batch country of origin
- Batch supplier
- Batch for material
- Batch for plant
Furthermore, for Batch Management, with this release we enhanced the Batch Master Record API by introducing five new fields at the header level, namely:
Field name | Description |
BatchExtWhseMgmtInternalId | Identifier of the batch as assigned by the cloud warehouse. |
NextInspectionDate | Date of the next recurring inspection for the batch. |
LastGoodsReceiptDate | Date of the last goods receipt. |
ExportAndImportProductGroup | Export and import product group assigned to the batch. |
BatchCertificationDate | Certification date of a batch. |
Handling Unit Management
The Handling Unit (HU) data migration object has been enhanced to integrate a serial number section in the XML file with the following fields:
Field name | Description |
Bundle ID | Used to group several handling units to a nested handling unit. For example, if a carton, that contains a material, is packed with another carton onto a pallet, the cartons and the pallet are a nested handling unit and have the same Bundle ID. |
External Handling Unit ID | External key to identify the unique position entry to avoid duplicate key. |
Counter | Technical item ID without business meaning. |
Serial Number | Specifies the serial number of a serialized material. |
The Handling Unit business object now triggers an event tied to Handling Unit creation in Inventory Management. This event is raised whenever a handling unit is created and saved in a storage location managed by Inventory Management, giving you a reliable way to react to these actions as they happen. Keep in mind that the event is currently not raised for handling units created in Warehouse Management, so it applies specifically to the Inventory Management scenario for now. For more details, check out the SAP Business Accelerator Hub.
Artificial Intelligence: Official release of the Joule Shipping Specialist
With this Feature Pack we deliver the official release of the Joule Shipping Specialist while also extending its coverage across the outbound delivery process. Users can now pick individual delivery items and execute or reverse a Goods Issue directly through Joule, conversationally completing two of the most critical steps in the shipping workflow. Full item details are available on demand, giving users the context they need without leaving the interaction.
On the creation side, outbound deliveries can now be created directly from the Sales Orders, removing the need to switch to a separate transaction. Joule also handles large delivery documents reliably, ensuring consistent performance regardless of document complexity.
Joule is a conversational AI assistant embedded in SAP S/4HANA, allowing users to interact with their business processes in natural language — without navigating complex menus or switching between transactions.
With this release, shipping teams can execute a broader set of outbound logistics tasks end-to-end through that conversational interface. Fewer steps, less context switching, and faster execution for the operations that matter most in daily warehouse work. For compliance-sensitive environments, all create, update, and delete operations performed through Joule are now fully traceable through framework-level audit logging.
FIND OUT MORE!
You can also find more technical details and documentation on the above listed topic and others we left out via the “What’s New” viewer on the Help Documentation portal.
For more information on SAP’s Clean Core strategy please read the Clean Core extensibility white paper.
Source link
