SAP JV_PREPARE_THRESH_UPDATE_HOLD Function Module for Prepare update of threshold table to hold data
JV_PREPARE_THRESH_UPDATE_HOLD is a standard jv prepare thresh update hold SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prepare update of threshold table to hold data 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 prepare thresh update hold FM, simply by entering the name JV_PREPARE_THRESH_UPDATE_HOLD into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJV_BTH
Program Name: SAPLGJV_BTH
Main Program: SAPLGJV_BTH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JV_PREPARE_THRESH_UPDATE_HOLD 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_PREPARE_THRESH_UPDATE_HOLD'"Prepare update of threshold table to hold data.
EXPORTING
BUKRS = "Company code
FPER = "Fiscal period
FYEAR = "Fiscal year
THRESHOLDLIST = "
IMPORTING Parameters details for JV_PREPARE_THRESH_UPDATE_HOLD
BUKRS - Company code
Data type: BUKRSOptional: No
Call by Reference: Yes
FPER - Fiscal period
Data type: MONATOptional: No
Call by Reference: Yes
FYEAR - Fiscal year
Data type: GJAHROptional: No
Call by Reference: Yes
THRESHOLDLIST -
Data type: GJVBT_THRESHOLDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JV_PREPARE_THRESH_UPDATE_HOLD 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_bukrs | TYPE BUKRS, " | |||
| lv_fper | TYPE MONAT, " | |||
| lv_fyear | TYPE GJAHR, " | |||
| lv_thresholdlist | TYPE GJVBT_THRESHOLD. " |
|   CALL FUNCTION 'JV_PREPARE_THRESH_UPDATE_HOLD' "Prepare update of threshold table to hold data |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| FPER | = lv_fper | |
| FYEAR | = lv_fyear | |
| THRESHOLDLIST | = lv_thresholdlist | |
| . " JV_PREPARE_THRESH_UPDATE_HOLD | ||
ABAP code using 7.40 inline data declarations to call FM JV_PREPARE_THRESH_UPDATE_HOLD
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