SAP JV_AM_COBL Function Module for Derive Venture Information from Asset for COBL
JV_AM_COBL is a standard jv am cobl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Derive Venture Information from Asset for COBL 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 jv am cobl FM, simply by entering the name JV_AM_COBL into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJAM
Program Name: SAPLGJAM
Main Program: SAPLGJAM
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JV_AM_COBL 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 'JV_AM_COBL'"Derive Venture Information from Asset for COBL.
EXPORTING
* BUZEI = 0 "dummy
I_COBL = "Coding Block
IMPORTING
E_COBL = "Coding Bolck
IMPORTING Parameters details for JV_AM_COBL
BUZEI - dummy
Data type: BSEG-BUZEIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_COBL - Coding Block
Data type: COBLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for JV_AM_COBL
E_COBL - Coding Bolck
Data type: COBLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JV_AM_COBL 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_buzei | TYPE BSEG-BUZEI, " 0 | |||
| lv_e_cobl | TYPE COBL, " | |||
| lv_i_cobl | TYPE COBL. " |
|   CALL FUNCTION 'JV_AM_COBL' "Derive Venture Information from Asset for COBL |
| EXPORTING | ||
| BUZEI | = lv_buzei | |
| I_COBL | = lv_i_cobl | |
| IMPORTING | ||
| E_COBL | = lv_e_cobl | |
| . " JV_AM_COBL | ||
ABAP code using 7.40 inline data declarations to call FM JV_AM_COBL
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.| "SELECT single BUZEI FROM BSEG INTO @DATA(ld_buzei). | ||||
Search for further information about these or an SAP related objects