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

Function JBD_EXP_TEMPLATE 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 'JBD_EXP_TEMPLATE'"Extraktion:.
EXPORTING
I_RECEIVERS = "Empfänger der IDocs
I_EXT_KEYS = "Tabelle der Schlüssel
* I_SUBOBJECTS = "Exportsubobjekt
I_MESTYP = "Nachrichtentyp
* I_CHANGE_TYPE = "Änderungsindikator
IMPORTING
E_BAPIRET = "Returntabelle
E_RECCNT = "Anzahl der bearbeiteten Objekte
E_ERROR_KEYS = "Tabelle der Schlüssel
IMPORTING Parameters details for JBD_EXP_TEMPLATE
I_RECEIVERS - Empfänger der IDocs
Data type: JBD_TAB_LOGSYSOptional: No
Call by Reference: Yes
I_EXT_KEYS - Tabelle der Schlüssel
Data type: JBD_TAB_TABKEYSOptional: No
Call by Reference: Yes
I_SUBOBJECTS - Exportsubobjekt
Data type: JBD_TAB_EXPSUBOBJOptional: Yes
Call by Reference: Yes
I_MESTYP - Nachrichtentyp
Data type: EDI_MESTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_CHANGE_TYPE - Änderungsindikator
Data type: JBD_DTE_CDCHGINDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for JBD_EXP_TEMPLATE
E_BAPIRET - Returntabelle
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
E_RECCNT - Anzahl der bearbeiteten Objekte
Data type: SY-DBCNTOptional: No
Call by Reference: No ( called with pass by value option)
E_ERROR_KEYS - Tabelle der Schlüssel
Data type: JBD_TAB_TABKEYSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JBD_EXP_TEMPLATE 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_e_bapiret | TYPE BAPIRET2_T, " | |||
| lv_i_receivers | TYPE JBD_TAB_LOGSYS, " | |||
| lv_e_reccnt | TYPE SY-DBCNT, " | |||
| lv_i_ext_keys | TYPE JBD_TAB_TABKEYS, " | |||
| lv_e_error_keys | TYPE JBD_TAB_TABKEYS, " | |||
| lv_i_subobjects | TYPE JBD_TAB_EXPSUBOBJ, " | |||
| lv_i_mestyp | TYPE EDI_MESTYP, " | |||
| lv_i_change_type | TYPE JBD_DTE_CDCHGIND. " |
|   CALL FUNCTION 'JBD_EXP_TEMPLATE' "Extraktion: |
| EXPORTING | ||
| I_RECEIVERS | = lv_i_receivers | |
| I_EXT_KEYS | = lv_i_ext_keys | |
| I_SUBOBJECTS | = lv_i_subobjects | |
| I_MESTYP | = lv_i_mestyp | |
| I_CHANGE_TYPE | = lv_i_change_type | |
| IMPORTING | ||
| E_BAPIRET | = lv_e_bapiret | |
| E_RECCNT | = lv_e_reccnt | |
| E_ERROR_KEYS | = lv_e_error_keys | |
| . " JBD_EXP_TEMPLATE | ||
ABAP code using 7.40 inline data declarations to call FM JBD_EXP_TEMPLATE
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 DBCNT FROM SY INTO @DATA(ld_e_reccnt). | ||||
Search for further information about these or an SAP related objects