on ‎2015 Dec 29 2:38 PM
Hello Friends,
I have a following scenario. Users plan at employee level and Asset level for HR and CAPEX planning and forecasts are updated each month
Each forecast employee or asset gets a unique number, which is sent to ECC manually.
In the future months when employees are hired or the assets are brought, the forecast numbers need to be updated.
ECC generates a new asset or new employee and the unique number is added as a property for recon.
At the moment the updates are done manually.
Is there a standard way to achieve this functionality or a better way.
Thanks
Ed.
Request clarification before answering.
There is no standard way
Looks like you receive a new members with the old id in property - is it correct?
And you want to move all data from the old ID to the new one?
Please provide some sample...
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Vadim for your reply
New Employee information is added through a custom VB Macro template. Unique ID is an auto generated number, unique for a cost center
This is a sample new employee forecast report, for cost center 1001 and for Month January
Cost Center 1001
Forecast Month - January
Emp UID title level salary benefits etc
1001450 T1 L1 100000 10000
1001451 T1 L2 110000 10000
if an employee is hired for the first line, then ECC would generate an employee id and a BPC reference number
Employee id BPC Reference number
2000235 1001450
Now that the employee is an actual figure, and its no longer a forecast, the cost center manager deletes the line corresponding to 1001450 , thus updating the forecast amounts.
The idea behind it is, the cost center manager needs to know exactly how much would be the spending on the employees for the rest of the fiscal year.
The actual costs + the forecast figures. Now if the forecast figures are not updated, when the actual person is hired, then there is possibility that we are double counting the expenses for a new hire.
Its an age old system. so if there is way to revamp completely the way its done currently it would be nice.
My idea here is understand on a process stand point. This would be a situation for many clients.
Thanks
Ed.
"ECC would generate an employee id and a BPC reference number" how ECC will know the BPC reference number?
"Now that the employee is an actual figure, and its no longer a forecast, the cost center manager deletes the line corresponding to 1001450 , thus updating the forecast amounts." - delete in BPC?? May be clear data?
How do you want to combine figures? "The actual costs + the forecast figures." - please provide an example...
Vadim
Thanks Vadim for your reply.
"ECC would generate an employee id and a BPC reference number" how ECC will know the BPC reference number? - This number currently flows to the HR team for hiring, ( excel sheet - manual,) and then after the hiring to ecc team ( excel sheet - manual). -
Delete the data 1001450- --clear data for 1001450 from forecast version for that ID in BPC
Combine figures - sorry- its actual costs + forecast costs ( salaries, benefits, other benefits for forecast employees) - This is a new employee planning for forecasting.
Eg actual data for cost center 1001, Month - January
Actual Forecast
Salary 950000 150000
Benefits 100000 20000
Other Benefits 40000 10000
Total Costs
Thanks
Ed
If you want to clear data for all ID's referenced in the property like REFNUM of EMPLOYEE dimension you can try the following script:
*SELECT(%CLEARID%,[REFNUM],EMPLOYEE,[REFNUM]<>'')
//%CLEARID% will contain list of ID to clear data
*XDIM_MEMBERSET EMPLOYEE=%CLEARID%
//other scope - category, time...
*WHEN EMPLOYEE
*IS *
*REC(EXPRESSION=0)
*ENDWHEN
Vadim
Thanks Vadim, it helps for point 2 and 3.
Is there a way to automate the integration of BPC reference id to ECC actual employee number. Do we need to retract this data to ECC for automation. or manual intervention is always necessary
If the planning is done at a job level or position instead of employee, then we might not be able to get an ID to tie back or clear forecast figures.
| User | Count |
|---|---|
| 17 | |
| 11 | |
| 9 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.