SAP CTE_FND_SHOW_DOC_COMP_SET_DATA Function Module for Show document (e.g. JSON or XML files) set global data









CTE_FND_SHOW_DOC_COMP_SET_DATA is a standard cte fnd show doc comp set data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Show document (e.g. JSON or XML files) set global data 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 cte fnd show doc comp set data FM, simply by entering the name CTE_FND_SHOW_DOC_COMP_SET_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function CTE_FND_SHOW_DOC_COMP_SET_DATA 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 'CTE_FND_SHOW_DOC_COMP_SET_DATA'"Show document (e.g. JSON or XML files) set global data
  EXPORTING
   IV_ORIGINAL_DOCUMENT =  "Original Document content as string
   IS_HIGHLIGHT_CHANGED =  "
   IV_CHANGED_DOCUMENT =  "Changed Document content as string
*  IV_DOCUMENT_CONTENT_TYPE =  "Type of the document content (e.g. 'J' JSON, 'X' XML, 'B' binary etc.)
*  IV_ORIGINAL_FILENAME =  "For download: Default filename for download
*  IV_CHANGED_FILENAME =  "
   IV_SYSTEM_KEY =  "
   IV_OTYPE =  "Concur Integration - Object Type
*  IV_DISPLAY_AS_XML =  "
   IS_HIGHLIGHT =  "
.



IMPORTING Parameters details for CTE_FND_SHOW_DOC_COMP_SET_DATA

IV_ORIGINAL_DOCUMENT - Original Document content as string

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

IS_HIGHLIGHT_CHANGED -

Data type: CL_CTE_FND_JSON=>TY_HIGHLIGHT
Optional: No
Call by Reference: Yes

IV_CHANGED_DOCUMENT - Changed Document content as string

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

IV_DOCUMENT_CONTENT_TYPE - Type of the document content (e.g. 'J' JSON, 'X' XML, 'B' binary etc.)

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

IV_ORIGINAL_FILENAME - For download: Default filename for download

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

IV_CHANGED_FILENAME -

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

IV_SYSTEM_KEY -

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

IV_OTYPE - Concur Integration - Object Type

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

IV_DISPLAY_AS_XML -

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

IS_HIGHLIGHT -

Data type: CL_CTE_FND_JSON=>TY_HIGHLIGHT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CTE_FND_SHOW_DOC_COMP_SET_DATA 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_original_document  TYPE STRING, "   
lv_is_highlight_changed  TYPE CL_CTE_FND_JSON=>TY_HIGHLIGHT, "   
lv_iv_changed_document  TYPE STRING, "   
lv_iv_document_content_type  TYPE CTE_API_CONTENT_TYPE, "   
lv_iv_original_filename  TYPE STRING, "   
lv_iv_changed_filename  TYPE STRING, "   
lv_iv_system_key  TYPE CTE_SYSTEM_KEY_NUMBER, "   
lv_iv_otype  TYPE CTE_OTYPE, "   
lv_iv_display_as_xml  TYPE ABAP_BOOL, "   
lv_is_highlight  TYPE CL_CTE_FND_JSON=>TY_HIGHLIGHT. "   

  CALL FUNCTION 'CTE_FND_SHOW_DOC_COMP_SET_DATA'  "Show document (e.g. JSON or XML files) set global data
    EXPORTING
         IV_ORIGINAL_DOCUMENT = lv_iv_original_document
         IS_HIGHLIGHT_CHANGED = lv_is_highlight_changed
         IV_CHANGED_DOCUMENT = lv_iv_changed_document
         IV_DOCUMENT_CONTENT_TYPE = lv_iv_document_content_type
         IV_ORIGINAL_FILENAME = lv_iv_original_filename
         IV_CHANGED_FILENAME = lv_iv_changed_filename
         IV_SYSTEM_KEY = lv_iv_system_key
         IV_OTYPE = lv_iv_otype
         IV_DISPLAY_AS_XML = lv_iv_display_as_xml
         IS_HIGHLIGHT = lv_is_highlight
. " CTE_FND_SHOW_DOC_COMP_SET_DATA




ABAP code using 7.40 inline data declarations to call FM CTE_FND_SHOW_DOC_COMP_SET_DATA

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



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!