Currently, not all of the fields in enterprise projects and WBS Elements are supported with mass change function. BAdi implementation on determination can be used as a workaround.
In this article, let's take WbsIsAvailyControlcontrolobj as an example. This field is not supported in the Fiori App Mass Change to Projects. While it is exposed in the BAdi implementation /S4PPM/PROJECT_DETERMINATION.
Here is the BAdi implementation, the check logic will be triggered if the priority code is updated as ‘003' (Medium). If it is, then the BAdi will update the target field as abap_true.
IF enterpriseproject-prioritycode="003" and enterpriseproject-wbsisavailycontrolcontrolobj IS INITIAL.
changedenterpriseproject-wbsisavailycontrolcontrolobj = abap_true.
ENDIF.
As this is triggered at the determination stage, so all of the original determination and validation checks will still work as expected.
The trigger field and target field can be replaced by any other fields. But for the trigger field, it is better to be a convertiable field and its update should not trigger any other business scenario.
Then schedule a mass change job to update the prioirt code for any enterprise project.
The trigger field priority and the traget field AVC check level are both updated after the mass change job is executed successfully.
Links:
