SAP SRET_IDXCAT_PHYS_DELETE Function Module for

Search SAP Function Modules

SRET_IDXCAT_PHYS_DELETE is a standard sret idxcat phys delete 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 sret idxcat phys delete FM, simply by entering the name SRET_IDXCAT_PHYS_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function SRET_IDXCAT_PHYS_DELETE 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 'SRET_IDXCAT_PHYS_DELETE'"
  EXPORTING
   CATID =  "

EXCEPTIONS
   CATID_UNKNOWN = 1    ERR_DEL_CATATR = 10    ERR_DEL_CATID = 11    NO_RFC_DEST = 2    DEL_ERROR = 3    IDXCAT_IS_INACTIVE = 4    RFC_SYS_FAILURE = 5    RFC_COM_FAILURE = 6    XERROR = 7    ERR_DEL_LANG = 8    ERR_DEL_DOCATR = 9 

.

IMPORTING Parameters details for SRET_IDXCAT_PHYS_DELETE

CATID -

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

EXCEPTIONS details

CATID_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

ERR_DEL_CATATR -

Data type:
Optional: No
Call by Reference: Yes

ERR_DEL_CATID -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_DEST -

Data type:
Optional: No
Call by Reference: Yes

DEL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

IDXCAT_IS_INACTIVE -

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

RFC_SYS_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

RFC_COM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

XERROR - Unknown Error

Data type:
Optional: No
Call by Reference: Yes

ERR_DEL_LANG -

Data type:
Optional: No
Call by Reference: Yes

ERR_DEL_DOCATR -

Data type:
Optional: No
Call by Reference: Yes

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

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