SAP JV_MANIPULATE_FAGL_CLR_ITEM Function Module for Manipulation of venture data for NewGL clearing items
JV_MANIPULATE_FAGL_CLR_ITEM is a standard jv manipulate fagl clr item SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Manipulation of venture data for NewGL clearing items 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 manipulate fagl clr item FM, simply by entering the name JV_MANIPULATE_FAGL_CLR_ITEM into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVI_FAGL
Program Name: SAPLGJVI_FAGL
Main Program: SAPLGJVI_FAGL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JV_MANIPULATE_FAGL_CLR_ITEM 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_MANIPULATE_FAGL_CLR_ITEM'"Manipulation of venture data for NewGL clearing items.
EXPORTING
IT_DOCUMENT = "
CHANGING
CT_CLR_ITEMS = "
IMPORTING Parameters details for JV_MANIPULATE_FAGL_CLR_ITEM
IT_DOCUMENT -
Data type: GLT0_ACCIT_EX_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for JV_MANIPULATE_FAGL_CLR_ITEM
CT_CLR_ITEMS -
Data type: GLT0_ACCIT_EX_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JV_MANIPULATE_FAGL_CLR_ITEM 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_it_document | TYPE GLT0_ACCIT_EX_TAB, " | |||
| lv_ct_clr_items | TYPE GLT0_ACCIT_EX_TAB. " |
|   CALL FUNCTION 'JV_MANIPULATE_FAGL_CLR_ITEM' "Manipulation of venture data for NewGL clearing items |
| EXPORTING | ||
| IT_DOCUMENT | = lv_it_document | |
| CHANGING | ||
| CT_CLR_ITEMS | = lv_ct_clr_items | |
| . " JV_MANIPULATE_FAGL_CLR_ITEM | ||
ABAP code using 7.40 inline data declarations to call FM JV_MANIPULATE_FAGL_CLR_ITEM
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