SAP ISM_SALES_AREA_RANGES Function Module for IS-M: Split Sales Area into Ranges









ISM_SALES_AREA_RANGES is a standard ism sales area ranges SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Split Sales Area into Ranges 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 ism sales area ranges FM, simply by entering the name ISM_SALES_AREA_RANGES into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_SALES_AREA_RANGES 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 'ISM_SALES_AREA_RANGES'"IS-M: Split Sales Area into Ranges
EXPORTING
PS_RJHVTBER = "IS-M: Sales Area Structure

IMPORTING
PT_VKORG_RNG = "IS-M: Selection Table for Sales Organization
PT_VTWEG_RNG = "IS-M: Selection Table for Distribution Channel
PT_SPART_RNG = "IS-M: Selection Table for Division
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJHA4_001 IS-M/AM: TOP_OF_PAGE Enhancement in Central Access Item Overviews
EXIT_SAPLJHA4_002 IS-M/AM: Item Data in Central Access Enhancement
EXIT_SAPLJHA4_003 IS-M/AM: Field Catalog for Item List in Central Access
EXIT_SAPLJHA4_004 IS-M/AM: Function Code Exclusion for Central Access Item List

IMPORTING Parameters details for ISM_SALES_AREA_RANGES

PS_RJHVTBER - IS-M: Sales Area Structure

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

EXPORTING Parameters details for ISM_SALES_AREA_RANGES

PT_VKORG_RNG - IS-M: Selection Table for Sales Organization

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

PT_VTWEG_RNG - IS-M: Selection Table for Distribution Channel

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

PT_SPART_RNG - IS-M: Selection Table for Division

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

Copy and paste ABAP code example for ISM_SALES_AREA_RANGES 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_ps_rjhvtber  TYPE RJHVTBER, "   
lv_pt_vkorg_rng  TYPE RJH_VKORG_RNG_TAB, "   
lv_pt_vtweg_rng  TYPE RJH_VTWEG_RNG_TAB, "   
lv_pt_spart_rng  TYPE RJH_SPART_RNG_TAB. "   

  CALL FUNCTION 'ISM_SALES_AREA_RANGES'  "IS-M: Split Sales Area into Ranges
    EXPORTING
         PS_RJHVTBER = lv_ps_rjhvtber
    IMPORTING
         PT_VKORG_RNG = lv_pt_vkorg_rng
         PT_VTWEG_RNG = lv_pt_vtweg_rng
         PT_SPART_RNG = lv_pt_spart_rng
. " ISM_SALES_AREA_RANGES




ABAP code using 7.40 inline data declarations to call FM ISM_SALES_AREA_RANGES

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!