SAP GJV_DRB_ORIGIN_GET Function Module for JV im DRB: Herkunft ermitteln
GJV_DRB_ORIGIN_GET is a standard gjv drb origin get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for JV im DRB: Herkunft ermitteln 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 gjv drb origin get FM, simply by entering the name GJV_DRB_ORIGIN_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJV_DRB
Program Name: SAPLGJV_DRB
Main Program: SAPLGJV_DRB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GJV_DRB_ORIGIN_GET 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 'GJV_DRB_ORIGIN_GET'"JV im DRB: Herkunft ermitteln.
EXPORTING
I_BORIDENT = "Object Relationship Service: BOR Object Identifier
IMPORTING
E_ORIGIN = "Origin of Data for Object
IMPORTING Parameters details for GJV_DRB_ORIGIN_GET
I_BORIDENT - Object Relationship Service: BOR Object Identifier
Data type: BORIDENTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GJV_DRB_ORIGIN_GET
E_ORIGIN - Origin of Data for Object
Data type: SDRBORIGINOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GJV_DRB_ORIGIN_GET 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_e_origin | TYPE SDRBORIGIN, " | |||
| lv_i_borident | TYPE BORIDENT. " |
|   CALL FUNCTION 'GJV_DRB_ORIGIN_GET' "JV im DRB: Herkunft ermitteln |
| EXPORTING | ||
| I_BORIDENT | = lv_i_borident | |
| IMPORTING | ||
| E_ORIGIN | = lv_e_origin | |
| . " GJV_DRB_ORIGIN_GET | ||
ABAP code using 7.40 inline data declarations to call FM GJV_DRB_ORIGIN_GET
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