Release V6.1

Release V6.1 introduces important adjustments for Packaging Fee replication and Handling Unit reports, plus several bug fixes.
This version also includes all fixes from V6.0.1 through V6.0.7,

Author: teodoraberindea

…umentation/RDP fields mapping_V6.0.7.pdf Documentation/RDP fields mapping_V6.1.pdfDocumentation/RDP fields mapping_V6.0.7.pdf renamed to Documentation/RDP fields mapping_V6.1.pdf Documentation/RDP fields mapping_V6.0.7.pdf renamed to Documentation/RDP fields mapping_V6.1.pdf

@@ -33,7 +33,7 @@ To install/update the RDP Integration Accelerator package:
 
 1. Upload the provided transport files using transaction **CG3Z** or any relevant function modules/tcodes in your system.
 2. Import transport requests in the specified sequence (see [installation steps](rdp-abap-technical-objects/readme.md)).
-3. Perform the configuration steps described in the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.7.pdf).
+3. Perform the configuration steps described in the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_1.pdf).
    - Ensure all prerequisites for initial setup on BTP account and subaccount are fulfilled (More details on [BTP configurations](https://help.sap.com/docs/sap-responsible-design-and-production/user-guide-sap-rdp/initial-setup).
    - Configure RFC destinations (**SM59**) for HTTPS communication with the RDP API.
    - Maintain service path prefixes (optional).

Documentation/SAP_VP_RDP_Integration Accelerator_ConfigGuide_v6_1.pdf

@@ -0,0 +1,7 @@
+C5092636     T BP7        1  87 447   0   0   6   0   0   0 513  740   .  0   0   0   0   0 217
+#A
+#/1/                          A   G   D   C   R   7   T   -   Z RELE EX.  _   _   _   _   _ CLI
+BP7 f 0000 20251211094345 anvm101       bp7adm
+BP7 e 0004 20251211094348 anvm101       bp7adm
+BP7 < 0000 20251211094356 anvm101       bp7adm
+BP7 E 0004 20251211094356 anvm101       bp7adm

README.md

@@ -151,6 +151,62 @@ This document provides details on the fixes available in the **Fixes** folder. A
 	* **Material documents replication report**
 	  - Adjust the logic for determining the ShipToCountry attribute, to correctly handle cases where a receiving vendor is maintained on the corresponding Purchase Order
 
+### **Update: V6.1 – December 2025**
+
+	### **TR 901515.BP7**
+
+      ⚠️ **Important Note – Impact on Pack Fee Replication Report**
+
+      A new mandatory selection parameter **Load ID** has been introduced for Delta Load execution in the **Packaging Fee Retrieval** report.
+
+      * Existing scheduled background jobs for “Retrieving Pack Fee – Delta Load” **will fail** unless batch jobs are updated to include this new parameter.
+      * Customers must **update their job variants** and verify the selected Load ID.
+      * Customer-specific **BAdI implementations**, especially those enhancing retrieval or posting logic, may require adjustments to align with the updated report logic.
+
+      It is highly recommended that customers review their automation and BAdI code before importing this update to avoid interruptions in replication processes.
+
+      ### ✨ Enhancements & Fixes
+
+      * **Packaging Fee – Retrieving & Posting Reports Adjustments**  
+        The RDP Pack Fee API now supports multiple delta tokens in parallel.  
+        Major functional enhancements include:
+        - Allow customers to maintain **separate delta runs per variant**
+        - During initial load, the variant name is stored together with the delta token
+        - Delta load must be executed **per variant**
+        - Retrieved data is saved and archived
+        - Added option to **post retrieved data directly** from the same report (via radio button)
+
+      * **Handling Unit Report Adjustments**
+        - Fix for correct handling of the entity mapper class
+
+      * **HTTP Protocol Version – Updated Logic for JSON Header**
+        - SM59 configuration now determines whether HTTP 1.0 or HTTP 1.1 is used when replicating data to RDP
+        - System automatically sets correct protocol version in HTTP requests
+
+      * **Determination of BOM Valid-To Field – Plant Added to Sorting Attribute**
+        - Ensures BOMs assigned to multiple plants appear correctly  
+        - Fix implemented without impacting existing customer BAdI logic
+
+      * **Material Document – Country Determination Priority Update**
+        - Implemented logic for prioritizing **country of target customer**  
+          (relevant for drop shipment scenarios)
+
+      * **Packaging Fee Reports – Added Missing Authorization Objects**
+        New authorization objects introduced for:
+        - Customer Role
+        - Company Code Exemptions
+        - Customer Exemptions
+
+      * **Delivery Report – Fix in Package Splitting**
+        - Adjustment in the package-splitting logic, in case BAdI is implemented
+
+      * **Bug in Example Implementation – Material Classification Fraction Mapping Versioning**
+        - Fix for missing **VERP** material in BOM processing
+        - Corrections in BOM where-used determination when components have no assigned material
+        - Includes performance improvements
+
+
+
 ---
 ### **Installation Instructions for fixes**
 To apply available fixes/updates:

rdp-abap-technical-objects/Fixes/K901515.BP7

@@ -73,6 +73,16 @@ Install all available fixes/new features transport requests from [Fixes](Fixes)
 
 📂 Details on changes introduced in each version are available in the [Fixes](Fixes) folder.
 
+9. ## **Update: Version V6.1.0** – TR 901515.BP7
+
+Version **V6.1.0** is a consolidated update that includes:
+
+### **✔ All fixes and features introduced from V6.0.1 through V6.0.7 (from point 1 to point 8 in this document)**
+### **✔ New fixes and new features introduced with V6.1**
+	
+Note: New customers can skip point 1 to point 8 and install instead TR for V6.1.0
+
+📂 Details on changes introduced in V6.1 are available in the [Fixes](Fixes) folder
 
 Note: Additional fixes may be provided in the future. Customers should always check for the latest available fixes or new features and ensure they are installed.