on 03-15-2019 7:16 AM
Hi
Anyone, please help me with this issue.
We have the package where the user selects either of the radio button "Support" or "Reject".
While "Support" the process chain will trigger the corresponding 'Script logic' and the package gets success, similarly for "Reject" also the process chain will trigger the corresponding 'Script logic' and package gets success. But in As per our Dynamic script one more "Script logic" file is executing for both "Support" or "Reject".
Actually as per scenario, third script logic should run when the "Reject" button pressed, but not for "Support"
How I can add IF/ELSE in a dynamic script that 'If Support selected then should not run 3rd script logic". "If Reject selected then should run 3rd script logic".
Please find an attached file which exists "dynamic script" & "process chain"epm101-dynamic-script-two-logic-scripts.jpg
Hi Vadim
Thank you for your time, we will debug the BADI code
Regards
Silu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, but it means that your badi is incorrectly developed!
And instead of playing with scripts it’s better to debug badi execution and correct badi code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim
Previously two BADI's embed in script logic (BPC 7.5), but in EPM10.1 (after upgrade) the code is not taking second BADI and submitting/reviewing for different data source (ex: first BADI DS00t_CCADJ, second BADI DS01_FINADJ) when we run the package first BADI Datasource itself is working, and not working for second badi datasource. Hence, the second badi kept in separate script logic. Hope you understood our issue. Due to this reason, in Dynamic script third script logic (which is not required in BPC7.5) added.
Regards
Silu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim
Thank you for your information.
If we are not sure of our answers then only we will post the questions in forum to get some help. Someone did this strange think and this packages already exist in production and 3 budget exercises finished without impact, however when running package extra log appearing for the user (when press Support button) which users asked why this extra log (even though not pressed Reject button), and extra log is appearing because of third script logic executing.
Anyhow thank you for your prompt answer. We got the solution previously that we can split this package into two packages "Support" and "Reject". But we are planning without splitting if we can manage in same package, hence posted the question in forums.
Regards
Silu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim
Thank you for your reply.
I understood your answer, our script logic contains two badi's
Previously BPc7.5 supporting two badi's in one Script logic "WF_205_DIV_SUPPORT_R.LGF"
(start badi....end badi) & (start badi....end badi) (two badi's in same script logic)
Now recently we upgraded to EPM10.1 and the script logic which mentioned above (WF_205_DIV_SUPPORT_R.LGF) is not supporting two badis, so we created one more script logic WF_205_DIV_SUPPORT_R.LGF (with second badi in this script logic) and passed this script logic in Dynamic advanced script.
Now when user press "Support" radio button, the second badi also running which not suppose to.
How to avoid this situation with same package (instead of creating two packages), someone suggested to create two packages (one for support and one for reject)
Regards
Silu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Absolutely strange idea to use custom chain to execute multiple scripts...
For Support - use WF_205_DIV_SUPPORT_A.LGF
For Reject - use WF_205_DIV_SUPPORT_R.LGF with the last line: *include WF_205_DIV_SUPPORT2.LGF
Or create a script for reject: REJECT.LGF and use it instead of WF_205_DIV_SUPPORT_R.LGF:
*include WF_205_DIV_SUPPORT_R.LGF
*include WF_205_DIV_SUPPORT2.LGF
Use standard Default Formulas chain!
Looks obvious!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.