SAP FIPR_VA_GET Function Module for Reads the Attribute Status for a Version









FIPR_VA_GET is a standard fipr va get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads the Attribute Status for a Version 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 fipr va get FM, simply by entering the name FIPR_VA_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FIPR_VA_GET 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 'FIPR_VA_GET'"Reads the Attribute Status for a Version
EXPORTING
I_PRODINT = "Product
I_VERSION = "Version
I_XACTIVE = "Indicator: Active

TABLES
T_VA = "Table: Version Attribute

EXCEPTIONS
PARAMETER_ERROR = 1 NO_RECORDS_FOUND = 2
.



IMPORTING Parameters details for FIPR_VA_GET

I_PRODINT - Product

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

I_VERSION - Version

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

I_XACTIVE - Indicator: Active

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

TABLES Parameters details for FIPR_VA_GET

T_VA - Table: Version Attribute

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

EXCEPTIONS details

PARAMETER_ERROR -

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

NO_RECORDS_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FIPR_VA_GET 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_t_va  TYPE STANDARD TABLE OF FIPR_VA, "   
lv_i_prodint  TYPE FIPR_VA-PRODINT, "   
lv_parameter_error  TYPE FIPR_VA, "   
lv_i_version  TYPE FIPR_VA-VERSION, "   
lv_no_records_found  TYPE FIPR_VA, "   
lv_i_xactive  TYPE FIPR_VA-XACTIVE. "   

  CALL FUNCTION 'FIPR_VA_GET'  "Reads the Attribute Status for a Version
    EXPORTING
         I_PRODINT = lv_i_prodint
         I_VERSION = lv_i_version
         I_XACTIVE = lv_i_xactive
    TABLES
         T_VA = lt_t_va
    EXCEPTIONS
        PARAMETER_ERROR = 1
        NO_RECORDS_FOUND = 2
. " FIPR_VA_GET




ABAP code using 7.40 inline data declarations to call FM FIPR_VA_GET

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 PRODINT FROM FIPR_VA INTO @DATA(ld_i_prodint).
 
 
"SELECT single VERSION FROM FIPR_VA INTO @DATA(ld_i_version).
 
 
"SELECT single XACTIVE FROM FIPR_VA INTO @DATA(ld_i_xactive).
 


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!