Colleagues,
I have a scenario in which I need my ChaRM Document (custom YMMJ) to automatically switch user statuses upon certain circumstances. Let me explain:
1) User invokes a visible PPF action to switch the status to E0011 (HF_SET_STATUS)
2) After switching to E0011, somehow code is automatically invoked that will apply some logic (custom action with BAdI?)
3) Based on the logic, the status can then automatically switch from E0011 to E0012, or stay at E0011
I've been trying to better understand the 'boundaries' of PPF actions versus BAdI actions, and I think with a combination of the two I can get this figured out, but I could use your help. I've been reading someof Michael Vollmer's blogs which are steering me in the right direction, but I could still use some assistance. Here's one idea, but not sure if it'll work:
1) Visible PPF action switches status to E0011
2) A custom Action at E0011 then invokes a custom BAdI (after consistency checks) to apply the logic
3) Based on the logic, the BAdI will submit program CRM_SOCM_SERVICE_REPORT to switch to next status of E0012
However, I'm not sure if that will work because perhaps the PPF action has the "final say" and the transaction will still finish in E0011. Right?
Is there a proper way of executing this scenario?
Much appreciated,
David