SAP CRM_IST_SEARCH_SERVICE_ID Function Module for Suchen von Tel. nr zu Partner und Geschäftsvereinbarung
CRM_IST_SEARCH_SERVICE_ID is a standard crm ist search service id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Suchen von Tel. nr zu Partner und Geschäftsvereinbarung 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 crm ist search service id FM, simply by entering the name CRM_IST_SEARCH_SERVICE_ID into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_ORDER_SEARCH
Program Name: SAPLCRM_IST_ORDER_SEARCH
Main Program: SAPLCRM_IST_ORDER_SEARCH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_SEARCH_SERVICE_ID 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 'CRM_IST_SEARCH_SERVICE_ID'"Suchen von Tel. nr zu Partner und Geschäftsvereinbarung.
EXPORTING
* IV_PARTNER = "Business Partners
* IV_BUAG_ID = "Number of the Contract Account
* IV_OBJECT_ID = "Transaction ID
* IV_GUID = "Globally Unique Identifier
IMPORTING
ET_SERVICE_ID = "Table Type for Service ID
EXCEPTIONS
NO_INPUT_PARAMETER = 1 DOCUMENT_NOT_FOUND = 2 SERVICE_ID_NOT_FOUND = 3 WRONG_PARAMETER = 4
IMPORTING Parameters details for CRM_IST_SEARCH_SERVICE_ID
IV_PARTNER - Business Partners
Data type: BU_PARTNEROptional: Yes
Call by Reference: Yes
IV_BUAG_ID - Number of the Contract Account
Data type: CRMT_BUAG_IDOptional: Yes
Call by Reference: Yes
IV_OBJECT_ID - Transaction ID
Data type: CRMT_OBJECT_IDOptional: Yes
Call by Reference: Yes
IV_GUID - Globally Unique Identifier
Data type: GUIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_IST_SEARCH_SERVICE_ID
ET_SERVICE_ID - Table Type for Service ID
Data type: CRMT_IST_TELCO_SERVICEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_INPUT_PARAMETER - Keine inputparameters eingegeben.
Data type:Optional: No
Call by Reference: Yes
DOCUMENT_NOT_FOUND - Kein Vertrag wurde gefunden
Data type:Optional: No
Call by Reference: Yes
SERVICE_ID_NOT_FOUND - Kein Service ID wurde gefunden
Data type:Optional: No
Call by Reference: Yes
WRONG_PARAMETER - Wrong parameters
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_SEARCH_SERVICE_ID 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_iv_partner | TYPE BU_PARTNER, " | |||
lv_et_service_id | TYPE CRMT_IST_TELCO_SERVICE, " | |||
lv_no_input_parameter | TYPE CRMT_IST_TELCO_SERVICE, " | |||
lv_iv_buag_id | TYPE CRMT_BUAG_ID, " | |||
lv_document_not_found | TYPE CRMT_BUAG_ID, " | |||
lv_iv_object_id | TYPE CRMT_OBJECT_ID, " | |||
lv_service_id_not_found | TYPE CRMT_OBJECT_ID, " | |||
lv_iv_guid | TYPE GUID, " | |||
lv_wrong_parameter | TYPE GUID. " |
  CALL FUNCTION 'CRM_IST_SEARCH_SERVICE_ID' "Suchen von Tel. nr zu Partner und Geschäftsvereinbarung |
EXPORTING | ||
IV_PARTNER | = lv_iv_partner | |
IV_BUAG_ID | = lv_iv_buag_id | |
IV_OBJECT_ID | = lv_iv_object_id | |
IV_GUID | = lv_iv_guid | |
IMPORTING | ||
ET_SERVICE_ID | = lv_et_service_id | |
EXCEPTIONS | ||
NO_INPUT_PARAMETER = 1 | ||
DOCUMENT_NOT_FOUND = 2 | ||
SERVICE_ID_NOT_FOUND = 3 | ||
WRONG_PARAMETER = 4 | ||
. " CRM_IST_SEARCH_SERVICE_ID |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_SEARCH_SERVICE_ID
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