SAP SPAM_READ_PATCH_TABLES Function Module for

Search SAP Function Modules

SPAM_READ_PATCH_TABLES is a standard spam read patch tables SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 spam read patch tables FM, simply by entering the name SPAM_READ_PATCH_TABLES into the relevant SAP transaction such as SE37 or SE38.

Function Group: OCS_CORE
Program Name: SAPLOCS_CORE
Main Program: SAPLOCS_CORE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SPAM_READ_PATCH_TABLES 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 'SPAM_READ_PATCH_TABLES'"
  EXPORTING
*  READ_PAT01 =  "
*  READ_PAT02 =  "
*  READ_PAT03 =  "
*  READ_PAT06 =  "
*  READ_PAT07 =  "
*  READ_PAT08 =  "

 IMPORTING
   PAT01_ENTRIES =  "
   PAT02_ENTRIES =  "
   PAT03_ENTRIES =  "
   PAT06_ENTRIES =  "
   PAT07_ENTRIES =  "
   PAT08_ENTRIES =  "

TABLES
*  PAT01_LIST =  "
*  PAT02_LIST =  "
*  PAT03_LIST =  "
*  PAT06_LIST =  "
*  PAT07_LIST =  "
*  PAT08_LIST =  "

.

IMPORTING Parameters details for SPAM_READ_PATCH_TABLES

READ_PAT01 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_PAT02 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_PAT03 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_PAT06 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_PAT07 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_PAT08 -

Data type: PAT03-STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SPAM_READ_PATCH_TABLES

PAT01_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

PAT02_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

PAT03_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

PAT06_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

PAT07_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

PAT08_ENTRIES -

Data type: SY-DBCNT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SPAM_READ_PATCH_TABLES

PAT01_LIST -

Data type: PAT01
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAT02_LIST -

Data type: PAT02
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAT03_LIST -

Data type: PAT03
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAT06_LIST -

Data type: PAT06
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAT07_LIST -

Data type: PAT07
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAT08_LIST -

Data type: PAT08
Optional: Yes
Call by Reference: No ( called with pass by value option)

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

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