SAP UA_TEXT_OBJECTTYPE Function Module for









UA_TEXT_OBJECTTYPE is a standard ua text objecttype 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 ua text objecttype FM, simply by entering the name UA_TEXT_OBJECTTYPE into the relevant SAP transaction such as SE37 or SE38.

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



Function UA_TEXT_OBJECTTYPE 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 'UA_TEXT_OBJECTTYPE'"
EXPORTING
IO_METADATA = "Metadata of a Costing Solution
ID_OBJECTTYPE = "Costing Solutions Structure Name

IMPORTING
ED_TEXT = "Costing Solutions Structure Name

EXCEPTIONS
DOES_NOT_EXIST = 1
.



IMPORTING Parameters details for UA_TEXT_OBJECTTYPE

IO_METADATA - Metadata of a Costing Solution

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

ID_OBJECTTYPE - Costing Solutions Structure Name

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

EXPORTING Parameters details for UA_TEXT_OBJECTTYPE

ED_TEXT - Costing Solutions Structure Name

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

EXCEPTIONS details

DOES_NOT_EXIST -

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

Copy and paste ABAP code example for UA_TEXT_OBJECTTYPE 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_ed_text  TYPE ABADR_TEXT, "   
lv_io_metadata  TYPE CL_UA_METADATA, "   
lv_does_not_exist  TYPE CL_UA_METADATA, "   
lv_id_objecttype  TYPE UAB_TYPENAME. "   

  CALL FUNCTION 'UA_TEXT_OBJECTTYPE'  "
    EXPORTING
         IO_METADATA = lv_io_metadata
         ID_OBJECTTYPE = lv_id_objecttype
    IMPORTING
         ED_TEXT = lv_ed_text
    EXCEPTIONS
        DOES_NOT_EXIST = 1
. " UA_TEXT_OBJECTTYPE




ABAP code using 7.40 inline data declarations to call FM UA_TEXT_OBJECTTYPE

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!