SAP FM_FEES_SAVE_SCHEDULE Function Module for Write fee schedule to database if document is saved
FM_FEES_SAVE_SCHEDULE is a standard fm fees save schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write fee schedule to database if document is saved 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 fm fees save schedule FM, simply by entering the name FM_FEES_SAVE_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM_FEE_SCHED_SERVICES
Program Name: SAPLFM_FEE_SCHED_SERVICES
Main Program: SAPLFM_FEE_SCHED_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_FEES_SAVE_SCHEDULE 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 'FM_FEES_SAVE_SCHEDULE'"Write fee schedule to database if document is saved.
EXPORTING
I_AWTYP = "Reference Transaction
I_AWREF = "Reference Document Number
I_AWORG = "Reference Organizational Units
IMPORTING Parameters details for FM_FEES_SAVE_SCHEDULE
I_AWTYP - Reference Transaction
Data type: AWTYPOptional: No
Call by Reference: Yes
I_AWREF - Reference Document Number
Data type: AWREFOptional: No
Call by Reference: Yes
I_AWORG - Reference Organizational Units
Data type: AWORGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_FEES_SAVE_SCHEDULE 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_awtyp | TYPE AWTYP, " | |||
| lv_i_awref | TYPE AWREF, " | |||
| lv_i_aworg | TYPE AWORG. " |
|   CALL FUNCTION 'FM_FEES_SAVE_SCHEDULE' "Write fee schedule to database if document is saved |
| EXPORTING | ||
| I_AWTYP | = lv_i_awtyp | |
| I_AWREF | = lv_i_awref | |
| I_AWORG | = lv_i_aworg | |
| . " FM_FEES_SAVE_SCHEDULE | ||
ABAP code using 7.40 inline data declarations to call FM FM_FEES_SAVE_SCHEDULE
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