SAP BBPV_CONTRACT_TRANSFER Function Module for NOTRANSL: Einkaufskontrakt/Lieferplan von BBP anlegen/ändern

Search SAP Function Modules

BBPV_CONTRACT_TRANSFER is a standard bbpv contract transfer 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/Lieferplan von BBP anlegen/ändern 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 transfer FM, simply by entering the name BBPV_CONTRACT_TRANSFER 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_TRANSFER 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_TRANSFER'"NOTRANSL: Einkaufskontrakt/Lieferplan von BBP anlegen/ändern
  EXPORTING
*  IV_USER =  "ERP System, User Logon Name
*  IV_LANGU =  "ERP System, Current Language
   IV_CALLING_LOGSYS =  "Logical System
   IS_HEADER =  "Contract Communication Structure: Header/Org/Partner

TABLES
   IT_ITEMS =  "Contract Communication Structure: Items/Partner
*  ET_RETURN =  "Return Parameter(s)
*  IT_TEXT =  "Contract Communication Structure: Texts
*  IT_CND_CT =  "BAPI struct. for condition tables (corresponds to COND_RECS)
*  IT_CND_HD =  "BAPI Structure of KONH with English Field Names
*  IT_CND_IT =  "BAPI Structure of KONP with English Field Names
*  IT_CND_QS =  "BAPI Structure of KONM with English Field Names
*  IT_CND_VS =  "BAPI Structure of KONW with English Field Names
*  IT_ATT =  "Contract Attachments Structure Without PHIO Content
*  IT_ATT_CONT =  "Contract Attachments Structure PHIO Content Only

EXCEPTIONS
   SAVE_ERROR_CONTRACT = 1    SAVE_ERROR_CONDITION = 2    SAVE_ERROR_CONTRACT_CONDITION = 3    MAPPING_ERROR_CONTRACT = 4    MAPPING_ERROR_CONDITION = 5    MAP_ERROR_CONTRACT_CONDITION = 6 

.

IMPORTING Parameters details for BBPV_CONTRACT_TRANSFER

IV_USER - ERP System, User Logon Name

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

IV_LANGU - ERP System, Current Language

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

IV_CALLING_LOGSYS - Logical System

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

IS_HEADER - Contract Communication Structure: Header/Org/Partner

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

TABLES Parameters details for BBPV_CONTRACT_TRANSFER

IT_ITEMS - Contract Communication Structure: Items/Partner

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

ET_RETURN - Return Parameter(s)

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

IT_TEXT - Contract Communication Structure: Texts

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

IT_CND_CT - BAPI struct. for condition tables (corresponds to COND_RECS)

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

IT_CND_HD - BAPI Structure of KONH with English Field Names

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

IT_CND_IT - BAPI Structure of KONP with English Field Names

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

IT_CND_QS - BAPI Structure of KONM with English Field Names

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

IT_CND_VS - BAPI Structure of KONW with English Field Names

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

IT_ATT - Contract Attachments Structure Without PHIO Content

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

IT_ATT_CONT - Contract Attachments Structure PHIO Content Only

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

EXCEPTIONS details

SAVE_ERROR_CONTRACT -

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

SAVE_ERROR_CONDITION -

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

SAVE_ERROR_CONTRACT_CONDITION -

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

MAPPING_ERROR_CONTRACT -

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

MAPPING_ERROR_CONDITION -

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

MAP_ERROR_CONTRACT_CONDITION -

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

Copy and paste ABAP code example for BBPV_CONTRACT_TRANSFER 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_TRANSFER

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