on 2018 Nov 19 2:30 PM
Summary:
We are currently using HCMTLMU01 data source to extract the data related to employee times and load them in BPC.
This data source has a Key Date figure, which indicates date on which employee has performed the work. Apart from Key Date figure, we would also need Posting Date figure in this report, so that we can see exact correlation between time booked and balance on the GL accounts for particular accounting period.
Detailed explanation:
-For example, employee has performed work on 25.10.2018.
-Employee is submitting his time calendar in the following month, for example on 10.11.2018.
-Since the previous month accounting period has been closed, the financial data (journal entry) will be posted in the current month (November), with Posting date 10.11.2018 (this posting date might be different depending on when source document was "force posted" by accounting team, however this posting date will be in the current month of November).
-The journal entry created from this will be posted with November posting date and it will create entry on GL account. The G/L date will be 10.11.2018 and Key Date will be 25.10.2018. When we extract date from ByD using HCMTLMU01 data source, we only have Key Date figure without G/L Date figure. Thus we can not explain the balances on G/L accounts which are driven by time booked, since we only have Key Date figure pulled in without G/L Date figure.
Question:
How can we load employee times in BPC with GL posting date?
Request clarification before answering.
You can extract 2 times to 2 different categories.
One category refers to employee time as of Key Date, while the other category refers to employee time as of posting date.
Thus, you can see the variance between time booked and balance on the GL accounts for the particular accounting period.
Which subsequently you can use as a base for adjustment on management reporting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then you have to change your data loading. For sure data has to be loaded with posting date! Use different data source or create a new one...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Every hour worked by chargeable employee has a cost rate (e.g. $100).
If employee has performed work on 25.10.2018 but entered his time in ByD on 10.11.2018 system will try to post journal entry in October, however October period has been closed for financial postings. So the journal will be posted in November.
When we look in the November report, we can see all the cost that has been posted in November accounting period (e.g. $1000) but we can not see 10h of work performed since accounting data is pulled with GL date and hours worked data with actual working date.
While the approach could be that we force employees to book the time in the month they have done the work, this is impaired by fact that we have more then 3000 employees booking time across the world and that we are half way trough ByD implementation.
Basically, our financial numbers that are driven by worked performed are always with GL date, while hours reported in BPC are coming trough with different key date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With BPC standard you have only single key figure. Not clear what do you want to achieve?
Please provide some sample
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are currently using standard BPC. We have plan to move to embedded one next year.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What bpc are you using? Standard or embedded?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 7 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.