SAP FM_INPUT_CHECK_POSTING_DATE Function Module for Ensures posting date used for FM accouting view









FM_INPUT_CHECK_POSTING_DATE is a standard fm input check posting date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ensures posting date used for FM accouting view 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 input check posting date FM, simply by entering the name FM_INPUT_CHECK_POSTING_DATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMWR_E
Program Name: SAPLFMWR_E
Main Program: SAPLFMWR_E
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FM_INPUT_CHECK_POSTING_DATE 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_INPUT_CHECK_POSTING_DATE'"Ensures posting date used for FM accouting view
EXPORTING
I_PROFILE = "
I_WRTTP = "
* I_VRGNG = ' ' "
* I_PAYMENT_DATE_TYPE = ' ' "
* I_COMMITMENT_DATE_TYPE = ' ' "
* I_FLG_ORIG_VALTYPE_PROFIL = ' ' "

CHANGING
* C_F_FMUP01 = "

EXCEPTIONS
PAYMENT_ACCOUNTING_VIEW_USED = 1 COMMIT_ACCOUNTING_VIEW_USED = 2
.



IMPORTING Parameters details for FM_INPUT_CHECK_POSTING_DATE

I_PROFILE -

Data type: FMUP01-PROFIL
Optional: No
Call by Reference: Yes

I_WRTTP -

Data type: FMUP01-WRTTP
Optional: No
Call by Reference: Yes

I_VRGNG -

Data type: FMUP01-VRGNG
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_PAYMENT_DATE_TYPE -

Data type: FMUP01-PAYDTFYEAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_COMMITMENT_DATE_TYPE -

Data type: FMUP01-COMDTFYEAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_ORIG_VALTYPE_PROFIL -

Data type: FMDY-XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for FM_INPUT_CHECK_POSTING_DATE

C_F_FMUP01 -

Data type: FMUP01
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PAYMENT_ACCOUNTING_VIEW_USED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

COMMIT_ACCOUNTING_VIEW_USED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FM_INPUT_CHECK_POSTING_DATE 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_profile  TYPE FMUP01-PROFIL, "   
lv_c_f_fmup01  TYPE FMUP01, "   
lv_payment_accounting_view_used  TYPE FMUP01, "   
lv_i_wrttp  TYPE FMUP01-WRTTP, "   
lv_commit_accounting_view_used  TYPE FMUP01, "   
lv_i_vrgng  TYPE FMUP01-VRGNG, "   SPACE
lv_i_payment_date_type  TYPE FMUP01-PAYDTFYEAR, "   SPACE
lv_i_commitment_date_type  TYPE FMUP01-COMDTFYEAR, "   SPACE
lv_i_flg_orig_valtype_profil  TYPE FMDY-XFELD. "   SPACE

  CALL FUNCTION 'FM_INPUT_CHECK_POSTING_DATE'  "Ensures posting date used for FM accouting view
    EXPORTING
         I_PROFILE = lv_i_profile
         I_WRTTP = lv_i_wrttp
         I_VRGNG = lv_i_vrgng
         I_PAYMENT_DATE_TYPE = lv_i_payment_date_type
         I_COMMITMENT_DATE_TYPE = lv_i_commitment_date_type
         I_FLG_ORIG_VALTYPE_PROFIL = lv_i_flg_orig_valtype_profil
    CHANGING
         C_F_FMUP01 = lv_c_f_fmup01
    EXCEPTIONS
        PAYMENT_ACCOUNTING_VIEW_USED = 1
        COMMIT_ACCOUNTING_VIEW_USED = 2
. " FM_INPUT_CHECK_POSTING_DATE




ABAP code using 7.40 inline data declarations to call FM FM_INPUT_CHECK_POSTING_DATE

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 PROFIL FROM FMUP01 INTO @DATA(ld_i_profile).
 
 
 
"SELECT single WRTTP FROM FMUP01 INTO @DATA(ld_i_wrttp).
 
 
"SELECT single VRGNG FROM FMUP01 INTO @DATA(ld_i_vrgng).
DATA(ld_i_vrgng) = ' '.
 
"SELECT single PAYDTFYEAR FROM FMUP01 INTO @DATA(ld_i_payment_date_type).
DATA(ld_i_payment_date_type) = ' '.
 
"SELECT single COMDTFYEAR FROM FMUP01 INTO @DATA(ld_i_commitment_date_type).
DATA(ld_i_commitment_date_type) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_orig_valtype_profil).
DATA(ld_i_flg_orig_valtype_profil) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!