SAP RFC_RP_BSIU_RTXRD Function Module for HR-US: Remote Function Call to list Reciprocal Taxes supported by BSI
RFC_RP_BSIU_RTXRD is a standard rfc rp bsiu rtxrd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HR-US: Remote Function Call to list Reciprocal Taxes supported by BSI processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for rfc rp bsiu rtxrd FM, simply by entering the name RFC_RP_BSIU_RTXRD into the relevant SAP transaction such as SE37 or SE38.
Function Group: PBSI
Program Name: SAPLPBSI
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RFC_RP_BSIU_RTXRD pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'RFC_RP_BSIU_RTXRD'"HR-US: Remote Function Call to list Reciprocal Taxes supported by BSI.
EXPORTING
AUTHORITYCODE = "
EFFECTIVEDATE = "
IMPORTING
RTXRDMESSAGE = "
IMPORTING Parameters details for RFC_RP_BSIU_RTXRD
AUTHORITYCODE -
Data type: PBSI_X0-AUTH_CODEOptional: No
Call by Reference: No ( called with pass by value option)
EFFECTIVEDATE -
Data type: PBSI_X1-CHECK_DATEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RFC_RP_BSIU_RTXRD
RTXRDMESSAGE -
Data type: PBSI_X2-MSG_AREAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RFC_RP_BSIU_RTXRD Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_rtxrdmessage | TYPE PBSI_X2-MSG_AREA, " | |||
| lv_authoritycode | TYPE PBSI_X0-AUTH_CODE, " | |||
| lv_effectivedate | TYPE PBSI_X1-CHECK_DATE. " |
|   CALL FUNCTION 'RFC_RP_BSIU_RTXRD' "HR-US: Remote Function Call to list Reciprocal Taxes supported by BSI |
| EXPORTING | ||
| AUTHORITYCODE | = lv_authoritycode | |
| EFFECTIVEDATE | = lv_effectivedate | |
| IMPORTING | ||
| RTXRDMESSAGE | = lv_rtxrdmessage | |
| . " RFC_RP_BSIU_RTXRD | ||
ABAP code using 7.40 inline data declarations to call FM RFC_RP_BSIU_RTXRD
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single MSG_AREA FROM PBSI_X2 INTO @DATA(ld_rtxrdmessage). | ||||
| "SELECT single AUTH_CODE FROM PBSI_X0 INTO @DATA(ld_authoritycode). | ||||
| "SELECT single CHECK_DATE FROM PBSI_X1 INTO @DATA(ld_effectivedate). | ||||
Search for further information about these or an SAP related objects