SAP PRE_RELATION_READ Function Module for NOTRANSL: Verbuchungspuffer lesen









PRE_RELATION_READ is a standard pre relation 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: Verbuchungspuffer lesen 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 pre relation read FM, simply by entering the name PRE_RELATION_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function PRE_RELATION_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 'PRE_RELATION_READ'"NOTRANSL: Verbuchungspuffer lesen
  EXPORTING
   DATA_TYPE =  "Node Type
*  POSNR =  "Item Number of the SD Document
*  I_SUBCON =  "
   XZUGA =  "No receipt
*  MATNR =  "Material Number
*  WERKS =  "Plant
*  CHARG =  "Batch Number
*  AUFNR =  "Order Number
*  EBELN =  "Purchasing Document Number
*  EBELP =  "Item Number of Purchasing Document
*  VBELN =  "Sales and Distribution Document Number

 IMPORTING
   BUFFERED_CHVW_PRE =  "Table Type for CHVW_PRE

EXCEPTIONS
   WRONG_PARAMETER = 1    WRONG_DATA_TYPE = 2
.



IMPORTING Parameters details for PRE_RELATION_READ

DATA_TYPE - Node Type

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

POSNR - Item Number of the SD Document

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

I_SUBCON -

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

XZUGA - No receipt

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

MATNR - Material Number

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

WERKS - Plant

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

CHARG - Batch Number

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

AUFNR - Order Number

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

EBELN - Purchasing Document Number

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

EBELP - Item Number of Purchasing Document

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

VBELN - Sales and Distribution Document Number

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

EXPORTING Parameters details for PRE_RELATION_READ

BUFFERED_CHVW_PRE - Table Type for CHVW_PRE

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

EXCEPTIONS details

WRONG_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

WRONG_DATA_TYPE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PRE_RELATION_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:
lv_data_type  TYPE SEU_TYPE, "   
lv_wrong_parameter  TYPE SEU_TYPE, "   
lv_buffered_chvw_pre  TYPE TT_CHVW_PRE, "   
lv_posnr  TYPE POSNR, "   
lv_i_subcon  TYPE XFELD, "   
lv_xzuga  TYPE XZUGA, "   
lv_wrong_data_type  TYPE XZUGA, "   
lv_matnr  TYPE MATNR, "   
lv_werks  TYPE WERKS_D, "   
lv_charg  TYPE CHARG_D, "   
lv_aufnr  TYPE AUFNR, "   
lv_ebeln  TYPE EBELN, "   
lv_ebelp  TYPE EBELP, "   
lv_vbeln  TYPE VBELN. "   

  CALL FUNCTION 'PRE_RELATION_READ'  "NOTRANSL: Verbuchungspuffer lesen
    EXPORTING
         DATA_TYPE = lv_data_type
         POSNR = lv_posnr
         I_SUBCON = lv_i_subcon
         XZUGA = lv_xzuga
         MATNR = lv_matnr
         WERKS = lv_werks
         CHARG = lv_charg
         AUFNR = lv_aufnr
         EBELN = lv_ebeln
         EBELP = lv_ebelp
         VBELN = lv_vbeln
    IMPORTING
         BUFFERED_CHVW_PRE = lv_buffered_chvw_pre
    EXCEPTIONS
        WRONG_PARAMETER = 1
        WRONG_DATA_TYPE = 2
. " PRE_RELATION_READ




ABAP code using 7.40 inline data declarations to call FM PRE_RELATION_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!