SAP BBP_PD_CTR_VENDOR Function Module for Contracts for Supplier









BBP_PD_CTR_VENDOR is a standard bbp pd ctr vendor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Contracts for Supplier 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 bbp pd ctr vendor FM, simply by entering the name BBP_PD_CTR_VENDOR into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PD_CTR_VENDOR 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 'BBP_PD_CTR_VENDOR'"Contracts for Supplier
  EXPORTING
   I_VENDOR_OLD =  "Geschäftspartnernummer
   I_TIME_CUR_UTC =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)
*  I_VENDOR_NEW =  "Geschäftspartnernummer
*  I_DATE =  "Datum und Zeit, aktuelles (Applikationsserver-)Datum
*  I_TIME =  "Datum und Zeit, aktuelle (Applikationsserver-) Uhrzeit
*  I_TIME_ZONE =  "Datum und Zeit, Zeitzone des Benutzers
*  I_CTR_DESCRIPTION =  "Beschreibung eines Vorgangs
   I_DISPLAY =  "Einstelliges Kennzeichen
   I_PO =  "Einstelliges Kennzeichen
*  I_TIME_NOV_UTC =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

 IMPORTING
   E_VENDOR_GUID_OLD =  "Partnernummer
   E_VENDOR_GUID_NEW =  "Partnernummer

CHANGING
*  C_PARTNER_FCT =  "Partnerfunktion

TABLES
*  I_STATUS =  "Einzelstatus
*  E_PO_D =  "Kontrakt/Bestellung Position für Novation
*  E_PO_HISTORY =  "Kontrakt/Bestellung Kopf für Novation
*  E_STATUS =  "Status
*  I_RANGE_OBJECT_ID =  "Interface Struktur für Ranges der Objekt-ID
   E_PDLIST_H =  "Schnittstelle GetList für Kontrakt
   E_PDLIST_D =  "Schnittstelle GetList für Kontrakt
   E_CTR_PO_H =  "Kontrakt/Bestellung Kopf für Novation
   E_CTR_PO_D =  "Kontrakt/Bestellung Position für Novation
*  E_MESSAGES =  "Fehlermeldungen zu einer PD-Methode
*  E_PO_H =  "Kontrakt/Bestellung Kopf für Novation
.



IMPORTING Parameters details for BBP_PD_CTR_VENDOR

I_VENDOR_OLD - Geschäftspartnernummer

Data type: BUT000-PARTNER
Optional: No
Call by Reference: Yes

I_TIME_CUR_UTC - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

I_VENDOR_NEW - Geschäftspartnernummer

Data type: BUT000-PARTNER
Optional: Yes
Call by Reference: Yes

I_DATE - Datum und Zeit, aktuelles (Applikationsserver-)Datum

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

I_TIME - Datum und Zeit, aktuelle (Applikationsserver-) Uhrzeit

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

I_TIME_ZONE - Datum und Zeit, Zeitzone des Benutzers

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

I_CTR_DESCRIPTION - Beschreibung eines Vorgangs

Data type: BBP_PDS_HEADER-DESCRIPTION
Optional: Yes
Call by Reference: Yes

I_DISPLAY - Einstelliges Kennzeichen

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

I_PO - Einstelliges Kennzeichen

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

I_TIME_NOV_UTC - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

EXPORTING Parameters details for BBP_PD_CTR_VENDOR

E_VENDOR_GUID_OLD - Partnernummer

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

E_VENDOR_GUID_NEW - Partnernummer

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

CHANGING Parameters details for BBP_PD_CTR_VENDOR

C_PARTNER_FCT - Partnerfunktion

Data type: CRMD_PARTNER-PARTNER_FCT
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for BBP_PD_CTR_VENDOR

I_STATUS - Einzelstatus

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

E_PO_D - Kontrakt/Bestellung Position für Novation

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

E_PO_HISTORY - Kontrakt/Bestellung Kopf für Novation

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

E_STATUS - Status

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

I_RANGE_OBJECT_ID - Interface Struktur für Ranges der Objekt-ID

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

E_PDLIST_H - Schnittstelle GetList für Kontrakt

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

E_PDLIST_D - Schnittstelle GetList für Kontrakt

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

E_CTR_PO_H - Kontrakt/Bestellung Kopf für Novation

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

E_CTR_PO_D - Kontrakt/Bestellung Position für Novation

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

E_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

E_PO_H - Kontrakt/Bestellung Kopf für Novation

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

Copy and paste ABAP code example for BBP_PD_CTR_VENDOR 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:
lt_i_status  TYPE STANDARD TABLE OF JSTAT, "   
lv_i_vendor_old  TYPE BUT000-PARTNER, "   
lv_c_partner_fct  TYPE CRMD_PARTNER-PARTNER_FCT, "   
lv_e_vendor_guid_old  TYPE BU_PARTNER_GUID, "   
lt_e_po_d  TYPE STANDARD TABLE OF BBPS_PO_D_NOVATION, "   
lv_i_time_cur_utc  TYPE TIMESTAMP, "   
lt_e_po_history  TYPE STANDARD TABLE OF BBPS_PO_HIST_NOVATION, "   
lt_e_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lv_i_vendor_new  TYPE BUT000-PARTNER, "   
lv_e_vendor_guid_new  TYPE BU_PARTNER_GUID, "   
lv_i_date  TYPE SYDATUM, "   
lt_i_range_object_id  TYPE STANDARD TABLE OF BBP_PDS_RANGE_OBJECT_ID, "   
lv_i_time  TYPE SYUZEIT, "   
lt_e_pdlist_h  TYPE STANDARD TABLE OF BBP_PDS_CTR_PDLIST, "   
lt_e_pdlist_d  TYPE STANDARD TABLE OF BBPS_CTR_D_NOVATION, "   
lv_i_time_zone  TYPE TZNZONE, "   
lt_e_ctr_po_h  TYPE STANDARD TABLE OF BBPS_PO_H_NOVATION, "   
lv_i_ctr_description  TYPE BBP_PDS_HEADER-DESCRIPTION, "   
lv_i_display  TYPE CHAR1, "   
lt_e_ctr_po_d  TYPE STANDARD TABLE OF BBPS_PO_D_NOVATION, "   
lv_i_po  TYPE CHAR1, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lt_e_po_h  TYPE STANDARD TABLE OF BBPS_PO_H_NOVATION, "   
lv_i_time_nov_utc  TYPE TIMESTAMP. "   

  CALL FUNCTION 'BBP_PD_CTR_VENDOR'  "Contracts for Supplier
    EXPORTING
         I_VENDOR_OLD = lv_i_vendor_old
         I_TIME_CUR_UTC = lv_i_time_cur_utc
         I_VENDOR_NEW = lv_i_vendor_new
         I_DATE = lv_i_date
         I_TIME = lv_i_time
         I_TIME_ZONE = lv_i_time_zone
         I_CTR_DESCRIPTION = lv_i_ctr_description
         I_DISPLAY = lv_i_display
         I_PO = lv_i_po
         I_TIME_NOV_UTC = lv_i_time_nov_utc
    IMPORTING
         E_VENDOR_GUID_OLD = lv_e_vendor_guid_old
         E_VENDOR_GUID_NEW = lv_e_vendor_guid_new
    CHANGING
         C_PARTNER_FCT = lv_c_partner_fct
    TABLES
         I_STATUS = lt_i_status
         E_PO_D = lt_e_po_d
         E_PO_HISTORY = lt_e_po_history
         E_STATUS = lt_e_status
         I_RANGE_OBJECT_ID = lt_i_range_object_id
         E_PDLIST_H = lt_e_pdlist_h
         E_PDLIST_D = lt_e_pdlist_d
         E_CTR_PO_H = lt_e_ctr_po_h
         E_CTR_PO_D = lt_e_ctr_po_d
         E_MESSAGES = lt_e_messages
         E_PO_H = lt_e_po_h
. " BBP_PD_CTR_VENDOR




ABAP code using 7.40 inline data declarations to call FM BBP_PD_CTR_VENDOR

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 PARTNER FROM BUT000 INTO @DATA(ld_i_vendor_old).
 
"SELECT single PARTNER_FCT FROM CRMD_PARTNER INTO @DATA(ld_c_partner_fct).
 
 
 
 
 
 
"SELECT single PARTNER FROM BUT000 INTO @DATA(ld_i_vendor_new).
 
 
 
 
 
 
 
 
 
"SELECT single DESCRIPTION FROM BBP_PDS_HEADER INTO @DATA(ld_i_ctr_description).
 
 
 
 
 
 
 


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!