SAP LE_PAD_PUT Function Module for NOTRANSL: Sammeln der Findungs-Protokolldaten

Search SAP Function Modules

LE_PAD_PUT is a standard le pad put 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: Sammeln der Findungs-Protokolldaten 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 put FM, simply by entering the name LE_PAD_PUT into the relevant SAP transaction such as SE37 or SE38.

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

Function LE_PAD_PUT 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_PUT'"NOTRANSL: Sammeln der Findungs-Protokolldaten
  EXPORTING
*  FIELD1 = 'DEFAULT' "
*  VBELN2 = '9999999999' "
*  POSNR2 = '999999' "
*  ORIGIN2 =  "
*  TUERZU =  "
*  VALUE1 = '?' "
*  FNAME1 = 'FIELD1' "
*  VBELN1 = '9999999999' "
*  POSNR1 = '999999' "
*  ORIGIN1 =  "
   FIELD2 =  "
   VALUE2 =  "
*  FNAME2 = 'FIELD2' "

.

IMPORTING Parameters details for LE_PAD_PUT

FIELD1 -

Data type:
Default: 'DEFAULT'
Optional: Yes
Call by Reference: Yes

VBELN2 -

Data type: V53F_PLACE-VBELN
Default: '9999999999'
Optional: Yes
Call by Reference: Yes

POSNR2 -

Data type: V53F_PLACE-POSNR
Default: '999999'
Optional: Yes
Call by Reference: Yes

ORIGIN2 -

Data type: V53F_DFIP-L-ORIGIN
Optional: Yes
Call by Reference: Yes

TUERZU -

Data type: V53F_DFIP-TUERZU
Optional: Yes
Call by Reference: Yes

VALUE1 -

Data type:
Default: '?'
Optional: Yes
Call by Reference: Yes

FNAME1 -

Data type:
Default: 'FIELD1'
Optional: Yes
Call by Reference: Yes

VBELN1 -

Data type: V53F_PLACE-VBELN
Default: '9999999999'
Optional: Yes
Call by Reference: Yes

POSNR1 -

Data type: V53F_PLACE-POSNR
Default: '999999'
Optional: Yes
Call by Reference: Yes

ORIGIN1 -

Data type: V53F_DFIP-L-ORIGIN
Optional: Yes
Call by Reference: Yes

FIELD2 -

Data type:
Optional: No
Call by Reference: Yes

VALUE2 -

Data type:
Optional: No
Call by Reference: Yes

FNAME2 -

Data type:
Default: 'FIELD2'
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LE_PAD_PUT 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_PUT

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