SAP JV_GET_CURRENT_BILLING_AMOUNT Function Module for Get current amount to be billed in JVA









JV_GET_CURRENT_BILLING_AMOUNT is a standard jv get current billing amount SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get current amount to be billed in JVA 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 get current billing amount FM, simply by entering the name JV_GET_CURRENT_BILLING_AMOUNT 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_GET_CURRENT_BILLING_AMOUNT 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_GET_CURRENT_BILLING_AMOUNT'"Get current amount to be billed in JVA
EXPORTING
BUKRS = "Company code
FPER = "Fiscal period
FYEAR = "Fiscal year
BILL_LEVEL = "Joint Venture Invoice Level
BILIST = "Billing indicator list

CHANGING
THRESHOLDLIST = "
.



IMPORTING Parameters details for JV_GET_CURRENT_BILLING_AMOUNT

BUKRS - Company code

Data type: BUKRS
Optional: No
Call by Reference: Yes

FPER - Fiscal period

Data type: MONAT
Optional: No
Call by Reference: Yes

FYEAR - Fiscal year

Data type: GJAHR
Optional: No
Call by Reference: Yes

BILL_LEVEL - Joint Venture Invoice Level

Data type: JV_INVLVL
Optional: No
Call by Reference: Yes

BILIST - Billing indicator list

Data type: GJVBT_BILL
Optional: No
Call by Reference: Yes

CHANGING Parameters details for JV_GET_CURRENT_BILLING_AMOUNT

THRESHOLDLIST -

Data type: GJVBT_THRESHOLD
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JV_GET_CURRENT_BILLING_AMOUNT 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_thresholdlist  TYPE GJVBT_THRESHOLD, "   
lv_fper  TYPE MONAT, "   
lv_fyear  TYPE GJAHR, "   
lv_bill_level  TYPE JV_INVLVL, "   
lv_bilist  TYPE GJVBT_BILL. "   

  CALL FUNCTION 'JV_GET_CURRENT_BILLING_AMOUNT'  "Get current amount to be billed in JVA
    EXPORTING
         BUKRS = lv_bukrs
         FPER = lv_fper
         FYEAR = lv_fyear
         BILL_LEVEL = lv_bill_level
         BILIST = lv_bilist
    CHANGING
         THRESHOLDLIST = lv_thresholdlist
. " JV_GET_CURRENT_BILLING_AMOUNT




ABAP code using 7.40 inline data declarations to call FM JV_GET_CURRENT_BILLING_AMOUNT

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!