SAP FMCU_CHECK_DOCTYPE Function Module for Check existence of document types

Search SAP Function Modules

FMCU_CHECK_DOCTYPE is a standard fmcu check doctype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check existence of document types 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 fmcu check doctype FM, simply by entering the name FMCU_CHECK_DOCTYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMCU_BUSERVICE
Program Name: SAPLFMCU_BUSERVICE
Main Program: SAPLFMCU_BUSERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCU_CHECK_DOCTYPE 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 'FMCU_CHECK_DOCTYPE'"Check existence of document types
  EXPORTING
   I_DOCTYPE =  "Budget entry document type
*  I_FLG_RELEASE =  "Flag for release
*  I_FLG_BUDGET =  "Flag for budget
*  I_FLG_STAT =  "Flag for statistical
*  I_FLG_NO_ROLLUP =  "Flag for excluding doc. types with rollup

 IMPORTING
   E_DOCTYPE_TXT =  "Budget entry document type text
   E_NRNUMBER =  "Number range number
   E_FLG_WORKFLOW_ACTIVE =  "Flag for workflow activation

EXCEPTIONS
   NO_DOCTYPE = 1    NO_DOCTYPE_RELEASE = 2 

.

IMPORTING Parameters details for FMCU_CHECK_DOCTYPE

I_DOCTYPE - Budget entry document type

Data type: BUED_DOCTYPE
Optional: No
Call by Reference: Yes

I_FLG_RELEASE - Flag for release

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_BUDGET - Flag for budget

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_STAT - Flag for statistical

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_NO_ROLLUP - Flag for excluding doc. types with rollup

Data type: XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMCU_CHECK_DOCTYPE

E_DOCTYPE_TXT - Budget entry document type text

Data type: BUED_DOCTYPETEXT
Optional: No
Call by Reference: Yes

E_NRNUMBER - Number range number

Data type: NUMKR
Optional: No
Call by Reference: Yes

E_FLG_WORKFLOW_ACTIVE - Flag for workflow activation

Data type: FMED_WORKFLOW_ACTIVE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_DOCTYPE - no document type found

Data type:
Optional: No
Call by Reference: Yes

NO_DOCTYPE_RELEASE - no document type found for release

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCU_CHECK_DOCTYPE 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.

ABAP code using 7.40 inline data declarations to call FM FMCU_CHECK_DOCTYPE

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.

Search for further information about these or an SAP related objects