Solved: Problem with 0HR_PT_2 Extraction

Former Member · ‎10-31-2009

Dear All,

I am extracting data from 0HR_PT_2 data source. For this Data Source I have also maintained Reporting Time Types.

Now the problem is the data source is extracting data but not for all employees.

Is there any other setting which I have missed.

Any inputs will be highly appreciated.

Cheers,

Neel.

Colin4 · ‎11-03-2009

Hi Neel,

Is this happening for new employees?

have a look at note 670751. The correction is already in

your system. (Please check) .

The only thing you have to do is to

activate the default implementation PTDW_CREATE_0439 of the BAdI that

was delivered with this note. (The name of the BAdI is PTDW_CREATE_0439

too).

this correction was delivered as a BAdI since at this time not all

customers agreed that new employees are taken into account

automatically. PTDW_CREATE_0439 creates infotype 439 records for

new employees automatically, only with a infotype 439 record a

personnel number is taken into account by the extractor. That means

that infotype 439 can be used to exclude personnel numbers from the

extraction, and some customers were doing so. After activating the

BAdI-Implementation this option does not exist any more, but this is

usually O.K..

In the R/3 standard, all actions that change time data either

on cluster B2 or in infotypes 2001/2002/2006/2007 will set a time

stamp in infotype 0439. These actions are PA30 on these infotype,

CATS with subsequent transfer to infotypes 200*, ESS scenarios,

Time Managers Worksplace (TMW), runs of RPTIME00.

Any specific updates on time date need to take care of

IT0439 update as well

regards,

Colin

Problem with 0HR_PT_2 Extraction