SAP HR_DK_FORMAT_F41_CORRECTION Function Module for
HR_DK_FORMAT_F41_CORRECTION is a standard hr dk format f41 correction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr dk format f41 correction FM, simply by entering the name HR_DK_FORMAT_F41_CORRECTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPMQ
Program Name: SAPLRPMQ
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_DK_FORMAT_F41_CORRECTION 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 'HR_DK_FORMAT_F41_CORRECTION'".
EXPORTING
FIRM = "
AMOUNT_STR = "
NUMBER_STR = "
AFREGNING = "
LONNUMMER = "
IMPORTING
PBSFORM = "
IMPORTING Parameters details for HR_DK_FORMAT_F41_CORRECTION
FIRM -
Data type:Optional: No
Call by Reference: Yes
AMOUNT_STR -
Data type:Optional: No
Call by Reference: Yes
NUMBER_STR -
Data type:Optional: No
Call by Reference: Yes
AFREGNING -
Data type:Optional: No
Call by Reference: Yes
LONNUMMER -
Data type:Optional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_DK_FORMAT_F41_CORRECTION
PBSFORM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_DK_FORMAT_F41_CORRECTION 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_firm | TYPE STRING, " | |||
| lv_pbsform | TYPE STRING, " | |||
| lv_amount_str | TYPE STRING, " | |||
| lv_number_str | TYPE STRING, " | |||
| lv_afregning | TYPE STRING, " | |||
| lv_lonnummer | TYPE STRING. " |
| CALL FUNCTION 'HR_DK_FORMAT_F41_CORRECTION' " |
| EXPORTING | ||
| FIRM | = lv_firm | |
| AMOUNT_STR | = lv_amount_str | |
| NUMBER_STR | = lv_number_str | |
| AFREGNING | = lv_afregning | |
| LONNUMMER | = lv_lonnummer | |
| IMPORTING | ||
| PBSFORM | = lv_pbsform | |
| . " HR_DK_FORMAT_F41_CORRECTION | ||
ABAP code using 7.40 inline data declarations to call FM HR_DK_FORMAT_F41_CORRECTION
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