SAP FCO_EBPR_API_TMP_SAVE Function Module for Event-Based Posting Rule API - TMP Save
FCO_EBPR_API_TMP_SAVE is a standard fco ebpr api tmp save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Event-Based Posting Rule API - TMP Save 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 fco ebpr api tmp save FM, simply by entering the name FCO_EBPR_API_TMP_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCO_EBPR_API
Program Name: SAPLFCO_EBPR_API
Main Program: SAPLFCO_EBPR_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FCO_EBPR_API_TMP_SAVE 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 'FCO_EBPR_API_TMP_SAVE'"Event-Based Posting Rule API - TMP Save.
EXPORTING
IS_TMP_RULE_SETTING = "
IT_TMP_RULE = "
EXCEPTIONS
TMP_RULES_CANNOT_BE_SAVED = 1
IMPORTING Parameters details for FCO_EBPR_API_TMP_SAVE
IS_TMP_RULE_SETTING -
Data type: FCOT_EBPR_TMPSTGOptional: No
Call by Reference: No ( called with pass by value option)
IT_TMP_RULE -
Data type: TFCOT_EBPR_TMPRULOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TMP_RULES_CANNOT_BE_SAVED - TMP Rules can't be saved to database
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FCO_EBPR_API_TMP_SAVE 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_is_tmp_rule_setting | TYPE FCOT_EBPR_TMPSTG, " | |||
| lv_tmp_rules_cannot_be_saved | TYPE FCOT_EBPR_TMPSTG, " | |||
| lv_it_tmp_rule | TYPE TFCOT_EBPR_TMPRUL. " |
|   CALL FUNCTION 'FCO_EBPR_API_TMP_SAVE' "Event-Based Posting Rule API - TMP Save |
| EXPORTING | ||
| IS_TMP_RULE_SETTING | = lv_is_tmp_rule_setting | |
| IT_TMP_RULE | = lv_it_tmp_rule | |
| EXCEPTIONS | ||
| TMP_RULES_CANNOT_BE_SAVED = 1 | ||
| . " FCO_EBPR_API_TMP_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM FCO_EBPR_API_TMP_SAVE
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