Skip to Content
0
Former Member
Jan 16, 2008 at 07:01 AM

PNP org structure restriction does not follow dates?

166 Views

Hi all,

I've a PNP report, in which I use the pop up org structure (org unit) restriction in attempt to restrict the Employees retrieved by GET PERNR.

Running the report, I notice that GET PERNR picks up employees who are no longer in the Org Units that I selected as restrictions). In debug mode I tried manually changnig the dates of pnpbegda, pnpendda, pnpbegps, pnpendps, pn-begda, pn-endda, pn-begps, pn-endps ..... but it was still retrieving employees that were no longer in the selected Org Unit.

See image link:

http://img255.imageshack.us/img255/3255/deletemeag9.gif

1) Is there a pnp date that the Org Unit restrcition follows which I am not aware of?

2) I cannot rememebr the difference between pnp***** and pn-***** dates, can someone refresh my mind?

I am currently thinking of using the following code to perform this function manually ( but I'm hoping for to use PNP to achieve the Org Units restriction to dates automatically)

GET pernr.

rp-provide-from-last p0001 space PNPBEGDA PNPENDDA.

CHECK p0001-ORGEH in PNPOBJID.

(PNPOBJID is similar to type rsrange and contains the Org Units restrictions as selected in the selection screen)

Regards,

Kevin