SAP FIPR_PROD_NUMBER_VERSIONS Function Module for Determines the Number of Versions for a Product
FIPR_PROD_NUMBER_VERSIONS is a standard fipr prod number versions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines the Number of Versions for a Product 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 prod number versions FM, simply by entering the name FIPR_PROD_NUMBER_VERSIONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FIPR_PROD_DB
Program Name: SAPLFIPR_PROD_DB
Main Program: SAPLFIPR_PROD_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FIPR_PROD_NUMBER_VERSIONS 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_PROD_NUMBER_VERSIONS'"Determines the Number of Versions for a Product.
EXPORTING
I_PRODINT = "Internal Product ID
IMPORTING
E_ANZ = "Number of Versions
IMPORTING Parameters details for FIPR_PROD_NUMBER_VERSIONS
I_PRODINT - Internal Product ID
Data type: FIPR_PRODUCT-PRODINTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FIPR_PROD_NUMBER_VERSIONS
E_ANZ - Number of Versions
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FIPR_PROD_NUMBER_VERSIONS 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_e_anz | TYPE I, " | |||
| lv_i_prodint | TYPE FIPR_PRODUCT-PRODINT. " |
|   CALL FUNCTION 'FIPR_PROD_NUMBER_VERSIONS' "Determines the Number of Versions for a Product |
| EXPORTING | ||
| I_PRODINT | = lv_i_prodint | |
| IMPORTING | ||
| E_ANZ | = lv_e_anz | |
| . " FIPR_PROD_NUMBER_VERSIONS | ||
ABAP code using 7.40 inline data declarations to call FM FIPR_PROD_NUMBER_VERSIONS
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_PRODUCT INTO @DATA(ld_i_prodint). | ||||
Search for further information about these or an SAP related objects