This content has been marked as final. Show 8 replies
I'm wonding if the only way is to create an information element to handle this, which wouldn't be ideal.
Hi Steve1 person found this helpful
A quick question: why do you think you need an element entry, as opposed to a run result?
I'm not sure creating element entries for an assignment during a payroll run is going to be a good idea, not the least of reasons being that it won't get processed because the payroll process only knows what element entries exist at the start of processing an assignment.
Initially the idea was the payroll team can visually see what's happening on the element entries screen. How would you do this through run results? Sorry i don't quite follow.
OK, run results are literally the results of what happened to a specific element entry during a specific payroll run. Normally the payroll team will get to see these if they look at an assignment within a given payroll run. If you navigate to
View -> Assignment Process Results
You will be able to look at the Payroll processes for that assignment (these are termed Assignment Actions) - for payroll (or Quickpay) types, there is the option, via a button at the bottom of the screen, to view the results. Thereafter you can see what run results and run result values were generated
In a formula, when it RETURNs something, that result can go somewhere. Where it actually goes depends on how you've configured the Formula Result Rules. There are numerous mechanisms available, but the most common one is 'Indirect Result'. This allows you to fire a formula on element type 'X' and have the result of a calculation sent as an indirect result to element 'Y'. There is no actual element entry for element 'Y', but there will be a run result and indeed a run result value for element 'Y' for that pay run for that assignment.
Hope that helps, but come back if you need further clarification.
Ah sorry, i do know what you mean, but didn't think it through. As standard i would use indirect in Info elements to feed another element. What i haven't done before is process this at a run result level without creating the element.
I'll give it a go.
Hi,1 person found this helpful
I think the best option if you need to handle this with fast formula is having the information element and we use this kind of design for requirements where in some calculation is required and child entries to be created based on the calculation.
Example - If there is a requirement of recovering an salary advance as a deduction element in x number of pay cycles, then its better to desing the parent information which captures the Salary advance details and number of periods and then within the FF we calculate the EMI for the month and feed an "indirect result" to the respective deduction element. Also, for you information in this example mentioned if you want to stop the processiong of the parent information element when the entire recovery is done then you can set the stop flag to Yes and the parent information element with get endated automatically.
Hope this helps.
If I've understood you correctly, the 'indirect' element 'Y' (to return to my example) can itself have a formula and formula results all of its own to do calculations etc based on the received 'input' (ie the indirect run result value from element 'X')
If I haven't understood you correctly, then my apologies! :-)
Thanks both for the replies. In the instance i was looking at there was actually an information element already present in which i could tag the indirect result to.