Error creating transport request ERP public cloud

[#1]

Hi Community!

I attempted to create a new, transportable package outside of the ZLOCAL component. However, the system still produces an error when I try to create the transportation.

I suspect the root cause may not be just the package type, but the extension methodology itself. My understanding is that for S/4HANA Cloud Public Edition, classic extensions (like creating an ENHO object from Eclipse) are not permitted in order to maintain a "Clean Core." Instead, the recommended approach is to use the "Custom Logic" Fiori app to implement BAdIs that SAP has explicitly released for the cloud.

My specific question is: Is the BADI_WHT BAdI enabled for extension via Eclipse ADT in our public cloud environment, or is it mandatory that we find an alternative, released BAdI within the "Custom Logic" app?

I am attaching screenshots of the new error I receive when using the transportable package.

I appreciate your guidance in ensuring we are using the correct extensibility method for our platform.

Best regards,

Diana
I only have ZLOCAL and Z001 for superpackage

more information (my question):
https://community.sap.com/t5/technology-q-a/error-creating-badi-enhancement-implementation-quot-sap-... 

BaDI: https://api.sap.com/badi/BADI_FIBRREI_WHT

[Chris1973 · Accepted solution]

Dear @diana_gonzalezcr60 

Thank you for sharing the detailed context and screenshots.

From what you have described and based on the errors in your screenshots; the issue is not just with your transport setup but with the extensibility model itself:

• In SAP S/4HANA Public Cloud, creating transportable ABAP packages (like you would in on-premise or private cloud) is not permitted. The platform enforces the Clean Core principle, which prevents the use of classical enhancements (ENHO, implicit/explicit enhancements, transportable custom packages, etc.).
• That is the reason why your system only offers ZLOCAL or customer-specific sandbox superpackages (like Z001) but blocks transport creation. Transports do not exist in Public Cloud, since lifecycle management is handled by SAP.

Regarding your main question about BADI_FIBRREI_WHT:

• In Public Cloud, only released BAdIs can be implemented, and this is done via the Custom Logic Fiori app.
• You cannot implement unreleased BAdIs (like classic BADI_WHT) directly via Eclipse ADT in Public Cloud. Those remain available only in on-premise or private cloud editions.
• If the functionality you need is not available in the released BAdIs catalog, you will need to check the SAP Extensibility Explorer or request an SAP Influence Note to have it added.

So, to simply answer your questions directly:

• No, BADI_WHT is not extensible in Public Cloud through ADT/Eclipse.
• Yes, you must rely on a released BAdI via the Custom Logic app.

Here is a summary and the recommended path you can take. First confirm in the Custom Logic app whether a released BAdI exists for your withholding tax use case. If the BAdi is available, implement your logic there instead of Eclipse. If it is not available, raise an influence request or check if SAP provides alternative APIs/events.

See links below for further details

Use Custom Logic to Overwrite Tax-Related Fields and Read the Manually-Set Billing Date During Creat...

Defining Custom Logic for External Sales and Use Tax Calculation

I hope this provides the desired insights. Happy to answer any further questions.

Best regards

Chris