#AI-Generated Content
Hello,
Thank you very much for your question.
I've asked our internal AI tool for support, and here's the response. Please check whether the suggestions work for you.
Kind regards,
Henrike
Returnable Packaging Material Process — Fit & Solution Architecture for SAP S/4HANA Cloud Public Edition
This is a well-structured requirement. Let me break it down into what is standard, what needs extension, and how to architect the custom components cleanly within the Public Edition constraints.
1. Standard Foundation: What SAP Already Provides
Before building anything custom, activate and leverage the relevant standard scope items:
Scope Item Description Relevance
| BDW | Returnables Processing | Core process — issues packaging with delivery, handles returns |
| BKP | Customer Returns (Advanced) | Returns order → returns delivery → Post Goods Receipt flow |
| BDD | Lean Customer Returns | Simplified returns if no inspection is needed |
The standard flow for returnable packaging in S/4HANA Cloud works like this:
- Packaging material is set up with item category group LEIH in the material master
- It is issued to the customer via a delivery note (DC in your context)
- The system tracks it as customer special stock (stock type V)
- Return is processed via a returns sales order (type LA) → returns delivery → Post Goods Receipt (PGR)
Key gap: The standard process does not provide a custom tracking screen with DC-wise / customer-wise pending quantities, nor a one-click PGR button against individual DCs. This is where you need to extend.
2. Extensibility Architecture: Clean-Core Approach
SAP S/4HANA Cloud Public Edition only supports clean-core extensibility — no direct modification of standard code. Your requirement falls into two tiers:
Tier 1 — Key User Extensibility (No-Code / Low-Code)
Use for:
- Adding custom fields to sales/delivery documents (e.g., LR Number, DC Number reference on delivery header/item)
- Adapting the UI of standard Fiori apps (e.g., adding DC number to delivery display)
- Custom CDS views for embedded analytics (customer-wise pending packaging stock reports)
Tools: Custom Fields app, Custom Logic app, UI Adaptation, Manage KPIs and Reports
Tier 2 — Side-by-Side Extensibility on SAP BTP (Required for Custom Screen)
The Returnable Packaging Tracking Screen with PGR button cannot be built inside S/4HANA Cloud Public Edition core — it must be a side-by-side BTP application. This is the correct and supported approach.
3. Technical Solution Blueprint
Component 1: Custom Fields on Delivery Documents
- Add DC Number and LR Number as custom fields on the Outbound Delivery (business context: Logistics: Delivery)
- These become part of the delivery document and are printable on DC output forms
- Use the Custom Fields app (Key User Extensibility)
Component 2: Returnable Packaging Tracking Screen (BTP Side-by-Side App)
Build a SAP Fiori Elements app using one of these approaches:
Option A — SAP Build Apps (Low-Code)
- UI built in SAP Build Apps on BTP
- Connects to S/4HANA Cloud via Communication Arrangement and BTP Destination
- Consumes released OData APIs for stock and delivery data
Option B — RAP-based Custom Fiori App (Pro-Code)
- Custom CDS views built on top of standard delivery/stock tables
- Exposed as an OData V4 service via RAP (ABAP RESTful Application Programming Model)
- Custom Fiori Elements List Report built in SAP Business Application Studio (BAS)
- Deployed on S/4HANA Cloud (on-stack, consuming only your own custom service — not standard API_* services)
Recommended: Option B (RAP) for tighter integration and better performance, since data stays within the system boundary.
Screen Logic:
- User enters Customer Code → app queries custom CDS view
- CDS view reads from standard delivery and special stock tables to derive: DC Number, Packaging Material, Qty Issued, Qty Returned, Qty Pending (= Issued − Returned)
- Each row shows a PGR button (only for rows with pending quantity)
Component 3: PGR Button — Triggering Post Goods Receipt
On PGR button click, the app must:
- Create a Returns Sales Order (LA) referencing the original delivery, via the released OData API:
POST /A_SalesOrder (or use the Returns Delivery API directly) - Create a Returns Delivery against it:
POST /A_ReturnsDeliveryHeader - Post Goods Receipt automatically (SAP supports automatic PGR on returns delivery creation if configured)
API to use (from SAP Business Accelerator Hub):
API_SALES_ORDER_SRV — Create Returns OrderAPI_OUTBOUND_DELIVERY_SRV — Create Returns Delivery- Released OData APIs are consumed from BTP, not from an on-stack custom UI
For a fully automated single-click PGR, consider orchestrating steps 1–3 via SAP Build Process Automation or a CAP (Cloud Application Programming Model) service on BTP acting as a middleware.
4. Deliverables Mapping
Your Requirement SAP Cloud Solution
| Enhanced Invoice Layout | Form template in SAP Forms by Adobe / Output Management — Key User Extensibility |
| Custom LR Creation Application | Side-by-side BTP app (SAP Build Apps or Fiori/RAP) |
| LR Output Print | Adobe Forms output, triggered from delivery/billing |
| Custom DC Creation Application | Extend standard delivery creation; DC = Outbound Delivery with custom fields (LR No., etc.) |
| DC Output Print | Adobe Forms / Smart Forms output on delivery |
| Auto Invoice Email Program | Output Management + SAP Integration Suite email channel, or BTP-based event-driven automation |
| Returnable Packaging Tracking Screen | BTP Side-by-Side app (RAP + Fiori Elements or SAP Build Apps) |
| PGR Integration for Packaging Material Returns | OData API calls from BTP app (Returns Order → Returns Delivery → Auto PGR) |
| Final Invoice with LR and DC Reference | Custom fields on billing document + invoice form template |
5. Action Items for Your Teams
Business Team
- Provide LR and DC print layouts
- Define customer-wise packaging material list and tolerance rules for pending returns
- Confirm whether debit memo should be triggered if packaging is not returned within X days (standard BDW supports this)
Functional Team
- Prepare detailed functional spec for the tracking screen (fields, filters, PGR logic)
- Define item category determination for LEIH materials in your system
- Configure Communication Scenarios / Arrangements for the OData APIs needed by the BTP app
- Confirm if automatic PGR on returns delivery creation is sufficient or if manual confirmation is needed
Technical Team
- Estimate effort for: Custom CDS Views + RAP service, Fiori Elements app in BAS, BTP Destination / Communication Arrangement setup, Adobe Forms for LR/DC/Invoice output
- Assess whether SAP Build Apps (low-code) or RAP (pro-code) better fits team skills
- Review the SAP Business Accelerator Hub for exact API names and communication scenario IDs
6. Key Constraints to Keep in Mind
- In SAP S/4HANA Cloud Public Edition, you cannot modify standard ABAP code — all custom development must go through extensibility APIs or BTP
- Standard OData
API_* services must be consumed from BTP, not from on-stack custom UIs - The standard BDW scope item supports pallets only; your custom packaging types must be correctly configured with LEIH
- There is no standard automatic packing function in BDW — quantity tracking via custom CDS is required
Recommended Next Step
Activate scope item BDW in your system and run through the standard process end-to-end to identify the exact data gaps. This will give the functional team a concrete baseline before writing the specification for the custom tracking screen and PGR integration.
Sources consulted: SAP Community — CBG0 & RPM Extensibility · SAP Help — Returns Logistics · SAP Help — Returns Delivery API · SAP Learning — Extensibility Approaches · SAP BTP Returnable Packaging Use Case
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.