2024 Mar 19 11:14 AM - edited 2024 Mar 22 10:21 AM
Hello Community Members,
We are facing limitation with Enhancement option : PaymentToPaymentFileConversion, when we tried to implment in our solution, the script is not triggered, hence we raised incident. SAP replied, as its Single Use enhancement option, it cannot be used more than once. The actual response from SAP as follows:
The configuration is fine with this BADI. However, used BADI BADI_FOP_O_PAYMENT(PaymentToPaymentFile ) is a single use badi, for single use BADI there can be only one active implementation. We can see that there are lots of implementations for this BADI in backend. My intuition here is that there is an active implementation of this BADI for some other solution and that is why the BADI for solution YXXXXXXX is not triggering. We can see an implementation in solution YZZZZZZZZ. If the BADI is triggering for YZZZZZZZZ. it should not trigger in solution YXXXXXXX since it is a single use BADI as per understanding. Please kindly confirm it by disabling their implementation for BADI BADI_FOP_O_PAYMENT(PaymentToPaymentFile ) in all other places(all other solutions that are using BADI BADI_FOP_O_PAYMENT) except YXXXXXXX .
When I checked the single use option in the Help document :
"If an enhancement option is for single use, it can be implemented only once in a solution. If an enhancement option is for multiple use, it can be implemented more than once in a solution".
On contrary to the SAP's reply, I interpret from the help document is within a solution the enhancment option can not be used multiple times, whereas if we have another solution created in the system there should not be any issue. Is my understanding wrong?
If we go with SAPs reply, do we need to buy seperate PDI tenant to have multiple Enhancment option to work in the system?
As the existing solution where the enhancmment option is already present is a localisation solution for a country(X), we cannot use the same for the other country(Y) even though we can write the code and manage with filters and IF conditions.
In such cases it defies the purpose of having multiple solution in a system?
Hi senthilmurugan,
Yes, your understanding is correct, a single use badi means it can be created only once per custom solution on SDK. If your custom solution is enabled and properly scoped, I would suggest to push the issue with SAP as there may be some constraints which prevent the badi action from running, like a different filter value or some pre-requisites which should be in place.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thiago,
Thanks for the clarification, We closely following up with the incident we created, seems there is a communication gap to make them understand Single Use Enhancement Option. If possible can you add your view in the ticket. - 156696/2024
Best Regards,
Senthil
User | Count |
---|---|
94 | |
9 | |
8 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.