SAP ITEM_DERIVE_FIELDS Function Module for
ITEM_DERIVE_FIELDS is a standard item derive fields 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 item derive fields FM, simply by entering the name ITEM_DERIVE_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FI_ITEMS
Program Name: SAPLFI_ITEMS
Main Program: SAPLFI_ITEMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function ITEM_DERIVE_FIELDS 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 'ITEM_DERIVE_FIELDS'".
EXPORTING
* S_T001 = "Company Code
* S_BSEGP = "Additional Information for Line Items (Special Fields)
KEY_DATE = "Date and Time, Current (Application Server) Date
* XOPVW = 'X' "
* X_ICONS_ONLY = ' ' "
* I_KALSM = "Procedure (Pricing, Output Control, Acct. Det., Costing,...)
CHANGING
S_ITEM = "Line Item data for Customer/Vendor/G/L Account
EXCEPTIONS
BAD_INPUT = 1
IMPORTING Parameters details for ITEM_DERIVE_FIELDS
S_T001 - Company Code
Data type: T001Optional: Yes
Call by Reference: Yes
S_BSEGP - Additional Information for Line Items (Special Fields)
Data type: BSEGPOptional: Yes
Call by Reference: Yes
KEY_DATE - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
XOPVW -
Data type: SKB1-XOPVWDefault: 'X'
Optional: Yes
Call by Reference: Yes
X_ICONS_ONLY -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_KALSM - Procedure (Pricing, Output Control, Acct. Det., Costing,...)
Data type: T005-KALSMOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for ITEM_DERIVE_FIELDS
S_ITEM - Line Item data for Customer/Vendor/G/L Account
Data type: RFPOSXEXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
BAD_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ITEM_DERIVE_FIELDS 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_s_item | TYPE RFPOSXEXT, " | |||
lv_s_t001 | TYPE T001, " | |||
lv_bad_input | TYPE T001, " | |||
lv_s_bsegp | TYPE BSEGP, " | |||
lv_key_date | TYPE SY-DATUM, " | |||
lv_xopvw | TYPE SKB1-XOPVW, " 'X' | |||
lv_x_icons_only | TYPE C, " SPACE | |||
lv_i_kalsm | TYPE T005-KALSM. " |
  CALL FUNCTION 'ITEM_DERIVE_FIELDS' " |
EXPORTING | ||
S_T001 | = lv_s_t001 | |
S_BSEGP | = lv_s_bsegp | |
KEY_DATE | = lv_key_date | |
XOPVW | = lv_xopvw | |
X_ICONS_ONLY | = lv_x_icons_only | |
I_KALSM | = lv_i_kalsm | |
CHANGING | ||
S_ITEM | = lv_s_item | |
EXCEPTIONS | ||
BAD_INPUT = 1 | ||
. " ITEM_DERIVE_FIELDS |
ABAP code using 7.40 inline data declarations to call FM ITEM_DERIVE_FIELDS
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 DATUM FROM SY INTO @DATA(ld_key_date). | ||||
"SELECT single XOPVW FROM SKB1 INTO @DATA(ld_xopvw). | ||||
DATA(ld_xopvw) | = 'X'. | |||
DATA(ld_x_icons_only) | = ' '. | |||
"SELECT single KALSM FROM T005 INTO @DATA(ld_i_kalsm). | ||||
Search for further information about these or an SAP related objects