SAP CHANGEDOCUMENT_IS_FIELD_INTRAW Function Module for
CHANGEDOCUMENT_IS_FIELD_INTRAW is a standard changedocument is field intraw 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 changedocument is field intraw FM, simply by entering the name CHANGEDOCUMENT_IS_FIELD_INTRAW into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCD0
Program Name: SAPLSCD0
Main Program: SAPLSCD0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CHANGEDOCUMENT_IS_FIELD_INTRAW 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 'CHANGEDOCUMENT_IS_FIELD_INTRAW'".
EXPORTING
IV_TABNAME = "Table Name
IV_FIELDNAME = "Field Name
IMPORTING
EV_TRUE = "
EXCEPTIONS
NO_TABLENAME = 1 NO_FIELDNAME = 2 WRONG_FIELDNAME = 3
IMPORTING Parameters details for CHANGEDOCUMENT_IS_FIELD_INTRAW
IV_TABNAME - Table Name
Data type: CDPOS-TABNAMEOptional: No
Call by Reference: Yes
IV_FIELDNAME - Field Name
Data type: CDPOS-FNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CHANGEDOCUMENT_IS_FIELD_INTRAW
EV_TRUE -
Data type: IOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_TABLENAME -
Data type:Optional: No
Call by Reference: Yes
NO_FIELDNAME -
Data type:Optional: No
Call by Reference: Yes
WRONG_FIELDNAME -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CHANGEDOCUMENT_IS_FIELD_INTRAW 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_ev_true | TYPE I, " | |||
lv_iv_tabname | TYPE CDPOS-TABNAME, " | |||
lv_no_tablename | TYPE CDPOS, " | |||
lv_iv_fieldname | TYPE CDPOS-FNAME, " | |||
lv_no_fieldname | TYPE CDPOS, " | |||
lv_wrong_fieldname | TYPE CDPOS. " |
  CALL FUNCTION 'CHANGEDOCUMENT_IS_FIELD_INTRAW' " |
EXPORTING | ||
IV_TABNAME | = lv_iv_tabname | |
IV_FIELDNAME | = lv_iv_fieldname | |
IMPORTING | ||
EV_TRUE | = lv_ev_true | |
EXCEPTIONS | ||
NO_TABLENAME = 1 | ||
NO_FIELDNAME = 2 | ||
WRONG_FIELDNAME = 3 | ||
. " CHANGEDOCUMENT_IS_FIELD_INTRAW |
ABAP code using 7.40 inline data declarations to call FM CHANGEDOCUMENT_IS_FIELD_INTRAW
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 TABNAME FROM CDPOS INTO @DATA(ld_iv_tabname). | ||||
"SELECT single FNAME FROM CDPOS INTO @DATA(ld_iv_fieldname). | ||||
Search for further information about these or an SAP related objects