SAP J_1A_CHANGES_KNAT_MF02D Function Module for NOTRANSL: Check, if something changed in table KNAT









J_1A_CHANGES_KNAT_MF02D is a standard j 1a changes knat mf02d SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check, if something changed in table KNAT 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 j 1a changes knat mf02d FM, simply by entering the name J_1A_CHANGES_KNAT_MF02D into the relevant SAP transaction such as SE37 or SE38.

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



Function J_1A_CHANGES_KNAT_MF02D 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 'J_1A_CHANGES_KNAT_MF02D'"NOTRANSL: Check, if something changed in table KNAT
IMPORTING
E_CHNG = "

TABLES
T_XKNAT = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJ1AT_001 User exit of report J_1AF105 at GET BKPF
EXIT_SAPLJ1AT_002 User exit of report J_1AF105 at GET BSEG
EXIT_SAPLJ1AT_003 User exit of report J_1AF106 at GET BKPF
EXIT_SAPLJ1AT_004 User exit of report J_1AF106 at GET BSEG
EXIT_SAPLJ1AT_005 User exit of report J_1AF105 at GET BKPF LATE

EXPORTING Parameters details for J_1A_CHANGES_KNAT_MF02D

E_CHNG -

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

TABLES Parameters details for J_1A_CHANGES_KNAT_MF02D

T_XKNAT -

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

Copy and paste ABAP code example for J_1A_CHANGES_KNAT_MF02D 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_e_chng  TYPE CDPOS-CHNGIND, "   
lt_t_xknat  TYPE STANDARD TABLE OF FKNAT. "   

  CALL FUNCTION 'J_1A_CHANGES_KNAT_MF02D'  "NOTRANSL: Check, if something changed in table KNAT
    IMPORTING
         E_CHNG = lv_e_chng
    TABLES
         T_XKNAT = lt_t_xknat
. " J_1A_CHANGES_KNAT_MF02D




ABAP code using 7.40 inline data declarations to call FM J_1A_CHANGES_KNAT_MF02D

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 CHNGIND FROM CDPOS INTO @DATA(ld_e_chng).
 
 


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!