SAP MSAM10_CODEGROUP_GETDETAIL Function Module for PM/CS: Code Group Get Detail









MSAM10_CODEGROUP_GETDETAIL is a standard msam10 codegroup getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PM/CS: Code Group Get Detail 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 msam10 codegroup getdetail FM, simply by entering the name MSAM10_CODEGROUP_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function MSAM10_CODEGROUP_GETDETAIL 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 'MSAM10_CODEGROUP_GETDETAIL'"PM/CS: Code Group Get Detail
  EXPORTING
   CODE_CAT_GROUP =  "Catalog Type and Code Group in One Field

 IMPORTING
   E_CODEGROUP =  "Code Group Key

TABLES
*  CODES =  "Code Catalog
*  ML_CODEGROUP_HEADER =  "Multilanguage for codegroup header
*  ML_CODE =  "Multilanguage data for code
*  CE_EXTENSION =  "Copy user-speific fields to the mobile device
*  CE_ML_EXTENSION =  "Multi langauge Customer Enahancement fields
*  WSAP_EXTENSION =  "SAP speific fields for the extension
*  WSAP_ML_EXTENSION =  "Multi langauge SAP Enahancement fields
*  RETURN =  "Return Parameter
.



IMPORTING Parameters details for MSAM10_CODEGROUP_GETDETAIL

CODE_CAT_GROUP - Catalog Type and Code Group in One Field

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

EXPORTING Parameters details for MSAM10_CODEGROUP_GETDETAIL

E_CODEGROUP - Code Group Key

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

TABLES Parameters details for MSAM10_CODEGROUP_GETDETAIL

CODES - Code Catalog

Data type: MSAM10_CODE_CATALOG
Optional: Yes
Call by Reference: Yes

ML_CODEGROUP_HEADER - Multilanguage for codegroup header

Data type: MSAM10_ML_CODEGROUP
Optional: Yes
Call by Reference: Yes

ML_CODE - Multilanguage data for code

Data type: MSAM10_ML_CODE
Optional: Yes
Call by Reference: Yes

CE_EXTENSION - Copy user-speific fields to the mobile device

Data type: MSAM_MO_CUSTOMER_ENHANCEMENT
Optional: Yes
Call by Reference: Yes

CE_ML_EXTENSION - Multi langauge Customer Enahancement fields

Data type: MSAM_MO_ML_CUSTOMER_ENHANCEMNT
Optional: Yes
Call by Reference: Yes

WSAP_EXTENSION - SAP speific fields for the extension

Data type: MSAM_MO_SAP_ENHANCEMENT
Optional: Yes
Call by Reference: Yes

WSAP_ML_EXTENSION - Multi langauge SAP Enahancement fields

Data type: MSAM_MO_ML_SAP_ENHANCEMENT
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for MSAM10_CODEGROUP_GETDETAIL 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:
lt_codes  TYPE STANDARD TABLE OF MSAM10_CODE_CATALOG, "   
lv_e_codegroup  TYPE MSAM10_CODEGROUP, "   
lv_code_cat_group  TYPE MSAM10_CODEGROUP-CODE_CAT_GROUP, "   
lt_ml_codegroup_header  TYPE STANDARD TABLE OF MSAM10_ML_CODEGROUP, "   
lt_ml_code  TYPE STANDARD TABLE OF MSAM10_ML_CODE, "   
lt_ce_extension  TYPE STANDARD TABLE OF MSAM_MO_CUSTOMER_ENHANCEMENT, "   
lt_ce_ml_extension  TYPE STANDARD TABLE OF MSAM_MO_ML_CUSTOMER_ENHANCEMNT, "   
lt_wsap_extension  TYPE STANDARD TABLE OF MSAM_MO_SAP_ENHANCEMENT, "   
lt_wsap_ml_extension  TYPE STANDARD TABLE OF MSAM_MO_ML_SAP_ENHANCEMENT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'MSAM10_CODEGROUP_GETDETAIL'  "PM/CS: Code Group Get Detail
    EXPORTING
         CODE_CAT_GROUP = lv_code_cat_group
    IMPORTING
         E_CODEGROUP = lv_e_codegroup
    TABLES
         CODES = lt_codes
         ML_CODEGROUP_HEADER = lt_ml_codegroup_header
         ML_CODE = lt_ml_code
         CE_EXTENSION = lt_ce_extension
         CE_ML_EXTENSION = lt_ce_ml_extension
         WSAP_EXTENSION = lt_wsap_extension
         WSAP_ML_EXTENSION = lt_wsap_ml_extension
         RETURN = lt_return
. " MSAM10_CODEGROUP_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM MSAM10_CODEGROUP_GETDETAIL

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 CODE_CAT_GROUP FROM MSAM10_CODEGROUP INTO @DATA(ld_code_cat_group).
 
 
 
 
 
 
 
 


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!