SAP EXIT_SAPLBPT1_006 Function Module for User-Exit OPEN: Opens Processing of Customer Object









EXIT_SAPLBPT1_006 is a standard exit saplbpt1 006 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User-Exit OPEN: Opens Processing of Customer Object 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 exit saplbpt1 006 FM, simply by entering the name EXIT_SAPLBPT1_006 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLBPT1_006 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 'EXIT_SAPLBPT1_006'"User-Exit OPEN: Opens Processing of Customer Object
  EXPORTING
   X_BPCONTACT =  "Business Partner Contact
   X_WMODE =  "Processing Type 1=Disp 2=Chng 3=Create
*  X_UPD_ONLINE =  "Flag: Update Directly Online
*  X_NO_DIALOG =  "Indicator: No Dialog
*  X_BCONT =  "Screen Data
*  X_AUTO =  "

 IMPORTING
   Y_HANDLE =  "Object Reference

EXCEPTIONS
   DATA_INCONSISTENCY = 1
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
BCONTACT_ACTION
BCONTACT_CHANGE
BCONTACT_CLOSE
BCONTACT_CREATE
BCONTACT_CREATE_ANSWER
BCONTACT_DELETE
BCONTACT_DISPLAY
BCONTACT_GET_CCONT
BCONTACT_INPUT
BCONTACT_INPUT_510
BCONTACT_INPUT_520
BCONTACT_INPUT_600
BCONTACT_OPEN
BCONTACT_PAI_AFTER
BCONTACT_PAI_BEFORE
BCONTACT_PBO
BCONTACT_PREPARE_CLOSE
BCONTACT_PROVIDE
BPCT_NUMBER_GET INTERNAL: Number Assignment in IS-U
BPCT_OBJTYPE_PARTNER_READ

IMPORTING Parameters details for EXIT_SAPLBPT1_006

X_BPCONTACT - Business Partner Contact

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

X_WMODE - Processing Type 1=Disp 2=Chng 3=Create

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

X_UPD_ONLINE - Flag: Update Directly Online

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

X_NO_DIALOG - Indicator: No Dialog

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

X_BCONT - Screen Data

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

X_AUTO -

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

EXPORTING Parameters details for EXIT_SAPLBPT1_006

Y_HANDLE - Object Reference

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

EXCEPTIONS details

DATA_INCONSISTENCY -

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

Copy and paste ABAP code example for EXIT_SAPLBPT1_006 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_y_handle  TYPE RSGEN-HANDLE, "   
lv_x_bpcontact  TYPE BCONT-BPCONTACT, "   
lv_data_inconsistency  TYPE BCONT, "   
lv_x_wmode  TYPE BCONTGEN-WMODE, "   
lv_x_upd_online  TYPE BCONTGEN-UPD_ONLINE, "   
lv_x_no_dialog  TYPE BCONTGEN-NO_DIALOG, "   
lv_x_bcont  TYPE BCONT, "   
lv_x_auto  TYPE BPC01_BCONTACT_AUTO. "   

  CALL FUNCTION 'EXIT_SAPLBPT1_006'  "User-Exit OPEN: Opens Processing of Customer Object
    EXPORTING
         X_BPCONTACT = lv_x_bpcontact
         X_WMODE = lv_x_wmode
         X_UPD_ONLINE = lv_x_upd_online
         X_NO_DIALOG = lv_x_no_dialog
         X_BCONT = lv_x_bcont
         X_AUTO = lv_x_auto
    IMPORTING
         Y_HANDLE = lv_y_handle
    EXCEPTIONS
        DATA_INCONSISTENCY = 1
. " EXIT_SAPLBPT1_006




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLBPT1_006

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 HANDLE FROM RSGEN INTO @DATA(ld_y_handle).
 
"SELECT single BPCONTACT FROM BCONT INTO @DATA(ld_x_bpcontact).
 
 
"SELECT single WMODE FROM BCONTGEN INTO @DATA(ld_x_wmode).
 
"SELECT single UPD_ONLINE FROM BCONTGEN INTO @DATA(ld_x_upd_online).
 
"SELECT single NO_DIALOG FROM BCONTGEN INTO @DATA(ld_x_no_dialog).
 
 
 


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!