SAP FTR_FX_WEB_CHANGE_PWORD_PREP Function Module for Wrapper for Determination of New Password
FTR_FX_WEB_CHANGE_PWORD_PREP is a standard ftr fx web change pword prep SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Wrapper for Determination of New Password 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 ftr fx web change pword prep FM, simply by entering the name FTR_FX_WEB_CHANGE_PWORD_PREP into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_FX_WEB
Program Name: SAPLFTR_FX_WEB
Main Program: SAPLFTR_FX_WEB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FTR_FX_WEB_CHANGE_PWORD_PREP 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 'FTR_FX_WEB_CHANGE_PWORD_PREP'"Wrapper for Determination of New Password.
EXPORTING
PI_URL = "Uniform resource locator
PI_USER = "Logon Name of User
PI_PASSWORD = "Password
* PI_PASSWORD_NEW = "neues Password
PI_XML = "XML Formats for Transaction Management
PI_RFCDEST = "Logical Destination (Specified when Calling Function)
PI_GUID = "Globally Unique Identifier
IMPORTING
PE_PASSWORD = "Password
PE_MSGNO = "Messages, Message Number
PE_MSGTEXT = "Text, 256 Characters
PE_GUID = "Globally Unique Identifier
IMPORTING Parameters details for FTR_FX_WEB_CHANGE_PWORD_PREP
PI_URL - Uniform resource locator
Data type: URLOptional: No
Call by Reference: No ( called with pass by value option)
PI_USER - Logon Name of User
Data type: CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
PI_PASSWORD - Password
Data type: SYUNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PI_PASSWORD_NEW - neues Password
Data type: SYUNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
PI_XML - XML Formats for Transaction Management
Data type: FTR_FX_WEB_XMLOptional: No
Call by Reference: No ( called with pass by value option)
PI_RFCDEST - Logical Destination (Specified when Calling Function)
Data type: RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
PI_GUID - Globally Unique Identifier
Data type: GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_FX_WEB_CHANGE_PWORD_PREP
PE_PASSWORD - Password
Data type: SYUNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PE_MSGNO - Messages, Message Number
Data type: SYMSGNOOptional: No
Call by Reference: No ( called with pass by value option)
PE_MSGTEXT - Text, 256 Characters
Data type: TEXT256Optional: No
Call by Reference: No ( called with pass by value option)
PE_GUID - Globally Unique Identifier
Data type: GUIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_FX_WEB_CHANGE_PWORD_PREP 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_pi_url | TYPE URL, " | |||
| lv_pe_password | TYPE SYUNAME, " | |||
| lv_pi_user | TYPE CHAR32, " | |||
| lv_pe_msgno | TYPE SYMSGNO, " | |||
| lv_pe_msgtext | TYPE TEXT256, " | |||
| lv_pi_password | TYPE SYUNAME, " | |||
| lv_pe_guid | TYPE GUID, " | |||
| lv_pi_password_new | TYPE SYUNAME, " | |||
| lv_pi_xml | TYPE FTR_FX_WEB_XML, " | |||
| lv_pi_rfcdest | TYPE RFCDEST, " | |||
| lv_pi_guid | TYPE GUID. " |
|   CALL FUNCTION 'FTR_FX_WEB_CHANGE_PWORD_PREP' "Wrapper for Determination of New Password |
| EXPORTING | ||
| PI_URL | = lv_pi_url | |
| PI_USER | = lv_pi_user | |
| PI_PASSWORD | = lv_pi_password | |
| PI_PASSWORD_NEW | = lv_pi_password_new | |
| PI_XML | = lv_pi_xml | |
| PI_RFCDEST | = lv_pi_rfcdest | |
| PI_GUID | = lv_pi_guid | |
| IMPORTING | ||
| PE_PASSWORD | = lv_pe_password | |
| PE_MSGNO | = lv_pe_msgno | |
| PE_MSGTEXT | = lv_pe_msgtext | |
| PE_GUID | = lv_pe_guid | |
| . " FTR_FX_WEB_CHANGE_PWORD_PREP | ||
ABAP code using 7.40 inline data declarations to call FM FTR_FX_WEB_CHANGE_PWORD_PREP
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.Search for further information about these or an SAP related objects