SAP Analytics cloud planning - Data action issue

[pragnya_m]

Hi, I’m facing an issue with a Data Action where users select a start and end time period to perform employee transfers. However, the Data Action is currently running even on closed periods—meaning the actual periods—where I don’t want the new data to appear. The problem is that I’m scoping the time dimension based on user-selected parameters rather than using version properties, so the Data Action affects both actual and planning periods indiscriminately.

To solve this, I need a way to restrict the Data Action so that it only updates data for planning periods within the user’s selected range and completely excludes any actual (closed) periods, even if they fall between the start and end dates. For example, if the user selects January to June 2025, but January to March 2025 are actual periods, the Data Action should only process April to June 2025, leaving the actual periods untouched.  i have locked data at model level but i dont want to show the user any data movements on actual periods. Can anyone please help.

@N1kh1l 

Regards,

Lakshmi

[SarauShen]

Hi @pragnya_m ,  if you have the periods being maintained as the properties of version dimension, here is an example how to filter out the data in data action formulas. 

More details can be found in help doc:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/afe93e3cf1414a7b8419b...

[N1kh1l]

@pragnya_m 

"For example, if the user selects January to June 2025, but January to March 2025 are actual periods," - How will the system know January to March is Actual period ? Either create some flag to indicate what periods are actual or you can also check if Actual data exists. I am not sure of you model setup but you just need to make the system understand what periods are actual.

IF RESULTLOOKUP([d/version]="public.Actual") !=NULL THEN

ELSE

<Put your logic here>

ENDIF

Hope this helps !!

Nikhil

[pragnya_m]

Hi Nikhil, I'm running data action on forecasting version where i have actual and planning periods. As i mentioned, i have time parameters for start and end date rather than version properties. Please let me know how can i restrict closed periods

[N1kh1l]

What you still did not mention how will the system know what is a closed period. Do you have any flags for close period. You need to define the criteria for closed period. 

Even if you are running the DA on Forecast version you can still build filtering logic based on Actual version. As you are not specifying what is a closed period, I asked you to check if there is data in Actual version ( logic that period is Actual period)