Skip to Content

Datasource 0HR_PY_1_CE doesnot have BEGDA and ENDDA populated.

Hi All,

I am using Datasource 0HR_PY_1_CE for extraction HR Payroll detailed data.

This dataosource doesn't not have Start date and End date populated .

I wanted these dates to be used for deriving Org unit.

Can anyone put some light on this ?




Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Nov 15, 2018 at 03:51 AM

    By these dates "Start date" and "End date" you mean extractor parameters BEGDA and ENDDA? You can enhance datasource and fill these dates from input parametes.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 15, 2018 at 06:24 AM

    Hi Amruta,

    Payroll data can be tricky as it contains data for "For Period" and "In Period", meaning the employee was paid "In Period" for work that he/she did in "For Period". Typically key master data attributes are already persisted on the record however I know that we have in the past done quite a few lookups on 0EMPLOYEE.

    For e.g.

    Employee For Period In Period

    1 Jan Mar

    1 Feb Mar

    1 Mar Mar

    So you should decided if you want to look up the org unit for the "For Period" values or for the "In Period" values. We typically use the "For Period" values, and we use the end of the period for the lookup, so last day in Jan, then last day in Feb, then last day in Mar. I'm not sure if this is the answer you were looking for, hope it helps.

    Kind regards,


    Add comment
    10|10000 characters needed characters exceeded