SAP ISU_S_LOYALACC_DELETE Function Module for INTERNAL: Delete LOYALACC

Search SAP Function Modules

ISU_S_LOYALACC_DELETE is a standard isu s loyalacc delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Delete LOYALACC 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 isu s loyalacc delete FM, simply by entering the name ISU_S_LOYALACC_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ELACC
Program Name: SAPLELACC
Main Program: SAPLELACC
Appliation area: E
Release date: 03-Feb-2000
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_S_LOYALACC_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 'ISU_S_LOYALACC_DELETE'"INTERNAL: Delete LOYALACC
  EXPORTING
   X_LPCODE =  "Object Key
   X_VKONT =  "Object Key
*  X_UPD_ONLINE =  "Indicator: Update Online
*  X_NO_DIALOG =  "Indicator: No Save Prompt

 IMPORTING
   Y_DB_UPDATE =  "Indicator: Data Change

EXCEPTIONS
   NOT_FOUND = 1    FOREIGN_LOCK = 2    CANCELLED = 3    GENERAL_FAULT = 4 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLELACC_001 IS-U: User-Defined Checks in Screen Fields
EXIT_SAPLELACC_002 IS-U: User-Defined Preassignment of Screen Fields
EXIT_SAPLELACC_003 IS-U: User Exit PBO: PBO for Customer Subscreen
EXIT_SAPLELACC_004 IS-U: User Exit PAI_BEFORE: Prepares the CALL SUBSCREEN PAI
EXIT_SAPLELACC_005 IS-U: User Exit PAI_AFTER: Closes the CALL SUBSCREEN PAI
EXIT_SAPLELACC_006 IS-U: User Exit OPEN: Opens Customer Object Processing
EXIT_SAPLELACC_007 IS-U: User Exit INPUT: Checks and Copies Entries on Customer Subscreen
EXIT_SAPLELACC_008 IS-U: User Exit PREPARE_CLOSE: Prepares Closing of Customer Data
EXIT_SAPLELACC_009 IS-U: User Exit ACTION: Actions of Customer Subscreen
EXIT_SAPLELACC_010 IS-U: User Exit CLOSE: Ends Customer Data Processing

IMPORTING Parameters details for ISU_S_LOYALACC_DELETE

X_LPCODE - Object Key

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

X_VKONT - Object Key

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

X_UPD_ONLINE - Indicator: Update Online

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

X_NO_DIALOG - Indicator: No Save Prompt

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

EXPORTING Parameters details for ISU_S_LOYALACC_DELETE

Y_DB_UPDATE - Indicator: Data Change

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

EXCEPTIONS details

NOT_FOUND - Object Does Not Exist

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

FOREIGN_LOCK - Object Currently Locked

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

CANCELLED - Function Canceled by User

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

GENERAL_FAULT - Other

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

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