SAP TWLFE_SINGLE_RECORD_CHECK Function Module for NOTRANSL: Prüfe einzelnen TWLFE-Satz gegen bereits vorhandene TWLFE-Sätze









TWLFE_SINGLE_RECORD_CHECK is a standard twlfe single record check 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: Prüfe einzelnen TWLFE-Satz gegen bereits vorhandene TWLFE-Sätze 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 twlfe single record check FM, simply by entering the name TWLFE_SINGLE_RECORD_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: WVK0
Program Name: SAPLWVK0
Main Program: SAPLWVK0
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TWLFE_SINGLE_RECORD_CHECK 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 'TWLFE_SINGLE_RECORD_CHECK'"NOTRANSL: Prüfe einzelnen TWLFE-Satz gegen bereits vorhandene TWLFE-Sätze
EXPORTING
PI_I_TWLFE = "Sales price calculation: schema/list field

IMPORTING
PE_KSCHL_MAIN = "Condition Type
PE_AKSCH_MAIN = "Condition Type
PE_KOZGF = "Access sequence
PE_AKOZG = "Access sequence

TABLES
PI_T_TWLFE = "Sales price calculation: schema/list field
PE_T_ERRO = "Structure for error messages from TWLFE maintenance
.




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_SAPLWVK0_001 Determine Pricing Type per Customer

IMPORTING Parameters details for TWLFE_SINGLE_RECORD_CHECK

PI_I_TWLFE - Sales price calculation: schema/list field

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

EXPORTING Parameters details for TWLFE_SINGLE_RECORD_CHECK

PE_KSCHL_MAIN - Condition Type

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

PE_AKSCH_MAIN - Condition Type

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

PE_KOZGF - Access sequence

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

PE_AKOZG - Access sequence

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

TABLES Parameters details for TWLFE_SINGLE_RECORD_CHECK

PI_T_TWLFE - Sales price calculation: schema/list field

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

PE_T_ERRO - Structure for error messages from TWLFE maintenance

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

Copy and paste ABAP code example for TWLFE_SINGLE_RECORD_CHECK 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_pi_i_twlfe  TYPE TWLFE, "   
lt_pi_t_twlfe  TYPE STANDARD TABLE OF TWLFE, "   
lv_pe_kschl_main  TYPE T685-KSCHL, "   
lt_pe_t_erro  TYPE STANDARD TABLE OF ERROLFE, "   
lv_pe_aksch_main  TYPE T685-KSCHL, "   
lv_pe_kozgf  TYPE T682Z-KOZGF, "   
lv_pe_akozg  TYPE T682Z-KOZGF. "   

  CALL FUNCTION 'TWLFE_SINGLE_RECORD_CHECK'  "NOTRANSL: Prüfe einzelnen TWLFE-Satz gegen bereits vorhandene TWLFE-Sätze
    EXPORTING
         PI_I_TWLFE = lv_pi_i_twlfe
    IMPORTING
         PE_KSCHL_MAIN = lv_pe_kschl_main
         PE_AKSCH_MAIN = lv_pe_aksch_main
         PE_KOZGF = lv_pe_kozgf
         PE_AKOZG = lv_pe_akozg
    TABLES
         PI_T_TWLFE = lt_pi_t_twlfe
         PE_T_ERRO = lt_pe_t_erro
. " TWLFE_SINGLE_RECORD_CHECK




ABAP code using 7.40 inline data declarations to call FM TWLFE_SINGLE_RECORD_CHECK

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.

 
 
"SELECT single KSCHL FROM T685 INTO @DATA(ld_pe_kschl_main).
 
 
"SELECT single KSCHL FROM T685 INTO @DATA(ld_pe_aksch_main).
 
"SELECT single KOZGF FROM T682Z INTO @DATA(ld_pe_kozgf).
 
"SELECT single KOZGF FROM T682Z INTO @DATA(ld_pe_akozg).
 


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!