SAP CR_API_FIELD_SELECTION Function Module for Work centers: API to get field influence
CR_API_FIELD_SELECTION is a standard cr api field selection SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Work centers: API to get field influence 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 cr api field selection FM, simply by entering the name CR_API_FIELD_SELECTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRA0
Program Name: SAPLCRA0
Main Program: SAPLCRA0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CR_API_FIELD_SELECTION 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 'CR_API_FIELD_SELECTION'"Work centers: API to get field influence.
EXPORTING
IV_GROUP = "Field selection control: Screen group
IV_FIELD = "Field name
IV_VALUE = "
IMPORTING
ET_MESSAGE = "Return Parameter
IMPORTING Parameters details for CR_API_FIELD_SELECTION
IV_GROUP - Field selection control: Screen group
Data type: TFAW-BLDGROptional: No
Call by Reference: Yes
IV_FIELD - Field name
Data type: TFAWF-MFELDOptional: No
Call by Reference: Yes
IV_VALUE -
Data type: COptional: No
Call by Reference: Yes
EXPORTING Parameters details for CR_API_FIELD_SELECTION
ET_MESSAGE - Return Parameter
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CR_API_FIELD_SELECTION 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_iv_group | TYPE TFAW-BLDGR, " | |||
| lv_et_message | TYPE BAPIRET2_T, " | |||
| lv_iv_field | TYPE TFAWF-MFELD, " | |||
| lv_iv_value | TYPE C. " |
|   CALL FUNCTION 'CR_API_FIELD_SELECTION' "Work centers: API to get field influence |
| EXPORTING | ||
| IV_GROUP | = lv_iv_group | |
| IV_FIELD | = lv_iv_field | |
| IV_VALUE | = lv_iv_value | |
| IMPORTING | ||
| ET_MESSAGE | = lv_et_message | |
| . " CR_API_FIELD_SELECTION | ||
ABAP code using 7.40 inline data declarations to call FM CR_API_FIELD_SELECTION
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 BLDGR FROM TFAW INTO @DATA(ld_iv_group). | ||||
| "SELECT single MFELD FROM TFAWF INTO @DATA(ld_iv_field). | ||||
Search for further information about these or an SAP related objects