SAP CURA_INSTANCE_TO_DB Function Module for NOTRANSL: Schreiben einer Instanz auf die Datenbank

Search SAP Function Modules

CURA_INSTANCE_TO_DB is a standard cura instance to db 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: Schreiben einer Instanz auf die Datenbank 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 cura instance to db FM, simply by entering the name CURA_INSTANCE_TO_DB into the relevant SAP transaction such as SE37 or SE38.

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

Function CURA_INSTANCE_TO_DB 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 'CURA_INSTANCE_TO_DB'"NOTRANSL: Schreiben einer Instanz auf die Datenbank
  EXPORTING
   INSTANCE =  "Configuration (internal object number)
   OBJECT =  "Key of Object to be Classified
   OBTAB =  "Name of database table for object
*  FORCE_NEW_INSTANCE =  "ABAP System Field: Obsolete
*  EXTERNAL_NUMBERRANGE =  "ABAP System Field: Obsolete
*  ROOT_INSTANCE =  "Configuration (internal object number)
*  PARENT_INSTANCE =  "Configuration (internal object number)
*  MATERIAL_VARIANT =  "Material Number

 IMPORTING
   DB_INSTANCE =  "Configuration (internal object number)

EXCEPTIONS
   INVALID_INSTANCE = 1    NO_CHANGES = 2 

.

IMPORTING Parameters details for CURA_INSTANCE_TO_DB

INSTANCE - Configuration (internal object number)

Data type: INOB-CUOBJ
Optional: No
Call by Reference: Yes

OBJECT - Key of Object to be Classified

Data type: INOB-OBJEK
Optional: No
Call by Reference: Yes

OBTAB - Name of database table for object

Data type: INOB-OBTAB
Optional: No
Call by Reference: Yes

FORCE_NEW_INSTANCE - ABAP System Field: Obsolete

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

EXTERNAL_NUMBERRANGE - ABAP System Field: Obsolete

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

ROOT_INSTANCE - Configuration (internal object number)

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

PARENT_INSTANCE - Configuration (internal object number)

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

MATERIAL_VARIANT - Material Number

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

EXPORTING Parameters details for CURA_INSTANCE_TO_DB

DB_INSTANCE - Configuration (internal object number)

Data type: INOB-CUOBJ
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_INSTANCE -

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

NO_CHANGES -

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

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

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