SAP MM_NEXT_PERIOD_CONDITION Function Module for









MM_NEXT_PERIOD_CONDITION is a standard mm next period condition 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 mm next period condition FM, simply by entering the name MM_NEXT_PERIOD_CONDITION into the relevant SAP transaction such as SE37 or SE38.

Function Group: WN03
Program Name: SAPLWN03
Main Program: SAPLWN03
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MM_NEXT_PERIOD_CONDITION 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_NEXT_PERIOD_CONDITION'"
  EXPORTING
   CONDITION_DATAB =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   CONDITION_DATBI =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   CALENDAR_ID =  "Calendar

TABLES
*  CONDITION_PERIODS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
   CALENDAR_BUFFER_NOT_LOADABLE = 1    CALENDAR_ID_MISSING = 2    DATAB_GREATER_DATBI = 3    NO_PERIODS = 4    DATE_INVALID = 5    FACTORY_CALENDAR_NOT_FOUND = 6    MISSING_LAST_PERIOD = 7
.



IMPORTING Parameters details for MM_NEXT_PERIOD_CONDITION

CONDITION_DATAB - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: KONA-DATAB
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITION_DATBI - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: KONA-DATBI
Optional: No
Call by Reference: No ( called with pass by value option)

CALENDAR_ID - Calendar

Data type: SCAL-FCALID
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MM_NEXT_PERIOD_CONDITION

CONDITION_PERIODS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: BONUSPERIO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CALENDAR_BUFFER_NOT_LOADABLE - Internal Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CALENDAR_ID_MISSING - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATAB_GREATER_DATBI - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_PERIODS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATE_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FACTORY_CALENDAR_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MISSING_LAST_PERIOD - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MM_NEXT_PERIOD_CONDITION 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_condition_datab  TYPE KONA-DATAB, "   
lt_condition_periods  TYPE STANDARD TABLE OF BONUSPERIO, "   
lv_calendar_buffer_not_loadable  TYPE BONUSPERIO, "   
lv_condition_datbi  TYPE KONA-DATBI, "   
lv_calendar_id_missing  TYPE KONA, "   
lv_calendar_id  TYPE SCAL-FCALID, "   
lv_datab_greater_datbi  TYPE SCAL, "   
lv_no_periods  TYPE SCAL, "   
lv_date_invalid  TYPE SCAL, "   
lv_factory_calendar_not_found  TYPE SCAL, "   
lv_missing_last_period  TYPE SCAL. "   

  CALL FUNCTION 'MM_NEXT_PERIOD_CONDITION'  "
    EXPORTING
         CONDITION_DATAB = lv_condition_datab
         CONDITION_DATBI = lv_condition_datbi
         CALENDAR_ID = lv_calendar_id
    TABLES
         CONDITION_PERIODS = lt_condition_periods
    EXCEPTIONS
        CALENDAR_BUFFER_NOT_LOADABLE = 1
        CALENDAR_ID_MISSING = 2
        DATAB_GREATER_DATBI = 3
        NO_PERIODS = 4
        DATE_INVALID = 5
        FACTORY_CALENDAR_NOT_FOUND = 6
        MISSING_LAST_PERIOD = 7
. " MM_NEXT_PERIOD_CONDITION




ABAP code using 7.40 inline data declarations to call FM MM_NEXT_PERIOD_CONDITION

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 KONA INTO @DATA(ld_condition_datab).
 
 
 
"SELECT single DATBI FROM KONA INTO @DATA(ld_condition_datbi).
 
 
"SELECT single FCALID FROM SCAL INTO @DATA(ld_calendar_id).
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!