SAP PVSDBBAL_PRBAL_READ_BY_LINEBAL Function Module for NOTRANSL: Lesen der Attribute zur FLO-Kante
PVSDBBAL_PRBAL_READ_BY_LINEBAL is a standard pvsdbbal prbal read by linebal 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: Lesen der Attribute zur FLO-Kante 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 pvsdbbal prbal read by linebal FM, simply by entering the name PVSDBBAL_PRBAL_READ_BY_LINEBAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSDBBAL
Program Name: SAPLPVSDBBAL
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PVSDBBAL_PRBAL_READ_BY_LINEBAL 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 'PVSDBBAL_PRBAL_READ_BY_LINEBAL'"NOTRANSL: Lesen der Attribute zur FLO-Kante.
EXPORTING
IM_LBGUID = "GUID for the Line Balance Version
IMPORTING
EX_PRBAL_TAB = "
IMPORTING Parameters details for PVSDBBAL_PRBAL_READ_BY_LINEBAL
IM_LBGUID - GUID for the Line Balance Version
Data type: LINEBAL-LBGUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PVSDBBAL_PRBAL_READ_BY_LINEBAL
EX_PRBAL_TAB -
Data type: PPET9_PRBAL_LI_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PVSDBBAL_PRBAL_READ_BY_LINEBAL 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_im_lbguid | TYPE LINEBAL-LBGUID, " | |||
lv_ex_prbal_tab | TYPE PPET9_PRBAL_LI_TAB. " |
  CALL FUNCTION 'PVSDBBAL_PRBAL_READ_BY_LINEBAL' "NOTRANSL: Lesen der Attribute zur FLO-Kante |
EXPORTING | ||
IM_LBGUID | = lv_im_lbguid | |
IMPORTING | ||
EX_PRBAL_TAB | = lv_ex_prbal_tab | |
. " PVSDBBAL_PRBAL_READ_BY_LINEBAL |
ABAP code using 7.40 inline data declarations to call FM PVSDBBAL_PRBAL_READ_BY_LINEBAL
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 LBGUID FROM LINEBAL INTO @DATA(ld_im_lbguid). | ||||
Search for further information about these or an SAP related objects