Isse withGET statement

[amit_khare]

Hi All,

I have a reports using LDB PNPCE. It's a custom report.

The contrl is not going to GET statement in this. It's directly going to END-OF-SELECTION reading everything before GET statement.

Tables: PERNR.
NODES: PERAS.

START-OF-SELECTION.
**--Get first date & last date of month
  PERFORM get_first_last_date_month CHANGING w_strdate
                                             w_enddate.

**--Get Employees data
GET peras.
**--Code

END-OF-SELECTION

Please suggest.

[Former Member]

Hi Amit,

I think you will have to use GET PERNR instead of GET PERAS. PERNR is the main high level node in this ldb.

regards,

amit m.

[amit_khare]

Hi Amit,

Thanks for reply.

PERAS will work with PNPCE.

As use of the 'GET PERNR' event is forbidden in this case.

But don't know what the issue is here, its not going to that line.

[Former Member]

Hi again,

I just tried, and it is working fine.

The event sequence is;

start-of-selection.

get peras. -

---

multiple times

end-of-selection.

Just copy paste to get a feel of it.

report abc.

tables : pernr.
nodes : peras.


start-of-selection.
write :/ 'start of selection'.

get peras.
write 'peras event '.


end-of-selection.
write :/ 'end of selection'.

regards,

amit m.

[amit_khare]

Hi,

Yeah it wok fine and same is working on couple of reports other reports also.

Its only giving problem in this object. Can't do much as its a copy of a standard report.

Changing the code to read from PNP Logical Database.

[Former Member]

Hello Amit,

Is the issue with the Subroutine???

Sas

[amit_khare]

No.

The control is going directly to END-OF SELECTION ihout going to GET statement.

Its reading everything written before GET in START-OF-SELECTION and after executing the last command before GET, control will go directly to END-OF-SELECTION.

[Former Member]

Ok Let clarify 2 things...

1) Do you have selection-screen for that? If so what inputs are u giving?

2) Sometimes due to Authorisation issues it may happen ( The same happend once ) so try to check with other diff SAP- ID'S...

3) Is the issue with only this report using PERAS or any other reports are also having same issue when using peras??

Regards

sas

Amit Did you check things?????

Edited by: saslove sap on Jan 25, 2010 7:23 AM