SAP CAD_GET_TITLE_BLOCK_DATA Function Module for NOTRANSL: Daten für den Zeichnungskopf lesen

Search SAP Function Modules

CAD_GET_TITLE_BLOCK_DATA is a standard cad get title block 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 NOTRANSL: Daten für den Zeichnungskopf lesen 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 cad get title block data FM, simply by entering the name CAD_GET_TITLE_BLOCK_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: CADR
Program Name: SAPLCADR
Main Program: SAPLCADR
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CAD_GET_TITLE_BLOCK_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 'CAD_GET_TITLE_BLOCK_DATA'"NOTRANSL: Daten für den Zeichnungskopf lesen
 IMPORTING
   DOCUMENTDATA =  "Document Data
   ECMDATA =  "Change Master
   E_RETURN =  "
   E_MESSAGE =  "Error message

TABLES
   IMPORT_DATA =  "
   OBJECTLINKS =  "Object links
   DOCUMENTDESCRIPTIONS =  "
   LONGTEXTS =  "
   STATUSLOG =  "Status Log
   CLASS_DATA =  "
   EXPORT_DATA =  "
   USER_DATA =  "Customer-specific data

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCADR_001 User Exit: Read drawing head data

EXPORTING Parameters details for CAD_GET_TITLE_BLOCK_DATA

DOCUMENTDATA - Document Data

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

ECMDATA - Change Master

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

E_RETURN -

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

E_MESSAGE - Error message

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

TABLES Parameters details for CAD_GET_TITLE_BLOCK_DATA

IMPORT_DATA -

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

OBJECTLINKS - Object links

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

DOCUMENTDESCRIPTIONS -

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

LONGTEXTS -

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

STATUSLOG - Status Log

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

CLASS_DATA -

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

EXPORT_DATA -

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

USER_DATA - Customer-specific data

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

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

ABAP code using 7.40 inline data declarations to call FM CAD_GET_TITLE_BLOCK_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