SAP FVD_MD_CON_GET_POSITIONS Function Module for Supplies Requested Items of a Condition Table
FVD_MD_CON_GET_POSITIONS is a standard fvd md con get positions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Supplies Requested Items of a Condition Table 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 fvd md con get positions FM, simply by entering the name FVD_MD_CON_GET_POSITIONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_MD_INTERFACE_CONDITION
Program Name: SAPLFVD_MD_INTERFACE_CONDITION
Main Program: SAPLFVD_MD_INTERFACE_CONDITION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_MD_CON_GET_POSITIONS 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 'FVD_MD_CON_GET_POSITIONS'"Supplies Requested Items of a Condition Table.
EXPORTING
* I_LAYER_BUFFER = 'O' "Control Layer for Read Access
I_BUKRS = "Company Code
I_VALID_AS_OF = "Key Date for Condition Determination
I_PRODINT = "Interne Produkt-ID
* I_CONTAB_DEFINING_PARAM = "Condition: Selection Criteria Level Condition Table
I_TAB_COND_TYPES_REQU = "Kondition: Selektionkriterien Ebene Kondition
* I_POS_DEFINING_PARAM = "Kondition: Selektionkriterien Ebene Position
* I_ALL_ASSIGNED_CONDS = ' ' "Auch Konditionen ohne Positionen zurückliefern?
* I_LOG_HANDLE = "Application Log: Log Handle
IMPORTING
E_TAB_COND_POS = "Condition Items Denormalized
E_TAB_COND_POS_NO_SUCC = "Table of Conditions for Which There are no Items
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for FVD_MD_CON_GET_POSITIONS
I_LAYER_BUFFER - Control Layer for Read Access
Data type: TB_S_LAYER_BUFFER_FOR_READDefault: 'O'
Optional: Yes
Call by Reference: Yes
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
I_VALID_AS_OF - Key Date for Condition Determination
Data type: TB_COND_VALID_AS_OFOptional: No
Call by Reference: Yes
I_PRODINT - Interne Produkt-ID
Data type: TB_PR_PRODINTOptional: No
Call by Reference: Yes
I_CONTAB_DEFINING_PARAM - Condition: Selection Criteria Level Condition Table
Data type: RFICO_PROD_ASS_CONTAB_PAR_EXTOptional: Yes
Call by Reference: Yes
I_TAB_COND_TYPES_REQU - Kondition: Selektionkriterien Ebene Kondition
Data type: TRTY_COND_SEL_CRIT_EXTOptional: No
Call by Reference: Yes
I_POS_DEFINING_PARAM - Kondition: Selektionkriterien Ebene Position
Data type: RFICO_POS_SEL_CRITERIA_EXTOptional: Yes
Call by Reference: Yes
I_ALL_ASSIGNED_CONDS - Auch Konditionen ohne Positionen zurückliefern?
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_LOG_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_MD_CON_GET_POSITIONS
E_TAB_COND_POS - Condition Items Denormalized
Data type: TRTY_COND_POS_VIEWOptional: No
Call by Reference: Yes
E_TAB_COND_POS_NO_SUCC - Table of Conditions for Which There are no Items
Data type: TRTY_COND_POS_NO_SUCCOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED - Es sind ein oder mehrere Fehler aufgetreten
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_MD_CON_GET_POSITIONS 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_error_occured | TYPE STRING, " | |||
| lv_e_tab_cond_pos | TYPE TRTY_COND_POS_VIEW, " | |||
| lv_i_layer_buffer | TYPE TB_S_LAYER_BUFFER_FOR_READ, " 'O' | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_e_tab_cond_pos_no_succ | TYPE TRTY_COND_POS_NO_SUCC, " | |||
| lv_i_valid_as_of | TYPE TB_COND_VALID_AS_OF, " | |||
| lv_i_prodint | TYPE TB_PR_PRODINT, " | |||
| lv_i_contab_defining_param | TYPE RFICO_PROD_ASS_CONTAB_PAR_EXT, " | |||
| lv_i_tab_cond_types_requ | TYPE TRTY_COND_SEL_CRIT_EXT, " | |||
| lv_i_pos_defining_param | TYPE RFICO_POS_SEL_CRITERIA_EXT, " | |||
| lv_i_all_assigned_conds | TYPE XFELD, " SPACE | |||
| lv_i_log_handle | TYPE BALLOGHNDL. " |
|   CALL FUNCTION 'FVD_MD_CON_GET_POSITIONS' "Supplies Requested Items of a Condition Table |
| EXPORTING | ||
| I_LAYER_BUFFER | = lv_i_layer_buffer | |
| I_BUKRS | = lv_i_bukrs | |
| I_VALID_AS_OF | = lv_i_valid_as_of | |
| I_PRODINT | = lv_i_prodint | |
| I_CONTAB_DEFINING_PARAM | = lv_i_contab_defining_param | |
| I_TAB_COND_TYPES_REQU | = lv_i_tab_cond_types_requ | |
| I_POS_DEFINING_PARAM | = lv_i_pos_defining_param | |
| I_ALL_ASSIGNED_CONDS | = lv_i_all_assigned_conds | |
| I_LOG_HANDLE | = lv_i_log_handle | |
| IMPORTING | ||
| E_TAB_COND_POS | = lv_e_tab_cond_pos | |
| E_TAB_COND_POS_NO_SUCC | = lv_e_tab_cond_pos_no_succ | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " FVD_MD_CON_GET_POSITIONS | ||
ABAP code using 7.40 inline data declarations to call FM FVD_MD_CON_GET_POSITIONS
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.| DATA(ld_i_layer_buffer) | = 'O'. | |||
| DATA(ld_i_all_assigned_conds) | = ' '. | |||
Search for further information about these or an SAP related objects