SAP BBPV_CONTRACT_STATUS_GET Function Module for NOTRANSL: Einkaufskontrakt von BBP anlegen

Search SAP Function Modules

BBPV_CONTRACT_STATUS_GET is a standard bbpv contract status get 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: Einkaufskontrakt von BBP anlegen 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 bbpv contract status get FM, simply by entering the name BBPV_CONTRACT_STATUS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBPV
Program Name: SAPLBBPV
Main Program: SAPLBBPV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBPV_CONTRACT_STATUS_GET 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 'BBPV_CONTRACT_STATUS_GET'"NOTRANSL: Einkaufskontrakt von BBP anlegen
  EXPORTING
*  IV_HEADER_OBJECT_ID =  "Single-Character Indicator
*  IV_CALLING_LOGSYS =  "Logical System
*  IV_BE_EKORG =  "Purchasing Organization
*  IV_LANGUAGE = SY-LANGU "ERP System, Current Language
*  IV_BE_PLANT =  "Plant
*  IV_PMNTTRMS =  "
*  IV_CURRENCY =  "Currency Key

 IMPORTING
   EV_CTR_CREATION =  "Single-Character Indicator
   EV_CND_CREATION =  "Single-Character Indicator

TABLES
*  ET_CTR_MM_ITEM_MAP =  "Mapping of EBP Items to R/3 Items
*  ET_RETURN =  "Return Parameter(s)

.

IMPORTING Parameters details for BBPV_CONTRACT_STATUS_GET

IV_HEADER_OBJECT_ID - Single-Character Indicator

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

IV_CALLING_LOGSYS - Logical System

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

IV_BE_EKORG - Purchasing Organization

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

IV_LANGUAGE - ERP System, Current Language

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

IV_BE_PLANT - Plant

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

IV_PMNTTRMS -

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

IV_CURRENCY - Currency Key

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

EXPORTING Parameters details for BBPV_CONTRACT_STATUS_GET

EV_CTR_CREATION - Single-Character Indicator

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

EV_CND_CREATION - Single-Character Indicator

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

TABLES Parameters details for BBPV_CONTRACT_STATUS_GET

ET_CTR_MM_ITEM_MAP - Mapping of EBP Items to R/3 Items

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

ET_RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for BBPV_CONTRACT_STATUS_GET 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.

ABAP code using 7.40 inline data declarations to call FM BBPV_CONTRACT_STATUS_GET

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.

Search for further information about these or an SAP related objects