SAP SD_KNA1_MAINTAIN_EXIT Function Module for Exit f.maint. of further data in customer master record (addl table KNA1)

Search SAP Function Modules

SD_KNA1_MAINTAIN_EXIT is a standard sd kna1 maintain exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Exit f.maint. of further data in customer master record (addl table KNA1) 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 sd kna1 maintain exit FM, simply by entering the name SD_KNA1_MAINTAIN_EXIT into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_KNA1_MAINTAIN_EXIT 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 'SD_KNA1_MAINTAIN_EXIT'"Exit f.maint. of further data in customer master record (addl table KNA1)
  EXPORTING
   CUSTOMER_KNA1 =  "Table KNA1 of current customer master
   MAINTAIN_MODE =  "Maintenance mode
   UPDATE_SIGN =  "Indicator: change in customer master

 IMPORTING
   CHANGED_KNA1 =  "Area of changed fields
   E_UPDATE_SIGN =  "Indicator: change in function module
   FUNCTION_CODE =  "Function code for further processing

TABLES
*  TAB055 =  "Table containing fields without change authorization

EXCEPTIONS
   MAINTAIN_MODE_NOT_VALID = 1 

.

IMPORTING Parameters details for SD_KNA1_MAINTAIN_EXIT

CUSTOMER_KNA1 - Table KNA1 of current customer master

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

MAINTAIN_MODE - Maintenance mode

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

UPDATE_SIGN - Indicator: change in customer master

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

EXPORTING Parameters details for SD_KNA1_MAINTAIN_EXIT

CHANGED_KNA1 - Area of changed fields

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

E_UPDATE_SIGN - Indicator: change in function module

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

FUNCTION_CODE - Function code for further processing

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

TABLES Parameters details for SD_KNA1_MAINTAIN_EXIT

TAB055 - Table containing fields without change authorization

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

EXCEPTIONS details

MAINTAIN_MODE_NOT_VALID - Call with invalid maintenance mode

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

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

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