SAP BBP_IMS_GET_CONTACT Function Module for Ermittelt Kontakte
BBP_IMS_GET_CONTACT is a standard bbp ims get contact SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ermittelt Kontakte 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 ims get contact FM, simply by entering the name BBP_IMS_GET_CONTACT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_IV_IMS
Program Name: SAPLBBP_IV_IMS
Main Program: SAPLBBP_IV_IMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_IMS_GET_CONTACT 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_IMS_GET_CONTACT'"Ermittelt Kontakte.
EXPORTING
IS_EXCEPTION = "Globally Unique Identifier
* IV_RECIP_ROLE = "IMS Rolle für den Kontakt
* IV_DEFAULT_RECIP = "Default Kontakt
IMPORTING
ET_CONTACT = "IMS Kontakte
EXCEPTIONS
WRONG_CALL = 1 NO_PO_FOUND = 2 NO_REFERENCE = 3 NO_PARTNER_FOUND = 4
IMPORTING Parameters details for BBP_IMS_GET_CONTACT
IS_EXCEPTION - Globally Unique Identifier
Data type: BBPS_EVENTOptional: No
Call by Reference: Yes
IV_RECIP_ROLE - IMS Rolle für den Kontakt
Data type: IMS_CONTACT_ROLEOptional: Yes
Call by Reference: Yes
IV_DEFAULT_RECIP - Default Kontakt
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_IMS_GET_CONTACT
ET_CONTACT - IMS Kontakte
Data type: BBPT_IMS_CONTACTOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_CALL - Parameters of module are missing
Data type:Optional: No
Call by Reference: Yes
NO_PO_FOUND - No reference object forun
Data type:Optional: No
Call by Reference: Yes
NO_REFERENCE - references are initial
Data type:Optional: No
Call by Reference: Yes
NO_PARTNER_FOUND - partner not available
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_IMS_GET_CONTACT 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_et_contact | TYPE BBPT_IMS_CONTACT, " | |||
| lv_wrong_call | TYPE BBPT_IMS_CONTACT, " | |||
| lv_is_exception | TYPE BBPS_EVENT, " | |||
| lv_no_po_found | TYPE BBPS_EVENT, " | |||
| lv_iv_recip_role | TYPE IMS_CONTACT_ROLE, " | |||
| lv_no_reference | TYPE IMS_CONTACT_ROLE, " | |||
| lv_iv_default_recip | TYPE XFELD, " | |||
| lv_no_partner_found | TYPE XFELD. " |
|   CALL FUNCTION 'BBP_IMS_GET_CONTACT' "Ermittelt Kontakte |
| EXPORTING | ||
| IS_EXCEPTION | = lv_is_exception | |
| IV_RECIP_ROLE | = lv_iv_recip_role | |
| IV_DEFAULT_RECIP | = lv_iv_default_recip | |
| IMPORTING | ||
| ET_CONTACT | = lv_et_contact | |
| EXCEPTIONS | ||
| WRONG_CALL = 1 | ||
| NO_PO_FOUND = 2 | ||
| NO_REFERENCE = 3 | ||
| NO_PARTNER_FOUND = 4 | ||
| . " BBP_IMS_GET_CONTACT | ||
ABAP code using 7.40 inline data declarations to call FM BBP_IMS_GET_CONTACT
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