topic Re: No Filtering while using PNP DB in Application Development and Automation Discussions

No Filtering while using PNP DB

RahulKeshav — Wed, 10 Sep 2008 06:41:25 GMT

HI all,

I am using PNP DB to get the HR data...

I m giving the data range in the std selection screen ...

but it is not filtering the data on the basis of data range....

it is giving all the data which are present in the DB...

plz help me in trobleshooting the problemm....

thnx

Rohit

Re: No Filtering while using PNP DB

RahulKeshav — Wed, 10 Sep 2008 10:23:28 GMT

any expert ......

Re: No Filtering while using PNP DB

Former Member — Wed, 10 Sep 2008 10:30:07 GMT

Hi,

Make sure that, Master Data field is empty or not in Attributes.

goto attributes, click on 'HR Report category'

now make sure that, 'Master Data (Infotype)' is empty or not.

If its value is : ______03, some data retrieval is not done.

hopefull, it will be helpfull to you.

Regards

Sai

Re: No Filtering while using PNP DB

RahulKeshav — Thu, 11 Sep 2008 10:29:09 GMT

no man its still not working.....

Re: No Filtering while using PNP DB

RahulKeshav — Wed, 17 Sep 2008 10:46:35 GMT

thnx experts for not repling.....

Re: No Filtering while using PNP DB

former_member181966 — Wed, 17 Sep 2008 12:19:53 GMT

Can you post your code? So we can look and suggest you something .. hmmmm

 

Example 

In your prog attr : PNP 

REPORT  Ypnp.
tables:pernr.

infotypes:0001,
          0002.

START-OF-SELECTION.
*reading logical database PNP with pernr node

GET PERNR .


* Reading pa0001 using macro

  RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.

  IF PNP-SW-FOUND  = 1. " if found = 1, otheriwse '0'

    YOURTAB-FIELD = P0001-PERSK.

  ENDIF.


  RP_PROVIDE_FROM_LAST P0002 SPACE PN-BEGDA PN-ENDDA.

  IF PNP-SW-FOUND  = 1. " if found = 1, otheriwse '0'

    YOURTAB-FIELD1 = P0002-NACHN.

  ENDIF.

  APPEND YOURTAB .

END-OF-SELECTION.
Perform write_output.

^ Saquib

Re: No Filtering while using PNP DB

Former Member — Wed, 17 Sep 2008 12:25:04 GMT

pass ur selection screen data like p_begda, p_endda to PN-BEGDA, PN-ENDDA before get pernr event.

It will restrict get pernr event from fetching all the data.

Re: No Filtering while using PNP DB

RahulKeshav — Wed, 17 Sep 2008 12:55:40 GMT

Thnx for replying SK....

my code is like this...

INFOTYPES: 0000, "Action

0001,

0002, "Personal Data

0006, "Address

0008,

1001,

0105, "Communication

0041. "Date Specification

9000.

*----

TABLES

*----

TABLES: "pernr, "Standard Selections for HR Master Dat

t510,

pa0000,

hrp1001.

TYPE-POOLS: slis.

......

..........

START-OF-SELECTION .

*Fetch Data from LDAP / Active Directory Server for reconcilation

PERFORM get_ldap_data.

*Get SAP HR data

rp_set_data_interval 'P0002' PN-BEGDA PN-endda.

rp-set-name-format.

GET pernr.

PERFORM get_sap_data.

rp_provide_from_last p0002 space PN-BEGDA pn-endda.

IF PNP-SW-FOUND = 1.

get last name

MOVE p0002-nachn TO g_nachn.

*get first name

MOVE p0002-vorna TO g_vorna.

endif.

....do the selection screen makes any differance....

i m using std one.....

plz suggest...

and amit Gupta ---i am passing the values as shown above....as it is...

Edited by: Rohit Kumar on Sep 17, 2008 6:26 PM

Re: No Filtering while using PNP DB

former_member181966 — Wed, 17 Sep 2008 13:18:50 GMT

Comment the following and try ..

*Get SAP HR data

rp_set_data_interval 'P0002' PN-BEGDA PN-endda.

Iu2019ve seen wired behavior with above macro in past .

Also Iu2019m assuming that you are selecting all of the data after Get pernr event.

Good luck !

^ Saquib

Re: No Filtering while using PNP DB

Former Member — Wed, 17 Sep 2008 14:11:41 GMT

THIS CODE CAN BE USED TO RESTRICT GET PERNR EVENT TO LOOP ONLY FOR PERNR MENTIONED IN SELECT OPTIONS

TABLES: PERNR.

SELECT-OPTIONS: R_PERNR FOR PERNR-PERNR.

START-OF-SELECTION.

PNPPERNR = R_PERNR.

GET PERNR.

WRITE: / PERNR-PERNR.

END-OF-SELECTION.

Re: No Filtering while using PNP DB

Former Member — Thu, 18 Sep 2008 04:38:06 GMT


> Thnx for replying SK....
> my code is like this...
> 
> INFOTYPES: 0000, "Action
>            0001,
>            0002, "Personal Data
>            0006, "Address
>            0008,
>            1001,
>            0105, "Communication
>            0041. "Date Specification
> *           9000.
> *----
> * TABLES
> *----
> TABLES: "pernr,                            "Standard Selections for HR Master Dat
>         t510,
>         pa0000,
>         hrp1001.
> 
> TYPE-POOLS: slis.
> -
> -
......
> ..........
> 
> START-OF-SELECTION .
> *Fetch Data from LDAP / Active Directory Server for reconcilation
>   PERFORM get_ldap_data.
> 
> *Get SAP HR data
>   rp_set_data_interval 'P0002' PN-BEGDA PN-endda.
>   rp-set-name-format.
> 
> GET pernr.
>   PERFORM get_sap_data.
> 
> rp_provide_from_last p0002 space PN-BEGDA pn-endda.
>   IF PNP-SW-FOUND  = 1.
> * get last name
>     MOVE p0002-nachn TO g_nachn.
> *get first name
>     MOVE p0002-vorna TO g_vorna.
>   endif.
> 
> ....do  the selection screen makes any differance....
> 
> i m using std one.....
> 
> plz suggest...
> 
> 
> and amit Gupta ---i am passing the values as shown above....as it is...
> 
> Edited by: Rohit Kumar on Sep 17, 2008 6:26 PM

Hi Rohit

The code is working fine for me, could you please post the values of pn-begda and pn-endda and the data(key fields) returned by LDB into the internal table P0002 and let us know as why you think LDB is not restricting the data. Here is the code that i've tested


REPORT zytest.
INFOTYPES: 0000, " Actions
0001,            " Org Assignment
0002,            " Personal Data
0006,            " Address
0008,            " Basic Pay
1001,            " Relationships
0070,            " Court orders
0105,            " Communication
0041.            " Date Specification

*9000.
*---------------------------------------------------------------------

*TABLES
*---------------------------------------------------------------------
TABLES: pernr, "Standard Selections for HR Master Dat
t510,
pa0000,
hrp1001.

TYPE-POOLS: slis.

START-OF-SELECTION .
*Fetch Data from LDAP / Active Directory Server for reconcilation
*PERFORM get_ldap_data.

*Get SAP HR data
  rp_set_data_interval 'P0002' pn-begda pn-endda.
  rp-set-name-format.

GET pernr.
*PERFORM get_sap_data.

  rp_provide_from_last p0002 space pn-begda pn-endda.
  IF pnp-sw-found = 1.

*get last name
*MOVE p0002-nachn TO g_nachn.
**get first name
*MOVE p0002-vorna TO g_vorna.
  ENDIF.REPORT zytest.
INFOTYPES: 0000, " Actions
0001,            " Org Assignment
0002,            " Personal Data
0006,            " Address
0008,            " Basic Pay
1001,            " Relationships
0070,            " Court orders
0105,            " Communication
0041.            " Date Specification

*9000.
*---------------------------------------------------------------------

*TABLES
*---------------------------------------------------------------------
TABLES: pernr, "Standard Selections for HR Master Dat
t510,
pa0000,
hrp1001.

TYPE-POOLS: slis.

START-OF-SELECTION .
*Fetch Data from LDAP / Active Directory Server for reconcilation
*PERFORM get_ldap_data.

*Get SAP HR data
  rp_set_data_interval 'P0002' pn-begda pn-endda.
  rp-set-name-format.

GET pernr.
*PERFORM get_sap_data.

  rp_provide_from_last p0002 space pn-begda pn-endda.
  IF pnp-sw-found = 1.

*get last name
*MOVE p0002-nachn TO g_nachn.
**get first name
*MOVE p0002-vorna TO g_vorna.
  ENDIF.

Re: No Filtering while using PNP DB

RahulKeshav — Fri, 19 Sep 2008 05:36:09 GMT

Hi Rajesh,,

the value in PN-BEGDA & PN-ENDDA...is the same which is i m entering in the selection screen...

Re: No Filtering while using PNP DB

RahulKeshav — Fri, 19 Sep 2008 05:37:46 GMT

Hi SK,

i commented it but didnt work...

Re: No Filtering while using PNP DB

RahulKeshav — Fri, 19 Sep 2008 05:41:01 GMT

Hi Amit,

i tried that also...

i jst copied ur code and tried alone ....bt still there is problem...

i think ther must be some problem with sonfig...

plz suggest me...

Re: No Filtering while using PNP DB

Former Member — Fri, 19 Sep 2008 09:15:00 GMT


> Hi Rajesh,,
> 
> the value in PN-BEGDA & PN-ENDDA...is the same which is i m entering in the selection screen...

Hi Rohit,

Could you please post the values of pn-begda, pn-endda and the values of the key fields in the records returned by the LDB into the internal table P0002

Re: No Filtering while using PNP DB

RahulKeshav — Fri, 19 Sep 2008 10:02:33 GMT

as shown while debugging...

the value which i have entered in selection screen :

PN-BEGDA 20080901

PN-endda 20080919

and in p0002:

PERNR INFTY SUBTY OBJPS SPRPS ENDDA BEGDA SEQNR AEDTM

00000010|0002 | | | |99991231|19670522| 000 |

00000010|0002 | | | |99991231|19670522| 000 | 20030

there is problem it is taking begda from begining....

plz suggest ....

Re: No Filtering while using PNP DB

KK07 — Fri, 19 Sep 2008 10:10:19 GMT

hi Rohit,

Retrieving the Data by 'Get Pernr' will not restrict the data.

The whole data for a pernr will be retrieved at the Get pernr event no matter of ur pn-begda and pn-endda.

if u want to filter the data u have to use the macro's.

Re: No Filtering while using PNP DB

former_member181966 — Fri, 19 Sep 2008 10:56:39 GMT

Iu2019d say perform the following checks.

~ Take employee # and run it for other period option

~ Look at employee data (all ITs you are accessing in your program one by one closely with open eyes, pay attention to dates u201C.

~ Run report and debug it and look data for every IT and make sure it is picking up all the records as period specified in report . Compare them with PA20/PA30 .

~ At last , see what you are getting in internal table .

~ If problem still exist , Comment any code before START-OF-SELECTION event .

~ Just use "Get Pernr" and write statement . Comment ALL ITs and just run it for one IT at a time .

Iu2019m sure , youu2019ll find what is really going wrong .

Good Luck !

^Saquib

Re: No Filtering while using PNP DB

Former Member — Sun, 21 Sep 2008 09:56:03 GMT


> as shown while debugging...
> 
> the value which i have entered in selection screen :
> PN-BEGDA                       20080901
> PN-endda                         20080919     
> 
> 
> 
> and in p0002:
> 
> 
> PERNR    INFTY SUBTY OBJPS SPRPS ENDDA    BEGDA    SEQNR AEDTM
> 
> 00000010|0002      |      |             |            |99991231|19670522| 000  |
> 00000010|0002 |          |     |                     |99991231|19670522| 000  | 20030
> 
> 
> there is problem it is taking begda from begining....
> 
> plz suggest ....

Hi Rohit

The records returned by the LDB are absolutely fine, i don't see any issue with them, since the 2 records are valid in the date range given in the selection screen(pn-begda, pn-endda) the LDB returned those 2 records this is the expected behaviour of the system and the macro

rp_set_data_interval is working as it should be.

If you want to analyze the macro(rp_set_data_interval), delimit any of the 2 records returned by the LDB such that the enddate of the record is before pn-begda(20080901), now the LDB will not return the delimited record as the enddate of the record does not fall in the interval pn-begda, pn-endda.

@Krishna Kishore : I totally agree with you, here in the example provided by Rohit as we are using the macro rp_set_data_interval we expect that the LDB should limit the records returned to the date range given in the selection screen(pn-begda, pn-endda) instead of returning all the records of the pernr.

One more option to totally restrict the records returned by the LDB is to add "MODE N" in the Infotypes declaration

itself. Please, check the link below

http://help.sap.com/saphelp_47x200/helpdata/en/4f/d527fb575e11d189270000e8322f96/content.htm

Regards

Rajesh.