SAP CUBM_PROJECT_BOM_READ Function Module for NOTRANSL: Liest eine Projektstückliste









CUBM_PROJECT_BOM_READ is a standard cubm project bom read 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: Liest eine Projektstückliste 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 cubm project bom read FM, simply by entering the name CUBM_PROJECT_BOM_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CUBM_PROJECT_BOM_READ 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 'CUBM_PROJECT_BOM_READ'"NOTRANSL: Liest eine Projektstückliste
EXPORTING
I_MATNR = "
I_PSPNR = "
I_WERKS = "
I_CAPID = "
* I_DATUV = SY-DATUM "

IMPORTING
E_PRSTB = "
E_HEADER = "
E_HEADER_ZU = "

TABLES
* E_ITEM = "
* E_ITEM_X = "

EXCEPTIONS
NO_COMPONENTS = 1 NOT_FOUND = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for CUBM_PROJECT_BOM_READ

I_MATNR -

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

I_PSPNR -

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

I_WERKS -

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

I_CAPID -

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

I_DATUV -

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

EXPORTING Parameters details for CUBM_PROJECT_BOM_READ

E_PRSTB -

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

E_HEADER -

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

E_HEADER_ZU -

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

TABLES Parameters details for CUBM_PROJECT_BOM_READ

E_ITEM -

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

E_ITEM_X -

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

EXCEPTIONS details

NO_COMPONENTS -

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

NOT_FOUND -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for CUBM_PROJECT_BOM_READ 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_e_item  TYPE STANDARD TABLE OF STPOB, "   
lv_e_prstb  TYPE PRSTB, "   
lv_i_matnr  TYPE KDST-MATNR, "   
lv_no_components  TYPE KDST, "   
lv_i_pspnr  TYPE CS_PSPNR, "   
lv_e_header  TYPE STKOB, "   
lt_e_item_x  TYPE STANDARD TABLE OF CSZALT, "   
lv_not_found  TYPE CSZALT, "   
lv_i_werks  TYPE KDST-WERKS, "   
lv_e_header_zu  TYPE STZUB, "   
lv_internal_error  TYPE STZUB, "   
lv_i_capid  TYPE CAPID, "   
lv_i_datuv  TYPE SY-DATUM. "   SY-DATUM

  CALL FUNCTION 'CUBM_PROJECT_BOM_READ'  "NOTRANSL: Liest eine Projektstückliste
    EXPORTING
         I_MATNR = lv_i_matnr
         I_PSPNR = lv_i_pspnr
         I_WERKS = lv_i_werks
         I_CAPID = lv_i_capid
         I_DATUV = lv_i_datuv
    IMPORTING
         E_PRSTB = lv_e_prstb
         E_HEADER = lv_e_header
         E_HEADER_ZU = lv_e_header_zu
    TABLES
         E_ITEM = lt_e_item
         E_ITEM_X = lt_e_item_x
    EXCEPTIONS
        NO_COMPONENTS = 1
        NOT_FOUND = 2
        INTERNAL_ERROR = 3
. " CUBM_PROJECT_BOM_READ




ABAP code using 7.40 inline data declarations to call FM CUBM_PROJECT_BOM_READ

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 MATNR FROM KDST INTO @DATA(ld_i_matnr).
 
 
 
 
 
 
"SELECT single WERKS FROM KDST INTO @DATA(ld_i_werks).
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_datuv).
DATA(ld_i_datuv) = SY-DATUM.
 


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!