SAP BBP_CTR_UI_MAIL_SF_SEND Function Module for dsfdsafdsf

Search SAP Function Modules

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

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

Function BBP_CTR_UI_MAIL_SF_SEND 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_CTR_UI_MAIL_SF_SEND'"dsfdsafdsf
  EXPORTING
   IV_GUID =  "GUID des Kontrakts
*  IV_APPEND_URL =  "Feld zum Ankreuzen
*  IV_FOLLOW_ON_GUID =  "GUID des Folgekontrakts
*  IV_BID_GUID =  "GUID der Ausschreibung
*  IV_USER =  "R/3-System, Anmeldename des Benutzers
*  IV_COMMIT =  "Feld zum Ankreuzen
*  IV_EVENT =  "Bildschirmbilder, Funktionscode, der PAI ausgelöst hat
*  IV_ATTACHMENT_TYPE =  "Kürzel für den Dokumenttyp
*  IV_ATTACHMENT_SUBJECT =  "Kurze Beschreibung des Inhaltes
*  IT_ATTACHMENT =  "objcont und objhead als Tabellentyp

EXCEPTIONS
   NO_MAIL_ADDRESS = 1    NO_OUTPUT = 2 

.

IMPORTING Parameters details for BBP_CTR_UI_MAIL_SF_SEND

IV_GUID - GUID des Kontrakts

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

IV_APPEND_URL - Feld zum Ankreuzen

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

IV_FOLLOW_ON_GUID - GUID des Folgekontrakts

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

IV_BID_GUID - GUID der Ausschreibung

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

IV_USER - R/3-System, Anmeldename des Benutzers

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

IV_COMMIT - Feld zum Ankreuzen

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

IV_EVENT - Bildschirmbilder, Funktionscode, der PAI ausgelöst hat

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

IV_ATTACHMENT_TYPE - Kürzel für den Dokumenttyp

Data type: SOODK-OBJTP
Optional: Yes
Call by Reference: Yes

IV_ATTACHMENT_SUBJECT - Kurze Beschreibung des Inhaltes

Data type: SOOD-OBJDES
Optional: Yes
Call by Reference: Yes

IT_ATTACHMENT - objcont und objhead als Tabellentyp

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

EXCEPTIONS details

NO_MAIL_ADDRESS - Keine Email Adresse gefunden

Data type:
Optional: No
Call by Reference: Yes

NO_OUTPUT - keine Ausgabe erzeugt.

Data type:
Optional: No
Call by Reference: Yes

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

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