SAP JV_PM_ACTIVE Function Module for Check if Procution month processing is active
JV_PM_ACTIVE is a standard jv pm active SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if Procution month processing is active 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 pm active FM, simply by entering the name JV_PM_ACTIVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVPM
Program Name: SAPLGJVPM
Main Program: SAPLGJVPM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function JV_PM_ACTIVE 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_PM_ACTIVE'"Check if Procution month processing is active.
EXPORTING
I_BUKRS = "Company Code
IMPORTING
E_PM_ACTIVE = "Checkbox
E_EG_FROM_PM = "Checkbox
IMPORTING Parameters details for JV_PM_ACTIVE
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for JV_PM_ACTIVE
E_PM_ACTIVE - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
E_EG_FROM_PM - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JV_PM_ACTIVE 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_bukrs | TYPE BUKRS, " | |||
lv_e_pm_active | TYPE XFELD, " | |||
lv_e_eg_from_pm | TYPE XFELD. " |
  CALL FUNCTION 'JV_PM_ACTIVE' "Check if Procution month processing is active |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
IMPORTING | ||
E_PM_ACTIVE | = lv_e_pm_active | |
E_EG_FROM_PM | = lv_e_eg_from_pm | |
. " JV_PM_ACTIVE |
ABAP code using 7.40 inline data declarations to call FM JV_PM_ACTIVE
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