Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

requirement to replace select statements

Former Member
0 Kudos

Hi,

We have to replace this query with macro RP_READ_INFOTYPE or funtiopn module HR_READ_INFOTYPE, also we dont need LDBs. so i have included DBPNPMAC too.

select single nachn

from pa0002

into name

where pernr EQ l_pernr.

i have tried with the following but still not working..

(i took additional values for Date variables)

rp_read_infotype l_pernr 0002 p0002 so_beg so_end.

move p0002-nachn to name.

Please provide inputs on this, if anyone knows it.

Thanks in advance

3 REPLIES 3

former_member226519
Active Contributor
0 Kudos

infotypes: 0002.

data: gv_subrc like sy-subrc

call function 'HR_READ_INFOTYPE'

exporting

pernr = pernr

infty = '0002'

begda = '19000101'

endda = '99991231'

importing

subrc = gv_subrc

tables

infty_tab = p0002

exceptions

infty_not_found = 1

others = 2.

if sy-subrc <> 0.

  • should not happen

endif.

loop at p0002.

endloop.

0 Kudos

Hi All,

i cant use LDB, so in place i am trying to use 'rp_read_infotype' as below, but its not working.

INCLUDE dbpnpmac.

INFOTYPES 0002.

SELECT-OPTIONS: so_pernr FOR p0002-pernr,

so_beg FOR p0002-begda,

so_end FOR p0002-endda.

rp_read_infotype so_pernr 0002 p0002 so_beg so_end.

write 😕 'Name: ', p0002-nachn.

The error dump is as

Type conflict when calling a FORM.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was

not caught and

therefore caused a runtime error.

The reason for the exception is:

Call to FORM "READ-INFOTYPE" is incorrect:

The actual parameter no. 4 has a different data type in the

PERFORM than requested for the FORM "READ-INFOTYPE" in program "SAPDBPNP".

Please help if anybody has done this earlier

Thanks in advance

Former Member
0 Kudos

Solved