SAP MM_ARRANG_SPMON_RANGE Function Module for NOTRANSL: Teilt Umsatzdaten nach SPMON auf
MM_ARRANG_SPMON_RANGE is a standard mm arrang spmon range 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: Teilt Umsatzdaten nach SPMON auf 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 mm arrang spmon range FM, simply by entering the name MM_ARRANG_SPMON_RANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: WN43
Program Name: SAPLWN43
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_SPMON_RANGE 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 'MM_ARRANG_SPMON_RANGE'"NOTRANSL: Teilt Umsatzdaten nach SPMON auf.
EXPORTING
I_DATAB = "Validity Start Date of the Condition Record
I_DATBI = "Validity End Date of the Condition Record
TABLES
T_SPMON = "Structure with Analysis Period (Month)
EXCEPTIONS
WRONG_RANGE = 1
IMPORTING Parameters details for MM_ARRANG_SPMON_RANGE
I_DATAB - Validity Start Date of the Condition Record
Data type: VAKE-DATABOptional: No
Call by Reference: No ( called with pass by value option)
I_DATBI - Validity End Date of the Condition Record
Data type: VAKE-DATBIOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MM_ARRANG_SPMON_RANGE
T_SPMON - Structure with Analysis Period (Month)
Data type: ARRANG_SPMONOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_RANGE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MM_ARRANG_SPMON_RANGE 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_i_datab | TYPE VAKE-DATAB, " | |||
| lt_t_spmon | TYPE STANDARD TABLE OF ARRANG_SPMON, " | |||
| lv_wrong_range | TYPE ARRANG_SPMON, " | |||
| lv_i_datbi | TYPE VAKE-DATBI. " |
|   CALL FUNCTION 'MM_ARRANG_SPMON_RANGE' "NOTRANSL: Teilt Umsatzdaten nach SPMON auf |
| EXPORTING | ||
| I_DATAB | = lv_i_datab | |
| I_DATBI | = lv_i_datbi | |
| TABLES | ||
| T_SPMON | = lt_t_spmon | |
| EXCEPTIONS | ||
| WRONG_RANGE = 1 | ||
| . " MM_ARRANG_SPMON_RANGE | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_SPMON_RANGE
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 DATAB FROM VAKE INTO @DATA(ld_i_datab). | ||||
| "SELECT single DATBI FROM VAKE INTO @DATA(ld_i_datbi). | ||||
Search for further information about these or an SAP related objects