block accounts if no updates were done in Accounts for last 12 months in SAP C4C

[former_member696337]

Hi Team,

We have a requirement to block the accounts if no updates happened in the accounts in the last 12 months in sap c4c. Could you please help how can we achieve this requirement. We need to automate it.

Warm Regards,

Pushpa

[former_member210407 · Accepted solution]

Hello,

I would suggest to use a workflow rule.

You can create one on the Administrator > Workflow rules section that would be scheduled to 365 DAYs after date of std field "modified on".

You then define the workflow will trigger the action "Obsolete".

Best regards,

Ben

[former_member696337 · Accepted solution]

Hi Ben,

Thanks for your response.

The issue we are facing is there might be activities (email,phone,task etc,) visit, lead opportunity added to the accounts and if they are added we have to check if in the last 365 days, the activities and other objects related to the account have been changed or not.If those activities got changed in the last 365 days , we can't block the accounts. But unfortunately, the standard field 'Changed on' only shows the change in the account(name,address,etc) if any new activity is added then also the 'Changed on' date does not show any change .

Can you please help me out whether it is feasible or not?

Warm Regards,

Pushpa

[former_member210407 · Accepted solution]

Hi Pushpa,

I don't thnik this is achievable using only customization. It would, at some point, require some SDK.
In that case the solution proposed by krpe is to be considered.
I would suggest some adaptations to the solution he provided.

1. Simple BO with only BP_UUId as Alternative key and an other field type DateTime (timestamp). Also create a related action "SetAsObsolete" and do the necessary coding to set corresponding BP as obsolete.

2. You would have to extend the BeforeSave.absl of all the objects you want to take into consideration for defining if account is active or not. You would then update the DateTime field with current datetime

3. Create workflow on the BO created in step 1 to trigger 365days after DateTime and do action "SetAsObsolete".
I would prefer this option over MassDataRun, as it work at a single account level whereas MDR works as batch with a list of accounts and if any account update fails no accounts in the list will be updated.

I hope that helps!

Best regards,

Ben

[Former Member]

Hi pushpa_11,

I would recommend using a Python script with pyautogui library.

As for the steps, Go to Customer work center >> Go to Accounts view >> Search the relevant account and open it >> Click the Actions button, then Set as Obsolete.

Another option would be to work with the data externally if you'd rather work your automation outside C4C. Check the steps in the following note.

2568268 - Frequently Asked Questions on Data Workbench Work Center

Additional references that can help in your journey:

2793614 - Frequently Asked Questions on Data Protection and Privacy Work Center

Data WorkbenchData Workbench

Kindly accept the answer, so the community members can benefit from your topic.

Cheers,

Luis

[PeterK]

Hello Pushpa,

this would be my solution approach:

1. Create a shadow account for every standard account by creating a new ShadowAccount.BO

Use the BP_UUID as alternative key

2. Extend the BeforeSave.absl in the account.xbo to create a ShadowAccount instance if there is no instance already

Check if an instance exists with the Retrieve() Method

3. Create a MDR for your ShadowAccount.BO with an action where you check the account for the last update and set the account to the blocked status

http://www.modulocrm.com.br/wp-content/uploads/2017/03/SAP-Hybris-C4C-Cloud-Aplication-Studio-using-...

Best regards

Peter