cancel
Showing results for 
Search instead for 
Did you mean: 

Employee data time dependendcy with Positon and costcenter (monthly)

Former Member
0 Kudos

Employee data for a given month will be in a given position - say position1 and next month can be in position 2. Similarly he can be transferred from cctr1 to cctr2.

We are using BPC on HANA

Cost has to be calculated for each costcenter based on position of employee.

Employee 1

Mon1  = Pos1 at  CCtr1

Mon2 = Pos2 at CCtr2

So here cost has to be calculated based on positions at each cost center level. Master data - if we define time dependency, it may end up in a complex hierarchy and it will approx create 12 hierarchies of employees ina  year.

Pls let me know how we can manage this complex dependencies and calculate cost based on the positon assigned in a respective month for a specific costcenter.

Accepted Solutions (0)

Answers (1)

Answers (1)

Astha_M
Participant
0 Kudos

Hi Karthi,

In Master Data, Employee and Cost Center can be kept as a different dimension. We can have properties in the Employee dimension as Position (Current & Previous, if required). Data would be saved in combination of Cost center and employee.

So Cost will be available based on each position and cost center level. 12 hierarchies would not be required.

Alternatively, employees data can be maintained in a separate model and position wise data for cost centers can be transferred in a different model which is used for reporting.

Hope it helps.

Thanks

Astha

Former Member
0 Kudos


Thanks Astha.

Current and prev postion property  can hold positions only information without time information when the positon was changed. Properties might not help in storing postion wise data of employee at cost center level. Other option I could thnk of is storing Employee+Position+costcenter level for each period, so that it can be used for cost calculation instead of hierarchies

Manpower planning with promotion plannng and transfers - is common. But master data configuation - looks like do not support effectively. Looks like it has to be stored as transaction data to derive the cost center expenses using the position/employee transactional data

Is there any other easy way to configure for promotion planning, transfer planning of employeess/

Astha_M
Participant
0 Kudos

Hi Karthi,

If it is possible to maintain Cost center dimension separately, data will be saved in the combination of employee+costcenter only.

Position can be maintained as a property or as a separate dimension depending on the requirement.

For the purpose of transfers / Promotions, an input schedule can be given to show opening employee headcount Additions during the period and attrition during the period. In that Input schedule, user can change cost center wise data for the given positions / designations. Actual Employee data will be extracted from the source system only.

If the Promotion / Transfer planning is required employee wise then one way can be to maintain employee wise data & is required to be carried forward every month for a particular CC. Like for the months, when employee belongs to a CC, 1 can be passed for that particular month and can be carried forward till he stays there. With this, you can track the employee's duration in a particular CC and for the given period.

For the updation of master data on real time basis, please see below link:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2020b522-cdb9-2e10-a1b1-873309454...

Hope it helps.

Thanks

Astha