SAP JBD_DB_GTVS_ARCH_JBRHKO_INS Function Module for Tabellenspezifischer Einfügebaustein für JBRHKO
JBD_DB_GTVS_ARCH_JBRHKO_INS is a standard jbd db gtvs arch jbrhko ins SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Tabellenspezifischer Einfügebaustein für JBRHKO 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 jbd db gtvs arch jbrhko ins FM, simply by entering the name JBD_DB_GTVS_ARCH_JBRHKO_INS into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBD_GTVS_ARCH_DB
Program Name: SAPLJBD_GTVS_ARCH_DB
Main Program: SAPLJBD_GTVS_ARCH_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JBD_DB_GTVS_ARCH_JBRHKO_INS 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 'JBD_DB_GTVS_ARCH_JBRHKO_INS'"Tabellenspezifischer Einfügebaustein für JBRHKO.
EXPORTING
I_TAB_DATA = "Standard-Tabellentyp für Tabelle JBRHKO
EXCEPTIONS
DATABASE_ERROR = 1
IMPORTING Parameters details for JBD_DB_GTVS_ARCH_JBRHKO_INS
I_TAB_DATA - Standard-Tabellentyp für Tabelle JBRHKO
Data type: JBD_TAB_JBRHKOOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATABASE_ERROR - Fehler beim Einfügen aufgetreten
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JBD_DB_GTVS_ARCH_JBRHKO_INS 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_i_tab_data | TYPE JBD_TAB_JBRHKO, " | |||
| lv_database_error | TYPE JBD_TAB_JBRHKO. " |
|   CALL FUNCTION 'JBD_DB_GTVS_ARCH_JBRHKO_INS' "Tabellenspezifischer Einfügebaustein für JBRHKO |
| EXPORTING | ||
| I_TAB_DATA | = lv_i_tab_data | |
| EXCEPTIONS | ||
| DATABASE_ERROR = 1 | ||
| . " JBD_DB_GTVS_ARCH_JBRHKO_INS | ||
ABAP code using 7.40 inline data declarations to call FM JBD_DB_GTVS_ARCH_JBRHKO_INS
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