Modification To Planned Call Transaction (PCAL) During Campaign Execution
We have a standart procedure (and therefore customizing) to generate call lists (Planned Call transactions - PCAL) from campaign elements (through execution) assigned to a campaign.
And planned cal transactions are generated succesfully.
I want to make some modification on this planned call transactions during execution (like changing planned call objective according to objective defined in campaign element).
For this purpose, I activated the business add-in: CRM_MKT_MODIFY_ORDER. I wrote some codes in MODIFY_ACTIVITY_OBJ method of the BAdI and set external break points. However while executing campaign element, abap debugger screen doesn't show up. It seems that this BAdI is not triggered.
It seems to me that the easiest way to make the required modifications can be done with this BAdI, but I'm open to other solution ideas as well.
I'd appreciate any advice regarding this issue.
Thanks in advance
Dawood Hla Shwe replied
I think the badi CRM_MKT_MODIFY_ORDER is called during execution, i.e. when you actually generate the call list. Usually, this is started in background as job and depending on setting, the job is called under different username name.
You can debug this either by setting an endless loop into the Badi and catch the running process in SM50 (potentially dangerous) or after campaign execution, find the job (transaction SM37) and re-run the generation report with the same variant. online.
If you need to modify the contact during the call, then I would start with badi ORDER_SAVE, which is called everytime you save any 1order document. Remember, the Badi is also called when the document is first time created during generation, so adapt your code accordingly.