SAP CRM_SRV_DELIVERY_TRIGGER Function Module for NOTRANSL: CRM Service: BTE Lieferavis
CRM_SRV_DELIVERY_TRIGGER is a standard crm srv delivery trigger 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: CRM Service: BTE Lieferavis 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 srv delivery trigger FM, simply by entering the name CRM_SRV_DELIVERY_TRIGGER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_SRV_LOG_EXT
Program Name: SAPLCRM_SRV_LOG_EXT
Main Program: SAPLCRM_SRV_LOG_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_SRV_DELIVERY_TRIGGER 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_SRV_DELIVERY_TRIGGER'"NOTRANSL: CRM Service: BTE Lieferavis.
TABLES
* T_XEKES = "Change Document Structure; Generated by RSSCD000
* T_YEKES = "Change Document Structure; Generated by RSSCD000
* PTI_XEKBE = "Purchasing Document History
* PTI_YEKBE = "Purchasing Document History
TABLES Parameters details for CRM_SRV_DELIVERY_TRIGGER
T_XEKES - Change Document Structure; Generated by RSSCD000
Data type: UEKESOptional: Yes
Call by Reference: Yes
T_YEKES - Change Document Structure; Generated by RSSCD000
Data type: UEKESOptional: Yes
Call by Reference: Yes
PTI_XEKBE - Purchasing Document History
Data type: EKBEOptional: Yes
Call by Reference: Yes
PTI_YEKBE - Purchasing Document History
Data type: EKBEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CRM_SRV_DELIVERY_TRIGGER 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_t_xekes | TYPE STANDARD TABLE OF UEKES, " | |||
| lt_t_yekes | TYPE STANDARD TABLE OF UEKES, " | |||
| lt_pti_xekbe | TYPE STANDARD TABLE OF EKBE, " | |||
| lt_pti_yekbe | TYPE STANDARD TABLE OF EKBE. " |
|   CALL FUNCTION 'CRM_SRV_DELIVERY_TRIGGER' "NOTRANSL: CRM Service: BTE Lieferavis |
| TABLES | ||
| T_XEKES | = lt_t_xekes | |
| T_YEKES | = lt_t_yekes | |
| PTI_XEKBE | = lt_pti_xekbe | |
| PTI_YEKBE | = lt_pti_yekbe | |
| . " CRM_SRV_DELIVERY_TRIGGER | ||
ABAP code using 7.40 inline data declarations to call FM CRM_SRV_DELIVERY_TRIGGER
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