SAP ISU_PS_ACTIVATE_R517 Function Module for Activation of Payment Schemes
ISU_PS_ACTIVATE_R517 is a standard isu ps activate r517 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Activation of Payment Schemes 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 isu ps activate r517 FM, simply by entering the name ISU_PS_ACTIVATE_R517 into the relevant SAP transaction such as SE37 or SE38.
Function Group: EA61PS
Program Name: SAPLEA61PS
Main Program: SAPLEA61PS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_PS_ACTIVATE_R517 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 'ISU_PS_ACTIVATE_R517'"Activation of Payment Schemes.
EXPORTING
X_OBJ = "
X_ACTIVDATE = "Date
IMPORTING
Y_ACTIVATE = "Indicator
EXCEPTIONS
NOT_ACTIVATED = 1
IMPORTING Parameters details for ISU_PS_ACTIVATE_R517
X_OBJ -
Data type: ISU25_PAYMENTSCHEMEOptional: No
Call by Reference: Yes
X_ACTIVDATE - Date
Data type: DATUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_PS_ACTIVATE_R517
Y_ACTIVATE - Indicator
Data type: REGEN-KENNZXOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_ACTIVATED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_PS_ACTIVATE_R517 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_x_obj | TYPE ISU25_PAYMENTSCHEME, " | |||
| lv_y_activate | TYPE REGEN-KENNZX, " | |||
| lv_not_activated | TYPE REGEN, " | |||
| lv_x_activdate | TYPE DATUM. " |
|   CALL FUNCTION 'ISU_PS_ACTIVATE_R517' "Activation of Payment Schemes |
| EXPORTING | ||
| X_OBJ | = lv_x_obj | |
| X_ACTIVDATE | = lv_x_activdate | |
| IMPORTING | ||
| Y_ACTIVATE | = lv_y_activate | |
| EXCEPTIONS | ||
| NOT_ACTIVATED = 1 | ||
| . " ISU_PS_ACTIVATE_R517 | ||
ABAP code using 7.40 inline data declarations to call FM ISU_PS_ACTIVATE_R517
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 KENNZX FROM REGEN INTO @DATA(ld_y_activate). | ||||
Search for further information about these or an SAP related objects