SAP PPEEXPL_EXPLOSION_SIM Function Module for NOTRANSL: Auflösung für die Konfigurationssimulation in der iPPE Workbench









PPEEXPL_EXPLOSION_SIM is a standard ppeexpl explosion sim 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: Auflösung für die Konfigurationssimulation in der iPPE Workbench 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 ppeexpl explosion sim FM, simply by entering the name PPEEXPL_EXPLOSION_SIM into the relevant SAP transaction such as SE37 or SE38.

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



Function PPEEXPL_EXPLOSION_SIM 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 'PPEEXPL_EXPLOSION_SIM'"NOTRANSL: Auflösung für die Konfigurationssimulation in der iPPE Workbench
  EXPORTING
*  IV_FOCUSID =  "Internal Identification for Focus Record
*  IV_USE_CLASS_ALLOC = 'X' "Generic Type
*  IV_QUANT =  "Quantity (in Component Variant)
*  IV_QUNIT =  "Unit of Measure
*  IV_MSG_HANDLING = 'N' "Parameter for Error Handling
*  IV_MSG_CONTEXT =  "Application Context of Message
*  IV_BYPASS_LIBUFFER = ' ' "Generic Type
*  IV_USE_MEMORY = ' ' "Generic Type
*  IV_ROUND_QUANT = PPET_FALSE "Generic Type
*  IV_ONLY_COLOR_NODE = PPET_FALSE "Generic Type
*  IV_PNGUID =  "Internal Number of iPPE Node
*  IV_PAGUID =  "Internal Identification for PVS Objects
*  IV_CLINT =  "Internal Class Number
*  IV_LOCID =  "Plant/Location in iPPE
*  IV_CHK_EFF = 'X' "Generic Type
*  IV_CHK_CONFIG = 'X' "Generic Type
*  IV_ECM_STATUS_ACTIVE = PPET_FALSE "Generic Type
*  IV_DATE =  "ABAP System Field: Current Date of Application Server

 IMPORTING
   ET_PVCMPHD =  "
   ET_MEM =  "

CHANGING
*  CV_CUOBJ =  "Configuration

EXCEPTIONS
   INTERNAL_ERROR = 1    NO_READ_AUTHORITY = 2    ERROR_IN_EFFECTIVITY = 3    ERROR_IN_CONFIGURATION = 4    INTERNAL_BUFFER_ERROR = 5    TOO_MANY_VALID_POSVARS = 6    VALID_POSVAR_REQUIRED = 7    MORE_THAN_ONE_PPEHDR = 8    NO_ENTRY_FOUND = 9
.



IMPORTING Parameters details for PPEEXPL_EXPLOSION_SIM

IV_FOCUSID - Internal Identification for Focus Record

Data type: PPFOC_PFOCID-PFGUID
Optional: Yes
Call by Reference: Yes

IV_USE_CLASS_ALLOC - Generic Type

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_QUANT - Quantity (in Component Variant)

Data type: PVCMPD-QUANT
Optional: Yes
Call by Reference: Yes

IV_QUNIT - Unit of Measure

Data type: PVCMPD-QUNIT
Optional: Yes
Call by Reference: Yes

IV_MSG_HANDLING - Parameter for Error Handling

Data type: PPET_MSG_OPT
Default: 'N'
Optional: Yes
Call by Reference: Yes

IV_MSG_CONTEXT - Application Context of Message

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

IV_BYPASS_LIBUFFER - Generic Type

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_USE_MEMORY - Generic Type

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_ROUND_QUANT - Generic Type

Data type: C
Default: PPET_FALSE
Optional: Yes
Call by Reference: Yes

IV_ONLY_COLOR_NODE - Generic Type

Data type: C
Default: PPET_FALSE
Optional: Yes
Call by Reference: Yes

IV_PNGUID - Internal Number of iPPE Node

Data type: PNODID-PNGUID
Optional: Yes
Call by Reference: Yes

IV_PAGUID - Internal Identification for PVS Objects

Data type: PALTID-PAGUID
Optional: Yes
Call by Reference: Yes

IV_CLINT - Internal Class Number

Data type: PPET1_PVCMPR-CLINT
Optional: Yes
Call by Reference: Yes

IV_LOCID - Plant/Location in iPPE

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

IV_CHK_EFF - Generic Type

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_CHK_CONFIG - Generic Type

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_ECM_STATUS_ACTIVE - Generic Type

Data type: C
Default: PPET_FALSE
Optional: Yes
Call by Reference: Yes

IV_DATE - ABAP System Field: Current Date of Application Server

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PPEEXPL_EXPLOSION_SIM

ET_PVCMPHD -

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

ET_MEM -

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

CHANGING Parameters details for PPEEXPL_EXPLOSION_SIM

CV_CUOBJ - Configuration

Data type: PPET1_PVCMPR-CUOBJ
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR - Unexpected Error

Data type:
Optional: No
Call by Reference: Yes

NO_READ_AUTHORITY - No authorization to read

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_EFFECTIVITY - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_CONFIGURATION - Error in the configuration

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_BUFFER_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

TOO_MANY_VALID_POSVARS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

VALID_POSVAR_REQUIRED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

MORE_THAN_ONE_PPEHDR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_ENTRY_FOUND - No access determined

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPEEXPL_EXPLOSION_SIM 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 PPET1_PVCMPR-CUOBJ, "   
lv_et_pvcmphd  TYPE PPET8_PVCMPHD_TAB, "   
lv_iv_focusid  TYPE PPFOC_PFOCID-PFGUID, "   
lv_internal_error  TYPE PPFOC_PFOCID, "   
lv_iv_use_class_alloc  TYPE C, "   'X'
lv_iv_quant  TYPE PVCMPD-QUANT, "   
lv_iv_qunit  TYPE PVCMPD-QUNIT, "   
lv_iv_msg_handling  TYPE PPET_MSG_OPT, "   'N'
lv_iv_msg_context  TYPE PPE_MSG_CONTEXT, "   
lv_iv_bypass_libuffer  TYPE C, "   SPACE
lv_iv_use_memory  TYPE C, "   SPACE
lv_iv_round_quant  TYPE C, "   PPET_FALSE
lv_iv_only_color_node  TYPE C, "   PPET_FALSE
lv_et_mem  TYPE PPET8_MEM_TAB, "   
lv_iv_pnguid  TYPE PNODID-PNGUID, "   
lv_no_read_authority  TYPE PNODID, "   
lv_iv_paguid  TYPE PALTID-PAGUID, "   
lv_error_in_effectivity  TYPE PALTID, "   
lv_iv_clint  TYPE PPET1_PVCMPR-CLINT, "   
lv_error_in_configuration  TYPE PPET1_PVCMPR, "   
lv_iv_locid  TYPE PPE_LOCID, "   
lv_internal_buffer_error  TYPE PPE_LOCID, "   
lv_iv_chk_eff  TYPE C, "   'X'
lv_too_many_valid_posvars  TYPE C, "   
lv_iv_chk_config  TYPE C, "   'X'
lv_valid_posvar_required  TYPE C, "   
lv_iv_ecm_status_active  TYPE C, "   PPET_FALSE
lv_more_than_one_ppehdr  TYPE C, "   
lv_iv_date  TYPE SY-DATUM, "   
lv_no_entry_found  TYPE SY. "   

  CALL FUNCTION 'PPEEXPL_EXPLOSION_SIM'  "NOTRANSL: Auflösung für die Konfigurationssimulation in der iPPE Workbench
    EXPORTING
         IV_FOCUSID = lv_iv_focusid
         IV_USE_CLASS_ALLOC = lv_iv_use_class_alloc
         IV_QUANT = lv_iv_quant
         IV_QUNIT = lv_iv_qunit
         IV_MSG_HANDLING = lv_iv_msg_handling
         IV_MSG_CONTEXT = lv_iv_msg_context
         IV_BYPASS_LIBUFFER = lv_iv_bypass_libuffer
         IV_USE_MEMORY = lv_iv_use_memory
         IV_ROUND_QUANT = lv_iv_round_quant
         IV_ONLY_COLOR_NODE = lv_iv_only_color_node
         IV_PNGUID = lv_iv_pnguid
         IV_PAGUID = lv_iv_paguid
         IV_CLINT = lv_iv_clint
         IV_LOCID = lv_iv_locid
         IV_CHK_EFF = lv_iv_chk_eff
         IV_CHK_CONFIG = lv_iv_chk_config
         IV_ECM_STATUS_ACTIVE = lv_iv_ecm_status_active
         IV_DATE = lv_iv_date
    IMPORTING
         ET_PVCMPHD = lv_et_pvcmphd
         ET_MEM = lv_et_mem
    CHANGING
         CV_CUOBJ = lv_cv_cuobj
    EXCEPTIONS
        INTERNAL_ERROR = 1
        NO_READ_AUTHORITY = 2
        ERROR_IN_EFFECTIVITY = 3
        ERROR_IN_CONFIGURATION = 4
        INTERNAL_BUFFER_ERROR = 5
        TOO_MANY_VALID_POSVARS = 6
        VALID_POSVAR_REQUIRED = 7
        MORE_THAN_ONE_PPEHDR = 8
        NO_ENTRY_FOUND = 9
. " PPEEXPL_EXPLOSION_SIM




ABAP code using 7.40 inline data declarations to call FM PPEEXPL_EXPLOSION_SIM

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 CUOBJ FROM PPET1_PVCMPR INTO @DATA(ld_cv_cuobj).
 
 
"SELECT single PFGUID FROM PPFOC_PFOCID INTO @DATA(ld_iv_focusid).
 
 
DATA(ld_iv_use_class_alloc) = 'X'.
 
"SELECT single QUANT FROM PVCMPD INTO @DATA(ld_iv_quant).
 
"SELECT single QUNIT FROM PVCMPD INTO @DATA(ld_iv_qunit).
 
DATA(ld_iv_msg_handling) = 'N'.
 
 
DATA(ld_iv_bypass_libuffer) = ' '.
 
DATA(ld_iv_use_memory) = ' '.
 
DATA(ld_iv_round_quant) = PPET_FALSE.
 
DATA(ld_iv_only_color_node) = PPET_FALSE.
 
 
"SELECT single PNGUID FROM PNODID INTO @DATA(ld_iv_pnguid).
 
 
"SELECT single PAGUID FROM PALTID INTO @DATA(ld_iv_paguid).
 
 
"SELECT single CLINT FROM PPET1_PVCMPR INTO @DATA(ld_iv_clint).
 
 
 
 
DATA(ld_iv_chk_eff) = 'X'.
 
 
DATA(ld_iv_chk_config) = 'X'.
 
 
DATA(ld_iv_ecm_status_active) = PPET_FALSE.
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_iv_date).
 
 


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!