SAP /MRSS/NW_API_CUSTOMIZING_READ Function Module for Read the customizing from R3









/MRSS/NW_API_CUSTOMIZING_READ is a standard /mrss/nw api customizing read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the customizing from R3 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 /mrss/nw api customizing read FM, simply by entering the name /MRSS/NW_API_CUSTOMIZING_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function /MRSS/NW_API_CUSTOMIZING_READ 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 '/MRSS/NW_API_CUSTOMIZING_READ'"Read  the customizing from R3
  EXPORTING
   IV_CUSTOMIZING_NAME =  "30 Characters
*  IV_ASSIGNMENT_TYPE =  "Assignment category
*  IT_STATUS =  "List with Abstract Statuses
*  IV_OPERATION =  "
*  IS_DEMAND_KEY =  "External Key of Demands
*  IV_DEMAND_TYPE =  "Demand Type
*  IV_PLANT =  "Plant
*  IV_DEMAND_HEADER_TYPE =  "Type of underlying order or operation
*  IV_DEMAND_ITEM_TYPE =  "Demand Item Category
*  IV_SALES_ORG =  "Sales Org
*  IV_MAINT_ACT_TYPE =  "3-Byte field
*  IV_SEARCH_DIRECTION =  "'1'

 IMPORTING
   ES_DATA =  "
   ET_DATA =  "Table of DATA
   EV_FAILED =  "Boolean Variable
   ET_MESSAGES =  "Message Table

EXCEPTIONS
   CUSTOMIZING_NOT_DEFINED = 1
.



IMPORTING Parameters details for /MRSS/NW_API_CUSTOMIZING_READ

IV_CUSTOMIZING_NAME - 30 Characters

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

IV_ASSIGNMENT_TYPE - Assignment category

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

IT_STATUS - List with Abstract Statuses

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

IV_OPERATION -

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

IS_DEMAND_KEY - External Key of Demands

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

IV_DEMAND_TYPE - Demand Type

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

IV_PLANT - Plant

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

IV_DEMAND_HEADER_TYPE - Type of underlying order or operation

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

IV_DEMAND_ITEM_TYPE - Demand Item Category

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

IV_SALES_ORG - Sales Org

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

IV_MAINT_ACT_TYPE - 3-Byte field

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

IV_SEARCH_DIRECTION - '1'

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

EXPORTING Parameters details for /MRSS/NW_API_CUSTOMIZING_READ

ES_DATA -

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

ET_DATA - Table of DATA

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

EV_FAILED - Boolean Variable

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

ET_MESSAGES - Message Table

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

EXCEPTIONS details

CUSTOMIZING_NOT_DEFINED - Customizing is not defined

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /MRSS/NW_API_CUSTOMIZING_READ 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_es_data  TYPE STRING, "   
lv_iv_customizing_name  TYPE /MRSS/T_NW_CUSTOMIZING_NAME, "   
lv_customizing_not_defined  TYPE /MRSS/T_NW_CUSTOMIZING_NAME, "   
lv_iv_assignment_type  TYPE /MRSS/T_SGE_ASSIGNMENT_TYPE, "   
lv_it_status  TYPE /MRSS/T_STATUS_TYPE_TAB, "   
lv_iv_operation  TYPE /MRSS/T_SGE_OPERATION, "   
lv_et_data  TYPE /MRSS/T_NW_STRING_TAB, "   
lv_is_demand_key  TYPE /MRSS/T_DEM_KEY_EXT_STRUC, "   
lv_ev_failed  TYPE /MRSS/T_BOOLEAN, "   
lv_iv_demand_type  TYPE /MRSS/T_DEM_TYPE, "   
lv_iv_plant  TYPE WERKS_D, "   
lv_et_messages  TYPE /MRSS/T_NW_MESSAGE_TAB, "   
lv_iv_demand_header_type  TYPE /MRSS/T_DEM_ORDER_TYPE, "   
lv_iv_demand_item_type  TYPE /MRSS/T_DEM_TYPE_I, "   
lv_iv_sales_org  TYPE /MRSS/T_SALES_ORG, "   
lv_iv_maint_act_type  TYPE CHAR3, "   
lv_iv_search_direction  TYPE /MRSS/T_SRCH_DIRECTION. "   

  CALL FUNCTION '/MRSS/NW_API_CUSTOMIZING_READ'  "Read the customizing from R3
    EXPORTING
         IV_CUSTOMIZING_NAME = lv_iv_customizing_name
         IV_ASSIGNMENT_TYPE = lv_iv_assignment_type
         IT_STATUS = lv_it_status
         IV_OPERATION = lv_iv_operation
         IS_DEMAND_KEY = lv_is_demand_key
         IV_DEMAND_TYPE = lv_iv_demand_type
         IV_PLANT = lv_iv_plant
         IV_DEMAND_HEADER_TYPE = lv_iv_demand_header_type
         IV_DEMAND_ITEM_TYPE = lv_iv_demand_item_type
         IV_SALES_ORG = lv_iv_sales_org
         IV_MAINT_ACT_TYPE = lv_iv_maint_act_type
         IV_SEARCH_DIRECTION = lv_iv_search_direction
    IMPORTING
         ES_DATA = lv_es_data
         ET_DATA = lv_et_data
         EV_FAILED = lv_ev_failed
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        CUSTOMIZING_NOT_DEFINED = 1
. " /MRSS/NW_API_CUSTOMIZING_READ




ABAP code using 7.40 inline data declarations to call FM /MRSS/NW_API_CUSTOMIZING_READ

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!