OIUH_RDLQ510 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name OIUH_RDLQ510 into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
OIUH_RDLQ510
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'OIUH_RDLQ510' "Business Logic for OIUH_RD02
EXPORTING
p_warning_ind = "
p_rb_sys_no = "
p_xfer_am = "
p_rem_no = "
p_rem_seq_no = "
p_prod_cd = "
p_sales_dt = "
p_prop_no = "
p_doi_no = "
p_mp_no = "
p_rb_ver_no = "
p_co_no = "
p_user_id = "
p_resp_no = "
EXCEPTIONS
GOBACK = 1 "
WARNING = 2 "
FAILED = 3 "
. " OIUH_RDLQ510
The ABAP code below is a full code listing to execute function module OIUH_RDLQ510 including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).
DATA(ld_p_warning_ind) = 'some text here'.
DATA(ld_p_rb_sys_no) = 'some text here'.
DATA(ld_p_xfer_am) = 'some text here'.
DATA(ld_p_rem_no) = 'some text here'.
DATA(ld_p_rem_seq_no) = 'some text here'.
DATA(ld_p_prod_cd) = 'some text here'.
DATA(ld_p_sales_dt) = 'some text here'.
DATA(ld_p_prop_no) = 'some text here'.
DATA(ld_p_doi_no) = 'some text here'.
DATA(ld_p_mp_no) = 'some text here'.
DATA(ld_p_rb_ver_no) = 'some text here'.
DATA(ld_p_co_no) = 'some text here'.
DATA(ld_p_user_id) = 'some text here'.
DATA(ld_p_resp_no) = 'some text here'. . CALL FUNCTION 'OIUH_RDLQ510' EXPORTING p_warning_ind = ld_p_warning_ind p_rb_sys_no = ld_p_rb_sys_no p_xfer_am = ld_p_xfer_am p_rem_no = ld_p_rem_no p_rem_seq_no = ld_p_rem_seq_no p_prod_cd = ld_p_prod_cd p_sales_dt = ld_p_sales_dt p_prop_no = ld_p_prop_no p_doi_no = ld_p_doi_no p_mp_no = ld_p_mp_no p_rb_ver_no = ld_p_rb_ver_no p_co_no = ld_p_co_no p_user_id = ld_p_user_id p_resp_no = ld_p_resp_no EXCEPTIONS GOBACK = 1 WARNING = 2 FAILED = 3 . " OIUH_RDLQ510
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_p_warning_ind | TYPE STRING , |
| ld_p_rb_sys_no | TYPE STRING , |
| ld_p_xfer_am | TYPE STRING , |
| ld_p_rem_no | TYPE STRING , |
| ld_p_rem_seq_no | TYPE STRING , |
| ld_p_prod_cd | TYPE STRING , |
| ld_p_sales_dt | TYPE STRING , |
| ld_p_prop_no | TYPE STRING , |
| ld_p_doi_no | TYPE STRING , |
| ld_p_mp_no | TYPE STRING , |
| ld_p_rb_ver_no | TYPE STRING , |
| ld_p_co_no | TYPE STRING , |
| ld_p_user_id | TYPE STRING , |
| ld_p_resp_no | TYPE STRING . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name OIUH_RDLQ510 or its description.