SAP BPAR_P_PARTNER_CENTRAL Function Module for









BPAR_P_PARTNER_CENTRAL is a standard bpar p partner central 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 bpar p partner central FM, simply by entering the name BPAR_P_PARTNER_CENTRAL into the relevant SAP transaction such as SE37 or SE38.

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



Function BPAR_P_PARTNER_CENTRAL 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 'BPAR_P_PARTNER_CENTRAL'"
EXPORTING
* DATE_IN = SY-DATUM "Default date for time-dependent data
* ENTRY = ' ' "Transfer structure for direct access
* LEAVE = ' ' "'Leave to transaction' required?
* MODUS = 'DISP' "Processing mode
* TCODE = SY-TCODE "Transaction code
* I_VTB_ST = "
* I_ZGP = "

IMPORTING
EXIT = "Transfer structure after processing
OKCODE_EXIT = "Function code termination

EXCEPTIONS
MODUS = 1
.



IMPORTING Parameters details for BPAR_P_PARTNER_CENTRAL

DATE_IN - Default date for time-dependent data

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

ENTRY - Transfer structure for direct access

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

LEAVE - 'Leave to transaction' required?

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

MODUS - Processing mode

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

TCODE - Transaction code

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

I_VTB_ST -

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

I_ZGP -

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BPAR_P_PARTNER_CENTRAL

EXIT - Transfer structure after processing

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

OKCODE_EXIT - Function code termination

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

EXCEPTIONS details

MODUS - Processing mode

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

Copy and paste ABAP code example for BPAR_P_PARTNER_CENTRAL 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_exit  TYPE BPDENTRY, "   
lv_modus  TYPE BPDENTRY, "   
lv_date_in  TYPE SY-DATUM, "   SY-DATUM
lv_entry  TYPE BPDENTRY, "   SPACE
lv_okcode_exit  TYPE SY-UCOMM, "   
lv_leave  TYPE SY, "   SPACE
lv_modus  TYPE SY-TCODE, "   'DISP'
lv_tcode  TYPE SY-TCODE, "   SY-TCODE
lv_i_vtb_st  TYPE VTB_ST_FB, "   
lv_i_zgp  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'BPAR_P_PARTNER_CENTRAL'  "
    EXPORTING
         DATE_IN = lv_date_in
         ENTRY = lv_entry
         LEAVE = lv_leave
         MODUS = lv_modus
         TCODE = lv_tcode
         I_VTB_ST = lv_i_vtb_st
         I_ZGP = lv_i_zgp
    IMPORTING
         EXIT = lv_exit
         OKCODE_EXIT = lv_okcode_exit
    EXCEPTIONS
        MODUS = 1
. " BPAR_P_PARTNER_CENTRAL




ABAP code using 7.40 inline data declarations to call FM BPAR_P_PARTNER_CENTRAL

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 DATUM FROM SY INTO @DATA(ld_date_in).
DATA(ld_date_in) = SY-DATUM.
 
DATA(ld_entry) = ' '.
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_okcode_exit).
 
DATA(ld_leave) = ' '.
 
"SELECT single TCODE FROM SY INTO @DATA(ld_modus).
DATA(ld_modus) = 'DISP'.
 
"SELECT single TCODE FROM SY INTO @DATA(ld_tcode).
DATA(ld_tcode) = SY-TCODE.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_zgp).
 


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!