SAP UPB_CHAVL_FISCPER_GET Function Module for









UPB_CHAVL_FISCPER_GET is a standard upb chavl fiscper get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 upb chavl fiscper get FM, simply by entering the name UPB_CHAVL_FISCPER_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: UPBS
Program Name: SAPLUPBS
Main Program: SAPLUPBS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function UPB_CHAVL_FISCPER_GET 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 'UPB_CHAVL_FISCPER_GET'"
EXPORTING
I_AREA = "
I_FISCVARNT = "
* I_PER3_START = "
* I_YEAR_START = "
* I_PER_START = "
* I_PER3_END = "
* I_YEAR_END = "
* I_PER_END = "
* I_PER_COUNT = "

IMPORTING
ETO_CHAVLINT = "

EXCEPTIONS
PARAMETER_ERROR = 1 RFC_ERROR = 2 FAILED = 3 OUT_OF_RANGE = 4
.



IMPORTING Parameters details for UPB_CHAVL_FISCPER_GET

I_AREA -

Data type: UPC_Y_AREA
Optional: No
Call by Reference: No ( called with pass by value option)

I_FISCVARNT -

Data type: UPC_Y_CHAVLINT
Optional: No
Call by Reference: No ( called with pass by value option)

I_PER3_START -

Data type: UPB_Y_PERDE3
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_YEAR_START -

Data type: UPB_Y_YEAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PER_START -

Data type: UPB_Y_PERDE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PER3_END -

Data type: UPB_Y_PERDE3
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_YEAR_END -

Data type: UPB_Y_YEAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PER_END -

Data type: UPB_Y_PERDE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PER_COUNT -

Data type: I
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UPB_CHAVL_FISCPER_GET

ETO_CHAVLINT -

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

OUT_OF_RANGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPB_CHAVL_FISCPER_GET 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_area  TYPE UPC_Y_AREA, "   
lv_eto_chavlint  TYPE UPB_YTO_CHAVL_PLAIN, "   
lv_parameter_error  TYPE UPB_YTO_CHAVL_PLAIN, "   
lv_rfc_error  TYPE UPB_YTO_CHAVL_PLAIN, "   
lv_i_fiscvarnt  TYPE UPC_Y_CHAVLINT, "   
lv_failed  TYPE UPC_Y_CHAVLINT, "   
lv_i_per3_start  TYPE UPB_Y_PERDE3, "   
lv_i_year_start  TYPE UPB_Y_YEAR, "   
lv_out_of_range  TYPE UPB_Y_YEAR, "   
lv_i_per_start  TYPE UPB_Y_PERDE, "   
lv_i_per3_end  TYPE UPB_Y_PERDE3, "   
lv_i_year_end  TYPE UPB_Y_YEAR, "   
lv_i_per_end  TYPE UPB_Y_PERDE, "   
lv_i_per_count  TYPE I. "   

  CALL FUNCTION 'UPB_CHAVL_FISCPER_GET'  "
    EXPORTING
         I_AREA = lv_i_area
         I_FISCVARNT = lv_i_fiscvarnt
         I_PER3_START = lv_i_per3_start
         I_YEAR_START = lv_i_year_start
         I_PER_START = lv_i_per_start
         I_PER3_END = lv_i_per3_end
         I_YEAR_END = lv_i_year_end
         I_PER_END = lv_i_per_end
         I_PER_COUNT = lv_i_per_count
    IMPORTING
         ETO_CHAVLINT = lv_eto_chavlint
    EXCEPTIONS
        PARAMETER_ERROR = 1
        RFC_ERROR = 2
        FAILED = 3
        OUT_OF_RANGE = 4
. " UPB_CHAVL_FISCPER_GET




ABAP code using 7.40 inline data declarations to call FM UPB_CHAVL_FISCPER_GET

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!