SAP ABRECHNUNGSTEILNAHME_ZU_MV Function Module for
ABRECHNUNGSTEILNAHME_ZU_MV is a standard abrechnungsteilnahme zu mv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 abrechnungsteilnahme zu mv FM, simply by entering the name ABRECHNUNGSTEILNAHME_ZU_MV into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITD
Program Name: SAPLFITD
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ABRECHNUNGSTEILNAHME_ZU_MV 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 'ABRECHNUNGSTEILNAHME_ZU_MV'".
EXPORTING
BUKRS = "
DBISPER = "
DVONPER = "
SMENR = "
SMIVE = "
SWENR = "
* IS_MVDAUER = "
* IS_ABR_PERIOD = "
* IF_IGNORE_ABREART = 'X' "
TABLES
ABRTEILNAHME = "
* ET_MVDAUER = "
EXCEPTIONS
NO_DATA_FOUND = 1 SKOART_NOT_FOUND = 2
IMPORTING Parameters details for ABRECHNUNGSTEILNAHME_ZU_MV
BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
DBISPER -
Data type: RF60BAPER-DBISPEROptional: No
Call by Reference: No ( called with pass by value option)
DVONPER -
Data type: RF60BAPER-DVONPEROptional: No
Call by Reference: No ( called with pass by value option)
SMENR -
Data type: VIMIMV-SMENROptional: No
Call by Reference: No ( called with pass by value option)
SMIVE -
Data type: VIMIMV-SMIVEOptional: No
Call by Reference: No ( called with pass by value option)
SWENR -
Data type: VIMIMV-SWENROptional: No
Call by Reference: No ( called with pass by value option)
IS_MVDAUER -
Data type: IMVDAUEROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_ABR_PERIOD -
Data type: RF60BAPEROptional: Yes
Call by Reference: No ( called with pass by value option)
IF_IGNORE_ABREART -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ABRECHNUNGSTEILNAHME_ZU_MV
ABRTEILNAHME -
Data type: RFIAGABRTOptional: No
Call by Reference: No ( called with pass by value option)
ET_MVDAUER -
Data type: IMVDAUEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SKOART_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ABRECHNUNGSTEILNAHME_ZU_MV 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_bukrs | TYPE T001-BUKRS, " | |||
| lt_abrteilnahme | TYPE STANDARD TABLE OF RFIAGABRT, " | |||
| lv_no_data_found | TYPE RFIAGABRT, " | |||
| lv_dbisper | TYPE RF60BAPER-DBISPER, " | |||
| lt_et_mvdauer | TYPE STANDARD TABLE OF IMVDAUER, " | |||
| lv_skoart_not_found | TYPE IMVDAUER, " | |||
| lv_dvonper | TYPE RF60BAPER-DVONPER, " | |||
| lv_smenr | TYPE VIMIMV-SMENR, " | |||
| lv_smive | TYPE VIMIMV-SMIVE, " | |||
| lv_swenr | TYPE VIMIMV-SWENR, " | |||
| lv_is_mvdauer | TYPE IMVDAUER, " | |||
| lv_is_abr_period | TYPE RF60BAPER, " | |||
| lv_if_ignore_abreart | TYPE C. " 'X' |
|   CALL FUNCTION 'ABRECHNUNGSTEILNAHME_ZU_MV' " |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| DBISPER | = lv_dbisper | |
| DVONPER | = lv_dvonper | |
| SMENR | = lv_smenr | |
| SMIVE | = lv_smive | |
| SWENR | = lv_swenr | |
| IS_MVDAUER | = lv_is_mvdauer | |
| IS_ABR_PERIOD | = lv_is_abr_period | |
| IF_IGNORE_ABREART | = lv_if_ignore_abreart | |
| TABLES | ||
| ABRTEILNAHME | = lt_abrteilnahme | |
| ET_MVDAUER | = lt_et_mvdauer | |
| EXCEPTIONS | ||
| NO_DATA_FOUND = 1 | ||
| SKOART_NOT_FOUND = 2 | ||
| . " ABRECHNUNGSTEILNAHME_ZU_MV | ||
ABAP code using 7.40 inline data declarations to call FM ABRECHNUNGSTEILNAHME_ZU_MV
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 BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| "SELECT single DBISPER FROM RF60BAPER INTO @DATA(ld_dbisper). | ||||
| "SELECT single DVONPER FROM RF60BAPER INTO @DATA(ld_dvonper). | ||||
| "SELECT single SMENR FROM VIMIMV INTO @DATA(ld_smenr). | ||||
| "SELECT single SMIVE FROM VIMIMV INTO @DATA(ld_smive). | ||||
| "SELECT single SWENR FROM VIMIMV INTO @DATA(ld_swenr). | ||||
| DATA(ld_if_ignore_abreart) | = 'X'. | |||
Search for further information about these or an SAP related objects