SAP EDI_CPIC_TRAILER_SEND Function Module for IDoc: Send header to R/2 System
EDI_CPIC_TRAILER_SEND is a standard edi cpic trailer 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 IDoc: Send header to R/2 System 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 edi cpic trailer send FM, simply by entering the name EDI_CPIC_TRAILER_SEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDI9
Program Name: SAPLEDI9
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDI_CPIC_TRAILER_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 'EDI_CPIC_TRAILER_SEND'"IDoc: Send header to R/2 System.
EXPORTING
NUMBER_OF_OBJECTS_SENT = "
EXCEPTIONS
TRAILER_SEND_ERROR = 1
IMPORTING Parameters details for EDI_CPIC_TRAILER_SEND
NUMBER_OF_OBJECTS_SENT -
Data type: EDIIT-OBJCNTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TRAILER_SEND_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EDI_CPIC_TRAILER_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.| DATA: | ||||
| lv_trailer_send_error | TYPE STRING, " | |||
| lv_number_of_objects_sent | TYPE EDIIT-OBJCNT. " |
|   CALL FUNCTION 'EDI_CPIC_TRAILER_SEND' "IDoc: Send header to R/2 System |
| EXPORTING | ||
| NUMBER_OF_OBJECTS_SENT | = lv_number_of_objects_sent | |
| EXCEPTIONS | ||
| TRAILER_SEND_ERROR = 1 | ||
| . " EDI_CPIC_TRAILER_SEND | ||
ABAP code using 7.40 inline data declarations to call FM EDI_CPIC_TRAILER_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.| "SELECT single OBJCNT FROM EDIIT INTO @DATA(ld_number_of_objects_sent). | ||||
Search for further information about these or an SAP related objects