SAP PPEDI_EXPLOSION_GET_CUOBJ Function Module for NOTRANSL: Bestimmung einer alternativen Merkmalsbewertung (iPPE)









PPEDI_EXPLOSION_GET_CUOBJ is a standard ppedi explosion get cuobj 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: Bestimmung einer alternativen Merkmalsbewertung (iPPE) 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 ppedi explosion get cuobj FM, simply by entering the name PPEDI_EXPLOSION_GET_CUOBJ into the relevant SAP transaction such as SE37 or SE38.

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



Function PPEDI_EXPLOSION_GET_CUOBJ 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 'PPEDI_EXPLOSION_GET_CUOBJ'"NOTRANSL: Bestimmung einer alternativen Merkmalsbewertung (iPPE)
  EXPORTING
   IS_MT61D =  "Material Master: MRP
   IV_VERID =  "Production Version
   IV_VRPLA =  "Indicator: planning without final assembly
   IS_CM61M =  "MRP Control Indicator -Material Level-
   IS_CM61B =  "MRP area control indicator
   IV_MATNR =  "Material Number
   IV_WERKS =  "Plant
   IV_PEDTR =  "Order finish date in the planned order
   IV_PSTTR =  "Order start date in planned order
   IV_SERNR =  "BOM explosion number
   IV_TECHS =  "Parameter Variant/Standard Variant

CHANGING
   CV_CUOBJ =  "Configuration (internal object number)
   CV_CHANGED =  "Indicator: Object Changed via Business Add-In
.



IMPORTING Parameters details for PPEDI_EXPLOSION_GET_CUOBJ

IS_MT61D - Material Master: MRP

Data type: MT61D
Optional: No
Call by Reference: Yes

IV_VERID - Production Version

Data type: VERID
Optional: No
Call by Reference: Yes

IV_VRPLA - Indicator: planning without final assembly

Data type: VRPLA
Optional: No
Call by Reference: Yes

IS_CM61M - MRP Control Indicator -Material Level-

Data type: CM61M
Optional: No
Call by Reference: Yes

IS_CM61B - MRP area control indicator

Data type: M61X_CM61B
Optional: No
Call by Reference: Yes

IV_MATNR - Material Number

Data type: MATNR
Optional: No
Call by Reference: Yes

IV_WERKS - Plant

Data type: EWERK
Optional: No
Call by Reference: Yes

IV_PEDTR - Order finish date in the planned order

Data type: PEDTR
Optional: No
Call by Reference: Yes

IV_PSTTR - Order start date in planned order

Data type: PSTTR
Optional: No
Call by Reference: Yes

IV_SERNR - BOM explosion number

Data type: SERNR
Optional: No
Call by Reference: Yes

IV_TECHS - Parameter Variant/Standard Variant

Data type: TECHS
Optional: No
Call by Reference: Yes

CHANGING Parameters details for PPEDI_EXPLOSION_GET_CUOBJ

CV_CUOBJ - Configuration (internal object number)

Data type: CUOBJ
Optional: No
Call by Reference: Yes

CV_CHANGED - Indicator: Object Changed via Business Add-In

Data type: MD_CHFLG
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPEDI_EXPLOSION_GET_CUOBJ 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_cv_cuobj  TYPE CUOBJ, "   
lv_is_mt61d  TYPE MT61D, "   
lv_iv_verid  TYPE VERID, "   
lv_iv_vrpla  TYPE VRPLA, "   
lv_is_cm61m  TYPE CM61M, "   
lv_cv_changed  TYPE MD_CHFLG, "   
lv_is_cm61b  TYPE M61X_CM61B, "   
lv_iv_matnr  TYPE MATNR, "   
lv_iv_werks  TYPE EWERK, "   
lv_iv_pedtr  TYPE PEDTR, "   
lv_iv_psttr  TYPE PSTTR, "   
lv_iv_sernr  TYPE SERNR, "   
lv_iv_techs  TYPE TECHS. "   

  CALL FUNCTION 'PPEDI_EXPLOSION_GET_CUOBJ'  "NOTRANSL: Bestimmung einer alternativen Merkmalsbewertung (iPPE)
    EXPORTING
         IS_MT61D = lv_is_mt61d
         IV_VERID = lv_iv_verid
         IV_VRPLA = lv_iv_vrpla
         IS_CM61M = lv_is_cm61m
         IS_CM61B = lv_is_cm61b
         IV_MATNR = lv_iv_matnr
         IV_WERKS = lv_iv_werks
         IV_PEDTR = lv_iv_pedtr
         IV_PSTTR = lv_iv_psttr
         IV_SERNR = lv_iv_sernr
         IV_TECHS = lv_iv_techs
    CHANGING
         CV_CUOBJ = lv_cv_cuobj
         CV_CHANGED = lv_cv_changed
. " PPEDI_EXPLOSION_GET_CUOBJ




ABAP code using 7.40 inline data declarations to call FM PPEDI_EXPLOSION_GET_CUOBJ

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!