SAP PB_INTERFACE_ADD Function Module for









PB_INTERFACE_ADD is a standard pb interface add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 pb interface add FM, simply by entering the name PB_INTERFACE_ADD into the relevant SAP transaction such as SE37 or SE38.

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



Function PB_INTERFACE_ADD 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 'PB_INTERFACE_ADD'"
EXPORTING
P_PB_INST = "
P_INTERFACE_STATE = "
* P_EDITOR_CALL = 'X' "
* P_WB_DATA_CONTAINER = "

CHANGING
P_OBJECTNAME = "WB Request: Development Environment Object Type
* P_TRANSPORT_REQUEST = "Request/Task

EXCEPTIONS
ACTION_CANCELLED = 1 ERROR_OCCURED = 2
.



IMPORTING Parameters details for PB_INTERFACE_ADD

P_PB_INST -

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

P_INTERFACE_STATE -

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

P_EDITOR_CALL -

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

P_WB_DATA_CONTAINER -

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

CHANGING Parameters details for PB_INTERFACE_ADD

P_OBJECTNAME - WB Request: Development Environment Object Type

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

P_TRANSPORT_REQUEST - Request/Task

Data type: E070-TRKORR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ACTION_CANCELLED - Canceled by User

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

ERROR_OCCURED - Error message

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

Copy and paste ABAP code example for PB_INTERFACE_ADD 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_p_pb_inst  TYPE CL_PB_ENTRY, "   
lv_p_objectname  TYPE SEU_OBJKEY, "   
lv_action_cancelled  TYPE SEU_OBJKEY, "   
lv_error_occured  TYPE SEU_OBJKEY, "   
lv_p_interface_state  TYPE CL_PB_PACKAGE_INTERFACE_STATE, "   
lv_p_transport_request  TYPE E070-TRKORR, "   
lv_p_editor_call  TYPE CHAR1, "   'X'
lv_p_wb_data_container  TYPE CL_WB_DATA_CONTAINER. "   

  CALL FUNCTION 'PB_INTERFACE_ADD'  "
    EXPORTING
         P_PB_INST = lv_p_pb_inst
         P_INTERFACE_STATE = lv_p_interface_state
         P_EDITOR_CALL = lv_p_editor_call
         P_WB_DATA_CONTAINER = lv_p_wb_data_container
    CHANGING
         P_OBJECTNAME = lv_p_objectname
         P_TRANSPORT_REQUEST = lv_p_transport_request
    EXCEPTIONS
        ACTION_CANCELLED = 1
        ERROR_OCCURED = 2
. " PB_INTERFACE_ADD




ABAP code using 7.40 inline data declarations to call FM PB_INTERFACE_ADD

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 TRKORR FROM E070 INTO @DATA(ld_p_transport_request).
 
DATA(ld_p_editor_call) = 'X'.
 
 


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!