Update: RDP Integration Accelerator V6.0.6 (TR 901467.BP7)

BoM Report:
• Optimized logic in BOM determination to prevent short dumps when material type is missing.
• Improved error handling for delta load scenarios.

Packaging Fee API V2:
• Introduced support for RDP Packaging Fee API V2 while keeping backward compatibility with V1.
• Adjusted ABAP structures and mapping logic to align with the new API specification.
• When API V2 is active, the Context field is removed from the selection screen and renamed attributes are supported.

Packaging Element Report (MCL):
• Added support for new attributes isExpanded and Functions under the Fraction node, aligned with RDP Packaging Data V2 API.

Material Document Report:
• Improved performance in material document selection and in country determination method.
• Fixed issue causing duplicate log entries when no data was found.

Packaging Data Validation:
• Added validation to ensure API paths defined in RFC connection and Configuration settings match the same API version.

Author: teodoraberindea

…umentation/RDP fields mapping_V6.0.5.pdf …umentation/RDP fields mapping_V6.0.6.pdfDocumentation/RDP fields mapping_V6.0.5.pdf renamed to Documentation/RDP fields mapping_V6.0.6.pdf Documentation/RDP fields mapping_V6.0.5.pdf renamed to Documentation/RDP fields mapping_V6.0.6.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.4.pdf).
+3. Perform the configuration steps described in the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.6.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).
@@ -89,7 +89,7 @@ The integration package provides several reports for required data replication,
 - **Error Monitoring and Troubleshooting Reports** – Comprehensive logging and troubleshooting capabilities for monitoring replication status and resolving data inconsistencies.
 
 
-For a complete list of reports and instructions on how to load the data, refer to the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.pdf).
+For a complete list of reports and instructions on how to load the data, refer to the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.6.pdf).
 
 ## BAdI Technical Documentation
 
@@ -101,7 +101,7 @@ For packaging fee data replication and mapping functionality, the **BAdI `/VPCOE
 
 For email notification processing enhancements, the **BAdI `/VPCOE/BADI_NOTIFICATION_PROCESSING`** needs to be implemented. 
 
-More details about these BAdIs and their usages can be found in the **[BAdI Technical Documentation](rdp-integration-enhancements-samples/)** and in the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.pdf).
+More details about these BAdIs and their usages can be found in the **[BAdI Technical Documentation](rdp-integration-enhancements-samples/)** and in the [RDP Integration Accelerator Guide](Documentation/SAP_VP_RDP_Integration%20Accelerator_ConfigGuide_v6_0.6.pdf).
 
 
 Sample BAdI implementations are included in the RDP IA package for all available BAdIs, to serve as a starting point for customer's own implementation.

…ation Accelerator_ConfigGuide_v6_0.5.pdf …ation Accelerator_ConfigGuide_v6_0.6.pdfDocumentation/SAP_VP_RDP_Integration Accelerator_ConfigGuide_v6_0.5.pdf renamed to Documentation/SAP_VP_RDP_Integration Accelerator_ConfigGuide_v6_0.6.pdf Documentation/SAP_VP_RDP_Integration Accelerator_ConfigGuide_v6_0.5.pdf renamed to Documentation/SAP_VP_RDP_Integration Accelerator_ConfigGuide_v6_0.6.pdf

@@ -0,0 +1,7 @@
+C5092636     T BP7        1  19 101   0   0   1   0   0   0 122  740   .  0   0   0   0   0 217
+#A
+#/1/                          A   G   D   C   R   7   T   -   Z RELE EX.  _   _   _   _   _ CLI
+BP7 f 0000 20251007092631 anvm101       bp7adm
+BP7 e 0000 20251007092633 anvm101       bp7adm
+BP7 < 0000 20251007092637 anvm101       bp7adm
+BP7 E 0004 20251007092637 anvm101       bp7adm

README.md

@@ -111,6 +111,36 @@ This document provides details on the fixes available in the **Fixes** folder. A
       
       * New version for User guide has been updated with details on the features introduced
 
+### **Update: V6.0.6 – October 2025**
+
+### **TR 901467.BP7**
+
+### ✨ Features and Fixes
+
+* **Packaging compositions from BoM Report**
+  - Optimized logic in determine BOM to avoid short dumps when material type is missing.
+  - Improved error handling for delta load scenario.
+
+* **Packaging Fee API V2**
+  - Introduced support for **RDP Packaging Fee API V2** .
+  - Adjusted ABAP structures and logic to align with the new API specification.
+  - Both V1 and V2 are supported; customers can select the version via RFC connection path.
+  - When RDP API V2 is preferred the `Context` field is removed form selection screen (as this is obsolete field in V2), adjusted renamed attributes, and updated sample BAdI mapping recommendations.
+
+* **Packaging Element Report from Material Classification**
+  - Added support for the new attributes `isExpanded` and `Functions` under the *Fraction* node, aligned with **RDP Packaging Data V2 API**.
+  
+* **Material Document report**
+  - Performance improvement in the material document selection and in Country Determination method.
+  - Display mode - Fixed issue where duplicate log entries appeared when no data was found.
+
+* **Packaging Data Validation**
+  - Introduced validation ensuring that API paths defined in the RFC connection(s) and in the Configuration settings for services match the same API version
+
+### 📘 Documentation
+
+* User Guide updated with details on the new features and adjustments.
+
 
 ---
 ### **Installation Instructions for fixes**

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

@@ -56,19 +56,20 @@ Details on addressed issues or features can be verified [here](Fixes).
 Install all available fixes/new features transport requests from [Fixes](Fixes) folder in the specified sequence below:
 
 1. **Fixes -> TR 901380.BP7
-2. **Update to Version 6.0.1** (Details on changes introduced in V6.0.1 are available in the [Fixes](Fixes) folder)<br>
+2. **Update: Version 6.0.1** (Details on changes introduced in V6.0.1 are available in the [Fixes](Fixes) folder)<br>
    2.1 **TR 901394.BP7** – General update.<br>
    2.2 **TR 901395.BP7** – Additional update for reports for PLM data replication.  ⚠️ *Only install this transport if the UI component **PLMWUI** is present in your system.*
-3. **Update to Version 6.0.2** (Details on changes introduced in V6.0.2 are available in the [Fixes](Fixes) folder)<br>
-   3.1 **TR 901413.BP7** – General update.<br>
-4. **Update to Version 6.0.3** (Details on changes introduced in V6.0.3 are available in the [Fixes](Fixes) folder)<br>
-   4.1 **TR 901420.BP7** – General update.<br>
-5. **Update to Version 6.0.4** (Details on changes introduced in V6.0.4 are available in the [Fixes](Fixes) folder)<br>
-   5.1 **TR 901435.BP7** – General update.<br>
-6. **Update to Version 6.0.5** (Details on changes introduced in V6.0.5 are available in the [Fixes](Fixes) folder)<br>
-   6.1 **TR 901440.BP7** – General update.<br>
+3. Update: Version V6.0.2 – TR 901413.BP7
 
+4. Update: Version V6.0.3 – TR 901420.BP7
 
+5. Update: Version V6.0.4 – TR 901435.BP7
+
+6. Update: Version V6.0.5 – TR 901440.BP7
+
+7. Update: Version V6.0.6 – TR 901467.BP7
+
+📂 Details on changes introduced in each version 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.