SAP MCS_CUSTOMER_RANGES_DETERMINE Function Module for LIS: Determine Next Free Event/Function Group

Search SAP Function Modules

MCS_CUSTOMER_RANGES_DETERMINE is a standard mcs customer ranges determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LIS: Determine Next Free Event/Function Group 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 mcs customer ranges determine FM, simply by entering the name MCS_CUSTOMER_RANGES_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

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

Function MCS_CUSTOMER_RANGES_DETERMINE 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 'MCS_CUSTOMER_RANGES_DETERMINE'"LIS: Determine Next Free Event/Function Group
  EXPORTING
*  I_NEXT_ZEITP =  "Determine next customer event
*  I_NEXT_FGROUP =  "Determine next function group
*  I_NEXT_SFEIN =  "Determine next customer unit

 IMPORTING
   E_FGROUP =  "Function group FM generation
   E_SFEIN =  "Unit

CHANGING
*  E_ZEITP =  "Event

EXCEPTIONS
   NO_INPUT_PARAMETERS = 1    NO_FREE_CUSTOMERRANGES = 2    NO_TRANSPORT = 3 

.

IMPORTING Parameters details for MCS_CUSTOMER_RANGES_DETERMINE

I_NEXT_ZEITP - Determine next customer event

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

I_NEXT_FGROUP - Determine next function group

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

I_NEXT_SFEIN - Determine next customer unit

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

EXPORTING Parameters details for MCS_CUSTOMER_RANGES_DETERMINE

E_FGROUP - Function group FM generation

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

E_SFEIN - Unit

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

CHANGING Parameters details for MCS_CUSTOMER_RANGES_DETERMINE

E_ZEITP - Event

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

EXCEPTIONS details

NO_INPUT_PARAMETERS - Event does not exist

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

NO_FREE_CUSTOMERRANGES - Customer name range exhausted

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

NO_TRANSPORT - No transport permitted

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

Copy and paste ABAP code example for MCS_CUSTOMER_RANGES_DETERMINE 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.

ABAP code using 7.40 inline data declarations to call FM MCS_CUSTOMER_RANGES_DETERMINE

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