SAP RV_AVAILABILITY_SHOW Function Module for NOTRANSL: Verfügbarkeitsanzeige auf Basis der bestätigten Menge
RV_AVAILABILITY_SHOW is a standard rv availability show 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: Verfügbarkeitsanzeige auf Basis der bestätigten Menge 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 rv availability show FM, simply by entering the name RV_AVAILABILITY_SHOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: V03V
Program Name: SAPLV03V
Main Program: SAPLV03V
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RV_AVAILABILITY_SHOW 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 'RV_AVAILABILITY_SHOW'"NOTRANSL: Verfügbarkeitsanzeige auf Basis der bestätigten Menge.
EXPORTING
* PRREG = ' ' "
SDBELEG = "
* BELEGTYP = "
* TRTYP_V_FORCE = ' ' "ATP Check for Deliveries: Check Mode Change Transaction
* LOGIC_CONT = "V03V: Control String for ATP Flow and Logic
IMPORTING
TMVF_VERPN = "No availability check
TABLES
XMVERF_POS = "
* AVBBD = "
* XEKPO = "
* XEKET = "
* XQUOT_VB = "
* XQUOT_CH = "
* XCATALOGUE = "
IMPORTING Parameters details for RV_AVAILABILITY_SHOW
PRREG -
Data type: T441V-PRREGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SDBELEG -
Data type: VBUK-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
BELEGTYP -
Data type: VBUK-VBTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
TRTYP_V_FORCE - ATP Check for Deliveries: Check Mode Change Transaction
Data type: FORCE_TRTYPV_DELIVERY_ATPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOGIC_CONT - V03V: Control String for ATP Flow and Logic
Data type: V03V_LOGIC_CONTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RV_AVAILABILITY_SHOW
TMVF_VERPN - No availability check
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RV_AVAILABILITY_SHOW
XMVERF_POS -
Data type: V03V_XMVERF_POSOptional: No
Call by Reference: No ( called with pass by value option)
AVBBD -
Data type: BV03VOptional: Yes
Call by Reference: No ( called with pass by value option)
XEKPO -
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
XEKET -
Data type: EKETOptional: Yes
Call by Reference: No ( called with pass by value option)
XQUOT_VB -
Data type: QUOT_VBOptional: Yes
Call by Reference: No ( called with pass by value option)
XQUOT_CH -
Data type: QUOT_CHOptional: Yes
Call by Reference: No ( called with pass by value option)
XCATALOGUE -
Data type: ATPFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RV_AVAILABILITY_SHOW 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_prreg | TYPE T441V-PRREG, " SPACE | |||
| lv_tmvf_verpn | TYPE XFELD, " | |||
| lt_xmverf_pos | TYPE STANDARD TABLE OF V03V_XMVERF_POS, " | |||
| lt_avbbd | TYPE STANDARD TABLE OF BV03V, " | |||
| lv_sdbeleg | TYPE VBUK-VBELN, " | |||
| lt_xekpo | TYPE STANDARD TABLE OF EKPO, " | |||
| lv_belegtyp | TYPE VBUK-VBTYP, " | |||
| lt_xeket | TYPE STANDARD TABLE OF EKET, " | |||
| lv_trtyp_v_force | TYPE FORCE_TRTYPV_DELIVERY_ATP, " SPACE | |||
| lt_xquot_vb | TYPE STANDARD TABLE OF QUOT_VB, " | |||
| lv_logic_cont | TYPE V03V_LOGIC_CONT, " | |||
| lt_xquot_ch | TYPE STANDARD TABLE OF QUOT_CH, " | |||
| lt_xcatalogue | TYPE STANDARD TABLE OF ATPFIELD. " |
|   CALL FUNCTION 'RV_AVAILABILITY_SHOW' "NOTRANSL: Verfügbarkeitsanzeige auf Basis der bestätigten Menge |
| EXPORTING | ||
| PRREG | = lv_prreg | |
| SDBELEG | = lv_sdbeleg | |
| BELEGTYP | = lv_belegtyp | |
| TRTYP_V_FORCE | = lv_trtyp_v_force | |
| LOGIC_CONT | = lv_logic_cont | |
| IMPORTING | ||
| TMVF_VERPN | = lv_tmvf_verpn | |
| TABLES | ||
| XMVERF_POS | = lt_xmverf_pos | |
| AVBBD | = lt_avbbd | |
| XEKPO | = lt_xekpo | |
| XEKET | = lt_xeket | |
| XQUOT_VB | = lt_xquot_vb | |
| XQUOT_CH | = lt_xquot_ch | |
| XCATALOGUE | = lt_xcatalogue | |
| . " RV_AVAILABILITY_SHOW | ||
ABAP code using 7.40 inline data declarations to call FM RV_AVAILABILITY_SHOW
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 PRREG FROM T441V INTO @DATA(ld_prreg). | ||||
| DATA(ld_prreg) | = ' '. | |||
| "SELECT single VBELN FROM VBUK INTO @DATA(ld_sdbeleg). | ||||
| "SELECT single VBTYP FROM VBUK INTO @DATA(ld_belegtyp). | ||||
| DATA(ld_trtyp_v_force) | = ' '. | |||
Search for further information about these or an SAP related objects