SAP CUSTOMER_INSERT Function Module for NOTRANSL: Anlegen Debitorstammdaten









CUSTOMER_INSERT is a standard customer insert 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: Anlegen Debitorstammdaten 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 customer insert FM, simply by entering the name CUSTOMER_INSERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: F02D
Program Name: SAPLF02D
Main Program: SAPLF02D
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function CUSTOMER_INSERT 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 'CUSTOMER_INSERT'"NOTRANSL: Anlegen Debitorstammdaten
  EXPORTING
   I_KNA1 =  "
   I_KNB1 =  "
   I_KNVV =  "

TABLES
   T_XKNAS =  "
   T_XKNVS =  "
   T_XKNEX =  "
   T_XKNZA =  "
   T_XKNB5 =  "
   T_XKNBK =  "
   T_XKNVA =  "
   T_XKNVD =  "
   T_XKNVI =  "
   T_XKNVK =  "
   T_XKNVL =  "
   T_XKNVP =  "
.



IMPORTING Parameters details for CUSTOMER_INSERT

I_KNA1 -

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

I_KNB1 -

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

I_KNVV -

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

TABLES Parameters details for CUSTOMER_INSERT

T_XKNAS -

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

T_XKNVS -

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

T_XKNEX -

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

T_XKNZA -

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

T_XKNB5 -

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

T_XKNBK -

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

T_XKNVA -

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

T_XKNVD -

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

T_XKNVI -

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

T_XKNVK -

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

T_XKNVL -

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

T_XKNVP -

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

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

DATA:
lv_i_kna1  TYPE KNA1, "   
lt_t_xknas  TYPE STANDARD TABLE OF FKNAS, "   
lt_t_xknvs  TYPE STANDARD TABLE OF FKNVS, "   
lt_t_xknex  TYPE STANDARD TABLE OF FKNEX, "   
lt_t_xknza  TYPE STANDARD TABLE OF FKNZA, "   
lv_i_knb1  TYPE KNB1, "   
lt_t_xknb5  TYPE STANDARD TABLE OF FKNB5, "   
lv_i_knvv  TYPE KNVV, "   
lt_t_xknbk  TYPE STANDARD TABLE OF FKNBK, "   
lt_t_xknva  TYPE STANDARD TABLE OF FKNVA, "   
lt_t_xknvd  TYPE STANDARD TABLE OF FKNVD, "   
lt_t_xknvi  TYPE STANDARD TABLE OF FKNVI, "   
lt_t_xknvk  TYPE STANDARD TABLE OF FKNVK, "   
lt_t_xknvl  TYPE STANDARD TABLE OF FKNVL, "   
lt_t_xknvp  TYPE STANDARD TABLE OF FKNVP. "   

  CALL FUNCTION 'CUSTOMER_INSERT'  "NOTRANSL: Anlegen Debitorstammdaten
    EXPORTING
         I_KNA1 = lv_i_kna1
         I_KNB1 = lv_i_knb1
         I_KNVV = lv_i_knvv
    TABLES
         T_XKNAS = lt_t_xknas
         T_XKNVS = lt_t_xknvs
         T_XKNEX = lt_t_xknex
         T_XKNZA = lt_t_xknza
         T_XKNB5 = lt_t_xknb5
         T_XKNBK = lt_t_xknbk
         T_XKNVA = lt_t_xknva
         T_XKNVD = lt_t_xknvd
         T_XKNVI = lt_t_xknvi
         T_XKNVK = lt_t_xknvk
         T_XKNVL = lt_t_xknvl
         T_XKNVP = lt_t_xknvp
. " CUSTOMER_INSERT




ABAP code using 7.40 inline data declarations to call FM CUSTOMER_INSERT

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!