SAP CRM_SALES_FCODE_CHECK Function Module for
CRM_SALES_FCODE_CHECK is a standard crm sales fcode check 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 crm sales fcode check FM, simply by entering the name CRM_SALES_FCODE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_SALES_UI
Program Name: SAPLCRM_SALES_UI
Main Program: SAPLCRM_SALES_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_SALES_FCODE_CHECK 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 'CRM_SALES_FCODE_CHECK'".
EXPORTING
IV_FCODE = "Function Code
IMPORTING
EV_LOCAL = "Logical Variable
IMPORTING Parameters details for CRM_SALES_FCODE_CHECK
IV_FCODE - Function Code
Data type: T185F-FCODEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_SALES_FCODE_CHECK
EV_LOCAL - Logical Variable
Data type: CRMT_BOOLEANOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_SALES_FCODE_CHECK 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_local | TYPE CRMT_BOOLEAN, " | |||
| lv_iv_fcode | TYPE T185F-FCODE. " |
|   CALL FUNCTION 'CRM_SALES_FCODE_CHECK' " |
| EXPORTING | ||
| IV_FCODE | = lv_iv_fcode | |
| IMPORTING | ||
| EV_LOCAL | = lv_ev_local | |
| . " CRM_SALES_FCODE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CRM_SALES_FCODE_CHECK
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 FCODE FROM T185F INTO @DATA(ld_iv_fcode). | ||||
Search for further information about these or an SAP related objects