SAP DOCUMENTS_VIA_PKEY_READ Function Module for NOTRANSL: Lese Kalkulationsbelege (WKBK/WKBP) für Tabelle von Positionssch









DOCUMENTS_VIA_PKEY_READ is a standard documents via pkey read 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: Lese Kalkulationsbelege (WKBK/WKBP) für Tabelle von Positionssch 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 documents via pkey read FM, simply by entering the name DOCUMENTS_VIA_PKEY_READ 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 DOCUMENTS_VIA_PKEY_READ 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 'DOCUMENTS_VIA_PKEY_READ'"NOTRANSL: Lese Kalkulationsbelege (WKBK/WKBP) für Tabelle von Positionssch
IMPORTING
PE_T_ERRO_ARCH = "Table Type for Structure ERRO_ARCH (Sales Price)

TABLES
PI_T_PKEY = "
* PE_T_WKBK = "
PE_T_WKBP = "
.




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

EXPORTING Parameters details for DOCUMENTS_VIA_PKEY_READ

PE_T_ERRO_ARCH - Table Type for Structure ERRO_ARCH (Sales Price)

Data type: W_TT_ERRO_ARCH
Optional: No
Call by Reference: Yes

TABLES Parameters details for DOCUMENTS_VIA_PKEY_READ

PI_T_PKEY -

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

PE_T_WKBK -

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

PE_T_WKBP -

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

Copy and paste ABAP code example for DOCUMENTS_VIA_PKEY_READ 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:
lt_pi_t_pkey  TYPE STANDARD TABLE OF WKBP_KEY, "   
lv_pe_t_erro_arch  TYPE W_TT_ERRO_ARCH, "   
lt_pe_t_wkbk  TYPE STANDARD TABLE OF WKBK, "   
lt_pe_t_wkbp  TYPE STANDARD TABLE OF WKBP. "   

  CALL FUNCTION 'DOCUMENTS_VIA_PKEY_READ'  "NOTRANSL: Lese Kalkulationsbelege (WKBK/WKBP) für Tabelle von Positionssch
    IMPORTING
         PE_T_ERRO_ARCH = lv_pe_t_erro_arch
    TABLES
         PI_T_PKEY = lt_pi_t_pkey
         PE_T_WKBK = lt_pe_t_wkbk
         PE_T_WKBP = lt_pe_t_wkbp
. " DOCUMENTS_VIA_PKEY_READ




ABAP code using 7.40 inline data declarations to call FM DOCUMENTS_VIA_PKEY_READ

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!