SAP ISB_USER_EXIT_301 Function Module for IS-B: Einsprung für User Exit 301 (Währungseinfluß)
ISB_USER_EXIT_301 is a standard isb user exit 301 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-B: Einsprung für User Exit 301 (Währungseinfluß) 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 isb user exit 301 FM, simply by entering the name ISB_USER_EXIT_301 into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBTR
Program Name: SAPLJBTR
Main Program: SAPLJBTR
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISB_USER_EXIT_301 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 'ISB_USER_EXIT_301'"IS-B: Einsprung für User Exit 301 (Währungseinfluß).
EXPORTING
I_ERKRS = "Ergebnisbereich
I_DKALK = "Kalkulationsstichtag
TABLES
T_VALUES = "Einzelposten
T_OBJECTS = "Finanzobjekte
IMPORTING Parameters details for ISB_USER_EXIT_301
I_ERKRS - Ergebnisbereich
Data type: TKEB-ERKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_DKALK - Kalkulationsstichtag
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISB_USER_EXIT_301
T_VALUES - Einzelposten
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
T_OBJECTS - Finanzobjekte
Data type: JBIXOBJOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISB_USER_EXIT_301 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_i_erkrs | TYPE TKEB-ERKRS, " | |||
| lt_t_values | TYPE STANDARD TABLE OF TKEB, " | |||
| lv_i_dkalk | TYPE SY-DATUM, " | |||
| lt_t_objects | TYPE STANDARD TABLE OF JBIXOBJ. " |
|   CALL FUNCTION 'ISB_USER_EXIT_301' "IS-B: Einsprung für User Exit 301 (Währungseinfluß) |
| EXPORTING | ||
| I_ERKRS | = lv_i_erkrs | |
| I_DKALK | = lv_i_dkalk | |
| TABLES | ||
| T_VALUES | = lt_t_values | |
| T_OBJECTS | = lt_t_objects | |
| . " ISB_USER_EXIT_301 | ||
ABAP code using 7.40 inline data declarations to call FM ISB_USER_EXIT_301
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 ERKRS FROM TKEB INTO @DATA(ld_i_erkrs). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_dkalk). | ||||
Search for further information about these or an SAP related objects