SAP CP_BT_PLFL_VORNR_PLNKN_DET Function Module for NOTRANSL: zu den BezugvorgangsNr.'s einer Bezugsfolge Planknoten bestimmen









CP_BT_PLFL_VORNR_PLNKN_DET is a standard cp bt plfl vornr plnkn det 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: zu den BezugvorgangsNr.'s einer Bezugsfolge Planknoten bestimmen 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 cp bt plfl vornr plnkn det FM, simply by entering the name CP_BT_PLFL_VORNR_PLNKN_DET into the relevant SAP transaction such as SE37 or SE38.

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



Function CP_BT_PLFL_VORNR_PLNKN_DET 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 'CP_BT_PLFL_VORNR_PLNKN_DET'"NOTRANSL: zu den BezugvorgangsNr.'s einer Bezugsfolge Planknoten bestimmen
  EXPORTING
   BEZFL =  "Reference sequence
   PLNAL =  "Routing/plan/network alternative
   PLNNR =  "Routing/plan/network number
   PLNTY =  "Routing/plan/network type
   VORNR1 =  "Reference operation 1
   VORNR2 =  "Reference operation 2

 IMPORTING
   BKNT1 =  "Reference point 1
   BKNT2 =  "Reference point 2

EXCEPTIONS
   NOT_FOUND_1 = 1    NOT_FOUND_2 = 2
.



IMPORTING Parameters details for CP_BT_PLFL_VORNR_PLNKN_DET

BEZFL - Reference sequence

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

PLNAL - Routing/plan/network alternative

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

PLNNR - Routing/plan/network number

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

PLNTY - Routing/plan/network type

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

VORNR1 - Reference operation 1

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

VORNR2 - Reference operation 2

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

EXPORTING Parameters details for CP_BT_PLFL_VORNR_PLNKN_DET

BKNT1 - Reference point 1

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

BKNT2 - Reference point 2

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

EXCEPTIONS details

NOT_FOUND_1 - Reference point 1 cannot be determ

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

NOT_FOUND_2 - Reference point 2 cannot be determ

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

Copy and paste ABAP code example for CP_BT_PLFL_VORNR_PLNKN_DET 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_bezfl  TYPE PLFL-BEZFL, "   
lv_bknt1  TYPE PLPO-PLNKN, "   
lv_not_found_1  TYPE PLPO, "   
lv_bknt2  TYPE PLPO-PLNKN, "   
lv_plnal  TYPE PLKO-PLNAL, "   
lv_not_found_2  TYPE PLKO, "   
lv_plnnr  TYPE PLPO-PLNNR, "   
lv_plnty  TYPE PLPO-PLNTY, "   
lv_vornr1  TYPE PLPO-VORNR, "   
lv_vornr2  TYPE PLPO-VORNR. "   

  CALL FUNCTION 'CP_BT_PLFL_VORNR_PLNKN_DET'  "NOTRANSL: zu den BezugvorgangsNr.'s einer Bezugsfolge Planknoten bestimmen
    EXPORTING
         BEZFL = lv_bezfl
         PLNAL = lv_plnal
         PLNNR = lv_plnnr
         PLNTY = lv_plnty
         VORNR1 = lv_vornr1
         VORNR2 = lv_vornr2
    IMPORTING
         BKNT1 = lv_bknt1
         BKNT2 = lv_bknt2
    EXCEPTIONS
        NOT_FOUND_1 = 1
        NOT_FOUND_2 = 2
. " CP_BT_PLFL_VORNR_PLNKN_DET




ABAP code using 7.40 inline data declarations to call FM CP_BT_PLFL_VORNR_PLNKN_DET

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 BEZFL FROM PLFL INTO @DATA(ld_bezfl).
 
"SELECT single PLNKN FROM PLPO INTO @DATA(ld_bknt1).
 
 
"SELECT single PLNKN FROM PLPO INTO @DATA(ld_bknt2).
 
"SELECT single PLNAL FROM PLKO INTO @DATA(ld_plnal).
 
 
"SELECT single PLNNR FROM PLPO INTO @DATA(ld_plnnr).
 
"SELECT single PLNTY FROM PLPO INTO @DATA(ld_plnty).
 
"SELECT single VORNR FROM PLPO INTO @DATA(ld_vornr1).
 
"SELECT single VORNR FROM PLPO INTO @DATA(ld_vornr2).
 


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!