SAP HR_FEATURE_BACKFIELD Function Module for Reading a Feature with Field Return
HR_FEATURE_BACKFIELD is a standard hr feature backfield SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reading a Feature with Field Return 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 hr feature backfield FM, simply by entering the name HR_FEATURE_BACKFIELD into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRP3
Program Name: SAPLHRP3
Main Program:
Appliation area:
Release date: 23-Jul-1998
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_FEATURE_BACKFIELD 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_FEATURE_BACKFIELD'"Reading a Feature with Field Return.
EXPORTING
FEATURE = "Feature Name
STRUC_CONTENT = "Feature Structure Contents
* KIND_OF_ERROR = "Desired Reaction to Error
IMPORTING
BACK = "Return Value
CHANGING
* STATUS = "Back Value Status
EXCEPTIONS
DUMMY = 1 ERROR_OPERATION = 2 NO_BACKVALUE = 3 FEATURE_NOT_GENERATED = 4 INVALID_SIGN_IN_FUNID = 5 FIELD_IN_REPORT_TAB_IN_PE03 = 6
IMPORTING Parameters details for HR_FEATURE_BACKFIELD
FEATURE - Feature Name
Data type: T549B-NAMENOptional: No
Call by Reference: No ( called with pass by value option)
STRUC_CONTENT - Feature Structure Contents
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KIND_OF_ERROR - Desired Reaction to Error
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HR_FEATURE_BACKFIELD
BACK - Return Value
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for HR_FEATURE_BACKFIELD
STATUS - Back Value Status
Data type:Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
DUMMY - Dummy for Compatibility Reasons (Status 1)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_OPERATION - Error Operation in Feature
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BACKVALUE - No Assignment Planned (No Error)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FEATURE_NOT_GENERATED - Feature Not Generated
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_SIGN_IN_FUNID - There is an invalid value in field T549D-FUNID
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIELD_IN_REPORT_TAB_IN_PE03 - In Report Field-, in PE03 Table Return
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_FEATURE_BACKFIELD 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_back | TYPE STRING, " | |||
lv_dummy | TYPE STRING, " | |||
lv_status | TYPE STRING, " | |||
lv_feature | TYPE T549B-NAMEN, " | |||
lv_struc_content | TYPE T549B, " | |||
lv_error_operation | TYPE T549B, " | |||
lv_no_backvalue | TYPE T549B, " | |||
lv_kind_of_error | TYPE T549B, " | |||
lv_feature_not_generated | TYPE T549B, " | |||
lv_invalid_sign_in_funid | TYPE T549B, " | |||
lv_field_in_report_tab_in_pe03 | TYPE T549B. " |
  CALL FUNCTION 'HR_FEATURE_BACKFIELD' "Reading a Feature with Field Return |
EXPORTING | ||
FEATURE | = lv_feature | |
STRUC_CONTENT | = lv_struc_content | |
KIND_OF_ERROR | = lv_kind_of_error | |
IMPORTING | ||
BACK | = lv_back | |
CHANGING | ||
STATUS | = lv_status | |
EXCEPTIONS | ||
DUMMY = 1 | ||
ERROR_OPERATION = 2 | ||
NO_BACKVALUE = 3 | ||
FEATURE_NOT_GENERATED = 4 | ||
INVALID_SIGN_IN_FUNID = 5 | ||
FIELD_IN_REPORT_TAB_IN_PE03 = 6 | ||
. " HR_FEATURE_BACKFIELD |
ABAP code using 7.40 inline data declarations to call FM HR_FEATURE_BACKFIELD
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 NAMEN FROM T549B INTO @DATA(ld_feature). | ||||
Search for further information about these or an SAP related objects