Hi Planning Experts,
I have created a Webtemplates and added a Button in which i have called my Planning function "COPY".
In the Planning function i have From and To Characterestics i have added different Variables.
After i Execute the report from Web Application Designer, I have clicked on the button "COPY". and Provided the Relevant input for the Source and Target characterstics. But i am getting the below error message.
"ABEND: Values cannot be entered in this context
ERROR: Planning function Copy Function ( ZCOPY ) ended with errors
ERROR: Values cannot be entered in this context"
Can any one help me where i am doing the wrong ? or any solution to fix this issue.
Thanks & Regards,
Muruganand.K
Hi
Could you please check the values enterd in the variable of To values are part of the filter of the query included as part of the Web Template.
The following rules apply:
● The From values are read as reference data and do not need to be part of the filter that is transferred to the planning function.
● The To values are changed; they have to be included in the transferred filter.
● The key figure values for the To values are always overwritten during copying. This is also valid when the From values are empty.
● If there are no values to form a block for a characteristic restriction on the From side, the subprocess is not executed.
● Combinations are generated on the To side for the specified characteristic restrictions. This is consistent with the master data and the characteristic relationships defined for the InfoProviders. If the system cannot find a target for a block and a subprocess, the system terminates the function and produces an error message.
● If a target has been specified in one or more subprocesses, the function is executed and as a result, the target contains the appropriate totals.
The copying function also forms blocks of reference data.
Regards, Hyma
Faced similar problem. The cause of issue was 2 input ready queries running in parallel with planning enabled keyfigures from the same realtime infocube C.
One query Bex1 was based on multiprovider, while another query Bex2 was based on aggregation level (which was based on another multiprovider).
Delta buffer created by planning engine for the cube C was initially created from Bex1 and it's metadata properties wasn't compatile with delta buffer required for Bex2. Since Bex1 wasn't really intended for planning (it was copied via RSZC) turning off 'planning enabled' on all KF's of Bex1 solved problem.
Add a comment