SAP EXIT_FUSITST_001 Function Module for
EXIT_FUSITST_001 is a standard exit fusitst 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 exit fusitst 001 FM, simply by entering the name EXIT_FUSITST_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XPSI
Program Name: SAPLXPSI
Main Program: SAPLXPSI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_FUSITST_001 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 'EXIT_FUSITST_001'".
EXPORTING
PERNR = "
PAYTY = "
PAYID = "
BONDT = "
CHANGING
BASE = "
MNTH = "
SHIFT = "
IMPORTING Parameters details for EXIT_FUSITST_001
PERNR -
Data type: PERNR-PERNROptional: No
Call by Reference: Yes
PAYTY -
Data type: PC261-PAYTYOptional: No
Call by Reference: Yes
PAYID -
Data type: PC261-PAYIDOptional: No
Call by Reference: Yes
BONDT -
Data type: PC261-BONDTOptional: No
Call by Reference: Yes
CHANGING Parameters details for EXIT_FUSITST_001
BASE -
Data type: PC207-BETRGOptional: No
Call by Reference: Yes
MNTH -
Data type: IOptional: No
Call by Reference: Yes
SHIFT -
Data type: IOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_FUSITST_001 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_base | TYPE PC207-BETRG, " | |||
| lv_pernr | TYPE PERNR-PERNR, " | |||
| lv_mnth | TYPE I, " | |||
| lv_payty | TYPE PC261-PAYTY, " | |||
| lv_payid | TYPE PC261-PAYID, " | |||
| lv_shift | TYPE I, " | |||
| lv_bondt | TYPE PC261-BONDT. " |
|   CALL FUNCTION 'EXIT_FUSITST_001' " |
| EXPORTING | ||
| PERNR | = lv_pernr | |
| PAYTY | = lv_payty | |
| PAYID | = lv_payid | |
| BONDT | = lv_bondt | |
| CHANGING | ||
| BASE | = lv_base | |
| MNTH | = lv_mnth | |
| SHIFT | = lv_shift | |
| . " EXIT_FUSITST_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_FUSITST_001
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 BETRG FROM PC207 INTO @DATA(ld_base). | ||||
| "SELECT single PERNR FROM PERNR INTO @DATA(ld_pernr). | ||||
| "SELECT single PAYTY FROM PC261 INTO @DATA(ld_payty). | ||||
| "SELECT single PAYID FROM PC261 INTO @DATA(ld_payid). | ||||
| "SELECT single BONDT FROM PC261 INTO @DATA(ld_bondt). | ||||
Search for further information about these or an SAP related objects