SAP CUDB_LOAD_TMP Function Module for NOTRANSL: Globale Daten der DDB und abhängiger Module aus temporärem Forma
CUDB_LOAD_TMP is a standard cudb load tmp 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: Globale Daten der DDB und abhängiger Module aus temporärem Forma 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 cudb load tmp FM, simply by entering the name CUDB_LOAD_TMP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUDB
Program Name: SAPLCUDB
Main Program: SAPLCUDB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUDB_LOAD_TMP 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 'CUDB_LOAD_TMP'"NOTRANSL: Globale Daten der DDB und abhängiger Module aus temporärem Forma.
EXPORTING
NAME = "
EXCEPTIONS
NOT_FOUND = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for CUDB_LOAD_TMP
NAME -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Configuration missing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUDB_LOAD_TMP 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_name | TYPE STRING, " | |||
| lv_not_found | TYPE STRING, " | |||
| lv_internal_error | TYPE STRING. " |
|   CALL FUNCTION 'CUDB_LOAD_TMP' "NOTRANSL: Globale Daten der DDB und abhängiger Module aus temporärem Forma |
| EXPORTING | ||
| NAME | = lv_name | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " CUDB_LOAD_TMP | ||
ABAP code using 7.40 inline data declarations to call FM CUDB_LOAD_TMP
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