SAP READ_DMS_POSTSCRIPT_TEXT Function Module for NOTRANSL: Read POSTSCRIPT text for a Doc. from Doc.Manag.Sys.









READ_DMS_POSTSCRIPT_TEXT is a standard read dms postscript text 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: Read POSTSCRIPT text for a Doc. from Doc.Manag.Sys. 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 read dms postscript text FM, simply by entering the name READ_DMS_POSTSCRIPT_TEXT into the relevant SAP transaction such as SE37 or SE38.

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



Function READ_DMS_POSTSCRIPT_TEXT 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 'READ_DMS_POSTSCRIPT_TEXT'"NOTRANSL: Read POSTSCRIPT text for a Doc. from  Doc.Manag.Sys.
  EXPORTING
   DOCUMENT =  "Document number
   DOCUMENT_TYPE =  "Document Type
   DOCUMENT_PART =  "Document Part
   DOCUMENT_VERS =  "Document Version
*  LANGUAGE = SYST-LANGU "ABAP System Field: Language Key of Text Environment

 IMPORTING
   EPS_TEXT_HEADER =  "SAPscript: Text Header

TABLES
   EPS_TEXT_LINES =  "SAPscript: Text Lines

EXCEPTIONS
   EPS_TEXT_NOT_FOUND = 1
.



IMPORTING Parameters details for READ_DMS_POSTSCRIPT_TEXT

DOCUMENT - Document number

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

DOCUMENT_TYPE - Document Type

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

DOCUMENT_PART - Document Part

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

DOCUMENT_VERS - Document Version

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

LANGUAGE - ABAP System Field: Language Key of Text Environment

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

EXPORTING Parameters details for READ_DMS_POSTSCRIPT_TEXT

EPS_TEXT_HEADER - SAPscript: Text Header

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

TABLES Parameters details for READ_DMS_POSTSCRIPT_TEXT

EPS_TEXT_LINES - SAPscript: Text Lines

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

EXCEPTIONS details

EPS_TEXT_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for READ_DMS_POSTSCRIPT_TEXT 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_document  TYPE DRAW-DOKNR, "   
lt_eps_text_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_eps_text_header  TYPE THEAD, "   
lv_eps_text_not_found  TYPE THEAD, "   
lv_document_type  TYPE DRAW-DOKAR, "   
lv_document_part  TYPE DRAW-DOKTL, "   
lv_document_vers  TYPE DRAW-DOKVR, "   
lv_language  TYPE SY-LANGU. "   SYST-LANGU

  CALL FUNCTION 'READ_DMS_POSTSCRIPT_TEXT'  "NOTRANSL: Read POSTSCRIPT text for a Doc. from Doc.Manag.Sys.
    EXPORTING
         DOCUMENT = lv_document
         DOCUMENT_TYPE = lv_document_type
         DOCUMENT_PART = lv_document_part
         DOCUMENT_VERS = lv_document_vers
         LANGUAGE = lv_language
    IMPORTING
         EPS_TEXT_HEADER = lv_eps_text_header
    TABLES
         EPS_TEXT_LINES = lt_eps_text_lines
    EXCEPTIONS
        EPS_TEXT_NOT_FOUND = 1
. " READ_DMS_POSTSCRIPT_TEXT




ABAP code using 7.40 inline data declarations to call FM READ_DMS_POSTSCRIPT_TEXT

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 DOKNR FROM DRAW INTO @DATA(ld_document).
 
 
 
 
"SELECT single DOKAR FROM DRAW INTO @DATA(ld_document_type).
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_document_part).
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_document_vers).
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SYST-LANGU.
 


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!