SAP CACS00_BDTI_HIDEDOC Function Module for NOTRANSL: Feststellen ob der aktuelle DOC-Subscreen ausgebledet werden sol









CACS00_BDTI_HIDEDOC is a standard cacs00 bdti hidedoc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Feststellen ob der aktuelle DOC-Subscreen ausgebledet werden sol 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 cacs00 bdti hidedoc FM, simply by entering the name CACS00_BDTI_HIDEDOC into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS00_BDTI_HIDEDOC 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 'CACS00_BDTI_HIDEDOC'"NOTRANSL: Feststellen ob der aktuelle DOC-Subscreen ausgebledet werden sol
EXPORTING
* I_DYNNR = "ABAP Program, Current Screen Number
* I_FLG_GET_FIELDS = "Single-Character Indicator

IMPORTING
E_FLG_HIDE = "Single-Character Indicator

TABLES
* E_FIELDS = "Hidden Fields in Document Creation/Display

EXCEPTIONS
DYNPRO_UNKNOWN = 1
.



IMPORTING Parameters details for CACS00_BDTI_HIDEDOC

I_DYNNR - ABAP Program, Current Screen Number

Data type: SY-DYNNR
Optional: Yes
Call by Reference: Yes

I_FLG_GET_FIELDS - Single-Character Indicator

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

EXPORTING Parameters details for CACS00_BDTI_HIDEDOC

E_FLG_HIDE - Single-Character Indicator

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

TABLES Parameters details for CACS00_BDTI_HIDEDOC

E_FIELDS - Hidden Fields in Document Creation/Display

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

EXCEPTIONS details

DYNPRO_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS00_BDTI_HIDEDOC 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_i_dynnr  TYPE SY-DYNNR, "   
lt_e_fields  TYPE STANDARD TABLE OF TCACS_HIDEDOC02, "   
lv_e_flg_hide  TYPE CHAR1, "   
lv_dynpro_unknown  TYPE CHAR1, "   
lv_i_flg_get_fields  TYPE CHAR1. "   

  CALL FUNCTION 'CACS00_BDTI_HIDEDOC'  "NOTRANSL: Feststellen ob der aktuelle DOC-Subscreen ausgebledet werden sol
    EXPORTING
         I_DYNNR = lv_i_dynnr
         I_FLG_GET_FIELDS = lv_i_flg_get_fields
    IMPORTING
         E_FLG_HIDE = lv_e_flg_hide
    TABLES
         E_FIELDS = lt_e_fields
    EXCEPTIONS
        DYNPRO_UNKNOWN = 1
. " CACS00_BDTI_HIDEDOC




ABAP code using 7.40 inline data declarations to call FM CACS00_BDTI_HIDEDOC

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 DYNNR FROM SY INTO @DATA(ld_i_dynnr).
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!