SAP MC_PG_STRUKTUR Function Module for NOTRANSL: Produktgruppenstruktur - Strukturanzeige









MC_PG_STRUKTUR is a standard mc pg struktur SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Produktgruppenstruktur - Strukturanzeige 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 mc pg struktur FM, simply by entering the name MC_PG_STRUKTUR into the relevant SAP transaction such as SE37 or SE38.

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



Function MC_PG_STRUKTUR 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 'MC_PG_STRUKTUR'"NOTRANSL: Produktgruppenstruktur - Strukturanzeige
  EXPORTING
*  IDATUB = SY-DATUM "
*  IDATUV = SY-DATUM "
   IPRGRP =  "
   IWERKS =  "
*  IFLG1S = ' ' "

TABLES
*  IPGBAU =  "
*  IPGMIT =  "
*  IPGTAB =  "

EXCEPTIONS
   PG_OR_MATERIAL_NOT_FOUND = 1    UNIT_CONVERSION_NOT_POSSIBLE = 2
.




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_SAPLMCP2_008 User Exit: Processing Header Data in a Purchase Order from an IDoc
EXIT_SAPLMCP2_009 User Exit: Processing Item Data in a Purchase Order from an IDoc

IMPORTING Parameters details for MC_PG_STRUKTUR

IDATUB -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IDATUV -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IPRGRP -

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

IWERKS -

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

IFLG1S -

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

TABLES Parameters details for MC_PG_STRUKTUR

IPGBAU -

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

IPGMIT -

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

IPGTAB -

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

EXCEPTIONS details

PG_OR_MATERIAL_NOT_FOUND - Product group or material not found

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

UNIT_CONVERSION_NOT_POSSIBLE - Units conversion not possible

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

Copy and paste ABAP code example for MC_PG_STRUKTUR 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_idatub  TYPE SY-DATUM, "   SY-DATUM
lt_ipgbau  TYPE STANDARD TABLE OF PGBAU, "   
lv_pg_or_material_not_found  TYPE PGBAU, "   
lv_idatuv  TYPE SY-DATUM, "   SY-DATUM
lt_ipgmit  TYPE STANDARD TABLE OF PGMIT, "   
lv_unit_conversion_not_possible  TYPE PGMIT, "   
lt_ipgtab  TYPE STANDARD TABLE OF PGTAB, "   
lv_iprgrp  TYPE PGMI-PRGRP, "   
lv_iwerks  TYPE PGMI-WERKS, "   
lv_iflg1s  TYPE CHAR01. "   ' '

  CALL FUNCTION 'MC_PG_STRUKTUR'  "NOTRANSL: Produktgruppenstruktur - Strukturanzeige
    EXPORTING
         IDATUB = lv_idatub
         IDATUV = lv_idatuv
         IPRGRP = lv_iprgrp
         IWERKS = lv_iwerks
         IFLG1S = lv_iflg1s
    TABLES
         IPGBAU = lt_ipgbau
         IPGMIT = lt_ipgmit
         IPGTAB = lt_ipgtab
    EXCEPTIONS
        PG_OR_MATERIAL_NOT_FOUND = 1
        UNIT_CONVERSION_NOT_POSSIBLE = 2
. " MC_PG_STRUKTUR




ABAP code using 7.40 inline data declarations to call FM MC_PG_STRUKTUR

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 DATUM FROM SY INTO @DATA(ld_idatub).
DATA(ld_idatub) = SY-DATUM.
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_idatuv).
DATA(ld_idatuv) = SY-DATUM.
 
 
 
 
"SELECT single PRGRP FROM PGMI INTO @DATA(ld_iprgrp).
 
"SELECT single WERKS FROM PGMI INTO @DATA(ld_iwerks).
 
DATA(ld_iflg1s) = ' '.
 


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!