SAP KW_DOCUMENT_GET Function Module for









KW_DOCUMENT_GET is a standard kw document get 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 kw document get FM, simply by entering the name KW_DOCUMENT_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function KW_DOCUMENT_GET 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 'KW_DOCUMENT_GET'"
EXPORTING
NOTETYPE = "Valid Document Types
* APPLICATION = 'CU' "Character field of length 6
* LANGUAGE = "SAP R/3 System, Current Language
OBJECTKEY = "Object Key
* SHORT_TABLE = "Single-Character Flag
* DOCUMENT_CLASS = 'SPRO_GEN' "Document Class

IMPORTING
DOCUMENT_TITLE = "Explanatory text
DOCUMENT_FORMAT = "Project management document file extension
CANCEL = "Single-Character Flag

TABLES
* FILE_CONTENT_ASCII = "SDOK: Line of text document content for WWW server
* FILE_CONTENT_BINARY = "SDOK: Line of binary document content for WWW server
* TEXT_TABLE = "Text Table
.



IMPORTING Parameters details for KW_DOCUMENT_GET

NOTETYPE - Valid Document Types

Data type: TNOTEEPR-NOTETYPE
Optional: No
Call by Reference: No ( called with pass by value option)

APPLICATION - Character field of length 6

Data type: CHAR6
Default: 'CU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE - SAP R/3 System, Current Language

Data type: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECTKEY - Object Key

Data type: TNOTFPR-OBJECTKEY
Optional: No
Call by Reference: No ( called with pass by value option)

SHORT_TABLE - Single-Character Flag

Data type: CHAR1
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCUMENT_CLASS - Document Class

Data type: SDOK_CLASS
Default: 'SPRO_GEN'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for KW_DOCUMENT_GET

DOCUMENT_TITLE - Explanatory text

Data type: HIER_TEXTS-TEXT
Optional: No
Call by Reference: No ( called with pass by value option)

DOCUMENT_FORMAT - Project management document file extension

Data type: PROJ_FILE
Optional: No
Call by Reference: No ( called with pass by value option)

CANCEL - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for KW_DOCUMENT_GET

FILE_CONTENT_ASCII - SDOK: Line of text document content for WWW server

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

FILE_CONTENT_BINARY - SDOK: Line of binary document content for WWW server

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

TEXT_TABLE - Text Table

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

Copy and paste ABAP code example for KW_DOCUMENT_GET 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_notetype  TYPE TNOTEEPR-NOTETYPE, "   
lv_document_title  TYPE HIER_TEXTS-TEXT, "   
lt_file_content_ascii  TYPE STANDARD TABLE OF SDOKCNTASC, "   
lv_application  TYPE CHAR6, "   'CU'
lv_document_format  TYPE PROJ_FILE, "   
lt_file_content_binary  TYPE STANDARD TABLE OF SDOKCNTBIN, "   
lv_cancel  TYPE CHAR1, "   
lv_language  TYPE SY-LANGU, "   
lt_text_table  TYPE STANDARD TABLE OF TEXTTAB, "   
lv_objectkey  TYPE TNOTFPR-OBJECTKEY, "   
lv_short_table  TYPE CHAR1, "   
lv_document_class  TYPE SDOK_CLASS. "   'SPRO_GEN'

  CALL FUNCTION 'KW_DOCUMENT_GET'  "
    EXPORTING
         NOTETYPE = lv_notetype
         APPLICATION = lv_application
         LANGUAGE = lv_language
         OBJECTKEY = lv_objectkey
         SHORT_TABLE = lv_short_table
         DOCUMENT_CLASS = lv_document_class
    IMPORTING
         DOCUMENT_TITLE = lv_document_title
         DOCUMENT_FORMAT = lv_document_format
         CANCEL = lv_cancel
    TABLES
         FILE_CONTENT_ASCII = lt_file_content_ascii
         FILE_CONTENT_BINARY = lt_file_content_binary
         TEXT_TABLE = lt_text_table
. " KW_DOCUMENT_GET




ABAP code using 7.40 inline data declarations to call FM KW_DOCUMENT_GET

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 NOTETYPE FROM TNOTEEPR INTO @DATA(ld_notetype).
 
"SELECT single TEXT FROM HIER_TEXTS INTO @DATA(ld_document_title).
 
 
DATA(ld_application) = 'CU'.
 
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
 
 
"SELECT single OBJECTKEY FROM TNOTFPR INTO @DATA(ld_objectkey).
 
 
DATA(ld_document_class) = 'SPRO_GEN'.
 


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!