SAP ISM_PARTNER_OK_CODE_SET Function Module for IS-M/AM: Provide Function Codes from Partner Subscreen
ISM_PARTNER_OK_CODE_SET is a standard ism partner ok code set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: Provide Function Codes from Partner Subscreen 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 ism partner ok code set FM, simply by entering the name ISM_PARTNER_OK_CODE_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHPD
Program Name: SAPLJHPD
Main Program: SAPLJHPD
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_PARTNER_OK_CODE_SET 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 'ISM_PARTNER_OK_CODE_SET'"IS-M/AM: Provide Function Codes from Partner Subscreen.
EXPORTING
PV_OK_CODE = "
* PV_FLG_STP_CHANGED = "
IMPORTING Parameters details for ISM_PARTNER_OK_CODE_SET
PV_OK_CODE -
Data type: T185F-FCODEOptional: No
Call by Reference: Yes
PV_FLG_STP_CHANGED -
Data type: XFELDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISM_PARTNER_OK_CODE_SET 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_pv_ok_code | TYPE T185F-FCODE, " | |||
| lv_pv_flg_stp_changed | TYPE XFELD. " |
|   CALL FUNCTION 'ISM_PARTNER_OK_CODE_SET' "IS-M/AM: Provide Function Codes from Partner Subscreen |
| EXPORTING | ||
| PV_OK_CODE | = lv_pv_ok_code | |
| PV_FLG_STP_CHANGED | = lv_pv_flg_stp_changed | |
| . " ISM_PARTNER_OK_CODE_SET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_PARTNER_OK_CODE_SET
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 FCODE FROM T185F INTO @DATA(ld_pv_ok_code). | ||||
Search for further information about these or an SAP related objects