SAP LE_PAD_SAVE Function Module for NOTRANSL: Findungsprotokolldaten in INDX schreiben

Search SAP Function Modules

LE_PAD_SAVE is a standard le pad save 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: Findungsprotokolldaten in INDX schreiben 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 le pad save FM, simply by entering the name LE_PAD_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: V53F
Program Name: SAPLV53F
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LE_PAD_SAVE 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 'LE_PAD_SAVE'"NOTRANSL: Findungsprotokolldaten in INDX schreiben
  EXPORTING
   IS_LIKP =  "SD Document: Delivery Header Data
   IS_V50AGL =  "Global Delivery Control Flags
   IS_VBSK =  "Collective Processing for a Sales Document Header

.

IMPORTING Parameters details for LE_PAD_SAVE

IS_LIKP - SD Document: Delivery Header Data

Data type: LIKP
Optional: No
Call by Reference: Yes

IS_V50AGL - Global Delivery Control Flags

Data type: V50AGL
Optional: No
Call by Reference: Yes

IS_VBSK - Collective Processing for a Sales Document Header

Data type: VBSK
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LE_PAD_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM LE_PAD_SAVE

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