SAP CS_BT_PHANTOM_EXPLODE_NEW Function Module for NOTRANSL: Dummybaugruppen auflösen für Komponentenzuordnung im Plan









CS_BT_PHANTOM_EXPLODE_NEW is a standard cs bt phantom explode new 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: Dummybaugruppen auflösen für Komponentenzuordnung im Plan 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 cs bt phantom explode new FM, simply by entering the name CS_BT_PHANTOM_EXPLODE_NEW into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_BT_PHANTOM_EXPLODE_NEW 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 'CS_BT_PHANTOM_EXPLODE_NEW'"NOTRANSL: Dummybaugruppen auflösen für Komponentenzuordnung im Plan
  EXPORTING
   EWERKS =  "Plant
*  ESTLAN =  "BOM Usage
*  EVBELN =  "Sales Order
*  EVBPOS =  "Sales order item
*  EPSPNR =  "Work breakdown structure element (WBS element)
*  ESANFE =  "Checkbox
*  ECAPID =  "Application
*  ESTLAL =  "Alternative BOM
*  ETRTYP = 'V' "Transaction Type

EXCEPTIONS
   CAPID_MISSING = 1
.




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_SAPLCSBT_001 Order BOM (Knowledge Based): Set Status at Fix

IMPORTING Parameters details for CS_BT_PHANTOM_EXPLODE_NEW

EWERKS - Plant

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

ESTLAN - BOM Usage

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

EVBELN - Sales Order

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

EVBPOS - Sales order item

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

EPSPNR - Work breakdown structure element (WBS element)

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

ESANFE - Checkbox

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

ECAPID - Application

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

ESTLAL - Alternative BOM

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

ETRTYP - Transaction Type

Data type: RCM01-TRTYP
Default: 'V'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CAPID_MISSING - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CS_BT_PHANTOM_EXPLODE_NEW 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_ewerks  TYPE MAST-WERKS, "   
lv_capid_missing  TYPE MAST, "   
lv_estlan  TYPE MAST-STLAN, "   
lv_evbeln  TYPE KDST-VBELN, "   
lv_evbpos  TYPE KDST-VBPOS, "   
lv_epspnr  TYPE PRST-PSPNR, "   
lv_esanfe  TYPE CSDATA-XFELD, "   
lv_ecapid  TYPE TC04-CAPID, "   
lv_estlal  TYPE STKO-STLAL, "   
lv_etrtyp  TYPE RCM01-TRTYP. "   'V'

  CALL FUNCTION 'CS_BT_PHANTOM_EXPLODE_NEW'  "NOTRANSL: Dummybaugruppen auflösen für Komponentenzuordnung im Plan
    EXPORTING
         EWERKS = lv_ewerks
         ESTLAN = lv_estlan
         EVBELN = lv_evbeln
         EVBPOS = lv_evbpos
         EPSPNR = lv_epspnr
         ESANFE = lv_esanfe
         ECAPID = lv_ecapid
         ESTLAL = lv_estlal
         ETRTYP = lv_etrtyp
    EXCEPTIONS
        CAPID_MISSING = 1
. " CS_BT_PHANTOM_EXPLODE_NEW




ABAP code using 7.40 inline data declarations to call FM CS_BT_PHANTOM_EXPLODE_NEW

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 WERKS FROM MAST INTO @DATA(ld_ewerks).
 
 
"SELECT single STLAN FROM MAST INTO @DATA(ld_estlan).
 
"SELECT single VBELN FROM KDST INTO @DATA(ld_evbeln).
 
"SELECT single VBPOS FROM KDST INTO @DATA(ld_evbpos).
 
"SELECT single PSPNR FROM PRST INTO @DATA(ld_epspnr).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_esanfe).
 
"SELECT single CAPID FROM TC04 INTO @DATA(ld_ecapid).
 
"SELECT single STLAL FROM STKO INTO @DATA(ld_estlal).
 
"SELECT single TRTYP FROM RCM01 INTO @DATA(ld_etrtyp).
DATA(ld_etrtyp) = 'V'.
 


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!