SAP SHP_DLFLD_UPDATE Function Module for NOTRANSL: Aufruf der Fortschreibung der DLFLD-Daten auf der Datenbank
SHP_DLFLD_UPDATE is a standard shp dlfld update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufruf der Fortschreibung der DLFLD-Daten auf der Datenbank 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 shp dlfld update FM, simply by entering the name SHP_DLFLD_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V50B
Program Name: SAPLV50B
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SHP_DLFLD_UPDATE 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 'SHP_DLFLD_UPDATE'"NOTRANSL: Aufruf der Fortschreibung der DLFLD-Daten auf der Datenbank.
EXPORTING
* IF_SYNCHRON = ' ' "Perform synchronous update
* IT_DLFLD_KEY = "
IMPORTING Parameters details for SHP_DLFLD_UPDATE
IF_SYNCHRON - Perform synchronous update
Data type: V50AGL-SYNCHRONDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_DLFLD_KEY -
Data type: V50B_DLFLD_KEY_TOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SHP_DLFLD_UPDATE 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_if_synchron | TYPE V50AGL-SYNCHRON, " SPACE | |||
| lv_it_dlfld_key | TYPE V50B_DLFLD_KEY_T. " |
|   CALL FUNCTION 'SHP_DLFLD_UPDATE' "NOTRANSL: Aufruf der Fortschreibung der DLFLD-Daten auf der Datenbank |
| EXPORTING | ||
| IF_SYNCHRON | = lv_if_synchron | |
| IT_DLFLD_KEY | = lv_it_dlfld_key | |
| . " SHP_DLFLD_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM SHP_DLFLD_UPDATE
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 SYNCHRON FROM V50AGL INTO @DATA(ld_if_synchron). | ||||
| DATA(ld_if_synchron) | = ' '. | |||
Search for further information about these or an SAP related objects