SAP ISP_DFIELD_MODIFICATION Function Module for IS-M: Field Modification for Individual Screen Field ('Static')
ISP_DFIELD_MODIFICATION is a standard isp dfield modification 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: Field Modification for Individual Screen Field ('Static') 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 isp dfield modification FM, simply by entering the name ISP_DFIELD_MODIFICATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: J0DM
Program Name: SAPLJ0DM
Main Program: SAPLJ0DM
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_DFIELD_MODIFICATION 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 'ISP_DFIELD_MODIFICATION'"IS-M: Field Modification for Individual Screen Field ('Static')
EXPORTING
ACTION = "
PROGNAME = "
EXCEPTIONS
INVALID_ACTION = 1 .IMPORTING Parameters details for ISP_DFIELD_MODIFICATION
ACTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGNAME -
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_ACTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_DFIELD_MODIFICATION 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_action | TYPE STRING, " | |||
| lv_invalid_action | TYPE STRING, " | |||
| lv_progname | TYPE SY-REPID. " |
|   CALL FUNCTION 'ISP_DFIELD_MODIFICATION' "IS-M: Field Modification for Individual Screen Field ('Static') |
| EXPORTING | ||
| ACTION | = lv_action | |
| PROGNAME | = lv_progname | |
| EXCEPTIONS | ||
| INVALID_ACTION = 1 | ||
| . " ISP_DFIELD_MODIFICATION | ||
ABAP code using 7.40 inline data declarations to call FM ISP_DFIELD_MODIFICATION
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 REPID FROM SY INTO @DATA(ld_progname). | ||||
Search for further information about these or an SAP related objects