on 2025 Apr 29 1:28 PM
While implementing a classic unreleased BADI we plan to write the core logic in a Tier-1 Class ( use Tier-2 wrapper class to wrap any unreleased objects). Once we have this logic in a Tier-1 class , we plan to call this method in the classical Tier-3 BADI. This is to avoid/decrease technical debt once this classical BADI cloud released. Do you see any issues with this approach (cross Tier, cross "ABAP language) on the upgrade stability?
This is on S4HANA 2023 , Basis version 758 SP 02
Do you have any documentation ( Note, KBA or blog) to support this approach?
Request clarification before answering.
Hello,
Thank you very much for your question. I'm very sorry for the late response.
Can you please check whether the following information (GenAI was used to help generate this content) solves the issue?
Implementing a classic unreleased BADI by writing the core logic in a Tier-1 class and using a Tier-2 wrapper class to wrap any unreleased objects is a strategic approach to minimize technical debt. This method allows you to prepare for future upgrades by ensuring that your logic is already in a cloud-ready format once the BADI is released. However, there are some considerations:
Cross-Tier Compatibility: Ensure that the Tier-1 class and Tier-2 wrapper are compatible with the Tier-3 BADI. This involves checking that the interfaces and data types used are consistent across tiers.
Upgrade Stability: While this approach is designed to enhance upgrade stability, it is crucial to test thoroughly to ensure that the integration between tiers does not introduce unexpected issues during upgrades.
Documentation and Guidelines: SAP provides guidelines on using tiers for extensibility, but specific documentation for your approach might not be available. It is recommended to follow SAP’s general guidelines for extensibility ABAP Cloud – SAP S/4HANA extensibility – May 2023 … - SAP Community and API usage.
Unfortunately, there is no specific SAP Note, KBA, or blog that directly supports this approach. However, the concept of using tiers for extensibility SAP S/4HANA Extensibility Options For Clean Core J… - SAP Community is discussed in various SAP resources, emphasizing the importance of using released APIs and extension points for upgrade stability.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.