SAP SXMB_SET_PERIODS Function Module for









SXMB_SET_PERIODS is a standard sxmb set periods 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 sxmb set periods FM, simply by entering the name SXMB_SET_PERIODS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXMBCONF
Program Name: SAPLSXMBCONF
Main Program: SAPLSXMBCONF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SXMB_SET_PERIODS 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 'SXMB_SET_PERIODS'"
  EXPORTING
   ARCHPERIOD =  "
   SYNCPERIODU =  "
   HISTPERIODU =  "
   IDX5PERIODU =  "
   DELPERIOD =  "
   SYNCERRPER =  "
   SYNCPERIOD =  "
   HISTPERIOD =  "
   IDX5PERIOD =  "
   DELPERIODU =  "
   ARCHPERIODU =  "
   SYNCERRPERU =  "

EXCEPTIONS
   PARAMETER_INVALID = 1    VALUE_INVALID = 2    FOREIGN_LOCK = 3    NOT_AUTHORIZED = 4
.



IMPORTING Parameters details for SXMB_SET_PERIODS

ARCHPERIOD -

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

SYNCPERIODU -

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

HISTPERIODU -

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

IDX5PERIODU -

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

DELPERIOD -

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

SYNCERRPER -

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

SYNCPERIOD -

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

HISTPERIOD -

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

IDX5PERIOD -

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

DELPERIODU -

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

ARCHPERIODU -

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

SYNCERRPERU -

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

EXCEPTIONS details

PARAMETER_INVALID -

Data type:
Optional: No
Call by Reference: Yes

VALUE_INVALID -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK - Record blocked

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SXMB_SET_PERIODS 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_archperiod  TYPE NUMC3, "   
lv_parameter_invalid  TYPE NUMC3, "   
lv_syncperiodu  TYPE SXMSTIMEUNIT, "   
lv_histperiodu  TYPE SXMSTIMEUNIT, "   
lv_idx5periodu  TYPE SXMSTIMEUNIT, "   
lv_delperiod  TYPE NUMC3, "   
lv_value_invalid  TYPE NUMC3, "   
lv_syncerrper  TYPE NUMC3, "   
lv_foreign_lock  TYPE NUMC3, "   
lv_syncperiod  TYPE NUMC3, "   
lv_not_authorized  TYPE NUMC3, "   
lv_histperiod  TYPE NUMC3, "   
lv_idx5period  TYPE NUMC3, "   
lv_delperiodu  TYPE SXMSTIMEUNIT, "   
lv_archperiodu  TYPE SXMSTIMEUNIT, "   
lv_syncerrperu  TYPE SXMSTIMEUNIT. "   

  CALL FUNCTION 'SXMB_SET_PERIODS'  "
    EXPORTING
         ARCHPERIOD = lv_archperiod
         SYNCPERIODU = lv_syncperiodu
         HISTPERIODU = lv_histperiodu
         IDX5PERIODU = lv_idx5periodu
         DELPERIOD = lv_delperiod
         SYNCERRPER = lv_syncerrper
         SYNCPERIOD = lv_syncperiod
         HISTPERIOD = lv_histperiod
         IDX5PERIOD = lv_idx5period
         DELPERIODU = lv_delperiodu
         ARCHPERIODU = lv_archperiodu
         SYNCERRPERU = lv_syncerrperu
    EXCEPTIONS
        PARAMETER_INVALID = 1
        VALUE_INVALID = 2
        FOREIGN_LOCK = 3
        NOT_AUTHORIZED = 4
. " SXMB_SET_PERIODS




ABAP code using 7.40 inline data declarations to call FM SXMB_SET_PERIODS

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!