[HR-PY] Querying PNP LDB infotype - wise

Question

Hello !
I got a question about optimizing data fetching from LDB.
Nowdays i do something like :
INFOTYPES: 0657.
GET pernr.
LOOP AT P0657 WHERE somefield IN criteria.
"do stuff here
ENDLOOP.
Problem with this approach is Preformance - i only want to process records that have IT0657 entry - but since no select options are given on screen GET pernr fetches every personal number - is there any way to restrict that ?
i know i could do SELECT to db and then insert its results as LDB params to loop only on the relevant records - problem with that is that my Selection Options regarding PERNR in LDB get lost that way - is there something more accurate ?

Answer 1

Can P0657 be queried with OpenSQL as usual ?
Yes.
i guess with mode N the only diffrence between LDB and physical DB is that LDB results are filtered by provided selection screen ?
Correct
Does PNP have any other nodes than PERNR ? how do i know what nodes i can use ?
Go to SE36-> type in PNP -> here you have all nodes available in PNP -> select PERNR and choose table icon
or
Go to SE11-> structure PERNR
All these fields are transported during GET PERNR event, so always try to restrict them to those which you really need
Can you please give some example of such query - it's my 1st approach to LDBs and i dont know how to deal with it exactly.
SELECT-OPTIONS so FOR field.
INFOTYPES: 0657 mode n. "table empty at GET pernr event.
GET PERNR FIELDS pernr ....
  SELECT field field2 field3 FROM PA0657 into corresponding fields of table PA0657
                                                                              where pernr = pernr-pernr
                                                                                and field in so.
if sy-dbcnt = 0.
   "entry exists
else.
  "no entry
   REJECT.  "reject EE and proceed to next node -> here next PERNR
endif.
This could help a litte bit with performamance but I think the best would be filtering at LDB level, so using select options for payrol area, company code, org unit, cost center etc (all Emoplyees processing should really never been performed, because it is time intensive) . Also giving dates PNPBEGDS and PNPENDDS restricts picking EEs to those who are at least one day active (PA0000-stat2 = 3) within this date range. On the other hand, PNPBEGDA and PNPENDDA only restrict fetching infotype table, so here it is of no relevance as we instructed it not to do it (mode N).
Regards
Marcin