SAP LOCU_DI_DATA_KNVV Function Module for NOTRANSL: Dunkle Pflege: Vertriebsbereichssegment Debitor
LOCU_DI_DATA_KNVV is a standard locu di data knvv 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: Dunkle Pflege: Vertriebsbereichssegment Debitor 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 locu di data knvv FM, simply by entering the name LOCU_DI_DATA_KNVV into the relevant SAP transaction such as SE37 or SE38.
Function Group: FLBPD_DARK
Program Name: SAPLFLBPD_DARK
Main Program: SAPLFLBPD_DARK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOCU_DI_DATA_KNVV 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 'LOCU_DI_DATA_KNVV'"NOTRANSL: Dunkle Pflege: Vertriebsbereichssegment Debitor.
EXPORTING
I_KNVV = "Customer Master (Sales) Direct Input Append Structure
TABLES
T_DATA = "BP: Direct input, record (record type 1, 2 or 3)
IMPORTING Parameters details for LOCU_DI_DATA_KNVV
I_KNVV - Customer Master (Sales) Direct Input Append Structure
Data type: KNVV_APP_DIOptional: No
Call by Reference: Yes
TABLES Parameters details for LOCU_DI_DATA_KNVV
T_DATA - BP: Direct input, record (record type 1, 2 or 3)
Data type: BUSSDIOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOCU_DI_DATA_KNVV 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_knvv | TYPE KNVV_APP_DI, " | |||
| lt_t_data | TYPE STANDARD TABLE OF BUSSDI. " |
|   CALL FUNCTION 'LOCU_DI_DATA_KNVV' "NOTRANSL: Dunkle Pflege: Vertriebsbereichssegment Debitor |
| EXPORTING | ||
| I_KNVV | = lv_i_knvv | |
| TABLES | ||
| T_DATA | = lt_t_data | |
| . " LOCU_DI_DATA_KNVV | ||
ABAP code using 7.40 inline data declarations to call FM LOCU_DI_DATA_KNVV
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